db2z 12 Codesbook

Db2 12 for z/OS
Codes
Last updated: 2023-11-28
IBM
GC27-8847-02
Notes
Before using this information and the product it supports, be sure to read the general information under
"Notices" at the end of this information.
Subsequent editions of this PDF will not be delivered in IBM Publications Center. Always download the
latest edition from IBM Documentation.
2023-11-28 edition
This edition applies to Db2® 12 for z/OS® (product number 5650-DB2), Db2 12 for z/OS Value Unit Edition (product
number 5770-AF3), and to any subsequent releases until otherwise indicated in new editions. Make sure you are using
the correct edition for the level of the product.
Specific changes are indicated by a vertical bar to the left of a change. A vertical bar to the left of a figure caption
indicates that the figure has changed. Editorial changes that have no technical significance are not noted.
© Copyright International Business Machines Corporation 1983, 2023.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
Contents
About this information .......................................................................................... v

Who should read this information...............................................................................................................vi
Db2 Utilities Suite for z/OS..........................................................................................................................vi
Terminology and citations........................................................................................................................... vi
Accessibility features for Db2 for z/OS...................................................................................................... vii
How to send comments..............................................................................................................................vii
How to interpret code numbers................................................................................................................ viii
Subcomponent identifiers in Db2 messages and codes..................................................................... viii
How to find additional information about messages.................................................................................. x
Part 1. SQL codes.................................................................................................. 1
Chapter 1. Success (0) and warning (+) SQL codes.................................................................................... 3
Chapter 2. Error (−) SQL codes ................................................................................................................. 39
Part 2. Db2 reason codes................................................................................... 373
Chapter 3. X'C1......' codes.......................................................................................................................375
Chapter 4. X'C2......' codes.......................................................................................................................391
Chapter 5. X'C5......' codes.......................................................................................................................447
Chapter 6. X'C6......' codes.......................................................................................................................453
Chapter 7. X'C8......' codes.......................................................................................................................455
Chapter 8. X'C9......' codes.......................................................................................................................457
Chapter 9. X'D1......' codes.......................................................................................................................527
Chapter 10. X'D3......' codes.................................................................................................................... 597
Chapter 11. X'D4......' codes.................................................................................................................... 871
Chapter 12. X'D5......' codes.................................................................................................................... 885
Chapter 13. X'D6......' codes.................................................................................................................... 887
Chapter 14. X'D7......' codes.................................................................................................................... 889
Chapter 15. X'D9......' codes.................................................................................................................... 909
Chapter 16. X'E2......' codes.....................................................................................................................939
Chapter 17. X'E3......' codes.....................................................................................................................961
Chapter 18. X'E4......' codes.....................................................................................................................995
iii
Chapter 19. X'E5......' codes.................................................................................................................. 1109
Chapter 20. X'E6......' codes.................................................................................................................. 1147
Chapter 21. X'E7......' codes.................................................................................................................. 1189
Chapter 22. X'E8......' codes.................................................................................................................. 1219
Chapter 23. X'E9......' codes.................................................................................................................. 1243
Chapter 24. X'F1......' codes...................................................................................................................1247
Chapter 25. X'F3......' codes...................................................................................................................1249
Chapter 26. X'F7......' codes...................................................................................................................1319
Chapter 27. X'F9......' codes...................................................................................................................1325
Appendix A. SNA sense codes ......................................................................... 1331
Appendix B. New, changed, and deleted codes................................................. 1339
Appendix C. z/OS diagnostic services............................................................... 1341
Appendix D. SQLSTATE values and common error codes....................................1343
Appendix E. Db2 abend completion codes (X'04E' and X'04F)............................1375
Appendix F. Resource types............................................................................. 1377
Appendix G. Service task plan names............................................................... 1383
Appendix H. ABEND codes associated with DSN1COPY misuse......................... 1385
Information resources for Db2 for z/OS and related products............................ 1391
Notices............................................................................................................1393
Programming interface information......................................................................................................1394
Trademarks............................................................................................................................................1394
Terms and conditions for product documentation............................................................................... 1394
Privacy policy considerations................................................................................................................1395
Glossary.......................................................................................................... 1397
iv
About this information
This information helps you to understand the codes that you could receive while working with Db2 12 for
z/OS (Db2 for z/OS). The topics provide detailed descriptions of the codes that are issued by Db2, with
explanations and user responses for the situations that are associated with these codes.
Throughout this information, "Db2" means "Db2 12 for z/OS". References to other Db2 products use
complete names or specific abbreviations.
Important: To find the most up to date content for Db2 12 for z/OS, always use IBM® Documentation
or download the latest PDF file from PDF format manuals for Db2 12 for z/OS (Db2 for z/OS in IBM
Documentation).
Most documentation topics for Db2 12 for z/OS assume that the highest available function level is
activated and that your applications are running with the highest available application compatibility level,
with the following exceptions:
• The following documentation sections describe the Db2 12 migration process and how to activate new
capabilities in function levels:
– Migrating to Db2 12 (Db2 Installation and Migration)
– What's new in Db2 12 (Db2 for z/OS What's New?)
– Adopting new capabilities in Db2 12 continuous delivery (Db2 for z/OS What's New?)
• FL 501 A label like this one usually marks documentation changed for function level 500 or higher,
with a link to the description of the function level that introduces the change in Db2 12. For more
information, see How Db2 function levels are documented (Db2 for z/OS What's New?).
The availability of new function depends on the type of enhancement, the activated function level, and
the application compatibility levels of applications. In the initial Db2 12 release, most new capabilities are
enabled only after the activation of function level 500 or higher.
Virtual storage enhancements
Virtual storage enhancements become available at the activation of the function level that introduces
them or higher. Activation of function level 100 introduces all virtual storage enhancements in
the initial Db2 12 release. That is, activation of function level 500 introduces no virtual storage
enhancements.
Subsystem parameters
New subsystem parameter settings are in effect only when the function level that introduced them or
a higher function level is activated. Many subsystem parameter changes in the initial Db2 12 release
take effect in function level 500. For more information about subsystem parameter changes in Db2
12, see Subsystem parameter changes in Db2 12 (Db2 for z/OS What's New?).
Optimization enhancements
Optimization enhancements become available after the activation of the function level that introduces
them or higher, and full prepare of the SQL statements. When a full prepare occurs depends on the
statement type:
• For static SQL statements, after bind or rebind of the package
• For non-stabilized dynamic SQL statements, immediately, unless the statement is in the dynamic
statement cache
• For stabilized dynamic SQL statements, after invalidation, free, or changed application compatibility
level
Activation of function level 100 introduces all optimization enhancements in the initial Db2 12
release. That is, function level 500 introduces no optimization enhancements.
SQL capabilities
New SQL capabilities become available after the activation of the function level that introduces them
or higher, for applications that run at the equivalent application compatibility level or higher. New SQL
© Copyright IBM Corp. 1983, 2023 v

capabilities in the initial Db2 12 release become available in function level 500 for applications that
run at the equivalent application compatibility level or higher. You can continue to run SQL statements
compatibly with lower function levels, or previous Db2 releases, including Db2 11 and DB2® 10. For
details, see Application compatibility levels in Db2 (Db2 Application programming and SQL)
Who should read this information

Db2 Codes lists codes that are issued by Db2, with explanations and suggested responses. This
information is intended for users and system programmers who might encounter Db2 messages and
codes.
Db2 Utilities Suite for z/OS

Important: Db2 Utilities Suite for z/OS is available as an optional product. You must separately order
and purchase a license to such utilities, and discussion of those utility functions in this publication is not
intended to otherwise imply that you have a license to them.
Db2 12 utilities can use the DFSORT program regardless of whether you purchased a license for DFSORT
on your system. For more information about DFSORT, see https://www.ibm.com/support/pages/dfsort.
Db2 utilities can use IBM Db2 Sort for z/OS as an alternative to DFSORT for utility SORT and MERGE
functions. Use of Db2 Sort for z/OS requires the purchase of a Db2 Sort for z/OS license. For more
information about Db2 Sort for z/OS, see Db2 Sort for z/OS documentation.
Related concepts
Db2 utilities packaging (Db2 Utilities)
Terminology and citations

When referring to a Db2 product other than Db2 for z/OS, this information uses the product's full name to
avoid ambiguity.
The following terms are used as indicated:
Db2
Represents either the Db2 licensed program or a particular Db2 subsystem.
IBM rebranded DB2 to Db2, and Db2 for z/OS is the new name of the offering that was previously
known as "DB2 for z/OS". For more information, see Revised naming for IBM Db2 family products on
IBM z/OS platform. As a result, you might sometimes still see references to the original names, such
as "DB2 for z/OS" and "DB2", in different IBM web pages and documents. If the PID, Entitlement
Entity, version, modification, and release information match, assume that they refer to the same
product.
IBM OMEGAMON® for Db2 Performance Expert on z/OS
Refers to any of the following products:
• IBM IBM OMEGAMON for Db2 Performance Expert on z/OS
• IBM Db2 Performance Monitor on z/OS
• IBM Db2 Performance Expert for Multiplatforms and Workgroups
• IBM Db2 Buffer Pool Analyzer for z/OS
C, C++, and C language
Represent the C or C++ programming language.
CICS®
Represents CICS Transaction Server for z/OS.
IMS
Represents the IMS Database Manager or IMS Transaction Manager.
vi About this information

MVS™
Represents the MVS element of the z/OS operating system, which is equivalent to the Base Control
Program (BCP) component of the z/OS operating system.
RACF®
Represents the functions that are provided by the RACF component of the z/OS Security Server.
Accessibility features for Db2 for z/OS

Accessibility features help a user who has a physical disability, such as restricted mobility or limited
vision, to use information technology products successfully.
Accessibility features
The following list includes the major accessibility features in z/OS products, including Db2 for z/OS. These
features support:
• Keyboard-only operation.
• Interfaces that are commonly used by screen readers and screen magnifiers.
• Customization of display attributes such as color, contrast, and font size
Tip: IBM Documentation (which includes information for Db2 for z/OS) and its related publications are
accessibility-enabled for the IBM Home Page Reader. You can operate all features using the keyboard
instead of the mouse.
Keyboard navigation
For information about navigating the Db2 for z/OS ISPF panels using TSO/E or ISPF, refer to the z/OS
TSO/E Primer, the z/OS TSO/E User's Guide, and the z/OS ISPF User's Guide. These guides describe how
to navigate each interface, including the use of keyboard shortcuts or function keys (PF keys). Each guide
includes the default settings for the PF keys and explains how to modify their functions.
Related accessibility information
IBM and accessibility

See the IBM Accessibility Center at http://www.ibm.com/able for more information about the commitment
that IBM has to accessibility.
How to send your comments about Db2 for z/OS documentation

Your feedback helps IBM to provide quality documentation.
Send any comments about Db2 for z/OS and related product documentation by email to
db2zinfo@us.ibm.com.
To help us respond to your comment, include the following information in your email:
• The product name and version
• The address (URL) of the page, for comments about online documentation
• The book name and publication date, for comments about PDF manuals
• The topic or section title
• The specific text that you are commenting about and your comment
Related concepts
About this information (Db2 for z/OS in IBM Documentation)
Related reference
PDF format manuals for Db2 12 for z/OS (Db2 for z/OS in IBM Documentation)
About this information vii

How to interpret code numbers
Db2 issues SQL execution codes, reason codes, abend reason codes, and Db2 instrumentation facility
interface reason codes to communicate about normal and error situations. The format of the code
numbers can help you understand what the code applies to.
Db2 SQL return code format

SQL return codes have the following format:
-418
sign
With the exception of the return code 000, SQL return codes are prefixed with either a + or - sign. The
sign represents either success (+) or error (-).
Regardless of whether the application program provides an SQLCA or a stand-alone variable,
SQLCODE is set by Db2 after each SQL statement is executed.
number
The length of the numeric portion of an SQL return code is three to five digits.
Db2 reason code format

All Db2 reason codes, including subsystem termination reason codes, are four bytes long and have the
following format:
00E50041
00
The first byte is always 00, which is the high-order byte.
E5
The second byte is the hexadecimal identifier (hex ID), which identifies the Db2 subcomponent. In
this example, E5 identifies the Db2 agent services manager. For more information, see Subcomponent
identifiers in Db2 messages and codes (Db2 Messages).
0041
The last two bytes are the numeric identifier, which is unique within the subcomponent.
The Db2 reason codes are grouped by hexadecimal identifier and listed in numeric order.
Related concepts
SQL codes
When Db2 executes an SQL statement, it returns information about the statement execution. This
information includes the SQL return code (SQLCODE) and the SQLSTATE, which indicate whether
statement execution was successful.
Db2 reason codes
Reason codes are typically presented as a value in a message that Db2 issues. The reason codes provide
specific details about the circumstances of a particular instance of the message.
Subcomponent identifiers in Db2 messages and codes

The identifiers for messages or reason codes in Db2 indicate the associated Db2 subcomponent or
functional area.
The following table lists the Db2 subcomponents and functional areas and the identifiers that are
associated with each one. Some message identifiers are shared by more than one subcomponent or
functional area. Also, subcomponents can call each other, so one subcomponent might return messages
with reason codes from another.
viii About this information

Table 1. Subcomponent identifiers used in Db2 messages and reason codes
Subcomponent or functional Identifier for messages Identifier for reason codes
area
Call attachment facility and some A X'C1'
Db2 supplied stored procedures
Buffer manager B X'C2'
TSO attachment facility E X'C5'
Message generator F X'C6'
Database descriptor manager G n/a
Precompiler, DSNH CLIST H X'C8'
Data manager I X'C9'
Recovery log manager J X'D1'
Distributed data facility L X'D3'
IMS attachment facility M X'D4'
XML manager n/a X'D5'
Data space manager P X'D7'
MQListener Q n/a
Recovery manager R X'D9'
Storage manager S X'E2'
Service controller, install T X'E3'
Utilities U X'E4'
Agent services manager V X'E5'
Instrumentation facility W X'E6'
Relational data system X X'E7'
Initialization procedures Y X'E8'
System parameter manager Z X'E9'
Service facilities 1 X'F1'
Subsystem support 3 X'F3'
subcomponent
Group manager 7 X'F7'
Db2 Accessories Suite for z/OS 5 n/a
Sample applications 8 X'F8'
General command processor 9 X'F9'
Messages with DSNC and DSN2 identifiers and codes in the X'C3®' range were previously used to display
CICS messages. For information about CICS messages, see the information in the Search the CICS
Library..
Related concepts
How to interpret code numbers
About this information ix

Db2 issues SQL execution codes, reason codes, abend reason codes, and Db2 instrumentation facility
interface reason codes to communicate about normal and error situations. The format of the code
numbers can help you understand what the code applies to.
How to interpret message numbers (Db2 Messages)
How to find additional information about messages

When you are working with Db2, you might encounter messages issued by other IBM products, such as
IMS, CICS, or z/OS. Information about messages issued by these and other IBM products is available in
IBM Documentation.
CICS
Information for multiple versions of CICS are available as part of the CICS library. Search the CICS
Library..
IMS
IMS messages are available in IMS messages and codes.
IRLM
Messages and codes related to the IRLM, which were previously part of this information, are now
provided in IRLM messages and codes (IRLM messages and codes). IRLM messages have the prefix
dxr.
• IRLM return and reason codes (IRLM messages and codes)
• IRLM abend codes (IRLM messages and codes)
• DXR messages (IRLM messages and codes)
z/OS
Information for multiple versions of z/OS is available as part of the z/OS library. Search the z/OS
library..
x Db2 12 for z/OS: Codes (Last updated: 2023-11-28)

Part 1. SQL codes
When Db2 executes an SQL statement, it returns information about the statement execution. This
information includes the SQL return code (SQLCODE) and the SQLSTATE, which indicate whether
statement execution was successful.
SQLCODE
The SQLCODE value is set by Db2 after each statement is executed, as shown in the following table.
SQLCODE value Meaning SQLCODE descriptions

SQLCODE = 0 Successful execution, if SQLWARN0 is blank. 000
If SQLWARN0 = 'W', successful execution with
warning.
SQLCODE = 100 No data was found. For example, a FETCH +100

statement returned no data because the cursor
was positioned after the last row of the result
table.
SQLCODE > 0 and not = Successful execution with a warning. +warning-sqlcodes
100
SQLCODE < 0 Execution was not successful. −error-sqlcodes
How applications receive SQL codes

An application program that contains executable SQL statements must do one of the following things:
• Declare SQLCODE and SQLSTATE (SQLCOD and SQLSTA in Fortran) as stand-alone host variables. If
you specify the STDSQL(YES) precompiler or SQL statement coprocessor option, these host variables
receive the return codes, and you should not include an SQLCA in your program.
• Provide a structure named SQLCA. The SQLCA includes the SQLCODE and SQLSTATE, in addition to
other status information. You can provide an SQLCA by using the INCLUDE SQLCA statement. You
can call the DSNTIAR sample subroutine from your application program to format the contents of the
SQLCA, or you can retrieve fields from the SQLCA yourself.
Regardless of whether the application program provides an SQLCA or a stand-alone variable, SQLCODE is
set by Db2 after each SQL statement is executed.
Tokens in SQL code message text

In this section, the italicized phrases in the SQL return code message text corresponds to the tokens
that are returned in the SQLERRMC field of the SQLCA. If Db2 returns several tokens, they appear
sequentially in SQLERRMC in the order that they appear in the message text. At most, 70 bytes are
returned for a message token because the SQLERRMC field of the SQLCA is limited to 70 bytes. Use
the GET DIAGNOSTICS statement with a DB2_ORDINAL_TOKEN_n keyword to obtain the full value of a
message token.
In some cases a token is not applicable or available for a specific instance of an error, and *N is returned
instead.
Tokens might sometimes refer to the names of objects on accelerators instead of the names of associated
objects on Db2.
© Copyright IBM Corp. 1983, 2023 1

SQLSTATE
SQLSTATE is also set by Db2 after the execution of each SQL statement. Thus, application programs can
check the execution of SQL statements by testing SQLSTATE instead of SQLCODE. SQLSTATE (SQLSTT in
FORTRAN) is a 5-byte character string variable in the SQLCA.
SQLSTATE provides application programs with common codes for common error conditions (the values of
SQLSTATE are product-specific only if the error or warning is product-specific). Furthermore, SQLSTATE is
designed so that application programs can test for specific errors or classes of errors. The coding scheme
is the same for all IBM relational database products.
Related concepts
SQL communication area (SQLCA) (Db2 SQL)
Related tasks
Checking the execution of SQL statements by using the SQLCA (Db2 Application programming and SQL)
Displaying SQLCA fields by calling DSNTIAR (Db2 Application programming and SQL)
Handling SQL error codes (Db2 Application programming and SQL)
Related reference
Description of SQLCA fields (Db2 SQL)
SQLSTATE values and common error codes
Db2 produces SQLSTATE values when it works as an application server or requester.
SQLCODE (Db2 SQL)
2 Db2 12 for z/OS: Codes (Last updated: 2023-11-28)

Chapter 1. Success (0) and warning (+) SQL codes
SQL return codes that are preceded by a plus sign (+) indicate that the SQL statement execution was
successful.
Some interfaces that return SQL conditions, such as SPUFI, might return the final SQLCODE condition
first, followed by any prior SQLCODE conditions incurred as a SQL statement was executed. If the final
SQLCODE is an error, most prior SQLCODE warning conditions can be ignored.
Successful SQL execution codes for Java programs: For information on SQL execution codes in the
range +4200 to +4299, and +4450 to +4499, see Error codes issued by the IBM Data Server Driver for
JDBC and SQLJ (Db2 Application Programming for Java).
List of success and warning SQL codes

The following SQL codes indicate successful execution of the SQL statement or successful execution with
a warning.
Related reference
SQLCODE (Db2 SQL)
000 SUCCESSFUL EXECUTION System action

The column name is interpreted as a correlated
Explanation reference.
Unqualified successful execution or successful
execution with one or more warnings. Programmer response
If SQLWARN0 is blank, there are no warnings. If If Db2 interpretates the column name differently
SQLWARN0 = W, at least one of the other warning than you intended, rewrite the SQL statement and
indicators in the SQLCA has been set to indicate a submit it again. If you intend the column name to
warning condition. For example, SQLWARN1 is used to refer to a table named at a higher level, we advise
indicate that a value of a string column was truncated rewriting the statement anyway, using a table name or
when assigned to a host variable. correlation name as a qualifier for the column name.
The unqualified column name could be interpreted
SQLSTATE differently if you do a rebind after altering one of the
tables to which you refer.
• 00000 for unqualified successful execution.
• 01003, 01004, 01503, 01504, 01505, 01506, SQLSTATE
01507, 01517, or 01524 for successful execution
with warning. 01545
Related concepts +020 BIND, REBIND, OR PRECOMPILE

SQL communication area (SQLCA) (Db2 SQL) OPTION option-name IS NOT
SUPPORTED BY THE TARGET
Related reference
SERVER AND WILL BE IGNORED.
+012 THE UNQUALIFIED COLUMN NAME Explanation

column-name WAS INTERPRETED At least one option specified at bind, rebind, or
AS A CORRELATED REFERENCE precompile time is not supported by the target server.
option-name
Explanation
The name of the first unsupported option.
The column name does not identify a column of a table
or view in the FROM clause of the subquery. However,
it does identify a column of a table or view in a FROM
clause at a higher level in the statement.

System action • No available rows qualified for return when SKIP
LOCKED DATA was specified with isolation level CS
Processing continues, but the unsupported options are or RS.
ignored.
• A FETCH statement that returns a rowset was
issued, but there were not enough rows after the
User response current cursor position to reposition the cursor on
Ensure that the specification of bind, rebind, or a full rowset. The cursor has been positioned on a
precompile option names or the associated option partial rowset. If a target was specified, data was
values was intended while connected to this server. returned only for the number of rows that were
actually fetched for the partial rowset. The number
of rows that were returned is in field SQLERRD3 of
SQLSTATE the SQLCA.
01615 When a SELECT statement is executed using SPUFI,
Related reference this SQLCODE indicates normal completion.
BIND PACKAGE (DSN) (Db2 Commands) This SQLCODE is also issued when LOB data cannot
REBIND PACKAGE (DSN) (Db2 Commands) be returned. This situation can occur when an
application is running with isolation level UR and
+098 A DYNAMIC SQL STATEMENT another application has locked the LOB table space.
ENDS WITH A SEMICOLON.
System action
Explanation
No data was retrieved, updated, or deleted.
The statement string of a PREPARE or EXECUTE
IMMEDIATE statement is a valid dynamic SQL SQLSTATE
statement, but it ends with a semicolon.
02000
System action +110 SQL UPDATE TO A DATA
CAPTURE TABLE NOT SIGNALED
The semicolon and any subsequent text are ignored.
TO ORIGINATING SUBSYSTEM
Programmer response
Explanation
Check that the semicolon is being used as a statement
IMS DataPropagator exit routine issued an SQL data
terminator.
change statement to a table defined with DATA
CAPTURE CHANGES. Since data capture is already in
SQLSTATE progress, notification is not sent back to the originating
01568 IMS subsystem.
+100 ROW NOT FOUND FOR FETCH,

System action
UPDATE OR DELETE, OR THE
RESULT OF A QUERY IS AN EMPTY Db2 changes the data and records the change in the
TABLE log. Db2 does not notify IMS DataPropagator's exit
routine of the change, because doing so might cause
Explanation the same change to be made again.
One of the following conditions occurred:

SQLSTATE
• No row met the search conditions specified in an
01561
UPDATE or DELETE statement.
• The result of a SELECT INTO statement was an +111 THE SUBPAGES OPTION IS NOT
empty table. SUPPORTED FOR TYPE 2 INDEXES
• The result of the subselect of an INSERT statement
is empty. Explanation
• A FETCH statement was executed when the cursor You cannot use the SUBPAGES option for type 2
was positioned after the last row of the result table. indexes.

System action Programmer response
The option is ignored and processing continues. Run the CHECK DATA utility. The enforcement of
the referential constraint or the check constraint is
Programmer response deferred until the CHECK DATA utility is run.
Remove the SUBPAGES option to get rid of the

SQLSTATE
warning.
01514
SQLSTATE +203 THE QUALIFIED COLUMN NAME
01590 column-name WAS RESOLVED
USING A NON-UNIQUE OR
+117 THE NUMBER OF INSERT VALUES UNEXPOSED NAME
IS NOT THE SAME AS THE
NUMBER OF OBJECT COLUMNS
Explanation
Explanation The table designator selected to resolve a qualified
column name is one of the following:
The number of insert values in the value list of the
• An unexposed name
insert operation is not the same as the number of
object columns specified. • An exposed name that has an exposed duplicate in
the same FROM clause
System action • An exposed name that has an unexposed duplicate
which appears before the selected name in the
A valid plan or package will be created if no errors are ordered list of names to which the qualifier is
detected. The statement is bound dynamically on each compared
execution of the statement.
Therefore, the statement does not conform to the
guidelines for using only unique exposed names as
Programmer response qualifiers or it is possible that the column reference
For better performance, rebind the plan or package was not resolved to the intended instance of the table
after correcting the statement. To correct the or view.
statement, specify one and only one value for each of
the specified object columns. System action
Db2 uses the selected name to resolve the reference.
SQLSTATE
01525 Programmer response
+162 TABLESPACE database- If Db2 did not resolve of the qualifier how you
name.tablespace-name HAS BEEN intended, rewrite the SQL statement and submit it
PLACED IN CHECK PENDING again.
Explanation SQLSTATE
The indicated table space is in check pending status 01552
because the ALTER TABLE statement was used to
specify either of the following: Related concepts
Resolution of column name qualifiers and
• A referential constraint column names (Db2 SQL)
• A check constraint, when the CURRENT RULES Qualified column names (Db2 SQL)
special register is set to 'DB2' Language elements (Db2 SQL)
The table space is not generally available until the
check pending status is removed from the table space. +204 name IS AN UNDEFINED NAME
System action
The table space was placed in check pending status.
Chapter 1. Success (0) and warning (+) SQL codes 5

Explanation • In the case of an INSERT or UPDATE statement, or
SELECT FROM INSERT or UPDATE statement, the
The object identified by name is not defined in the Db2 specified column is not a column of the table or
subsystem. This return code can be generated for any view that was specified as the object of the insert
type of Db2 object. or update.
• In the case a SELECT or DELETE statement, the
System action specified column is not a column of any of the
A valid plan or package will be created if no errors are tables or views identified in a FROM clause in the
detected. The statement is bound dynamically on each statement.
execution of the statement. • There is a correlated reference in GROUP BY.
• There is an unresolved qualified reference in
Programmer response HAVING.
For better performance, rebind the plan or package • In the case of a MERGE statement or SELECT from
after correcting the statement. To correct the MERGE statement, the specified column is not a
statement, determine that the object name was column in the target-table. Also, it is not a column
correctly specified in the SQL statement (including any specified in the include-columns clause.
required qualifiers). If so, ensure that the object exists
in the system before resubmitting the statement. System action
A valid plan or package will be created if no errors are
SQLSTATE detected. The statement is bound dynamically on each
01532 execution of the statement.
+205 column-name IS NOT A COLUMN

OF TABLE table-name
Programmer response
For better performance, rebind the plan or package
Explanation after correcting the statement. To correct the
statement, verify that the column and table names are
For ALTER TABLE ALTER COLUMN, column column- specified correctly in the SQL statement. In the case
name is not a column in table table-name. of a SELECT statement, check to be sure that all of the
required tables were named in the FROM clause.
System action
A valid plan or package will be created if no errors are SQLSTATE
detected. The statement is bound dynamically on each 01533
+217 THE STATEMENT WAS NOT
EXECUTED AS ONLY EXPLAIN
Programmer response INFORMATION REQUESTS ARE
Verify that the column and table names are specified BEING PROCESSED.
correctly (including any required qualifiers) in the SQL
statement. Explanation
The current value of the EXPLAIN MODE special
SQLSTATE register has been set to EXPLAIN. This value allows
01533 dynamic SQL statements to be prepared and explained
but prevents any dynamic statement from being
+206 column-name IS NOT A COLUMN executed.
OF AN INSERTED TABLE,
UPDATED TABLE, MERGED TABLE,
OR ANY TABLE IDENTIFIED IN A System action
FROM CLAUSE The statement was not executed because only
information requests from EXPLAIN are being
Explanation processed.
This return code is used to report one of these errors:

Programmer response Programmer response
To execute the statement, change the value of the For better performance, rebind the plan or package
EXPLAIN MODE special register to a setting other than after correcting the statement. To correct the
EXPLAIN. Issue the appropriate SET statement from statement, determine whether the required EXPLAIN
the interface or application that is encountering this table does exist. If not, create the required table.
condition.
SQLSTATE
SQLSTATE
01532
01604
Related tasks
+218 THE SQL STATEMENT Creating EXPLAIN tables (Db2 Performance)
REFERENCING A REMOTE OBJECT Related reference
CANNOT BE EXPLAINED
EXPLAIN (Db2 SQL)
EXPLAIN tables (Db2 Performance)
Explanation PLAN_TABLE (Db2 Performance)
The user has used EXPLAIN(YES) on the bind
subcommand to bind an application which has SQL +220 THE COLUMN column-name IN
statement referencing a remote object or the user has EXPLANATION TABLE table-name
a static EXPLAIN SQL statement which references a IS NOT DEFINED PROPERLY
remote object in the application program. EXPLAIN on
a remote object is not supported by Db2. Explanation
It is issued at BIND time, and only with An error occurred during the insertion of a row into an
VALIDATE(RUN). optional explanation table.
column-name
System action The name of the column that is the cause of the
The plan or package will be bound successfully, but error. Possible reasons for this error include:
no information will be filled in the user's PLAN_TABLE • A column is missing.
for the SQL statement referencing a remote object.
• Columns are defined in the wrong order.
An SQLCODE -512 will be issued at run time if the
EXPLAIN statement is found to explain a remote • The table contains an extra column.
object. • A column description is invalid because of its
name, data type, length, or null attributes.
SQLSTATE table-name
01537 The name of the explanation table.
+219 THE REQUIRED EXPLANATION

TABLE table-name DOES NOT
System action
EXIST A valid plan or package will be created if no
additional errors are detected. The statement is bound
Explanation dynamically on each execution of the statement.
The EXPLAIN statement assumes the existence of

an EXPLAIN table and it is not defined in the Db2
Programmer response
subsystem as a base table. For better performance, rebind the plan or package
after correcting the statement. To correct the
System action statement, correct the definition of the required
explanation table.
detected. The statement is bound dynamically on each
SQLSTATE
01546
Related tasks
Creating EXPLAIN tables (Db2 Performance)

Related reference System action
EXPLAIN tables (Db2 Performance)
The statement cannot be processed. No data was
EXPLAIN (Db2 SQL) fetched, and the cursor position is unchanged.
+222 HOLE DETECTED USING CURSOR
cursor-name Programmer response
Correct the application program to establish a valid
Explanation cursor position before issuing this FETCH statement.
A delete hole or an update hole has been detected
while processing a FETCH for cursor cursor-name. With SQLSTATE
a SENSITIVE STATIC cursor, a delete hole occurs when 02000
Db2 tries to refetch a row from the database for a
cursor and finds that the corresponding row of the +236 SQLDA INCLUDES integer1 SQLVAR
underlying table has been deleted. An update hole ENTRIES, BUT integer2 ARE
occurs when Db2 tries to refetch a row from the REQUIRED FOR integer3 COLUMNS
database for a cursor and finds that the corresponding
row of the underlying table no longer satisfies the Explanation
search condition.
The value of the SQLN field of the SQLDA should be
cursor-name
at least as large as the number of columns being
Name of the cursor used for the FETCH statement.
described. integer3 is the number of columns being
described.
System action
In the case that USING BOTH has been specified,
The statement cannot be processed, and no data is twice as many SQLVAR entries are needed as the
fetched. The cursor is repositioned on the hole. number of columns being described.
The number of SQLVAR entries that are needed to
Programmer response return all of the information about the columns is
Correct the application program to handle this integer2.
situation, or change isolation levels so the base row Attention: In the case of DESCRIBE INPUT, each
cannot be deleted during the cursor operation. reference to column would actually be parameter.
SQLSTATE System action

02502 The SQLDAID 7th byte has been set to "on" with a
value of 2 indicating that 2 SQLVAR entries are needed
+231 CURRENT POSITION OF CURSOR
for each column. Db2 has not set any SQLVAR entries.
cursor-name IS NOT VALID
FOR THE SPECIFIED FETCH
ORIENTATION OF THE CURRENT Programmer response
ROW OR ROWSET
Increase the value of the SQLN field in the SQLDA to
the value indicated in the message (making sure the
Explanation SQLDA is large enough to support that amount) and
resubmit the statement.
The cursor was not positioned on a row or rowset, and
one of the following fetch orientations specified that
the cursor was to be positioned relative to its current SQLSTATE
position:
01005
• CURRENT or CURRENT ROWSET
+237 SQLDA INCLUDES integer1 SQLVAR
• RELATIVE 0 or ROWSET STARTING AT RELATIVE 0 ENTRIES, BUT integer2 ARE
cursor-name REQUIRED BECAUSE AT LEAST
Name of the cursor used for the FETCH statement. ONE OF THE COLUMNS BEING
DESCRIBED IS A DISTINCT TYPE

Explanation Explanation
Given that at least one of the columns being described Given that at least one the columns being described
is a distinct type, space should be provided for the is a LOB, space must be provided for the extended
extended SQLVAR entries in addition to the base SQLVAR entries in addition to the base SQLVAR entries.
SQLVAR entries. The value of SQLN, integer1, indicates The value of SQLN, integer1, indicates that there are
that there are not enough SQLVAR entries for the base not enough SQLVAR entries for the base and extended
and extended SQLVAR entries. SQLVAR entries. One or more of the columns being
described may be a distinct type.
The total number of SQLVAR entries that are required
depends on whether USING BOTH was specified (n is The total number of SQLVAR entries that are required
the number of columns being described): depends on whether USING BOTH was specified or not
(n is the number of columns being described which
• With USING BOTH, space should be allocated for 3n
is integer3), and whether the columns include any
SQLVAR entries.
distinct types:
• Otherwise, space should be allocated for 2n SQLVAR
entries. • With USING BOTH, and one or more distinct types,
space should be allocated for 3n SQLVAR entries.
return all of the information about the columns is
entries.
integer2.
Attention: In the case of DESCRIBE INPUT, each
reference to column would actually be parameter.
integer2.
System action Important: In the case of DESCRIBE INPUT, each

reference to column would actually be parameter.
Db2 has set the SQLDAID 7th byte flag "on" because
sufficient space was not provided for the extended
System action
SQLVAR entries. The value of the 7th byte flag
indicates how many SQLVAR entries are needed for Db2 has set the SQLDAID 7th byte flag "on" because
each column. Additionally, because there were enough sufficient space was not provided for the extended
SQLVAR entries for the base SQLVARs, Db2 has set the SQLVAR entries. The value of the 7th byte flag
fields of the base SQLVAR entries. However, Db2 has indicates how many SQLVAR entries are needed for
not set any extended SQLVAR entries. each column. Db2 has not set any SQLVAR entries.

If there is no need for the additional information about Increase the value of the SQLN field in the SQLDA to
the distinct type(s), then no action is required unless integer2 (after making sure that the SQLDA is large
USING BOTH was specified (in which case additional enough to support that amount) and resubmit the
SQLVAR entries must be provided for the labels). statement.
If the distinct type information is needed, the value
of the SQLN field in the SQLDA should be increased SQLSTATE
to integer2 (after making sure that the SQLDA is large
01005
enough to support that amount) and the statement
should be resubmitted. +239 SQLDA INCLUDES integer1 SQLVAR
ENTRIES, BUT integer2 ARE
SQLSTATE REQUIRED FOR integer3 COLUMNS
BECAUSE AT LEAST ONE OF THE
01594 COLUMNS BEING DESCRIBED IS A
DISTINCT TYPE
+238 SQLDA INCLUDES integer1 SQLVAR
ENTRIES, BUT integer2 SQLVAR
ENTRIES ARE NEEDED FOR Explanation
integer3 COLUMNS BECAUSE AT
Given that at least one of the columns being described
LEAST ONE OF THE COLUMNS
is a distinct type, space should be provided for the
BEING DESCRIBED IS A LOB
extended SQLVAR entries in addition to the base
SQLVAR entries. The value of SQLN, integer1, indicates

that there are not enough SQLVAR entries for the base DIAGNOSTICS to obtain information about the warning
and extended SQLVAR entries. conditions that occurred.
The total number of SQLVAR entries that are required
depends on whether USING BOTH was specified or not System action
(n is the number of columns being described which is
The statement was processed.
integer3),
• With USING BOTH, space should be allocated for 3n Programmer response
SQLVAR entries.
Analyze the warning conditions to determine whether
the statement should be rolled back or not.
entries.
SQLSTATE
integer2. 01659
Note: in the case of DESCRIBE INPUT, each reference +304 A VALUE WITH DATA TYPE data-
to column would actually be parameter. type1 CANNOT BE ASSIGNED
TO A HOST VARIABLE BECAUSE
System action THE VALUE IS NOT WITHIN THE
RANGE OF THE HOST VARIABLE
Db2 has set the SQLDAID 7th byte flag "on" because IN POSITION position-number
sufficient space was not provided for the extended WITH DATA TYPE data-type2
SQLVAR entries. The value of the 7th byte flag
indicates how many SQLVAR entries are needed
for each column. Db2 has not set any SQLVAR
Explanation
entries. :elq. A FETCH or SELECT into a host variable list or
structure, position number position-number failed
Programmer response because the host variable having data type data-type2
was not large enough to hold the retrieved value
If the distinct type information is needed, the value of having data type data-type1.
the SQLN field in the SQLDA should be increased to
integer2 (after making sure the SQLDA is large enough
to support that amount) and the statement should be
System action
resubmitted. The FETCH or SELECT could not return the data for
If there is no need for the additional information the indicated SELECT item, the indicator variable is set
about the distinct type(s) in the result set, then it to negative two (-2) to indicate a null value returned.
is possible to resubmit the statement only providing Processing continues.
enough SQLVAR entries to accommodate the number
of columns being described (i.e. provide the necessary Programmer response
number of base SQL entries).
Verify that table definitions are current, and that
the host variable has the proper data type. See the
SQLSTATE explanation for SQLCODE -405 for ranges of SQL data
01005 types.
+252 A NON-ATOMIC statement SQLSTATE

STATEMENT SUCCESSFULLY
PROCESSED ALL REQUESTED 01515
ROWS, WITH ONE OR MORE
+331 THE NULL VALUE HAS BEEN
WARNING CONDITIONS
ASSIGNED TO A HOST VARIABLE
OR PARAMETER BECAUSE THE
Explanation STRING CANNOT BE CONVERTED
A non-atomic statement statement successfully FROM source-ccsid TO target-ccsid.
processed multiple rows of data. However, one REASON reason-code, POSITION
or more warning conditions occurred. Use GET position-number

Explanation System action
A string had to be converted from source-ccsid Db2 processes the statement successfully.
to target-ccsid and an error occurred during the
conversion. The position-number, if provided (non- Programmer response
zero), is the ordinality of the host variable or parameter
in the SQLDA. See the description of SQLCODE -331 This warning can occur in two situations:
for further information including the meaning of the
• If trace for IFCID 136 or 168 is not active, Db2
reason-code.
processes the SQL statement, but used substitution
characters instead of one or more characters as a
System action result of character conversion from from ccsid to
to-ccsid. If substitution is acceptable, no action is
The host variable is unchanged and its indicator
necessary. If substitution is not acceptable, issue a
variable is set to -2 to indicate that a null value is
ROLLBACK. Ensure that data being provided to Db2
returned. Execution of the statement continues as if
is convertible from from ccsid to to-ccsid without
the conversion error had not occurred.
data loss.
• If trace for IFCID 136 or 168 is active, and the
SQLSTATE to-ccsid token is an EBCDIC CCSID, and system
01520 parameter UIFCIDS is OFF, this warning is caused
by the conversion to EBCDIC CCSID for IFCID trace
+335 DB2 CONVERTED A HOST record. Use the GET DIAGNOSTICS statement to
VARIABLE, PARAMETER, OR determine if the there are other warnings associated
COLUMN NUMBER var-num var- with the original SQL string. If GET DIAGNOSTICS
name-or-num TO COLUMN NAME, returns no other warnings, no action is required.
HOST VARIABLE, OR EXPRESSION
NUMBER col-name-or-num FROM
from ccsid TO to-ccsid, AND SQLSTATE
RESULTING IN SUBSTITUTION 01517
CHARACTERS.
Related reference
GET DIAGNOSTICS (Db2 SQL)
Explanation
A conversion error occurred during the conversion of a +347 THE RECURSIVE COMMON TABLE
string to a different coded character set. One or more EXPRESSION name MAY CONTAIN
substitution characters have been placed in the string AN INFINITE LOOP
during the conversion process.
var-num var-name-or-num Explanation
The value of the host variable, the parameter, The recursive common table expression called name
or the column number prior to the conversion may not complete. This warning is based on not finding
process. This value might be the string *N if specific syntax as part of the iterative portion of the
the column number is not available when this recursive common table expression. The expected
SQLCODE is issued. syntax includes:
col-name-or-num
• incrementing an INTEGER column in the iterative
The value of the host variable, the parameter or
select list by 1.
the column number after the conversion process.
This value might be the string *N if the column • a predicate in the where clause of the iterative
number is not available when this SQLCODE is portion of the form "counter_col < constant" or
issued. "counter_col < :hostvar".
from ccsid The absence of this syntax in the recursive common
The input CCSID for the host variable, parameter, table expression may result in an infinite loop. The
or column number. data or some other characteristic of the recursive
to-ccsid common table expression may allow the successful
The resulting CCSID from the conversion of the completion of the statement anyway.
host variable, parameter, or column number.

System action Explanation
The statement cannot be executed. During the processing of a command such as a
BIND PACKAGE or DROP or FREE PACKAGE, a
Programmer response condition occurred, as specified by msg-token, and the
command needs to be examined.
To prevent an infinite loop, include the expected
syntax as described.
System action
SQLSTATE The request was successful.
01605
User response
+354 A ROWSET FETCH STATEMENT Evaluate the information contained in msg-token to
MAY HAVE RETURNED ONE determine if the results were as expected.
OR MORE ROWS OF DATA.
HOWEVER, ONE OR MORE
WARNING CONDITIONS WERE SQLSTATE
ALSO ENCOUNTERED. USE THE 0168B
GET DIAGNOSTICS STATEMENT
FOR MORE INFORMATION +364 DECFLOAT EXCEPTION exception-
REGARDING THE CONDITIONS type HAS OCCURRED DURING
THAT WERE ENCOUNTERED operation-type OPERATION,
POSITION position-number
Explanation:
A rowset FETCH statement encountered one or
more warning conditions. Use the GET DIAGNOSTICS Explanation
statement to obtain information about the conditions The exception error exception-type occurred
that occurred, and to determine if data was returned. while performing an ADDITION, SUBTRACTION,
It is possible that one or more rows of data were MULTIPLICATION, DIVISION, NEGATION, or BUILT-IN
returned. If the row information that was returned for FUNCTION operation on a field whose data type is
the row that encountered the condition is incomplete, DECFLOAT. The error occurred while processing an
do not use the data for the row that encountered the arithmetic expression. If the error occurred in the
condition, such as displaying or printing the data. SELECT list of an outer SELECT statement, position in
System action: the select list is denoted by position-number. If not,
Db2 processed the statement successfully, but with position number is 0. The possible exception types
a warning that the fetching of some rows might have are UNDERFLOW, OVERFLOW, INEXACT, INVALID
encountered warnings. OPERATION, DIVISION BY ZERO, or SUBNORMAL. The
data type displayed in the message may indicate the
data type of the temporary internal copy of the data,
Programmer response
which may differ from the actual column or literal data
Analyze the conditions to determine whether follow- type due to conversions by Db2.
up actions are needed. The GET DIAGNOSTICS
Any of the exceptions or overflows can occur during
statement can be used to determine which additional
the processing of a built-in function. If operation-type
actions might be necessary.
is FUNCTION, then the error occurred while processing
Attention: It is also possible that an end of either an input, intermediate, or final value. The cause
data condition was detected. SQLERRD3 and could be that the value of a parameter is out of range.
GET DIAGNOSTICS can be used to determine if
Note: Parts of exception-type, operation-type, and
all of the requested rows were fetched or if a
position-number might or might not be returned in
partial rowset was returned.
SQLCA, depending upon when the error was detected.

01668
The resulting data proceeds according to IEEE 754r
+361 COMMAND WAS SUCCESSFUL BUT rules. Execution of the statement continues. If the
RESULTED IN THE FOLLOWING: statement is cursor controlled, then the cursor will
msg-token remain open.

Programmer response DURING ACCESS PATH
SELECTION
Examine the expression for which the warning
occurred to see if the likely cause of the problem can
be determined. The problem may be data-dependent, Explanation
in which case it will be necessary to examine the data All user specified optimization hints that were found
that was being processed at the time that the error for the statement being optimized are used.
occurred. See the explanation of SQLCODE -405 for
allowed ranges of numeric data types.
System action
SQLSTATE Processing continues normally.
0168C if INEXACT
Programmer response
0168D if INVALID OPERATION
Ensure that the access path is correct and produces
0168E if UNDERFLOW,OVERFLOW the correct results.
0168F if DIVISION BY ZERO Suppressing this SQLCODE:
0168G if SUBNORMAL You can set the value of the
SUPPRESS_HINT_SQLCODE_DYN to suppress
+385 ASSIGNMENT TO AN SQLSTATE SQLCODEs +394 and +395 for dynamic SQL
OR SQLCODE VARIABLE IN AN statements.
SQL ROUTINE routine-name MAY
BE OVERWRITTEN AND DOES NOT
ACTIVATE ANY HANDLER
SQLSTATE
01629
Explanation Related concepts
SQL routine routine-name was created, but it contains Validation of specified access paths (Db2
an assignment statement that specifies the SQLCODE Performance)
or SQLSTATE variable as the target. Related tasks
Assignment to an SQLSTATE or SQLCODE variable in Influencing access path selection (Db2
an SQL routine only changes the value in the variable, Performance)
and does not activate any handler. The SQLSTATE and Related reference
SQLCODE variables are assigned values by processing PLAN_TABLE (Db2 Performance)
of SQL statements in the SQL routine. Therefore, any DSN_USERQUERY_TABLE (Db2 Performance)
value assigned might be over-written as a result of SQL Subsystem parameters that are not on
statement processing. installation panels (Db2 Installation and
Migration)
System action Related information
The routine definition is processed successfully. +395
A USER SPECIFIED OPTIMIZATION HINT IS
INVALID (REASON CODE = reason-code)
User response
No recovery is necessary. If the intent was to signal +395 A USER SPECIFIED
an error or warning, specify the SIGNAL or RESIGNAL OPTIMIZATION HINT IS INVALID
statement instead of the assignment. (REASON CODE = reason-code)
To prevent the warning, remove any assignments to

the SQLSTATE or SQLCODE special variables.
Explanation
Db2 detected that one or more optimization hints
SQLSTATE provided for this statement are invalid. You can use
the following reason-code values to identify why a hint
01643 is invalid:
+394 ALL USER SPECIFIED reason-code
OPTIMIZATION HINTS USED The reason why a hint was invalid. Only one
reason-code is returned even if the hint contains

multiple problems. The following descriptions refer 13
to the of the values in PLAN_TABLE columns for One of the following columns contains
the set of rows that contain the same value in the an invalid value: ACCESSCREATOR or
OPTHINT column. ACCESSNAME.
2 15
The value of the TABNO column is not valid. The hint specifies an index that cannot be
Negative values and values greater than the used.
total number of table references are not valid. 16
The value of the TABNO column is validated The hint specified multi-index access that
only when the combination of the following cannot be used.
columns does not identify a particular 17
table reference within a query block: The hint specifies an invalid combination of
CREATOR, TNAME, CORRELATION_NAME, and ACCESSTYPE values.
QBLOCKNO. 18
3 The join method for the inner table of a join
A value is not specified for one of the following was not specified in the METHOD column.
columns: CREATOR or TNAME 19
4 The nested-loop join that is specified by the
The value of the TABNO column was value of the METHOD column cannot be used.
not specified, and the combination of 20
the following columns does not uniquely The merge join that is specified by the value of
identify a table reference: CREATOR, TNAME, the METHOD column cannot be used.
CORRELATION_NAME, and QBLOCKNO.
21
5 The hybrid join that is specified by the value of
The value specified for the TABNO column the METHOD column cannot be used.
contains a value in the valid range. However,
22
the value does not correctly correspond to
The mode of parallelism that is specified by
the values of the following columns: CREATOR,
the value of the PARALLELISM_MODE column
TNAME, and CORRELATION_NAME.
requested cannot be used.
6
23
The table identified by the values specified
The PARALLELISM_MODE column contains an
by the following columns cannot be found
invalid value.
within the query block that is identified by
the QBLOCKNO column: CREATOR, TNAME, 24
CORRELATION_NAME. One of the following columns contains
an invalid value: ACCESS_DEGREE or
7
ACCESS_PGROUP_ID
The PAGE_RANGE column contains an invalid
value. 25
One of the following columns contains
8
an invalid value: JOIN_DEGREE or
The PREFETCH column contains an invalid
JOIN_PGROUP_ID
value.
26
9
A row for a table reference that is required
The METHOD column contains an invalid value.
for the hint is missing. For query blocks
10 that reference multiple tables, the hint must
The SORTN_JOIN column contains an invalid contain a row for each table. Required tables
value. might not be mentioned in the statement
11 text because Db2 uses materialization or
The SORTC_JOIN column contains an invalid transformations in the access path.
value. 27
12 The hint contains a redundant table reference
The ACCESSTYPE column contains an invalid because a table that is identified by a
value. combination of the following columns appears
in more than one row for the same query block:

CREATOR, TNAME, CORRELATION_NAME, problem by recapturing EXPLAIN information
TABNO (when required). and reissuing the BIND QUERY command.
28 43
The PRIMARY_ACCESSTYPE column contains A selectivity override with multiple instances
an invalid value. cannot be applied for the specified SQL
29 statement. You might need to create a
The SORTN_GROUP_ID column contains an selectivity override that uses only a single
invalid value. instance.
30 48
The SORTN_GROUP_ID column contains an Access path information for a correlated
invalid value. subquery is missing
31 50
No value is specified in the The APREUSE option was specified during
PARALLELISM_MODE column. a bind or rebind operation and the hint
was accepted. However, during access path
32 comparison, Db2 detected that the resulting
One of the following columns contains an access path does not match the original access
invalid value: CREATOR or TNAME path.
33 99
The join sequence is incorrect. An unexpected error occurred.
34
Only one reason-code is returned even if the hint
The column WHEN_OPTIMIZE contains an
contains multiple problems.
invalid or inconsistent value.
35
The value of the ACCESSTYPE column cannot
System action
contain 'V' for the specified table. The invalid hint is ignored and Db2 determines the
36 access path without that hint. If other hints are
The number of dimension tables that are joined supplied for the statement, Db2 might use those hints,
before the star join fact table exceeds the if they are valid.
maximum number of dimensions that can be
joined by a fact table index. Programmer response
37 Examine the EXPLAIN output to determine which hints
When the value of the JOIN_TYPE column for were used by Db2, and which hints were not used. If
the fact table is 'SJ', a nested-loop join must be needed, correct the problem with the hints that were
used. not used, or disable their use as hints to the optimizer.
38
Suppressing this SQLCODE:
The join sequence for dimension tables in a
You can set the value of the
star join is incorrect because it does not match
SUPPRESS_HINT_SQLCODE_DYN to suppress
the sequence that is specified by the fact table
SQLCODEs +394 and +395 for dynamic SQL
index.
statements.
39
The value of ACCESSTYPE column is 'O' but the
specified access path cannot be used. SQLSTATE
40 01628
Multiple index access cannot be used with the Related concepts
specified indexes .
Validation of specified access paths (Db2
41 Performance)
Duplicate hint input records found for the same Related tasks
table.
Influencing access path selection (Db2
42 Performance)
Predicate validation failed for a selectivity Related reference
override, but no matching predicate was found
PLAN_TABLE (Db2 Performance)
in the statement. You might be able to fix the
DSN_USERQUERY_TABLE (Db2 Performance)

Subsystem parameters that are not on For indexes, use type 2 indexes rather than type 1
installation panels (Db2 Installation and indexes to avoid any incompatibilities.
Migration)
Related information System action
+394
ALL USER SPECIFIED OPTIMIZATION HINTS Processing continues and the clause is ignored.
USED DURING ACCESS PATH SELECTION
User response
+402 LOCATION location IS UNKNOWN
No change is required for the current release.
However, you should change your SQL statement and
Explanation remove this clause to prepare for releases when this
A remote object is referenced and either the clause is no longer accepted.
table SYSIBM.LOCATIONS is not defined or the To prevent the warning, remove the deprecated clause
referenced 'location' matches no entry in the from the statement.
SYSIBM.LOCATIONS.LOCATION column.
SQLSTATE
System action
01608
For the CREATE ALIAS statement, the alias is created.
For binding a plan or package with the VALIDATE(RUN) +438 APPLICATION RAISED WARNING
option, the plan or package is created. WITH DIAGNOSTIC TEXT: text
SQLSTATE Explanation
01521 This warning occurred as a result of the SIGNAL or
RESIGNAL statement.
+403 THE LOCAL OBJECT REFERENCED
BY THE CREATE ALIAS text
STATEMENT DOES NOT EXIST Diagnostic text provided by the SIGNAL or
RESIGNAL statement.
Explanation
System action
The local object referenced by the CREATE ALIAS
statement does not exist when creating the alias. The statement was processed, but a warning was
encountered.
System action
Programmer response
The alias is created.
Use the application-provided diagnostic text, if
provided, to determine the cause of the warning.
SQLSTATE
01522 SQLSTATE
+434 clause IS A DEPRECATED CLAUSE Defined by the application
+440 NO routine-type BY THE
Explanation NAME routine-name HAVING
The use of clause is accepted for now, but continued COMPATIBLE ARGUMENTS WAS
use of it is not recommended. However, for native FOUND
SQL procedures, clause is not supported. See the SQL
Reference for a list of options that are supported Explanation
for native SQL procedures. SQLCODE -4705 might be
issued instead if the situation occurs with a BIND This warning occurs in a reference to routine (stored
COPY command that is used to deploy a version procedure or function) routine-name, when Db2
of a native SQL procedure that uses a deprecated cannot find a function or stored procedure it can use to
option,and a package already exists by that name at implement the reference. Several reasons are present
the server. for this warning:

• routine-name was incorrectly specified or does not SQLSTATE
exist in the database.
01004
• A qualified reference was made, and the qualifier
was incorrectly spelled. +462 EXTERNAL FUNCTION OR
• A user's SQL path does not contain the schema PROCEDURE name (SPECIFIC
to which the function belongs, and an unqualified NAME specific-name) HAS
reference was used. RETURNED A WARNING
SQLSTATE, WITH DIAGNOSTIC
• The wrong number of arguments were included. TEXT text
• For functions, the data types of one or more of the
arguments is incorrect. Explanation
An SQLSTATE of the form 01Hxx was returned to Db2
System action
by user-defined function or procedure name, along
A valid plan or package will be created if no errors are with message text text.
execution of the statement. System action
Processing continues.
Programmer response
Fix the problem and retry. Change the SQL statement, Programmer response
add new routines, or change the user's SQL path.
See your database administrator, or the author of the
function or procedure to find out the meaning of the
SQLSTATE
warning. The significance of the bad SQLSTATE to the
0168L invoking application can be learned from the author of
the function or procedure.
+445 VALUE value HAS BEEN
TRUNCATED
SQLSTATE
Explanation 01Hxx
The value value was truncated by a cast function, +464 PROCEDURE proc RETURNED num
which was called to transform the value in some way. QUERY RESULT SETS, WHICH
This is a warning situation. The cast function is a result EXCEEDS THE DEFINED LIMIT
of integer
• a CAST specification
• a built-in function such as CHAR, VARCHAR, etc.
Explanation
• a CAST FROM specification on the CREATE The stored procedure named by proc completed
FUNCTION statement that created the function normally. However, the stored procedure exceeded the
defined limit on the number of query result sets the
• a user-defined function that is sourced on another procedure can return.
function and the result needed to be transformed.
• num identifies the number of query result sets
If 'value' has the 'for bit data' subtype, then the 'value' returned by the stored procedure.
is printed as a hexadecimal string in quotes followed
by an X. • integer identifies the defined limit on the number of
query result sets for the stored procedure.
System action Only the first integer query result sets are returned to
the SQL program that issued the SQL CALL statement.
The value has been truncated.
The possible causes are as follows:
Programmer response • The stored procedure is unable to return num result
sets due to the limit defined for the procedure.
Ensure that the output is as expected and that
the truncation has not caused any unexpected • The stored procedure is unable to return num result
consequences. sets due to the DRDA limitations imposed by the

client. The DRDA client establishes this limit with the SECONDS (estimate-amount2
MAXRSLCNT DDM code point. SERVICE UNITS) IN COST
CATEGORY cost-category EXCEEDS
System action A RESOURCE LIMIT WARNING
THRESHOLD OF limit- amount
The SQL statement is successful. The SQLWARN9 field SERVICE UNITS
is set to 'Z'.
Explanation
SQLSTATE
The prepare of a dynamic INSERT, UPDATE, MERGE,
0100E DELETE, or SELECT SQL statement resulted in a
cost estimate that exceeded the warning threshold
+466 PROCEDURE proc RETURNED num
value specified in the resource limit specification
QUERY RESULTS SETS
table (RLST). This warning is also issued if the Db2
cost category value was "B", and the default action
Explanation specified in the RLF_CATEGORY_B column in the RLST
is to issue a warning.
The stored procedure named by proc completed
normally. The procedure returned the number of SQL estimate_amount1
query result sets specified in num. The cost estimate (in processor seconds) if the
prepared INSERT, UPDATE, MERGE, DELETE, or
SELECT statement were to be executed.
System action
estimate_amount2
The SQL statement is successful. The SQLWARN9 field The cost estimate (in service units) if the prepared
is set to 'Z'. INSERT, UPDATE, MERGE, DELETE, or SELECT
statement were to be executed.
SQLSTATE cost-category
0100C The Db2 cost-category for this SQL statement. The
possible values are A or B.
+494 NUMBER OF RESULT SETS IS
limit-amount
GREATER THAN NUMBER OF
The warning threshold (in service units) specified
LOCATORS
in the RLFASUWARN column of the RLST.
If you entered any negative number for the
Explanation RLFASUWARN column, the value for limit-amount
defaults to zero.
The number of result set locators specified on
the ASSOCIATE LOCATORS statement is less than
the number of result sets returned by the stored System action
procedure. The first "n" result set locator values are
The prepare of the dynamic INSERT, UPDATE, MERGE,
returned, where "n" is the number of result set locator
DELETE, or SELECT statement was successful. An
variables specified on the SQL statement.
SQLCODE -905 might be issued if the execution of
the prepared statement exceeds the ASUTIME value
System action specified in the RLST.
The SQL statement is successful. The SQLWARN3 field
is set to 'Z'. User response
If the warning is caused by an SQL statement that
Programmer response is consuming too much processor resource, attempt
to rewrite the statement to perform more efficiently.
Increase the number of result set locator variables
Another option is to ask the administrator to increase
specified on the SQL statement.
the warning threshold value in the RLST.
SQLSTATE Programmer response

01614
Ensure that there is application logic to handle the
+495 ESTIMATED PROCESSOR COST warning to either allow the statement to execute or
OF estimate-amount1 PROCESSOR to stop the statement from being executed. If this

SQLCODE was returned because the cost category SQLSTATE
value is "B", it might be that the statement is using
parameter markers or that some statistics are not 01543
available for the referenced tables and columns. Make +551 auth-id DOES NOT HAVE
sure the administrator has run the utility RUNSTATS THE PRIVILEGE TO PERFORM
on the referenced tables. It might also be that UDFs OPERATION operation ON OBJECT
will be invoked when the statement is executed, or for object-name
INSERT, UPDATE, MERGE, or DELETE statements that
triggers are defined on the changed table. Check the
DSN_STATEMNT_TABLE or the IFCID 22 record for this Explanation
statement to find the reasons this SQL statement has Authorization ID auth-id has attempted to perform
been put in cost category "B". the specified operation on object object-name without
having been granted the proper authority to do so. This
SQLSTATE error might also occur if the specified object does not
exist, or if the object is a read-only view (for UPDATE,
01616 INSERT, or MERGE). Additionally, the error may occur
+535 THE RESULT OF THE POSITIONED if auth-id is trying to create a table or view with a
UPDATE OR DELETE MAY DEPEND schema qualifier that is a value other than auth-id. You
ON THE ORDER OF THE ROWS may create a table or view with a schema qualifier
other than auth-id other than your own authorization
ID if your authorization ID is SYSADM, DBADM, or
Explanation DBCTRL.
A positioned update of a primary key or a delete from a If you are using a trusted context, the token auth-
table with a self-referencing constraint was requested. id might return a role instead of an authorization
ID. A role is returned if a role was in effect and
System action the authorization checking is performed against the
role, rather than the authorization ID of the session,
Db2 executes the UPDATE or DELETE statement and when the condition was encountered. Otherwise an
the contents of the table are changed. authorization ID is returned. A role is returned in the
following format as a single token:
SQLSTATE • ROLE: role-name
01591 If this error occurs while Db2 is creating or altering
+541 THE REFERENTIAL OR UNIQUE a table involving referential constraints, this code
CONSTRAINT name HAS BEEN reports that the user does not have the necessary
IGNORED BECAUSE IT IS A ALTER privilege to perform a FOREIGN KEY, DROP
DUPLICATE FOREIGN KEY, DROP PRIMARY KEY, or DROP UNIQUE
operation. The object-name identifies the object table
of the CREATE or ALTER TABLE statement, not the
Explanation table for which the user lacks the ALTER privilege.
A FOREIGN KEY clause uses the same key and parent
table as another FOREIGN KEY clause, or a UNIQUE System action
clause uses the same column list as another UNIQUE
or PRIMARY KEY clause. In either case, the duplicate A valid plan or package will be created if no errors are
clause is ignored. detected. The statement is bound dynamically on each
name is either the foreign key name or the unique
constraint name.
Programmer response
System action For better performance, rebind the plan or package
Db2 continues processing. statement, ensure that auth-id has been granted the
authority to perform the operation, that object-name
Programmer response exists, and that auth-id is not trying to create a table
with a schema qualifier other than the authorization
If the duplication is an error, correct the statement and ID.
execute it again.

SQLSTATE • DATAACCESS authority was being granted.
01548 • CREATE_SECURE_OBJECT privilege was being

granted.
+552 auth-id DOES NOT HAVE
THE PRIVILEGE TO PERFORM
System action
OPERATION operation
The offending privileges in the authorization
Explanation specification are granted without the GRANT option.
If the grantee is PUBLIC, all the privileges in the
Authorization ID auth-id has attempted to perform the authorization specification are granted without the
specified operation without having been granted the GRANT option.
authority to do so.
If you are using a trusted context, the token auth- SQLSTATE
id might return a role instead of an authorization
01516
ID. A role is returned if a role was in effect and
the authorization checking is performed against the +562 A GRANT OF A PRIVILEGE WAS
role, rather than the authorization ID of the session, IGNORED BECAUSE THE GRANTEE
when the condition was encountered. Otherwise an ALREADY HAS THE PRIVILEGE
authorization ID is returned. A role is returned in the FROM THE GRANTOR
following format as a single token:
ROLE: role-name Explanation

At least one of the privileges in the GRANT statement
was ignored because the privilege was already granted
System action to the grantee by the grantor.
detected. The statement is bound dynamically on each System action
The privileges previously granted are ignored; all
others are granted.
Programmer response
For better performance, rebind the plan or package SQLSTATE
statement, ensure that the authorization ID has 01560
been granted the authority necessary to perform the +585 THE COLLECTION collection-id
operation. APPEARS MORE THAN ONCE
WHEN SETTING THE special-
SQLSTATE register SPECIAL REGISTER
01542
Explanation
+558 THE WITH GRANT OPTION IS
IGNORED. The SET statement for special register special-register
includes collection-id more than once.
Explanation
System action
The WITH GRANT option was used where it is not
valid. It cannot be used in the following cases: Duplicates are removed from the list, and the first
occurrence of collection-id is used. The statement is
• PUBLIC was within the list of grantee authorization executed.
IDs.
• The BINDAGENT privilege was being granted. Programmer response
• The ANY package privilege on collection-id.* was
being granted. Verify the list that contains the duplicate. If the error is
only in entering a collection-id incorrectly that happens
• System DBADM authority was being granted. to duplicate another entry, enter the collection-id
• ACCESSCTRL authority was being granted.

correctly and reissue the statement. If the entry is COLUMN was issued on table object-name. The
intended to be a duplicate, no action is required. column that was altered is part of the index, and
the alter operation caused the index to be placed
SQLSTATE in REBUILD PENDING status. The table space
that contains the table is placed in ADVISORY
01625 REORG PENDING status.
+599 COMPARISON FUNCTIONS ARE The index is not generally available until the index
NOT CREATED FOR A DISTINCT is removed from the REBUILD pending state.
TYPE BASED ON A LONG STRING
REORG pending for a table space partition
DATA TYPE
The table space is in REORG pending because
ALTER INDEX was used to change the limit key
Explanation values. The table space partition is not generally
available until the REORG pending status is
Comparison functions are not created for a distinct
removed.
type based on a long string data type (BLOB, CLOB,
DBCLOB) since the corresponding function are not REORG pending for a table space
available for these built-in data types. The table space is in REORG pending because
ALTER TABLE was used to add an identity column
to a populated table. The table space is not
System action generally available until the REORG pending status
The statement is processed successfully. is removed.
ADVISORY REORG pending for a table space
Programmer response The table space is in ADVISORY REORG pending
because an ALTER statement with pending
No action is required. definition changes has been issued. The table
space is available, but the definition changes have
SQLSTATE not yet been applied.
01596 ADVISORY REORG pending for an index

The index is in ADVISORY REORG pending because
+610 A CREATE/ALTER ON OBJECT an ALTER statement with pending definition
object-name HAS PLACED OBJECT changes has been issued. The index is available,
IN utility-name PENDING but the definition changes have not yet been
applied.
Explanation REORG pending for a table
The table is in REORG pending because an
As the result of a CREATE or ALTER action on object-
ALTER statement with the INLINE LENGTH option
name, the object or a related object has been placed in
reduced the maximum length for a LOB column.
a pending status.
object-name System action
The name of the object.
The object was placed in the indicated pending status.
utility-name
The name of the utility.
Programmer response
The reason for this error depends on the utility-name
value and the object type. The response depends on the utility-name value and
the object type:
REBUILD pending for an index
REBUILD pending for an index
• The index is in REBUILD PENDING status
Use the REBUILD INDEX utility to rebuild the index
because CREATE INDEX with DEFER was
and remove the REBUILD pending status.
specified on a populated table.
REORG pending for a table space partition
• The index is in REBUILD PENDING status
Perform the following steps:
because ALTER INDEX was used to add a
nullable column to an EXCLUDE NULL KEYS 1. Issue a DISPLAY DATABASE command for the
index. table space to identify which partitions are in
• An index on table object-name is in REBUILD REORG pending.
PENDING status because ALTER TABLE ALTER

2. Run the REORG utility on the partitions that are Explanation
in REORG pending.
This table is defined with the maximum number of
REORG pending for a table space columns. It cannot be altered to be a dependent table
Run the REORG utility on the table space. later.
ADVISORY REORG pending for a table space
Run the REORG TABLESPACE utility with System action
SHRLEVEL CHANGE or SHRLEVEL REFERENCE on
the entire table space to materialize the pending The table is created. Check to see if the table will
definition changes. become a dependent table at a later time. If yes, drop
and re-create the table with fewer than 750 columns.
ADVISORY REORG pending for an index
If pending definition changes do not exist for the
table space, run the REORG INDEX utility with SQLSTATE
SHRLEVEL CHANGE or SHRLEVEL REFERENCE to
01538
materialize the pending definition changes for the
index. +653 TABLE table-name IN
PARTITIONED TABLESPACE
If pending definition changes exist for the table
tspace-name IS NOT AVAILABLE
space, run the REORG TABLESPACE utility with
BECAUSE ITS PARTITIONED
SHRLEVEL CHANGE or SHRLEVEL REFERENCE to
INDEX HAS NOT BEEN CREATED
materialize the pending definition changes for the
table space and associated indexes.
Explanation
SQLSTATE An attempt has been made to insert or manipulate
data in or create a view on a partitioned table (that is,
01566
a table residing in a partitioned table space) before the
+645 WHERE NOT NULL IS IGNORED partitioned index for that table has been created.
BECAUSE THE INDEX KEY
A table residing in a partitioned table space cannot
CANNOT CONTAIN NULL VALUES
be referenced in any SQL manipulative statement or a
OR THE INDEX IS AN XML INDEX
CREATE VIEW statement before the partitioned index
for that table has been created.
Explanation
The WHERE NOT NULL clause is ignored on the System action
CREATE INDEX statement because the index key is
defined on columns that cannot contain null values, or,
the index is an XML index.

The option is ignored; processing continues.
For better performance, rebind the plan or package
Programmer response statement, verify that the correct table was specified
in the statement. If so, ensure that the partitioned
Remove the WHERE NOT NULL clause to get rid of the
index for the table has been created successfully
warning.
before attempting to execute any SQL manipulative
statements that reference that table.
SQLSTATE
01528 SQLSTATE
+650 THE TABLE BEING CREATED OR 01551
ALTERED CANNOT BECOME A
+655 STOGROUP stogroup_name HAS
DEPENDENT TABLE
BOTH SPECIFIC AND NON-
SPECIFIC VOLUME IDS. IT WILL
NOT BE ALLOWED IN FUTURE
RELEASES

Explanation limit key length to ensure the new limit key value has
the same internal length as the other partitions.
The CREATE or ALTER STOGROUP statement has
caused the STOGROUP with stogroup_name to have
both specific and non-specific ('*') volume Ids. This System action
warning code is used to specify that the mixing of The specified index or table was altered but the limit
different types of volume Ids will not be allowed in key was truncated to be the existing internal limit key
future releases. length.
System action SQLSTATE

Db2 continues processing. 01540
+738 DEFINITION CHANGE OF object
Programmer response object_name MAY REQUIRE
Plan to use either specific or non-specific volume SIMILAR CHANGE ON READ-ONLY
ids to avoid future release migration impact. ALTER SYSTEMS
STOGROUP may be used to drop all specific volume
ids or all non-specific volume ids. Explanation
A change was made to the definition of the specified
SQLSTATE object that may also require a similar change to any
01597 read-only shared systems.
+658 THE SUBPAGES VALUE IS

IGNORED FOR THE CATALOG System action
INDEX index-name The statement is successfully executed.
Explanation Programmer response

Only SUBPAGES 1 is allowed for this catalog index. Check the read-only shared systems that have the
specified object defined, and determine if a change
System action must be made to the object on those systems.
The index was altered successfully using SUBPAGES 1.

If you are also altering the TYPE option to a new value, SQLSTATE
the index is placed in recovery pending status. 01530
+799 THE STATEMENT set-stmt
SQLSTATE REFERENCES A SPECIAL
01600 REGISTER OR BUILT_IN GLOBAL
VARIABLE THAT DOES NOT EXIST
+664 THE INTERNAL LENGTH OF THE AT THE SERVER SITE
LIMIT-KEY FIELDS SPECIFIED
IN THE PARTITION CLAUSE OF
THE statement-name STATEMENT Explanation
EXCEEDS THE EXISTING A Db2 server received an statement that it does not
INTERNAL LIMIT KEY LENGTH understand.
STORED IN CATALOG TABLE table-
name set-stmt
The statement that contains the unrecognized
special register or built-in global variable. This
Explanation token might be blank for servers other than Db2
The sum of the internal lengths of the limit keys for z/OS, or for down-level Db2 for z/OS servers.
specified in the PARTITION clause of the ALTER
INDEX or ALTER TABLE statement exceeds the existing System action
internal limit key length stored in catalog table
SYSIBM.SYSINDEXPART or SYSIBM.SYSTABLEPART. The request is ignored.
The limit key was truncated to the existing internal

Programmer response FIXED POINT OVERFLOW
A fixed point overflow can occur during any
This SQLCODE can be returned to an application for arithmetic operation on either INTEGER or
any SQL statement. This SQLCODE might be masked SMALLINT fields.
by other negative SQLCODEs that the SQL statement
receives. Processing continues at the server. INVALID OPERATION
OUT OF RANGE
An error might occur during while processing an
SQLSTATE
input, intermediate, or final value if the value of a
01527 parameter is out of range.
Related reference OVERFLOW
Special registers (Db2 SQL) An overflow can occur during the processing
of a built-in function. If the operation-type
Built-in global variables (Db2 SQL)
is FUNCTION, then the error occurred while
+802 EXCEPTION ERROR exception- processing an input, intermediate, or final value.
type HAS OCCURRED DURING SUBNORMAL
operation-type OPERATION ON UNDERFLOW
data-type DATA, POSITION An underflow can occur during the processing
position-number of a built-in function. If the operation-type
is FUNCTION, then the error occurred while
Explanation processing an input, intermediate, or final value.
The exception error exception-type occurred while ZERO DIVIDE

performing one of the following operations on a field The data type displayed in the message might indicate
that has a data-type of DECIMAL, FLOAT, SMALLINT, or the data type of the temporary internal copy of the
INTEGER: data. This might differ from the actual column or literal
data type due to conversions by Db2.
• ADDITION
• SUBTRACTION Attention: Parts of exception-type, data-type,
operation-type, and position-number might or might
• MULTIPLICATION not be returned in SQLCA, depending upon when the
• DIVISION error was detected.
• NEGATION
• BUILT-IN FUNCTION System action
The error occurred while processing an arithmetic For each expression in error the indicator variable
expression in the SELECT list of an outer SELECT is set to negative two (-2) to indicate a null value
statement, and the position in the select list is denoted returned. The data variable is unchanged. Execution
by position-number. The possible exception types are: of the statement continues with all non-error columns
and expressions of the outer SELECT list being
DECIMAL OVERFLOW
returned. If the statement is cursor controlled then the
A decimal overflow exception can occur when
cursor will remain open.
one or more nonzero digits are lost because the
destination field in any decimal operation is too
short to contain the result. Programmer response
DIVIDE EXCEPTION Examine the expression for which the warning
A divide exception can occur on a decimal division occurred to see if the cause (or the likely cause) of
operation when the quotient exceeds the specified the problem can be determined. The problem may be
data-field size. A zero divide exception occurs on data-dependent, in which case it will be necessary to
any division by zero, except when the data type is examine the data that was being processed at the time
DECFLOAT. the error occurred.
EXPONENT OVERFLOW See the explanation of SQLCODE -405 for allowed
An exponent overflow can occur when the ranges of numeric data types.
result characteristic of any floating-point operation
exceeds 127 and the result fraction is not zero, i.e.
the magnitude of the result exceeds approximately SQLSTATE
7.2E+75. 01519

+806 BIND ISOLATION LEVEL RR +863 THE CONNECTION WAS
CONFLICTS WITH TABLESPACE SUCCESSFUL BUT ONLY SBCS
LOCKSIZE PAGE OR LOCKSIZE WILL BE SUPPORTED
ROW AND LOCKMAX 0
Explanation
Explanation
The target AS supports only the Db2 SBCS CCSID. The
The specification of isolation level RR is incompatible Db2 Mixed CCSID or GRAPHIC CCSID or both are not
with the LOCKSIZE PAGE or LOCKSIZE ROW and supported by the target AS. Db2 character data sent to
LOCKMAX 0 specification for a table space accessed the target AS must be restricted to SBCS.
by the application. Table space locking is used to
protect the integrity of the application. System action
The CONNECT statement is successful. The release
System action
level of the target AS has been placed into the
A valid package/plan is created if no errors are SQLERRP field of the SQLCA.
detected. Table space locking is used. RR isolation
level is preserved. Programmer response
Do not execute any SQL statements which pass either
Programmer response
mixed data or graphic data as input host variables.
If you do not want table space locking, use isolation
level UR, CS, or RS. SQLSTATE
01539
SQLSTATE
Related concepts
01553
+807 THE RESULT OF DECIMAL Character and graphic string operands (Db2
MULTIPLICATION MAY CAUSE SQL)
OVERFLOW Mixed data in character strings (Db2 SQL)
Related reference
Explanation CONNECT (Db2 SQL)
An arithmetic expression contains a decimal
multiplication that may cause an overflow condition +883 ROLLBACK TO SAVEPOINT
when the statement is executed. The problem may be OCCURRED WHEN THERE WERE
corrected by restructuring the arithmetic expression OPERATIONS THAT CANNOT BE
so that decimal multiplication precedes decimal UNDONE, OR AN OPERATION
division or by changing the precision and scale of the THAT CANNOT BE UNDONE
operands in the arithmetic expression. OCCURRED WHEN THERE WAS A
SAVEPOINT OUTSTANDING
System action
Explanation
A valid package will be created if no errors are
detected. The operations that are referred to are updates
(inserts into or deletes from) a created global
temporary table. If this SQL warning code is received
SQLSTATE as the result of a ROLLBACK TO SAVEPOINT
01554 statement, the rollback is performed; however, the
changes that were made to the temporary table are
Related concepts not undone. If this SQL warning code is received as the
Decimal multiplication (Db2 SQL) result of an operation to a created global temporary
Decimal division (Db2 SQL) table, the operation is performed; however, be advised
Precision for operations with decimal numbers that a savepoint is outstanding, and the update will
(Db2 Application programming and SQL) not be backed out if a rollback to the savepoint is
performed.

System action When SQLCODE +904 is issued by IBM Db2 Analytics
Accelerator for z/OS, processing of the SQL statement
The SQL statement is processed. continues on the accelerator.

Verify that this is what you meant. No programmer response is needed.
See the IBM Db2 Analytics Accelerator for z/OS
SQLSTATE documentation for more information about the
01640 situations that can result in SQLCODE +904 being
issued.
+904 A RESOURCE IS UNAVAILABLE
BUT PROCESSING CONTINUES.
REASON reason-code, TYPE OF SQLSTATE
RESOURCE resource-type, AND 01687
RESOURCE NAME resource-name
+4726 THE STATEMENT WAS
SUCCESSFULLY PREPARED, BUT
Explanation IT CANNOT BE EXECUTED
A resource was unavailable, but the processing of the BECAUSE authorization-id DOES
SQL statement continues. NOT HAVE privilege-name
PRIVILEGE ON OBJECT object-
reason-code name BUT HAS EXPLAIN
The Db2 reason code value that indicates the PRIVILEGE
reason for the failure. For explanations of reason
codes, see Part 2, “Db2 reason codes,” on page
373. Explanation
resource-type During prepare, the authorization ID does not have
The type of resource that the message identifies. the indicated privilege for an object but has EXPLAIN
For explanations of resource types, see Resource privilege.
types (Db2 Messages).
authorization-id
resource-name The authorization ID of the process.
The name of the resource that the message
object-name
identifies.
The name of the object that the privilege applies
The value in resource-name depends on the to.
remote server source of SQLCODE +904. See the privilege-name
following notes for more information. The name of the privilege required to prepare the
Notes: statement.
• When reason-code is 00E7000E and resource-type is The statement that was prepared by using the
00001080, SQLCODE +904 was issued by IBM Db2 EXPLAIN privilege cannot be executed, and a cursor
Analytics Accelerator for z/OS, and resource-name is cannot be opened for the statement. Only the SQL
message text from the accelerator that indicates the descriptor information can be obtained from the
reason for the SQL code. prepared statement.
IBM Db2 Analytics Accelerator for z/OS can return The following authorities have implicit EXPLAIN
SQLCODE +904 on an SQL OPEN for certain privilege:
accelerated queries when the CURRENT QUERY • SQLADM
ACCELERATION WAITFORDATA special register
is used to specify a delay wait time for the • System DBADM
query. See the IBM Db2 Analytics Accelerator for • SYSADM
z/OS documentation for information about when
SQLCODE +904 is returned for an accelerated query. System action
The prepared statement was not executed. No cursor
System action
was opened for the statement.
Processing of the SQL statement continues.

Programmer response Related reference
SYSPACKSTMT catalog table (Db2 SQL)
Ensure that no OPEN or EXECUTE statements refer to
the prepared statement. +4748 THE statement STATEMENT
FOR OBJECT object-name
SQLSTATE WAS SUCCESSFUL ON THE
DB2 SERVER. THE OBJECT
0168Z
MAY NOT HAVE BEEN
+4745 A SECTION WAS BOUND SUCCESSFULLY PROCESSED ON
SUCCESSFULLY, BUT AN THE ACCELERATOR SERVER FOR
ERROR OCCURRED WHEN REASON reason-code.
A STATEMENT IN A
RELATED EXTENDED SECTION Explanation
WAS BOUND. INFORMATION
RETURNED: SECTION NUMBER The statement for object-name was successful, but an
section-number, SQLCODE sqlcode, error occurred on the accelerator server.
SQLSTATE sqlstate, AND MESSAGE object-name
TOKENS token-list The name of the object that was specified to be
dropped.
Explanation reason-code
The bind of a section was successful, but an error A numeric value that provides additional
occurred in one of the statements in the related information about why the statement cannot be
extended section. executed in the accelerator server. Possible values
are:
section-number
The section number that is associated with the 1. A row corresponding to the table does not exist
failing triggered SQL statement. in the SYSACCELERATEDTABLES catalog table.
sqlcode 2. The accelerator server is not available for one
The SQLCODE that was generated when the failing of the following reasons:
statement was bound. • The accelerator server has not been started.
sqlstate • The accelerator server was started in
The corresponding SQLSTATE for the SQLCODE EXPLAIN ONLY mode.
that was generated when the failing statement was
• The accelerator server was started in
bound
maintenance mode.
token-list
• The accelerator server accelerator does not
The list of tokens from the original SQL error. This
exist.
list might be truncated.
3. A DRDA error was encountered.
System action
System action
Db2 bound a section successfully and created a
package for that section. However, Db2 could not The object was dropped at the Db2 server. The
bind the related extended section. A package was not object might not have been dropped at the associated
created for the extended section. accelerator server.

Use the section number in the SYSIBM.SYSPACKSTMT Use the reason code to determine the cause of the
table to determine the failing SQL statement. Refer to failure, and take the appropriate action.
the explanation of the reported SQLCODE. Follow the 1. No action is needed. The table on the accelerator
suggested action for that message. has already been dropped.
2. When the accelerator is available, invoke the
SQLSTATE accelerator procedure to drop the table on the
01578 accelerator.

3. The drop did not get processed on the accelerator Related tasks
because a connection could not be established with Reusing and comparing access paths at bind
the accelerator. When the accelerator is available, and rebind (Db2 Performance)
invoke the accelerator procedure to drop the table Related reference
on the accelerator.
APCOMPARE bind option (Db2 Commands)
APREUSE bind option (Db2 Commands)
SQLSTATE EXPLAIN bind option (Db2 Commands)
0169B Related information
Related reference DSNT337I (Db2 Messages)
+4754 THE ACCELERATOR accelerator-
name DOES NOT EXIST.
+4751 bind-type WARNING FOR
PACKAGE = package-name,
THE USE OF keyword RESULTED Explanation
IN UNSUCCESSFUL COMPLETION
An SQL statement referenced an accelerator server
FOR ONE OR MORE STATEMENTS.
that does not exist or has not been started. The
specified accelerator might not be defined to Db2 or
Explanation it might not have been started since Db2 was last
started.
The subcommand finished successfully. However,
APCOMPARE or APREUSE might not be completely accelerator-name
successful. This warning message is issued for remote The name of the accelerator server that does not
BIND or REBIND only. One of the following conditions exist or that has not been started.
occurred:
• APCOMPARE(WARN) was specified but the use of System action
APCOMPARE resulted in some statements where
Processing continues normally. If an SQL statement
comparison is not successful or comparison could
references an accelerator server that does not exist,
not be performed.
the statement is processed as if no accelerator server
• APREUSE(WARN) was specified and the use of is specified.
APREUSE resulted in some statements where
APREUSE is either not successful or partially
successful, or APREUSE could not be performed, or
User response
APREUSE was suppressed by other hints. No change is required. However, the specified
bind-type accelerator server must be defined to Db2 before it
The type of bind command: BIND or REBIND is used during the execution of other SQL statements
that require it.
package-name
The name of the package, in the format location-
id.collection-id.package-id. SQLSTATE
keyword 0169D
APCOMPARE or APREUSE. Related reference
ACCELERATOR bind option (Db2 Commands)
System action
+20002 THE specification-source
The package is rebound.
SPECIFICATION IS IGNORED FOR
OBJECT object-name
User response
For detailed results of APREUSE or APCOMPARE, Explanation
check the EXPLAIN tables
An SQL statement includes a specification that was
ignored.
SQLSTATE
specification-source
01599 The source of the specification, either a clause or a
bind option.

GBPCACHE clause • Avoid using the USE CURRENTLY COMMITTED
The GBPCACHE clause conflicts with the group clause to access non-versioned XML.
buffer pool specification GBPCACHE(NO). • Convert the table to a table that supports
When the group buffer pool attribute is set to multiple XML versions.
GBPCACHE(NO), the clause can contain only
GBPCACHE NONE. The clause is part of one of ACCESSCONCURRENTRESOLUTION
the following statements: (UseCurrentlyCommitted)
To prevent future instances of this message:
• CREATE INDEX
• Avoid using this bind option for a plan or package
• ALTER INDEX
that will access non-versioned XML.
• CREATE TABLESPACE
• Convert the table to a table that supports
• ALTER TABLESPACE multiple XML versions.
PADDED or NOT PADDED clause
The statement identifies an index that does not SQLSTATE
have any varying-length character or graphic
columns in the index key. The PADDED and 01624
NOT PADDED attributes do not apply in this Related concepts
case. The clause is part of one of the following XML versions (Db2 Programming for XML)
statements:
Related tasks
• CREATE INDEX Changing the GBPCACHE attribute (Db2 Data
• ALTER INDEX Sharing Planning and Administration)
Related reference
USE CURRENTLY COMMITTED clause
The SELECT statement identifies a table that REORG TABLESPACE (Db2 Utilities)
does not support multiple XML versions. The BIND PACKAGE (DSN) (Db2 Commands)
USE CURRENTLY COMMITTED clause requires BIND PLAN (DSN) (Db2 Commands)
that the table support multiple XML versions.
+20007 USE OF OPTIMIZATION HINTS
ACCESSCONCURRENTRESOLUTION
IS DISALLOWED BY A
(UseCurrentlyCommitted) bind option
DB2 SUBSYSTEM PARAMETER.
The SELECT statements that are bound in
THE SPECIAL REGISTER
this package identify one or more tables that
'OPTIMIZATION HINT' IS SET TO
do not support multiple XML versions. This
AN EMPTY STRING.
bind option requires that the tables support
multiple XML versions.
object-name
Explanation
The name of the object. Db2 is not enabled to use optimization hints. The
special register OPTIMIZATION HINT is set to an
System action empty string.
The statement is processed, but the clause is ignored.

System action
User response The user-specified optimization hints are ignored. The
access path is determined without the use of hints and
No action is required. processing continues normally.
GBPCACHE clause
To use other GBPCACHE options (ALL, CHANGED, Programmer response
or SYSTEM), alter the table space or index to
Enable the use of OPTIMIZATION HINT by changing
use a group buffer pool that is defined with
the value of OPTIMIZATION HINTS on the Db2
GBPCACHE(YES).
Installation panel DSNTIP8.
PADDED or NOT PADDED clause
To prevent future instances of this message, If, after further consideration, you do not want to
remove the clause from the statement. use an OPTIMIZATION HINT, use the SET CURRENT
OPTIMIZATION HINT statement to disable the use of
USE CURRENTLY COMMITTED clause optimization hints.
To prevent future instances of this message:

Specify an empty string, or a string of blanks, on a SET In these cases, the actual length of the truncated
CURRENT OPTIMIZATION HINT statement to cause value cannot be returned to the application that uses
Db2 to use normal optimization techniques and ignore the indicator variable. The actual length of the value is
optimization hints. returned as message token length.

01602 The assignment was made, but the data was
truncated.
+20122 DEFINE NO OPTION IS NOT
APPLICABLE IN THE CONTEXT
SPECIFIED Programmer response
Change the declaration of hv-or-parm-number to avoid
Explanation truncation.
The DEFINE NO option was specified, however it is not
applicable in the context specified. DEFINE NO was SQLSTATE
specified in one of the following situations: 01004
• a CREATE INDEX statement that included the VCAT
+20187 ROLLBACK TO SAVEPOINT
clause
CAUSED A NOT LOGGED TABLE
• a CREATE INDEX statement for a non-empty table SPACE TO BE PLACED IN THE LPL
• a CREATE INDEX statement on a declared temporary
table Explanation
• a CREATE LOB TABLESPACE statement An application issued a ROLLBACK, but uncommitted
• a CREATE TABLESPACE statement that included the changes existed for a table space defined with the NOT
VCAT clause LOGGED logging attribute. Db2 cannot undo changes
• a CREATE INDEX statement for a table that has a made to not logged table spaces because no log
defined clone records were written due to the logging attribute of
the table space. The table space is placed in the LPL
so that other concurrently running agents are not able
System action to see the data that cannot be rolled back. The table
Db2 ignored the DEFINE NO option and created the space is also marked recover pending because the
object with the DEFINE YES option instead. table space has been modified.

01644 The ROLLBACK TO SAVEPOINT was performed,
however changes that were made to not logged table
+20141 TRUNCATION OF VALUE WITH spaces have not been undone.
LENGTH length OCCURRED FOR
hv-or-parm-number
Programmer response
Explanation Avoid making changes to a not logged table space
within the span of a savepoint to which you intend to
A value that was assigned to a host variable or rollback.
parameter was truncated. However, the length of the
value that was truncated is too large to be returned in To remove a table space from the LPL and reset
the indicator variable. This situation can occur when recover pending, use one of the following options:
truncation occurs on assignment of: • REFRESH TABLE to repopulate a Materialized Query
• a value to a parameter of a remote stored procedure Table, but only if the Materialized Query Table is
if the value being truncated is greater than 127 alone in its table space. If the table, including
bytes. In this case, the indicator variable will contain Materialized Query Tables, is not alone in its table
a value of 127. space, a utility must be used to reset the table space
and remove it from recover pending.
• a LOB value to a host variable if the value being
truncated is greater than 32K bytes. In this case, the • RECOVER utility, to recover either to currency or to a
indicator variable will contain a value of 32K. prior image copy

• LOAD REPLACE utility or LOAD REPLACE PART utility: SQLSTATE
– With an input data set to empty the table space 01658
and repopulate the table
+20237 FETCH PRIOR ROWSET FOR
– Without an input data set to empty the table
CURSOR cursor-name RETURNED
space to prepare for one or more insert operations
A PARTIAL ROWSET
to repopulate the table
• Drop and re-create the table space and repopulate
the table.
Explanation
• DELETE without a WHERE clause to empty the table. A FETCH PRIOR ROWSET statement was issued, but
When the table space is a segmented (non-UTS) there were not enough rows prior to the current cursor
table space or universal table space, the table is position to reposition the cursor on a full rowset. The
alone in its table space and the table does not have a cursor has been positioned on a partial rowset. If a
VALIDPROC, referential constraints, delete Triggers, target was specified, then data has only been returned
or a SECURITY LABEL column (or has this column, for the number of rows that were actually fetched for
but multilevel security is not in effect). the partial rowset.
• TRUNCATE TABLE to empty the table. When the
table space is segmented (non-UTS) table space or System action
universal table space, the table is alone in its table The cursor is positioned on a partial rowset.
space and the table does not have a VALIDPROC,
referential constraints, or a SECURITY LABEL column
(or has this column, but multilevel security with row Programmer response
level granularity is not in effect). Analyze the situation to determine if anything should
Important: If the table, materialized query table or be rolled back.
not, is not alone in its table space, a utility must be
used to reset the table space and remove it from SQLSTATE
recover pending.
02504
SQLSTATE +20245 NOT PADDED CLAUSE IS IGNORED
FOR INDEXES CREATED ON
01656 AUXILIARY TABLES
+20224 ENCRYPTED DATA THAT WAS
ORIGINALLY A BINARY STRING Explanation
CANNOT BE DECRYPTED TO A
CHARACTER STRING The NOT PADDED clause is ignored on the CREATE
INDEX statement because auxiliary indexes are always
PADDED.
Explanation
The DECRYPT_BIT, DECRYPT_CHAR, or DECRYPT_DB System action
function was invoked with an argument that
represents an encrypted string that was originally The option is ignored; processing continues.
a binary string. A binary string cannot be cast
to a character string using the DECRYPT_BIT, Programmer response
DECRYPT_CHAR, or DECRYPT_DB function.
Remove the NOT PADDED clause to avoid this warning.
System action
SQLSTATE
The statement cannot be processed.
01663
Programmer response +20270 OPTION NOT SPECIFIED

FOLLOWING ALTER PARTITION
The encrypted value can only be decrypted using the CLAUSE
DECRYPT_BINARY function.

Explanation object-name
The name of a column, user-defined type, schema
An ALTER INDEX statement, which included the ALTER of a user-defined type, or parameter that was
PARTITION clause, did not contain an option following truncated. Use of the SQLDA structure limits the
the ALTER PARTITION keywords. length of names for objects of these types.
System action System action

The SQL statement is processed. Processing continues.
Programmer response User response

Specify a partition option after the ALTER PARTITION If the exact name is significant, do one of the
keywords to avoid this warning in the future. For following:
an ALTER INDEX statement, if partition-element is
specified, specify either the ENDING clause of: • For the name of a result column that is specified in
an AS clause, change the name in the AS clause so
• partition-element that the result column has a shorter name.
• using-block • For the name of a column in a table or view, drop and
• free-block re-create the table or view so that the column has
• gbcaches-block a shorter name, or provide a shorter name for the
result column in the query with an AS clause.
• For the name of a column in a table, use the ALTER
SQLSTATE
TABLE statement to rename the column so that it
01664 has a shorter name.
+20271 THE NAME AT ORDINAL • For a parameter name, change the procedure so the
POSITION position-number IN THE parameter has a shorter name.
STATEMENT, WITH NAME object- • For a user-defined type name drop and recreate the
name, WAS TRUNCATED. user defined-type with a shorter name.
At least one object name in the described statement 01665
was truncated. The object name was either too long, or
became too long after code page conversion. +20272 TABLE SPACE table-space-name
HAS BEEN CONVERTED
position-number TO USE TABLE-CONTROLLED
The ordinal position number of the name that was PARTITIONING INSTEAD
truncated. For the describe output of a prepared OF INDEX-CONTROLLED
query, the ordinal position is relative to the order of PARTITIONING, ADDITIONAL
columns in the select list of the query: INFORMATION: old-limit-key-value
• For DESCRIBE CURSOR or DESCRIBE OUTPUT,
the position is relative to the order of the Explanation
columns in the select list of the query.
When one of the following statements executed, table-
• For DESCRIBE TABLE, the position is relative to space-name was converted to use table-controlled
the order of the columns in the table or view partitioning instead of index-controlled partitioning:
definition.
• ALTER INDEX with the CLUSTER NO clause
• When describing the output of a CALL statement,
the position is relative to the OUT or INOUT • ALTER TABLE...ADD PARTITION
parameters of the procedure to which the CALL • ALTER TABLE...ALTER PARTITION
resolved.
• ALTER TABLE...ROTATE PARTITION
• When describing the input of a CALL statement,
• CREATE INDEX...ENDING AT without the CLUSTER
the position is relative to the IN or INOUT
clause
parameters of the procedure to which the CALL
resolved. • CREATE PARTITIONED INDEX
• DROP INDEX for a partitioning index

If the statement was ALTER INDEX, CREATE disabled. You can also define the fullselect of the view
PARTITIONED INDEX, or DROP INDEX, the last to remove the elements that prevent optimization.
partition's old value of old-limit-key-value was set to
the highest possible value for an ascending index key SQLSTATE
column, or the lowest possible value for a descending
index key column. For all other statements, *N is 01667
returned for old-limit-key-value.
Related reference
If the statement was ALTER TABLE with the ROTATE CREATE TABLE (Db2 SQL)
PARTITION clause, then certain partitions might be CREATE VIEW (Db2 SQL)
left in REORG pending state.
DROP (Db2 SQL)
System action +20341 OWNERSHIP TRANSFER WAS

IGNORED BECAUSE auth-id IS
The statement is successfully executed. If the
ALREADY THE OWNER OF THE
statement was ALTER INDEX, CREATE PARTITIONED
OBJECT.
INDEX, or DROP INDEX, the LIMITKEY column
in SYSIBM.SYSTABLEPART was set to the highest
possible value for an ascending index key column, or Explanation
the lowest possible value for a descending index key A TRANSFER OWNERSHIP statement was issued to
column. transfer the ownership of the object to authorization
ID auth-id. The specified authorization ID is already
SQLSTATE the owner of the object. There is no need for the
transfer. If the ownership is transferred to a role, the
01666
role name is returned as a single token in the format of
Related tasks ROLE: role-name.
Creating tables partitioned by data value ranges
(Db2 Administration Guide) System action
Eliminating unnecessary partitioning indexes
(Db2 Performance)
+20278 THE VIEW view-name MAY NOT Programmer response

BE USED TO OPTIMIZE THE
No action is required.
PROCESSING OF QUERIES
01676
The fullselect of the view includes elements that
prohibit the use of the statistics on the view for +20348 THE PATH VALUE HAS BEEN
optimization when the view is not referenced directly TRUNCATED.
in a query. These elements of the fullselect might
include:
Explanation
• Aggregate functions
The PATH value exceeded the limit of bytes that the
• Distinct operations PATH column of SYSIBM.SYSJAROBJECTS can contain.
• Set operations (UNION, EXCEPT, or INTERSECT) The PATH column of SYSIBM.SYSJAROBJECTS stores
only the first 2048 bytes of the value passed to
SQLJ.ALTER_JAVA_PATH.
System action
The view is successfully altered to enable query System action
optimization.
Programmer response
User response
No action is required. If the intent of the view is to
optimize queries that do not directly reference the If you need to know the entire PATH value, query the
view, you can drop the view or have query optimization SYSIBM.SYSJAVAPATHS table.

SQLSTATE SQLSTATE:
01011 01565
+20360 TRUSTED CONNECTION CAN NOT +20367 OPTION clause IS NOT
BE ESTABLISHED FOR SYSTEM SUPPORTED IN THE CONTEXT IN
AUTHID authorization-name WHICH IT WAS SPECIFIED
A trusted connection cannot be established for The clause in the statement is not supported in the
authorization-name. A matching trusted context is not context in which has been specified. The clause is
currently defined. SQLWARN8 is set to indicate that a ignored.
trusted connection was not established.
System action
System action
Processing continues normally.
The attempt to create a trusted connection was not
successful. A normal connection is created without Programmer response
any attributes of a trusted context.
No change is required for the current release; however,
it is recommended that the statement be modified to
Programmer response
conform to valid SQL syntax.
Ensure that the trusted context has been correctly
defined and try to re-establish a trusted connection. SQLSTATE
01680
SQLSTATE
01679 +20368 TRUSTED CONTEXT context-name
IS NO LONGER DEFINED TO BE
+20365 A SIGNALING NAN WAS USED BY SPECIFIC VALUES FOR
ENCOUNTERED, OR AN ATTRIBUTE attribute-name.
EXCEPTION OCCURRED IN
AN ARITHMETIC OPERATION Explanation
OR FUNCTION INVOLVING A
DECFLOAT. An ALTER TRUSTED CONTEXT statement for context-
name was issued that removed all of the values for
attribute attribute-name.
Explanation
A signaling NaN (sNaN) was encountered in an System action
expression, arithmetic operation, or function involving
a DECFLOAT column, or value resulted in an exception. The statement was processed. The trusted context
In either case, the result is NAN, and a warning is no longer has any values associated with attribute
issued. attribute-name.
System action User response

Execution of the statement continues. All non-error Issue an ALTER TRUSTED CONTEXT statement with an
columns and expressions of the outer SELECT list are ADD ATTRIBUTES clause if you want to define new
returned. If the statement is cursor controlled, then values for the attribute.
the cursor will remain open.
SQLSTATE
User response
01681
Examine the expression for which the warning
Related reference
occurred to see you can determine the cause of the
problem. The problem might be data-dependent, in ALTER TRUSTED CONTEXT (Db2 SQL)
which case you must examine the data that was being CREATE TRUSTED CONTEXT (Db2 SQL)
processed at the time the error occurred.

+20371 THE ABILITY TO USE TRUSTED SQLSTATE:
CONTEXT context-name WAS
REMOVED FROM SOME, BUT 01683
NOT ALL AUTHORIZATION IDS +20458 THE PROCEDURE procedure-name
SPECIFIED IN THE STATEMENT. HAS ENCOUNTERED AN INTERNAL
PARAMETER PROCESSING ERROR
Explanation IN PARAMETER number1.
THE VALUE FOR PARAMETER
An ALTER TRUSTED CONTEXT statement for context number2 CONTAINS FURTHER
name contained a DROP USE FOR clause with INFORMATION ABOUT THE
multiple authorization IDs or PUBLIC, but one or more ERROR.
authorization IDs were not defined to use the trusted
context.
Explanation
System action The format or content of the parameter in ordinal
position number1 in the call to the procedure
The statement is processed. procedure-name is invalid. The output parameter
specified in ordinal position number2 contains
Programmer response information on how to respond to the error.
One or more users were removed from the definition of

the trusted context, but one or more other users were User response
not previously allowed to use the trusted context. Use the information in the output parameter specified
in ordinal position number2 to correct the format or
SQLSTATE content of the parameter value and call the procedure
again.
01682
+20378 A NON-ATOMIC statement SQLSTATE
STATEMENT SUCCESSFULLY
COMPLETED FOR SOME OF THE 01H54
REQUESTED ROWS, POSSIBLY +20459 THE PROCEDURE procedure-
WITH WARNINGS, AND ONE OR name HAD ENCOUNTERED AN
MORE ERRORS, AND THE CURSOR INTERNAL PROCESSING ERROR.
CAN BE USED THE VALUE FOR PARAMETER
number CONTAINS FURTHER
Explanation INFORMATION ABOUT THE
ERROR.
A non-atomic statement statement successfully
processed some of the rows of data that
were requested. However, one or more error Explanation
conditions occurred, and some warnings might have An error occurred when the procedure procedure-
also occurred. Use GET DIAGNOSTICS to obtain name was processing a request. The output parameter
information about the error and warning conditions specified in ordinal position number contains
that occurred. The cursor can be used to retrieve data information on how to respond to the error.
for the rows that were successfully processed.
User response
System action
An error occurred when the procedure procedure-
One or more rows were successfully processed, but name was processing a request. The output parameter
one or more errors or warnings also occurred. specified in ordinal position number contains
information on how to respond to the error. number
Programmer response to correct the error and call the procedure again.
Analyze the error and warning conditions to determine

if the statement should be rolled back. SQLSTATE
01H55

+20460 THE PROCEDURE procedure- already contains one or more XML schemas with
name SUPPORTS A HIGHER the same combination of the target namespace and
VERSION, version1. THAN THE schema location hint values.
SPECIFIED VERSION, version2,
target-namespace
FOR PARAMETER number.
The target namespace of the XML schema that was
registered.
Explanation location-hint
A higher version, version1, for the parameter in The schema location hint for the XML schema that
ordinal position number is supported by the procedure was registered.
procedure-name. The specified version, version2, is
supported for the parameter. System action
The XML schema has been successfully registered and
User response is stored in the Db2 XML schema repository.
Check the documentation for the procedure to
understand the additional features supported by the Programmer response
newer version of the parameter. Upgrade to the
current version to take advantage of these additional Applications that perform XML schema validation
features. using this XML schema can refer to the XML schema
only by its schema name, and not by its target
namespace and schema location hint. If there is a
SQLSTATE need to refer to the XML schema with the target
01H56 namespace and schema location hint, remove the
XML schema from the XML schema repository, and
+20461 THE PROCEDURE procedure-name register it again with a unique combination of target
RETURNED OUTPUT IN THE namespace and schema location hint.
ALTERNATE LOCALE, locale1,
INSTEAD OF THE LOCALE locale2,
SPECIFIED IN PARAMETER SQLSTATE
number. 0168X
+20520 ATTEMPT TO USE A DEPRECATED
Explanation FEATURE msg-token. REASON
The locale, locale2, specified in the parameter in CODE reason-code
ordinal position number was not available for the
output of the procedure procedure-name. The output Explanation
is returned using locale locale1.
The statement attempted to use a feature or format
that is deprecated.
User response
msg-token
Install the message file support on the server for the Text that identifies the deprecated feature.
specified locale, locale2, or specify a supported locale.
reason-code
A numeric value that identifies the deprecated
SQLSTATE feature.
01H57 2
A table is defined with a format that is
+20468 THE COMBINATION OF TARGET
no longer supported by EXPLAIN. Processing
NAMESPACE target-namespace
continues, and the EXPLAIN tables are
AND SCHEMA LOCATION HINT
populated as usual. The name of the table
location-hint IS NOT UNIQUE
is returned in msg-token. Only one instance
IN THE DB2 XML SCHEMA
of this message is issued per package for
REPOSITORY.
EXPLAIN tables in supported formats during
bind or rebind.
Explanation
XSR_COMPLETE completed registration of an XML
schema. However, the Db2 XML schema repository

Processing continues. No action is required.
User response SQLSTATE

No immediate action is required. However, it is best to 0169A
update the statement to prepare for when an error will
be returned for the same condition. +30100 OPERATION COMPLETED
SUCCESSFULLY BUT A
DISTRIBUTION PROTOCOL
Programmer response VIOLATION HAS BEEN DETECTED.
Change the statement for future releases. ORIGINAL SQLCODE=original-
sqlcode AND ORIGINAL
SQLSTATE=original-sqlstate
SQLSTATE
01694 Explanation
Related concepts The application requested operation (either COMMIT
Function that Db2 12 no longer supports (Db2 or ROLLBACK) has completed successfully but the
for z/OS What's New?) response from the remote server and the SQLCODE
Related reference that was returned from the remote server are
Deprecated function in Db2 12 (Db2 for z/OS inconsistent. For example, the reply message from
What's New?) the remote server indicates that a COMMIT operation
completed successfully but the SQLCODE returned
Related information
from the AS was negative.
-20008
ATTEMPT TO USE UNSUPPORTED FEATURE
msg-token. REASON CODE: reason-code System action
An alert was generated. A DSNL031I message may
+20543 A SYSTEM PARAMETER WAS have been written to the console. Refer to the
OVERRIDDEN FOR object-name description of this message for further information.
WHEN PROCESSING THE
statement-name STATEMENT. The SQLCODE returned by the remote server is
REASON reason-code replaced with +30100 and the SQLSTATE returned by
the remote server is replaced with 01558.
Explanation The SQLCODE and SQLSTATE values that were
returned from the AS are stored in the SQLERRM field
A system parameter was overridden for the statement- in a string of the following format: original-sqlcode
name SQL statement that was processed. 'FF'X original-sqlstate
reason-code indicates which system parameter was
overridden and what value was used by the system.
The RBA or LRSN 6-byte limit was already
exceeded when an object that was created or Notify the System Programmer for assistance in
added. The statement was processed by using 10- analyzing the trace data that was generated.
byte RBA or LRSN values.
SQLSTATE
System action 01558
The statement was processed with the system-
determined value for the system parameter.

Chapter 2. Error (−) SQL codes
SQL return codes that are preceded by a minus sign (−) indicate that the SQL statement execution was
unsuccessful.
List of error SQL codes

The following SQL codes indicate unsuccessful execution of the SQL statement.
Related tasks
Handling SQL error codes (Db2 Application programming and SQL)
Related reference
SQLCODE (Db2 SQL)
-007 STATEMENT CONTAINS THE SQLSTATE

ILLEGAL CHARACTER invalid-
character 42603
-011 COMMENT NOT CLOSED
Explanation
The specified invalid-character is not a valid character Explanation
in SQL statements. A comment is not closed correctly with a comment
delimiter. The comment is treated as if it were closed
System action by the end of source file.

System action
Programmer response The statement cannot be processed.
Correct the syntax and resubmit the statement.

User response
SQLSTATE Ensure that the comment delimiter is specified
properly. This error is likely to cause other errors.
42601 Some statements might not have been processed as
Related concepts a result of a missing comment delimiter.
Characters (Db2 SQL)
Language elements (Db2 SQL) SQLSTATE
42601
-010 THE STRING CONSTANT
BEGINNING string IS NOT -029 INTO CLAUSE REQUIRED
TERMINATED
Explanation
Explanation
SELECT statements embedded in an application
The statement contains a string constant, beginning program must have an INTO clause to denote where
with 'string', that is not terminated properly. the results of the SELECT are to be placed. Dynamic
SELECT statements do not permit the INTO clause.
System action
System action
Programmer response
Examine the statement for missing quotation marks or
apostrophes in the indicated string constant.

Add the INTO clause to the SELECT statement and Change the routine definition so that the SQLSTATE
precompile the application program again. and SQLCODE variables are only declared in the
outermost compound statement of the SQL routine.
SQLSTATE
SQLSTATE
42601
42630
-051 identifier-name (sql-type) WAS
PREVIOUSLY DECLARED OR -057 THE RETURN STATEMENT IN AN
REFERENCED SQL FUNCTION MUST RETURN A
VALUE.
Explanation
Explanation
The identifier name has already been defined for the
indicated type of SQL object. A RETURN statement is specified without a value in an
SQL function. The return value must be specified.
identifier-name
The name that has already been used.
sql-type
System action
The type of SQL object: TABLE, CURSOR, or The statement cannot be processed.
STATEMENT.
The definition might have occurred implicitly. For User response
example, identifier-name might have been found in
Add a return value to the statement, and retry your
the FROM clause of a SELECT, which causes it to be
request.
defined as a table.
A cursor name must be unique within the program or
SQLSTATE
routine.
42631
System action -058 VALUE SPECIFIED ON RETURN
The statement cannot be processed. STATEMENT MUST BE AN INTEGER
User response Explanation

Remove duplicate definitions or correct the A RETURN statement is specified in an SQL procedure
references. but the value specified is not an integer. The return
value for an SQL procedure must be an integer.
SQLSTATE
System action
3C000
-056 AN SQLSTATE OR SQLCODE
VARIABLE DECLARATION IS IN A
User response
NESTED COMPOUND STATEMENT
Specify an integer value on the RETURN statement. Try
Explanation the request again.
An SQLSTATE or SQLCODE variable declaration is in a

SQLSTATE
nested compound statement instead of the outermost
compound statement in the SQL routine. 428F2
-060 INVALID specification-type
System action SPECIFICATION : specification-
The statement cannot be processed. value

Explanation SQL is optional, but for external SQL procedures,
LANGUAGE SQL is required.
The specified value is invalid.
specification-type System action
The type of specification: LENGTH, SCALE, or
CCSID. The statement cannot be processed.
specification-value
The value specified. Programmer response
LENGTH or SCALE must be specified by an unsigned Ensure that each defined parameter includes a
integer constant and the value must be in the range parameter name.
allowed by the data type.
In addition: SQLSTATE
• For a CREATE INDEX statement, a length specified 42629
for VARCHAR must not be greater than 1000, and an Related reference
integer specified with DECFLOAT must be 34.
CREATE TABLE (Db2 SQL)
• For CREATE TABLE, CREATE TYPE, ALTER TABLE
ADD COLUMN, or ALTER TABLE ALTER COLUMN -079 QUALIFIER FOR OBJECT name
statements, the INLINE LENGTH attribute specified WAS SPECIFIED AS qualifier1 but
for a LOB type must not exceed 32680 for a CLOB or qualifier2 IS REQUIRED
BLOB column, or 16340 for a DBCLOB column.
• For a CREATE VARIABLE statement, an array type Explanation
with elements that are defined as character strings
must be defined with CCSID UNICODE. The schema qualifier for the Db2 object must be
qualifier2. The statement defines a new object named
name with an explicit schema qualifier of qualifier1.
System action Specifying a schema qualifier other than qualifier2 is
The statement cannot be processed. not allowed.
Programmer response System action

Correct the syntax, and reissue the statement. The statement cannot be processed.

42815 Change the statement in one of the following ways:
Related concepts • Change the schema qualifier to qualifier2.

Language elements (Db2 SQL) • Remove the schema qualifier, and let Db2 default it
Related reference to qualifier2.
Statements (Db2 SQL)
SQLSTATE
-078 PARAMETER NAMES MUST BE
SPECIFIED FOR ROUTINE routine- 428EK
name -084 UNACCEPTABLE SQL STATEMENT
The routine does not have parameter names specified This SQL statement is unacceptable to Db2. One of the
for all parameters. following situations has occurred:
routine-name • An attempt has been made to PREPARE or EXECUTE
The name of the routine. IMMEDIATE an SQL statement that cannot be
When the SQL routine is defined with LANGUAGE SQL, prepared.
a parameter name is required for each parameter • The embedded SQL statement is not an SQL
that is defined. For native SQL procedures, LANGUAGE statement supported by Db2.
Chapter 2. Error (−) SQL codes 41

• The statement referenced an undeclared cursor. -087 A NULL VALUE WAS SPECIFIED
• An attempt was made to prepare an ALLOCATE IN A CONTEXT WHERE A NULL IS
CURSOR statement but the statement identifier is NOT ALLOWED
already associated with a declared cursor.
• A statement that is to be processed remotely Explanation
referenced an array variable or array element. The An SQL parameter or SQL variable having a null value
remote execution is the result of one of the following was specified in a context in which a null value is
actions: not allowed. For example, an SQL statement can be
– Previous execution of a CONNECT statement specified with an SQL parameter or SQL variable on the
PREPARE and EXECUTE statements. In these contexts
– Use of a three-part name or alias in the current
the value of an SQL parameter or SQL variable must
statement that resolves to an object at a remote
not be null.
server
A statement that is executed remotely cannot
System action
reference an array, except in the following cases:
– The statement is a CALL statement.
– An array element in the statement is a target of a
FETCH, SELECT INTO, SET assignment-statement,
User response
or VALUES INTO statement. Correct the SQL statement.

The statement cannot be processed. 22004
Related reference
Programmer response Statements (Db2 SQL)
Perform one of the following actions, depending on the PREPARE (Db2 SQL)
situation: EXECUTE (Db2 SQL)
• If the SQL statement cannot be prepared, the
-096 VARIABLE variable-name DOES
problem is in the source of the SQL statement,
NOT EXIST OR IS NOT SUPPORTED
not the application program. Thus, no action is
BY THE SERVER AND A DEFAULT
necessary unless the source of the SQL statement
VALUE WAS NOT PROVIDED
is the application program itself.
• If the SQL statement is not supported by Db2,
remove it from the application program and Explanation
precompile again. For a global variable, the variable does not exist at this
• If an attempt was made to prepare an ALLOCATE server.
CURSOR statement, change the application program For a built-in session global variable, the
to use a statement identifier that is not associated GETVARIABLE function was invoked. However, a value
with a declared cursor. does not exist for a variable with the name that was
• If the SQL statement references an array, change the specified, and a default value was not provided.
application program so that the statement does not
• If the qualifier is SESSION, a user-defined variable
execute on a remote server.
with the specified name has not been set by the
connection or signon exit routine.
• If the qualifier is SYSIBM, the server does not
Routing code support a built-in session variable with name that
was specified.
42612
variable-name
Related reference The name of the variable.
PREPARE (Db2 SQL)
EXECUTE IMMEDIATE (Db2 SQL)
System action

Programmer response Explanation
For a global variable, create the variable at this server Db2 cannot process the statement because it exceeds
using the CREATE VARIABLE statement. the system limits for length or complexity. This
SQLCODE is issued for a variety of situations, such as:
For a built-in session global variable, change the
invocation of the function to specify a default value for • Too many parameter markers are specified.
variable-name, or specify a variable that is supported • Enablement of parallelism has made the statement
at the server. too complex.

42704 Db2 cannot process the statement.
Related reference
CREATE VARIABLE (Db2 SQL) Programmer response
GETVARIABLE (Db2 SQL)
Divide the statement into shorter or less complex SQL
statements.
-097 THE USE OF LONG VARCHAR
OR LONG VARGRAPHIC IS NOT If parallelism is enabled for the statement, disable
ALLOWED IN THIS CONTEXT parallelism. You can do that by using the DEGREE(1)
bind option for static SQL, or by setting the CURRENT
Explanation DEGREE special register to '1' for dynamic SQL.
The statement attempted to use the LONG VARCHAR

SQLSTATE
or LONG VARGRAPHIC syntax. This syntax cannot be
used for the following statements: 54001
• CAST specification syntax -102 STRING CONSTANT IS TOO LONG.
• CREATE DISTINCT TYPE STRING BEGINS string
• CREATE FUNCTION
• CREATE PROCEDURE
Explanation
• ALTER FUNCTION The string constant beginning with string has a length
greater than the maximum allowed length. Most
• COMMENT ON FUNCTION strings have these limits:
• GRANT EXECUTE ON FUNCTION
• For a hexadecimal constant (X, GX, or UX), the
• REVOKE EXECUTE ON FUNCTION number of hexadecimal digits must not exceed
• DROP 32704.
Use the VARCHAR or VARGRAPHIC syntax specifying • Any other character string constant must be short
an explicit length as required. enough so that its UTF-8 representation requires no
more than 32704 bytes.
System action • Any other graphic string constant must be short
enough so that its UTF-8 representation requires no
The statement cannot be processed. more than 32704 bytes.
• The sum of the lengths of the UTF-8 representations
Programmer response of the constant values in an ENDING AT clause
must not exceed 765 bytes. This clause applies to
Correct the statement.
CREATE TABLE, ALTER TABLE, CREATE INDEX, or
ALTER INDEX.
SQLSTATE
In some contexts, however, the limit is smaller.
42601
For special registers, the allowable length depends on
-101 THE STATEMENT IS TOO LONG OR the particular special register. A string that exceeds
TOO COMPLEX the limit can be specified only through assignment
from a host variable.

Two consecutive string delimiters are used to is omitted, Db2 detects the error later, and not
represent one string delimiter within the character always immediately after the point where the keyword
string, but these count as 2 bytes when calculating the should appear. The list of alternate symbols are only
lengths of character string constants. suggestions. Some of those symbols might not even
be legal for statements to be executed by Db2. Those
System action symbols are possibly correct for statements sent to
other database management systems.
This SQLCODE will also be issued if the ROLLBACK TO
SAVEPOINT statement is specified without a savepoint
Programmer response name.
The requested function is not available interactively. If
the error occurred in the context of an SQL statement System action
embedded in an application program, assign the long
string to a host variable, and substitute that variable
for the string constant in the SQL statement.
Programmer response
SQLSTATE Correct the statement and execute it again.
54002
SQLSTATE
Related reference
Limits in Db2 for z/OS (Db2 SQL) 42601
-105 INVALID STRING
-103 constant IS AN INVALID NUMERIC
CONSTANT
Explanation
Explanation The statement contains an invalid string. It is neither a
character string nor a graphic string.
The indicated constant begins with a digit, but is not
a valid integer, decimal, decimal floating point, or float
constant. System action
System action
The statement cannot be processed. Programmer response
Specify the correct format of the string. Check for a
Programmer response graphic string, paired delimiters, the character G or N,
and an even number of bytes within the string.
Correct the invalid constant.
SQLSTATE
SQLSTATE
42604
42604
-107 THE NAME name-value IS TOO
-104 ILLEGAL SYMBOL "token". SOME
LONG. MAXIMUM ALLOWABLE
SYMBOLS THAT MIGHT BE LEGAL
SIZE IS maximum-size
ARE: token-list
Explanation
Explanation
The name name-value is too long. The maximum
A syntax error was detected where the symbol "token"
permissible length for names of that type is indicated
occurs in the SQL statement. The list of symbols that
by maximum-size.
might be legal shows some alternate symbols that
could possibly be correct at that point, if the preceding For an SQL version ID, the name must not exceed 64
part of the statement is entirely correct. EBCDIC bytes, or 122 UTF-8 bytes.
However, the preceding part of the statement might
be incorrect. For example, if an important keyword

System action • A UNION or UNION ALL set operator is specified in a
SELECT INTO statement.
• A CREATE TRIGGER statement with an OR REPLACE
clause was specified without a VERSION clause and
Programmer response the existing trigger is defined with more than a single
Choose a shorter name for the object. version.
SQLSTATE clause was specified without a VERSION clause and
the existing trigger is defined with a single version
46002 but the version id is not V1.
42622 • A CREATE PROCEDURE statement with an OR
REPLACE clause was specified without a VERSION
Related reference clause and the existing procedure is defined with
Limits in Db2 for z/OS (Db2 SQL) more than a single version.
-108 THE NAME name IS QUALIFIED • A CREATE PROCEDURE statement with an OR

INCORRECTLY REPLACE clause was specified without a VERSION
clause and the existing procedure is defined with a
single version but the version id is not V1.
Explanation
• A CREATE LOB TABLESPACE statement specifies a
The name name is improperly qualified. COMPRESS YES FIXEDLENGTH or COMPRESS YES
HUFFMAN clause.
A target name on the RENAME statement may not
have a schema qualifier.
System action
System action The statement cannot be processed.
Programmer response
Programmer response Correct the syntax, and reissue the SQL statement.
Remove the schema qualifier and reissue the You can use a nested table expression to rewrite a
statement. UNION or UNION ALL set operator that is used in a
SQLSTATE
SQLSTATE
42601
42601
-109 clause-type CLAUSE IS NOT
PERMITTED Related reference
ALTER TABLESPACE (Db2 SQL)
Explanation ALTER TABLE (Db2 SQL)
A clause was used where it is not permitted. -110 INVALID HEXADECIMAL

clause-type CONSTANT BEGINNING constant
The type of clause.
The error can be issued for reasons that include the Explanation
following: The string constant that begins with the specified
• An ALTER TABLESPACE statement with a LOGGED or string is invalid because it has at least one of the
NOT LOGGED clause was specified for an XML table following errors:
space. • the string constant contains one or more characters
• An ALTER TABLE statement specified an ALTER that are not valid hexadecimal digits
PARTITION clause, a ROTATE PARTITION clause, or • the string constant does not have an even number of
an ADD PARTITION clause to insert a partition for a digits
table that contains an XML column.
• for a UX or GX string constant, the number of digits is
not a multiple of 4

Related concepts
Programmer response Aggregate functions (Db2 SQL)
Correct the invalid string constant.
-113 INVALID CHARACTER FOUND IN:
string, REASON CODE nnn
SQLSTATE
42606 Explanation
-111 AN AGGREGATE FUNCTION DOES The string contains an invalid character. It can be an
NOT INCLUDE A COLUMN NAME SQL ordinary identifier name, a host variable name, or
a DBCS comment.
Explanation Certain SQL identifiers (for example names of buffer
The specification of an aggregate function was invalid pools, databases, and plans) must contain only
because a column name was not specified in the uppercase alphabetic or national characters and
argument. In a trigger definition, a transition variable numerics; the first character must be alphabetic or
specification does not qualify as a column name for national.
this purpose. The following reason codes apply to SBCS identifiers:
000
System action An invalid character was found in the SBCS
identifier (including the case in which a DBCS
The statement cannot be executed.
identifier was used where only an SBCS identifier is
allowed.)
Programmer response
The following reason codes apply to DBCS identifiers
Refer to Aggregate functions (Db2 SQL) for information or comments:
about the proper usage of aggregate functions.
101
An odd number of bytes exists between the shift-
SQLSTATE out and the shift-in character.
42901 102
Either a shift-in or shift-out character is missing.
-112 THE OPERAND OF AN AGGREGATE
FUNCTION INCLUDES AN 103
AGGREGATE FUNCTION, AN OLAP DBCS blanks X'4040' are not allowed.
SPECIFICATION, OR A SCALAR 104
FULLSELECT There are no characters between the shift-out and
the shift-in characters.
Explanation 105
Shift-out cannot be the first byte of the DBCS
The operand of an aggregate function can be either character between the shift-out and the shift-in
an expression or DISTINCT followed by an expression. characters.
The operand cannot be another aggregate function, an
OLAP specification, or a scalar fullselect.
System action
System action Processing is terminated.
User response
Programmer response Correct the name.
Correct the use of the aggregate function to eliminate
the invalid expression and reissue the statement. SQLSTATE
42602

-114 THE LOCATION NAME location BY ANY OR ALL WITHOUT A
DOES NOT MATCH THE CURRENT SUBQUERY
SERVER
Explanation
Explanation A simple comparison like '>' must not be followed by
A 3-part SQL procedure name was provided for one of a list of items. ANY and ALL comparisons must be
the following SQL statements: followed by a subselect, rather than an expression or a
list of items.
ASSOCIATE LOCATORS
CALL
DESCRIBE PROCEDURE System action
The first part of the SQL procedure name, which The statement cannot be processed.
specifies the location where the stored procedure
resides, did not match the value of the SQL CURRENT Programmer response
SERVER special register.
Correct the SQL statement.
System action
SQLSTATE
42601
Programmer response Related concepts
Predicates (Db2 SQL)
Take one of these actions to resolve the mismatch:
Language elements (Db2 SQL)
• Change the location qualifier to match the CURRENT Related reference
SERVER special register.
• Issue an SQL CONNECT to the location where the
stored procedure resides before issuing the SQL -117 THE NUMBER OF VALUES
statement. Ensure that the SQL CALL statement ASSIGNED IS NOT THE SAME AS
is issued before the ASSOCIATE LOCATORS or THE NUMBER OF SPECIFIED OR
DESCRIBE PROCEDURE. IMPLIED COLUMNS
• Bind the package containing the 3-part
SQL procedure name with the BIND option Explanation
DBPROTOCOL(DRDA). With this option, Db2
implicitly uses the DRDA protocol for remote access The number of insert values in the value list of the
to the stored procedure. insert operation is not the same as the number of
object columns specified. Alternatively, the number of
• Correct the statements so that the exact syntax values on the right side of an assignment in a SET
used to specify the procedure name on the CALL assignment statement or the SET clause of an update
statement be the same as that on the ASSOCIATE operation does not match the number of columns on
LOCATOR and/or DESCRIBE PROCEDURE. If an the left side.
unqualified name is used to CALL the procedure,
the 1-part name must also be used on the other
statements. If the CALL statement is made with a System action
3-part name, and the current server is the same The statement cannot be processed. No data was
as the location in the 3-part name, the ASSOCIATE inserted into the object table.
LOCATOR or DESCRIBE procedure can omit the
location.
Programmer response
SQLSTATE Correct the statement to specify one and only one
value for each of the specified object columns.
42961
-115 A PREDICATE IS INVALID SQLSTATE
BECAUSE THE COMPARISON
OPERATOR operator IS FOLLOWED 42802
BY A PARENTHESIZED LIST OR

-118 THE OBJECT TABLE OR VIEW System action
OF THE DELETE OR UPDATE
STATEMENT IS ALSO IDENTIFIED The statement cannot be processed.
IN A FROM CLAUSE
Programmer response
Explanation The implied function is not supported by Db2.
The table or view specified as the object of a DELETE
or UPDATE statement also appears in the FROM clause SQLSTATE
of a subselect within the statement.
42803
The table or view that is the object of a UPDATE or
Related concepts
DELETE cannot also be used to supply the values to
be inserted or to qualify the rows to be updated or Queries (Db2 SQL)
deleted. Related reference
group-by-clause (Db2 SQL)
System action having-clause (Db2 SQL)
The statement cannot be processed. No data was -120 AN AGGREGATE FUNCTION OR

updated or deleted. OLAP SPECIFICATION IS NOT
VALID IN THE CONTEXT IN WHICH
Programmer response IT WAS INVOKED
Create a temporary copy of the object table or view,

and perform the subselect on that copy. Explanation
An aggregate function, a user-defined function that
SQLSTATE is sourced on an aggregate function, or an OLAP
specification is not permitted in the following contexts:
42902
• In a SET clause.
Related reference
• In a VALUES clause.
DELETE (Db2 SQL)
• In a SET transition-variable statement.
UPDATE (Db2 SQL)
Statements (Db2 SQL) • In an assignment statement.
from-clause (Db2 SQL) • In the key-expression of an index definition.
• In the expression of a RETURN statement.
-119 A COLUMN OR EXPRESSION IN A
HAVING CLAUSE IS NOT VALID An aggregate function or an OLAP specification can
only be specified in a WHERE clause if the WHERE
clause appears within a subquery of a HAVING clause.
Explanation
The search-condition of the ON clause of a MERGE
A column or expression identified in a HAVING clause, statement cannot contain an expression that uses an
possibly within a scalar function, does not appear aggregate function.
in the GROUP BY clause. Columns or expressions
specified in a HAVING clause must appear within
aggregate functions or also be specified in the GROUP System action
BY clause. The statement cannot be processed.
Grouping expressions can be used in a SELECT list or
in a search condition in a HAVING clause. A grouping Programmer response
expression specifies only one value for each group.
A grouping expression specified in this context must Change the statement so that the aggregate function
exactly match a grouping expression specified in the or OLAP specification is not specified in a context
GROUP BY clause, with the exception of blanks, which where it is not allowed.
are not significant.
This message is also issued when an expression SQLSTATE
starting with GROUPING is specified in a SELECT 42903
clause, and a GROUP BY clause is not specified.

Related concepts Explanation
Queries (Db2 SQL)
The SELECT statement contains one of these errors:
Aggregate functions (Db2 SQL)
Related reference • The statement contains a column name and an
aggregate function in the SELECT clause, but no
where-clause (Db2 SQL)
GROUP BY clause.
having-clause (Db2 SQL)
• A column name is contained in the SELECT clause
VALUES INTO (Db2 SQL)
(possibly within a scalar function) but not in the
SET assignment-statement (Db2 SQL) GROUP BY clause. Grouping expressions can be
RETURN statement (Db2 SQL) used in a SELECT list. A grouping expression
RETURN statement (Db2 SQL) specifies only one value for each group. A grouping
OLAP specification (Db2 SQL) expression that is specified in this context must
exactly match a grouping expression that is specified
-121 THE TARGET name IS IDENTIFIED in the GROUP BY clause, except that blanks are not
MORE THAN ONCE FOR significant.
ASSIGNMENT IN THE SAME SQL
STATEMENT Attention: A HAVING clause specified
without a GROUP BY clause implies a GROUP
BY with no columns. Thus, no column names
Explanation are allowed in the SELECT clause.
The same name is specified more than once as a target • An expression is specified in the SELECT clause but
for an assignment. not in the GROUP BY clause.
name • A sort-key-expression was specified in the ORDER
The name of the target of the assignment. BY clause, the result table contains grouped data,
but the select-clause and ORDER BY clause contain
This situation can occur when a target name is
a mixture of grouped data and non-grouped data.
specified more than once in any of the following
Grouping expressions can be used in a sort-key-
contexts:
expression of an ORDER BY clause. A grouping
• In the list of object columns of a data change expression specifies only one value for each group. A
operation grouping expression that is specified in this context
• In the SET clause of an update operation must exactly match a grouping expression that is
specified in the GROUP BY clause, except that blanks
• In the SET statement for assignment to a transition are not significant.
variable
This error can also occur during an update or insert System action
operation on a view, when one column of the view is
based on the same column of a base table. The statement cannot be processed.

The statement cannot be processed. No data was You can correct the statement by:
assigned. • Including the columns or expressions in the GROUP
BY clause that are in the SELECT clause, or
Programmer response • Removing the columns or expressions from the
Correct the syntax of the statement so that each target SELECT clause.
name is specified only once.
SQLSTATE
SQLSTATE 42803
42701 Related concepts
-122 COLUMN OR EXPRESSION IN THE Queries (Db2 SQL)
SELECT LIST IS NOT VALID Related reference
select-clause (Db2 SQL)

order-by-clause (Db2 SQL) Explanation
-123 THE PARAMETER IN POSITION n The SELECT statement in the declaration for a cursor
IN THE FUNCTION name MUST BE contains both an UPDATE clause and an ORDER BY
A CONSTANT OR KEYWORD clause. Unless you use a static sensitive scrollable
cursor, an ORDER BY clause cannot be specified in the
declaration for a cursor that is to be used for UPDATE.
Explanation
The parameter in position n in the function name is not System action
a constant when it is required to be a constant or a
keyword when it is required to be a keyword. The statement cannot be processed. The cursor
remains undefined in the application program.
System action
Programmer response
The implied function is not supported by Db2. A cursor
that is to be used for update cannot be defined to fetch
Programmer response the rows of the object table in a specific order.
Action: Ensure that each argument of the function
conforms to the definition of the corresponding SQLSTATE
parameter.
42829
SQLSTATE Related concepts
Queries (Db2 SQL)
42601
Related reference
-125 AN INTEGER IN THE ORDER BY update-clause (Db2 SQL)
CLAUSE DOES NOT IDENTIFY A order-by-clause (Db2 SQL)
COLUMN OF THE RESULT
DECLARE CURSOR (Db2 SQL)
Explanation -127 DISTINCT IS SPECIFIED MORE

THAN ONCE IN A SUBSELECT
The ORDER BY clause in the statement contains a
column number that is either less than one, or greater
than the number of columns of the result table (the Explanation
number of items in the SELECT clause).
The DISTINCT qualifier can be used only once in a
SELECT statement or a subselect.
System action
The statement cannot be processed. System action
Programmer response
Correct the syntax of the ORDER BY clause such that Programmer response
each column identifier properly denotes a column of
The implied function is not supported by Db2.
the result table.
SQLSTATE
SQLSTATE
42905
42805
Related concepts
-126 THE SELECT STATEMENT
Queries (Db2 SQL)
CONTAINS BOTH AN UPDATE
CLAUSE AND AN ORDER BY Related reference
CLAUSE select-clause (Db2 SQL)
subselect (Db2 SQL)
-128 INVALID USE OF NULL IN A

PREDICATE

The use of NULL in the search condition does not The ESCAPE character must be a single character,
conform to the rules of SQL syntax. either SBCS or DBCS as appropriate. For 'column-
name LIKE pattern', the ESCAPE character can only
System action appear in the character string if it is followed by itself,
%, or _ (underscore). The Escape Clause cannot be
The statement cannot be processed. specified if the column name at the left of the LIKE or
NOT LIKE has the MIXED subtype.
Programmer response
System action
The implied function is not supported by Db2.
SQLSTATE
Programmer response
42601
Correct the string pattern, or choose a different
Related concepts
ESCAPE character and change the pattern accordingly,
Predicates (Db2 SQL) or eliminate the use of the Escape Clause on the LIKE
Language elements (Db2 SQL) or NOT LIKE predicate where the column name to the
left has the MIXED subtype.
-129 THE STATEMENT CONTAINS TOO
MANY TABLE NAMES
SQLSTATE
Explanation 22019 if other than invalid ESCAPE pattern. 22025 if
invalid ESCAPE pattern.
A subselect (including all subqueries) can have a
maximum of 225 references to table names. -131 STATEMENT WITH LIKE
PREDICATE HAS INCOMPATIBLE
DATA TYPES
System action
The statement cannot be processed. Explanation
If the column name at the left of LIKE or NOT LIKE
Programmer response is of type character, the expression at the right and
Break the SQL statement into two or more simpler the ESCAPE character must be of type character. If
statements with less than 225 table references in the column name is of type graphic, the expression
each. The count will include the number of base table at the right and the ESCAPE character must be of
occurrences from each table or view on the FROM list. type graphic. If the column data type is binary string,
the expression on the right and the ESCAPE character
must be binary strings.
SQLSTATE
54004 System action
Related concepts
Queries (Db2 SQL)
Related reference
Programmer response
subselect (Db2 SQL)
Limits in Db2 for z/OS (Db2 SQL) Check the data type of every operand.
-130 THE ESCAPE CLAUSE CONSISTS SQLSTATE

OF MORE THAN ONE
CHARACTER, OR THE STRING 42818
PATTERN CONTAINS AN INVALID -132 AN OPERAND OF value IS NOT
OCCURRENCE OF THE ESCAPE VALID
CHARACTER

Explanation – A CAST specification whose arguments are any of
the above
The operation value can be the LIKE predicate,
the ESCAPE clause, the LOCATE scalar function, the A LIKE predicate, ESCAPE clause, LOCATE
LOCATE_IN_STRING scalar function, the POSITION scalar function, LOCATE_IN_STRING scalar function,
scalar function, or the POSSTR scalar function. The POSITION scalar function, or POSSTR scalar function
operand or argument of value was not valid for one of cannot be used with DATE, TIME, or TIMESTAMP.
the following reasons:
• The match-expression operand of a LIKE or NOT System action
LIKE predicate must be a string expression. The statement cannot be processed.
• The pattern-expression operand of the LIKE or
NOT LIKE predicate, or search-string argument of Programmer response
the LOCATE, LOCATE_IN_STRING, POSITION, or
POSSTR function must be a string expression that Check and correct the syntax of the LIKE predicate, or
can be specified by any one of the following: LOCATE, LOCATE_IN_STRING, POSITION, or POSSTR
scalar function.
– A constant
– A special register
SQLSTATE
– A variable
42824
– An array element specification
Related reference
– A scalar function whose arguments are any of the
above (though nested function invocations cannot LIKE predicate (Db2 SQL)
be used) LOCATE (Db2 SQL)
– A CAST specification whose arguments are any of LOCATE_IN_STRING (Db2 SQL)
the above POSITION (Db2 SQL)
– An expression that concatenates (using CONCAT POSSTR (Db2 SQL)
or ||) any of the above
-133 AN AGGREGATE FUNCTION IN
• The source-string argument of the LOCATE, A SUBQUERY OF A HAVING
LOCATE_IN_STRING, POSITION, or POSSTR CLAUSE IS INVALID BECAUSE
function must be a string expression that can be ALL COLUMN REFERENCES IN
specified by any of the following: ITS ARGUMENT ARE NOT
– A constant CORRELATED TO THE GROUP
BY RESULT THAT THE HAVING
– A special register CLAUSE IS APPLIED TO
– A host variable (including a LOB locator variable)
– A scalar function whose arguments are any of the Explanation
above (though nested function invocations cannot
be used) If an aggregate function has a correlated column
reference, it must be correlated from within a HAVING
– A CAST specification whose arguments are any of clause to the GROUP BY result that the HAVING clause
the above is applied to. All column references in the argument
– A column name must satisfy this condition.
– An expression that concatenates (using CONCAT
or ||) any of the above System action
• The escape-expression operand of the LIKE or NOT The statement cannot be processed.
LIKE predicate must be a string expression that can
be specified by any of the following:
Programmer response
– A constant
Correct the syntax of the HAVING clause.
– A host variable (including a LOB locator variable)
– A scalar function whose arguments are any of the
SQLSTATE
above (though nested function invocations cannot
be used) 42906

Related concepts A token might be returned with the name of the
Queries (Db2 SQL) column or special register that resulted in the error.
Related reference The nature of the error and the syntax in which it
occurred determines whether a token is returned.
having-clause (Db2 SQL)
System action
-134 IMPROPER USE OF A STRING, The statement cannot be processed.
LOB, XML, OR ARRAY VALUE
Programmer response
Explanation
Db2 does not support the requested operation on the
The SQL statement references a string, LOB, XML string, LOB, or XML value.
value, or an array with elements that are defined
as LOBs, that is not valid in the context that was
specified. SQLSTATE
This error can be issued when the length attribute of 42907
a string value is too long for the context in which it is Related concepts
used. The string value that you specified is invalid for
String representations of numeric values (Db2
one of the following reasons:
SQL)
• A string value with a length attribute greater than Related reference
255 bytes is not allowed in a SELECT list that also REPLACE (Db2 SQL)
specifies DISTINCT.
order-by-clause (Db2 SQL)
• A string value with a length attribute greater than CREATE TABLE (Db2 SQL)
255 bytes is not allowed for a string representation
of a number.
• A string value with a length attribute greater than -136 SORT CANNOT BE EXECUTED
16000 bytes is not allowed for a sort operation such BECAUSE THE SORT KEY LENGTH
as an ORDER BY clause. TOO LONG
• A string value with a length attribute greater than
32704 bytes is not allowed as an argument to the Explanation
REPLACE function.
A sort key is derived from the list of columns specified
This error can also be issued when: following a DISTINCT keyword, or in an ORDER BY
• LOB or XML values are specified in a context in which or GROUP BY clause in a query. If both a DISTINCT
they are not allowed. The LOB or XML value that you keyword and an ORDER BY or GROUP BY clause are
specified is invalid for one of the following reasons: present, the sort key is derived from the combination
of both lists of columns.
– A LOB or an XML value is not allowed in an ORDER
BY clause. The internal length of the sort key cannot exceed
16000 bytes. In attempting to process the SQL
– A LOB or an XML value is not allowed in a check statement, the internal length of the sort key derived
constraint. from the DISTINCT and ORDER BY (or GROUP BY),
• An array type with LOB elements is specified in a or, the DISTINCT or ORDER BY (or GROUP BY)
context in which it is not allowed. The array type specifications was found to exceed that maximum
that you specified is invalid for one of the following limit.
reasons:
The error can also occur for an ORDER BY specification
– The array type that was specified is invalid for the XMLAGG function. The internal length of the
because an array type with LOB elements is not sort key for XMLAGG cannot exceed 4000 bytes.
allowed as a parameter data type for a procedure In attempting to process the XMLAGG function
defined with the AUTONOMOUS option. invocation, the internal length of the sort key derived
– The ARRAY_AGG function returned an array of from the ORDER BY specification was found to exceed
LOBs, and the query in which ARRAY_AGG was that maximum limit.
invoked also contained a GROUP BY clause.

System action • The value of the third argument of the SUBSTR or
SUBSTRING function is an integer constant 0 or
The statement cannot be processed. greater than M-N+1.
M is the length of the first argument if it is of fixed-
User response length, or, M is the maximum length of the first
The statement must be modified such that the internal argument if it is of varying-length. N is the value of
length of the sort key does not exceed the maximum the second argument.
limit. In general, this means that one or more column
names must be deleted from the ORDER BY or GROUP System action
BY clause, or deleted from the list following the
DISTINCT keyword. The statement cannot be processed.

54005 Ensure that the second and third arguments of the
SUBSTR or SUBSTRING function have legal values
-137 THE LENGTH RESULTING FROM according the rules listed in the Explanation.
operation IS GREATER THAN
maximum-length
SQLSTATE
Explanation 22011
The length of the result of concatenation or a function -142 THE SQL STATEMENT IS NOT
exceeds the defined maximum. The operation that SUPPORTED
resulted in the error is operation.
• For concatenation, the length cannot exceed 32,764 Explanation
(if character operands) or 16,382 (if graphic An SQL statement was detected that is not supported
operands). by the database. The statement might be valid for
• For other functions, check the maximum result other IBM relational database products or it might be
length. valid in another context. For example, statements such
as VALUES and SIGNAL or RESIGNAL SQLSTATE can
be used only in certain contexts, such as in a trigger
System action
body or in an SQL Procedure.
System action
Programmer response
Ensure that the length of the result does not exceed
the defined maximum. Programmer response
Change the syntax of the SQL statement or remove the
SQLSTATE
statement from the program.
54006
Related reference SQLSTATE
Limits in Db2 for z/OS (Db2 SQL) 42612
-138 THE SECOND OR THIRD -144 INVALID SECTION NUMBER
ARGUMENT OF THE SUBSTR OR number
SUBSTRING FUNCTION IS OUT OF
RANGE Explanation
One of the following:
Explanation
• The user attempted to execute an invalid section.
One of the following conditions exists:
• This release of Db2 does not support the SQL
• The value of the second argument of the SUBSTR or statement.
SUBSTRING function is less than 1 or greater than M.

• The section number in the call parameter list is one way. In general, you should not attempt to change the
of these: output of the precompiler.
– Negative
– An invalid duplicate
SQLSTATE
– Greater than the maximum section number of the 58003
DBRM or package -147 ALTER FUNCTION function-name
FAILED BECAUSE SOURCE
System action FUNCTIONS OR SPATIAL
FUNCTIONS CANNOT BE ALTERED
Explanation
Programmer response
The function cannot be altered because it is a source
For case 1: If you are executing a package that
function or a spatial function. Only fenced external
was bound with SQLERROR(CONTINUE), determine
scalar functions, or fenced external table functions can
whether the statement in question was bound as a
be altered.
valid section. You can use the following statements to
query the Db2 catalog: To change an existing source function or spatial
function, you must DROP the function and re-create
SELECT SQLERROR it.
FROM SYSIBM.SYSPACKAGE
WHERE COLLID = collection-id AND
NAME = package-id AND
VERSION = version-name; System action
If that query returns 'C', the package was bound with
SQLERROR(CONTINUE).
Programmer response
SELECT STMTNO, TEXT
FROM SYSIBM.SYSPACKSTMT Change the statement to refer to a function that can
WHERE COLLID = collection-id AND
NAME = package-id AND
be altered, or re-create the function by dropping it and
VERSION = version-name AND then creating a new version of it.
SECTNO = number AND
BINDERROR = 'Y';
SQLSTATE
If that query returns any rows, the section is invalid.
Refer to the error messages issued during the bind to 42917
determine the cause. Correct any errors and bind the -148 THE SOURCE TABLE OR
package again, using the REPLACE option. TABLESPACE source-name
For case 2: If the Db2 system has fallen back to a CANNOT BE ALTERED, REASON
previous release, determine whether there are any reason-code
SQL statements with a section number of zero that
are not supported by that release. You can use the Explanation
following statements to query the Db2 catalog.
The ALTER statement issued could not be processed.
When executing from a DBRM, use:
source-name
SELECT * The name of the source table or table space.
FROM SYSIBM.SYSSTMT
WHERE SECTNO = 0 reason-code
ORDER BY NAME, PLNAME, STMTNO, SEQNO; The reason for the message or SQL code, indicated
by one of the following values:
When executing from a package, use:
01
SELECT * The ALTER statement specified an ALTER
FROM SYSIBM.SYSPACKSTMT COLUMN clause that attempted to drop the
WHERE SECTNO = 0
ORDER BY COLLID, NAME, VERSION, STMTNO, SEQNO; default value, alter the default value, or change
the length of the column. The column cannot
For case 3: Examine the application to determine be altered because the column has a field
whether the call parameter list was changed in some procedure or is involved in a referential or
check constraint. The default value cannot

be changed because the column has a field was created with DEFINE NO, and the data set
procedure. is not yet defined.
02 An auxiliary object for a source table with a
The ALTER statement specified an ALTER LOB or XML column was created with DEFINE
COLUMN clause that attempted to drop the NO, and the data set is not yet defined
default value, alter the default value, or change
the length of the column. The column cannot 11
be altered because the table that is identified The ALTER statement attempted to change a
by source-name might be one of the following: table that has a defined clone, or a table that is
a clone.
• A table that has an edit procedure or
12
validation procedure.
The ALTER statement cannot be used to define
03 a clone table because table source-name is
The ALTER statement specified an ALTER defined with an edit procedure, validation
COLUMN clause that attempted to drop procedure, or field procedure.
the default value, alter the default value, 13
or alter the data type of the column. The ALTER statement cannot be processed
The column cannot be altered because because an index exceeds versioning limit of
the table is defined with DATA CAPTURE 16.
CHANGES and the subsystem parameter
RESTRICT_ALT_COL_FOR_DCC is set to YES. 14
An ALTER statement with an ALTER COLUMN
04 clause attempted to change the data type from
The ALTER statement cannot be used to define character FOR BIT DATA to BINARY, but the
a clone table because a clone table is already cast default value length exceeds 1536 UTF-8
defined for source-name. bytes.
05 15
The ALTER statement cannot be used to define The ALTER statement cannot be processed
a clone table because table source-name is because no pending changes are associated
not in a universal table space or it is in a with the table space.
table space that is defined with PAGENUM
RELATIVE. 16
An ALTER TABLESPACE statement cannot
06 include the MEMBER CLUSTER YES option for
The ALTER statement cannot be used to define hash-organized table space.
a clone table because table source-name is
involved in a referential or check constraint. 17
07 a clone table because table source-name is
The ALTER statement cannot be used to define hash-organized.
a clone table because table source-name has
an after trigger defined on it. 18
The ALTER statement cannot be processed
08 because Db2 11 Unicode columns in EBCDIC
The ALTER statement cannot be used to define tables can only be altered by specifying the
a clone table because table source-name is a same data type, length, and CCSID as were
materialized query table. specified when the column was originally
09 defined with a CREATE or ALTER TABLE
The ALTER statement cannot be used to define statement. The alteration migrates the column
a clone table because table source-name has definitions for Db2 11 Unicode columns to Db2
more than one table space version or index 12 or later Unicode columns. The migration to
version in use. Db2 12 or later Unicode columns is available
10 beginning with the activation of function level
Either of the following reasons: 500 or higher. For more information, see
Unicode columns in EBCDIC tables (Db2 SQL).
a clone table because table space of table 19
source-name or an index on table source-name The ALTER statement attempted to define or
change a key label for a clone table.

System action 13
Reduce the number of versions for the index, then
The statement cannot be processed. issue the ALTER statement again.
14
Programmer response Either reduce or drop the default value. To alter the
Change source-name to the name of an object that can default value, use an ALTER TABLE statement with
be altered as specified and reissue the statement, or ALTER COLUMN SET DEFAULT. To drop the default
take an appropriate action for the reason-code value: value, use an ALTER TABLE statement with ALTER
COLUMN DROP DEFAULT.
01
15
Do not attempt to change source-name to the
Avoid altering a table space to drop the pending
name of an object that can be altered as specified
changes that do not exist.
and reissue the statement.
16
02
Do not attempt to add the MEMBER CLUSTER YES
Do not attempt to change a column that is defined
option for a hash-organized table space.
with an edit procedure or valid procedure.
17
03
Do not attempt to define a clone table for a hash-
Do not attempt to change or drop the
organized table.
default value, or change the data type of a
column when the table is defined with DATA 18
CAPTURE CHANGES and the subsystem parameter Do not attempt to alter a Db2 11 Unicode column
RESTRICT_ALT_COL_FOR_DCC is set to YES. in an EBCDIC table.
04 19
Before defining a clone table, verify that there is no Do not attempt to define or change a key label for
clone table already defined for source-name. a clone table. The key label is inherited from the
05 base table.
Before defining a clone table, verify that table
source-name is in a universal table space. SQLSTATE
06 42809
source-name is not involved in a referential or Related concepts
check constraint. Unicode columns in EBCDIC tables (Db2 SQL)
07 Related reference
Before defining a clone table, verify that table ALTER TABLE (Db2 SQL)
source-name does not have any AFTER triggers
defined on it. -150 THE OBJECT OF THE INSERT,
DELETE, UPDATE, MERGE, OR
08
TRUNCATE STATEMENT IS A
VIEW, SYSTEM-MAINTAINED
source-name is not a materialized query table.
MATERIALIZED QUERY TABLE, OR
09 TRANSITION TABLE FOR WHICH
Before defining a clone table, verify that table THE REQUESTED OPERATION IS
source-name does not have more than one table NOT PERMITTED
space version or index version in use.
10 Explanation
Before defining a clone table, verify that the data
sets for source-name and its indexes are defined. One of the following occurred:
11 • A transition table was named in an INSERT, UPDATE,
Drop the clone table, then alter the column. Use DELETE, MERGE, or TRUNCATE statement in a
an ALTER TABLE statement with the DROP CLONE triggered action. Transition tables are read-only.
clause. • The view named in the INSERT, UPDATE, DELETE,
12 MERGE, or TRUNCATE statement is defined in such
Before defining a clone table, verify that table a way that the requested insert, update, delete, or
source-name does not have an edit procedure, truncate operation cannot be performed upon it.
valid procedure, or field procedure.

Inserts into a view are prohibited if: Related reference
– The view definition contains a join, a GROUP BY, or Statements (Db2 SQL)
a HAVING clause. INSERT (Db2 SQL)
– The SELECT clause in the view definition contains UPDATE (Db2 SQL)
the DISTINCT qualifier, an arithmetic expression, DELETE (Db2 SQL)
a string expression, a built-in function, or a MERGE (Db2 SQL)
constant. TRUNCATE (Db2 SQL)
– Two or more columns of the view are derived from
the same column. -151 THE UPDATE OPERATION IS
INVALID BECAUSE THE CATALOG
– A base table of the view contains a column that DESCRIPTION OF COLUMN
does not have a default value and is not included column-name INDICATES THAT IT
in the view. CANNOT BE UPDATED
Updates to a view are prohibited if:
– The view definition contains a join, a GROUP BY, or Explanation
a HAVING clause. The requested function is not supported by Db2.
– The SELECT clause in the view definition contains
column-name
the DISTINCT qualifier or a built-in function.
The name of the column that could not be
Also, a given column in a view cannot be updated updated.
(that is, the values in that column cannot be
This error occurs if either:
updated) if the column is derived from an arithmetic
expression, a constant, a column that is part of the • The object column in an update operation is defined
key of a partitioned index, or a column of a catalog with the GENERATED ALWAYS and AS IDENTITY or
table that cannot be updated. AS ROW CHANGE TIMESTAMP attributes, its value is
not being set with the DEFAULT keyword, and one of
Deletes against a view are prohibited if:
the following conditions is true:
– The view definition contains a join, a GROUP BY, or
– Extended indicator variable values are not
a HAVING clause.
enabled.
– The SELECT clause in the view definition contains
– Extended indicator variable values are enabled,
the DISTINCT qualifier or a built-in function.
but the value specified for the indicator variable is
Truncates against a view are always prohibited. not the extended indicator variable-based values
• An auxiliary table or an XML table was named in a of DEFAULT or UNASSIGNED.
TRUNCATE statement. • The object column is not updatable.
A column is not updatable for one or more of the
System action following reasons:
The statement cannot be processed. No data was • The values for columns occurring in the partitioning
inserted, updated, deleted, merged, or truncated. key of a partitioned table cannot be updated.
• The object table is a view and the specified column
User response is defined (in the definition of the view) in such a way
that it cannot be updated.
The requested function cannot be performed on the
view. • The object table is a catalog table with no columns
that can be updated.
If the error occurred on a CREATE TRIGGER
statement, remove the INSERT, UPDATE, MERGE, or • The object column is a ROWID column.
DELETE reference to the transition table. • The specified column of catalog tables cannot be
updated because the column itself is not updatable.
SQLSTATE • The values for columns occurring in the hash key of a
table that is organized by hash cannot be updated.
42807
• The BUSINESS_TIME period in the table includes a
Related concepts column that was specified to be updated. A column
Db2 views (Introduction to Db2 for z/OS) of a BUSINESS_TIME period must not be modified
within a trigger body.

• The BUSINESS_TIME period in the table includes a UNIQUE KEY CONSTRAINT
column that was specified to be updated. A column The identified constraint must be a unique key
of a BUSINESS_TIME period must not be modified if constraint.
the data change statement includes a period clause.
Individual columns in a view cannot be updated for System action
The ALTER TABLE DROP statement cannot be
• The column is derived from an SQL function, an executed. No object was dropped.
arithmetic expression, or a constant.
• The column is defined for a column of an underlying Programmer response
view that cannot be updated.
Drop the existing object with the correct DROP clause
• The column is defined for a read-only view. of the ALTER TABLE statement.
• The column is defined for a column that is in the
partitioning key of a partitioned table. SQLSTATE
42809
System action
-153 THE STATEMENT IS INVALID
BECAUSE THE VIEW OR TABLE
updated in the object table or view.
DEFINITION DOES NOT INCLUDE
A UNIQUE NAME FOR EACH
Programmer response COLUMN
Correct the syntax and reissue the statement that
included the update operation. Explanation
You must specify a list of column names if the
SQLSTATE result table of the fullselect that is specified in the
CREATE VIEW, CREATE TABLE, or DECLARE GLOBAL
42808
TEMPORARY TABLE statement has duplicate column
Related reference names or an unnamed column (a column from a
MERGE (Db2 SQL) constant, function, or expression).
UPDATE (Db2 SQL)
update-clause (Db2 SQL) System action
The statement cannot be processed. The specified
-152 THE DROP clause CLAUSE IN THE
view or table was not created, or the declared
ALTER STATEMENT IS INVALID
temporary table was not declared.
BECAUSE constraint-name IS A
constraint-type
Programmer response
Explanation Correct the statement by providing a list of names for
the columns of the view or table.
The DROP clause of an ALTER TABLE statement
tried to drop a constraint that does not match the
constraint-type in the DROP clause. clause must SQLSTATE
identify an appropriate constraint-type as follows:
42908
REFERENTIAL CONSTRAINT
Related reference
The identified constraint must be a referential
constraint. CREATE TABLE (Db2 SQL)
CREATE VIEW (Db2 SQL)
CHECK CONSTRAINT
The identified constraint must be a check DECLARE GLOBAL TEMPORARY TABLE (Db2
constraint. SQL)
PRIMARY KEY CONSTRAINT
The identified constraint must be a primary key
-154 THE STATEMENT FAILED BECAUSE
constraint.
VIEW OR TABLE DEFINITION IS
NOT VALID

The view defined in the CREATE VIEW statement, the 42809
table defined in the CREATE TABLE statement, or the
Related reference
table declared in the DECLARE GLOBAL TEMPORARY
TABLE statement is not valid because the view or table Statements (Db2 SQL)
definition references a remote object.
-157 ONLY A TABLE NAME CAN BE
SPECIFIED IN A FOREIGN KEY
System action CLAUSE. object-name IS NOT THE
The statement cannot be processed. The specified NAME OF A TABLE.
object is not defined.
Explanation
Programmer response The indicated object was identified in a FOREIGN KEY
The implied function is not supported. clause of a CREATE or ALTER TABLE statement. A
FOREIGN KEY clause must identify a table.
SQLSTATE
System action
42909
Related reference
CREATE TABLE (Db2 SQL) Programmer response
DECLARE GLOBAL TEMPORARY TABLE (Db2 Correct the statement to specify a table name in the
SQL) foreign key clause.
-156 THE STATEMENT DOES NOT SQLSTATE

IDENTIFY A TABLE
42810
Explanation -158 THE NUMBER OF COLUMNS OR

ARGUMENTS SPECIFIED FOR
A statement that applies only to tables was issued, name IS NOT THE SAME AS THE
but no table was identified. The following statements NUMBER OF COLUMNS IN THE
apply only to tables: RESULT TABLE.
• ALTER TABLE
• CREATE INDEX Explanation
• CREATE MASK One of the following situations has occurred:
• CREATE PERMISSION • The number of column names that are specified for
• CREATE TRIGGER a view in a CREATE VIEW statement is not the same
as the number of elements that are specified in the
• DROP TABLE
SELECT clauses of the fullselect that follows. These
• LOCK TABLE elements might be column names, SQL functions,
Indexes and triggers can be defined only on tables. and expressions, for example.
• The number of column names that are specified for a
Additionally, a DROP TABLE statement cannot be used
table in a CREATE TABLE statement is not the same
to drop a clone table.
as the number of columns in the result table of the
fullselect that follows.
System action • The number of column names that are specified
The statement cannot be processed. in a correlation clause is not the same as the
number of columns in the corresponding table, view,
table expression, table function, data change table
Programmer response
reference, or UNNEST.
Correct the syntax, and reissue the statement. • The number of columns that are specified in the
RETURNS TABLE clause of a user defined table

function is not the same as the number of elements Programmer response
that are specified in the fullselect in the RETURN
statement. The fullselect can return zero or more Change the statement to match the type of object that
rows with one or more columns. The number of is identified by the expected-type value. For example:
columns in the fullselect must match the number of • An ALTER VIEW statement must reference an
columns in the function result. existing view.
• The number of column names that are specified in • A COMMENT ON ALIAS statement must specify the
a column list of a common table expression is not name of an alias, and not the name of a table or
the same as the number of elements specified in the view.
fullselect.
• A COMMENT ON TABLE statement must reference an
existing table or view.
System action • A CREATE INDEX statement with the UNIQUE
The statement cannot be processed. keyword must specify a table that is not a
materialized query table.
Programmer response • A CREATE INDEX statement must specify the name
of a table that is not a clone table.
Specify a column name for each column in the result,
and try the request again. • A CREATE TRIGGER statement must specify a table
in the ON clause that is not a materialized query
table. That is, a trigger cannot be defined for a
SQLSTATE materialized query table.
42811 • A CREATE TRIGGER statement must specify the
name of a table that is not a clone table.
Related reference
Statements (Db2 SQL) • A DROP ALIAS statement must specify the name of
an alias, and not the name of a table or view.
-159 THE STATEMENT REFERENCES • A DROP TABLE statement must reference an existing
object-name WHICH IDENTIFIES table. If an alias is specified, then the table that
AN actual-type RATHER THAN AN the alias refers to is dropped. Use the DROP ALIAS
expected-type statement to drop the alias.
• A DROP VIEW statement must reference an existing
Explanation view.
An object was specified as part of a statement, but the • A REFRESH TABLE statement must refer to a
actual type of the object is not the expected type. For materialized query table.
example, if the statement is DROP ALIAS TED.T1, then • A CREATE MASK or CREATE PERMISSION statement
TED.T1 must be an alias name. must name a base table that exists on the server.
object-name The table must not be an accelerator-only table, a
The name of the object. materialized query table, or a table with dependent
materialized query tables.
actual-type
The current type of the object. • The table-locator-reference must reference a table
name in the LIKE clause.
expected-type
The expected type of the object. • FL 508 An ALTER TABLESPACE statement with a
MOVE TABLE clause must identify a table that is to
If actual-type or expected-type is TABLE, and actual- be moved. A view must not be specified.
type or expected-type is a particular type of table, then
• A CREATE AUXILIARY TABLE statement with a
the type of table was not valid for the statement that
STORES clause must identify a base table. An
was specified.
auxiliary table, clone table, or view must not be
specified.
System action
The statement cannot be processed. SQLSTATE
42809

-160 THE WITH CHECK OPTION Programmer response
CLAUSE IS NOT VALID FOR THE
SPECIFIED VIEW Examine the view definition to determine why the
requested insert or update operation was rejected.
Note that this may be a data-dependent condition.
Explanation
The WITH CHECK OPTION clause does not apply to a SQLSTATE
view definition under the following circumstances:
44000
• The view is read-only (for example, the view
definition includes DISTINCT GROUP BY, or JOIN). -164 authorization-id DOES NOT HAVE
THE PRIVILEGE TO CREATE
• The view definition includes a subquery. A VIEW WITH QUALIFICATION
• The view definition includes a global variable. qualifier-name
• A view on which the specified view definition is
dependent has an INSTEAD OF trigger defined. Explanation
• The view definition references a table for which row An attempt was made to create a view, but the
or column access control is activated. authorization ID that was used lacks the authority
to create views with other qualifiers. Only an
System action authorization ID that holds SYSADM or system DBADM
authority can create views for other authorization IDs.
view was not created. authorization-id
The authorization ID that was used for the CREATE
VIEW statement.
Programmer response
qualifier-name
Correct the syntax of the WITH CHECK OPTION The qualifier that was specified in the CREATE
keyword in the CREATE VIEW statement. VIEW statement.

42813 The statement cannot be processed. The specified
Related reference view is not created.
Statements (Db2 SQL) Programmer response
Do not attempt to create views with other than your
-161 THE INSERT OR UPDATE IS NOT
own ID as a qualifier. The system DBADM privilege
ALLOWED BECAUSE A RESULTING
should be granted on any of the databases that contain
ROW DOES NOT SATISFY THE
at least one of the tables on which this CREATE VIEW
VIEW DEFINITION
is based. For the view to be created successfully,
system DBADM should have DATAACCESS authority or
Explanation select privilege on the tables on which this CREATE
VIEW is based.
The WITH CHECK OPTION applies to the view that
is the object of the insert or update operation.
Consequently, all attempts to insert or update rows in SQLSTATE
that view are checked to ensure that the results will
42502
conform to the view definition.
Related reference
System action SYSADM (Managing Security)
System DBADM (Managing Security)
The statement cannot be processed. No inserts
or updates were performed, and the contents of -170 THE NUMBER OF ARGUMENTS
the object view (and underlying base table) remain SPECIFIED FOR function-name IS
unchanged. INVALID

Explanation argument, or a graphic argument was specified for a
built-in function that expects a character argument.
An SQL statement includes a scalar function that The UNICODE encoding scheme supports the mixing
contains too many or too few arguments. of character and graphic arguments, but EBCDIC and
function-name ASCII do not.
The name of the function that contains the wrong If the function is a string function, this code might
number of arguments. be issued if a string unit was required but not
specified. The string unit keywords are CODEUNITS16,
System action CODEUNITS32, and OCTETS.
The statement cannot be processed. This error is issued when the RID function is invoked
with an unexposed name. An exposed name must be
used as the argument to the RID function.
Programmer response
If a parameter of the function is optional, the value of
Correct the statement. the argument-position token for SQLCODE -171 might
take into consideration the implicit argument.
SQLSTATE
For example, suppose that you invoke this function, in
42605 which parameter value '12' is invalid:
Related reference TRIM('12' FROM '123')
Scalar functions (Db2 SQL)
The first argument to the TRIM function, BOTH, is
-171 THE DATA TYPE, LENGTH, OR implicitly specified. Therefore, the value of argument-
VALUE OF ARGUMENT argument- position for parameter value '12' is 2.
position OF function-name IS
INVALID
SQLSTATE
Explanation 22546 if the error is encountered for an invalid format
for a BSON object; 42815 otherwise.
The data type, the length, or the value of an argument
Related concepts
of a scalar function is incorrect.
Application compatibility levels in Db2 (Db2
argument-position Application programming and SQL)
An integer that identifies the position of the Related reference
incorrect argument in the function invocation.
Scalar functions (Db2 SQL)
function-name
The name of the scalar function. -173 UR IS SPECIFIED ON THE WITH
This error can be issued for an attempt to use a feature CLAUSE BUT THE CURSOR IS NOT
that requires a higher APPLCOMPAT setting than the READ-ONLY
current setting. The current APPLCOMPAT setting does
not support a feature that was requested. Explanation
The cursor is not a read-only cursor. WITH UR can be
System action specified only if Db2 can determine that the cursor is
The statement that contains the function cannot be read-only.
processed.
System action
Programmer response Statement execution fails.
Correct the invocation of the function, and reissue the
statement. Programmer response
If the cursor is intended to be read-only but is
Problem determination ambiguous, add the FOR FETCH ONLY clause. If
If the encoding scheme is EBCDIC or ASCII, a possible the cursor is updatable, change the isolation level
reason for this error is that a character argument was specified on the WITH clause.
specified for a built-in function that expects a graphic

42801 The string representation of a datetime is not in the
acceptable range or is not in the correct format. The
-180 THE DATE, TIME, OR TIMESTAMP proper ranges for datetime values are as follows:
VALUE value IS INVALID
Table 2. Range of datetime values
Explanation Datetime Specific Cases Numeric Range
The length or string representation of a DATE, TIME,
Years 0001 - 9999
or TIMESTAMP value does not conform to any valid
format. Months 1 - 12
The value can contain one of the following: Days For months: 1 - 30
• For a host variable, the position number of the input • April (month 4)
host variable. If the position number cannot be
• June (6)
determined, a blank is displayed.
• September (9)
• For a character string constant, the character string
constant. The maximum length that is displayed is • November (11)
the length of SQLERRM.
For February 1 - 28 (Years
• For a character column, the column name. If the (month 2) other than leap
column is a VIEW column and it has a corresponding years.)
base column, the VIEW column name is displayed.
If the column is a VIEW column but it does not 1 - 29 (Leap
have a corresponding base column, a string of '*N' years only.)
is displayed.
For months: 1 - 31
Otherwise, value is a string of '*N'.
• January (month
1)
System action • March (3)
The statement cannot be processed. • May (5)
• July (7)
Programmer response • August (8)
Correct the program to ensure the specified value • October (10)
conforms to the syntax of DATE, TIME, and
• December (12)
TIMESTAMP.
Hours If the format for 0 - 12
SQLSTATE hours is USA
22007 For all other 0 - 24
predefined formats
Related concepts
Datetime values (Db2 SQL) Minutes 1 0 - 59
Date, time, and timestamp data types Seconds 1 0 - 59
(Introduction to Db2 for z/OS)
Related reference Fractional 0 - 999999
seconds 1
Dates, times, and timestamps for edit and
validation routines (Db2 Administration Guide) Time zone -12 - 14
hours
-181 THE STRING REPRESENTATION
OF A DATETIME VALUE IS NOT A Time zone 0 - 59
VALID DATETIME VALUE minutes

Table 2. Range of datetime values (continued) Explanation
Datetime Specific Cases Numeric Range The result of an arithmetic operation is a date or
timestamp that is not within the valid range of dates
Note: which are between 0001-01-01 and 9999-12-31.
1. When the hour format is not USA and the value
of the hour is 24, other parts of time values are System action
zeros.

The statement cannot be processed. Examine the SQL statement to see if the cause of
the problem can be determined. The problem may be
data-dependent, in which case it will be necessary to
Programmer response
examine the data that was processed at the time the
Check whether the value is within the valid range and error occurred.
is in the proper format. Correct the syntax, and reissue
the statement. SQLSTATE
22008
SQLSTATE
-184 AN ARITHMETIC EXPRESSION
22007
WITH A DATETIME VALUE
Related concepts CONTAINS A PARAMETER
Datetime values (Db2 SQL) MARKER
String representations of datetime values (Db2
SQL) Explanation
-182 AN ARITHMETIC EXPRESSION The specified arithmetic expression contains a
WITH A DATETIME VALUE IS parameter marker improperly used with a datetime
INVALID value.

The specified arithmetic expression contains an The statement cannot be processed.
improperly used datetime value or labeled duration.
Programmer response
System action Correct the indicated arithmetic expression.
SQLSTATE
Programmer response 42610
Correct the indicated arithmetic expression. -185 THE LOCAL FORMAT OPTION HAS
BEEN USED WITH A DATE OR TIME
SQLSTATE AND NO LOCAL EXIT HAS BEEN
INSTALLED
42816
-183 AN ARITHMETIC OPERATION ON Explanation
A DATE OR TIMESTAMP HAS A
RESULT THAT IS NOT WITHIN THE The local format option has been used with a datetime
VALID RANGE OF DATES value and no datetime exit has been installed. This
may occur if the LOCAL DATE LENGTH or LOCAL TIME
LENGTH on the Installation Application Programming
Defaults Panel indicated that an exit for datetime was
supplied, but in fact the exit supplied by Db2 was not
replaced. This may also occur if the datetime exit was

replaced and the corresponding LOCAL DATE LENGTH referenced CURRENT TIMEZONE, the MVS parameter
or LOCAL TIME LENGTH on the Installation Application PARMTZ was out of range.
Programming Defaults Panel was not set to a nonzero
value. System action
System action
For CURRENT TIMEZONE, check that the MVS
Programmer response
parameter PARMTZ is between -24 and +24 hours. For
Contact the system programmer about installation of the other CURRENT special registers, check that the
the date or time exit. MVS TOD clock has been set correctly.
SQLSTATE SQLSTATE
57008 22506
-186 THE LOCAL DATE LENGTH OR -188 THE STRING REPRESENTATION
LOCAL TIME LENGTH HAS BEEN OF A NAME IS INVALID
INCREASED AND EXECUTING
PROGRAM RELIES ON THE OLD Explanation
LENGTH
The host variable referenced in the DESCRIBE
statement does not contain a valid string
Explanation
representation of a name. One of the following error
The local format option has been used with a datetime conditions has occurred.
value and Db2 has discovered that the datetime exit
• The first byte of the variable is a period or a blank.
routine has been changed to produce a longer local
format. • The number of identifiers is greater than 3.
• An identifier is too long.
System action • A period not contained in a delimited identifier is
followed by a period or a blank.
• A delimited identifier is followed by a character other
than a period or a blank.
Programmer response
• A delimited identifier is not terminated by a
If the statement receiving this error is embedded in quotation mark.
the application program, then a REBIND command
must be issued for the application plan. If the
statement was dynamic SQL, then the statement can System action
be reentered. The statement cannot be processed.

22505 Correct the value of the host variable so that it is a
-187 A REFERENCE TO A CURRENT valid string representation of a name.
DATETIME SPECIAL REGISTER IS
INVALID BECAUSE THE MVS TOD SQLSTATE
CLOCK IS BAD OR THE MVS
22503
PARMTZ IS OUT OF RANGE
-189 CCSID ccsid IS INVALID
Explanation
Db2 has encountered an invalid time-of-day (TOD) Explanation
clock. The user referenced one of the special To determine the subtype of an input host variable
registers: CURRENT DATE, CURRENT TIME, CURRENT or result column, the SYSSTRINGS catalog table was
TIMESTAMP, or CURRENT TIMEZONE. If the user

accessed with the specified CCSID and, one of the Related tasks
following error conditions occurred: Setting up Db2 to ensure that it interprets
• The CCSID is not a value of either INCCSID or characters correctly (Db2 Internationalization
OUTCCSID. Guide)
Checking defined character conversions (Db2
• The TRANSTYPE column classifies the CCSID as
Internationalization Guide)
GRAPHIC rather than CHARACTER.
Related reference
• A graphic CCSID has not been specified on your
SYSSTRINGS catalog table (Db2 SQL)
system.
• The CCSID is outside the acceptable range of values. -190 THE ATTRIBUTES SPECIFIED FOR
The CCSID must be between 1 and 65533, inclusive, THE COLUMN table-name.column-
or the value 65535. name ARE NOT COMPATIBLE
• A DBCS CCSID was specified when casting to CHAR, WITH THE EXISTING COLUMN
VARCHAR or CLOB. DEFINITION
• An SBCS or mixed CCSID, or 65535 was specified
when casting to a graphic data type. Explanation
• CCSID 65535, which is valid only for data with the The attributes for the column in an ALTER TABLE
FOR BIT DATA attribute, was specified when casting statement are not compatible with the attributes of the
to a CLOB. existing column.
This error can occur when SYSSTRINGS is accessed table-name
with a pair of CCSIDs to determine if a translation The name of the table.
is defined for the pair. In this case, the error is the column-name
inconsistency between the data type of a string and The name of the column.
the TRANSTYPE classification of its CCSID (one is
GRAPHIC and the other is CHARACTER). Possible reasons for this error include:
This error can also occur when a CCSID specified in Incompatible data type
DECP does not exist as a value in the INCCSID or The ALTER TABLE ALTER COLUMN SET DATA
OUTCCSID columns of SYSSTRINGS. TYPE statement allows changing columns of the
following data types only:
Another reason this error can occur is that you may
be using one of the graphic built-in functions but • Character
a graphic CCSID was not specified during system • Numeric
installation.
• Binary
System action If the SET DATA TYPE clause was specified, the
existing column is not compatible with the new
The statement cannot be bound or executed. data type that was specified, or is of a data type
that cannot be changed.
Programmer response Identity column is required
Ensure that the CCSID is valid and consistent with the The following clauses can be specified only for a
data type of the string. If a valid CCSID is not listed column that is defined as an identity column:
in a built-in row of SYSSTRINGS, it can be defined • RESTART
by inserting a user-provided row. If a valid CCSID is
• SET GENERATED
misclassified in a user-provided row, that row can be
updated to correct the mistake. • SET INCREMENT BY
If a graphic CCSID had not been specified at system • SET MINVALUE and SET NO MINVALUE
installation, update your DECP to include a graphic • SET MAXVALUE and SET NO MAXVALUE
CCSID and recycle your Db2. • SET CYCLE and SET NO CYCLE
• SET CACHE and SET NO CACHE
SQLSTATE
• SET ORDER and SET NO ORDER
22522
If one of these clause was specified, the existing
column is not defined as an identity column.

Default values Programmer response
If a SET DEFAULT or DROP DEFAULT clause was
specified, the existing column either: If the string contains the intended information, the
description of the column or host variable should be
• Does not have a defined default value, or the changed from MIXED DATA to BIT or SBCS DATA. If the
column has NOT NULL as the null attribute. description of the column or host variable is correct,
• Is defined as an identity column, ROWID, or row the string is the problem and it must be changed to
change timestamp column. conform to the rules for well-formed mixed data.
Changing ROW BEGIN, ROW END, or TRANSACTION
START ID columns SQLSTATE
If ALTER COLUMN was specified to change 22504
the column to a ROW BEGIN, ROW END, or
TRANSACTION START ID column: Related concepts
Conversion rules for comparisons (Db2 SQL)
• The column is already defined as a generated
column. Mixed data in character strings (Db2 SQL)
Assignments involving mixed data strings (Db2
• The column is already defined with a user-
SQL)
specified default value. Issue an ALTER TABLE
statement to drop the default value. Then the Language elements (Db2 SQL)
column definition can be changed.
-195 LAST COLUMN OF table-name
CANNOT BE DROPPED
System action
table-name
Programmer response The name of the table.
Review the SQL statement and take the appropriate An attempt was made to drop a column using an
action, then resubmit the statement. ALTER TABLE statement. The column cannot be
dropped from the table table-name because at least
• Modify the statement so that the attributes that are
one of the existing columns must be preserved when
specified for the altered column are compatible with
altering a table.
the existing column definition.
• Remove the incompatible attribute specification.
System action
• Specify a different column.
SQLSTATE
Programmer response
42837
Ensure that the table, table-name, will have at least
Related reference one column after the ALTER statement is complete.
ALTER TABLE (Db2 SQL) If all of the columns should be removed, consider
dropping the table (and if necessary, create it again).
-191 A STRING CANNOT BE USED
BECAUSE IT IS INVALID MIXED
DATA SQLSTATE
42814
Explanation Related reference
The operation required the conversion of a mixed data ALTER TABLE (Db2 SQL)
character string to a different coded character set.
The string could not be converted because it does not -196 COLUMN table-name.column-name
conform to the rules for well-formed mixed data. CANNOT BE DROPPED. REASON =
reason-code.
System action

Explanation 15
An SQL table function is dependent on the
An attempt was made to drop the specified column, table, table-name.
but the column cannot be dropped for the indicated
reason.
System action
table-name
The name of the table. The statement cannot be processed.
column-name
The name of the column. Programmer response
reason-code Take the action that corresponds to the reason-code
A numeric value that indicates the reason that the value:
statement cannot be executed.
1
1
• If the column is part of a partitioning key, drop
The column cannot be dropped because it is
the table and create it again without the column
part of the hash key or partitioning key.
that needs to be dropped and redefine the
3 partitioning key.
The column cannot be dropped because it is a
• If the column is part of a hash key:
security label column.
4 1. Alter the table to remove the hash
The column cannot be dropped because it is organization.
part of a period. 2. Drop the column.
5 3. Run the REORG utility on the containing table
The column cannot be dropped because the space so the drop column operation takes
table is a system-period temporal table or effect.
archive-enabled table. 4. Alter the table to add the hash organization.
6
As an alternative, consider dropping the table
The column cannot be dropped because it is a
and creating it again without the column that
column in a history table or archive table.
needs to be dropped.
8
The table, table-name, is defined with an edit 3
procedure or validation procedure. Drop the table and create it again, without creating
the security label column.
9
The table, table-name, is referenced (directly 4
or indirectly) in the definition of a materialized Drop the table and create it again, without creating
query table. the column that needs to be dropped.
10 5
A check constraint is defined on the table, Alter the table to remove system-period data
table-name. versioning or disable archiving. (Issue ALTER
TABLE with the DROP VERSIONING or DISABLE
11 ARCHIVE clause.) Then drop the column from the
An extended index is defined on the table, table.
table-name.
If system-period versioning or archiving is still
12
needed, drop the column from the previously
A trigger is defined on the table, table-name,
associated history table or archive table. Then add
or an INSTEAD OF trigger is defined on a view
system-period data versioning or archiving back to
that is dependent on the table.
the table.
13
A row permission is dependent on the table, 6
table-name. Drop versioning or archiving so that the table
is no longer a history table or an archive table.
14 (Use the ALTER TABLE statement with the DROP
A column mask is dependent on the table, VERSIONING or DISABLE ARCHIVE clause on
table-name. the associated system-period temporal table or

archive-enabled table.) Then drop the column from System action
the table.
If versioning or archiving is still needed, drop the
column from the system-period temporal table
or archive-enabled table. Then add versioning or Programmer response
archiving back to this table. Change the statement to ensure that all column names
8 in the ORDER BY clause are unqualified.
If the table is defined with a validation procedure,
alter the table to remove the valid procedure and SQLSTATE
then drop the column. If the table is defined
with an edit procedure, drop the table and create 42877
it again without the column that needs to be -198 THE OPERAND OF THE PREPARE
dropped. OR EXECUTE IMMEDIATE
9 STATEMENT IS BLANK OR EMPTY
Drop any materialized query tables that reference
the table, then drop the column. Explanation
10
The operand (host variable or string constant) that was
Drop and check constraints that reference the
the object of the PREPARE or EXECUTE IMMEDIATE
table, then drop the column.
statement either contained all blanks or was an empty
11 string. A DBRM built in Version 2 Release 3 cannot
Drop any extended indexes that reference the be used on a Version 2 Release 2 system if the
table, then drop the column. distributive functions were used. If this error appears
12 on Version 2 Release 2 and the DBRM was built on
Drop any triggers that reference the table or Version 2 Release 3, then the program needs to be
dependent views, then drop the column. precompiled again to correct the problem.
13
Drop any row permissions that reference the table, System action
then drop the column.
14
Drop any column masks that reference the table,
Programmer response
then drop the column.
15 Correct the logic of the application program to ensure
Drop any SQL table functions that reference the that a valid SQL statement is provided in the operand
table, then drop the column. of the PREPARE or EXECUTE IMMEDIATE statement
before that statement is executed.
SQLSTATE
SQLSTATE
42817
42617
Related concepts
Archive-enabled tables and archive tables -199 ILLEGAL USE OF KEYWORD
(Introduction to Db2 for z/OS) keyword. TOKEN token-list WAS
EXPECTED
-197 A QUALIFIED COLUMN NAME IS
NOT ALLOWED IN THE ORDER BY Explanation
CLAUSE WHEN A SET OPERATOR
IS ALSO SPECIFIED A syntax error was detected in the statement at the
point where the keyword keyword appears.
Explanation As an aid to the programmer, a partial list of valid

tokens is provided in SQLERRM as token-list. Only
The ORDER BY clause of a fullselect that includes a those tokens that will fit are listed. Some tokens in
set operator, such as UNION, EXCEPT, or INTERSECT, the list might not be valid in statements to be executed
cannot have qualified column names. by Db2; those tokens are valid for sending to other
database management systems.

The statement cannot be processed. The object that is identified by name is not defined in
the Db2 subsystem. This SQLCODE can be generated
Programmer response for any type of Db2 object.
If the error was encountered for a particular version
Examine the statement in the area of keyword
of an object, the name token might return the version
keyword. A colon or SQL delimiter might be missing.
identifier. For example:
Verify that the clauses are in the correct order. If the
reserved word that is identified in the messages is name-of-procedure VERSION version-id
listed as a reserved word, make the word a delimited
identifier. For COMMENT or DROP, if the specified object is a
package, the implicitly or explicitly specified version
of the package is not defined in the Db2 subsystem.
SQLSTATE If the version-ID was not explicitly specified, the
42601 statement attempted to process the null version for
the identified package, but the null version does not
Related reference exist. The VERSION clause can be used to specify a
Reserved words (Db2 SQL) specific version to be processed.
-203 A REFERENCE TO COLUMN For CREATE FUNCTION, the name token can refer to
column-name IS AMBIGUOUS a built-in function that cannot be the source of a user-
defined function, or cannot be used as the source of a
user-defined function in certain conditions. For details,
Explanation see CREATE FUNCTION (sourced) (Db2 SQL).
An unqualified column name is ambiguous if more If the statement executes on an accelerator, the name
than one table or view identified in the FROM clause token can refer the name of a table on the accelerator
has a column with that name, or if more than one server instead of the name of the associated table on
column of a nested table expression has that name. Db2.
A qualified column name is ambiguous only if the
qualifier is the correlation name for a nested table System action
expression and the column name is not unique.
A reference to a column of the triggering table in a
CREATE TRIGGER statement is ambiguous if it does
not use the correlation name to indicate if it refers to Programmer response
the old or new transition variable. Verify that the object name was correctly specified in
the SQL statement, including any required qualifiers. If
System action it is correct, ensure that the object exists in the system
before resubmitting the statement.
Check the application compatibility value that is used
by your application to ensure that it is set properly. The
Programmer response behavior of the statement might change based on the
If the problem is caused by a nonunique column name application compatibility level.
in a nested table expression, change the nested table If the specified object is a routine, issue the
expression so that the column name is unique. If the CREATE PROCEDURE or CREATE FUNCTION statement
problem is caused by the use of an unqualified name, to define the routine to Db2. Issue the -START
qualify it with a table, view, or correlation name. PROCEDURE command to activate the new definition.
If the specified object is a package, issue the
SQLSTATE COMMENT or DROP statement with the VERSION
42702 clause to identify the specific version to be processed.
-204 name IS AN UNDEFINED NAME

SQLSTATE
42704
46002

-205 column-name IS NOT A COLUMN • The specified period is not a period of any of the
OF TABLE table-name source or target tables or views of the statement.
• The target of an assignment clause of an SQL data
Explanation change statement specified a name that is not a
column of the target table or view of the statement,
No column with the specified column-name occurs in or an INCLUDE column defined for the statement.
the table table-name. For a DELETE statement, the target of an assignment
clause can only be an INCLUDE column.
System action • The source of an assignment clause of an SQL data
The statement cannot be processed. change statement referenced an INCLUDE column
in an expression. A column defined in an INCLUDE
clause can only be specified as the target of an
Programmer response assignment in an SQL data change statement.
Verify that the column and table names are specified • A correlated reference to a column was specified for
correctly (including any required qualifiers) in the SQL a grouping expression, which is not allowed.
statement. • A column defined in the INCLUDE clause of an
UPDATE or DELETE statement was referenced in the
SQLSTATE WHERE clause of that statement.
42703 • The specified name is a correlated column reference
in a subselect, which is not allowed.
-206 object-name IS NOT VALID IN THE
• A VALUES clause of an SQL data change statement
CONTEXT WHERE IT IS USED
specified the name of a column of the target table,
which is not allowed.
Explanation • For a CREATE or ALTER FUNCTION statement, or a
An object is specified in a context where it is not valid. CREATE or ALTER PROCEDURE statement:
object-name – The specified name does not resolve to the name
The name of the object that could not be resolved. of a column or variable.
Possible reasons for this error include: – The specified name resolves to the name of a
variable that is not available in the current scope.
• The specified name is not a column of any of the
– The specified condition name name specified in
source or target tables or views of the statement.
the SIGNAL statement has not been declared.
– In a SELECT or DELETE statement, the specified • For a CREATE TRIGGER statement:
name is not a column of any of the tables or
views that are identified in a FROM clause in the – A reference is made to a name using an OLD or
statement. NEW correlation name for a transition variable.
The name is not defined as a column in the
– In an INSERT, UPDATE, or MERGE statement, the
triggering table.
specified name is not a column of the table, or
view that was specified as the target of the data – The target of an assignment in the triggered action
change statement. specified an old transition variable that is not valid
for the type of trigger.
– A column list of an SQL data change statement
specified a name that is not a column of the target – The referenced name does not resolve to the
table or view of the statement. name of a column or variable.
• A qualified column name was specified, but the table – The specified name resolves to the name of a
designator that is specified as the qualifier is not variable that is not available in the current scope.
defined in this context. – The specified condition name name specified in
• A correlated reference to a column was specified the SIGNAL statement has not been declared.
in an OLAP specification. Each column name – The target variable is not a transition variable. The
that is referenced in an OLAP specification must target of a SET assignment statement in a basic
unambiguously reference a column of the result trigger must be a transition variable.
table of the subselect that contains the OLAP
• The specified column reference to the index of an
specification.
array element is not allowed in the INTO clause for a

This error can be issued when there is an SQLSTATE
attempt to use a feature that requires a higher
APPLCOMPAT setting than the current setting. The 42703
current APPLCOMPAT setting does not support a -208 THE ORDER BY CLAUSE IS
feature that was requested. INVALID BECAUSE COLUMN
column-name IS NOT PART OF THE
System action RESULT TABLE
Explanation
Programmer response The statement is invalid because a column (column-
name) specified in the ORDER BY list does not appear
Verify the following items: in the result table (that is, it is not specified in the
• For a SELECT statement: SELECT-list). Only columns in the result table can be
used to order that result when the fullselect of the
– Ensure that all the required tables are specified in SELECT statement is not a subselect.
the FROM clause.
– Verify that all of the required tables or views System action
were named in the FROM clause. If the name was
intended to be a correlated reference to a column, The statement cannot be processed.
qualify the name with the correct table designator.
– For a subselect in an ORDER BY clause, ensure Programmer response
that there are no correlated column references.
Correct the syntax of the statement, either by adding
• For a DELETE statement, ensure that columns that the specified column to the result table, or deleting it
are defined in the INCLUDE clause are specified only from the ORDER BY clause.
as targets of assignments.
• For a CREATE FUNCTION, ALTER FUNCTION, SQLSTATE
CREATE PROCEDURE or ALTER PROCEDURE
statement, ensure that: 42707
– The specified name resolves to the name of a Related concepts
column or variable. Queries (Db2 SQL)
– The specified name resolves to the name of a Related reference
variable that is available in the current scope. order-by-clause (Db2 SQL)
– The specified condition name name specified in fullselect (Db2 SQL)
the SIGNAL statement has been declared. subselect (Db2 SQL)
• For a CREATE TRIGGER statement, ensure that: select-clause (Db2 SQL)
– The target of an assignment in a SET transition- -212 name IS SPECIFIED MORE THAN
variable statement specifies only new transition ONCE IN THE REFERENCING
variables. Any reference to columns of the CLAUSE OF A TRIGGER
triggering table, including those that are contained DEFINITION
in the top-level query block in the WHEN clause
search condition, are qualified with a transition
variable correlation name. Explanation
– The top-level query block in the WHEN clause The REFERENCING clause of a CREATE TRIGGER
search condition contains only transition variables statement specified the same name for more than
or transition table correlation names. one of the OLD or NEW correlation names or the
OLD_TABLE or NEW_TABLE identifiers. name is the
– The specified name resolves to the name of a
name that was specified multiple times.
variable that is available in the current scope.
– The specified condition name name specified in
the SIGNAL statement has been declared. System action
• For a SELECT INTO statement, make sure that the The statement cannot be processed. The trigger was
index of an array element is not specified as a not created.
column in the INTO clause.

Programmer response CALL statement for a parameter that is defined as
an input parameter (IN).
Change the statement to specify unique names for all
transition variables and tables in the REFERENCING 8
clause and resubmit the CREATE TRIGGER request. DISTINCT is specified in the LISTAGG function and
the first argument expression cannot be matched
exactly with the first sort key expression of the
SQLSTATE ORDER BY specified in the WITHIN GROUP clause.
42712 This reason code occurs only when clause-type is
ORDER BY.
-214 AN EXPRESSION IN THE
FOLLOWING POSITION, OR
System action
STARTING WITH position-or-
expression-start IN THE clause- The statement cannot be processed.
type CLAUSE IS NOT VALID.
REASON CODE = reason-code
Programmer response
Explanation Modify the select-statement based on the reason
specified by the reason-code. Use the following
The expression identified by the first part of the suggestions to modify the select-statement:
expression expression-start in the clause-type clause
1
is not valid for the reason specified by the reason-code
Remove the expression from the ORDER BY clause.
as follows:
If attempting to reference a column of the result,
1 change the sort key to the simple-integer or
The fullselect of the select-statement is not a simple-column-name form. For more information,
subselect. Expressions are not allowed in the see the ORDER BY syntax diagram in order-by-
ORDER BY clause for this type of select-statement. clause (Db2 SQL).
This reason code occurs only when clause-type is 2
ORDER BY. Remove DISTINCT from the SELECT clause.
2 3
DISTINCT is specified in the SELECT clause, and a Change the expression in the ORDER BY or GROUP
column name or sort-key-expression in the ORDER BY clause to an aggregate function or change the
BY clause cannot be matched exactly with a clause to use a numeric column identifier or a
column name or expression in the select list. column name.
This reason code occurs only when clause-type is
ORDER BY. 4
Add a GROUP BY clause or remove the aggregate
3 function from the ORDER BY clause.
The select list includes an aggregate function or
the subselect includes a GROUP BY clause and the 5
expression is not an aggregate function or does not Remove the scalar fullselect from the GROUP BY
match exactly with an expression in the select list. clause.
4 6
Grouping is caused by the presence of an Remove the scalar fullselect from the statement.
aggregate function in the ORDER BY clause. This 8
reason code occurs only when clause-type is When DISTINCT is specified in the LISTAGG
ORDER BY. function, ensure that ORDER BY is specified and
5 that the first sort key expression matches the
Expression in a GROUP BY clause cannot contain argument of LISTAGG.
a scalar-fullselect. This reason code occurs only
when clause-type is GROUP BY. SQLSTATE
6 42822
Invalid use of scalar-fullselect. This reason code
can be issued when the scalar-fullselect appears -216 THE NUMBER OF ELEMENTS ON
in an ORDER BY clause, the RETURN statement EACH SIDE OF A PREDICATE
of an SQL function contains a scalar-fullselect, or OPERATOR DOES NOT MATCH.
a scalar-fullselect is passed as an argument on a

PREDICATE OPERATOR IS -220 THE COLUMN column-name IN
operator. EXPLANATION TABLE table-name
IS NOT DEFINED PROPERLY
Explanation
The number of expressions specified on the left-hand
Explanation
side of OPERATOR operator is unequal to either the An error occurred during the insertion of a row into the
number of values returned by the fullselect or to the EXPLAIN table.
number of expressions specified on the right-hand
column-name
side of the operator. The number of expressions and
the number of values/expressions on either side of the The name of the column that caused the error. If
the column definition is incorrect, column-name
operator must be equal.
is the name of the column in error. Otherwise, *N
is returned for column-name because the column
System action name is not applicable.
The statement cannot be processed. table-name
The name of the EXPLAIN table.
Programmer response Possible reasons for this error include:
Change the number of expressions to match the • A column is missing.
number of values returned by the fullselect or vice • Columns are defined in the wrong order.
versa.
• The table contains an extra column.
SQLSTATE • A column description is invalid because of its name,

data type, length, or null attributes.
428C4 • The SQL statement contains contains mixed data,
-219 THE REQUIRED EXPLANATION and the EXPLAIN table was defined as CCSID
TABLE table-name DOES NOT EBCDIC.
EXIST
System action
Explanation The statement cannot be processed. The EXPLAIN
The EXPLAIN statement assumes the existence of information is not generated.
an EXPLAIN table, but it is not defined in the Db2
subsystem as a base table. Programmer response
Correct the definition of the required EXPLAIN table.
System action If the SQL statement being explained contains mixed
The statement cannot be processed. data and the EXPLAIN table is defined as CCSID
EBCDIC, take the following actions:
Programmer response 1. Copy the data from the EXPLAIN table.
Determine whether the required EXPLAIN tables exist. 2. Drop the EXPLAIN table.
If they do not, create the required tables. 3. Re-create the EXPLAIN table with CCSID UNICODE.
4. Copy the data into the EXPLAIN table.
SQLSTATE
42704 SQLSTATE
Related tasks 55002
Creating EXPLAIN tables (Db2 Performance) Related tasks
Related reference Creating EXPLAIN tables (Db2 Performance)
EXPLAIN (Db2 SQL) Related reference
EXPLAIN tables (Db2 Performance) EXPLAIN tables (Db2 Performance)
PLAN_TABLE (Db2 Performance) EXPLAIN (Db2 SQL)

-221 "SET OF OPTIONAL COLUMNS" • An update hole occurs when the corresponding row
IN EXPLANATION TABLE table- of the underlying table has been updated, and the
name IS INCOMPLETE. OPTIONAL updated row no longer satisfies the search condition
COLUMN column-name IS that is specified in the SELECT statement of the
MISSING cursor.
• A delete hole occurs when the corresponding row of
Explanation the underlying table has been deleted.
The EXPLAIN statement assumes that the required This error might be issued if the following situations
explanation table is defined properly. However, the occur:
optional column indicated is not defined in the • If the cursor is not a rowset cursor, then the row
indicated explanation table. corresponding to the current cursor position is either
table-name an update hole, or a delete hole. Db2 detects these
The name of the explanation table. holes when Db2 tries to update or delete the current
row of the result table for the cursor cursor-name,
column-name
and cannot locate the corresponding row of the
The name of the column.
underlying table.
Plan tables must have one of several specific formats. • If the cursor is a rowset cursor, then a row
The format chosen must be complete, and each corresponding to a row of the current rowset cursor
column in the PLAN_TABLE definition must be correct position is either an update hole or a delete hole.
for the chosen format. Db2 detects these holes when Db2 tries to update or
delete the current row of the result table for cursor
System action cursor-name, and cannot locate the corresponding
row or rows of the underlying table.
The explanation information is not generated.
System action
Programmer response
Correct the definition of the required explanation table updated or deleted, and the cursor position is
to include either all or none of the optional columns in unchanged.
the chosen format.
Programmer response
SQLSTATE
Correct the logic of the application program to ensure
55002 that the cursor is correctly positioned on the intended
Related tasks row or rows of the object table, and that the intended
Creating EXPLAIN tables (Db2 Performance) rows are not holes, before the DELETE or UPDATE
statement is executed.
Related reference
EXPLAIN tables (Db2 Performance) • If the cursor is not a rowset cursor, then issue a
EXPLAIN (Db2 SQL) FETCH statement to position the cursor on a row that
is not a hole. Then, reissue the UPDATE or DELETE
-222 AN UPDATE OR DELETE statement.
OPERATION WAS ATTEMPTED • If the cursor is a rowset cursor, and is also the
AGAINST A HOLE USING CURSOR positioned UPDATE or DELETE statement intended
cursor-name to affect a single row corresponding to the rows of
the current rowset cursor position (this means for a
Explanation FOR ROW n of ROWSET clause was specified), then
change the UPDATE or DELETE statement to process
Db2 could not process a positioned update or delete the rows that are not holes, one at a time.
with cursor cursor-name that is defined as SENSITIVE
• If the cursor is a rowset cursor, and is also the
STATIC. The application program attempted to execute
positioned UPDATE or DELETE statement intended
an UPDATE or DELETE WHERE CURRENT OF cursor
to affect all rows corresponding to the rows of the
statement at a time when the specified cursor was
current rowset cursor position (this means for a FOR
positioned on a row of the object table that is a hole.
ROW n of ROWSET clause was not specified), then
Each row that the cursor is positioned on, that is to be
change the UPDATE or DELETE statement to process
updated or deleted must not be a hole:
the rows that are not holes, one at a time. Add a FOR

ROW n of ROWSET clause to the UPDATE or DELETE that was not declared with the SCROLL attribute,
statement to indicate which row of the cursor is to however, the CURRENT clause is allowed with a
be updated or deleted. non-scrollable cursor only when combined with the
CONTINUE clause.
SQLSTATE • CONTINUE was specified on the FETCH statement,
but the specified cursor was opened for a multiple-
24510 row fetch operation. This combination is not
-224 THE RESULT TABLE DOES NOT supported.
AGREE WITH THE BASE TABLE
USING cursor-name System action
Explanation written to the output host variables.
A positioned UPDATE or DELETE was attempted on a
row that no longer matches its previous condition. The Programmer response
column values in the result table row no longer match
the current values in the base table row. The row was If a scrolling option was specified on the FETCH
updated after it was inserted into the result table but statement for a non-scrollable cursor, correct the
before the positioned update or delete was completed. FETCH statement to exclude the disallowed keyword,
or, correct the DECLARE CURSOR statement to include
cursor-name the appropriate SCROLL option. If the CONTINUE
The name of the cursor that was used for the clause was specified for a multiple-row cursor, change
positioned update or delete. the application to use single row fetch for this
cursor. If multiple-row fetch is required, use another
System action technique, such as a LOB locator for retrieving large
LOB or XML values.
The statement cannot be processed. The cursor is
positioned on the same row.
SQLSTATE
Correct the application program to handle this error -227 FETCH fetch-orientation IS NOT
condition, or change the isolation levels so that ALLOWED, BECAUSE CURSOR
the base row cannot be updated during the cursor cursor-name HAS AN UNKNOWN
operation. POSITION (sqlcode,sqlstate)
24512 The cursor position for cursor-name is unknown. The
previous multiple-row FETCH for cursor cursor-name
Related reference resulted in an error (SQLCODE sqlcode, SQLSTATE
DELETE (Db2 SQL) sqlstate) in the middle of processing multiple rows
UPDATE (Db2 SQL) that were retrieved from Db2. One or more of the
requested rows could not be returned to the program
-225 FETCH STATEMENT FOR cursor- following the error, leaving the position of the cursor
name IS NOT VALID FOR THE unknown.
DECLARATION OF THE CURSOR
If an indicator structure had been provided on the
previous multiple-row FETCH, a positive SQLCODE
Explanation would have been returned and all of the rows that
Db2 could not process a FETCH statement for were retrieved from Db2 could have been returned to
cursor cursor-name because it contained a disallowed the application program.
keyword. One of the following errors have occurred:
• A FETCH statement for a non-scrollable cursor
System action
specified one of the keywords PRIOR, FIRST, The statement cannot be processed. The cursor
LAST, ABSOLUTE, RELATIVE, CURRENT, BEFORE, or position is not changed.
AFTER. These keywords are disallowed for a cursor

Close and reopen the cursor to reset the position. The statement cannot be executed.
For scrollable cursors, you can change the FETCH
statement to specify one of the other fetch Programmer response
orientations (such as FIRST, LAST, BEFORE, AFTER,
or ABSOLUTE) to establish a valid cursor position and Depending on whether the locale was explicitly
fetch a row of data. specified in a SET CURRENT LOCALE LC_CTYPE
statement or the current locale was used implicitly,
complete one of the following actions:
SQLSTATE
• If the statement was a SET CURRENT LOCALE
24513
LC_CTYPE statement, re-specify a locale that is
-228 FOR UPDATE CLAUSE SPECIFIED correct (known and available to Db2).
FOR READ-ONLY CURSOR cursor- • If the statement was something other than SET
name CURRENT LOCALE LC_CTYPE, then the statement
contained a locale sensitive interface (the UPPER
Explanation function is an example of a locale sensitive
interface).
A cursor was declared read-only with the
INSENSITIVE SCROLL option, but the SELECT Issue the following statement to determine the value
statement contained a FOR UPDATE clause. of the locale in use by your program:
cursor-name SELECT CURRENT LOCALE LC_CTYPE FROM
Name of the cursor used for the FETCH. SYSIBM.SYSDUMMY1.
Another possible reason for this message is that Db2

System action used an incorrect locale default value specified at
The statement cannot be processed. installation time. Because locales are dynamic, they
can be added, created, or deleted at anytime. Db2
does not validate the value of the locale until it is used.
Programmer response Therefore, it is possible to specify a locale that is not
To define a scrollable cursor that is read-only, valid at installation time.
specify INSENSITIVE SCROLL, but do not specify For information about locales and their naming
FOR UPDATE clause. To define a scrollable cursor conventions, see z/OS XL C/C++ Programming Guide.
that can be updated, specify SENSITIVE SCROLL.
Correct the application program to DECLARE CURSOR
appropriately. SQLSTATE
42708
SQLSTATE -240 THE PARTITION CLAUSE OF
42620 A LOCK TABLE STATEMENT IS
INVALID
-229 THE LOCALE locale SPECIFIED
IN A SET LC_CTYPE OR OTHER
STATEMENT THAT IS LOCALE Explanation
SENSITIVE WAS NOT FOUND The LOCK TABLE statement is invalid for one of the
following reasons:
Explanation • If it is partitioned, specify a PARTITION clause that
The statement attempted to reference a locale that identifies the partition you want to lock.
is not known or not available to Db2. The value of
the variable locale indicates what locale Db2 is using System action
when it processed the statement. Db2 used the locale
that was either specified on the SET CURRENT LOCALE The LOCK TABLE statement cannot be executed.
LC_CTYPE statement or the locale that was in effect at
the time the locale access was attempted. Programmer response
Determine whether the specified table resides in a
partitioned table space defined with LOCKPART YES.

• If it is partitioned and defined with LOCKPART YES, • The cursor, cursor-name, is defined as SENSITIVE
specify a PART clause that identifies the partition DYNAMIC and an OFFSET or FETCH clause was
you want to lock. specified for outermost subselect or fullselect.
• If it is partitioned but does not have the LOCKPART
YES attribute and you want to lock a single partition, System action
use ALTER TABLESPACE to change the LOCKPART
attribute to YES. The statement cannot be processed.
• If it is not partitioned, do not specify the PART

clause. Programmer response
If the cursor is defined as SENSITIVE, but the content
SQLSTATE of the SELECT statement makes the cursor read-only,
either change the content of the query to result in a
428B4 result table that is not read-only, or change the type of
-242 THE OBJECT NAMED object- cursor to be INSENSITIVE or ASENSITIVE.
name OF TYPE object-type WAS If the cursor is defined as SENSITIVE DYNAMIC and
SPECIFIED MORE THAN ONCE an OFFSET clause or FETCH clause was specified for
IN THE LIST OF OBJECTS, OR outermost subselect or fullselect, either change the
THE NAME IS THE SAME AS AN cursor sensitivity or change the outermost subselect
EXISTING OBJECT or fullselect to remove the OFFSET clause or FETCH
clause.
Explanation
In a list of object names of type object-type, the object SQLSTATE
named object-name was specified more than once, or 36001
is the same as an existing name of that type.
Related reference
select-statement (Db2 SQL)
System action
subselect (Db2 SQL)
The statement cannot be processed. fullselect (Db2 SQL)
User response -244 SENSITIVITY sensitivity

SPECIFIED ON THE FETCH IS NOT
Correct the error by removing all of the duplicate VALID FOR CURSOR cursor-name
occurrences of the object from the list.
Explanation
SQLSTATE
The sensitivity option specified on FETCH conflicts
42713 with the sensitivity option in effect for cursor cursor-
-243 SENSITIVE CURSOR cursor-name name. If a cursor is declared INSENSITIVE, the FETCH
CANNOT BE DEFINED FOR THE statement can only specify INSENSITIVE or nothing. If
SPECIFIED SELECT STATEMENT a cursor is declared SENSITIVE, the FETCH statement
can specify INSENSITIVE, SENSITIVE, or nothing.
Explanation The keyword INSENSITIVE is not allowed with the

FETCH statements if the associated cursor is either:
A clause was not valid for one of the following reasons:
• Declared as SENSITIVE DYNAMIC SCROLL, or
• The cursor, cursor-name, is defined as SENSITIVE,
• The cursor is declared ASENSITIVE, and Db2
but the content of the SELECT statement makes
selected the maximum allowable sensitivity of
the cursor read-only. In most cases the SELECT
SENSITIVE DYNAMIC SCROLL for the associated
statement requires Db2 to build a temporary table
SELECT statement.
or work file with the result table of the cursor, and
Db2 cannot guarantee that changes made outside In the case of a non-scrollable cursor, the sensitivity
the cursor will be visible. In this case, the cursor option cannot be specified.
must be defined INSENSITIVE or ASENSITIVE.
sensitivity
Specified sensitivity for the FETCH statement.

cursor-name OF ROWS num-rows WHICH IS
Name of the cursor used for the FETCH statement. NOT VALID WITH dimension

The statement cannot be processed. A multiple-row FETCH, MERGE, or INSERT statement
is not valid in this context. The statement is invalid for
Programmer response one of the following reasons:
• The specified number of rows is not greater than 0
Change or remove the sensitivity option that is
and not less than or equal to 32767.
specified on the FETCH.
• The specified number of rows is greater than the
dimension of the host-variable array.
SQLSTATE
• If the statement is a multiple-row FETCH statement
428F4 that is executed in a distributed environment or is
-245 THE INVOCATION OF FUNCTION executed on an accelerator, the computed maximum
routine-name IS AMBIGUOUS size of the reply data exceeds the Db2 limit. The
computed maximum size of the reply data is the
product of the number of rows and the maximum
Explanation size of the data that is returned in a single row of the
Db2 was not able to resolve the indicated function. query.
• If the statement is a multiple-row INSERT statement
routine-name
that is executed on an accelerator, the FOR n ROWS
The name of the function.
clause is not supported unless when the VALUES
This situation can occur in the following clause uses a host variable array.
circumstances:
cursor-name
• An untyped parameter marker is passed to a If the SQL statement is a FETCH statement, this
function and there are two or more possible value is the name of the cursor that was used for
candidate functions to resolve to during function the FETCH statement. If the SQL statement is not
resolution. a FETCH statement, this value is the string *N. *N
• Db2 cannot determine how to implicitly cast the indicates that the cursor name is not applicable.
arguments between string and numeric data types. num-rows
• Db2 is unable to resolve a function invocation The number of rows that were specified.
using the promotable process or castable process of dimension
function resolution. If the statement is not a multiple-row FETCH
statement that is executed in a distributed
System action environment, and is not a multiple-row FETCH
statement that is executed on an accelerator, this
The statement cannot be processed. value is the dimension of the array.
If the statement is a multiple-row FETCH
Programmer response statement that is executed in a distributed
Correct the problem and reissue the statement. environment, or a multiple-row FETCH statement
You might need to change the SQL statement, the that is executed on an accelerator, this value is the
definition of a function, or the user's SQL path. string *N. *N indicates that the dimension is not
applicable.
SQLSTATE
System action
428F5
The statement cannot be processed. The cursor
Related concepts position is unchanged.
How Db2 resolves functions (Db2 Application
programming and SQL) Programmer response
-246 STATEMENT USING CURSOR Take one of the following actions:
cursor-name SPECIFIED NUMBER

• Change the application to declare or allocate a host- number of rows. In this case, a partial rowset is
variable array that is large enough to contain the returned. A partial rowset can occur for various
specified number of rows. reasons, including an end of data condition or an error
• Change the specified number of rows to be between that did not result in the closure of the cursor.
1 and 32767, inclusive.
• If the statement is a multiple-row FETCH statement System action
that is executed in a distributed environment, or is The statement cannot be processed.
executed on an accelerator, decrease the specified
number of rows.
Programmer response
• If the statement is a multiple-row INSERT statement
that is executed on an accelerator, use host variable Reissue the positioned UPDATE or DELETE with a value
arrays in the VALUES clause. that corresponds to a row of the current rowset. If the
row that is specified is outside of the current rowset,
then do the following:
SQLSTATE
• Use the FOR n ROWS clause on a FETCH CURRENT
42873
ROWSET statement to specify that the rowset
-247 A HOLE WAS DETECTED ON contains a larger number of rows
A MULTIPLE ROW FETCH • Reissue the positioned UPDATE or DELETE
STATEMENT USING CURSOR statement.
cursor-name, BUT INDICATOR
VARIABLES WERE NOT PROVIDED If this message is issued because a partial rowset was
TO DETECT THE CONDITION returned,
• Update the application logic to detect that the actual
Explanation rowset size was less than the rowset size that was
requested
A hole was detected on a FETCH statement for
• Ensure that a positioned UPDATE or DELETE
multiple rows of data, but no indicator variables were
statement only refers to rows of the current rowset.
provided to reflect the situation to the application.

24521
-249 DEFINITION OF ROWSET ACCESS
Programmer response FOR CURSOR cursor-name IS
INCONSISTENT WITH THE FETCH
Change the FETCH statement to provide at least one ORIENTATION CLAUSE clause
indicator variable, and resubmit the statement. SPECIFIED
24519 A clause specified for the FETCH statement is
-248 A POSITIONED DELETE OR inconsistent with the definition of the cursor cursor-
UPDATE STATEMENT FOR CURSOR name. This error can be issued for the following
cursor-name SPECIFIED ROW n situations:
OF A ROWSET, BUT THE ROW • A cursor defined WITHOUT ROWSET POSITIONING
IS NOT CONTAINED WITHIN THE can only use BEFORE, AFTER, row positioned fetch
CURRENT ROWSET orientation keywords: NEXT, PRIOR, FIRST, LAST,
CURRENT, ABSOLUTE, or RELATIVE.
Explanation • A cursor defined WITH ROWSET POSITIONING
can use BEFORE, AFTER, rowset positioned fetch
The FOR ROW n OF ROWSET clause was specified on
orientation clauses: NEXT ROWSET, PRIOR ROWSET,
a positioned DELETE or UPDATE statement, but row
FIRST ROWSET, LAST ROWSET, CURRENT ROWSET,
n is not contained within the bound of the rowset.
or ROWSET STARTING AT, or, row positioned fetch
This situation can also occur when row n is within
orientation keywords: NEXT, PRIOR, FIRST, LAST,
the bounds of the rowset that was requested, but
CURRENT, ABSOLUTE, or RELATIVE.
the current rowset contains less than the requested

A FOR n ROWS clause was specified on a FETCH SQLSTATE
statement, but the cursor is not defined for rowset
access. 42602
-253 A NON-ATOMIC statement
System action STATEMENT SUCCESSFULLY
COMPLETED FOR SOME OF THE
The statement cannot be processed. REQUESTED ROWS, POSSIBLY
WITH WARNINGS, AND ONE OR
Programmer response MORE ERRORS
Correct the fetch orientation, remove the FOR n ROWS
clause, or redefine the cursor. Explanation
A non-atomic statement statement successfully
SQLSTATE processed some of the rows of data that
were requested. However, one or more error
24523 conditions occurred, and some warnings might have
-250 THE LOCAL LOCATION NAME also occurred. Use GET DIAGNOSTICS to obtain
IS NOT DEFINED WHEN information about the error and warning conditions
PROCESSING A THREE-PART that occurred.
OBJECT NAME
System action
Explanation One or more rows were successfully processed, but
A three-part object name (table, view, or alias) cannot one or more errors or warnings also occurred.
be used until the local location name is defined.
Programmer response
System action Analyze the error and warning conditions to determine
Install or reinstall the Db2 distributed data facility if the statement should be rolled back.
(DDF) with a registered location name for local Db2.
SQLSTATE
Define the local location name and then retry the -254 A NON-ATOMIC statement
function. STATEMENT ATTEMPTED TO
PROCESS MULTIPLE ROWS OF
SQLSTATE DATA, BUT ERRORS OCCURRED
42718
Explanation
-251 TOKEN name IS NOT VALID
A non-atomic statement statement specified that
multiple rows of data were to be processed, but errors
Explanation occurred during the processing of those rows of data.
A location name cannot contain alphabetic extenders. Use GET DIAGNOSTICS to obtain information about
(The standard alphabetic extenders in the United the error and warning conditions that occurred.
States are #, @, $.)
System action
Programmer response
Programmer response Analyze the error and warning conditions to determine
Correct the name and reissue the statement. the appropriate corrective actions.

SQLSTATE • When a spatial index is created on a column of
BLOB or distinct type on BLOB, the LOB table
22530 space that stores the BLOB column must exist.
-270 FUNCTION NOT SUPPORTED • A spatial index cannot be altered.
• The internal limit of 30,000 bytes for the
Explanation versioned object descriptor (OBD) was exceeded.
This condition can happen when an ALTER
The statement cannot be processed because it
INDEX statement resulted in a new index
violates one or more of the following restrictions:
version.
ALTER FUNCTION statement • A CREATE INDEX DSSIZE and CREATE INDEX
• An obfuscated function cannot be altered. PART DSSIZE cannot both be specified in the
same statement.
ALTER INDEX or CREATE INDEX statements
For more information, see:
• A CREATE INDEX or ALTER INDEX statement
must not specify PADDED for an XML index or CREATE INDEX (Db2 SQL)
an index on a VARBINARY column. ALTER INDEX (Db2 SQL)
• A CREATE INDEX or ALTER INDEX statement Unicode columns in EBCDIC tables (Db2 SQL)
must not specify a column that is defined as NOT ALTER PROCEDURE statement
NULL when the index is defined with EXCLUDE
NULL KEYS. • An obfuscated procedure cannot be altered.
• A CREATE INDEX statement must not specify ALTER TABLE or CREATE TABLE statements
UNIQUE, BUSINESS_TIME WITHOUT OVERLAPS, • An ALTER TABLE statement must not attempt
an XML-index-specification, or a key-expression to alter a VARBINARY column to BINARY if that
when the index is defined with EXCLUDE NULL column is part of a unique index.
KEYS.
• An ALTER TABLE statement must not specify
• A CREATE INDEX statement must not specify a materialized query table in an ADD CLONE
EXCLUDE NULL KEYS when the index is a clause. Alter the materialized query table into a
partitioning index. base table before altering the table.
• A CREATE INDEX statement must not specify • An ALTER TABLE or CREATE TABLE statement
ASC, DESC, or RANDOM for an XML index. can only specify the KEY LABEL clause for tables
• A CREATE INDEX statement must not specify in a universal or partitioned table space.
DESC or RANDOM if the index is an expression- • An ALTER TABLE statement with the ALTER
based index. COLUMN SET DATA TYPE clause must not specify
• A CREATE INDEX statement must not specify VARBINARY or BINARY for the new data type
DESC, PADDED, or RANDOM for a Db2 11 when both of the following conditions are true:
Unicode column in an EBCDIC table.
– The column is a partitioning key column.
• A CREATE INDEX statement must not specify
– The existing data type is CHAR or VARCHAR
INCLUDE or CLUSTER for an expression-based
FOR BIT DATA.
index.
• A materialized query table cannot be cloned for
• A CREATE INDEX statement must not specify a
ALTER TABLE.
BINARY or VARBINARY column in a partitioning
key. • The result table of the fullselect in the as-result-
table clause of a CREATE TABLE statement
• A CREATE or ALTER INDEX statement must not
includes data that is encoded with different
specify RANDOM for an index that contains a
CCSID sets. The result table must not use
column that is defined as TIMESTAMP WITH
multiple CCSID sets.
TIME ZONE or DECFLOAT.
• The internal limit of 30000 bytes for the
• A CREATE INDEX statement must specify DEFER
versioned object descriptor (OBD) was exceeded.
YES for a spatial index.
This condition can happen when an ALTER table
• A CREATE INDEX statement must not specify the statement results in a new table version or index
name of a declared global temporary table. version, or is executed on a versioned table.
• A column can have one spatial index only.

• INLINE LENGTH is not allowed for the LOB ALTER TABLE (Db2 SQL)
column because the table space is not a Unicode columns in EBCDIC tables (Db2 SQL)
universal table space.
ALTER TABLE ALTER COLUMN SET DATATYPE
• An ALTER TABLE statement was specified with statement
an ADD PERIOD clause and a column mask or
row permission is defined for the table. A period • Altering the data type of a column in a table with
cannot be added to a table for which a column PAGENUM RELATIVE is not allowed if it causes
mask or row permission is defined. the minimum data size of a row to be less than 3
bytes.
• The table or view that is specified in a LIKE
clause must not contain a Db2 11 Unicode ALTER TABLE DROP COLUMN statement
column in an EBCDIC table.
• Dropping a column in a table with PAGENUM
• An ALTER TABLE statement must not specify an RELATIVE is not allowed if it causes the
ADD PARTITION BY RANGE clause if the table minimum data size of a row to be less than 3
is EBCDIC and it contains a Db2 11 Unicode bytes.
column.
ALTER TABLESPACE statements
• An ALTER TABLE statement must not specify an
IMPLICITLY HIDDEN clause in an ADD COLUMN • An ALTER TABLESPACE DSSIZE and ALTER
clause for a column that is defined as a ROWID, TABLESPACE PART DSSIZE cannot both be
or a distinct type that is based on a ROWID. specified in the same statement.
• An ALTER TABLE or CREATE TABLE statement • An ALTER TABLESPACE PAGENUM RELATIVE is
that defines a generated expression column not allowed when the table space has a table in
must specify the same data type as the result which the minimum data size of the row is less
type of the expression. For a column that is than 3 bytes.
defined as DATA CHANGE OPERATION, CHAR(1) CREATE GLOBAL TEMPORARY TABLE statements
must be specified as the data type.
• table or view that is specified in a LIKE clause
• A CREATE TABLE statement must not contain a
must not contain a Db2 11 Unicode column in an
LIKE clause and an IN ACCELERATOR clause.
EBCDIC table.
• A CREATE TABLE statement must not contain a
LIKE clause that references an accelerator-only For more information, see:
table. CREATE GLOBAL TEMPORARY TABLE (Db2 SQL)
• A CREATE TABLE statement must not contain an Unicode columns in EBCDIC tables (Db2 SQL)
AS fullselect clause and an IN ACCELERATOR
DECLARE GLOBAL TEMPORARY TABLE statements
clause.
• A CREATE TABLE statement must not contain • The result table of the fullselect in the as-result-
an AS fullselect clause where the fullselect table clause of a DECLARE GLOBAL TEMPORARY
references an accelerator-only table. TABLE statement includes data that is encoded
with different CCSID sets. The result table must
• A CREATE TABLE statement must not contain not use multiple CCSID sets, other than EBCDIC
a materialized query definition and an IN and Unicode.
ACCELERATOR clause.
• A BINARY or VARBINARY column cannot be
• A CREATE or ALTER TABLE statement must not specified in a partitioning key.
define a Unicode column in an EBCDIC table if
the table is an accelerator-only table. • table or view that is specified in a LIKE clause
must not contain a Db2 11 Unicode column in an
• CREATE TABLE with PAGENUM RELATIVE or in a EBCDIC table.
table space with PAGENUM RELATIVE must have
rows with a minimum data size of 3 bytes. • The LIKE clause of a DECLARE GLOBAL
TEMPORARY TABLE must not reference an
• An ALTER TABLE or CREATE TABLE statement accelerator-only table.
must not specify KEY LABEL clause for a table in
a multi-table table space. If the table resides in For more information, see DECLARE GLOBAL
a multiple-table table space, consider using the TEMPORARY TABLE (Db2 SQL).
key label specification at the storage group level. CREATE FUNCTION statements
For more information, see: A CREATE FUNCTION statement must not attempt
to define an SQL table function with either of the
CREATE TABLE (Db2 SQL) following items:

• A function body that references a column that is routine. The STACKED keyword is supported only
defined with a field procedure within a native SQL routine.
• A RETURNS clause that references a column that For more information, see GET DIAGNOSTICS (Db2
is defined with a field procedure. SQL).
For more information, see CREATE FUNCTION MERGE statements
(Db2 SQL).
• A column of the source table is referenced
CREATE MASK statements multiple times in a modification operation of the
A CREATE MASK statement must not define a mask MERGE statement. When extended indicators
for an accelerator-only table. are in effect, a column of the source table
For more information, see: must not be referenced more than one time
in a modification operation. A modification
CREATE MASK (Db2 SQL) operation is an update operation or an insert
CREATE PERMISSION statements operation. Extended indicators are in effect when
A CREATE PERMISSION statement must not define EXTENDEDINDICATOR(YES) is used, or when the
a column permission for an accelerator-only table. WITH EXTENDED INDICATORS prepare attribute
is specified for the MERGE statement.
For more information, see CREATE PERMISSION
• The search-condition of the ON clause of
(Db2 SQL).
a MERGE statement must not include an
CREATE PROCEDURE statement IN predicate that includes a fullselect, or a
A CREATE PROCEDURE statement must not be quantified predicate that includes a fullselect.
used to add or replace a version of an obfuscated • The matching-condition of the WHEN MATCHED
procedure. or WHEN NOT MATCHED clause of a MERGE
For more information, see CREATE PROCEDURE statement must not include an IN predicate that
(Db2 SQL). includes a fullselect, or a quantified predicate
that includes a fullselect.
CREATE VARIABLE statements
A CREATE VARIABLE statement cannot specify • A MERGE statement that contains a delete
a default value of the CURRENT TEMPORAL operation cannot be used as a data-change-
SYSTEM_TIME or CURRENT TEMPORAL table-reference in the FROM clause of the outer
BUSINESS_TIME special registers. SELECT clause of a fullselect.
For more information, see CREATE VARIABLE (Db2 For more information, see MERGE (Db2 SQL).
SQL). TRIGGER statements
CREATE VIEW or ALTER VIEW REGENERATE • A CREATE TRIGGER statement must not specify
statements a view that has any of the following types of
All of the views and SQL functions that are columns:
referenced in a view definition must have the same
rounding mode as the view that is being defined. – ROWID columns
SQL functions that have undefined rounding mode – LOB columns
information are ignored during rounding mode – XML columns
checking.
– Defined (directly or indirectly) as identity
For more information, see: columns
CREATE VIEW (Db2 SQL) – Security label columns
ALTER VIEW (Db2 SQL) – Row change timestamp columns
FETCH statements – Row-begin columns
A FETCH statement cannot include WITH – Row-end columns
CONTINUE or CURRENT CONTINUE within an SQL
routine. – Transaction-start-ID columns
– Expressions
For more information, see FETCH (Db2 SQL).
– Columns of result tables that involve set
GET DIAGNOSTICS statements operators
The STACKED keyword cannot be specified for a
GET DIAGNOSTICS statement in an external SQL

• A CREATE [or ALTER] TRIGGER statement must requalification. See "Programmer response" for
not reference an accelerator-only table in the information about handling requalification errors.
body of the trigger.
Other restrictions for SQL statements:
• A CREATE TRIGGER statement with INSTEAD OF
clause specified must not reference a view that • Views and SQL functions that are referenced in
references an accelerator-only table in the body an SQL statement must have the same rounding
of the trigger. mode as the SQL statement. Views and SQL
functions that have undefined rounding mode
• The transition variable that is specified does not information are ignored during rounding mode
support XML. checking.
• A CREATE TABLE statement in the body of a • In a subselect, the select list cannot contain an
trigger must not define a column as a LOB or XML column if OLD TABLE is specified.
XML.
• The RID built-in function and ROW CHANGE
• The statement string for a PREPARE statement TOKEN expression must not be specified in a
must not be an ALLOCATE CURSOR statement if subselect when that subselect directly includes
the PREPARE statement is issued in the body of a one of the following operators:
trigger.
– LEFT OUTER JOIN
• An ALTER TRIGGER (basic) statement must not
specify an option other than SECURED or NOT – RIGHT OUTER JOIN
SECURED. – FULL OUTER JOIN
• An ALTER TRIGGER (advanced) statement can • The ROW CHANGE TIMESTAMP expression can
only be dynamically prepared. be specified only in a subselect when the
• A CREATE TRIGGER (advanced) or ALTER following conditions are true:
TRIGGER (advanced) statement cannot be – That subselect directly includes a LEFT OUTER
processed as a static statement. JOIN, RIGHT OUTER JOIN, or FULL OUTER
• An obfuscated trigger cannot be altered. JOIN operator.
For more information, see CREATE TRIGGER – The table designator identifies a base table
(basic) (Db2 SQL). that contains a row change timestamp
column.
UPDATE statements:
Some UPDATE statements that modify data in • An SQL table function must not be invoked with
a column for which a BEFORE UPDATE trigger an expression that is derived from a column that
is defined might result in this code in certain is defined with a field procedure.
circumstances. • An input argument for an SQL table function
must not contain a scalar fullselect, a function,
• If a BEFORE UPDATE TRIGGER statement
or a column reference, either directly or as part
contains a SET clause for one or more columns
of an expression.
that participate in the access path index,
execution of the BEFORE UPDATE TRIGGER • No combination of ARRAY_AGG, LISTAGG or
statement might cause the row to qualify again. XMLAGG can be specified together in the same
This situation occurs when all of the following statement.
conditions are met: • The SQL statement includes a use of UNNEST,
– Db2 is using an index access path to locate and an argument to the UNNEST operator is
rows that qualify for update. an array function invocation that includes a
reference to a column. An argument of an array
– A BEFORE TRIGGER exists on the table to function invocation must not include a reference
which the rows belong. to a column of a common table expression.
– The BEFORE TRIGGER updates the values of • A query or a SELECT INTO, INSERT, UPDATE,
one or more columns that participate in the DELETE, or MERGE statement must not
access path index. reference tables or views that include both
This situation can happen with both searched inclusive-exclusive BUSINESS_TIME periods and
updates and positioned updates (updates that inclusive-inclusive BUSINESS_TIME periods.
use the statement UPDATE WHERE CURRENT • In a DELETE or UPDATE statement, a FROM
OF CURSOR). This code is issued for statements expression1 TO expression2 clause must not be
that are susceptible to this problem, even if the specified for an inclusive-inclusive period.
data involved in the update would not cause

• In a DELETE or UPDATE statement, a BETWEEN If a view or SQL function has a different
expression1 AND expression2 clause must not be rounding mode than the referencing view during
specified for an inclusive-exclusive period. execution of ALTER VIEW REGENERATE:
Change the rounding mode in effect to make
BIND PACKAGE command
sure all the views or SQL functions that are
A BIND PACKAGE command with the DEPLOY
referenced have the same rounding mode as
option must not be specified for the following
the referencing view. The view for ALTER VIEW
situations:
REGENERATE might always fail. In this case,
• A package for a routine that is obfuscated. drop and re-create the view with a different
• A package for a version of a procedure for view definition that references a new view or
which the CREATE PROCEDURE statement SQL function.
contains an OR REPLACE or SPECIFIC clause. Errors that are caused by the requalification of data
If the problem is caused by requalification of
For more information, see BIND PACKAGE
data that was set by a BEFORE UPDATE TRIGGER
(DSN) (Db2 Commands).
statement, take one of the following actions:
System action • Ensure that the columns that are modified by

the trigger are also modified by the UPDATE
The statement cannot be processed. statement itself. Modify the UPDATE statement
to include a dummy clause of the type column-
Programmer response name=column-name for each column that the
BEFORE UPDATE TRIGGER modifies.
Correct the syntax, and resubmit the statement. For
• Rebind with hints to cause the RIDLIST access
the following errors, take the specified actions.
path to use the same index.
Errors that are caused by an XML data type
Errors that are caused by size of the OBDREC
If this error is caused by an XML data type, input
If the size of the OBDREC exceeds 30,000 bytes,
the XML data to one of the functions that accept
you might be able to reclaim some space in the
XML input. Store the output of the function in the
OBD by reducing the size of the default value for
database, or return it to the application.
varying-length columns, if any exist.
Errors that are caused by the rounding mode
If this error is caused by different rounding modes,
take one of the following actions:
SQLSTATE
If a view or SQL function has a different 42997
rounding mode than the referencing SQL -300 THE STRING CONTAINED IN
statement: HOST VARIABLE OR PARAMETER
Change the SQL statement or change the position-number IS NOT NUL-
rounding mode in effect to make sure all the TERMINATED
views or SQL functions that are referenced
have the same rounding mode as the SQL
statement. A new view, SQL function, or both Explanation
might be needed to match the rounding mode A host variable or parameter is invalid. Its entry in
of the SQL statement. the SQLDA is indicated by position-number. The host
If a view or SQL function has a different variable or parameter is a C string variable that is one
rounding mode than the referencing view during of the following:
execution of CREATE VIEW:
• Used as an input parameter to a stored procedure or
Change the view definition or change the
function.
rounding mode in effect to make sure all the
views or SQL functions that are referenced • Returned as an output parameter from a stored
have the same rounding mode as the procedure or function.
referencing view. A new view, SQL function, or • Referenced as an input variable in an embedded SQL
both might be needed to match the rounding statement.
mode of the referencing view.
• Used to provide a value for a parameter marker of a
dynamic SQL statement.
If the data type of the variable is character string,
it is invalid because it does not include X'00'. If the

data type of the variable is graphic string, it is invalid Explanation
because it does not include X'0000'.
Db2 received data that was invalid or too large
to fit in the corresponding column of the table or
System action the corresponding target value. The position-number
The statement cannot be processed. identifies either the host variable number (if the
message is issued as a result of an INSERT, UPDATE,
MERGE, DELETE, SELECT, VALUES INTO, or SET
Programmer response assignment statement), or the parameter number
Append a NUL-terminator to the end of the string. (if the message is issued as the result of a CALL
statement or the invocation of a function).
SQLSTATE One of the following occurred:
22024 • The column is defined as a string and the host
variable or parameter contains a string that is too
-301 THE VALUE OF INPUT VARIABLE long for the column.
OR ARGUMENT NUMBER position-
number CANNOT BE USED AS • The column is defined as numeric and the host
SPECIFIED BECAUSE OF ITS DATA variable or parameter contains a numeric value too
TYPE large for the definition of the column.
• The host variable is defined as decimal, but contains
invalid decimal data.
Explanation
• The target value is a string constant and the host
Db2 received data that could not be used as specified variable or parameter contains a string that is too
in the statement because its data type is incompatible long for the target value.
with the requested operation.
• The target value is a numeric constant and the host
The position-number identifies either the variable variable or parameter contains a numeric value that
number (if the message is issued as a result of an is too large for the target value.
INSERT, UPDATE, MERGE, DELETE, SELECT, VALUES
INTO, or SET assignment statement), or the argument
number (if the message is issued as the result of a
System action
CALL statement, or the invocation of a function). The statement cannot be processed.
For a statement other than CALL, an ordinary array
cannot be specified for a target that is defined as an Programmer response
associative array in the specified context. See CALL
Correct the application program, function or stored
(Db2 SQL) for the exceptions for a CALL statement.
procedure. Check the column type and length of the
value or the data type and contents of the input host
System action variable or parameter position-number. Ensure that
The statement cannot be processed. the value of the host variable or parameter will fit
in the column or contains valid decimal data. Valid
decimal data is a System/370 packed decimal number.
Programmer response
Correct the application program, function or stored SQLSTATE
procedure. Ensure that the data type of the indicated
input variable or argument in the statement is 22003 if number too large for target; 22001 otherwise.
compatible with the way it is used. -303 A VALUE CANNOT BE ASSIGNED
TO VARIABLE NUMBER position-
SQLSTATE number BECAUSE THE DATA
TYPES ARE NOT COMPATIBLE
42895
-302 THE VALUE OF INPUT VARIABLE Explanation
OR PARAMETER NUMBER position-
number IS INVALID OR TOO A CALL, FETCH, SELECT, VALUES INTO, or SET
LARGE FOR THE TARGET COLUMN assignment-statement statement with an output
OR THE TARGET VALUE variable could not be performed because the data
type of a variable was not compatible with the data

type of the source value in the statement. For more Explanation
information, see Assignment and comparison (Db2
SQL). A CALL, FETCH, SELECT, VALUES INTO, or SET
assignment statement with a host variable list or
position-number structure in position number position-number failed
Location of the variable in the statement. because the host variable with data type data-type2
The values of the target variable and the was not large enough to hold the retrieved value with
corresponding source value must be in one of the data type data-type1.
following categories:
• One value is numeric and one of the following System action
conditions is true: The statement cannot be processed. No data was
– The other value is also numeric. retrieved. If the statement was a FETCH, the cursor
remains open.
– The other value is a character string.
– The other value is a graphic string and uses Programmer response
Unicode.
– The statement has a subtype of FOR BIT DATA. Verify that table definitions are current, and that
the host variable has the correct data type. See the
• Both must be character strings, unless you are using explanation for SQLCODE -405 for ranges of SQL data
Unicode. types.
• Both must be graphic strings, unless you are using
Unicode. SQLSTATE
• Both must be row IDs.
22003
• Both must be binary strings, or one can be BINARY
or VARBINARY, and the other can be FOR BIT DATA. -305 THE NULL VALUE CANNOT BE
ASSIGNED TO OUTPUT HOST
• A variable is XML or binary XML and the
VARIABLE NUMBER position-
corresponding statement list element is XML.
number BECAUSE NO INDICATOR
In addition: VARIABLE IS SPECIFIED
• For datetime or timestamp values, the target host
variable must be a character string variable with the Explanation
correct length.
A FETCH, SELECT, VALUES INTO, or SET assignment
• For array values, see Assignment and comparison statement resulted in the retrieval of a null value to be
(Db2 SQL). inserted into the output host variable, designated by
entry number 'position-number' of the output SQLDA,
System action for which no indicator variable was provided. An
indicator variable must be supplied if a column returns
The statement was not executed. No data is retrieved. a null value.

Verify that table definitions are current, and that the The statement cannot be processed. No data was
target variable has the correct data type. retrieved.

42806 Examine the definition of the table that is the object
of the statement and correct the application program
-304 A VALUE WITH DATA TYPE data-
to provide indicator variables for all host variables
type1 CANNOT BE ASSIGNED
into which null values can be retrieved. This includes
TO A HOST VARIABLE BECAUSE
host variables for columns which can contain null
THE VALUE IS NOT WITHIN THE
values and host variables which receive the results
RANGE OF THE HOST VARIABLE
of aggregate functions whose result table could be
IN POSITION position-number
empty.
WITH DATA TYPE data-type2

22002 Correct the application program or stored procedure.
Ensure that all decimal variables or parameters
-309 A PREDICATE IS INVALID
contain valid System/370 packed decimal numbers.
BECAUSE A REFERENCED HOST
VARIABLE HAS THE NULL VALUE
SQLSTATE
Explanation 22023
The statement could not be processed because a host -311 THE LENGTH OF INPUT HOST
variable appearing in a predicate such as VARIABLE NUMBER position-
number IS NEGATIVE OR GREATER
column-name = host-variable THAN THE MAXIMUM
had the NULL value. Such a predicate is not permitted
when the host variable contains the NULL value even Explanation
though the object column might contain nulls.
When evaluated, the length specification for input host
string variable, whose entry in the SQLDA is indicated
System action by position-number, was negative or greater than the
maximum.
System action
Programmer response
Rebind the plan or package containing the statement.
The condition described is not an error in Version 2
Release 3 and later Db2 releases. Programmer response
Correct the program to ensure that the lengths of all
SQLSTATE host string variables are not negative or that they are
not greater than the maximum allowed length.
22512
-310 DECIMAL HOST VARIABLE OR SQLSTATE
PARAMETER number CONTAINS
NON-DECIMAL DATA 22501
-312 VARIABLE variable-name IS NOT
Explanation DEFINED OR NOT USABLE
Db2 received nondecimal data from either an
application (in the form of a host variable), function Explanation
or a stored procedure (in the form of a parameter that
A variable is referenced in the SQL statement, but it
was passed to or from function or a stored procedure).
either is not defined or cannot be used.
number
variable-name
Identifies either the host variable number (if the
The name of the variable that is referenced in the
message is issued as a result of a FETCH, INSERT,
statement.
UPDATE, MERGE, DELETE, SELECT, VALUES INTO,
or SET assignment statement), or the parameter The following list identifies examples of conditions
number (if the message is issued as the result of that result in this SQLCODE:
the invocation of a function, or a CALL statement).
• The variable is not declared.
• The attributes of the variable are inconsistent with
System action its usage in the SQL statement.
The statement cannot be processed. • The host variable was specified in a dynamic SQL
statement. Host variables are not valid in dynamic
SQL statements.
• The variable is a host-variable array that was
referenced in an unsupported context. For more

information, see Host-variable arrays in PL/I, C, C++, Related concepts
and COBOL (Db2 SQL). Host-variable arrays in PL/I, C, C++, and COBOL
• The variable appeared in one of the triggered SQL (Db2 SQL)
statements in a CREATE TRIGGER statement. An
OLD transition variable cannot be modified in a -313 THE NUMBER OF HOST
trigger body. VARIABLES SPECIFIED IS NOT
EQUAL TO THE NUMBER OF
• The variable name is used in the body of an SQL PARAMETER MARKERS
procedure, SQL function, or trigger, but the variable
is not declared as an SQL variable or parameter.
The scope of an SQL variable is the compound Explanation
statement that contains the declaration, including The number of host variables specified in the EXECUTE
any compound statements that are nested within or OPEN statement is not the same as the number of
that compound statement. parameter markers (question marks) appearing in the
• The variable appeared in one of the key-expressions prepared SQL statement.
of an index definition.
• An array variable is used in a context in which it is System action
unsupported. An array variable, other than a global
variable, is not allowed in a CREATE VIEW statement. The statement cannot be processed.
• A host variable is declared in PL/I with the attributes

BINARY, FIXED and UNSIGNED. Programmer response
Correct the application program so that the number
System action of host variables specified in the EXECUTE or OPEN
statement is the same as the number of parameter
The statement cannot be processed. markers appearing in the prepared SQL statement.
The DESCRIBE INPUT SQL statement can be used to
Programmer response determine the expected number of input parameter
markers.
Do one of the following solutions and try the request
again:
SQLSTATE
• Verify that the program or SQL routine contains a
declaration for the variable. Verify that the variable 07001
name in the SQL statement is spelled correctly. -314 THE STATEMENT CONTAINS AN
• Verify that the attributes of the variable are AMBIGUOUS HOST VARIABLE
compatible with its use in the statement. REFERENCE
• Use parameter markers in a dynamic SQL statement
instead of host variables. Explanation
• Specify a NEW transition variable when the variable A host variable used in the statement has been defined
is modified in a trigger. more than once in this application program causing
• Declare the variable as an SQL variable or parameter confusion as to which host variable defined should be
in the SQL routine. used.
• Check the definition of the index and remove any
host variables that are specified. System action
• Remove array variables, other than global variables, The statement cannot be processed.
from the statement.
• BINARY FIXED UNSIGNED variables cannot be used Programmer response
as host variables in PL/I. Instead, use a BINARY
FIXED SIGNED variable with enough precision to Make the host variable unique or use qualifications to
represent the range of values needed. indicate which host variable definition is to be used.
SQLSTATE SQLSTATE
42618 42714

-327 THE ROW CANNOT BE INSERTED If the string is the value of an input host variable, the
BECAUSE IT IS OUTSIDE THE position-number is the ordinality of the variable in the
BOUND OF THE PARTITION SQLDA. If the string is not the value of a host variable,
RANGE FOR THE LAST PARTITION the position-number is blank.

When a row is inserted, the calculated partition key The statement cannot be processed.
value for the new row must be within the bounds of a
partition. Programmer response
Take one of the following actions based on the reason-
System action code:
Extend the maximum length of the host variable to
Programmer response allow for the expansion that occurs when the string
is converted.
Correct the statement to specify a value for the
partition key that is within the bounds of the last 12
partition of the partitioned table space. Change the convert table to accept the code-point
or the data to eliminate the code-point.
SQLSTATE 16
If the string is described as MIXED data, change its
22525 description or change the string to conform to the
rules for well-formed mixed data.
-330 A STRING CANNOT BE USED
BECAUSE IT CANNOT BE 20
PROCESSED. REASON reason- Correct the conversion procedure.
code, CHARACTER code-point, 24
HOST VARIABLE position-number Delete the SBCS character from the graphic string.
AN error occurred during the processing of a string, 22021
or in the conversion of a string. The type of error is
indicated by the reason-code: -331 CHARACTER CONVERSION
CANNOT BE PERFORMED
8 BECAUSE A STRING, POSITION
Length exception (for example, expansion required position-number, CANNOT BE
for PC MIXED data exceeds the maximum length of CONVERTED FROM source-ccsid TO
the string). target-ccsid, REASON reason-code
12
Invalid code point (for example, use of the Explanation
ERRORBYTE option of SYSSTRINGS).
16 The operation required the conversion from source-
Form exception (for example, invalid MIXED data). ccsid to target-ccsid and a conversion error occurred.
The type of error is indicated by the reason-code:
20
Conversion procedure error (for example, an exit • 8 for length exception (for example, expansion
set the length control field of the string to an required for PC MIXED data exceeds the maximum
invalid value). length of the string).
24 • 12 for invalid code-point (for example, use of the
SBCS character found in string contained in a ERRORBYTE option of SYSSTRINGS).
wchar_t or sqldbchar host variable. • 16 for form exception (for example, invalid MIXED
If the reason-code is 12, code-point is the invalid data).
code point. Otherwise, code-point is either blank or an • 20 for conversion procedure error (for example,
additional reason-code returned by an exit. an exit set the length control field of the
string to an invalid value). You can find the

procedure name in SYSIBM.SYSSTRINGS row with reason-code
INCCSID=source-ccsid and OUTCCSID=target-ccsid Describes the reason codes returned from Db2.
in the TRANSPROC column. Reason codes returned from Db2 begin with 'DSN'
and identify the context in which the conversion
The position-number, if provided (non-zero), is the
was requested. Values other than those that start
ordinality of the output variable in the SQLDA.
with 'DSN' are returned from other Db2 platforms
and are described in the documentation for the
System action platform.
System action
Take one of the following actions based on the reason-
code: Programmer response
8 If the conversion request is correct, see the
Extend the maximum length of the result column information about how to add conversion support.
to allow for the expansion that occurs when the
string is converted.
SQLSTATE
12
Change the conversion table to accept the code- 57017
point, or change the data to eliminate the code- Related concepts
point. Introduction to character conversion (Db2
16 Internationalization Guide)
If the string is described as MIXED data, change its Related tasks
description or change the string to conform to the Setting up Db2 to ensure that it interprets
rules for well-formed MIXED data. characters correctly (Db2 Internationalization
20 Guide)
Correct the conversion procedure. Working with international data (Db2
An alternative to these corrective actions is to provide Installation and Migration)
an indicator variable so that a null value and a warning Related reference
can be returned rather than an error. SYSSTRINGS catalog table (Db2 SQL)
SQLSTATE -333 THE SUBTYPE OF A STRING

VARIABLE IS NOT THE SAME
22021 AS THE SUBTYPE KNOWN AT
Related concepts BIND TIME AND THE DIFFERENCE
CANNOT BE RESOLVED BY
Coded character sets and CCSIDS (Introduction CHARACTER CONVERSION
to Db2 for z/OS)
-332 CHARACTER CONVERSION Explanation

BETWEEN CCSID from-ccsid TO to-
The CCSID in the run time SQLDA is inconsistent
ccsid REQUESTED BY reason-code
with the bind time subtype of the host variable or
IS NOT SUPPORTED
parameter marker. Either the run time description is
BIT and the bind time description was not BIT, or
Explanation the run time description is not BIT and the bind time
description was BIT.
The operation required a conversion between two
different CCSIDs. No conversion support was found.
System action
from-ccsid
Identifies the coded character set of the string to The statement cannot be processed.
be converted.
to-ccsid
Identifies the coded character set to which it must
be converted.

Programmer response • The ON clause cannot contain a subquery.
Change the CCSID in the SQLDA so that the subtype • The ON clause cannot contain an XMLEXISTS
of the host variable is consistent with the bind time predicate.
subtype of the host variable or parameter marker. If • The search-condition of the ON clause of a MERGE
the input data in error is a parameter marker, you can statement cannot contain non-deterministic scalar
use the DESCRIBE INPUT SQL statement to determine functions.
the expected SQLTYPE, SQLLEN and CCSID expected. • A subquery is not allowed in the search-condition of
the ON clause of a MERGE statement.
SQLSTATE
56010 System action
Related concepts The statement cannot be processed.
Coded character sets and CCSIDS (Introduction
to Db2 for z/OS) Programmer response
Character conversion (Introduction to Db2 for Correct the syntax, and reissue the statement.
z/OS)
Related reference
SQLSTATE
DESCRIBE INPUT (Db2 SQL)
42972
-336 THE SCALE OF THE DECIMAL
NUMBER MUST BE ZERO Related concepts
Ways to join data from more than one table
Explanation
XMLEXISTS predicate for querying XML data
The decimal number is used in a context where (Db2 Programming for XML)
the scale must be zero. This can occur when a Related reference
decimal number is specified in a CREATE or ALTER MERGE (Db2 SQL)
SEQUENCE statement for START WITH, INCREMENT
BY, MINVALUE, MAXVALUE, or RESTART WITH. -340 THE COMMON TABLE EXPRESSION
name HAS THE SAME IDENTIFIER
Programmer response AS ANOTHER OCCURRENCE OF
A COMMON TABLE EXPRESSION
Change the decimal number so that there are no non- DEFINITION WITHIN THE SAME
zero digits to the right of the decimal point. STATEMENT
428FA The common table expression name name is used
-338 AN ON CLAUSE IS INVALID in the definition of more than one common table
expressions in the statement. The name used to
describe a common table expression must be unique
Explanation within the same statement.
A statement contains an invalid ON clause. Conditions
that can cause this error include, but are not limited to, System action
violations of the following requirements:
• For a full join, each expression of the predicate must
reference only columns in its own operand tables.
Programmer response
• For a full join, a Db2 11 Unicode column in an
EBCDIC table must not be referenced in the join Correct the error by changing the name of one of the
condition. common table expressions.
• Only VALUE and COALESCE functions are allowed in
the ON clause for full outer joins and full joins. SQLSTATE
• Full outer joins and full joins permit only the = 42726
operator.

-341 A CYCLIC REFERENCE EXISTS Explanation
BETWEEN THE COMMON TABLE
EXPRESSIONS name1 AND name2 The recursive common table expression name
name must include the specification of the column
names following the identifier of the common table
Explanation expression.
The common table expression name1 refers to name2
in a FROM clause within its fullselect and name2 refers System action
to name1 in a FROM clause within its fullselects. Such
forms of cyclic references are not allowed. The statement cannot be processed.

The statement cannot be processed. Add column names following the identifier of the
common table expressions.
Programmer response
SQLSTATE
Remove the cyclic reference from one of the common
table expressions. 42908
-344 THE RECURSIVE COMMON
SQLSTATE TABLE EXPRESSION name HAS
MISMATCHED DATA TYPES OR
42835 LENGTHS OR CODE PAGE FOR
-342 THE COMMON TABLE EXPRESSION COLUMN column-name
name MUST NOT USE SELECT
DISTINCT AND MUST USE UNION Explanation
ALL BECAUSE IT IS RECURSIVE
The recursive common table expression name name
has a column column-name that is referred to in the
Explanation iterative fullselect of the common table expression.
There are two possible explanations: The data type and length are set based on the
initialization fullselect for this column. The result of
• A fullselect within the common table expression the expression for the column column-name in the
name cannot start with SELECT DISTINCT because iterative fullselect has a different data type or length
the common table expression is recursive. that may result in failure to assign the value for the
• A fullselect within the common table expression column.
name specified UNION instead of UNION ALL as
required for recursive common table expressions. System action
System action
Correct the column used in the fullselects of the
Programmer response recursive common table expression so that the
Remove the keyword DISTINCT from the common initialization column matches the iterative columns.
table expression, add the keyword ALL following
UNION, or remove the recursive reference within the SQLSTATE
common table expression.
42825
SQLSTATE -345 THE FULLSELECT OF THE
RECURSIVE COMMON TABLE
42925
EXPRESSION name MUST BE
-343 THE COLUMN NAMES ARE A UNION ALL AND MUST
REQUIRED FOR THE RECURSIVE NOT INCLUDE AGGREGATE
COMMON TABLE EXPRESSION FUNCTIONS, GROUP BY, HAVING,
name ORDER BY, OFFSET, FETCH FIRST,

OR AN EXPLICIT JOIN INCLUDING • More than one reference to the same common
AN ON CLAUSE table expression in the same FROM clause. Such
references are not permitted in recursive common
Explanation table expression.
• A recursive reference in the FROM clause of a
The common table expression name includes a subquery. A recursion cycle cannot be defined using
reference to itself and therefore: a subquery.
• must be the union of two or more fullselects.
• cannot have aggregate functions. System action
• cannot include a GROUP BY clause. The statement cannot be processed.
• cannot include a HAVING clause.
• cannot include an ORDER BY clause. Programmer response
• cannot include an OFFSET clause. Change one of the following:
• cannot include a FETCH FIRST clause. • the fullselect prior to the union operator so that it
• cannot include an explicit join with an ON clause. does not include a recursive reference.
• the FROM clause containing more than one
System action reference to the same common table expression to
just one reference .
• the FROM clause of the subquery so that it does not
reference the common table expression.
Programmer response
Change the common table expression by: SQLSTATE
• making it a union of two or more fullselects. 42836
• removing any aggregate functions, GROUP BY -348 sequence-expression CANNOT BE
clause, HAVING clause, ORDER BY clause, OFFSET SPECIFIED IN THIS CONTEXT
clause, FETCH FIRST clause, or explicit JOIN
including an ON clause.
Explanation
• removing the recursive reference.
The statement contains a NEXT VALUE expression or
SQLSTATE PREVIOUS VALUE expression in an invalid context.
The NEXT VALUE expression or PREVIOUS VALUE
42836
expression cannot be specified in the following
Related concepts contexts:
Queries (Db2 SQL) • Join condition of a full outer join
-346 AN INVALID REFERENCE TO • DEFAULT value for a column in a CREATE TABLE or
COMMON TABLE EXPRESSION ALTER TABLE statement
name OCCURS IN THE FIRST • Column definition that is generated in a CREATE
FULLSELECT, AS A SECOND TABLE or ALTER TABLE statement
OCCURRENCE IN THE SAME FROM
• Materialized query table definition in a CREATE
CLAUSE, OR IN THE FROM CLAUSE
TABLE or ALTER TABLE statement
OF A SUBQUERY
• An as-result-table clause of a CREATE TABLE or
DECLARED GLOBAL TEMPORARY TABLE statement.
Explanation
• Condition of a CHECK constraint
The common table expression name includes an
• Input value-specification for LOAD
invalid reference to itself as described by one of the
following: • CREATE VIEW statement
• A recursive reference in the first fullselect before • Key-expression of an index definition.
the UNION ALL set operator. The first fullselect must • The SELECT list of a subselect that contains a NOT
be an initialization and cannot include a recursive ATOMIC data change statement.
reference.

• An expression that generates the value of an index Explanation
for an array.
The SQL statement cannot be processed because it
The NEXT VALUE expressions cannot be specified in references a column in an invalid context.
the following contexts:
column-name
• CASE expression The name of the column.
• Parameter list of an aggregate function Possible reasons for this error include:
• Subquery in a context in which it is not otherwise
DECFLOAT columns
allowed
A DECFLOAT column cannot be:
• SELECT statement for which the outer SELECT
contains a DISTINCT operator or a GROUP BY clause • Specified as a column of a foreign key in a
referential-constraint clause.
• SELECT statement for which the outer SELECT is
combined with another SELECT statement using a • Specified as a column of a parent key in a
set operator such as UNION, EXCEPT, or INTERSECT REFERENCES clause.
• Join condition of a join • Specified as a column of a partitioning key for
range partitioning.
• Nested table expression
• Defined in a table that has an EDITPROC.
• Parameter list of a table function
• The result data type of a key expression in an
• SELECT clause of the fullselect of an expression in expression-based index must not be DECFLOAT
the SET clause of an UPDATE statement or a distinct type based on the DECFLOAT data
• ORDER BY clause in the SELECT statement type. An intermediate result, of a key expression
• ORDER BY clause in an OLAP specification for an index can be the DECFLOAT data type or a
distinct type based on the DECFLOAT data type.
• IF, WHILE, DO ... UNTIL, or CASE statement in an
SQL routine • Specified as a column in a CREATE TABLE
ORGANIZE BY HASH or ALTER TABLE ADD
• Key-expression of an index definition. ORGANIZE BY HASH statement.
• The select list of a subselect that contains a NOT
LOB columns
ATOMIC data change statement.
A LOB column cannot be:
• The select list of a fullselect that contains an OFFSET
clause. • Defined in a temporary table (created global
temporary table or declared global temporary
table).
System action
• Defined in an accelerator-only table.
The statement cannot be processed. • Defined in a table that has an edit procedure that
is defined with row attribute sensitivity.
Programmer response • Specified as a column of the primary key in a
Remove the reference to the sequence expression and PRIMARY KEY clause.
resubmit the statement. • Specified as a column of a UNIQUE KEY.
• Specified as a column of a parent key in a
SQLSTATE REFERENCES clause.
428F9 • Specified as a column of an index key.
Additionally, the result data type, including the
Related reference intermediate result, of a key-expression for an
Sequence reference (Db2 SQL) index cannot be a LOB data type or a distinct
type based on a LOB data type. However, an
-350 column-name WAS IMPLICITLY OR inline LOB column is allowed in index-expression
EXPLICITLY REFERENCED IN A as the source of a SUBSTR function expression
CONTEXT IN WHICH IT CANNOT or as the first argument of the JSON_VAL
BE USED function, and the LOB data type is allowed as the
intermediate result of the expression.
• Referenced in the first argument of the
JSON_VAL function invocation in the index-

expression of a CREATE INDEX statement, unless • A value must not be specified after the DEFAULT
the column is defined as an inline LOB. keyword for a Db2 11 Unicode column in an
• Specified as a column of a partitioning key for EBCDIC table.
range partitioning. • NOT PADDED must not be specified for an index
• Referenced by the definition of a column mask or for an EBCDIC table if the table contains a Db2
a row permission. 11 Unicode column.
• Defined as a column mask. • A UNIQUE or PRIMARY KEY clause must not be

specified for a Db2 11 Unicode column in an
• Referenced in a period specification or period EBCDIC table.
clause.
VARBINARY columns
• Specified as a column in a CREATE TABLE
A VARBINARY column can not be specified as
ORGANIZE BY HASH or ALTER TABLE ADD
a column of an index key when DESC is also
ORGANIZE BY HASH statement.
specified.
Hidden columns XML columns
A hidden column cannot be specified in a key An XML column cannot be:
expression for an index.
• Specified as a column of the primary key in a
Result table columns
PRIMARY KEY clause.
• A ROWID, LOB, or XML data type cannot • Specified as a column of a UNIQUE KEY.
be the data type of a column in the result
table of an as-result-table clause of a CREATE • Specified as a column of a foreign key in a
TABLE or DECLARE GLOBAL TEMPORARY TABLE referential-constraint clause.
statement. • Specified as a column of a parent key in a
• A security label column column-name exists in REFERENCES clause.
the result table of the as-result-table clause; • Specified as a column of a partitioning key for
however, it is not the only security label column range partitioning.
in that result table. A table can be defined only • Defined in a temporary table (created global
with a single security label column. temporary table or declared global temporary
Security label columns table).
A security label column cannot be: • Defined in a table that has an edit procedure that
• Specified as a column of a foreign key in a is defined with row attribute sensitivity.
referential-constraint clause. • Specified as a column of an index key.
• Specified in a REFERENCES clause. Additionally, the result data type, including the
intermediate result, of a key expression for an
• Specified in a key expression for an index. index cannot be an XML data type. For an
Timestamp with time zone columns XML index, only XML columns can be specified,
A timestamp with time zone column cannot be and the result type of the index key can be
specified as a column of a partitioning key for DECFLOAT.
range partitioning. • Specified with the SET DEFAULT or DROP
A Db2 11 Unicode column in an EBCDIC table DEFAULT clause.
A Db2 11 Unicode column in an EBCDIC table • Referenced by the definition of a column mask or
cannot be specified in the following: a row permission.
• An ALTER TABLE statement in an ADD COLUMN • Defined as a column mask.
clause if the table is already defined with an • Specified as a column in a CREATE TABLE
EDITPROC. ORGANIZE BY HASH or ALTER TABLE ADD
• In a UNIQUE, PRIMARY KEY, REFERENCES, ORGANIZE BY HASH statement.
FOREIGN KEY, or ORGANIZE BY HASH clause. • Specified in an ALTER TABLE statement in a
This error can also be issued for the following: DROP COLUMN clause.
• An EDITPROC clause cannot be specified if the DOCID columns

table contains a Db2 11 Unicode column in an A DOCID column cannot be specified in the
EBCDIC table. following:
• An ALTER TABLE statement in an ALTER COLUMN
clause.

• An ALTER TABLE statement in a DROP COLUMN For an array type, this value is the position
clause. number of the first element in the SQLDA with
an unsupported data type for the elements of the
System action array.
Either the application requester or the application
server does not have support for this data type. This
error can occur only in a client/server environment.
Programmer response
Correct the syntax, and resubmit the statement. System action
SQLSTATE
-351 AN UNSUPPORTED SQLTYPE WAS Change the SQLDA to exclude the unsupported data
ENCOUNTERED IN POSITION type.
position-number OF THE SELECT-
LIST SQLSTATE
56084
Explanation
position-number -353 FETCH IS NOT ALLOWED,
The position of the first element in the SQLDA with BECAUSE CURSOR cursor-name
an unsupported data type. HAS AN UNKNOWN POSITION
This error can occur when an application requester or

application server does not have support for this type.
Explanation
The cursor position for cursor-name is unknown. The
System action previous multiple-row-fetch for cursor cursor-name
resulted in an error in the middle of processing
The statement cannot be processed. multiple rows that were retrieved from Db2. One or
more of the requested rows could not be returned to
Programmer response the program following the error, leaving the position of
the cursor unknown.
Change the statement to exclude the unsupported
data type. For a select statement, remove the names The error might have been detected at the requester.
of any columns in the select-list with the unsupported For example, a row with a null value was returned
data types. to an application, but no indicator variable was
provided. A subsequent FETCH statement would result
in SQLCODE -353. If an indicator had been provided, a
SQLSTATE positive SQLCODE would have been returned and all of
56084 the rows retrieved from Db2 could have been returned
to the application program.
-352 AN UNSUPPORTED SQLTYPE WAS
ENCOUNTERED IN POSITION
position-number OF THE INPUT-
System action
LIST The statement cannot be processed. The cursor
position is not changed.
Explanation
The input SQLDA for an OPEN, EXECUTE, FETCH, or
Programmer response
CALL statement contains an unsupported SQLTYPE for Close and reopen the cursor to reset the cursor
a parameter. position. For scrollable cursors, you can change the
position-number FETCH statement to specify one of the other fetch
The position of the first element in the SQLDA with orientations. For example, you can modify the FETCH
an unsupported data type. statement by specifying one of the following fetch
orientations:
• BEFORE or AFTER

• row-positioned fetch orientations: FIRST, LAST, or be used to determine if all the requested rows were
ABSOLUTE to establish a valid row cursor and fetch a fetched or if a partial rowset was returned.
row of data
• rowset-positioned fetch orientations: FIRST SQLSTATE
ROWSET, LAST ROWSET, or ROWSET STARTING AT
ABSOLUTE to establish a valid rowset cursor position 22537
and fetch multiple rows of data -355 A LOB COLUMN IS TOO LARGE TO
Alternately, change the application to correct the error BE LOGGED
that originally occurred. For example, if the error was
issued because an indicator was not provided, change Explanation
the application to provide an indicator.
One of the following has occurred:
SQLSTATE • a CREATE TABLE statement for an auxiliary table

stores a BLOB, CLOB or DBCLOB column whose
24513 length exceeds 1 gigabyte but whose associated LOB
-354 A ROWSET FETCH STATEMENT table space was defined with the LOG YES attribute
MAY HAVE RETURNED • an ALTER TABLESPACE statement of a LOB table
ONE OR MORE ROWS space specifies the LOG YES clause but the auxiliary
OF DATA. HOWEVER, ONE table in the LOB table space stores a BLOB or
OR MORE NON-TERMINATING CLOB column whose length exceeds 1 gigabyte
ERROR CONDITIONS WERE or a DBCLOB column whose length exceeds 500
ENCOUNTERED. USE THE GET megabyte characters
DIAGNOSTICS STATEMENT FOR
MORE INFORMATION REGARDING System action
THE CONDITIONS THAT WERE
ENCOUNTERED The statement cannot be processed.

A rowset FETCH statement encountered one or Either change the attribute of the LOB table space to
more non-terminating error conditions. One or more LOG NO or drop the base table, and re-create it with
warnings might also have been encountered. Use the columns of an acceptable length for logging.
GET DIAGNOSTICS statement to obtain information
about the conditions that occurred, and to determine SQLSTATE
if data was returned. It is possible that one or more
rows of data were returned. In cases where the row 42993
information returned for the row that encountered the
-356 COLUMN OR KEY EXPRESSION
condition is incomplete, use of the data for the row
expression-number IS NOT VALID,
that encountered the condition, such as displaying or
printing the data, is not recommended.
Explanation
System action
The CREATE INDEX statement cannot be processed
Db2 processed the statement successfully, but with
because a column or key expression is not valid.
at least one non-terminating error. Additionally, the
fetching of some rows might have encountered expression-number
warnings. The number of the invalid column or key
expression.
Programmer response reason-code
A numeric value that indicates the reason for the
Analyze the conditions to determine whether follow- failure.
up actions are needed. The GET DIAGNOSTICS
statement can be used to determine which additional 1
actions might be necessary. Contains a subquery.
Attention: It is possible that an end of data condition

was detected. SQLERRD3 and GET DIAGNOSTICS can

2 columns. For more information, see Unicode
Does not contain at least one reference to a columns in EBCDIC tables (Db2 SQL).
column. 116
3 In an invocation of the JSON_VAL built-in
References a special register. function in a key-expression for an index, the
4 third argument of the function must end in ':na',
Includes a CASE expression. to indicate that the first argument does not
contain a JSON array.
5
Includes a user-defined function. 117
In an invocation of the JSON_VAL built-in
6 function in a key-expression for an index, if
Appears more than once in the index. the first argument of the function is a column,
7 that column must be contained in a table in a
References a qualified column name. partition-by-growth table space.
8 118
References a column that is defined with a If there is an invocation of the JSON_VAL built-
FIELDPROC. in function in a key-expression for an index, the
9 CREATE INDEX statement must not reference a
References the LOWER or UPPER function LOB column other than the LOB column that is
without a locale name or the input string- the argument to the JSON_VAL function. Such
expression is FOR BIT DATA. a CREATE INDEX statement can refer only to a
single LOB column.
10
References the TRANSLATE function without 119
an output translation table. If a key-expression for an index contains
an invocation of the JSON_VAL function, the
11 invocation must be the outermost expression
The encoding scheme of the result of a column for key-expression.
or key expression is different than the CCSID
encoding scheme of the table.
System action
12
The SUBSTR built-in function is allowed to The statement cannot be processed.
reference the inline portion of a LOB column
in the specified context. In addition, the Programmer response
START and LENGTH arguments of the SUBSTR
function must be constants. Correct the error in the key expression, and reissue the
statement.
13
References one of the following built-in
functions: SQLSTATE
• VERIFY_GROUP_FOR_USER 429BX
• VERIFY_TRUSTED_CONTEXT_ -359 THE RANGE OF VALUES FOR THE
ROLE_FOR_USER IDENTITY COLUMN OR SEQUENCE
• VERIFY_ROLE_FOR_USER. IS EXHAUSTED
14
Contains an expression that requires the use of Explanation
an implicit time zone value. For example, the Db2 attempted to generate a value for an identity
key expression might include an explicit cast of column or a sequence object. However, all allowable
a TIMESTAMP WITHOUT TIME ZONE value to a values have already been assigned.
TIMESTAMP WITH TIME ZONE value.
15
System action
References a global variable.
25 The statement cannot be processed.
A specification for an index on an EBCDIC table
includes one or more Db2 11 Unicode columns
and one or more Db2 12 or later Unicode

Programmer response IN POSITION value-position IS
NOT VALID.
Take one of the following actions:
• For an identity column, redefine the table with a Explanation
larger range of values for the identity column. If
a MAXVALUE or MINVALUE specification has been The value of DEFAULT (-5) or UNASSIGNED (-7) was
made that limits the range of values to be less than used for the extended indicator variable in a context
the range for the data type of the column, then where it is not allowed. These values are allowed
the column can be altered to expand the range of as indicator variables only in INSERT, UPDATE, and
valid values. Otherwise, the identity column must MERGE statements when the host variable provides
be re-created, which requires that the table be re- the source value for a column value.
created. First, drop the existing table; then, re-create value-position
the table with a different data type for the identity Identifies the location of the extended indicator
column, specifying a data type that has a larger variable value.
range of values than the current data type for the
identity column. When extended indicator variables are enabled:
• For a sequence object, redefine the sequence with a • An expression must not be more complex than
larger range of values. If a MAXVALUE or MINVALUE a reference to a single host variable if the
specification has been made that limits the range of indicator is set to the extended indicator values of
values to be less than the range for the data type, DEFAULT (-5) or UNASSIGNED (-7), except that a
then the sequence can be altered to expand the CAST specification is allowed when the following
range of valid values. Otherwise, the sequence must conditions are met:
be re-created using DROP SEQUENCE and CREATE
– The source of the CAST specification is a single
SEQUENCE to cover a larger range of values.
host variable.
– The data attributes (data type, length, precision,
SQLSTATE and scale) of the host variable are the same as the
23522 result of the cast specification.
• The extended indicator variable values of DEFAULT
-363 THE EXTENDED INDICATOR
(-5) or UNASSIGNED (-7) must not be used in:
VARIABLE VALUE FOR
PARAMETER position-number IS – An expression that involves more than a host
OUT OF RANGE. variable, or a host variable that is explicitly cast.
– Any expression other than:
Explanation - The set assignment list of an UPDATE operation.
The extended indicator variable value is invalid. - The values list of an INSERT operation.
position-number - The expression's corresponding places in a
The ordinal position of parameter marker. MERGE statement.
When extended indicator variables are enabled, all - The source-value parameter of a MERGE
negative input indicator variable values must be in the statement.
-1 to -7 (inclusive) range. - The select list of an INSERT statement in the
FROM clause of the SELECT statement.
System action
The statement cannot be processed. System action
System programmer response
Correct the value, and reissue the statement. System programmer response
Change the value of the extended indicator variable to
SQLSTATE an allowable value for the context in which it is used
22010
SQLSTATE
-365 USE OF THE VALUE OF
EXTENDED INDICATOR VARIABLE 22539

Related reference Explanation
The definition or change that was specified for the
-372 ONLY ONE ROWID, IDENTITY, column or the SQL variable included the DEFAULT
ROW CHANGE TIMESTAMP, ROW clause. However, DEFAULT is not supported for the
BEGIN, ROW END, TRANSACTION column data type or SQL variable.
START ID, SECURITY LABEL, name
OR DATA CHANGE OPERATION The name of the column or SQL variable.
COLUMN IS ALLOWED IN A TABLE
Possible reasons for this error include the following
situations:
Explanation
• A CREATE TABLE or ALTER TABLE statement
An attempt was made to modify or create a table to attempted to define one of the following columns
have two columns of the same type when only one with the DEFAULT clause:
column of that type is permitted in a table.
– Identity column
A table cannot have two or more columns of the
– ROWID column
following types:
– XML column
• Explicitly created ROWID
– Row change timestamp column
• Implicitly hidden ROWID
– Security label column
• Identity
– Row begin column
• ROW CHANGE TIMESTAMP
– Row end column
• ROW BEGIN
– Transaction start ID column
• ROW END
– Generated expression column
• TRANSACTION START ID
• The declaration of an SQL variable specified the
• Security label DEFAULT clause, and the data type of the SQL
• DATA CHANGE OPERATION variable is ROWID or XML.
• A SET statement specified DEFAULT for the value of
System action a ROWID column.
System action
For a CREATE TABLE statement, select only one
column to have the specified attribute. Programmer response
For an ALTER TABLE statement, a column with one of Remove the DEFAULT clause and resubmit the
the specified types already exists for the table. Do not statement.
attempt to add another column with the same data
type. SQLSTATE
42623
SQLSTATE
Related reference
428C1
Related reference ALTER TABLE (Db2 SQL)
CREATE TABLE (Db2 SQL) SET assignment-statement (Db2 SQL)
ALTER TABLE (Db2 SQL) compound-statement (Db2 SQL)
-373 DEFAULT CANNOT BE SPECIFIED -374 THE CLAUSE clause HAS NOT
FOR COLUMN OR SQL VARIABLE BEEN SPECIFIED IN THE
name CREATE OR ALTER FUNCTION
STATEMENT FOR LANGUAGE SQL
FUNCTION function-name BUT AN
EXAMINATION OF THE FUNCTION

BODY REVEALS THAT IT SHOULD specific-name
BE SPECIFIED The specific name. If specific-name is an empty
string, then the function resolved to the built-in
Explanation function identified by function-name.
If the error is for an invalid use of UNNEST,
This message might be issued if the following
specific-name is *N.
conditions apply:
Possible causes for this error include:
• You must specify NOT DETERMINISTIC if either of
the following conditions apply within the body of the • A scalar or aggregate function is referenced where
function: only a table function is allowed (such as in the FROM
clause of a query).
– Db2 invokes a function that has the NOT
DETERMINISTIC attribute specified. • A table function is referenced where only a scalar
or aggregate function is allowed (such as in an
– Db2 accesses a special register.
expression).
• You must specify MODIFIES SQL DATA if the body
• A function is referenced in a SOURCE clause of a
of the function defined with LANGUAGE SQL can
CREATE FUNCTION statement, but a source function
modify SQL data or if it calls a function or a
cannot be defined on that function (or on that
procedure that can modify SQL data.
specific function signature).
• You must specify READS SQL DATA if the body of
• Function XMLMODIFY is referenced where it is not
the function defined with LANGUAGE SQL contains
the topmost expression on the right side of the SET
a subselect, or if it invokes a function that can read
assignment clause in an update.
SQL data.
• A generic table function is referenced, but a typed-
• You must specify EXTERNAL ACTION if the body of
correlation-clause is not specified.
the function defined with LANGUAGE SQL invokes a
function that has the EXTERNAL ACTION attribute • A typed-correlation-clause is specified, but the
specified. referenced function is not a generic table function.
• UNNEST was specified in an unsupported context.
System action • A CORRELATION, COVARIANCE,
The statement cannot be processed. COVARIANCE_SAMP or ARRAY_AGG set function is
referenced where a CUBE, ROLLUP or GROUPING
SETS clause exists in the same SQL statement.
Programmer response
• ARRAY_AGG is referenced in a fullselect that
Specify the correct clause or change the function of includes an ORDER BY clause or a DISTINCT clause.
the body. • ARRAY_AGG or LISTAGG is referenced in a fullselect
that includes an ORDER BY clause or a DISTINCT
SQLSTATE clause.
428C2
System action
-390 OBJECT object-name, SPECIFIC
NAME specific-name, IS NOT The statement cannot be processed.
VALID IN THE CONTEXT WHERE IT
IS USED Programmer response
For a function, ensure that the correct function name
Explanation and arguments are specified and that the SQL path
One of the following situations occurred: includes the schema where the correct function is
defined. You might need to change the function name,
• A function resolved to a specific function that is not arguments, or SQL path (using SET CURRENT PATH or
valid in the context where it is used. the PATH bind option), or change the context in which
• UNNEST was used in a context in which it is not the function is used.
allowed.
object-name SQLSTATE
The name of the object. 42887

Related concepts XML data in successive fetches, or to request
Functions (Db2 SQL) binary XML data in successive fetches.
Related reference
table-reference (Db2 SQL) SQLSTATE
42855
-392 SQLDA PROVIDED FOR CURSOR
cursor-name HAS BEEN CHANGED Related reference
FROM THE PREVIOUS FETCH CURRENT RULES (Db2 SQL)
(reason-code)
-393 THE CONDITION OR CONNECTION
Explanation NUMBER IS INVALID
The application has requested incompatible returns

from successive FETCH statements.
Explanation
cursor-name The value of the CONDITION or CONNECTION number
The name of the cursor. that was specified in the GET DIAGNOSTICS statement
is either less than zero, or greater than the number of
reason-code available diagnostics.
A numeric value that indicates the reason for the
failure. Possible values are:
System action
1
The application is running with DB2 rules, and The statement cannot be processed.
has requested that LOB data be returned as a
LOB in one FETCH statement, and as a locator Programmer response
in another FETCH statement. This request is
not permitted. Correct the value of the CONDITION or CONNECTION
number, while ensuring that the number is between 1
2
and the value of the NUMBER statement-information
The application has requested textual XML
item or GET DIAGNOSTICS. Resubmit the GET
in one FETCH statement, and binary XML in
DIAGNOSTICS CONDITION or GET DIAGNOSTICS
another FETCH statement. This request is not
CONNECTION statement.
permitted.
If the cursor is a result set returned by a stored SQLSTATE
procedure called by the application, then the
application error might result from a mismatch with 35000
the last FETCH performed by the stored procedure.
-396 object-type object-name
ATTEMPTED TO EXECUTE AN SQL
System action STATEMENT DURING FINAL CALL
PROCESSING
The statement is not processed, and the connection is
terminated.
Explanation
Programmer response A user-defined function named object-name was
invoked and attempted to execute an SQL statement
Take the action that corresponds to the reason-code
(other than CLOSE CURSOR) during final call
value:
processing, but the statement is not allowed.
1
For a mismatch involving LOB and locator: Either System action
do not use DB2 rules, or modify the application
so that it does not change the data type code The SQL statement cannot be executed.
from LOB to locator (or the reverse) in the SQLDA
between successive fetches. Programmer response
2
For a mismatch involving textual XML and binary Change the definition of the function to not issue SQL
XML: Change the application to request textual statements during final call processing.

-397 GENERATED IS SPECIFIED AS
PART OF A COLUMN DEFINITION, Programmer response
BUT IT IS NOT VALID FOR THE Change the statement to either return LOB data, or
DEFINITION OF THE COLUMN change the target host variable to not be a locator.
In a CREATE TABLE statement or ALTER TABLE 428D2
statement, GENERATED was specified for a column
type that does not support generated values. -399 INVALID VALUE ROWID WAS
GENERATED can be specified only for a column with SPECIFIED
one of the following data types:
• Row ID Explanation
• Distinct type that is based on a row ID When inserting into a table, a value specified for
• Row change timestamp a ROWID column was invalid. Only row ID values
previously generated by Db2 are valid.
• Identity column
• Row-begin column
System action
• Row-end column
• Transaction-start-ID column
• Generated expression column System programmer response
Do not attempt to generate any value into a ROWID
System action
column. Insertion into ROWID columns is supported
The statement cannot be processed. for purposes of Data Propagation, where Db2 has
previously generated the row ID values. Only row ID
Programmer response values previously generated by Db2 can be used as
values for insertion into a row ID column. Alternatively,
Correct the statement. Either remove the GENERATED insert the row specifying DEFAULT for the ROWID
clause or change the definition of the column to one of column or remove the ROWID column from the insert
the types that can be generated. column-list.
You could also use the OVERRIDING clause as
SQLSTATE a possible solution for this situation. For more
428D3 information about the OVERRIDING USER VALUE
clause, see INSERT (Db2 SQL).
Related reference
CREATE TABLE (Db2 SQL) SQLSTATE
ALTER TABLE (Db2 SQL)
22511
-398 A LOCATOR WAS REQUESTED -400 THE CATALOG HAS THE MAXIMUM
FOR HOST VARIABLE NUMBER NUMBER OF USER DEFINED
position-number BUT THE INDEXES
VARIABLE IS NOT A LOB
Explanation
Explanation
No more than 500 user-defined indexes can be
The application requested that a locator be returned created in the catalog database.
from host variable number position-number. A locator
can only be used with LOB data, and the requested
data is not a LOB. System action

If this index must be created, another user-defined The statement cannot be processed.
index on the catalog must be dropped. After that index
is dropped, this statement can be executed. Programmer response
Examine and correct the syntax of the SQL statement
SQLSTATE
so that all operands of the specified function or
54027 operator are valid. A valid operand is either numeric,
or is capable of being implicitly cast to a numeric data
-401 THE DATA TYPES OF THE
type.
OPERANDS OF AN OPERATION
ARE NOT COMPATIBLE
SQLSTATE
Explanation 42819
An operation cannot be processed for one of the
-404 THE SQL STATEMENT SPECIFIES A
following reasons:
STRING THAT IS TOO LONG
• The data types of the operands must be compatible
but at least one pair of data types is not compatible. Explanation
• An operation contains a mixture of numeric and non-
numeric operands. An INSERT, UPDATE, MERGE, CALL, VALUES INTO,
SET, parameter, host variable, or transition variable
• One of the operands is a column defined with a statement specifies a value that is longer than the
field procedure, and another column operand is not maximum length string that can be stored in the target
defined with the same field procedure. If one column column or index key.
of arithmetic or comparison operation is defined with
a field procedure, other columns in the operation
must be defined with the same field procedure. System action
System action
Check the length of the target column, parameter, host
Programmer response variable, transition variable, or index key and correct
the program or SQL statement so that the length of the
Check the data types of all operands to ensure that string does not exceed that maximum. For example,
their data types are comparable and compatible with you could use the SUBSTR function to shorten the
their usage in the statement. string.
If all the operands of the SQL statement are correct,
then, if a view is being accessed, check the data types SQLSTATE
of all the operands in the view definition.
22001
SQLSTATE -405 THE NUMERIC CONSTANT constant
CANNOT BE USED AS SPECIFIED
42818 BECAUSE IT IS OUT OF RANGE
-402 AN ARITHMETIC FUNCTION OR
OPERATOR function-operator IS Explanation
APPLIED TO CHARACTER OR
DATETIME DATA The numeric constant is not in the proper range.
The proper ranges for SQL values are as follows:
Explanation • 5.4E-79 to 7.2E+75 for FLOAT values
An invalid operand has been specified for the • -(1031 -1) to +(1031 -1) for DECIMAL values
arithmetic function or operator.
• -2147483648 to 2147483647 for INTEGER values
function-operator • -32768 to +32767 for small integer (SMALLINT)
The name of the arithmetic function or operator. values

• -9.999999999999999x10-383 to SQLSTATE
9.999999999999999x10384 for DECFLOAT(16)
values 22003
• -9.999999999999999999999999999999999x10-6 Related concepts
143 to Big integer (BIGINT) (Db2 SQL)
9.999999999999999999999999999999999x10614 Related reference
4 for DECFLOAT(34) values
• - 9223372036854775808 to Related information
+9223372036854775807 for big integer (BIGINT) -405
values THE NUMERIC CONSTANT constant CANNOT BE
USED AS SPECIFIED BECAUSE IT IS OUT OF
System action RANGE
The statement cannot be processed. -407 AN UPDATE, INSERT, OR SET
VALUE IS NULL, BUT THE OBJECT
Programmer response COLUMN column-name CANNOT
CONTAIN NULL VALUES
The value of constant should be reduced to the
appropriate size for this data type.
Explanation
SQLSTATE One of the following conditions occurred:
42820 • A null insert or update value was specified for a
column defined as NOT NULL.
-406 A CALCULATED OR DERIVED
NUMERIC VALUE IS NOT WITHIN • A SET transition variable statement specified a NULL
THE RANGE OF ITS OBJECT value for column defined as NOT NULL without the
COLUMN WITH DEFAULT clause in the table definition.
• The update or insert value was DEFAULT, but the
object column was declared as NOT NULL without
Explanation
WITH DEFAULT in the table definition. Consequently:
A value derived or calculated during processing of the
– A default value of NULL cannot be inserted into
SQL statement was outside the range of the data type
that column.
of its object column. This problem might have arisen
for one of the following reasons: – An update cannot set default values of NULL in
that column.
• The values occurring in the object column were out
of range. – A SET transition variable statement in a trigger
cannot set default values of NULL in that column.
• The SQL operation performed was not appropriate
for the values in the object column. • The column name list for the INSERT statement
omits a column declared NOT NULL and without
• A DECIMAL(19,0) column is altered to BIGINT, but a WITH DEFAULT in the table definition.
value in the column is outside the range of BIGINT.
• The view for the INSERT statement omits a column
declared NOT NULL and without WITH DEFAULT in
System action the base table definition.
The statement cannot be processed. • A null insert value was specified for a ROWID
column.
Programmer response
See the explanation of SQLCODE -405 for allowed
System action
ranges for numeric data types. The statement cannot be processed. The 'column-
name' might be returned in the SQLCA, depending on
If the error occurred while accessing a table column
the syntax of the SQL statement in which the error was
that was altered from DECIMAL(19,0) to BIGINT,
detected.
alter the column data type back to DECIMAL(19,0)
and refer description of the ALTER TABLE statement
for information about how to change DECIMAL(19,0)
columns to BIGINT.

Examine the definition of the object table to determine Examine the SQL statement and the current definition
which columns of the table have the NOT NULL for the object table, procedure, user-defined function,
attribute or have a type of ROWID, and correct the SQL host variable, or SQL variable, and ensure that the
statement accordingly. variable, constant, or result of an expression that is
assigned to the object has the proper data type.
SQLSTATE If the target is a result set locator, the application
might have tried to explicitly assign an invalid locator
23502
value to a result set locator. Use the ASSOCIATE
-408 THE VALUE IS NOT COMPATIBLE LOCATORS statement to get a valid locator value for
WITH THE DATA TYPE OF ITS a result set into a locator variable. Then, reference the
TARGET. TARGET NAME IS name result set locator in an ALLOCATE CURSOR statement.
A statement failed required assignment rule checking. 42821
name -409 INVALID OPERAND OF A COUNT
The name of the target of the assignment. FUNCTION
The data type that is to be assigned is incompatible
with the declared data type of the assignment target. Explanation
Both data types must be:
The operand of the COUNT or COUNT_BIG function in
• Numeric or character the statement violates SQL syntax. A common error is
• Character (see restriction) a column name or other expression without DISTINCT.
• Graphic (see restriction)
System action
• Dates or character (see restriction)
• Times or character (see restriction) The statement cannot be processed.
• Timestamps or character (see restriction)

Programmer response
• Row IDs
• The same distinct types
• XML
SQLSTATE
• Result set locator
42607
• Table locator
Related reference
Restrictions:
COUNT (Db2 SQL)
• Dates, times, and timestamps cannot be assigned to COUNT_BIG (Db2 SQL)
a character column that has a field procedure.
• Character and graphic data types are compatible -410 A NUMERIC VALUE value IS TOO
when using Unicode. LONG, OR IT HAS A VALUE THAT IS
• An array value with a user-defined array type can be NOT WITHIN THE RANGE OF ITS
assigned only to an array variable that is defined as DATA TYPE
the same user-defined array type.
Explanation
The rules for assigning an array value without a user-
defined array type to an array variable depend on the The specified value is too long. A floating-point string
statement that specifies the assignment. See Array has a maximum length of 30 characters. A decimal
type assignments (Db2 SQL) for more information. floating-point string has a maximum length of 42
characters.
System action
System action

Programmer response SQLSTATE
Correct the indicated string value. 22003
-414 A LIKE PREDICATE IS INVALID
SQLSTATE BECAUSE THE FIRST OPERAND IS
42820 NOT A STRING
-412 THE SELECT CLAUSE OF A

Explanation
SUBQUERY SPECIFIES MULTIPLE
COLUMNS The data type of the first operand of the LIKE predicate
must be a character string, graphic string, or binary
Explanation string.
In the context in which it was used in the SQL

System action
statement, the subquery can have only one column
specified in its SELECT clause. The statement cannot be processed.

The statement cannot be processed. Specify the predicate so that the data type of each
operand is a character string or a graphic string.
Programmer response
SQLSTATE
Correct the syntax of the SQL statement.
42824
SQLSTATE -415 THE CORRESPONDING COLUMNS,
42823 column-number, OF THE
OPERANDS OF A SET OPERATOR
Related concepts ARE NOT COMPATIBLE
Queries (Db2 SQL)
The data types of the corresponding columns of a
subselect (Db2 SQL)
UNION, EXCEPT, or INTERSECT set operator are not
compatible, or the corresponding columns do not have
-413 OVERFLOW OR UNDERFLOW
the same field procedure. The relative position of the
OCCURRED DURING NUMERIC
value in the select list is column-number.
DATA TYPE CONVERSION
This error is issued if one of the columns is a distinct
Explanation type, and the other column is not a distinct type, or
the other column is a different distinct type. This error
During processing of the SQL statement, an overflow code is also issued if one column is defined with a field
or underflow condition arose when converting from procedure, and the other column is not defined with
one numeric type to another. Numeric conversion is the same field procedure. If corresponding columns
performed according to the standard rules of SQL. have field procedures, they must both be defined with
the same field procedure.
System action
System action
retrieved, updated, or deleted. The statement cannot be processed.

Examine the syntax of the SQL statement to determine Check the data types of the specified columns and
the cause of the error. If the problem is data- correct the statement containing the set operator
dependent, it might be necessary to examine the data to ensure that all corresponding columns have
processed at the time of the error. comparable column descriptions. A CAST specification

can be used to make the data type of the columns Explanation
compatible.
The statement string specified as the object of a
PREPARE contains a predicate or expression where
SQLSTATE parameter markers have been used as operands of the
42825 same operator—for example: ? > ?
Related concepts This syntax is not permitted.

Rules for result data types (Db2 SQL)
Restrictions when using distinct types with System action
UNION, EXCEPT, and INTERSECT (Db2 The statement cannot be processed.
Application programming and SQL)
Related reference
Programmer response
fullselect (Db2 SQL)
Correct the logic of the application program so that
-416 AN OPERAND OF A SET OPERATOR this syntax error does not occur.
CONTAINS A LONG STRING
COLUMN
SQLSTATE
Explanation 42609
Related concepts
The UNION, EXCEPT, or INTERSECT set operator that
you specified in the SQL statement could not be Variables (Db2 SQL)
performed because one of the tables participating in References to SQL parameters and variables
the union contains a long string column. The operands (Db2 SQL)
of a set operator that does not include the ALL Related reference
keyword cannot contain long string columns. PREPARE (Db2 SQL)
System action -418 A STATEMENT STRING TO

BE PREPARED CONTAINS AN
The statement cannot be processed. INVALID USE OF PARAMETER
MARKERS
Programmer response
The implied function is not supported by Db2. Explanation
The statement cannot be executed because a
SQLSTATE parameter marker has been used in an invalid way.
42907 Examples of places where parameter markers cannot

be used:
Related concepts
• As an argument to some built-in functions.
Rules for result data types (Db2 SQL)
Character and graphic string operands (Db2 • In the SELECT list of a scalar fullselect that is the
SQL) sole argument of a scalar function.
Related reference • In a concatenation operation.
Limits in Db2 for z/OS (Db2 SQL) • In the string expression of an EXECUTE IMMEDIATE
fullselect (Db2 SQL) SQL statement.
• In a result-expression in any CASE expression when
-417 A STATEMENT STRING TO all the other result-expressions are either NULL or
BE PREPARED INCLUDES untyped parameter markers.
PARAMETER MARKERS AS THE
OPERANDS OF THE SAME • In a key-expression of an index definition.
OPERATOR • As an argument to an XMLEXISTS predicate.
System action

Programmer response ACCEPTABLE TO THE function-
name FUNCTION
Correct the logic of the application program so
that this error does not occur. See the discussion
of the PREPARE statement for information about Explanation
the proper usage of parameter markers within A string argument did not conform to the requirements
SQL statements and for EXECUTE IMMEDIATE SQL of the function. For example, a character string passed
statement restrictions. The PREPARE statement to the DECIMAL function did not conform to the rules
description includes tables that describe contexts for forming an SQL integer or decimal constant.
where untyped parameter markers are supported
in expressions, predicates, and statements. A CAST If the error is issued for an implicit or explicit cast,
specification can be used in some cases to explicitly the function-name token contains the name of the
assign attributes to a parameter marker. cast's target data type. For implicit cast where a
character-string or graphic-string value is compared
with a numeric value, Db2 implicitly converts the string
SQLSTATE value to DECFLOAT(34) so the function-name function
42610 will have a DECFLOAT value.
Related reference
PREPARE (Db2 SQL)
System action
-419 THE DECIMAL DIVIDE OPERATION
IS INVALID BECAUSE THE RESULT
WOULD HAVE A NEGATIVE SCALE
Programmer response
Change the argument value so that it conforms to the
Explanation requirements of the function.
The decimal division is invalid because it will result in a

negative scale.
SQLSTATE
22018
System action Related reference
The statement cannot be processed. No data was Built-in functions (Db2 SQL)
retrieved, updated, or deleted. DECIMAL or DEC (Db2 SQL)
-421 THE OPERANDS OF A SET

Programmer response
OPERATOR DO NOT HAVE THE
Examine the precision and scale of all columns that SAME NUMBER OF COLUMNS
might have participated in a decimal division. Note
that an integer or small integer value might have been Explanation
converted to decimal for this calculation.
The operands of a set operator, such as UNION,
A YES value for the DECDIV3 subsystem parameter EXCEPT, or INTERSECT, must have the same number
specifies that the scale of the result of a decimal of columns.
division is never less than 3.
System action
SQLSTATE
42911
Related concepts Programmer response
Decimal division (Db2 SQL)
Correct the SQL statement so that there are exactly
Related reference
the same number of columns.
MINIMUM DIVIDE SCALE field (DECDIV3
subsystem parameter) (Db2 Installation and
Migration) SQLSTATE
42826
-420 THE VALUE OF A STRING
ARGUMENT WAS NOT

-423 INVALID VALUE FOR LOCATOR IN at which updates are not allowed. A dynamic COMMIT
POSITION position-# or COMMIT_ON_RETURN can be issued only while
connected to a location at which updates are allowed.
Explanation
System action
The value specified in a result set locator host variable,
a LOB locator host variable, or a table locator that is The statement cannot be processed. No COMMIT is
specified at position position-# in the locator variable performed.
list of the SQL statement does not identify a valid
result set locator, LOB locator variable, or table locator, Programmer response
respectively.
The IMS or CICS protocols should be used to commit
work in these environments.
System action
2D528
Programmer response
-427 DYNAMIC ROLLBACK NOT VALID
For a result set locator there are two common causes
AT AN APPLICATION SERVER
for the error:
WHERE UPDATES ARE NOT
• The host variable used as a result set locator was ALLOWED
never assigned a valid result set locator value.
Result set locator values are returned by the Explanation
DESCRIBE PROCEDURE and ASSOCIATE LOCATORS
statements. Make sure the value in your host An application executing using DRDA protocols has
variable is obtained from one of these statements. attempted to issue a dynamic ROLLBACK statement
• Result set locator values are only valid as long as while connected to a location at which updates are
the underlying SQL cursor is open. If a commit or not allowed. A dynamic ROLLBACK may be issued only
rollback operation closes an SQL cursor, the result while connected to a location at which updates are
set locator associated with the cursor is no longer allowed.
valid.
For a LOB locator, some common causes for the error
System action
are: The statement cannot be processed. No ROLLBACK is
performed.
• The host variable used as a LOB locator was never
assigned a valid LOB value.
• A commit or rollback operation or an SQL FREE Programmer response
LOCATOR statement freed the locator. The IMS or CICS protocols should be used to rollback
For a table locator, the error commonly occurs when work in these environments.
the host variable that was used as a table locator was
never assigned a valid table locator value. SQLSTATE
2D529
SQLSTATE
-430 routine-type routine-name
0F001 (SPECIFIC NAME specific-name)
-426 DYNAMIC COMMIT NOT VALID AT HAS ABNORMALLY TERMINATED
AN APPLICATION SERVER WHERE
UPDATES ARE NOT ALLOWED Explanation
An abnormal termination has occurred while the
Explanation routine routine-name (stored procedure or function)
An application executing using DRDA protocols has was in control.
attempted to issue a dynamic COMMIT statement,
or a stored procedure has attempted to issue a System action
COMMIT_ON_RETURN, while connected to a location

The stored procedure or function needs to be fixed. If value is a literal string in the SQL statement, it is too
Contact the author of the routine or your database long for its intended use. If value is not a literal string,
administrator. Until it is fixed, the routine should not examine the SQL statement to determine where the
be used. transformation is taking place. Either the input to the
transformation is too long, or the target is too short.
SQLSTATE Correct the problem and rerun the statement.
38503
SQLSTATE
-431 ROUTINE routine-name (SPECIFIC 22001
NAME specific-name) OF
TYPE routine-type HAS BEEN -435 AN INVALID SQLSTATE
INTERRUPTED BY THE USER sqlstate IS SPECIFIED IN
A RAISE_ERROR FUNCTION,
Explanation RESIGNAL STATEMENT, OR
SIGNAL STATEMENT
A user has issued TERMINATE during a debugging
session of SQL routine routine-name. The TERMINATE
Explanation
might have been issued because an infinite wait or
loop was encountered. The SQLSTATE specified in the RAISE_ERROR
function, RESIGNAL statement, or SIGNAL statement
System action of a trigger or a routine does not conform to the rules
for a valid SQLSTATE.
System action
User response
No recovery is necessary.
Programmer response
SQLSTATE
Change the SQLSTATE specified in the RAISE_ERROR
38504 function, RESIGNAL statement, or SIGNAL statement
so that it conforms to the rules of the statement.
-433 VALUE value IS TOO LONG
For the RAISE_ERROR function, the SQLSTATE must
be a character string containing exactly five (5)
Explanation
characters. It must be of type CHAR defined with a
The value value required truncation by a system (built- length of five (5), or, a type VARCHAR defined with a
in) cast or adjustment function, which was called to length of five (5) or greater. The SQLSTATE value must
transform the value in some way. The truncation is conform to the following rules:
not allowed where this value is used. The value being
• Each character must be from the set of digits ('0'
transformed is one of the following:
through '9') or non-accented upper case letters ('A'
• an argument to a user defined function (UDF) through 'Z').
• an input to the SET clause of an UPDATE statement • The SQLSTATE class (the first two characters) cannot
• a value being INSERTed into a table be '00', '01' or '02' because these characters do not
indicate error classes.
• an input to a cast or adjustment function in some
other context. • If the SQLSTATE class (the first two characters) start
with the character '0' through '6' or 'A' through 'H',
If value has the 'for bit data' subtype, or has a data then the subclass (the last three characters) must
type of BINARY or VARBINARY, then the value is start with a letter in the range 'I' through 'Z'.
printed as a hexadecimal string in quotes followed by
• If the SQLSTATE class (the first two characters) start
an X.
with the character '7', '8', '9' or 'I' through 'Z', then
the subclass (the last three characters) must be from
System action the set of characters '0' through '9' or 'A' through 'Z'.

For the RESIGNAL and SIGNAL statements, the Explanation
SQLSTATE value must be exactly five (5) characters
that follow the following rules: An attempt was made to invoke a routine, but Db2
could not resolve the invocation of a routine, including
• Each character must be from the set of digits '0' the argument list, to a specific routine definition.
through '9' or non-accented upper case letter 'A'
through 'Z'. routine-type
The type of routine, such as FUNCTION or
• The SQLSTATE class (the first two characters) cannot PROCEDURE.
be '00' because it represents successful completion.
routine-name or schema-name.routine-name
The name of the routine. If the originating
SQLSTATE statement references a qualified name, the routine
428B3 name in the message text is qualified by the name
of the schema.
Related tasks
Checking the execution of SQL statements by Possible causes for this error include:
using SQLCODE and SQLSTATE (Db2 Application • The routine name was either incorrectly specified or
programming and SQL) does not exist in the database.
Related reference • A qualified reference was used, and the schema
RAISE_ERROR (Db2 SQL) qualifier was incorrectly specified.
SIGNAL statement (Db2 SQL) • The user's SQL path does not contain the schema
RESIGNAL statement (Db2 SQL) to which the function belongs, and an unqualified
SQLSTATE (Db2 SQL) reference was used.
• The wrong number of arguments was included.
-438 APPLICATION RAISED ERROR
WITH DIAGNOSTIC TEXT: text • The right number of arguments was included in the
routine reference, but the data type of one or more
of the arguments is incorrect.
Explanation
• The invoker of the routine is not authorized to
This error occurred as a result of the RAISE_ERROR execute the routine.
function, a RESIGNAL statement, a SIGNAL SQLSTATE • CURRENT QUERY ACCELERATION was set to NONE
statement, or it was an unhandled condition when while a passthrough-only expression was running.
processing of the trigger or routine completed.
• An application or SQL object attempted to use
text a capability that is not supported by the current
Diagnostic text provided by the invocation of the application compatibility level.
RAISE_ERROR function or the SIGNAL SQLSTATE
statement. – Before the activation of function level 500 or
higher, Db2 environments must use application
compatibility levels from previous releases. After
System action the activation of function level 500 or higher, the
The statement cannot be processed. application compatibility level can be equivalent
to the current function level, a lower function level
in the current release, or a function level from a
Programmer response previous release.
Use application-provided diagnostic text, if provided,
to determine the cause of the error. System action
SQLSTATE
Defined by the application Programmer response
-440 NO AUTHORIZED routine-type BY Use the routine name identified in the message to find
THE NAME routine-name HAVING the invocation, and verify that the invocation can be
COMPATIBLE ARGUMENTS WAS resolved to the intended routine, based on the function
FOUND and procedure resolution processes.
• For functions: Function resolution (Db2 SQL)

• For procedures: CALL (Db2 SQL) • If a scalar function is being used, then remove the
keyword DISTINCT or ALL.
To ensure that the intended routine is invoked, specify
a qualified routine name whenever possible. • If the function is an aggregate function that does not
support the DISTINCT or ALL keywords, then remove
If you are executing a passthrough-only expression, the keyword.
set CURRENT QUERY ACCELERATION to ELIGIBLE,
ENABLE, or ALL. • Otherwise, if an aggregate function is being used,
then there is a problem with function resolution.
If the error might be due to an unsupported capability, Check your SQL path to see if the function
check the application compatibility level of your is in one of the schemas, and also check the
application or SQL object and take one of the following SYSIBM.SYSROUTINES catalog for the spelling of
actions: the function name and the number and types of
• Rebind the application or modify the SQL object to parameters
use an application compatibility level that supports
the capability. SQLSTATE
• Remove usage of the unsupported capability from 42601
the application or SQL object.
-443 ROUTINE routine-name (SPECIFIC
NAME specific-name) HAS
SQLSTATE RETURNED AN ERROR SQLSTATE
42884 WITH DIAGNOSTIC TEXT msg-text
Related concepts
Privileges required for executing routines Explanation
(Managing Security) An SQLSTATE was returned by routine routine-name,
along with message text msg-text.
-441 INVALID USE OF 'DISTINCT' OR
'ALL' WITH FUNCTION function-
name System action
Execution of the SQL statement is terminated.
Explanation
This error can occur for the following situations: Programmer response
• The keyword DISTINCT or ALL was detected within Contact the author of the routine or your database
parentheses in a reference to function function- administrator. Until the problem is resolved, the
name and the function has been resolved as a scalar routine should not be used.
function. Use of the keywords DISTINCT or ALL with
the specified scalar function is invalid. SQLSTATE
• The keyword DISTINCT was detected within xxxxx (the SQLSTATE that was returned by the
parentheses in a reference to function function- routine).
name and the function has been resolved as an
aggregate function. Use of the keywords DISTINCT -444 USER PROGRAM name COULD NOT
with the specified aggregate function is not valid. BE FOUND
• The function was expected to be an aggregate
function supporting the keyword ALL or DISTINCT, Explanation
but the function that was resolved to is not an
Db2 received an SQL CALL statement for a
aggregate function.
stored procedure or an SQL statement containing
an invocation of a user-defined function, and
System action found the row in the SYSIBM.SYSROUTINES
The statement cannot be processed. catalog table associated with the requested
procedure name. However, the MVS load module
identified in the EXTERNAL_NAME column of the
Programmer response SYSIBM.SYSROUTINES row could not be found.
Take the appropriate action: name
The name of the MVS load module that could not
be found

System action – The method-signature is optional, and is a list of
Java™ data types that are separated by commas.
The statement cannot be processed. If specified, the method-signature must not be
longer than 1024 bytes.
Programmer response – If multiple strings are specified, the total length
If the EXTERNAL_NAME column value in the of all the strings concatenated together for the
SYSIBM.SYSROUTINES table is incorrect, use the external-java-routine-name must not be greater
ALTER FUNCTION or ALTER PROCEDURE statement to than 1305.
correct the value. • For external routines with a language other than
JAVA, the external name must be a short identifier
If the EXTERNAL_NAME column value is correct, use
with letters or digits. The first character must be a
the MVS linkage editor to create the required MVS load
letter (this is the MVS naming convention for load
module in one of the MVS load libraries used by your
modules). A possible cause for this error is the
installation for stored procedures.
inclusion of a blank in the name.
This error can also occur if you are invoking a
If the clause is omitted, the external name defaults
WLM-managed stored procedure that is not APF
to function-name. However, for CREATE FUNCTION
authorized, and the Db2 load libraries are not in the
or CREATE PROCEDURE, if the function or procedure
STEPLIB concatenation because they are being loaded
name is longer than eight characters then the
from LINKLIST. In this case, if you want the stored
EXTERNAL NAME clause must be explicitly specified
procedure program to run APF-authorized, link-edit
to specify a valid short identifier as the external
it with AC=1 into an MVS APF authorized library. If
name.
you do not want the stored procedure program to
run APF authorized, add the Db2 load library to the
STEPLIB concatenation of the JCL used to start the System action
WLM-managed address space.
SQLSTATE User response

42724
When LANGUAGE is JAVA, possible causes include:
-449 CREATE OR ALTER STATEMENT • Omitting the EXTERNAL NAME clause.
FOR FUNCTION OR PROCEDURE
routine-name CONTAINS AN • Including a blank.
INVALID FORMAT OF THE • Having the '!' at the beginning or end of the name.
EXTERNAL NAME CLAUSE OR IS • Specifying an invalid external-java-routine-name.
MISSING THE EXTERNAL NAME
CLAUSE
Programmer response
Explanation Correct the syntax of the SQL statement.
An error was found in the EXTERNAL NAME clause
of the CREATE FUNCTION, CREATE PROCEDURE, SQLSTATE
ALTER FUNCTION, or ALTER PROCEDURE statement 42878
for routine-name, or the clause is needed but was not
specified. Related reference
CREATE PROCEDURE (external) (Db2 SQL)
• For external routines with LANGUAGE JAVA,
the name must be specified and it must ALTER PROCEDURE (external) (Db2 SQL)
contain a valid external-java-routine-name of CREATE FUNCTION (external scalar) (Db2 SQL)
the following form: jar-name:package-id...class- CREATE FUNCTION (external table) (Db2 SQL)
id.method-id(method-signature) ALTER FUNCTION (external) (Db2 SQL)
– No blanks are permitted within the single quotes. Statements (Db2 SQL)
– The method-name consists of the list of package-
-450 USER-DEFINED FUNCTION OR
ids, class-id, and method-id, and must not be
STORED PROCEDURE name,
longer than 254 bytes.
PARAMETER NUMBER parmnum,
– Zero or more package-ids can be specified, OVERLAYED STORAGE BEYOND
preceding the class-id. ITS DECLARED LENGTH.

Explanation variable-position
Indicates the position of the host variable that
Upon return from a specific function name or a stored referenced the file, as the nth host variable, where
procedure name, Db2 has detected an overlay storage n is the value.
beyond a parameter's declared length. The parameter
number is specified for a stored procedure or function. reason-code
This is not permitted. A numeric value that indicates the reason for the
error:
System action 1
If the file name length is invalid, the path
Execution of the SQL statement is terminated. has an invalid format, or a relative path was
specified.
If the file option is invalid (the file option must
Contact the author of the function or your database
be 2, 8, 16, or 32), or the specified file option
administrator. Until it is fixed, the function should not
is not consistent with the operation that Db2
be used.
attempted to perform. For example, the file
option FILE_READ is specified on a FETCH SQL
SQLSTATE statement.
39501 3
If the file cannot be found.
-451 THE data-item DEFINITION IN THE
CREATE OR ALTER STATEMENT 4
FOR routine-name CONTAINS If the SQL_FILE_CREATE option was specified
DATA TYPE type WHICH IS NOT for a file with the same name as an existing file.
SUPPORTED FOR THE TYPE AND 7
LANGUAGE OF THE ROUTINE If a full disk was encountered while writing to
the file.
Explanation 9
If a media error was encountered while
An error was made in the data-item part of the CREATE accessing the file.
or ALTER statement for routine-name. The statement
contained an invalid data type, or it contained a 12
distinct type which is based on the invalid data type. If the HFS file Db2 attempted to open for a
read, append, or rewrite operation is not a
regular file:
System action
• The BSAM data set that Db2 attempted to
The statement cannot be processed. open for a read, append, or rewrite operation
is not a physical sequential (PS) or partition
Programmer response organization (PO) data set.
Correct the specification of the routine and reissue the • The BSAM data set that Db2 attempted to
CREATE statement. open for a read, append, or rewrite operation
does not have a record format of VB, V, or U.
• The APPEND option was specified for a data
SQLSTATE
set with partition organization (PO).
42815
13
-452 UNABLE TO ACCESS THE FILE If errors were encountered when Db2
REFERENCED BY HOST VARIABLE attempted to OPEN, READ, WRITE, or CLOSE
variable-position. REASON CODE: an HFS file or BSAM data set, there might be
reason-code a system completion code on the console to
indicate the reason that Db2 was unable to
perform the requested operation.
Explanation
variable-position is set to 0 if the host variable position
An error was encountered while Db2 was accessing,
cannot be determined.
or attempting to access, the file referenced by the
specified host variable.

System action CREATE FUNCTION STATEMENT
FOR function-name
Explanation
Programmer response
A problem casting the result of user-defined function
Take one of the following actions based on the reason- function-name has been identified. The CAST FROM
code value: data type is not castable to the RETURNS data type,
1 and it must be. For more information, see Casting
Correct the file name length, file name, and file between data types (Db2 SQL)
path. If a relative path is being used for the HFS
file, replace it with an absolute path. System action
2
Correct the file option in the application.
3
Ensure that the file specified exists before
Programmer response
attempting to access the file. Change the RETURNS or CAST FROM clause so that
4 the CAST FROM data type is castable to the RETURNS
Delete the file if it is no longer required or specify a data type.
file name that does not currently exist.
7 SQLSTATE
Delete unnecessary files to free up disk space or 42880
specify a file that resides on another drive or file
system with sufficient disk space. Also, ensure -454 THE SIGNATURE PROVIDED
that no operating system or user file size limits IN THE CREATE FUNCTION
were reached. If your application code page uses a STATEMENT FOR function-name
multibyte encoding scheme, it is possible that only MATCHES THE SIGNATURE OF
part of the last character was written. Ensure that SOME OTHER FUNCTION ALREADY
the file contains only fully formed characters. EXISTING IN THE SCHEMA
8
The maximum length of the result column must be Explanation
extended to allow for the expansion that occurs
when the string is converted. The signature consists of the function name (function-
name), the number of parameters defined for the
9 function, and an ordered list of the types of the
Correct all errors on the media where the file has parameters (without regard to any parameters of the
been read. types). In this case there is a function already in
12 the schema and the existing function has the same
Take the appropriate action: signature as the function being created. See the SQL
Reference for the details on the uniqueness of a
• Correct the file name to refer to a regular file if it
function.
is an HFS file.
• Correct the file name to refer to a PS or a PO data
System action
set if it is a BSAM data set.
• Correct the file operation to contain the correct The statement cannot be processed.
action.
Correct the error based on the system completion Determine if the existing function already provides the
code. appropriate functionality. If not, change the signature
of the new function. One way to do that is to change
SQLSTATE the function name.
428A1
SQLSTATE
-453 THERE IS A PROBLEM WITH
THE RETURNS CLAUSE IN THE 42723

-455 IN CREATE FOR routine-name, THE Explanation
SCHEMA NAME schema-name1
PROVIDED FOR THE SPECIFIC A user-defined function or user-defined type cannot
NAME DOES NOT MATCH THE be created or referenced because the name is
SCHEMA NAME schema-name2 OF reserved for use by the system.
THE ROUTINE name
The name of the user-defined function or user-
Explanation defined type.
If the SPECIFIC name is specified as a two part A number of names that are used as keywords are
name, the schema-name1 portion must be the same reserved for system use. These names cannot be used
as the schema-name2 portion of the routine-name. as user-defined functions or user-defined type names,
Note that the schema-name2 portion of routine-name even if they are delimited identifiers.
might have been specified directly or it might have Those names are:
defaulted to the authorization ID of the statement.
= < > >= <=
System action
< > ¬= ¬> ¬>
The statement cannot be processed. ALL AND ANY BETWEEN
DISTINCT
EXCEPT EXISTS FALSE FOR
FROM
Programmer response IN IS LIKE MATCH
NOT
Correct the statement. NULL ONLY OR OVERLAPS
SIMILAR
SOME TABLE TRUE TYPE
SQLSTATE UNIQUE
UNKNOWN
42882
The names of built-in data types cannot be used as the
-456 IN CREATE FUNCTION FOR name of a user-defined type (for example, CHAR).
function-name, THE SPECIFIC
NAME specific-name ALREADY You cannot use an asterisk (*) as a specific name for a
EXISTS IN THE SCHEMA user-defined type or procedure name.

A SPECIFIC name has been explicitly specified as The statement cannot be processed.
specific-name in the CREATE FUNCTION statement
for function-name, but this name already exists as Programmer response
the SPECIFIC name for another function within the
schema. Select a name for the function or user-defined type
that is not reserved for system use.
System action
SQLSTATE
42939
Programmer response -458 IN A REFERENCE TO FUNCTION

function-name BY SIGNATURE, A
Choose a new SPECIFIC name. MATCHING FUNCTION COULD NOT
BE FOUND
SQLSTATE
42710 Explanation
-457 A USER-DEFINED FUNCTION OR In a reference to function function-name by signature,
USER-DEFINED TYPE CANNOT no matching function could be found. The problem
BE CALLED name SINCE IT IS could be with the data type or some other attributes of
RESERVED FOR SYSTEM USE a parameter. For some data types there are attributes
in addition to data type:

• Length, precision, or scale System action
While it is not necessary to specify a length, The statement cannot be processed.
precision, or scale attribute for a data type, if one
is specified then there must be an exact match on
the corresponding specification of the parameter for Programmer response
the existing function as defined in SYSPARMS. Possible responses include:
A type of FLOAT(n) does not need to match the • Changing the SQL path to include the correct
defined value for n since 1<=n<=21 means REAL and schema.
22<=n<=53 means DOUBLE. Matching occurs based
• Changing the attributes of the parameters.
on whether the type is REAL or DOUBLE.
• Using a SPECIFIC name to refer to the function
However, a match on data type is sufficient. instead of a signature.
To indicate this, an empty set of parentheses
must be specified for the data types that allow SQLSTATE
a specification of length, precision, or scale. For
example, assuming a function exists for which a 42883
parameter was defined as CHAR(12) on the CREATE Related concepts
FUNCTION statement, a reference to that function
Db2 schemas and schema qualifiers
by a signature could specify this parameter as either
CHAR(12), or CHAR(). The CHAR() syntax provides a
way to say, "do not care about length, precision and Related reference
scale attributes in finding a matching function". ALTER FUNCTION (external) (Db2 SQL)
ALTER FUNCTION (SQL table) (Db2 SQL)
FLOAT() cannot be used since the parameter value
indicates different data types (REAL or DOUBLE). ALTER FUNCTION (compiled SQL scalar) (Db2
SQL)
If, however, neither length, precision, scale, or empty COMMENT (Db2 SQL)
parenthesis were specified, then normal default
DROP (Db2 SQL)
rules apply. For example, a specification of CHAR
would result in CHAR(1) as on the CREATE TABLE -461 A VALUE WITH DATA TYPE source-
statement. Furthermore, this implicit specification of data-type CANNOT BE CAST TO
length, precision, or scale must exactly match the TYPE target-data-type
corresponding specification of the parameter for the
existing function as defined in SYSPARMS.
Explanation
• Subtype, or encoding scheme
The statement contains an implicit or explicit CAST,
You do not need to specify the subtype or encoding
but the combination of the source and target data
scheme (CCSID clause) to identify an existing
types is not supported. Db2 attempted to cast a value
function in the database. However, if a subtype or
of source-data-type to the data type target-data-type.
encoding scheme is specified then there must be an
This combination is not supported.
exact match on the corresponding specification of
the parameter for the existing function as defined in This error is also issued for a statement that
SYSPARMS. references multiple encoding schemes, when there is
an attempt to cast a string value with a field procedure.
Unqualified function names:
• For ALTER FUNCTION, DROP FUNCTION, COMMENT
This error can be issued for an attempt to use a feature
ON FUNCTION, GRANT and REVOKE statements for
that requires a higher APPLCOMPAT setting than the
EXECUTE on functions, an unqualified function name
current setting. The current APPLCOMPAT setting does
is implicitly qualified with the default schema, and
not support a feature that was requested.
this is the schema where the function with the
problem can be found.
• In the SOURCE clause of a CREATE FUNCTION
System action
statement, the qualification comes from the SQL The statement cannot be processed.
path. In this case, Db2 could not resolve the
invocation of a function using the schemas in the
user's SQL path. For details, see CREATE FUNCTION
(sourced) (Db2 SQL).

Change the data type of either the source or target so If the SQL CALL statement is coded incorrectly, modify
that the cast is supported. the SQL application to provide an output variable on
the SQL CALL statement.
For built-in data type values, a cast involving a user-
defined distinct type value, or a cast involving an array If the SYSIBM.SYSPARMS table contains incorrect
value, see Casting between data types (Db2 SQL). information, the DROP PROCEDURE and CREATE
PROCEDURE statements must be used to replace the
If an explicit CAST was specified, correct the CAST
catalog definition for the stored procedure.
specification to specify a supported combination of
source and target types.
SQLSTATE
SQLSTATE 42886
42846 -470 SQL CALL STATEMENT SPECIFIED
Related concepts A NULL VALUE FOR INPUT
PARAMETER number, BUT THE
Casting between data types (Db2 SQL)
STORED PROCEDURE DOES NOT
Application compatibility levels in Db2 (Db2 SUPPORT NULL VALUES.
-469 SQL CALL STATEMENT MUST Explanation

SPECIFY AN OUTPUT VARIABLE Db2 received an SQL CALL statement for a stored
FOR PARAMETER number procedure and found a null value in the incoming
parameter list. The stored procedure was defined
Explanation in the SYSIBM.SYSROUTINES catalog table with
PARAMETER_STYLE of GENERAL, which specifies that
Db2 received an SQL CALL statement for a the routine does not accept null values.
stored procedure. Db2 found the row in the
SYSIBM.SYSROUTINES catalog table associated with A call to a stored procedure with a LANGUAGE value
the requested procedure name. However, parameter of JAVA receives this SQLCODE if an input parameter
number was identified in the SYSIBM.SYSPARMS table in the Java stored procedure has a Java base type that
as an OUT or INOUT parameter. An updatable variable cannot be set to a null value.
must be supplied on the SQL CALL statement for a number
parameter that is defined as OUT or INOUT. The parameter number from the ORDINAL field in
A constant or an expression is an example of an invalid SYSIBM.SYSPARMS.
input argument to a function or an OUT or INOUT
parameter to a procedure. For example, suppose that System action
a procedure named MY_PROC is defined with one OUT
parameter. The following invocation of the procedure The statement cannot be processed.
is not valid because the argument that is passed to the
OUT parameter is a constant expression, which cannot Programmer response
have values assigned to it.
If the stored procedure should not accept null values,
CALL MY_PROC(1+2); change the calling application to provide a non-null
value.
number
The parameter number from the ORDINAL field in If the stored procedure should accept null values,
SYSIBM.SYSPARMS. use the ALTER PROCEDURE statement to change the
PARAMETER STYLE of the stored procedure to be
DB2SQL or GENERAL WITH NULLS.
System action
39004
-471 INVOCATION OF FUNCTION OR
PROCEDURE name FAILED DUE TO
REASON rc

Explanation is not allowed. Adding delimiters does not make the
name valid. The following names are restricted:
A routine was invoked. The routine invocation was not
accepted because of Db2 reason code rc. Restricted names
name BIGINT DECIMAL REF
The name of the routine that was invoked.
BINARY DECFLOAT ROWID
rc
The Db2 reason code describing the cause of the BLOB DOUBLE SMALLINT
failure. BOOLEAN DOUBLE TIME
PRECISION
System action CHAR FLOAT TIMESTAMP
The statement cannot be processed. A DSNX9xx CHAR VARYING GRAPHIC VARBINARY
message describing the error might be displayed on
the MVS system console. CHARACTER INT VARCHAR
CHARACTER INTEGER VARGRAPHIC
Programmer response VARYING
Correct the condition described by the Db2 reason CLOB LONG VARCHAR XML
code. DATALINK LONG
VARGRAPHIC
SQLSTATE DATE NUMERIC
55023 DBCLOB REAL
-472 CURSOR cursor-name WAS LEFT DEC ROWID
OPEN BY EXTERNAL FUNCTION
function-name (SPECIFIC NAME
specific-name) System action
Explanation
The function program did not close the specified Programmer response
cursor. Modify the function program so that it closes
Correct the statement to use another identifier for the
the cursor.
name of the new user-defined type.

42918
Programmer response -475 THE RESULT TYPE type-1 OF THE

SOURCE FUNCTION CANNOT BE
Reissue the statement. CAST TO THE RETURNS TYPE
type-2 OF THE USER-DEFINED
SQLSTATE FUNCTION function-name
24517
Explanation
-473 A USER DEFINED DATA TYPE
In order for the CREATE FUNCTION for a sourced user-
CANNOT BE CALLED THE SAME
defined function to be valid, the result type (type-1) of
NAME AS A SYSTEM PREDEFINED
the source function must be castable to the RETURNS
TYPE (BUILT-IN TYPE)
type (type-2) of the function being created. There is no
supported cast between these data types.
Explanation
The name of a data type to be created has an System action
unqualified name that is the same as a system-
predefined data type. The name that you specified

Change the RETURNS data type or the SOURCE 42725
function identified so that the result type of the
Related concepts
SOURCE function is castable to the RETURNS data
type. Db2 schemas and schema qualifiers
Related reference
SQLSTATE
CREATE PROCEDURE (Db2 SQL)
42866 ALTER FUNCTION (external) (Db2 SQL)
Related concepts ALTER FUNCTION (SQL table) (Db2 SQL)
Casting between data types (Db2 SQL) ALTER FUNCTION (compiled SQL scalar) (Db2
Related reference SQL)
CREATE FUNCTION (sourced) (Db2 SQL) COMMENT (Db2 SQL)
DROP (Db2 SQL)
-476 REFERENCE TO ROUTINE routine-
name WAS IDENTIFIED WITHOUT -478 ALTER, DROP, OR REVOKE
A SIGNATURE, OR BY BOTH AFFECTING OBJECT TYPE object-
SIGNATURE AND SPECIFIC NAME, type CANNOT BE PROCESSED
BUT THE ROUTINE IS NOT UNIQUE BECAUSE OBJECT dependent-
WITHIN ITS SCHEMA object OF TYPE dependent-type IS
DEPENDENT ON IT
Explanation
Explanation
References to a routines without a signature are
permitted, but the identified routine routine-name An ALTER, DROP, or REVOKE statement was issued on
must be unique in its schema and it is not. an object type that is a dependency for one or more
objects. An object type cannot be dropped or revoked
Note also that in the ALTER FUNCTION, DROP if another object type has a dependency on that object
FUNCTION, COMMENT, GRANT and REVOKE (for type.
EXECUTE on functions) statements, an unqualified
reference is qualified with the default schema, and this object-type
is the schema where the problem can be found. In the The type of object that is required and cannot be
SOURCE clause of a CREATE FUNCTION statement, dropped.
the qualification comes from the SQL path. In this dependent-object
case, the first schema in the path containing a function The name of the object that prevents the object-
with this name had other functions by the same name. type from being dropped or revoked.
dependent-type
System action The type of the object that prevents the object-type
The statement cannot be processed. from being dropped or revoked.
Examples of where the dependency might occur
Programmer response include the following situations:
If the statement references a function, take one of the ALTER or DROP statement
following actions: For an ALTER or DROP statement, the following
dependencies might exist based on the object-type
• Complete the signature. value.
• Use the SPECIFIC name of the function. • If object-type is ALIAS:
• Change the SQL path.
– A row permission or a column mask
If the statement references a procedure, a procedure references this alias.
with the same name exists, but there are differences in
This will only occur when the alias is an alias
the parameter list. To change the parameter list of the
for a table or view.
existing procedure, add the SPECIFIC clause with the
name of the procedure to the CREATE statement. – An inline SQL function exists that uses the
sequence in a NEXT VALUE or PREVIOUS

VALUE expression. This will only occur when In the case where object-type is ROLE, this error
the alias is an alias for a sequence. can also occur when revoking the privileges
• If object-type is COLUMN: held by this role. When the role privileges are
revoked, the cascading of the REVOKE statement
– An index references this column. might encounter dependencies that prevent
– A unique constraint references this column. the REVOKE statement from being successfully
processed.
– A view that directly or indirectly references
this column. • If object-type is SEQUENCE:
– A referential constraint that references this – An SQL function is defined that references this
column as a foreign key. sequence.
• If object-type is ARRAY: – An SQL procedure is defined that references
this sequence.
– A function or stored procedure uses the user-
defined array type. – A view definition is defined that references
this sequence.
• If object-type is DISTINCT TYPE:
– A trigger is defined that references this
– A column of a table is defined as this distinct sequence.
type.
• If object-type is SYNONYM:
– A parameter or an SQL variable of a function is
defined as this distinct type. – A row permission or a column mask
references this synonym.
– A parameter or an SQL variable of a procedure
is defined as this distinct type. • If object-type is TABLE:
– A sequence is defined with this distinct type – A row permission or a column mask
as the data type. references this table.
The dependency might be on one of the – This table is the history table for a system-
generated cast functions for a distinct type. period temporal table. An attempt to drop
the table space or database that contains the
• If object-type is FUNCTION:
history table also causes this error.
– A row permission or a column mask – This table is the archive table for an archive-
references this function. enabled table. An attempt to drop the table
– Another function is sourced on this function. space or database that contains the archive
– A view uses this function. table also causes this error.
– A trigger package uses this function. • If object-type is VIEW:
– A table uses this function in a check constraint – A row permission or a column mask
or user-defined default. references this view.
– A materialized query table definition uses this • If object-type is a global variable:
function. – An SQL function references this global
• If object-type is JAR: variable.
– A function or stored procedure uses this JAR – A view references this global variable.
in its EXTERNAL NAME. – A trigger references this global variable.
– Another JAR uses this JAR in its Java path. REVOKE statement
• If object-type is ROLE: For a REVOKE statement, the following
dependencies might exist based on the object-type
– A trusted context uses this role.
value.
– The role is associated with the current thread.
• SYSADM is being revoked. When SYSADM is
– The role is the owner of the object that is revoked, the cascading of the REVOKE statement
being dropped. might encounter dependencies that prevent
– The role is the grantor of ACCESSCTRL, the REVOKE statement from being successfully
DATAACCESS, or system DBADM authority. processed.
– The role is the grantor of any privilege or • If object-type is ARRAY:
authority that used ACCESSCTRL or SECADM
authority to make the grant.

– A function or stored procedure uses the user- – A view that is owned by the revokee
defined array type. references this global variable.
• If object-type is DISTINCT TYPE: – A trigger that is owned by the revokee
references this global variable.
– A column of a table that is owned by the
revokee is defined as this distinct type.
– A parameter or an SQL variable of a function
System action
that is owned by the revokee is defined as this The statement cannot be processed.
distinct type.
– A parameter or an SQL variable of a procedure Programmer response
that is owned by the revokee is defined as this
distinct type. Remove the dependencies on this object. For example,
drop the object that is identified by dependent-object.
– A sequence that is owned by the revokee is Then, reissue the request.
defined with this distinct type as the data type.
• If object-type is FUNCTION:
SQLSTATE
– A function that is owned by the revokee is
The SQLSTATE depends on the values of object-type
sourced on this function.
and dependent-type:
– A view that is owned by the revokee uses this
function. Values SQLSTATE
– A trigger package that is owned by the revokee 46003
object-type: JAR
uses this function.
– A table that is owned by the revokee uses this dependent-type:
function in a check constraint or user-defined FUNCTION or
default. PROCEDURE
– A materialized query table that is owned by object-type: JAR 4600C

the revokee uses this function in the definition.
dependent-type: JAR
– An index that is owned by the revokee uses
this function. All other cases 42893
• If object-type is JAR:
– A function or stored procedure that is owned Related concepts
by the revokee uses this JAR in its EXTERNAL Archive-enabled tables and archive tables
NAME. (Introduction to Db2 for z/OS)
– Another JAR that is owned by the revokee
-480 THE PROCEDURE procedure-name
uses this JAR in its Java path.
HAS NOT YET BEEN CALLED
• If object-type is PROCEDURE:
– A trigger definition that is owned by the Explanation
revokee, contains a CALL statement with the
The procedure identified in a DESCRIBE PROCEDURE
name of this stored procedure.
or an ASSOCIATE LOCATORS statement has not yet
• If object-type is SEQUENCE: been called within the application process or the
– An SQL function is defined that references this procedure has been called, but an explicit or implicit
sequence. commit occurred before the statement.
– An SQL procedure is defined that references
this sequence. System action
– A view definition is defined that references The statement cannot be processed.
this sequence.
– A trigger is defined that references this Programmer response
sequence.
Correct the statements so that the exact syntax used
• If object-type is a global variable: to specify the procedure name on the CALL statement
– A function that is owned by the revokee be the same as that on the ASSOCIATE LOCATOR
references this global variable. and/or DESCRIBE PROCEDURE. If an unqualified name

is used to CALL the procedure, the 1-part name must Explanation
also be used on the other statements. If the CALL
statement is made with a 3-part name, and the current The procedure identified in an ASSOCIATE LOCATORS
server is the same as the location in the 3-part name, statement returned no result set locators.
the ASSOCIATE LOCATOR or DESCRIBE procedure can
omit the location. Rerun the statements. System action
SQLSTATE
-481 THE GROUP BY CLAUSE Determine if result set locators are returned from
CONTAINS element-1 NESTED the identified procedure by using the DESCRIBE
WITHIN element-2 PROCEDURE statement.
The following types of nesting are not allowed within a 51030
GROUP BY clause:
-483 IN CREATE FUNCTION FOR
• CUBE within CUBE, ROLLUP, or grouping-expression- function-name STATEMENT, THE
list NUMBER OF PARAMETERS DOES
• ROLLUP within CUBE, ROLLUP, or grouping- NOT MATCH THE NUMBER OF
expression-list PARAMETERS OF THE SOURCE
FUNCTION
• () - sometimes referred to a grand-total - within
CUBE, ROLLUP, or grouping-expression-list
• GROUPING SETS within GROUPING SETS, CUBE,
Explanation
ROLLUP, or grouping-expression-list An attempt is being made to CREATE a user-defined
• CUBE, ROLLUP, () - sometimes referred to a grand- function function-name which is sourced on another
total, GROUPING SETS within any function, CASE function. One of the following situations has been
expression, or CAST specification identified:
In some instances, the value "*N" will be provided for • The SOURCE clause uses a function-name (input
element-2. In this case "*N" represents one of CUBE, parameter list) to identify the source function, and
ROLLUP, GROUPING SETS, or grouping-expression-list. the number of types in the list is different from the
number of parameters of the function being created.
System action • The SOURCE clause uses different syntax to identify
the source function, and the number of types of that
The statement cannot be processed. function is different from the number of parameters
of the function being created.
Programmer response
Modify the GROUP BY clause to remove the nesting System action
identified by element-1. The statement cannot be processed.

428B0 The number of parameters for the SOURCE function
Related reference and for the function being created must be the same.
The identification of the SOURCE function needs to be
changed to:
-482 THE PROCEDURE procedure-name • fix the input parameter list
RETURNED NO LOCATORS • correct the function name or function specific name
to identify the proper function.

It is also possible that the SQL path needs to be System action
corrected in order for correct function resolution to
occur. The statement cannot be processed.

42885 Change the value n to a valid value in the statement.

ATTEMPTED TO EXECUTE AN
SQLSTATE
SQL STATEMENT WHEN THE 428B7
DEFINITION OF THE FUNCTION
OR PROCEDURE DID NOT SPECIFY -491 CREATE STATEMENT FOR USER-
THIS ACTION DEFINED FUNCTION function-
name MUST HAVE A RETURNS
CLAUSE AND: THE EXTERNAL
Explanation CLAUSE WITH OTHER REQUIRED
A user-defined function or stored procedure object- KEYWORDS; THE PARAMETER
name was invoked and attempted to execute SQL NAMES; OR THE SOURCE CLAUSE
statements, but the function or procedure was created
with the NO SQL option. Explanation
In an environment of nested functions and procedures, A required clause is missing in the CREATE for the
the SQL option in effect is the most restrictive one that specified function.
has been specified in the nested hierarchy of functions
an procedures. The SQL data access option in effect function-name
does not allow for modifying data. The name of the function.

The SQL statement cannot be executed. The statement cannot be processed.

Either use an ALTER statement to change the definition Add the missing clauses, and reissue the failing
of the function or procedure to allow SQL statements, statement.
or remove the failing SQL statement from the external For an EXTERNAL function, specify EXTERNAL and one
function or procedure. of the following options:
• LANGUAGE
SQLSTATE
• PARAMETER STYLE
38001
For a user-defined SOURCE FUNCTION, specify the
-490 NUMBER number DIRECTLY SOURCE clause.
SPECIFIED IN AN SQL STATEMENT
IS OUTSIDE THE RANGE OF SQLSTATE
ALLOWABLE VALUES IN THIS
CONTEXT (minval, maxval) 42601
-492 THE CREATE FUNCTION FOR
Explanation function-name HAS A PROBLEM
WITH PARAMETER NUMBER
A number (number) was specified that is not valid in
number. IT MAY INVOLVE A
the context in which it was specified. The minimum
MISMATCH WITH A SOURCE
allowed value in this context is minval. The maximum
FUNCTION
allowed value in this context is maxval. n must be
within the range specified by minval and maxval
(minval =< n =< maxval). Explanation
The parameter in position number of function function-
name is in error.

function-name value specified in the resource limit specification
The name of the function that cannot be created. table (RLST). This error is also issued if the Db2
number cost category value was "B", and the default action
The position number of the function parameter specified in the RLF_CATEGORY_B column in the RLST
that has the problem. is to issue an error.
estimate_amount1
This error is issued in the following circumstances:
The cost estimate (in processor seconds) if the
• The parameter of the source function is not castable prepared INSERT, UPDATE, MERGE, DELETE or
to the corresponding parameter of the function being SELECT statement were to be executed.
created. estimate_amount2
If the parameter of the function being created is The cost estimate (in service units) if the prepared
a table parameter, the corresponding parameter of INSERT, UPDATE, MERGE, DELETE or SELECT
the source function must also be a table parameter. statement were to be executed.
Furthermore, the column numbers for both of the cost-category
table parameters must be the same. The Db2 cost-category for this SQL statement. The
If the parameter of the function being created is possible values are A or B.
not a table parameter, the corresponding parameter limit-amount
of the source function must also not be a table The error threshold (in service units) specified in
parameter. the RLFASUERR column of the RLST. If you entered
• The parameter of the function that is being created is any negative number for the RLFASUERR column,
an array. A sourced function cannot be defined with the value for limit-amount defaults to zero.
an array parameter.
System action
System action The prepare of the dynamic INSERT, UPDATE, MERGE,
The statement cannot be processed. DELETE, or SELECT statement was unsuccessful.

Possible corrections include: If the warning is caused by an SQL statement that
is consuming too much processor resource, attempt
• Identify a different source function. to rewrite the statement to perform more efficiently.
• Change the data type of the parameter of the Another option is to ask the administrator to increase
function being created so that the data type of the the error threshold value in the RLST.
source function can be cast to this data type.
• Do not create a sourced function from a source Programmer response
function with array parameters.
If this SQLCODE was returned because the cost
category value is "B", it might be that the statement
SQLSTATE is using parameter markers or that some statistics are
not available for the referenced tables and columns.
42879
Make sure the administrator has run the utility
-495 ESTIMATED PROCESSOR COST RUNSTATS on the referenced tables. It might also
OF estimate-amount1 PROCESSOR be that UDFs will be invoked when the statement is
SECONDS (estimate-amount2 executed, or for INSERT, UPDATE, MERGE, or DELETE
SERVICE UNITS) IN COST statements that triggers are defined on the changed
CATEGORY cost-category EXCEEDS table. Check the DSN_STATEMNT_TABLE or the IFCID
A RESOURCE LIMIT ERROR 22 record for this statement to find the reasons this
THRESHOLD OF limit- amount SQL statement has been put in cost category "B". If
SERVICE UNITS the program cannot be changed, or if statistics cannot
be obtained, ask the administrator to change the value
Explanation in the RLF_CATEGORY_B column in the RLST to "Y"
which allows the statement to execute or "W" which
The prepare of a dynamic INSERT, UPDATE, MERGE, returns a warning instead of an error.
DELETE, or SELECT SQL statement resulted in a
cost estimate that exceeded the error threshold

SQLSTATE • The number of indexes defined on declared
global temporary tables belonging to all agents
57051 on the local Db2 member has exceeded the limit
-496 THE SQL STATEMENT CANNOT of 10,000.
BE EXECUTED BECAUSE IT • The number of tables and triggers belonging
REFERENCES A RESULT SET THAT to a local agent exceeded the limit of 11,767.
WAS NOT CREATED BY THE The tables in the WORKFILE database include
CURRENT SERVER work files, created global temporary tables, and
declared global temporary tables.
Explanation
System action
The SQL statement cannot be executed because the
current server is different from the server that called The statement cannot be processed.
a stored procedure. The SQL statement can be any of
the following:
Programmer response
• ALLOCATE CURSOR
Take the appropriate action as described in the
• DESCRIBE CURSOR following cases:
• FETCH (using an allocated cursor) 1. In the case of a DBID limit being exceeded, DROP
• CLOSE (using an allocated cursor) all unused databases and issue a COMMIT.
2. In the case of an OBID limit being exceeded, take
System action one of the following actions:
The statement cannot be processed. • Specify a different database.
• Drop all unused table spaces or indexes in the
Programmer response database and issue a COMMIT.
Connect to the server that called the stored procedure • If the database contains multi-table table spaces
which created the result set before running the SQL that contain a mix of used and unused tables,
statement that failed. drop all unused tables and issue a COMMIT.
Run the REORG utility on each affected table
space, and then run the MODIFY RECOVERY
SQLSTATE utility to reclaim the dropped table OBIDs. For
51033 more information, see Reclaiming space in the
DBD (Db2 Utilities).
-497 THE MAXIMUM LIMIT OF
INTERNAL IDENTIFIERS HAS
SQLSTATE
BEEN EXCEEDED FOR DATABASE
database-name 54041
Related tasks
Explanation Reclaiming space in the DBD (Db2 Utilities)
The SQL statement cannot be executed because an Related reference
internal identifier limit has been exceeded for the DROP (Db2 SQL)
database. The cause of this error is due to one of the COMMIT (Db2 SQL)
following: REORG TABLESPACE (Db2 Utilities)
1. On a CREATE DATABASE statement, the limit of MODIFY RECOVERY (Db2 Utilities)
65217 DBIDs has been exceeded.
2. For all other statements, the limit of 32767 OBIDs -499 CURSOR cursor-name HAS
has been exceeded for that database. ALREADY BEEN ASSIGNED TO
THIS OR ANOTHER RESULT
3. If the database is a WORKFILE database, then one SET FROM PROCEDURE procedure-
of the following reasons might apply: name.
• The number of tablespaces in the WORKFILE
database has exceeded the limit of 500.

An attempt was made to assign a cursor to a result set The FETCH, UPDATE, DELETE, or CLOSE statement
using the SQL statement ALLOCATE CURSOR and one identifies a closed cursor that was defined with the
of the following applies: WITH HOLD option. The cursor was closed when
the connection on which it was dependent was
• The result set locator variable specified in the
destroyed during a commit operation. The connection
ALLOCATE CURSOR statement has been previously
was destroyed because the application process placed
assigned to cursor cursor-name.
it in the released state, or the application plan was
• Cursor cursor-name specified in the ALLOCATE bound with the DISCONNECT(AUTOMATIC) option.
CURSOR statement has been previously assigned to
a result set from stored procedure procedure-name.
System action

Programmer response
Programmer response Take one of the following actions:
Determine if the target result set named in the • If you want the cursor closed, change the application
ALLOCATE CURSOR statement has been previously program so that the cursor is not referenced in the
assigned to a cursor. closed state.
• If you want the cursor open and the connection
If the result set has been previously assigned to cursor
was placed in the released state by the application
cursor-name, then either choose another target result
program, change the program so that the connection
set or call stored procedure procedure-name again
is not placed in the released state until the cursor is
and reissue the ASSOCIATE LOCATOR and ALLOCATE
explicitly closed.
CURSOR statements.
• If you want the cursor open and the connection
If the result set has not been previously assigned was placed in the released state as a result of the
to a cursor, the cursor cursor-name specified in the DISCONNECT(AUTOMATIC) option, rebind the plan
ALLOCATE CURSOR statement has been previously using DISCONNECT(CONDITIONAL).
assigned to some result set from stored procedure
procedure-name. You can not assign cursor cursor- Correct the error in the application, rebind the plan,
name to another result set, so you must specify and resubmit the job.
a different cursor name in the ALLOCATE CURSOR
statement. SQLSTATE
Correct the statements so that the exact syntax used 24501
to specify the procedure name on the CALL statement
be the same as that on the ASSOCIATE LOCATOR -501 THE CURSOR IDENTIFIED IN A
and/or DESCRIBE PROCEDURE. If an unqualified name FETCH OR CLOSE STATEMENT IS
is used to CALL the procedure, the 1-part name must NOT OPEN
also be used on the other statements. If the CALL
statement is made with a 3-part name, and the current Explanation
server is the same as the location in the 3-part name,
the ASSOCIATE LOCATOR or DESCRIBE procedure can The application program attempted either to fetch
omit the location. using a cursor or to close a cursor at a time when the
specified cursor was not open.
SQLSTATE
System action
24516
-500 THE IDENTIFIED CURSOR WAS
CLOSED WHEN THE CONNECTION
WAS DESTROYED Programmer response
Check for a previous SQL return code that might have
closed the cursor.
• Commit and rollback operations close cursors.

• SQL return codes -404, -652, -679, -802, -901, Any column that is to be updated must be identified in
-904, -909, -910, -911, -913, and -952 might force the FOR UPDATE clause of the cursor declaration.
the cursor to close.
• An error SQLCODE during predicate processing System action
closes the cursor.
After the cursor is closed, any fetches or close cursor updated in the object table.
statements will receive SQLCODE -501.
If no previous SQL return codes have been issued, Programmer response
correct the logic of the application program to ensure
Correct the application program. If the column is to be
that the cursor is open at the time the FETCH or CLOSE
updated, its name must be added to the FOR UPDATE
statement is processed.
clause of the cursor declaration.
SQLSTATE
SQLSTATE
24501
42912
Related reference
-504 CURSOR NAME cursor-name IS
CLOSE (Db2 SQL)
NOT DECLARED
FETCH (Db2 SQL)
-502 THE CURSOR IDENTIFIED IN AN Explanation

OPEN STATEMENT IS ALREADY Cursor cursor-name was referenced in an SQL
OPEN statement, and one of the following is true:
• Cursor cursor-name was not declared (using the
Explanation DECLARE CURSOR statement) or allocated (using
The application program attempted to execute an the ALLOCATE CURSOR statement) in the application
OPEN statement for a cursor that was already open. program or SQL routine before it was referenced.
• Cursor cursor-name was referenced in a positioned
System action UPDATE or DELETE statement which is not a
supported operation for an allocated cursor.
The statement cannot be processed. The cursor was
unchanged (that is, it was not 'reopened'). • Cursor cursor-name was allocated, but a CLOSE
cursor statement naming cursor-name was issued
and deallocated the cursor before this cursor
Programmer response reference.
Correct the logic of the application program to ensure • Cursor cursor-name was allocated, but a ROLLBACK
that it does not attempt to execute an OPEN statement operation occurred and deallocated the cursor
for a cursor that is already open. before this cursor reference.
• Cursor cursor-name was allocated, but its associated
SQLSTATE cursor declared in a stored procedure was not
declared WITH HOLD, and a COMMIT operation
24502 occurred and deallocated the cursor before this
-503 A COLUMN CANNOT BE UPDATED cursor reference. The COMMIT operation can
BECAUSE IT IS NOT IDENTIFIED be either explicit (the COMMIT statement) or
IN THE UPDATE CLAUSE OF implicit (that is, a stored procedure defined as
THE SELECT STATEMENT OF THE COMMIT_ON_RETURN = 'Y' was called before this
CURSOR cursor reference).
• Cursor cursor-name was allocated, but its associated
Explanation stored procedure was called again since the cursor
was allocated, new result sets were returned, and
The application program attempted to update (using a cursor cursor-name was deallocated.
cursor) a value in a column of the object table that was
• The declaration of a cursor cursor-name was not in
not identified in the FOR UPDATE clause in the cursor
scope for the reference to a cursor named cursor-
declaration.
name.

The statement cannot be processed. Check for a previous SQL return code that might have
closed the cursor. SQLCODES -404, -652, -679,-802,
Programmer response -901, -904, -909, -910, -911, -913, and -952 may
force the cursor to close. After the cursor is closed, any
Check the application program or SQL routine for fetches or close cursor statements receive SQLCODE
completeness and for a possible spelling error in the -501. Any updates or deletes receive this SQLCODE
cursor declaration or allocation. The declaration for or -507. Correct the logic of the application program to
allocation of a cursor must appear in an application ensure that the specified cursor is open at the time the
program or SQL routine before SQL statements that UPDATE or DELETE statement is executed.
reference the cursor.
If the cursor-name was <UNKNOWN>, the cursor SQLSTATE
was not successfully declared or allocated. This error
24501
can occur if SQL(Db2) was used, and a warning
message was issued during precompilation. Check -508 THE CURSOR IDENTIFIED IN THE
the precompile output for warning messages on the UPDATE OR DELETE STATEMENT
DECLARE CURSOR or ALLOCATE CURSOR statement, IS NOT POSITIONED ON A ROW
and correct the statement. OR ROWSET THAT CAN BE
UPDATED OR DELETED
For an allocated cursor, if an implicit or explicit
COMMIT, ROLLBACK, or CLOSE occurred since
the cursor was successfully allocated, modify the Explanation
application program logic to do one of the following
The application program attempted to execute an
actions:
UPDATE or DELETE WHERE CURRENT OF cursor
• After the COMMIT, ROLLBACK, or CLOSE operation, statement at a time when the specified cursor was
call the associated stored procedure again, and not positioned on a row or rowset of the object table.
reissue the ASSOCIATE LOCATORS and ALLOCATE The cursor must be positioned on the row that is to be
CURSOR statements. updated or deleted.
• For COMMIT, declare the associated cursor in the This can occur in the following situations:
stored procedure WITH HOLD so the COMMIT
operation does not deallocate the cursor. • The cursor is no longer positioned on the row
because another cursor in the same application
For an allocated cursor, if the associated stored program deletes the row or updates an index
procedure was called again and new result sets column. This includes deletes and index column
were returned since the cursor was allocated, reissue updates that are performed as a result of rolling back
the ASSOCIATE LOCATORS and ALLOCATE CURSOR to a savepoint.
statements.
• A sensitive dynamic cursor with the FOR ROW n OF
ROWSET clause is specified, and the specified row of
SQLSTATE the current rowset has been updated or deleted.
34000
System action
-507 THE CURSOR IDENTIFIED IN THE
UPDATE OR DELETE STATEMENT The statement cannot be processed. No data was
IS NOT OPEN updated or deleted, and the cursor position is
unchanged.
Explanation
Programmer response
The application program attempted to execute an
UPDATE or DELETE WHERE CURRENT OF cursor Correct the logic of the application program to ensure
statement at a time when the specified cursor was not that the cursor is correctly positioned on the intended
open. row of the object table before the UPDATE or DELETE
statement is executed. Note that for single row or non-
rowset cursors, the cursors are not positioned on a
System action
row if FETCH returned SQLCODE +100.
The statement cannot be processed. No update or
delete was performed.

SQLSTATE • A target table exists at a remote location and Db2
has employed block fetching because you explicitly
24504 declared the cursor FOR FETCH ONLY, or because
Related reference the application is bound CURRENTDATA( NO) and
UPDATE (Db2 SQL) the cursor is ambiguous.
DELETE (Db2 SQL) • Db2 has employed parallelism to execute the
FETCH (Db2 SQL) SELECT statement associated with the cursor named
in a DELETE WHERE CURRENT OF cursor statement,
Related information
or a DELETE WHERE CURRENT OF is issued against
+100 a row which Db2 cannot guarantee to have not been
ROW NOT FOUND FOR FETCH, UPDATE OR modified by another application since the time the
DELETE, OR THE RESULT OF A QUERY IS AN cursor was positioned upon it (in accordance with
EMPTY TABLE ISO(CS)) semantics for an ambiguous cursor in an
application bound CURRENTDATA(NO)).
-509 THE TABLE IDENTIFIED IN THE
UPDATE OR DELETE STATEMENT • The cursor references a view on which an INSTEAD
IS NOT THE SAME TABLE OF UPDATE trigger is defined, even if the view is an
DESIGNATED BY THE CURSOR updatable view.

The application program attempted to execute an The statement cannot be processed. No data was
UPDATE or DELETE WHERE CURRENT OF cursor updated or deleted in the object table or view.
statement where the table named in that statement
did not match the name of the table specified in the Programmer response
declaration for that cursor.
The requested UPDATE or DELETE cannot be
performed.
System action
For a remote table, modify the DECLARE CURSOR and
The statement cannot be processed. The update or then rebind the PLAN.
delete was not performed.
For a cursor that uses parallelism, disable parallelism
for the query by using the DEGREE(1) BIND option for
Programmer response static SQL or by setting the CURRENT DEGREE special
Correct the application program to ensure that the register to '1' for dynamic SQL.
table identified in the UPDATE or DELETE statement For an ambiguous cursor in an application
is the same table identified in the declaration for the bound CURRENTDATA(NO), either make the cursor
cursor. unambiguous (declare it FOR UPDATE OF), or rebind
the application CURRENTDATA(YES).
SQLSTATE For a view with INSTEAD OF triggers, drop those
42827 triggers.
-510 THE TABLE DESIGNATED BY THE

CURSOR OF THE UPDATE OR SQLSTATE
DELETE STATEMENT CANNOT BE 42828
MODIFIED
Related concepts
Db2 views (Introduction to Db2 for z/OS)
Explanation
Related reference
The application program attempted to execute an DELETE (Db2 SQL)
UPDATE or DELETE WHERE CURRENT OF cursor UPDATE (Db2 SQL)
statement against a table or view that cannot be
updated or deleted. This error can be returned for the -511 THE FOR UPDATE CLAUSE
following reasons: CANNOT BE SPECIFIED BECAUSE
• A delete was performed from a read-only view or for THE RESULT TABLE DESIGNATED
an update in which the cursor was not defined with BY THE SELECT STATEMENT
the FOR UPDATE clause. CANNOT BE MODIFIED

The result table of the SELECT statement cannot be The statement cannot be processed.
updated. This error can occur if the SELECT specifies
more than one table or view in the FROM clause, if the Programmer response
SELECT list contains a built-in function or DISTINCT,
or if the statement contains an ORDER BY or GROUP If the object cannot be meaningfully eliminated from
BY or HAVING clause. This error can also occur if a the statement, see your database administrator for
view is specified in the FROM clause and the view other ways to obtain the data required.
cannot be updated, or if a data change statement is
If the remote object reference is in a triggered SQL
specified within the SELECT statement, for example:
statement, you can instead invoke a user-defined
SELECT from INSERT.
function or a stored procedure from the trigger and
access the remote object from the function or stored
System action procedure.
SQLSTATE
Updates cannot be performed on the result table as it -513 INVALID USE OF alias-name
is specified.
Explanation
SQLSTATE
The object indicated by alias-name can be the name of
42829 an alias that was being created, or the name of an alias
Related reference that was used in an invalid context. An alias cannot be
defined on another alias at the same server.
read-only-clause (Db2 SQL)
update-clause (Db2 SQL)
System action
-512 STATEMENT REFERENCE TO The statement cannot be processed.
REMOTE OBJECT IS INVALID
Programmer response
Explanation
Modify the SQL statement to refer to the name of an
One of the following conditions exists: object of a supported type.
• The statement refers to multiple locations.
• A statement with a remote reference is being SQLSTATE
EXPLAINED either by a dynamic EXPLAIN statement 42924
or the EXPLAIN(YES) option.
Related concepts
• An alias is used incorrectly.
Aliases (Introduction to Db2 for z/OS)
• A three-part name is implicitly or explicitly used in a
Related reference
statement that is not supported by the Db2 private
protocols. CREATE ALIAS (Db2 SQL)
• A three-part name is implicitly or explicitly used in a -514 THE CURSOR cursor-name IS NOT
triggered statement. IN A PREPARED STATE
• A PREPARE statement contains an ATTRIBUTES
clause. This is not supported by the Db2 private Explanation
protocols.
• A three-part name with a remote reference is not The application program has tried to use a cursor,
allowed in a body of an SQL function. 'cursor-name,' that is not in a prepared state. The
cursor is associated with a statement that:
• A three-part name with a remote reference is
specified in a TRANSFER OWNERSHIP statement. 1. Was never prepared.
2. Was invalidated by a commit or rollback operations

The statement cannot be processed. The cursor 'cursor-name' could not be used as
specified because the prepared statement named in
Programmer response the declaration for the cursor was not a SELECT
statement.
For case 1, ensure that you prepare the statement
that is named in the DECLARE CURSOR statement for
System action
'cursor-name' before you try to open the cursor.
For case 2, take one of the following actions:
• Use the WITH HOLD option of DECLARE CURSOR. Programmer response
• Do not execute a commit or rollback operation until
you are finished using the cursor. Verify that the statement-name is specified correctly
in the PREPARE statement and the DECLARE CURSOR
• Prepare the statement again after the commit or statement for cursor 'cursor-name'. Alternatively,
rollback. correct the application program logic to ensure
that only prepared SELECT statements are used in
SQLSTATE association with cursor declarations.
26501
SQLSTATE
Related reference
DECLARE CURSOR (Db2 SQL) 07005
EXPLAIN (Db2 SQL) -518 THE EXECUTE STATEMENT
Explicit system privileges (Managing Security) DOES NOT IDENTIFY A VALID
PREPARED STATEMENT
-516 THE DESCRIBE STATEMENT DOES
NOT SPECIFY A PREPARED Explanation
STATEMENT
Explanation • The statement identified in the EXECUTE statement
has not been prepared.
An attempt was made to execute a DESCRIBE
statement that did not refer to a statement that had • The statement identified in the EXECUTE statement
been successfully prepared at the current server. identifies a SELECT, or ASSOCIATE LOCATORS
statement
System action • The statement identified in the EXECUTE
IMMEDIATE statement identifies a SELECT or
The statement cannot be processed. ASSOCIATE LOCATORS statement.
• The statement identified in the EXECUTE statement
Programmer response is a data definition statement written in native SQL
language, and that statement has already been
Verify that the statement name specified in the
executed.
DESCRIBE statement is a statement that has been
prepared at the current server. • A COMMIT or ROLLBACK statement was issued.
The COMMIT or ROLLBACK operation destroyed the
prepared version of the statement.
SQLSTATE
26501 System action
-517 CURSOR cursor-name CANNOT BE The statement cannot be processed.
USED BECAUSE ITS STATEMENT
NAME DOES NOT IDENTIFY A
PREPARED SELECT STATEMENT Programmer response
Ensure that you prepare the statement prior to
EXECUTE. Also, ensure that the statement prepared
statement is not:

• A SELECT statement. SQLSTATE
• An ASSOCIATE LOCATORS statement. 24506
If the statement is a data definition statement written
-525 THE SQL STATEMENT CANNOT
in native SQL language and that statement has already
BE EXECUTED BECAUSE IT WAS
been executed, you must prepare the statement again
IN ERROR AT BIND TIME FOR
before it can be executed again.
SECTION = sectno PACKAGE =
If the prepared statement is issued after a COMMIT pkgname CONSISTENCY TOKEN =
or ROLLBACK statement, take one of the following contoken
actions:
• Prepare the statement again. Explanation
• Bind the application package with the One of the following:
KEEPDYNAMIC(YES) option to keep the prepared
• The statement was in error when the package was
statement after a COMMIT or ROLLBACK statement.
bound, but the error was ignored then because the
• Bind the application package with option SQLERROR (CONTINUE) was used. Since the
RELEASE(DEALLOCATE) to keep a prepared statement contains an error, it cannot be executed.
statement that references declared temporary
• The statement might not be an executable
tables after a COMMIT statement.
statement at this location, or might only be
executable by a Db2 application requester (for
SQLSTATE example, DECLARE TABLE in an application running
07003 on OS/2 causes this message).
Related concepts The variables are:

Methods for keeping prepared statements sectno
after the point of commit or rollback (Db2 Section number
Performance) pkgname
Related reference locid.collid.pkgid
EXECUTE (Db2 SQL) contoken
EXECUTE IMMEDIATE (Db2 SQL) Consistency token in hexadecimal
ASSOCIATE LOCATORS (Db2 SQL)
Explicit system privileges (Managing Security) System action
EXPLAIN (Db2 SQL)
-519 THE PREPARE STATEMENT
IDENTIFIES THE SELECT Programmer response
STATEMENT OF THE OPENED
If the SQL statement is not supposed to execute
CURSOR cursor-name
at the indicated location, then correct the program
so that the statement in error does not execute at
Explanation that location. Precompile, compile, and bind replace
the package. If the SQL statement is supposed
The application program has attempted to PREPARE
to execute at the indicated location, correct the
(actually, re-PREPARE) the SELECT statement for the
problem found when it was bound and bind the
specified cursor at a time when that cursor was
package over using BIND with ACTION(REPLACE). If
already open.
multiple versions of the package have been bound,
issue the following SELECT statement to determine
System action which version has the error: SELECT VERSION FROM
The statement cannot be processed. The cursor was locid.SYSIBM.SYSPACKAGE WHERE LOCATION = ' '
not affected. AND COLLID = 'collid' AND NAME = 'pkgid' AND
HEX(CONTOKEN) = 'contoken'
Programmer response Where:

locid
Location name
it does not attempt to re-PREPARE the SELECT
statement for a cursor when that cursor is open.

collid to reference the persistent base table with the same
Collection id table-name in the same application process
pkgid • Remove the DECLARE GLOBAL TEMPORARY TABLE
Program name statement from the application process to use the
persistent base table with the same table-name
SQLSTATE If table-type is CREATED, perform the following action
and issue the statement again:
51015
• If the SQL statement is a DELETE statement that
-526 THE REQUESTED OPERATION OR
specifies the fetch-clause, remove the fetch-clause
USAGE DOES NOT APPLY TO table-
from the DELETE statement.
type TEMPORARY TABLE table-
name • If the SQL statement contains a KEY LABEL clause,
remove the key label specification.
Explanation
SQLSTATE
Db2 assumes that the SQL statement being executed
refers to a created or declared temporary table, named 42995
table-name, and the requested operation or usage in -530 THE INSERT OR UPDATE VALUE OF
the statement is not allowed on the temporary table. FOREIGN KEY constraint-name IS
table-type INVALID
CREATED or DECLARED
CREATED is for a temporary table defined by the Explanation
CREATE GLOBAL TEMPORARY TABLE statement.
An insert or update operation attempted to place a
DECLARED is for a temporary table defined by the value in a foreign key of the object table; however, this
DECLARE GLOBAL TEMPORARY TABLE statement. value was not equal to some value of the parent key of
the parent table.
table-name
Qualified name of the temporary table. When a row is inserted into a dependent table, the
insert value of a foreign key must be equal to the value
This error might be issued for the following reasons
of the parent key of some row of the parent table in the
when table-type is CREATED:
associated relationship.
• If the SQL statement is a DELETE statement that
When the value of the foreign key is updated, the
specifies the fetch-clause, remove the fetch-clause
update value of a foreign key must be equal to the
from the DELETE statement.
value of the parent key of some row of the parent table
• FL 502 A KEY LABEL clause is specified of the associated relationship.
The following additional rules apply for a temporal
System action referential constraint:
The statement cannot be processed. • When a row is inserted into a dependent table,
the BUSINESS_TIME value in the child table must
Programmer response be contained in a BUSINESS_TIME period in the
parent table that is represented by the union of
Modify the SQL statement to ensure that the object BUSINESS_TIME periods of one or more contiguous
references are not to the indicated type of temporary matching rows in the parent table.
table
• When the value of the foreign key is updated, the
If table-type is DECLARED and you intended table- update value of the foreign key must be contained
name to refer to an existing persistent base table, you in a BUSINESS_TIME period in the parent table
must perform one of the following actions: that is represented by the union of BUSINESS_TIME
periods of one or more contiguous matching rows in
• Recreate the persistent base table table-name with a
the parent table.
different schema qualifier
• In the same application process, issue a DROP
TABLE for table name followed by a COMMIT to drop
System action
the declared temporary table and afterwards be able The UPDATE, MERGE, or INSERT statement cannot be
executed. The object table is unchanged.

UPDATE (Db2 SQL)
Examine the insert or update value of the foreign key
first, and then compare it with each of the parent key -532 THE RELATIONSHIP constraint-
values of the parent table to determine the cause of name RESTRICTS THE DELETION
the problem. OF ROW WITH RID X rid-number
23503 A DELETE operation attempted to delete a specified
-531 PARENT KEY IN A PARENT parent row in the object table and all related
ROW CANNOT BE UPDATED descendent rows in the descendent tables. However,
BECAUSE IT HAS ONE OR a delete rule of RESTRICT or NO ACTION was specified
MORE DEPENDENT ROWS IN for one or more descendent tables.
RELATIONSHIP constraint-name A row of the table cannot be deleted because it has
a dependent in a relationship with a delete rule of
Explanation RESTRICT or NO ACTION or the deletion cascades to
a row which is a dependent in a relationship with a
For plans and packages bound beginning with Version delete rule of RESTRICT or NO ACTION.
5 or dynamic SQL, a multi-row update of a parent key
attempted to remove a parent key value on which a If the statement that failed is an ALTER TABLE with
foreign key was dependent. ALTER PART ROTATE FIRST TO LAST, then there is
a referential constraint that is defined with DELETE
For plans and packages bound prior to Version 5, an RESTRICT on the table, and the data in the partition
UPDATE operation attempted to update a primary key that is to be reused cannot be deleted because of the
in the specified row of the object table; however, the referential constraint.
primary key in the specified row had dependent rows
associated with it. The value of a primary key in a
parent row cannot be updated if the parent row has System action
any dependent rows. The DELETE statement cannot be executed. The
contents of the object table are unchanged.
System action
The UPDATE statement cannot be executed. The Programmer response
object table is unchanged. Examine the delete rule for all descendent tables
to determine the cause of the problem. The
Programmer response specific tables involved can be determined from the
relationship constraint-name. The specific descendent
Examine the parent key of the object table and the row is known by RID X rid-number.
foreign key of the dependent table to determine if the
value of the specified row of the parent key should be
changed. If this does not expose the problem, examine SQLSTATE
the contents of the object table and the dependent 23504
table to determine the cause of the problem.
-533 INVALID MULTIPLE-ROW INSERT
SQLSTATE
Explanation
23504
An INSERT operation with a subselect attempted to
Related concepts insert multiple rows into a self-referencing table.
Parent key columns (Db2 Application
programming and SQL) The subselect of the INSERT operation should return
no more than one row of data.
Referential constraints (Introduction to Db2 for
z/OS)
Related tasks System action
Retrieving catalog information about primary The INSERT statement cannot be executed. The
keys (Db2 Administration Guide) contents of the object table are unchanged.

Examine the search condition of the subselect to make A DELETE operation with the indicated table
sure that no more than one row of data is selected. referenced in a subquery was attempted.
If 'T' is the object table of the DELETE, the indicated
SQLSTATE table is one of the following:
21501 • A dependent of 'T' in a relationship with a delete rule
of CASCADE or SET NULL
-534 THE PRIMARY KEY CANNOT BE
UPDATED BECAUSE OF MULTIPLE- • A dependent of another table in a relationship with
ROW UPDATE a delete rule of CASCADE or SET NULL in which
deletions from 'T' can cascade to that table.
Explanation
System action
An UPDATE operation attempted to update a primary
key on multiple rows of the object table. The DELETE statement cannot be processed. The
contents of the object table are unchanged.
An UPDATE statement updating the primary key
cannot be used to update more than one row of the
object table. Programmer response
Note: This SQLCODE will only be issued for plans and Do not attempt to reference a table in a subquery of a
packages bound prior to Version 5. SQLCODE -534 will DELETE statement when the table can be affected by
not be issued for dynamic SQL or plans and packages the DELETE statement.
bound with Version 5 or later releases.
SQLSTATE
System action 42914
The UPDATE statement cannot be executed. The -537 THE PRIMARY KEY, FOREIGN
contents of the object table are unchanged. KEY, UNIQUE, OR PARTITIONING
KEY CLAUSE IDENTIFIES COLUMN
Programmer response column-name MORE THAN ONCE
Examine the search condition of the UPDATE
statement to make sure that no more than one row Explanation
of the object table is selected to be updated. PRIMARY KEY, FOREIGN KEY, UNIQUE, or
PARTITIONING KEY can each be followed by a list of
SQLSTATE column names. The statement violates the rule that no
column name can appear more than once in any such
21502 list.
Related concepts
Parent key columns (Db2 Application System action
programming and SQL)
Related tasks
Retrieving catalog information about primary
keys (Db2 Administration Guide) Programmer response
Related reference Correct the statement to specify unique names for
UPDATE (Db2 SQL) each column.
-536 THE DELETE STATEMENT IS

SQLSTATE
INVALID BECAUSE TABLE table-
name CAN BE AFFECTED BY THE 42709
OPERATION
-538 FOREIGN KEY name DOES NOT
CONFORM TO THE DESCRIPTION
OF A PARENT KEY OF TABLE table-
name

The definition of the indicated foreign key does not Correct the statement to reference a table with a
conform to the description of parent key of the primary key, or define a primary key with ALTER TABLE
indicated table due to one of the following reasons: ADD PRIMARY KEY before referencing the table in a
FOREIGN KEY clause.
• The referenced parent key has not been defined as a
primary key or a unique key.
• The keys do not have the same number of columns.
SQLSTATE
• The description of the keys are not identical. The 42888
requirement for identical descriptions includes data -540 THE DEFINITION OF TABLE table-
type, length attribute, and field procedure. name IS INCOMPLETE BECAUSE IT
• PERIOD BUSINESS_TIME was specified for the LACKS A PRIMARY INDEX OR A
child key in the FOREIGN KEY clause, but PERIOD REQUIRED UNIQUE INDEX
BUSINESS_TIME was not specified in the parent key
in the REFERENCES clause.
Explanation
• PERIOD BUSINESS_TIME was specified for the
parent key in the REFERENCES clause, but PERIOD An attempt was made to use table table-name in
BUSINESS_TIME was not specified in the child key in a CREATE or ALTER statement to define a foreign
the FOREIGN KEY clause. key or a clone table, or it was referenced in an
SQL manipulative statement. However, the current
• PERIOD BUSINESS_TIME was specified for both the status of the table is incomplete, so it cannot be
parent and child keys, but the semantic of the used as specified. The definition of the table may
BUSINESS_TIME period in the two tables is not the be incomplete because the table was defined with a
same. PRIMARY KEY clause, a UNIQUE clause, a referential
name is the constraint-name specified in the foreign constraint, or a ROWID column with the GENERATED
key clause or, if a constraint-name was not specified, BY DEFAULT attribute. The definition of the table is
the first column-name specified in the clause. incomplete, and it cannot be used until a required
index is defined for:
System action • the primary key (the primary index)
The statement cannot be processed. • a ROWID column
• for each set of columns in any UNIQUE clause (the
Programmer response required unique indexes).
• a foreign key of a temporal referential constraint
Correct the statement so that the description of the
foreign key references a primary key or unique key, or An attempt was made to use the table in a FOREIGN
so that the description of the foreign key conforms to KEY clause or in an SQL manipulative statement.
that of a parent key of the indicated table.
System action
SQLSTATE The statement cannot be processed.
42830
-539 TABLE table-name DOES NOT Programmer response
HAVE A PRIMARY KEY Define a primary index or a required unique index on
the table before referencing it.
Explanation
Db2 cannot perform the CREATE or ALTER TABLE SQLSTATE
statement because the indicated table does not have a 57001
primary key. Thus, the primary key cannot be dropped,
or the table cannot be defined as a parent in a -541 DUPLICATE TEMPORAL FOREIGN
referential constraint. KEY CONSTRAINT EXISTS FOR
TABLE table-name (constraint
name).
System action

Explanation -543 A ROW IN A PARENT TABLE
CANNOT BE DELETED BECAUSE
An attempt was made to add a FOREIGN KEY THE CHECK CONSTRAINT check-
constraint. The table already has a constraint that is constraint RESTRICTS THE
a duplicate of the constraint being added. A temporal DELETION
FOREIGN KEY constraint is a duplicate if the columns
in the constraint are the same as in another temporal
foreign key constraint. An attempt was made to use Explanation
the table in a FOREIGN KEY clause or in an SQL The delete operation cannot be executed because the
manipulative statement. target table is a parent table and is connected with
a referential constraint to a dependent table with a
System action delete rule of SET NULL. However, a check constraint
defined on the dependent table restricts the column
The statement cannot be processed. from containing a null value.

The constraint is already in effect. The DELETE statement was not executed. The
contents of the tables are unchanged.
SQLSTATE
-542 column-name CANNOT BE A Examine the foreign key and its delete rule in the
COLUMN OF A HASH KEY, dependent table and the conflicting check constraint.
PRIMARY KEY, A UNIQUE Change either the delete rule or the check constraint
CONSTRAINT, OR A PARENT KEY so that they do not conflict.
BECAUSE IT CAN CONTAIN NULL
VALUES SQLSTATE
23511
Explanation
-544 THE CHECK CONSTRAINT
A column that is identified in a HASH KEY, a PRIMARY SPECIFIED IN THE ALTER
KEY, a UNIQUE constraint clause, or a parent key TABLE STATEMENT CANNOT BE
(through a REFERENCES clause) is defined to allow ADDED BECAUSE AN EXISTING
null values. Null values are not permitted for these ROW VIOLATES THE CHECK
keys and clauses. CONSTRAINT

The statement cannot be processed. An existing row violates the check constraint specified
in the ALTER TABLE statement.
Programmer response
In the case of a column identified in a HASH KEY, a System action
PRIMARY KEY or a UNIQUE constraint clause, correct The statement cannot be processed. The check
the statement and resubmit it. constraint definition is not added to the table. The
In the case of a column identified in a REFERENCES table definition is unchanged.
clause:
1. Drop the parent table. Programmer response
2. Recreate it with referenced columns defined as Examine the check constraint definition that was
NOT NULL. specified in the ALTER TABLE statement and the
3. Resubmit the statement. data in the table to determine why the ALTER TABLE
statement was rejected.
SQLSTATE You can determine which rows violated the check

constraint by using the SELECT statement, negating
42831

the check constraint in the WHERE clause. For • The constraint definition refers to a column with a
example: numeric data type that is not the same numeric data
type as that of the other column operands.
SELECT * FROM table WHERE (NOT (check-
condition)); • The constraint definition refers to a column with a
length that is shorter than the other operands when
the column and other operands are not character
SQLSTATE string data types.
23512 • The constraint definition refers to a DECFLOAT
column.
-545 THE REQUESTED OPERATION IS
NOT ALLOWED BECAUSE A ROW • The constraint definition refers to a Db2 11 Unicode
DOES NOT SATISFY THE CHECK column in an EBCDIC table.
CONSTRAINT check-constraint • The constraint definition refers to a built-in or user-
defined function.
Explanation • The constraint definition uses a cast function that
requires conversion of the data. The only functions
Check constraint violations occurred on an INSERT, that are allowed in a check constraint are cast
UPDATE, or MERGE statement. The resulting row functions that do not require conversion of the data.
violated the check constraint definition on the table.
• The constraint definition contains a global variable.
System action • The constraint contains an XML column

• The constraint definition contains an XMLQuery
The INSERT, UPDATE, or MERGE statement cannot be
expression.
executed. The contents of the table are unchanged.
constraint-name
The name of the check constraint.
Programmer response
Examine the data and the check constraint definition System action
in the SYSIBM.SYSCHECKS catalog table to determine
why the INSERT, MERGE, DELETE, or UPDATE The statement cannot be processed.
statement was rejected. The data must be changed to
For ALTER TABLE, the check constraint is not added
satisfy the check constraint.
to the object table. The definition of the table is
unchanged.
SQLSTATE
For CREATE TABLE, the table is not created.
23513
-546 THE CHECK CONSTRAINT Programmer response
constraint-name IS INVALID Correct the check constraint definition and execute the
statement again.
Explanation
A check constraint in the CREATE TABLE or ALTER SQLSTATE
TABLE statement is invalid for one or more of the 42621
following reasons:
Related reference
• The constraint definition refers to a column that has
a field procedure.
• The constraint definition refers to a column with a
data type that is lower in the hierarchy of numeric -548 A CHECK CONSTRAINT THAT IS
data types than the data type of any other operand. DEFINED WITH column-name IS
The hierarchy is as follows: INVALID
small integer < large integer < decimal
< single precision float
< double precision float
Explanation
A check constraint in the CREATE TABLE or ALTER
TABLE statement is not valid for one or more of the
following reasons:

• The constraint definition refers to a column that has Related reference
a field procedure. ALTER TABLE (Db2 SQL)
• The constraint definition refers to a column with a CREATE TABLE (Db2 SQL)
data type that is lower in the hierarchy of numeric
data types than the data type of any other operand. -549 THE statement STATEMENT IS
The hierarchy is as follows: NOT ALLOWED FOR object_type1
object_name BECAUSE THE BIND
small integer < large integer OPTION DYNAMICRULES(RUN) IS
< big integer < decimal
< single precision float NOT IN EFFECT FOR object_type2
< double precision float
• The constraint definition refers to a column with a Explanation

numeric data type that is not the same numeric data A program attempted to issue the indicated SQL
type as that of the other column operands. statement that is one of several SQL statements that
• The constraint definition refers to a column with a cannot be issued from a plan or package for which the
length that is shorter than the other operands when option DYNAMICRULES(RUN) is not in effect. Those
the column and other operands are not character SQL statements are:
string data types.
• Dynamic GRANT statement
• The constraint definition refers to a ROWID column.
• Dynamic REVOKE statement
• The constraint definition refers to a LOB column.
• Dynamic ALTER statement
• The constraint definition refers to a DECFLOAT
• Dynamic CREATE statement
column.
• Dynamic DROP statement
• The constraint definition refers to a Db2 11 Unicode
column in an EBCDIC table. The indicated SQL statement is bound to one of the
• The constraint contains an XML column. following:
• The constraint definition contains an XMLQuery • The named plan or package that was not bound with
expression. the option DYNAMICRULES(RUN)
• An XMLQUERY or XMLEXISTS argument list • The named package that was not bound with the
contained two arguments with the same name. DYNAMICRULES option, but is appended to a plan
that was not bound with DYNAMICRULES(RUN)
• The generated column expression references a
column for a column mask is defined. statement
• The constraint definition contains a built-in function The SQL statement in error
that depends on the value of a special register. object_type1
• The constraint definition contains a global variable. PACKAGE or DBRM
object_name
If object_type1 is PACKAGE, object_name is the
System action
name of the package in the format 'location-
The statement cannot be processed. id.collection-id.package-id'.
For ALTER TABLE, the check constraint is not added If object_type1 is DBRM, object_name is the name
to the object table. The definition of the table is of the DBRM in the format 'plan-name DBRM-
unchanged. name'.
For CREATE TABLE, the table is not created. object_type2
PLAN or PACKAGE
Programmer response If object_type1 is PACKAGE, object_type2 can be
either PACKAGE or PLAN (whichever is bound with
Correct the check constraint definition, and execute
a DYNAMICRULES value other than RUN).
the statement again.
If object_type1 is DBRM, object_type2 is PLAN.
SQLSTATE
42621
System action

Programmer response object-name
The name of the object on which the operation was
Take one of the following actions to correct the error: to be performed.
• If the SQL statement is embedded, remove it, Some of the situations in which this error occurs are:
precompile and compile the application program
again, and reissue the BIND command with the • For an INSERT, DELETE, or UPDATE statement, the
appropriate DYNAMICRULES option. target object is a read-only view.
• Use the SQL statement with a package or plan that is • For a CREATE TABLE or CREATE VIEW statement, the
bound with DYNAMICRULES(RUN). authorization ID of the user who issues the CREATE
statement does not match the schema name of the
• Issue the REBIND command with the
object that is to be created.
DYNAMICRULES(RUN) option for the plan or package
to which the SQL statement is bound. You can create a table with a schema name
that is different from your authorization ID only
Determine if either the SQL statement should be
if your authorization ID has SYSADM, DBADM, or
removed from the program or the plan or package
DBCTRL authority. You can create a view from an
should be rebound with the DYNAMICRULES(RUN)
with a schema name that is different from your
option.
authorization ID only if your authorization ID has
SYSADM authority.
SQLSTATE
If you are using a trusted context, the auth-id value
42509 contains a role name if a role was in effect when
the condition was encountered, and the authorization
Related concepts
checking was performed against the role. In that case,
SQL processing options for dynamic statements the auth-id value is in the following format:
(Db2 SQL)
Related reference ROLE: role-name
DYNAMICRULES bind option (Db2 Commands)
If you use the RACF access control module for
BIND PACKAGE (DSN) (Db2 Commands)
authorization checking, auth-id might be different from
BIND PLAN (DSN) (Db2 Commands) the value that is reported in message ICH408I. The ID
REBIND PACKAGE (DSN) (Db2 Commands) that is reported in message ICH408I is the user ID that
REBIND PLAN (DSN) (Db2 Commands) RACF used to check the privilege.
In addition to the situations mentioned previously, this
-551 auth-id DOES NOT HAVE
error can occur for the following situations:
OPERATION operation ON OBJECT • When operation is GRANT ***, the keyword ALL was
object-name used in the GRANT statement, but the grantor auth-
id does not have any privilege to grant.
Explanation • When operation is GRANT (table or view privileges)
and the specified privilege cannot be granted on a
Authorization IDs or roles were checked for
view or auxiliary table.
authorization to perform an operation on a Db2 object.
None of the authorization IDs or roles were authorized • If operation is DROP PACKAGE, the object-name
to perform the operation. consists of the collection ID, the package name,
and the consistency token. The consistency token
auth-id uniquely identifies the version of the package that
One of the following values: the user does not have authorization to drop.
• A list of one to three authorization IDs that • If operation is USAGE OF DISTINCT TYPE, USAGE OF
were checked for authorization to perform the USER-DEFINED TYPE, or USAGE OF JAR, the object-
operation name identifies, respectively, the DISTINCT TYPE,
• A role name USER-DEFINED TYPE, or JAR for which the auth-id
lacks USAGE privilege.
operation
The operation for which authorization was • If operation is ALTER JAR, the auth-id lacks ALTERIN
checked. privilege on the schema of the JAR object-name.
• If this error occurs while Db2 is creating or altering
a table that involves referential constraints, this error
message reports that the user does not have the

necessary ALTER privilege to perform a FOREIGN System action
KEY, DROP FOREIGN KEY, DROP PRIMARY KEY, or
DROP UNIQUE operation. The object-name identifies The statement cannot be processed.
the object table of the CREATE or ALTER TABLE
statement, not the table for which the user lacks the Programmer response
ALTER privilege.
To correct the error, verify the following situations:
• If this error occurs for a distributed SQL request, one
of the following conditions can occur: • The auth-id has the authority to perform the
operation.
– If authorization ID translation is in effect for
either the requesting Db2 site or the serving • The object-name exists.
(responding) Db2 site, then auth-id is the • The auth-id is not trying to create a table with a
translated authorization ID. Refer to Part 3 schema qualifier that is not the same as auth-id.
(Volume 1) of the Db2 Administration Guide for • If you are using the access control authorization exit
information on authorization ID translation. with RACF, ensure that the authorization ID auth-id
– If an alias name was used in the SQL statement, is defined in RACF and was granted the required
the object-name is the resolved remote table privilege to perform the operation. Check the USER
name or view name. value in RACF message ICH408I to determine the
• If this error occurs during invocation of a routine, authorization ID that attempted to perform the
the authorization ID auth-id does not have the operation.
EXECUTE privilege on any candidate routine in the
SQL path. The variable for object-name is the name SQLSTATE
of a candidate routine in the SQL path.
42501
• An object does not exist, and the CURRENT RULES
special register is set to STD. -552 authorization-id DOES NOT HAVE
• This error might occur for packages that are
OPERATION operation
bound with the DYNAMICRULES(BIND) option when
authorization caching, statement caching, or both
are enabled and if the following conditions exist: Explanation
– The access control authorization exit routine is An operation was attempted by an authorization ID
active that lacks the required authority.
– The AUTHEXIT_CHECK subsystem parameter is authorization-id
set to PRIMARY The authorization ID that attempted to perform the
– The authorization ID of the process does not have operation.
the necessary privileges. If you are using a trusted context, the
• If the access control authorization exit is active and authorization-id value might be a role instead of an
the AUTHEXIT_CHECK subsystem parameter is set authorization ID. A role is returned if a role was in
to DB2, this error might occur if ACEE cannot be effect and the authorization checking is performed
created for the authorization ID auth-id. against the role, rather than the authorization ID of
• If operation is CREATE VARIABLE or DROP the session, when the condition was encountered.
VARIABLE, the auth-id lacks the necessary privileges Otherwise an authorization ID is returned. A role is
to perform this action. returned in the following format as a single token:
• When operation is CREATE, the OR REPLACE clause ROLE: role-name DOES NOT HAVE
was specified, and the object already exists, the THE PRIVILEGE TO PERFORM OPERATION
user who issues the statement must be the owner operation
of the object that is to be replaced. The security operation
administrator, who holds SECADM authority, can use The operation that was attempted.
the TRANSFER OWNERSHIP statement to transfer
the ownership of the object, if necessary. If you use the RACF access control module for
authorization checking, auth-id might be different from
• FL 509 If operation is UPDATE or DELETE and
the value that is reported in message ICH408I. The ID
object-name is SYSIBM.SYSAUDITPOLICIES, this
that is reported in message ICH408I is the user ID that
error might occur if the auth-id lacks access to the
RACF used to check the privilege.
audit policy profile in the RACF DSNR class.

-554 AN AUTHORIZATION ID OR ROLE
Administrator response CANNOT GRANT A PRIVILEGE TO
Check for an attempted authorization violation. ITSELF

Ensure that the authorization ID has been granted the An authorization ID or a role attempted to execute a
authority necessary to perform the operation. GRANT statement in which that ID itself appears as
one of the entries in the list of 'grantee' authorization
SECADM authority is required to revoke any of the IDs or role names.
following:
An authorization ID or a role cannot GRANT a privilege
• System DBADM authority to itself. However, if SQLRULES(STD) is in effect or
• DATAACCESS authority CURRENT RULES contains STD, GRANT to self is
allowed.
• ACCESSCTRL authority
• CREATE_SECURE_OBJECT privilege
System action
SQLSTATE The statement cannot be processed. No privileges
were granted.
42502
-553 AUTHORIZATION ID OR SCHEMA Programmer response
NAME name SPECIFIED IS
Remove the reference to the authorization ID that
NOT VALID FOR REQUESTED
issued the GRANT statement from the list of grantee
OPERATION
authorization IDs.
The statement failed for one of the following reasons:
42502
• The authorization ID specified as the value of name
Related reference
or host variable in the SQL SET CURRENT SQLID
statement is neither the user's primary authorization Statements (Db2 SQL)
ID nor one of the associated secondary authorization GRANT (Db2 SQL)
IDs. SQLRULES bind option (Db2 Commands)
• The authorization ID specified as the value of the CURRENT RULES (Db2 SQL)
PACKAGE OWNER option for a CREATE or ALTER
PROCEDURE statement is neither the user's primary -555 AN AUTHORIZATION ID OR ROLE
authorization ID nor one of the associated secondary CANNOT REVOKE A PRIVILEGE
authorization IDs. FROM ITSELF
• SYSPUBLIC cannot be specified as the schema for a
private alias for a sequence. Explanation
Schema names should not start with 'SYS' because An authorization ID or a role attempted to execute a
additional schemas that start with these letters REVOKE statement in which that ID itself appears as
might be reserved for exclusive use of Db2 products one of the entries in the list of authorization IDs or role
in the future. names to be revoked.
An authorization ID or a role cannot REVOKE its own
System action privilege. However, if SQLRULES(STD) is in effect or
CURRENT RULES contains STD, REVOKE from self is
allowed.
User response
Change the name to a value that the user can use.

System action A failed revocation attempt is commonly caused by
one or more of the following conditions:
The statement cannot be processed. No privileges
were revoked. • The authorization ID that was the target of the
REVOKE statement, revoke-target, does not possess
the privilege that was to be revoked.
Programmer response
• The revoking authorization ID, revoker-id, did not
Take one of the following actions and reissue the explicitly grant the privilege to revoke-target. An
REVOKE statement: authorization ID can revoke only the privileges
• Remove the authorization ID that issues the REVOKE that it has explicitly granted to other authorization
statement from the list of authorization IDs to be IDs, unless the authorization ID has SECADM or
revoked. ACCESSCTRL authority and specifies the BY clause.
• Issue the REVOKE statement from a different • The authorization ID revoke-target is the owner of
authorization ID. the specified object. No authorization ID, not even
SECADM, can revoke privileges on an object from the
object owner.
SQLSTATE
• If privilege is "***": The keyword ALL was used in
42502 the REVOKE statement, but revoke-target did not
possess any privilege to revoke.
Related reference
REVOKE (Db2 SQL) • If revoker-id is "ALL": The BY ALL clause was used
in the REVOKE statement, but revoke-target did not
CURRENT RULES (Db2 SQL)
possess any privilege to revoke.
-556 revoke-target CANNOT HAVE • If revoker-id holds SECADM or ACCESSCTRL
THE privilege PRIVILEGE object- authority: The BY clause might have been omitted
name REVOKED BY revoker-id from the REVOKE statement.
BECAUSE THE REVOKEE DOES
NOT POSSESS THE PRIVILEGE OR System action
THE REVOKER DID NOT MAKE THE
GRANT The statement was not executed. No privileges were
revoked from any authorization ID.
Explanation
Programmer response
The REVOKE statement was not successful.
Check the appropriate authorization catalog tables to
revoke-target
verify that revoke-target possesses the privilege to be
The authorization ID that the revoke attempt was
revoked. Issue a query with GRANTEE set to the value
made against.
in revoke-target and the privilege column not equal to
privilege blanks. Correct and reissue the REVOKE statement.
The name of the privilege that was to be revoked.
object-name SQLSTATE
The name of the object that the privilege applies
to. 42504
revoker-id -557 INCONSISTENT GRANT/REVOKE
The authorization ID that attempted to revoke the KEYWORD keyword. PERMITTED
privilege. KEYWORDS ARE keyword-list
If you are using a trusted context, the tokens revoke-
target and revoker-id might return a role instead of Explanation
an authorization ID. A role is returned if a role was
The GRANT or REVOKE statement contains a syntax
in effect and the authorization checking is performed
or spelling error at or before the specified 'keyword'.
against the role, rather than the authorization ID of
As an aid to the programmer, 'keyword-list' provides
the session, when the condition was encountered.
a list of the keywords that would be permitted in this
Otherwise an authorization ID is returned. A role is
context.
returned in the following format as a single token:
Alternatively:
ROLE: role-name

• The mixture of privileges specified on the GRANT or • ACCESSCTRL
REVOKE statement is not permitted. The privileges • CREATE_SECURE_OBJECT
must all be of one type, and consistent with the form
of the GRANT or REVOKE statement. These privileges cannot be granted to PUBLIC (public).
• REVOKE UPDATE (column-list) is not permitted; only
REVOKE UPDATE is valid. System action
• The keywords DELETE, INSERT, SELECT, TRIGGER, The statement cannot be processed.
UPDATE, REFERENCES and ALTER cannot be
specified for an auxiliary table.
Programmer response
System action Change the statement to specify a privilege that can
be granted to PUBLIC, or specify a grantee other than
The statement cannot be processed. PUBLIC.

Correct the syntax of the GRANT or REVOKE 42508
statement.
Related reference
GRANT (Db2 SQL)
SQLSTATE
42852 -567 bind-type AUTHORIZATION ERROR
USING auth-id AUTHORITY
-559 ALL AUTHORIZATION FUNCTIONS PACKAGE = package-name
HAVE BEEN DISABLED PRIVILEGE = privilege
The authorization mechanism has been disabled in the The authorization ID given does not have the
Db2 subsystem. Consequently, GRANT and REVOKE privilege indicated, and cannot invoke the indicated
statements are ignored. subcommand against the indicated package.
bind-type
System action Type of bind subcommand (BIND | REBIND |
The statement cannot be processed. No privileges FREE).
were granted or revoked. auth-id
Authorization ID of the package owner.
Programmer response package-name
Name of the package
Do not attempt to execute GRANT or REVOKE (location.collection.package.version)
statements unless and until the authorization
mechanism is enabled in the Db2 subsystem. privilege
Name of the privilege not held:
SQLSTATE • BINDADD—The authority to create a new

package using BIND with the ADD option.
57002
• BIND—The authority to BIND (REPLACE) or
-562 THE SPECIFIED PRIVILEGES REBIND a package.
CANNOT BE GRANTED TO PUBLIC. • COPY—The authority to COPY from the indicated
package
Explanation • CREATE IN—The authority to create a package in
The GRANT statement attempted to grant one of the the indicated collection.
following privileges to the reserved authorization ID If you are using a trusted context, the token auth-
PUBLIC (public): id might return a role instead of an authorization
• System DBADM ID. A role is returned if a role was in effect and
the authorization checking is performed against the
• DATAACCESS role, rather than the authorization ID of the session,

when the condition was encountered. Otherwise an System action
authorization ID is returned. A role is returned in the
following format as a single token: The statement cannot be processed.
• ROLE: role-name
Programmer response
System action • Ensure that all requests for modifications to the data
are confined to a single location within any given
The indicated package is not bound, rebound, or freed. commit scope for any application that references a
location that does not support multi-site update.
System programmer response • For programs operating in an IMS or CICS
The indicated privilege must be granted to the environment where the remote database systems do
authorization ID that will become the package owner. not support multi-site update, all SQL statements
must be read-only access.
• If an autobind is causing this SQLCODE to be issued,
SQLSTATE
REBIND the plan or package.
42501
-571 THE STATEMENT WOULD RESULT SQLSTATE
IN A MULTIPLE SITE UPDATE 25000
-573 TABLE table-name DOES NOT
Explanation
HAVE A UNIQUE KEY WITH THE
This SQLCODE is issued in the following situations: SPECIFIED COLUMN NAMES
• When an application program operating in an IMS
or CICS environment attempts to modify data at a Explanation
remote location where multi-site update capabilities
A referential constraint cannot be defined with the
are not supported.
specified table as the parent because a unique index
• When an application program has explicit SQL with the specified column names does not exist for the
statements within a commit scope that would result identified parent table.
in updates at multiple sites where one of the sites
at which data is being updated does not support
System action
multi-site update.
This SQLCODE can be issued when an application
program explicitly modifies data at a single location
within a commit scope. This can occur in the following Programmer response
situations:
Create a unique index with the specified columns for
• A package that is associated with the application the parent table.
program was invalidated.
• A package or plan was bound at one release of Db2 SQLSTATE
and fallback occurs to a prior release.
42890
In the situations described above, an implicit autobind
is done on behalf of the user. An autobind results in -574 THE SPECIFIED DEFAULT VALUE
the Db2 catalog being updated. The conditions that OR IDENTITY ATTRIBUTE
must exist for this SQLCODE to be issued when an VALUE CONFLICTS WITH THE
autobind occurs are: DEFINITION OF COLUMN column-
name
• One site where data has been modified does not
support multi-site update.
Explanation
• The autobind occurs at a separate and distinct
site from where an application program explicitly A value specified for a column is not valid.
modifies data. column-name
• At the time of the autobind, locks are being held The name of the column.
to process an SQL statement within the application
Possible reasons for this error include:
program.

• The value is not assignable to the column because -575 OBJECT object-name (OBJECT
the constant does not conform to the format for TYPE object-type) CANNOT BE
a constant of that data type, or the value has the REFERENCED EXPLICITLY OR
incorrect length or precision. IMPLICITLY
• A floating-point constant is specified and the column
is not a floating point data type. Explanation
• A decimal constant is specified and non-zero digits The statement referenced an object, but the object
would be truncated when assigned to the column. cannot be used as requested.
• The value is more than 255 bytes, including
object-name
quotation marks for strings, introducer characters
The name of the referenced object.
such as the X for a hex constant, fully qualified
function names, and parentheses. object-type
The type of object that was referenced. Possible
• Either the USER, or SESSION_USER, or CURRENT
values include:
SQLID special register is specified and the length
attribute of the character string column is not VIEW
sufficient to store a value that is 8 characters when An alteration was made to a table that
the value is expressed in CCSID 37. underlies the object-name view, which caused
• A system-generated cast function was specified the view definition to become invalid. The
and the column is not defined with a user-defined view must be successfully regenerated with
distinct type. an ALTER VIEW statement before it can be
referenced in a statement other than ALTER
• A function was specified that is not supported. A VIEW, GRANT, REVOKE, DROP, COMMENT, or
function can be specified only when the data type is LABEL. Issue an ALTER VIEW statement to
a distinct type, and in this case the specified function regenerate the view.
must be one of the system-generated cast functions
associated with this distinct type. ROW PERMISSION
The object-name row permission is invalid
• A value with non-zero scale was specified for the because a previous attempt to regenerate it
START WITH or INCREMENT BY option of an identity was unsuccessful. The row permission must
column with the DECIMAL data type. be disabled before the row access control
• A decimal floating point (DECFLOAT) constant is enforced table can be referenced. To correct
specified. A decimal floating point cannot be the invalid state, the row permission must
restricted to zero scale numbers and, as such, may be dropped and re-created with a modified
not be used in IDENTITY columns. definition.
• WITH DEFAULT is specified using a value other than COLUMN MASK
NULL for a LOB column without INLINE LENGTH The object-name column mask is invalid
attribute. because a previous attempt to regenerate it
• The length of the default value is greater than the was unsuccessful. The column mask must be
INLINE LENGTH attribute of the LOB column. disabled before the column access control
enforced table can be referenced. To correct
• A default value was specified for a timestamp with the invalid state, the column mask must
time zone column but the default value does not be dropped and re-created with a modified
contain a time zone. definition.

The statement cannot be processed. The statement cannot be processed.

Specify a default value that is valid for the definition of Take the suggested corrective action.
the column, and reissue the statement.
SQLSTATE
SQLSTATE
51024
42894

-577 object-type object-name Explanation
ATTEMPTED TO MODIFY DATA
WHEN THE DEFINITION OF THE The SQL function reached the end of the routine body
FUNCTION OR PROCEDURE DID without executing a RETURN statement.
NOT SPECIFY THIS ACTION function-name
Explanation
The current environment does not allow SQL
System action
statements that modify data. One of the following The statement cannot be processed.
situations has occurred:
• A user-defined function or stored procedure object- User response
name was invoked and attempted to modify data,
Add a RETURN statement to the function routine body,
but the function or procedure was defined without
and try the request again.
the MODIFIES SQL option.
• A user-defined function or stored procedure object-
name was invoked and attempted to execute a data SQLSTATE
definition statement, but the function or procedure 2F005
was defined without the MODIFIES SQL option.
• A function or procedure defined with READS SQL
ATTEMPTED TO READ DATA
DATA, CONTAINS SQL, or NO SQL has attempted to
WHEN THE DEFINITION OF THE
invoke another function or procedure defined with
FUNCTION OR PROCEDURE DID
MODIFIES SQL DATA.
NOT SPECIFY THIS ACTION
• A user-defined function or stored procedure object-
name was invoked and attempted to use a
Explanation
NEXT VALUE expression. However, the function or
procedure was defined without the MODIFIES SQL The current environment does not allow SQL
DATA option. statements that read data. One of the following
situations had occurred:
In an environment of nested functions and procedures,
the SQL option in effect is the most restrictive one that • A user-defined function or stored procedure object-
has been specified in the nested hierarchy of functions name was invoked and attempted to read data, but
and procedures. The SQL data access option in effect the function or procedure was defined without the
does not allow for modifying the data. READS SQL DATA or MODIFIES SQL DATA option.
• A function or procedure defined with CONTAINS SQL
System action or NO SQL has attempted to invoke another function
or procedure defined with READS SQL DATA.
In an environment of nested functions and procedures,
the SQL option in effect is the most restrictive one that
Programmer response
has been specified in the nested hierarchy of functions
Either use an ALTER statement to change the definition and procedures. The SQL data access option in effect
of the function or procedure to allow statements that does not allow for reading data.
modify data, or remove the failing SQL statement from
the external function or procedure. System action
The SQL statement failed.
SQLSTATE
-578 THE RETURN STATEMENT WAS Either use an ALTER statement to change the definition
NOT EXECUTED FOR SQL of the function or procedure to allow statements that
FUNCTION function-name. read data, or remove the failing SQL statement from
the external function or procedure.

SQLSTATE type to an array variable depend on the statement that
specifies the assignment. See Array type assignments
38004 (Db2 SQL) for more information.
-580 THE RESULT-EXPRESSIONS OF A
CASE EXPRESSION CANNOT ALL System action
BE NULL
Explanation
Programmer response
There is a CASE expression in the statement that has
all the result-expressions (expressions following the Correct the result-expressions so that they are
THEN and ELSE keywords) coded with the keyword compatible.
NULL.
SQLSTATE
System action 42804
The statement cannot be processed. -582 THE SEARCH-CONDITION IN
A SEARCHED-WHEN-CLAUSE OF
Programmer response A CASE IS NOT VALID IN
THE CONTEXT IN WHICH
Change the CASE expression to include at least one IT WAS SPECIFIED. THE
result-expression with a keyword other than NULL. SEARCH CONDITION CONTAINS A
QUANTIFIED PREDICATE OR AN
SQLSTATE IN PREDICATE THAT INCLUDES
A FULLSELECT, AND THESE ARE
42625 NOT ALLOWED IN THE SPECIFIED
-581 THE DATA TYPES OF THE CONTEXT.
RESULT-EXPRESSIONS OF A
CASE EXPRESSION ARE NOT Explanation
COMPATIBLE
The search-condition in a searched-when-clause
specifies a quantified predicate, an IN predicate, or
Explanation an EXISTS predicate, but is not allowed. However, an
There is a CASE expression in the statement that has IN predicate is allowed within a select list or VALUES
result-expressions (expressions following THEN and clause if that IN predicate explicitly includes a list of
ELSE keywords) that are not compatible. The data expressions.
type of the result-expressions might be incompatible The search-condition in a searched-when-clause
because the CASE condition result data types are not specifies a quantified predicate or an IN predicate
all: that includes a fullselect. A CASE specification that
• character includes either of these cannot be used in the
following contexts:
• graphic
• numeric • A SELECT list
• date • A VALUES clause of an INSERT or MERGE statement
• time • A SET or assignment clause of an UPDATE, MERGE,

or DELETE statement
• timestamp
• The right side of a SET or an assignment statement
• binary string
• A column mask or row permission definition
• user-defined type
The search-condition in a searched-when-clause
If encoded in Unicode, character and graphic data specified an EXISTS predicate. A CASE specification
types are compatible, however. that includes an EXISTS predicate cannot be used in
An array value with a user-defined array type can the following contexts:
be assigned only to an array variable that is defined • A VALUES clause of an INSERT or MERGE statement
as the same user-defined array type. The rules for
assigning an array value without a user-defined array • The right side of a SET or an assignment statement

• The diagnostic-string-expression of a SIGNAL use the alternate form of the statements that make
statement that intent explicit.
• An ORDER BY clause or a GROUP BY clause • Instead of a simple-when-clause, use the
corresponding searched-when-clause where the
System action function or expression would be specified in each
search-condition.
• Remove the WITH CHECK OPTION from the CREATE
VIEW statement.
Programmer response • Remove the function or expression from the ORDER
Correct the syntax, and reissue the statement. BY clause. If the column is part of the result set of
the query, change the expression in the ORDER BY
clause to the simple-integer or simple-column-name
SQLSTATE
form of the sort key.
42625 • Remove the function or expression from the GROUP
-583 THE USE OF FUNCTION BY clause.
OR EXPRESSION name IS • Remove the expression that generates the value of
INVALID BECAUSE IT IS NOT an index for an array.
DETERMINISTIC OR HAS AN • Remove the expression from the OFFSET or FETCH
EXTERNAL ACTION FIRST clause.
• Change the comparison operator in the row-value-
Explanation expression, or remove the comparison with the row-
The function name is defined as a non-deterministic value-expression.
function or a function with an external action, or the
expression name is defined as a non-deterministic SQLSTATE
expression. This type of function or expression is not
supported in the context in which it is used. The 42845
contexts in which these are not valid are: Related concepts
• In the expression prior to the first WHEN keyword in Queries (Db2 SQL)
a simple-case-expression. Related reference
• In the WHERE clause of the fullselect in a CREATE CASE expressions (Db2 SQL)
VIEW statement if the WITH CHECK OPTION is CREATE VIEW (Db2 SQL)
specified. CREATE INDEX (Db2 SQL)
• In an expression of an ORDER BY clause
-584 INVALID USE OF NULL OR
• In a key-expression of an index definition
DEFAULT
• In an expression of a GROUP BY clause
• In an expression that generates the value of an index Explanation
for an array
The NULL or DEFAULT keyword is not valid as
• In an OFFSET or FETCH FIRST clause
specified. One of the following error situations
• In a row-value-expression if the comparison operator occurred:
is <, <=, >, or >=
• The NULL keyword was used in the USING source-
table clause of the MERGE statement, but the NULL
System action keyword was not explicitly cast to a supported data
The statement cannot be processed. type.
• In a SET assignment-statement statement, DEFAULT
Programmer response was assigned to a variable other than a global
variable.
If the use of a non-deterministic or external action • A CREATE VARIABLE statement was used to define
function or expression was not intended, substitute a a global variable as an array type. The DEFAULT
function or expression without these characteristics. constant or DEFAULT special-register clause was
If the behavior associated with the non-deterministic specified in the CREATE VARIABLE statement. Only
or external action function or expression is intentional, DEFAULT NULL is allowed.

• The DEFAULT keyword was specified as the source -586 THE TOTAL LENGTH OF
value for a transition variable in a SET assignment- THE CURRENT PATH SPECIAL
statement statement that assigns values to multiple REGISTER CANNOT EXCEED 2048
targets, and either all of the targets were not CHARACTERS
transition variables, or all of the source values were
not specified with the DEFAULT keyword.
Explanation
System action The CURRENT PATH special register is defined as a
VARCHAR(2048). The content of the string includes
The statement cannot be processed. each schema name delimited with double quotes and
separated from the next schema name by a comma.
User response The total length of the string of all schema names in
the CURRENT PATH cannot exceed 2048 characters.
Take one of the following actions: A SET PATH statement causing this message would
• Specify the NULL keyword within a CAST expression exceed this limit.
when using NULL within the USING VALUES clause of
the MERGE statement. System action
• Do not assign DEFAULT to any variable other than a The statement cannot be processed.
global variable.
• In a CREATE VARIABLE statement that is used Programmer response
to define a global variable as an array type, do
not assign DEFAULT constant or DEFAULT special- Remove schema names to reduce the total length
register to the global variable. to fit the 2048 character maximum length. If all the
schema names are required, it may be necessary to
• Do not assign DEFAULT to a transition variable in
consolidate some user-defined functions so that fewer
a SET assignment-statement statement that assigns
schema names are required for the CURRENT PATH.
values to multiple targets if all the targets are not
transition variables, or if all the source values are
not specified as the DEFAULT keyword. Replace SQLSTATE
the single assignment statement with separate
42907
assignment statements.
-589 A POSITIONED DELETE OR
SQLSTATE UPDATE STATEMENT FOR CURSOR
cursor-name SPECIFIED A ROW OF
42608 A ROWSET, BUT THE CURSOR IS
NOT POSITIONED ON A ROWSET
-585 THE COLLECTION collection-id
APPEARS MORE THAN ONCE
IN THE SET special-register Explanation
STATEMENT
The FOR ROW n OF ROWSET clause was specified on
a positioned DELETE or UPDATE statement, but the
Explanation cursor is not currently positioned on a rowset.
The SET statement for special register special-register
includes collection-id more than once. System action
System action
Issue a FETCH statement to position the cursor on
Programmer response the correct rowset, and then reissue the positioned
DELETE or UPDATE statement. If the cursor is not
Remove duplicate occurrences of collection-id from
defined for rowset access, redefine the cursor first.
the SET statement for the special register.
SQLSTATE SQLSTATE
24520
42732

-590 NAME name IS NOT UNIQUE -592 NOT AUTHORIZED TO CREATE
IN THE CREATE OR ALTER FOR OR ALTER FUNCTIONS,
ROUTINE OR TRIGGER object- PROCEDURES, OR TRIGGERS IN
name WLM ENVIRONMENT env-name
The name that is specified for a parameter, SQL This message is issued when the check for
variable, cursor, label, or condition in a CREATE or authorization to the WLM application environment in
ALTER statement for a routine or advanced trigger is env-name token failed.
not unique.
name System action
The item name that is not unique within the routine
or trigger.
object-name
The name of the routine or trigger that contains the
Programmer response
duplicate item names. To correct the error, choose a different value for the
WLM ENVIRONMENT keyword or request authorization
The value for name must adhere to the following rules:
to create objects in the specified WLM ENVIRONMENT
• A parameter name must be unique within the from the system administrator. Then, reissue the SQL
parameter list. statement.
• An SQL variable name must be unique within
the compound statement in which it is declared, SQLSTATE
excluding any declarations within compound
statements that are nested within the compound 42510
statement that declares the SQL variable. -593 NOT NULL MUST BE SPECIFIED
• An SQL variable name must not be the same as a FOR column-name BECAUSE IT
parameter name. IS DEFINED AS A ROWID (OR
• A cursor name must be unique within the routine DISTINCT TYPE FOR ROWID),
or trigger in which it is declared, excluding any ROW CHANGE TIMESTAMP
declaration within compound statements that are COLUMN, ROW BEGIN COLUMN,
nested within the compound statement that declares ROW END COLUMN, OR COLUMN
the cursor. OF A PERIOD column-name
• A condition name must be unique within the

compound statement in which it is declared, Explanation
excluding any declarations within compound The NOT NULL clause was specified for a column
statements that are nested within the compound whose type does not permit null values.
statement that declares the condition.
column-name
• A label must be unique within a compound The name of the column that requires the NOT
statement, including any labels within compound NULL clause.
statements that are nested within the compound
statement that defines the label. The following columns do not permit null values:
• ROWID columns
System action • Distinct type columns for which the source type is
The statement cannot be processed. ROWID
• Row change timestamp columns
Programmer response • Row begin columns and row end columns
Change the name so that it is unique. • Columns of a period
When one of these columns is defined on a CREATE
SQLSTATE TABLE, ALTER TABLE, or DECLARE TABLE statement,
the NOT NULL clause must be specified for the
42734 column.

System action object-name
object-type
The type of object.
Programmer response
This message can be issued for different situations,
Change the statement to specify the NOT NULL clause. including the following examples, among others:
ALTER statements
SQLSTATE An ALTER statement attempted to alter an object.
42831 object-type=TABLE
Related reference An ALTER statement attempted to add a clone
table, but an object of the same type with the
same name already exists in the catalog table
SYSIBM.SYSPENDINGOBJECTS.
-594 ATTEMPT TO CREATE A NULLABLE
ROWID OR DISTINCT TYPE object-type=VERSION
COLUMN column-name An ALTER statement attempted to define a new
version of an SQL routine or advanced trigger
and specified a version identifier that already
Explanation
exists for the specified object.
A CREATE VIEW statement attempted to create a new object-type=VOLUME
view with a nullable ROWID column. ROWID columns An ALTER statement attempted to add a
(or distinct type columns for which the source type volume name to a storage group, but a volume
is a ROWID) do not support null values. One of the with volume serial number already exists for
following situations has occurred: the storage group.
• The subselect of a CREATE VIEW statement involves CREATE statements
an outer join for which a column of the result table is A CREATE statement attempted to create an object
a ROWID column that needs to allow for null values. object-name of type object-type, but an object of
that type with the same name is already defined in
System action the Db2 subsystem.
The statement cannot be processed. A CREATE statement failed because an

object of the same type with the same
name already exists in the catalog table
Programmer response SYSIBM.SYSPENDINGOBJECTS.
Change the content of the statement so that it does object-type=CONSTRAINT
not try to create a ROWID column which must allow for The object name was specified in the FOREIGN
null values. KEY clause, CHECK clause, PRIMARY KEY
clause, or UNIQUE clause of either a CREATE
SQLSTATE or ALTER TABLE statement. All referential
integrity, check constraint, primary key, and
42831 unique key constraint names defined on a table
-601 THE NAME (VERSION OR VOLUME must be unique.
SERIAL NUMBER) OF THE OBJECT object-type=DISTINCT TYPE
TO BE DEFINED OR THE TARGET If a CREATE DISTINCT TYPE statement failed,
OF A RENAME STATEMENT IS a user-defined type already exists with the
IDENTICAL TO THE EXISTING same name as the distinct type name specified
NAME (VERSION OR VOLUME in the CREATE DISTINCT TYPE statement.
SERIAL NUMBER) object-name OF
object-type=FUNCTION
THE OBJECT TYPE object-type
If a CREATE FUNCTION statement failed,
a routine already exists with the same
Explanation name as the name specified in the CREATE
FUNCTION statement. If a CREATE DISTINCT
An attempt to name an object failed because the name
TYPE statement failed, a user-defined function
is already in use for an object of the same type.
already exists with the same name as the

distinct type that is specified in the CREATE object-type=TABLE
DISTINCT TYPE statement. If a CREATE ALIAS statement failed, the
alias name specified in the CREATE ALIAS
If the error was encountered for a particular
statement is identical to the table name or
version of an SQL function, the object-name
view name specified. The table might not exist
token might return the name and version of
in the Db2 subsystem.
the function, in the following format: function-
name VERSION version-id. object-type=TRIGGER
If a CREATE TRIGGER statement failed, a
object-type=INDEX trigger already exists with the same name as
If a CREATE INDEX statement failed, an the name specified in the CREATE TRIGGER
index already exists with the same name as statement.
the name specified in the CREATE INDEX
statement. If the error was encountered for a particular
version of a trigger, the object-name token
object-type=JAR
might return the name and version of the
If an invocation of procedure
trigger, in the following format: trigger-name
SQLJ.INSTALL_JAR failed, a JAR already
VERSION version-id.
exists with the same name as the name
specified on the invocation of procedure object-type=TRUSTED CONTEXT
SQLJ.INSTALL_JAR. If a CREATE TRUSTED CONTEXT statement
object-type=MASK failed, a trusted context already exists with
If a CREATE MASK statement failed, the the same name as the name specified in the
column mask name identifies a column mask CREATE TRUSTED CONTEXT statement.
that already exists at the current server. object-type=VARIABLE
object-type=PERMISSION If a CREATE VARIABLE statement failed, the
If a CREATE PERMISSION statement failed, name of global variable that was specified in
the row permission name identifies a row the CREATE VARIABLE statement is identical
permission that already exists at the current to the name of a global variable that already
server. exists at this server.
object-type=PROCEDURE object-type=VIEW
If a CREATE PROCEDURE statement failed, a If a CREATE ALIAS statement failed, the
routine already exists with the same name as alias name specified in the CREATE ALIAS
the name specified in the CREATE PROCEDURE statement is identical to the table name or
statement. If the CREATE PROCEDURE view name specified. The view might not exist
statement for an SQL procedure failed, then in the Db2 subsystem.
an SQL procedure might already with the same object-type=XSR SCHEMA
name as the external name that was implicitly If an invocation of procedure
or explicitly specified. SYSPROC.XSR_REGISTER failed, an XSR XML
If the error was encountered for a particular schema already exists with the same name
version of a native SQL procedure, the object- as the name specified on the invocation of
name token might return the name and version procedure SYSPROC.XSR_REGISTER.
of the procedure, in the following format: RENAME statements
procedure-name VERSION version-id An object with the same name as the target
name already exists in the catalog table
.
SYSIBM.SYSPENDINGOBJECTS.
object-type=ROLE
If a CREATE ROLE statement failed, a role
already exists with the same name as the System action
name specified in the CREATE ROLE statement. The statement cannot be processed.
object-type=SEQUENCE
If a CREATE SEQUENCE statement failed, a Programmer response
sequence already exists with the same name
as the sequence name that was specified in the Either drop or remove the existing object or choose
CREATE SEQUENCE statement. another name.
If the object-type is a data set, consider one of the
following actions:

• Verify that the correct integrated catalog facility Explanation
catalog is specified in the storage group definition.
The ICF catalog is identified in the VCATNAME The index that is defined in the CREATE INDEX
column of SYSIBM.SYSSTOGROUP catalog table. statement could not be created as unique because
the specified table already contains rows that are
• Issue an IDCAMS DELETE of the data set before duplicates with respect to the values of the identified
retrying the CREATE statement. columns and periods.

46002
Related concepts Programmer response
Naming conventions (Db2 SQL) Examine the data to determine whether or not the
Qualification of unqualified object names (Db2 duplicate data is valid. Alternatively, consider creating
SQL) a nonunique index.
Related reference
SYSPENDINGOBJECTS catalog table (Db2 SQL) SQLSTATE
-602 TOO MANY COLUMNS, PERIODS, 23515
OR KEY-EXPRESSIONS SPECIFIED Related reference
IN A CREATE INDEX OR ALTER CREATE INDEX (Db2 SQL)
INDEX STATEMENT
-604 A DATA TYPE DEFINITION
Explanation SPECIFIES AN INVALID
ATTRIBUTE SUCH AS LENGTH,
One of the following specifications in a CREATE INDEX PRECISION, OR SCALE
or ALTER INDEX statement exceeds the permitted ATTRIBUTE
maximum value of 64:
• The sum of the number of columns and twice the Explanation
number of identified periods:
A data type definition in a CREATE or ALTER statement
columns + (2 × periods) is incorrect in one of the following ways:
• The number of key-expressions. • The data type definition contains an invalid length,
precision, or scale attribute specification.
System action • The specification of the data type might be incorrect
The statement cannot be processed. or invalid.
• The column definition in a view referenced in a
Programmer response CREATE TABLE LIKE view statement has an invalid
length.
Modify the index definition to conform to the system-
imposed column or key-expression limit of 64.
System action
SQLSTATE The statement cannot be processed. The specified
object was not created or altered.
54008
Related reference Programmer response
Statements (Db2 SQL) Correct the statement syntax as follows, and resubmit
the statement:
-603 A UNIQUE INDEX CANNOT BE
CREATED BECAUSE THE TABLE • Correct the data type definition in the statement to
CONTAINS ROWS WHICH ARE have a valid length, precision, or scale attribute.
DUPLICATES WITH RESPECT TO • Ensure that the specified data types are valid for the
THE VALUES OF THE IDENTIFIED CREATE or ALTER statement.
COLUMNS AND PERIODS

• Correct the invalid length in the column definition • The operation is a SELECT statement, and a target
of the view that is referenced in the CREATE TABLE of the operation is a directory object. Db2 cannot
LIKE statement. convert the SELECT statement to the UR isolation
level. For example, the following SQL statement
SQLSTATE cannot be executed because the SELECT operation
against directory object SYSIBM.SYSLGRNX cannot
42611 be converted to the UR isolation level:
Related concepts UPDATE T1 SET C1 = (SELECT C1 FROM T1)
Data types (Db2 SQL) WHERE EXISTS(
SELECT LGRDBID FROM SYSIBM.SYSLGRNX);
-607 OPERATION OR OPTION operation • FL 508 An ALTER TABLESPACE statement that

IS NOT DEFINED FOR THIS includes a MOVE TABLE clause must not specify a
OBJECT catalog or directory table space.

The operation or option cannot be performed on the The statement cannot be processed.
object specified in the SQL statement.
For example, this SQL code might be issued for the Programmer response
following situations:
If an option of the SQL statement is not allowed for
• The ownership of most system objects cannot be this object, modify the SQL statement and resubmit
transferred if their OWNER is SYSIBM or if their the statement. If an operation is not defined for the
schema begins with SYS. object, the statement cannot be executed.
• LOGGED and NOT LOGGED cannot be set when you
create or alter a table space in the Db2 catalog SQLSTATE
(DSNDB06) database.
42832
• Catalog and directory objects cannot be cloned.
• Data change operations such as these cannot be -611 ONLY LOCKMAX 0 CAN BE
performed on a directory table: SPECIFIED WHEN THE LOCK
SIZE OF THE TABLESPACE IS
– ALTER TABLE TABLESPACE OR TABLE
– ALTER TABLESPACE
– DELETE Explanation
– MERGE This message is issued when:
– UPDATE
• The LOCKSIZE of the table space is TABLESPACE or
– RENAME TABLE TABLE, and LOCKMAX is being altered to or created
• The following operations are not allowed for an index as a nonzero value.
on a directory table: • The LOCKSIZE of the table space is being altered
– ALTER INDEX to TABLESPACE or TABLE, and LOCKMAX is being
altered to or created as a nonzero value.
– CREATE INDEX
If LOCKSIZE is TABLESPACE or TABLE, LOCKMAX must
– DROP INDEX
be 0 because lock escalation is not supported from
– RENAME INDEX these levels.
• A directory table cannot be:
– The parent table in a referential relationship System action
– The triggering table in a trigger The statement cannot be processed.
• An ALTER TABLE statement that specifies operation
cannot be specified on a catalog table. Programmer response
• A period specification must not be used if the table Do one of the following:
reference is not a table.
• Reissue the statement with LOCKMAX 0.

• Alter the LOCKSIZE of the table space to a value XMLQUERY function or XMLEXISTS predicate
other than TABLESPACE or TABLE.
• The PASSING clause of an XMLQUERY function
or an XMLEXISTS predicate contains two
SQLSTATE arguments with the same name.
53088 • An XMLQUERY or XMLEXISTS argument list
contains two arguments with the same name.
-612 identifier IS A DUPLICATE NAME
SQL data change statements
Explanation • The SQL data change statement uses an include
column, and the column name that is specified is
A non-unique name was specified where a unique the same as another column name of the target
name is required. Column and period names must be table or view, or of another include column.
unique within an index, a table, or a view, and in the
UPDATE OF clause of a trigger definition.
System action
identifier
The non-unique name. The statement cannot be processed.

Programmer response
CREATE INDEX and ALTER INDEX statements
Correct the statement syntax, and reissue the
• The same column name is specified for two or statement.
more columns of the index.
CREATE TABLE and ALTER TABLE statements SQLSTATE
• The same column name is specified for two or 42711
more columns of the table.
Related reference
• A constraint specifies an XML column and the
constraint definition contains an expression that
invokes the XMLQUERY function or uses the
-613 THE PRIMARY KEY OR A HASH
XMLEXISTS predicate.
KEY OR A UNIQUE CONSTRAINT
• The same period name is specified for two or IS TOO LONG OR HAS TOO MANY
more columns of the table. COLUMNS AND PERIODS
• The same period is specified more than one time
in the constraint. Explanation
• A period and a column are defined with the same The number of columns and periods that are defined
name. for a PRIMARY KEY or UNIQUE constraint is too large.
• For a CREATE TABLE statement, a column list Both of the following conditions must be met:
of a PRIMARY KEY, FOREIGN KEY, or UNIQUE
• The total of the number of columns and two times
clause contains two or more occurrences of the
the number of identified periods must not exceed
same column name.
64.
• A column is specified more than once in
• The sum of the column length attributes of the
an ALTER TABLE statement. With only one
identified columns and the begin and end columns of
exception, a column cannot be specified in
any identified periods must not exceed the permitted
multiple clauses of an ALTER TABLE statement.
limit for the type of constraint.
The exception is when the two clauses are ALTER
COLUMN and ADD CHECK CONSTRAINT. If the failing statement was an ALTER TABLE
statement that included the SET DATA TYPE clause
CREATE VIEW statements
to alter the definition of an existing column, a
• The same column name is specified for two or column being changed is part of a unique or primary
more columns of the view constraint. The new sum of the lengths of the columns
of the keys exceeds 2000-n-2m, where n is the
CREATE TRIGGER statements
number of nullable columns and m is the number of
• For a CREATE TRIGGER statement, the UPDATE varying length columns. This sum currently exceeds
OF clause specifies the same column name more the maximum number that is allowed.
than once.

If the failing statement was an ALTER TABLE Programmer response
statement with a PARTITIONING KEY specification,
only 64 columns can be specified, and the combined The definition for the index must be modified (possibly
lengths of all columns specified in the PARTITIONING by eliminating one or more key columns) to reduce the
KEY clause exceeds the maximum length of 255-n, length of the key to the permitted maximum.
where n is the number of columns that can contain null
values. SQLSTATE
The failing statement might have been either CREATE 54008
TABLE with an ORGANIZE BY HASH specification or
an ALTER TABLE with an ADD ORGANIZE BY HASH Related reference
specification. ALTER INDEX (Db2 SQL)
CREATE INDEX (Db2 SQL)
System action Limits in Db2 for z/OS (Db2 SQL)
The statement cannot be processed. -615 operation-type IS NOT ALLOWED

ON A PACKAGE IN USE
Programmer response
Change the table definition to keep within the
Explanation
prescribed limits. The operation cannot be performed because the
package is in use by the same application process,
SQLSTATE or the package is dependent on an object that is the
target of a DROP statement.
54008
operation-type
-614 THE INDEX CANNOT BE CREATED Type of bind operation (BIND, REBIND or DROP).
OR ALTERED, OR THE LENGTH
OF A COLUMN CANNOT BE
System action
CHANGED BECAUSE THE SUM OF
THE INTERNAL LENGTHS OF THE The BIND, REBIND, or DROP operation on the package
COLUMNS FOR THE INDEX IS is not performed.
GREATER THAN THE ALLOWABLE
MAXIMUM
Programmer response
Explanation Take one of the following actions:
• Change the application to invoke the BIND, REBIND
The index could not be created or the length of a
or DROP operation when the package is not in use by
column cannot be changed because the sum of the
the same application process.
internal lengths of the key columns would exceed
the allowable maximum. The maximum permitted key • Drop the object when the package is not in use.
length is as follows:
• For PADDED indexes, the sum of the length SQLSTATE
attributes of the columns must not be greater than 55006
2000-n, where n is the number of columns that
contain null values. -616 obj-type1 obj-name1 CANNOT
BE DROPPED BECAUSE IT IS
• For NOT PADDED indexes, the sum of the length
REFERENCED BY obj-type2 obj-
attributes of the columns must not be greater than
name2
2000 - n - 2m - 3d, where n is the number of nullable
columns, m is the number of varying length columns,
and d is the number of DECFLOAT columns. Explanation
Some types of objects cannot be dropped if there are
System action other objects which are dependent upon them. For
example, a storage group cannot be dropped if there
are one or more existing table spaces that use that
index was not created or the length of the column was
storage group.
not changed.

Execution of the specified DROP statement would drop SQLSTATE
object obj-name1 of type obj-type1 on which object
obj-name2 of type obj-type2 is dependent. 42832
-619 OPERATION DISALLOWED
System action BECAUSE THE DATABASE IS NOT
STOPPED
object was not dropped.
Explanation
Programmer response The statements CREATE, ALTER or DROP for a table
space, table, or index in the database cannot be
Verify that the object specified in the DROP statement processed unless the database is stopped (using the
was, indeed, the object to be dropped. If so, all the STOP command).
existing objects that have a dependency on that object
must first be dropped.
System action
A LOB table space cannot be dropped when an
association exists between it and another table space. The statement cannot be processed.
The associated base table must be dropped first.
A populated auxiliary table and its index can only be Programmer response
dropped by dropping the associated base table. Issue the -DISPLAY DATABASE command to verify that
A trigger package cannot be explicitly dropped. It can the RTS database is stopped before resubmitting the
only be dropped by dropping the associated trigger statement.
with a DROP TRIGGER statement or by dropping the
triggering table. SQLSTATE
55011
SQLSTATE
-620 KEYWORD keyword IN stmt-type
42893 STATEMENT IS NOT PERMITTED
-618 OPERATION operation IS NOT FOR A space-type SPACE IN THE
ALLOWED ON SYSTEM DATABASES database-type DATABASE
System databases cannot be the object of certain The specified keyword in the SQL statement stmt-type
types of operations. The attempted operation cannot indicates an attribute that is not allowed for a space-
be performed on system databases. Possible reasons type space in a database-type database. For example,
are: you cannot set LOGGED or NOT LOGGED when you
create or alter a table space in a WORK FILE database.
• CCSID ASCII was specified when a system database
was being created. keyword
Specifies the keyword that is not allowed.
• APPEND was specified when a system database was
being created. stmt-type
One of the following values:
• TRANSFER OWNERSHIP was issued to transfer the
ownership of a system database. CREATE
CREATE TABLESPACE or CREATE INDEX
System action ALTER
ALTER TABLESPACE or ALTER INDEX
The statement cannot be processed. No changes were
space-type
made to the specified system database.
One of the following values:
TABLE
User response
Table space
Do not attempt to perform the requested operation on INDEX
system databases. Index space

database-type -622 FOR MIXED DATA IS INVALID
One of the following values: WORK FILE or TEMP. BECAUSE THE MIXED DATA
INSTALL OPTION IS NO
System action
Explanation
FOR MIXED DATA is specified in a column, variable
Programmer response or SQL parameter declaration, but the MIXED DATA
installation option is set to NO. FOR MIXED DATA is
Correct and resubmit the statement. valid only when the MIXED DATA installation option is
set to YES.
SQLSTATE
53001
System action
Creation of temporary tables (Introduction to
Db2 for z/OS) Programmer response
Related reference Either change the installation option or the FOR clause.
ALTER INDEX (Db2 SQL) If the installation option is correctly set to NO, the
ALTER TABLESPACE (Db2 SQL) allowable FOR clause options are BIT and SBCS.
CREATE TABLESPACE (Db2 SQL) SQLSTATE
-621 DUPLICATE DBID dbid WAS 56031
DETECTED AND PREVIOUSLY -623 CLUSTER IS NOT VALID FOR table-
ASSIGNED TO database-name name
The current database being created was assigned a A table can have only one cluster index, and hash
DBID of 'dbid', which is identical to the DBID assigned organization cannot be used when a table has a
to database 'database-name'. An inconsistency exists clustering index.
between the Db2 catalog and directory.
table-name
The name of the table.
System action
The CLUSTER option cannot be specified for one of the
The statement cannot be processed. No new object following reasons:
was created, and the existing object was not altered or
modified. • A CREATE INDEX statement attempted to create a
cluster index on the specified table, but a clustering
index already exists on the table.
• An ALTER INDEX statement specified the CLUSTER
If you suspect an error in Db2, you might need to clause, but there is already a clustering index
report the problem. For information about identifying defined for the table.
and reporting the problem, see Collecting diagnostic
data (Collecting data).
System action
Notify the system programmer. The inconsistency

must be corrected before CREATE DATABASE will be
Programmer response
successful. Check to determine the identity and validity of the
existing cluster index on or use of hash organization
SQLSTATE with the object table. Alternatively, consider creating
the index without the CLUSTER attribute.
58001

55012 Make sure the key list specified on the ALTER
TABLE statement identifies an existing unique index
-624 TABLE table-name ALREADY HAS
of the table that is not already enforcing referential
A PRIMARY KEY OR UNIQUE
constraints.
CONSTRAINT WITH SPECIFIED
COLUMNS AND PERIODS
SQLSTATE
Explanation 55014
An ALTER TABLE statement cannot be processed for -626 THE ALTER STATEMENT IS NOT
one of the following reasons: EXECUTABLE BECAUSE THE PAGE
SET IS NOT STOPPED
• The table already has a primary key.
• The table has an existing unique constraint with the
same definition as the new key. (The existing set
Explanation
of columns and periods is specified in the ALTER An ALTER statement specifies an ADD PART, USING,
statement.) PRIQTY, SECQTY, ERASE, or GBPCACHE clause, but
the page set is not stopped.
System action
System action
Programmer response
Do not attempt to define a table with more than one
Programmer response
primary key, or a unique constraint that duplicates the Stop the page set and resubmit the statement.
definition of an existing unique constraint.
SQLSTATE
SQLSTATE
55015
42889
-627 THE ALTER STATEMENT IS
Related reference INVALID BECAUSE THE TABLE
ALTER TABLE (Db2 SQL) SPACE OR INDEX HAS USER-
MANAGED DATA SETS
-625 TABLE table-name DOES NOT
HAVE AN INDEX TO ENFORCE THE
UNIQUENESS OF THE PRIMARY
Explanation
OR UNIQUE KEY This error is issued for the following reasons:
• A CREATE or ALTER statement specified a PRIQTY,
Explanation SECQTY, or ERASE clause, USING STOGROUP was
The ALTER TABLE statement is invalid for one of the not specified, and the table space or index has
following reasons: user-managed data sets. The primary and secondary
space allocation of a user-managed data set cannot
• The table does not have a unique index with a key be altered by means of an ALTER statement.
that is identical to the nominated primary or unique
• An ALTER statement attempted to define a clone
key.
table for a base table that is in a table space that
• A unique index exists, but the index is already has user-managed data sets. A clone table cannot be
being used to enforce referential constraints. In this defined for a base table that is in a table space that
case, Db2 does not choose the index to enforce the has user-managed data sets.
primary or unique key.
• A CREATE TABLE or ALTER TABLE statement
specified a KEY LABEL clause. One or more
System action underlying data sets for the table space that
contains the table or an index on the table are
user-managed data sets. The key label specification
for a user-managed data set cannot be modified.

This also includes data sets for associated objects • A CREATE FUNCTION or ALTER FUNCTION
that contain the table's data, such as auxiliary table statement can contain the CAST FROM clause for
spaces, XML table spaces, index spaces, and clone only external scalar functions.
table spaces. • A CREATE FUNCTION or ALTER FUNCTION
statement specified SCRATCHPAD. SCRATCHPAD
System action must not be specified when LANGUAGE JAVA or
PARAMETER STYLE JAVA is also specified for a
The statement cannot be processed. function.
• A CREATE FUNCTION or ALTER FUNCTION
Programmer response statement specified FINAL CALL. FINAL CALL
Verify that the correct table, index, or partition is must not be specified when LANGUAGE JAVA or
specified. PARAMETER STYLE JAVA is also specified for a
function.
SQLSTATE • A CREATE FUNCTION or ALTER FUNCTION
statement specified LANGUAGE JAVA,
55016 LANGUAGE COMPJAVA, or PARAMETER STYLE
JAVA, with DBINFO. DBINFO must not be
-628 THE CLAUSES ARE MUTUALLY
specified in these cases.
EXCLUSIVE
statement specified LANGUAGE JAVA or
Explanation
PARAMETER STYLE JAVA, with RUN OPTIONS.
Mutually exclusive clauses were specified in the SQL RUN OPTIONS must not be specified in these
statement. In the cases where you alter an object, cases.
a clause was specified that conflicts with an existing • A CREATE FUNCTION or ALTER FUNCTION
property of the object. statement specified PARAMETER STYLE JAVA,
SELECT statements but LANGUAGE JAVA was not specified.
• A select-statement value contains both the • A CREATE FUNCTION or ALTER FUNCTION

update-clause and the FOR FETCH ONLY clause. statement specified LANGUAGE JAVA, but did
not specify PARAMETER STYLE JAVA.
CREATE DATABASE statements
• A CREATE DATABASE statement contains both statement specified RETURNS GENERIC TABLE,
the AS WORKFILE clause and the AS TEMP but did not specify LANGUAGE C.
clause. • LANGUAGE JAVA is not allowed for table
ALTER FUNCTION or CREATE FUNCTION statements functions.
• An ALTER FUNCTION statement for a function ALTER INDEX or CREATE INDEX statements
that is defined as secured specified the ADD • UNIQUE or UNIQUE WHERE NOT NULL was
VERSION clause or the REPLACE clause, but specified with PARTITIONED on CREATE INDEX.
not the SECURED clause. When a function is You cannot specify UNIQUE or UNIQUE WHERE
defined as secured and a new version is added NOT NULL with PARTITIONED on CREATE INDEX
or a version is replaced, the ALTER FUNCTION unless the index includes all the partitioning
statement must specify the SECURED clause. columns.
• A CREATE FUNCTION statement contains both a • A CREATE INDEX statement contains both a
CAST FROM clause and a SOURCE clause. GENERATE KEY USING and column specified as
• A CREATE FUNCTION statement contains both a ASC, DESC, or RANDOM.
SOURCE clause and a RETURNS TABLE clause. • A CREATE INDEX statement contains
• A CREATE FUNCTION statement contains both XMLPATTERN and PARTITIONED.
a SOURCE clause and a clause used to • A CREATE INDEX or ALTER INDEX statement
define an external function (such as EXTERNAL, attempted to specify either CLUSTER,
LANGUAGE, or NO SQL). PARTITION BY or both for an XML index or an
• A CREATE FUNCTION statement was specified extended index.
with a PARAMETER VARCHAR clause. You can
specify CREATE FUNCTION with PARAMETER
VARCHAR only if LANGUAGE C is also specified.

ALTER PROCEDURE or CREATE PROCEDURE • A CREATE or ALTER ADD statement contains
statements a DYNAMIC RESULT SETS clause and an
AUTONOMOUS clause.
• A CREATE PROCEDURE statement specified
either FENCED or EXTERNAL indicating that • EXTERNAL NAME was specified on ALTER
an external SQL procedure is to be defined, PROCEDURE for an SQL procedure. You can
and the statement also included one or more attempt the same action by issuing a DROP for
options which are allowed only for native SQL the procedure and attempting to rebuild it with
procedures. For example, PACKAGE OWNER CREATE PROCEDURE.
can be specified on the CREATE PROCEDURE ALTER TABLE or CREATE TABLE statements
statement for a native SQL procedure, but it is
not allowed for an external SQL procedure. Only for ALTER TABLE
• A CREATE PROCEDURE statement was specified • An ALTER TABLE statement contains both
with a PARAMETER VARCHAR clause. You can a DROP CONSTRAINT clause and either a
specify CREATE PROCEDURE with PARAMETER DROP FOREIGN KEY, DROP CHECK, DROP
VARCHAR only if LANGUAGE C is also specified. PRIMARY KEY, or DROP UNIQUE clause.
• A CREATE PROCEDURE or ALTER PROCEDURE • An ALTER TABLE statement contains both
statement specified LANGUAGE JAVA or an ALTER COLUMN clause and a VALIDPROC
PARAMETER STYLE JAVA, with DBINFO. DBINFO clause.
must not be specified in these cases. • An ALTER TABLE statement contains both an
• A CREATE PROCEDURE or ALTER PROCEDURE ALTER COLUMN clause and a clause other
statement specified PARAMETER STYLE JAVA, than the check constraint clause.
but LANGUAGE JAVA was not specified. • An ALTER TABLE statement contains either
• A CREATE or ALTER PROCEDURE statement an ADD MATERIALIZED QUERY or DROP
specified LANGUAGE JAVA, but did not specify MATERIALIZED QUERY clause, and some
PARAMETER STYLE JAVA. other clauses.
• A CREATE PROCEDURE or ALTER PROCEDURE • An ALTER TABLE statement contains the
statement specified LANGUAGE JAVA with NO DROP COLUMN clause with another clause.
WLM ENVIRONMENT. NO WLM ENVIRONMENT The DROP COLUMN clause cannot be used
must not be specified when LANGUAGE JAVA is with any other clause.
also specified for a procedure. • An ALTER TABLE statement contains an
• A CREATE PROCEDURE or ALTER PROCEDURE ENABLE ARCHIVE clause and another clause.
statement attempts to use the NO WLM The ENABLE ARCHIVE clause cannot be used
ENVIRONMENT and PROGRAM TYPE SUB with any other clause.
options. When NO WLM ENVIRONMENT is used, • An ALTER TABLE statement contains a
then SECURITY must also be used. DISABLE ARCHIVE clause and another
• A CREATE PROCEDURE or ALTER PROCEDURE clause. The DISABLE ARCHIVE clause cannot
statement attempts to use both NO WLM be used with any other clause.
ENVIRONMENT and either USER or DEFINER • An ALTER TABLE statement contains both an
for SECURITY. When NO WLM ENVIRONMENT is ORGANIZE BY HASH clause and the APPEND
used, then SECURITY Db2 must also be used. option.
• A CREATE PROCEDURE or ALTER PROCEDURE • An ALTER TABLE statement contains an
statement contains both a LANGUAGE REXX ORGANIZE BY HASH clause, but the table
clause and either a PARAMETER STYLE DB2SQL is not in a universal table space. The
or PARAMETER STYLE JAVA clause. ORGANIZE BY HASH clause is valid only for
• A CREATE PROCEDURE or ALTER PROCEDURE tables in a universal table space.
statement specified LANGUAGE JAVA or • An ALTER TABLE statement contains both
PARAMETER STYLE JAVA, with RUN OPTIONS. an ADD COLUMN clause and the LONG
RUN OPTIONS must not be specified in these VARCHAR (or LONG VARGRAPHIC) syntax for
cases. the data type for a system-period temporal
• A CREATE PROCEDURE or ALTER PROCEDURE table or archive-enabled table.
statement contains a DEBUG MODE clause when • A RENAME clause was issued with another
neither LANGUAGE JAVA or LANGUAGE SQL are clause in a single ALTER statement. RENAME
in effect for the procedure.

cannot be issued with any other clause in a DSSIZE clause. The DSSIZE clause cannot
single ALTER statement. be specified for a non-relative partition-by-
• An ALTER TABLE statement distinctly range table space.
contains two or more of the following • An ALTER TABLESPACE statement contains
clauses: ALTER COLUMN, ADD PARTITION, the DROP PENDING CHANGES clause
ALTER PARTITION, and ROTATE PARTITION. with another clause. The DROP PENDING
The clauses are mutually exclusive with each CHANGES clause cannot be used with any
other, unless the ADD PARTITION and ALTER other clause.
PARTITION clauses are specified together to • NOT LOGGED for ALTER TABLESPACE is
add a new partition between existing logical mutually exclusive with DATA CAPTURE
partitions. CHANGES, which is an attribute of one or
Only for CREATE TABLE more of the tables in the table space.
• A CREATE TABLE statement contains both a • FL 508 An ALTER TABLESPACE statement

DSSIZE clause and EVERY integer G clause. contains the MOVE TABLE clause with
another clause. The MOVE TABLE clause
• A CREATE TABLE statement contains a CCSID cannot be used with any other clause.
1208 clause for a VARCHAR column, or
a CCSID 1200 clause for a VARGRAPHIC • An ALTER TABLESPACE statement contains
column in an EBCDIC table. the PAGENUM clause with another clause.
The PAGENUM clause cannot be used with
• A CREATE TABLE statement contains both any other clause.
a CCSID 1208 or CCSID 1200 clause and a
FIELDPROC clause. • An ALTER TABLESPACE statement contains
the SEGSIZE clause with another clause. The
• An explicit table space cannot be specified SEGSIZE clause cannot be used with any
on a CREATE TABLE statement that specifies other clause.
table space attributes for an implicit table
space. • A CREATE TABLESPACE statement specified
MAXPARTITIONS and NUMPARTS.
• None
• A CREATE TABLESPACE statement contains
For both ALTER TABLE and CREATE TABLE both MAXPARTITIONS and PARTITION
• An ALTER TABLE or CREATE TABLE clauses.
statement contains an ORGANIZE BY HASH • A CREATE TABLESPACE statement contains
clause, but the table is defined in a table both the SEGSIZE and MEMBER CLUSTER
space that is defined with the MEMBER clauses without either a MAXPARTITIONS or
CLUSTER option. NUMPARTS clause.
• An ALTER TABLE or CREATE TABLE • A CREATE TABLESPACE or ALTER
statement contains the VERSIONING clause TABLESPACE statement contains both
and the LIKE clause. LOCKPART YES and LOCKSIZE TABLESPACE.
• DATA CAPTURE CHANGES for ALTER TABLE • A CREATE TABLESPACE or ALTER
or CREATE TABLE can be specified only for TABLESPACE statement specified
tables in table spaces with the LOGGED MAXPARTITIONS and LOCKSIZE TABLE.
logging attribute. • A CREATE TABLESPACE or ALTER
• PARTITION BY SIZE was specified along with TABLESPACE statement contains both an
an IN clause that identified a table space that ORGANIZE BY HASH clause and the APPEND
is not defined as a partition-by-growth table option.
space. • A USING VCAT clause was specified on a
• A column-definition value contains both NOT CREATE TABLESPACE or ALTER TABLESPACE
NULL and DEFAULT NULL clauses. statement for a partition-by-growth table
• A column-definition value contains both space.
FIELDPROC and DEFAULT clauses. ALTER TRIGGER or CREATE TRIGGER
ALTER TABLESPACE or CREATE TABLESPACE statements
statements • An ALTER or CREATE TRIGGER statement
• An ALTER TABLESPACE statement with the specifies more than one correlation name
ALTER PARTITION clause also contains the for OLD, NEW, OLD_TABLE, or NEW_TABLE.
Each of these correlation specifications can

appear no more than once in the ALTER or System action
CREATE TRIGGER statement.
• The WHEN clause must not be specified for
an INSTEAD OF trigger.
Programmer response
• Two attributes in the ALTER or CREATE
TRIGGER statement conflict. CREATE Review the permitted options for the statement that
TRIGGER (basic) (Db2 SQL) indicates you want to issue, change the options specified in the
which combinations are valid. For example, statement, and reissue the statement.
according to the table, FOR EACH
STATEMENT must not be used for a SQLSTATE
BEFORE or INSTEAD OF trigger or with the
REFERENCING NEW ROW clause. 42613
ALTER TRUSTED CONTEXT statements Related reference
• A TRUSTED CONTEXT definition specified Statements (Db2 SQL)
ATTRIBUTE JOBNAME with ATTRIBUTE
-629 SET NULL CANNOT BE SPECIFIED
ADDRESS or SERVAUTH or ENCRYPTION.
BECAUSE FOREIGN KEY name
DECLARE CURSOR statements CANNOT CONTAIN NULL VALUES
• A DECLARE CURSOR statement specifies
both the WITH RETURN TO CLIENT option Explanation
and one the following options: WITH
The code SET NULL option of the indicated FOREIGN
RETURN (TO CALLER) or WITHOUT RETURN.
KEY clause is invalid because no column of the
• If INSENSITIVE or SENSITIVE is specified, key allows null values. The name is the constraint-
then SCROLL must also be specified, name specified in the FOREIGN KEY clause or, if a
either on DECLARE CURSOR or with constraint-name was not specified, the first column-
the ATTRIBUTES clause of the PREPARE name specified in the clause.
statement.
• If SCROLL is specified, then either System action
INSENSITIVE or SENSITIVE STATIC must
also be specified, either on DECLARE The statement cannot be processed.
CURSOR or with the ATTRIBUTES clause of
the PREPARE statement. Programmer response
DECLARE GLOBAL TEMPORARY TABLE Change a column of the key to allow null values or
statements change the delete rule.
• The AS (subselect) clause of a DECLARE
GLOBAL TEMPORARY TABLE statement SQLSTATE
contains both an INCLUDING COLUMN
DEFAULTS clause and a USING TYPE 42834
DEFAULTS clause. -631 FOREIGN KEY name IS TOO LONG
PREPARE statements OR HAS TOO MANY COLUMNS
• If INSENSITIVE or SENSITIVE is specified,

then SCROLL must also be specified, Explanation
either on DECLARE CURSOR or with This code is used to report that the sum of the length
the ATTRIBUTES clause of the PREPARE attributes of the columns identified in the indicated
statement. FOREIGN KEY clause is greater than 255 bytes or
• If SCROLL is specified, then either the number of columns identified is greater than 64.
INSENSITIVE or SENSITIVE STATIC must The 'name' is the constraint-name specified in the
also be specified, either on DECLARE FOREIGN KEY clause or, if a constraint-name was
CURSOR or with the ATTRIBUTES clause of not specified, the first column-name specified in the
the PREPARE statement. clause.
• The attribute-string value specified in
the ATTRIBUTES clause of the PREPARE
statement cannot specify conflicting options.

System action • A self-referencing constraint must have a 'delete-
rule' of CASCADE or NO ACTION.
• The relationship would cause the table to be delete-
connected to the same table through multiple paths
Programmer response and such relationships must have the same 'delete-
The table definition must be modified to conform to rule'.
the system-imposed limit of the sum of the length • When PERIOD BUSINESS_TIME is specified for
attributes of the columns identified in the PRIMARY a temporal referential constraint, the 'delete-rule'
KEY clause. must be RESTRICT.

-632 THE TABLE CANNOT BE DEFINED
AS A DEPENDENT OF table- Programmer response
name BECAUSE OF DELETE RULE Change the 'delete rule' in the FOREIGN KEY clause.
RESTRICTIONS
SQLSTATE
Explanation
42915
This code is used to report that the object of an ALTER
TABLE statement cannot be defined as a dependent of -634 THE DELETE RULE MUST NOT BE
the indicated table because either: CASCADE
• The relationship would form a cycle that would
cause the table to be delete-connected to itself. Explanation
• The relationship would cause the table to be delete- The code is used to report that the CASCADE delete
connected to the indicated table through multiple rule specified in the FOREIGN KEY clause of an ALTER
paths and the delete rule of the existing relationship TABLE statement is invalid because:
is SET NULL.
• The relationship would form a cycle that would
The error is due to the delete rules of existing cause a table to be delete-connected to itself.
relationships, not the delete rule specified in the • The relationship would cause another table to be
FOREIGN KEY clause of the ALTER TABLE statement. delete-connected to the same table through multiple
paths with different delete rules or with a delete rule
System action equal to SET NULL.
System action
Eliminate the particular FOREIGN KEY clause from the
ALTER or CREATE TABLE statement. Programmer response
Change the delete rule.
SQLSTATE
42915 SQLSTATE
-633 THE DELETE RULE MUST BE delete- 42915
rule -635 THE DELETE RULES CANNOT BE
DIFFERENT OR CANNOT BE SET
Explanation NULL
The code is used to report that the 'delete-rule'
specified in a FOREIGN KEY clause of the ALTER Explanation
TABLE statement is invalid. The indicated 'delete-rule' The code is used to report that the delete rules
is required because: specified in two FOREIGN KEY clauses of the CREATE

TABLE statement are invalid because the table would -637 DUPLICATE keyword-name
be delete-connected to the same table through KEYWORD OR CLAUSE
multiple paths involving relationships with different
delete rules or with delete rules of SET NULL.
Explanation
System action The SQL statement contains a duplicate specification
for the keyword-name key word. For example:
• DEFAULT, UNIQUE, and PRIMARY can only be
specified once in a column definition.
Programmer response
• UNIQUE and PRIMARY cannot both be specified for
Change the delete rule. the same column definition.
• PRIMARY can only be specified once in a CREATE
SQLSTATE TABLE statement.
42915 • The attribute-string specified in the ATTRIBUTES
clause of the PREPARE statement cannot specify an
-636 RANGES SPECIFIED FOR option more than once.
PARTITION part-num ARE NOT
• ACTIVATE or DEACTIVATE ROW ACCESS CONTROL
VALID
can only be specified once.
• ACTIVATE or DEACTIVATE COLUMN ACCESS
Explanation CONTROL can only be specified once.
The ranges specified for physical partition part-num • IN ACCELERATOR can only be specified once.
are not valid for one of the following reasons:
• ATTRIBUTE ENCRYPTION can only be specified once
• The partitioning key values specified in the limit key in a TRUSTED CONTEXT definition.
value specifications were not in either ascending or • There are more than one xquery-context-item-
descending order. expression in the PASSING clause of an XMLQUERY
• A partitioning key value that was specified in or XMLEXISTS.
the limit key value specifications already exists. • WHEN MATCHED and WHEN NOT MATCHED clauses
Duplicate limit keys must not be specified. cannot be specified more than once in a MERGE
• All of the columns in the partitioning key are statement.
ascending, and a constant or MINVALUE was • SKIP LOCKED DATA clause cannot be specified more
specified following MAXVALUE in the limit key value than once for:
specification for the partition. Once MAXVALUE
is specified, all subsequent columns must be – all clauses in select-stmt
MAXVALUE. – SELECT INTO statements
• All of the columns in the partitioning key are – search UPDATE statements
descending, and a constant or MAXVALUE was
– search DELETE statements
specified following MINVALUE in the limit key value
specification for the partition. Once MINVALUE • If multiple ADD COLUMN clauses are specified in the
is specified, all subsequent columns must be same statement, at most one ADD COLUMN clause
MINVALUE. can contain a references-clause.

User response Programmer response

Correct the range partitioning specifications in the Correct the statement by removing duplicate clauses.
statement for the identified partition.
SQLSTATE
SQLSTATE 42614
56016

-638 TABLE table-name CANNOT BE -640 LOCKSIZE ROW CANNOT BE
CREATED BECAUSE COLUMN SPECIFIED BECAUSE TABLE IN
DEFINITION IS MISSING THIS TABLESPACE HAS TYPE 1
INDEX
Explanation
Explanation
The CREATE TABLE statement does not contain any
column definition. If LOCKSIZE ROW is specified for a table space, all
indexes on tables in the table space must be type 2
System action indexes. The following SQL statement identifies all the
type 1 indexes:
The SQL statement cannot be executed.
SELECT I.CREATOR, I.NAME
FROM SYSIBM.SYSINDEXES I,
Programmer response SYSIBM.SYSTABLES T
WHERE INDEXTYPE = ' '
AND T.TSNAME = 'table_space_name'
Add column definition to the statement. AND T.DBNAMe = 'database_name'
AND T.CREATOR = I.TBCREATOR
AND T.NAME = I.TBNAME;
SQLSTATE
42601 where 'table_space_name' is the name of the table
space that is to be altered; 'database_name' is the
-639 A NULLABLE COLUMN OF A name of the database that contains the table space.
FOREIGN KEY WITH A DELETE
RULE OF SET NULL CANNOT BE
System action
A COLUMN OF THE KEY OF A
PARTITIONED INDEX The statement cannot be processed.

A partition key of the clustering index cannot be Since the LOCKSIZE ROW on the table space and the
updated. Therefore, a foreign key column with a delete type 1 indexes conflict, either use the ALTER INDEX
rule of SET NULL cannot be a column of a partition statement to convert all type 1 indexes to type 2
key if that column is nullable. If this error occurs for indexes or use another LOCKSIZE option.
an ALTER TABLE operation, the foreign key cannot
be created. If this error occurs for a CREATE INDEX SQLSTATE
operation, the index cannot be created.
56089
System action -643 A CHECK CONSTRAINT OR THE
VALUE OF AN EXPRESSION FOR A
COLUMN OF AN INDEX EXCEEDS
THE MAXIMUM ALLOWABLE
Programmer response LENGTH KEY EXPRESSION
Review the delete rule of the referential constraint
and the partition keys for the index. Do one of the Explanation
following:
The definition of a check constraint or expression of an
• If the operation in error was CREATE INDEX, either index column exceeds the maximum allowable length:
change the index partition key definition or drop and
• A check constraint exceeded 3800 UTF-8 bytes.
redefine the referential constraint with a different
Redundant blank spaces are excluded from this
delete rule.
limit.
• If the operation in error was ALTER TABLE, change
• A value for an expression for an index exceeded
the referential delete rule so that all nullable index
4000 UTF-8 bytes.
keys are not part of the foreign keys.

The CREATE TABLE or ALTER TABLE statement failed.
56027
The statement cannot be executed.

Programmer response -646 TABLE table-name CANNOT BE
CREATED IN OR MOVED TO
Change the constraint or expression so that it does not SPECIFIED TABLE SPACE table-
exceed the maximum allowable limit. If it is a check space-name BECAUSE IT ALREADY
constraint, rewrite the check constraint definition so CONTAINS A TABLE
that it is less than 3800 UTF-8 bytes. You might need
to divide a the check constraint into two or more
smaller check constraints. Explanation
FL 508 The table space that is specified in a CREATE
SQLSTATE TABLE or ALTER TABLESPACE statement is one of the
following types of table spaces and already contains
54024 an existing table or has a pending definition change to
-644 INVALID VALUE SPECIFIED move a table to table-space-name:
FOR KEYWORD OR CLAUSE • A partitioned table space
keyword-or-clause IN STATEMENT
statement-type • An implicitly defined table space
• A LOB table space
Explanation • An XML table space
The value that was specified for the keyword-or-clause • A table space that contains a system-period
parameter in the statement-type SQL statement is not temporal table or history table
valid. • A table space that contains an archive-enabled table
or archive table
System action • FL 508 A table space that is the target table space
for a pending ALTER TABLESPACE MOVE TABLE
The statement cannot be processed. statement
Only one table can exist in these types of table spaces.
Programmer response
In most cases, change the value of the specified System action
keyword-or-clause to a valid value.
The statement cannot be processed. FL 508 The table
This error might be issued for pending definition was not created or moved.
changes by utilities or data definition statements.
In that case, check the STATEMENT_TEXT column
of related rows in the SYSIBM.SYSPENDINGDDL Programmer response
catalog table for a pending definition change that Verify that the correct table space was specified in the
contains an invalid value. If the error is for an invalid failing statement.
MAXPARTITIONS change, compare the actual number
of partitions for the table space to the specified
MAXPARTITIONS value. It is possible that the number SQLSTATE
of partitions has grown to exceed the MAXPARITIONS 55017
value of a pending definition change. In that case,
alter the table space to drop all pending definition Related concepts
changes. Then, reissue the pending changes with valid Table space types and characteristics in Db2 for
specifications. z/OS (Db2 Administration Guide)
Temporal tables and data versioning (Db2
SQLSTATE Administration Guide)
Archive-enabled tables and archive tables
42615 (Introduction to Db2 for z/OS)
Related tasks Related reference
Materializing pending definition changes (Db2 CREATE TABLE (Db2 SQL)
Administration Guide)
Related reference -647 BUFFERPOOL bp-name FOR
Statements (Db2 SQL) IMPLICIT OR EXPLICIT
TABLESPACE OR INDEXSPACE
SYSPENDINGDDL catalog table (Db2 SQL)
name HAS NOT BEEN ACTIVATED

Explanation 8
An ALTER statement with a SEGSIZE clause
The buffer pool specified in a CREATE or ALTER is allowed for universal table spaces and
statement for a table space or index (index space) partitioned table spaces that use table-
is not activated. Alternatively, on a CREATE TABLE controlled partitioning.
statement without an IN clause, the buffer pool, which
is chosen by Db2 implicitly according to the actual 9
record size, is not activated. An ALTER statement with a BUFFERPOOL
clause where a different page size is specified
Table spaces and indexes (index spaces) can only is allowed only for LOB and universal table
be assigned or reassigned to buffer pools that are spaces (excluding XML table spaces).
currently activated.
10
An ALTER statement with a MAXPARTITIONS
System action clause is allowed only for the following table
spaces:
table space or index space was not created or altered. • Single-table simple table spaces
• Single-table segmented table spaces
Programmer response • Universal table spaces that use partition-by-
Verify that the proper buffer pool was specified in growth organization
the CREATE or ALTER statement and the buffer pool 11
is chosen by Db2. Use the -DISPLAY BUFFERPOOL An ALTER statement with an ENDING AT clause
command to display the attributes of the buffer is not allowed for an index on a partitioned
pool and determine if the buffer pool is activated. base table with LOB columns or the table itself.
If the buffer pool is not activated, use the -ALTER
12
BUFFERPOOL command to change the VPSIZE from
ALTER INDEX is not allowed when there is a
0 to the appropriate size.
pending SQL statement.
13
SQLSTATE
ALTER TABLE is not allowed when there is a
57003 pending SQL statement.
-650 THE ALTER STATEMENT CANNOT 14
BE EXECUTED, REASON reason- An ALTER INDEX statement with an ENDING
code AT clause is not allowed when using table-
controlled partitioning.
Explanation 15
Using ALTER to change the attributes of a
The ALTER statement cannot be executed for the partition values is not allowed for an index on
indicated reason. a partitioned base table with LOB columns, or
the table itself.
reason-code
A numeric value that indicates the reason that the 16
statement cannot be executed. ALTER TABLE DATA CAPTURE CHANGES is not
allowed for table spaces in advisory REORG-
5
pending (AREO) state.
An ALTER statement with a PIECESIZE clause
is not allowed for a partitioning index. 17
ALTER TABLE DROP CLONE cannot be used to
6
drop a clone when the table itself is a clone.
An ALTER statement with a PIECESIZE 4G
clause is not allowed for non-partitioned 18
indexes on a non-large table. ALTER INDEX is not allowed when the table
has defined a clone.
7
An ALTER statement with a DSSIZE clause 19
is allowed only for LOB and universal table ALTER TABLESPACE is not allowed when the
spaces. table space contains a table that has a clone
defined.

20 • Specifying the following clauses:
ALTER TABLE DROP CLONE cannot be used to
– ADD RESTRICT ON DROP
drop a clone when the table does not have a
defined clone. – ALTER MATERIALIZED QUERY
21 – ALTER PARTITION
ALTER TABLE SET DEFAULT is not allowed – AUDIT
when all of the following conditions are true:
– DATA CAPTURE
• The table exists in a table space that – DROP MATERIALIZED QUERY
currently has the DEFINE YES attribute.
– DROP RESTRICT ON DROP
• The ALTER TABLE statement references a
column that was not part of the original table – ROTATE PARTITION
definition. – KEY LABEL
• The table has not been reorganized since the – NO KEY LABEL
referenced column was added.
ADD RESTRICT ON DROP and DROP RESTRICT
22 ON DROP clauses cannot be used in the same
ALTER TABLE SET DEFAULT and DROP statement.
DEFAULT are not allowed for tables referenced
28
by a materialized query table or view.
ALTER TABLE is not allowed for an accelerator-
23 only table unless the only alteration that is
ALTER TABLE DROP DEFAULT is not allowed specified is either ADD RESTRICT ON DROP or
when the table space is in the advisory DROP RESTRICT ON DROP.
REORG-pending (AREO*) state.
29
24 ALTER TABLESPACE is not allowed when the
An ALTER TABLE statement with pending table space contains an accelerator-only table.
options is allowed only for universal table
32
spaces.
An ALTER statement with an ADD PARTITION
25 clause attempted to insert a partition. This is
ALTER TABLE DROP DEFAULT is not allowed not allowed for one of the following reasons:
when all of the following conditions are true:
• The table is not in a partition-by-range table
• The table space is in either the advisory space.
REORG-pending (AREO*) or REORG-pending
• The partition number is not valid.
(REORP) state.
• The limit key value is not valid for an affected
• The ALTER TABLE statement references a
partition.
column that was not part of the original table
definition. • The table contains a LOB column, or a
distinct type column that is based on a LOB
• The table has not been reorganized since the
data type.
referenced column was added.
34
In this case, a mass UPDATE can be used to
ALTER TABLESPACE COMPRESS is not allowed
clear the AREO* state.
for a LOB table space when the associated
26 base table space is not a universal table space.
An ALTER VIEW statement with a 35
REGENERATE clause is not allowed if the view ALTER TABLESPACE PAGENUM is not
is referenced by a materialized query table. successful because the table space is not a
27 partition by range table space.
For an ALTER TABLE statement that names a 36
materialized query table, the alterations are ALTER TABLESPACE PAGENUM is not
limited to the following situations: successful because the table space is DEFINE
• Changing the materialized query table NO, but at least one index for the table space is
attributes DEFINE YES.
• Turning the materialized query table to a
base table

37 and re-created before the pending change is
ALTER TABLESPACE PAGENUM is not materialized.
successful because an invalid keyword was 48
specified. PAGENUM must be followed by the FL 508 An ALTER TABLESPACE with a
keyword RELATIVE. MAXPARTITIONS clause to convert the table
38 space to a partition-by-growth universal table
ALTER TABLESPACE PAGENUM is not space must specify MAXPARTITIONS 1 if a
successful because the table space uses a pending definition change to move a table from
hash organization, or ALTER TABLE cannot be the table space exists.
used to add hash organization when the table 49
resides in a table space that uses relative page FL 509 ALTER TABLESPACE COMPRESS YES
numbers. HUFFMAN is not allowed for a non-universal
39 table space.
ALTER TABLESPACE PAGENUM is not 50
successful because the table contains FL 509 ALTER TABLESPACE COMPRESS YES
truncated limit key values. FIXEDLENGTH or COMPRESS YES HUFFMAN is
40 not allowed for a LOB table space.
FL 508 An ALTER TABLESPACE statement with 51
a MOVE TABLE clause must specify a table that FL 509 ALTER TABLESPACE COMPRESS YES
exists in the table space that is being altered. HUFFMAN is not allowed for a table space that
41 uses a hash organization.
FL 508 An ALTER TABLESPACE statement with ALTER TABLE with an ALTER PARTITIONING
a MOVE TABLE clause must specify a simple or clause is not allowed if the maximum number of
segmented (non-UTS) table space that is to be partitions for the new partitioning scheme is less
altered. than the existing maximum number of partitions
42 where the table is defined with DATA CAPTURE
FL 508 An ALTER TABLESPACE statement with CHANGES, and the table's table space data sets
a MOVE TABLE clause must specify a table are defined.
space that exists in the same database as the
table space that is being altered.
System action
43
FL 508 An ALTER TABLESPACE statement The statement cannot be processed.
with a MOVE TABLE clause must specify a
target table space that is a partition-by-growth Programmer response
universal table space.
Correct the error based on the information provided for
44 the reason-code value, and reissue the statement.
FL 508 An ALTER TABLESPACE statement with
a MOVE TABLE clause must specify a target FL 508 For errors due to incorrect definition of the
table space that does not already have data target table space for a pending definition change to
sets created. move a table, take one of the following actions:
45 • Alter the target table space to specify the correct
FL 508 An ALTER TABLESPACE statement attributes.
with a MOVE TABLE clause must specify • Complete the following steps:
a target table space that is defined with
MAXPARTITIONS 1. 1. Drop all pending definition changes, including
the MOVE TABLE operation, associated with the
46
source table space.
FL 508 An ALTER TABLESPACE statement with
a MOVE TABLE clause must specify a target 2. Drop the target table space.
table space that is defined with the same 3. Re-create the target table space with the correct
LOGGED attribute as the source table space. attributes.
47 4. Execute all the pending definition changes again.
FL 508 If a table space is the target of a
pending definition change to move a table,
the target table space cannot be dropped

SQLSTATE SQLSTATE
56090 23506
Related reference -653 TABLE table-name IN
ALTER INDEX (Db2 SQL) PARTITIONED TABLE SPACE
ALTER TABLE (Db2 SQL) tspace-name IS NOT AVAILABLE
BECAUSE ITS PARTITIONED
ALTER TABLESPACE (Db2 SQL)
INDEX HAS NOT BEEN CREATED
UPDATE (Db2 SQL)
-651 TABLE DESCRIPTION EXCEEDS Explanation

MAXIMUM SIZE OF OBJECT
An attempt has been made to insert or manipulate
DESCRIPTOR.
data in or create a view on a partitioned table (that is,
a table residing in a partitioned table space) before the
Explanation partitioned index for that table has been created.
The CREATE TABLE or ALTER TABLE statement causes A table residing in a partitioned table space cannot
the table descriptor (record OBD) to exceed the object be referenced in any SQL manipulative statement or a
descriptor size limit of 32KB. CREATE VIEW statement before the partitioned index
for that table has been created.
System action
System action
The statement is not executed. For an ALTER TABLE
statement, the definition of the table is unchanged. For The statement cannot be processed.
a CREATE TABLE statement, the table is not created.
Programmer response
Programmer response
Verify that the correct table was specified in
Change the statement by reducing either the number the statement. If so, ensure that the partitioned
or length (or a combination of both) of the user- index for the table has been created successfully
defined default string constants or check constraints before attempting to execute any SQL manipulative
and execute the statement again. statements that reference that table.
SQLSTATE SQLSTATE
54025 57004
-652 VIOLATION OF INSTALLATION -655 THE CREATE OR ALTER STOGROUP
DEFINED EDIT OR VALIDATION IS INVALID BECAUSE THE
PROCEDURE proc-name STORAGE GROUP WOULD HAVE
BOTH SPECIFIC AND NON-
Explanation SPECIFIC VOLUME IDS
The result of the SQL statement has been rejected by

Explanation
the installation defined edit or validation procedure
'proc-name' for the object table. One of the following error conditions occurred:
• Both a specific and a non-specific ('*') volume ID
System action are specified in the VOLUMES clause of a CREATE
STOGROUP statement.
The statement cannot be processed. The contents of
the object table were not modified. • Both a specific and a non-specific ('*') volume ID are
specified in an ADD VOLUMES clause of an ALTER
STOGROUP statement.
Programmer response
• A specific volume ID is specified in an ADD VOLUMES
Determine the requirements imposed by the edit or clause of an ALTER of a storage group that has non-
validation procedure for inserts and updates of the specific volume IDs or mixed volume IDs.
object table.

• A non-specific volume ID ('*') is specified in an ADD System action
VOLUMES clause of an ALTER of a storage group that
has specific volume IDs or mixed volume IDs. The statement cannot be processed.

The statement cannot be processed. Issue the appropriate DROP statement to drop the
intended objects.
Programmer response
SQLSTATE
Specify either specific or non-specific volume IDs
in the VOLUMES clause of CREATE STOGROUP 42917
statement and the ADD VOLUMES clause of the ALTER -660 INDEX index-name CANNOT BE
STOGROUP statement. To add specific volume IDs CREATED OR ALTERED ON
to a storage group with non-specific volume IDs, PARTITIONED TABLE SPACE
use the REMOVE VOLUMES clause to remove the tspace-name BECAUSE KEY
non-specific volume IDs. To add non-specific volume LIMITS ARE NOT SPECIFIED
IDs to a storage group with specific volume IDs, use
the REMOVE VOLUMES clause to remove the specific
volume IDs. Explanation
The CREATE INDEX or ALTER INDEX statement did
SQLSTATE not specify limit key values for the partitions of the
table space. To create a clustering index for a table in
56036 a partitioned table space, or to modify those values
-658 A object-type CANNOT BE using ALTER INDEX, you must include those values.
DROPPED USING THE statement
STATEMENT System action
Explanation cluster index was not created or altered.
A DROP statement was issued, but the object cannot
be explicitly dropped. The object must be dropped by Programmer response
dropping an associated object:
Verify that the correct table was specified in the
TRIGGER PACKAGE CREATE INDEX or ALTER INDEX statement. If so, the
A trigger package cannot be dropped with the definition for the partitioned table space must be
DROP PACKAGE statement. A trigger package can examined so that a proper definition for the cluster
only be dropped implicitly when the associated index for the table may be constructed.
trigger is dropped using the DROP TRIGGER
statement.
SQLSTATE
CAST FUNCTION
A cast function cannot be explicitly dropped 53035
with the DROP FUNCTION statement. A cast Related concepts
function can only be dropped implicitly when the
Db2 indexes (Introduction to Db2 for z/OS)
associated distinct type is dropped using the DROP
DISTINCT TYPE statement. Related reference
ALTER INDEX (Db2 SQL)
ROW PERMISSION
A default row permission cannot be explicitly CREATE INDEX (Db2 SQL)
dropped with the DROP PERMISSION statement.
A default row permission can only be dropped -661 object-type object-name CANNOT
implicitly when the associated table is dropped BE CREATED ON PARTITIONED
using the DROP TABLE statement. Alternatively, TABLE SPACE tspace-name
the default row permission can be dropped BECAUSE THE NUMBER OF
by using the ALTER TABLE statement with the PARTITION SPECIFICATIONS IS
DEACTIVATE ROW ACCESS clause. NOT EQUAL TO THE NUMBER OF
PARTITIONS OF THE TABLE SPACE

Explanation • The table is not in a partitioned table space.
The object-name definition is incorrect for one of the • The table is in a partition-by-growth or a
following reasons: partition-by-range table space.
• If object-type is INDEX, the CREATE INDEX 02

statement for the cluster index on a partitioned The CREATE INDEX statement contains the
table (that is, a table residing in a partitioned PARTITIONED option, but the table on which
table space) does not contain the same number of the index is created has one of the following
partition specifications as there are partitions in the characteristics:
table space. The definition for the cluster index for • The table is not in a partitioned table space.
a partitioned table must contain exactly as many
• The table is in a partition-by-growth table space.
partition specifications as there are partitions in the
table space in which that table resides. Also, the
partition numbers must be valid and unique. System action
• If object-type is TABLE, the number of partitions The statement cannot be processed. The specified
that is specified in the partitioning clause of the index was not created.
CREATE TABLE statement differs from the number
of partitions in the table space in which the table is
Programmer response
being created.
Verify that the proper object table was specified in the
System action statement. Review the proper usage of the PARTITION
BY clause or the PARTITIONED option in CREATE
The statement cannot be processed. The specified INDEX statements
cluster index or table was not created.
SQLSTATE
Programmer response
53037
Examine the definition of the partitioned table space
Related reference
to determine how many partitions have been specified.
Correct the syntax of the CREATE INDEX or CREATE CREATE INDEX (Db2 SQL)
TABLE statement to provide the proper number of
partition specifications. -663 THE NUMBER OF KEY LIMIT
VALUES IS EITHER ZERO, OR
GREATER THAN THE NUMBER OF
SQLSTATE COLUMNS IN THE KEY OF INDEX
53036 index-name
Related reference
Explanation
CREATE TABLE (Db2 SQL) The number of limit key value specifications provided
in at least one of the PART specifications of the
-662 A PARTITIONED INDEX CANNOT CREATE INDEX or ALTER INDEX statement is either
BE CREATED ON A TABLE SPACE, zero or greater than the number of columns in the
OR A TABLE SPACE CANNOT index key.
BE INDEX-CONTROLLED. TABLE
SPACE tspace-name, REASON System action
reason-code
index was not created.
Explanation
The CREATE INDEX statement could not be processed. Programmer response
The value in reason-code identifies the problem.
Correct the statement so that each PART specification
01 contains exactly the same number of limit key value
The CREATE INDEX statement contains the specifications as there are columns in the index key.
PARTITION BY clause for index-controlled
partitioning, but the table on which the index is
created has one of the following characteristics:

53038 The SQL statement could not be executed because the
named function was executing at the time.
-665 THE PARTITION CLAUSE OF AN
ALTER STATEMENT IS OMITTED stmt-verb
OR INVALID The type of data definition language (DDL)
statement
Explanation object
The Db2 object type
The ALTER statement is invalid for one of the following
function
reasons:
The active function that prevented the action. A
• The table space or index is not partitioned and the utility, the resource limit facility, or Db2ZAI.
PARTITION clause is specified.
If the object is part of the communications database, it
• The table space is a partition-by-growth table space cannot be dropped while the DDF is active.
and the PARTITION clause is specified.
• The table space or index is partitioned, a partition System action
attribute (FREEPAGE or PCTFREE) is specified, and
the PARTITION clause is not specified. The statement cannot be processed.
• The integer specified in the PARTITION clause does
not identify a partition of the table space or index. Programmer response
• A USING, PRIQTY, SECQTY, or ERASE clause is used If the function is a utility, wait for the function to
to alter storage attributes, but the partition is not complete or stop. Then resubmit the statement for
specified. execution.
• A GBPCACHE clause is used to alter the group If the function is the resource limit facility, the
buffer pool caching attributes, but the partition is not statement cannot be executed until the resource limit
specified. facility is stopped or switched to a different resource
• The PARTITION BY clause is specified without a limit table. In a Db2 data sharing environment, the
PARTITION clause to specify the range for the resource limit facility must be stopped on all members
partition. You must specify a PARTITION clause with of the Db2 data sharing group or all members must
a range to alter the PARTITION BY specification. switch to a resource limit table that is not associated
with the object.
• Using ALTER to change the attributes of a partition
values is not allowed for an index on a partitioned If the function is the DDF, the facility must be stopped
base table with LOB columns, or the table itself. before the object can be dropped. In a Db2 data
sharing environment, the facility must be stopped on
System action all members of the Db2 data sharing group.

SQLSTATE
Related concepts
Determine whether the table space or index you want
to alter is partitioned. If it is partitioned, specify a Distributed data facility (Introduction to Db2 for
PARTITION clause that identifies the partition you z/OS)
want to alter. If it is not partitioned, do not specify the Related tasks
PARTITION clause. Setting limits for system resource usage
by using the resource limit facility (Db2
SQLSTATE Performance)
Stopping DDF (Db2 Administration Guide)
53039
Related reference
-666 stmt-verb object CANNOT BE Restricted activity on resource limit tables (Db2
EXECUTED BECAUSE function IS Performance)
IN PROGRESS Resource limit facility tables (Db2 Performance)
-DISPLAY UTILITY (Db2) (Db2 Commands)

-667 THE CLUSTERING INDEX FOR -669 THE OBJECT CANNOT BE
A PARTITIONED TABLE SPACE EXPLICITLY DROPPED. REASON
CANNOT BE EXPLICITLY DROPPED reason-code
The DROP INDEX statement attempted to drop the The DROP statement failed.
cluster index for a table residing in a partitioned table
reason-code
space. The cluster index for such a table cannot be
The reason for the message or SQL code, indicated
dropped explicitly with the DROP INDEX statement.
0001
System action
FL 506 One of the following statements
The statement cannot be processed. The specified attempted to drop a table that resides in an
index was not dropped. explicitly defined (non-UTS) partitioned table
space:
Programmer response • The DROP TABLE statement
The cluster index for a table in a partitioned table • A DROP statement which causes a
space can only be dropped implicitly when the dependent table to be dropped
associated partitioned table space is dropped. Prior to FL 506, SQLCODE -669 with reason
code 0001 is issued when one of the
SQLSTATE statements listed above attempts to drop a
table that resides in an explicitly defined
42917 partitioned table space or a partition-by-
-668 THE COLUMN CANNOT BE ADDED growth table space.
TO THE TABLE BECAUSE THE 0002
TABLE HAS AN EDIT PROCEDURE The DROP INDEX statement attempted to
DEFINED WITH ROW ATTRIBUTE drop an index that Db2 requires to retain the
SENSITIVITY following conditions:
• The primary key constraint on a table
Explanation
• A unique key constraint on a table
The ALTER TABLE statement attempted to add a
• A referential constraint on a table
column to a table that has an edit procedure that is
defined with row attribute sensitivity. No columns can • The uniqueness of a ROWID column
be added to this table. • An XML column defined on a table
A system required index cannot be dropped
System action using the DROP INDEX statement.
The statement cannot be processed. The specified 0003
table was not altered. The DROP INDEX statement attempted to drop
an implicitly created index for a table that is
Programmer response defined with HASH organization.
Verify that the correct table was specified in the ALTER 0004
statement. Do not attempt to alter the definition of a The DROP TABLE statement attempted to drop
table that has an installation-written edit procedure a table that was implicitly created for an XML
associated with it. column.
0005
The DROP TABLESPACE statement attempted
SQLSTATE
to drop a table space that was implicitly
56018 created for a table containing an XML column.
Related reference 0006
ALTER TABLE (Db2 SQL) The DROP statement attempted to drop an
auxiliary table, an auxiliary index, or an
auxiliary table space that is involved in cloning.

0007 0007
The DROP TABLESPACE statement or DROP The table space or database can be dropped
DATABASE statement attempted to drop a explicitly only when the accelerator-only table is
table space or database that contains an dropped.
accelerator-only table. 0008
0008 The index can be dropped only after the temporal
The DROP INDEX statement attempted to referential constraint is dropped.
drop an index that is used for the definition
of a foreign key for a temporal referential SQLSTATE
constraint.
42917
System action -670 THE RECORD LENGTH OF THE
TABLE EXCEEDS THE PAGE SIZE
The statement cannot be processed. The object is not
LIMIT
dropped.

Take the appropriate corrective action based on the The row length for a table cannot exceed the page size
reason-code value: of the table space in which that table resides (or is to
reside). The page size of the table space is determined
0001 by the buffer pool used by that table space. This error
FL 506 The table of a partitioned (non-UTS) table can result from one of the following conditions:
space can be dropped implicitly only when the
Cast specification
table space itself is dropped.
The target length exceeds the maximum limit. The
0002 limit is 32764 for a varying length character string
If you do not want to keep the primary key, result.
unique key, or referential constraint, use the
Table creation
DROP CONSTRAINT clause of the ALTER TABLE
The following conditions are possible for a CREATE
statement to remove the primary key or unique
TABLE statement:
constraint. If the index was created only for
enforcing the primary or unique key, the index will • As defined in a CREATE TABLE statement, the
be dropped. If not, the DROP INDEX statement row length for the table would exceed the page
could then be processed. An index for a ROWID size of the specified (or default) table space. To
column can only be dropped by dropping the table. correct this situation, either:
0003 – Reduce the row length of the table by reducing
The index can only be dropped implicitly when the length of one or more of the columns.
the associated table that contains the XML column
– Assign the table to a table space that uses a
is dropped. If the error is about a table that
larger buffer pool.
is organized by hash, then the associated hash
overflow index cannot be dropped. Dropping hash • The LOB column with INLINE LENGTH clause has
organization will automatically drop the hash contributed to exceeding the page size limit.
overflow index. Table alteration
0004 The following conditions are possible for an ALTER
The table can be dropped implicitly only when TABLE statement:
the associated table containing the XML column is
• Addition of the specified column would cause the
dropped.
row length of the table to exceed the page size of
0005 the table space. This table cannot be altered to
The table space can be dropped implicitly only add columns.
when the associated table containing the XML
• The statement was issued to alter the length of
column is dropped.
an existing variable-length column and the new
0006 length of the altered column would cause the
An auxiliary table, an auxiliary index, or an auxiliary row length of the table to exceed the page size of
table space that is involved in cloning can be the table space.
dropped implicitly only when the associated table
• The LOB column with an INLINE LENGTH clause
containing the XML column is dropped.
has contributed to exceeding the page size limit.

To correct this situation, reduce the length of the IT WOULD CHANGE THE PAGE
column. SIZE OF THE TABLE SPACE
Table space alteration
The following conditions are possible for an ALTER Explanation
TABLESPACE statement:
For example, the change to the buffer pool attribute for
• In the case of an ALTER TABLESPACE statement the table space specified in the ALTER TABLESPACE
that is used to alter the buffer pool to a smaller statement would change the page size of the table
page size, the row length for one of the tables space—either from 4KB to 32KB, 8KB to 16KB, or vice
in the table space exceeds the new smaller page versa.
size.
Use of the ALTER TABLESPACE statement to change
• FL 508 In the case of an ALTER TABLESPACE the page size of a table space is not permitted.
statement with a MOVE TABLE clause, the target
table space must be defined with a buffer pool
that has a page size that can accommodate the
System action
record length of the table that is being moved. The statement cannot be processed. The table space
definition was not altered.
Join result
The row length in the result of a join exceeds
the maximum limit. The limit is 65,529 bytes The Programmer response
sort record includes columns that are being sorted
For example, if the table space uses one of the 4KB
and columns that the user selects. The length of
buffer pools (for example, BP0, BP1, or BP2), it can be
the columns that the user selects is the sort data
reassigned to one of the other 4KB buffer pools (but
length.
not buffer pool BP32K). If, however, it is assigned to
Sort result buffer pool BP32K, the buffer pool assignment cannot
The following conditions are possible for a sort be subsequently altered.
result:
• The row length of a large sort record exceeds SQLSTATE
the maximum limit. The limit is 65,529 bytes
The sort record includes columns that are being 53040
sorted and columns that the user selects. The -672 OPERATION DROP NOT ALLOWED
length of the columns that the user selects is the ON TABLE table_name
sort data length.
• The sort key length for a sort exceeds the Explanation
maximum limit. The limit is 32,000 bytes. The
length of the columns that are being sorted is the The DROP operation failed for one of the following
sort key length. reasons:
• The table being dropped has the RESTRICT ON
System action DROP attribute.
The statement cannot be processed. • The table space or database being dropped contains
the specified table, which has the RESTRICT ON
DROP attribute.
Programmer response
Correct the error based on the information provided, System action
and reissue the statement.
The DROP statement cannot be executed.
SQLSTATE
Programmer response
54010
Before dropping the table, alter the table, specifying
Related reference DROP RESTRICT ON DROP.
For DROP TABLESPACE or DROP DATABASE, make
-671 THE BUFFERPOOL ATTRIBUTE OF sure that there are no other tables within the table
THE TABLE SPACE CANNOT BE space or database with the RESTRICT ON DROP
ALTERED AS SPECIFIED BECAUSE

attribute. The following SELECT statement can identify • If the index is compressed, then the index pages
the tables: on disk are always 4 KB. The CISIZE for the data
set must also be 4KB.
SELECT CREATOR, NAME
FROM SYSIBM.SYSTABLES
WHERE TYPE = 'T'
AND CLUSTERTYPE = 'Y'
System action
AND DBNAME = 'database_name'
AND TSNAME = 'tablespace_name'; The statement cannot be processed.
Programmer response
SQLSTATE
Depending on the reason code value, take the
55035 following action:
-676 THE PHYSICAL 0001
CHARACTERISTICS OF THE Change the buffer pool specification to the name of
INDEX ARE INCOMPATIBLE WITH a buffer pool with a 4KB page size.
RESPECT TO THE SPECIFIED
0002
STATEMENT. THE STATEMENT HAS
Modify the statement so that is does not result in a
FAILED. REASON reason-code
compressed index with a 4 KB page size.
0003
Explanation ALTER the STOGROUP to use a Db2 managed data
A reason code is issued during the processing of a set or change the CISIZE of the user-managed
CREATE INDEX or ALTER INDEX statement. When the data set to be compatible with the specified index
statement fails, the reason for the failure is indicated options. If the index is compressed, the CISIZE
by the following reason code value: must be 4KB. Otherwise, the CISIZE should match
the page size or be 4KB.
0001
You specified a buffer pool with a page size
other then 4KB in the CREATE or ALTER INDEX SQLSTATE
statement. 53041
0002
Related reference
An ALTER INDEX or CREATE INDEX statement
results in an invalid combination of a 4KB page ALTER INDEX (Db2 SQL)
size and COMPRESS YES. This reason-code will be CREATE INDEX (Db2 SQL)
issued for the following reasons:
-677 INSUFFICIENT VIRTUAL STORAGE
• If you tried to CREATE or ALTER an index, you did FOR BUFFERPOOL EXPANSION
not specify a buffer pool having a page size that
is supported for index compression. You can only
choose a buffer pool with an 8KB, 16KB, or 32KB Explanation
page size for a compressed index. An attempt to either open (create) or expand a buffer
• If you tried to ALTER an index using ALTER pool has failed because insufficient virtual storage was
INDEX with the COMPRESS YES clause, then the available.
existing index is not defined with a buffer pool
This error may occur under either of two
that has an 8KB, 16KB, or 32KB page size, and
circumstances:
therefore, the index cannot be compressed.
• An attempt to create a buffer pool while opening a
0003
table space or index(space), or
The ALTER INDEX statement has resulted in an
index that's on-disk page size in incompatible • An attempt to expand a buffer pool from its current
with the CISIZE of the index's underlying non-Db2 size to its maximum size.
managed data set. This reason-code will be issued
for the following reasons: System action
• If the index is not compressed, a 4 KB page size The statement cannot be processed.
must reside in a data set that has a 4 KB CISIZE.
A page size greater than 4KB must have a CISIZE
that is either 4KB or equal to the page size.

Programmer response -679 THE OBJECT name CANNOT BE
CREATED BECAUSE A DROP IS
If this error should occur during interactive PENDING ON THE OBJECT
execution of an SQL statement or execution of an
application program, installation administration should
be notified. Explanation
Installation Action: It may be necessary to reexamine The application program has executed a DROP for the
the buffer pool storage strategy. specified object, and then tried to re-create an object
with the same name (and of the same type) before the
One of the following messages has also been sent DROP was completed.
to the MVS console: DSNB601I, DSNB603I, or
DSNB605I. If the object is an index, this error is returned if the
index that is to be created uses the same index space
name as the index that was dropped without a commit.
SQLSTATE
57011 System action
Related tasks The statement cannot be processed. The specified
Controlling buffer storage (Db2 Installation and object was not created.
Migration)
Related information Programmer response
DSNB601I (Db2 Messages)
DSNB603I (Db2 Messages) The logic of the application program must be modified
to issue a COMMIT (or the IMS or CICS equivalent)
between the DROP and CREATE statements.
-678 THE CONSTANT constant
SPECIFIED FOR THE INDEX SQLSTATE
LIMIT KEY MUST CONFORM TO
57006
THE DATA TYPE data-type OF
THE CORRESPONDING COLUMN -680 TOO MANY COLUMNS SPECIFIED
column-name FOR A TABLE, VIEW OR TABLE
FUNCTION
Explanation
The index limit key value constant has been specified
Explanation
incorrectly in the CREATE INDEX or ALTER INDEX The maximum number of columns permitted per
statement. table, view, or table function is 750. The statement
attempted to perform one of the following actions:
Limit key value specifications must conform to the
data type of the corresponding index key column. In • CREATE or ALTER a table to contain more than 750
this case, constant must be of data type data-type to columns
conform to the data type of column column-name. • CREATE a view with more than 750 columns
• CREATE a table function with more than 750
System action columns in the RETURNS TABLE clause
The statement cannot be processed. The index was
not created. System action
Programmer response
Correct the statement so that each limit key value Programmer response
constant is of precisely the same data type as that of
the corresponding index key column. Change the CREATE statement to not include more
than 750 columns, or do not try to alter an existing
table to contain more than 750 columns.
SQLSTATE
53045 SQLSTATE
54011

-681 COLUMN column-name IN SQLSTATE
VIOLATION OF INSTALLATION
DEFINED FIELD PROCEDURE. 57010
RT: return-code, RS: reason-code, -683 THE SPECIFICATION FOR
MSG: message-token COLUMN, DISTINCT TYPE,
FUNCTION, OR PROCEDURE data-
Explanation item CONTAINS INCOMPATIBLE
CLAUSES
An installation field procedure returned an error
for 'column-name'. The 'reason-code' and 'message-
token' are defined by the field procedure. They may Explanation
give additional information to help determine the The data item specification of a CREATE or ALTER
cause of the problem. statement contains an error.
Return code data-item
Error The source of the problem, which varies by
4 statement.
Invalid value on encode or decode or invalid CREATE DISTINCT TYPE statements
column description on define The name of the type that is being defined.
8 CREATE FUNCTION or ALTER FUNCTION
Invalid parameter value statements
12 The area of the statement that caused the
Field procedure error on any function error, such as "PARAMETER 3", "RETURNS" or
"CAST FROM".
Use 'reason-code' and 'message-token' for additional
information. CREATE TABLE or ALTER TABLE statements
The name of the column that caused the error.
The error could be an invalid specification of
System action FOR BIT DATA, FOR SBCS DATA, FOR MIXED
The statement cannot be processed. DATA, or FIELDPROC for the column definition.
The following additional restrictions apply
Programmer response to CREATE TABLE statements, ALTER TABLE
statements, or both:
If it is not a field procedure error, determine the
requirements imposed by the field procedure. If it is • On an ALTER TABLE statement, generation-
a field procedure error, examine the field procedure. alteration cannot be specified for a column
that is not defined as an identity column.
SQLSTATE • The columns for a BUSINESS_TIME period
must be defined with a data type of DATE or
23507 TIMESTAMP(6) WITHOUT TIME ZONE.
-682 FIELD PROCEDURE procedure- • The data type for a column that is
name COULD NOT BE LOADED defined as ROW BEGIN, ROW END,
or TRANSACTION START ID must be
Explanation TIMESTAMP(12) WITHOUT TIME ZONE.
The field procedure 'procedure-name' cannot be General causes

loaded. FIELDPROC can only be specified for columns
that are a built-in character string or graphic
string data type that is not a LOB.
System action
FIELDPROC cannot be specified for a Unicode
The statement cannot be processed. column in an EBCDIC table.

The application should either commit or roll back to The statement cannot be processed.
previous COMMIT. Then, in general, the application
should terminate.

Correct the SQL statement by removing the The columns specified are not compatible. Different
incompatible specification. field procedures are specified, or only one field
procedure is specified.
SQLSTATE
System action
42842
Related reference
Programmer response
-684 THE LENGTH OF CONSTANT LIST Correct the SQL statement.
BEGINNING string IS TOO LONG
SQLSTATE
Explanation
53043
The length of the constant list beginning with
'string', excluding insignificant blanks and delimiting Related concepts
parentheses is greater than 255. String comparisons with field procedures (Db2
SQL)
System action
-687 FIELD TYPES INCOMPARABLE
Explanation
Programmer response
One column cannot be compared with another column
Correct the SQL statement. that has incompatible field types.

-685 INVALID FIELD TYPE, column-
name Programmer response
Explanation
The field description returned by the field procedure is SQLSTATE
invalid. The data type code denotes a long string or has 53044
an invalid value.
Related concepts
System action String comparisons with field procedures (Db2
SQL)
-688 INCORRECT DATA RETURNED
Programmer response FROM FIELD PROCEDURE, column-
name, msgno
Correct the field procedure so that it returns a valid
data type code.
Explanation
SQLSTATE Unexpected data returned from field procedure for
column 'column-name'. For more information see
58002 'msgno'.
-686 COLUMN DEFINED WITH A FIELD
PROCEDURE CAN NOT COMPARE System action
WITH ANOTHER COLUMN WITH The statement cannot be processed.
DIFFERENT FIELD PROCEDURE

Programmer response • 0002
Correct the field procedure so that it returns values Data definition control support is running under
that are consistent with their descriptions. the controlling by application name with exceptions
mode. The statement is rejected because the object
is not registered in object registration table and the
SQLSTATE current application is not registered in application
58002 registration table with DEFAULTAPPL on.
-689 TOO MANY COLUMNS DEFINED • 0003

FOR A DEPENDENT TABLE Data definition control support is running under
the controlling by application name with exceptions
Explanation mode. The statement is rejected because the object
is registered in object registration table but the
The maximum number of columns allowed for a current application does not match.
dependent table is 749. The code is used to report
• 0004
that the statement is invalid because of one of the
following: Data definition control support is running under the
controlling by object name with exceptions mode.
• A CREATE TABLE statement is creating a dependent
The statement is rejected because the object is
table with 750 columns.
registered in object registration table but the current
• An ALTER TABLE statement is altering a dependent application does not match.
table with 749 columns to add a column, or altering
• 0005
a table with 750 columns to become a dependent
table. Data definition control support is running under the
controlling by object name mode. The statement is
System action rejected because the object is registered in object
registration table but the current application does
The statement cannot be processed. not match.
• 0006
Programmer response Data definition control support is running under the
Correct the SQL statement to conform to the column controlling by object name mode. The statement
limit for a dependent table. is rejected because the object is not registered in
object registration table.
SQLSTATE
System action
54011
-690 THE STATEMENT IS REJECTED
BY DATA DEFINITION CONTROL
SUPPORT. REASON reason-code Programmer response
Check whether data definition control support is
Explanation running in the correct mode. Check one or both
registration tables to determine if the entries of the
The code is issued by the data definition control registration tables are correct. If they are not, update
support to report that the statement is rejected for the the registration tables.
reason indicated by 'reason-code' after consulting the
application registration table and object registration
table. SQLSTATE
The explanation of the given reason code: 23508
• 0001 -691 THE REQUIRED REGISTRATION

TABLE table-name DOES NOT
Data definition control support is running under EXIST
the controlling by application name mode.
The statement is rejected because the current
application is not registered in application
registration table with DEFAULTAPPL on.

Explanation • A column description is invalid because its name,
column number, data type, length, or null attribute is
The data definition control support assumes the incorrect.
existence of the application registration table and
object registration table. But either one or both tables or
is not defined. The index is improperly defined for the following
reasons:
System action • A required key column is missing.
The statement cannot be processed. • A key column description is invalid because of its key
sequence or because its ordering is incorrect.
Programmer response • A defined key column should not be part of the
unique key.
Determine whether the required registration tables do
exist. If not, create the required tables.
System action
57018
Programmer response
-692 THE REQUIRED UNIQUE
INDEX index-name FOR DDL Correct or alter the definition of the required
REGISTRATION TABLE table-name registration table or index.
DOES NOT EXIST
SQLSTATE
Explanation 55003
A unique index must be defined for each registration
-694 THE SCHEMA STATEMENT
table. The code is issued when either the required
CANNOT BE EXECUTED BECAUSE
index does not exist or the index defined is not a
A DROP IS PENDING ON THE DDL
unique index.
REGISTRATION TABLE table-name
System action
Explanation
An error occurred while accessing the application
registration table or object registration table. The
Programmer response application registration table or object registration
table was dropped, but the DROP statement was not
Determine whether the required unique index does
committed.
exist. If not, create the required index. If the index
does exist, but is not unique, drop it and re-create it as
a unique index. System action
SQLSTATE
-693 THE COLUMN column-name IN DDL Resubmit the job. If the same error happens, check
REGISTRATION TABLE OR INDEX for the application that issued the DROP statement
name IS NOT DEFINED PROPERLY for the application registration table or the object
registration table. Either commit the DROP statement
which dropped the table and create a new application
Explanation
registration table or object registration table, or issue
An error occurred during verification of the application a ROLLBACK for the DROP statement to put the tables
or object registration table. back.
The table is improperly defined for the following
reasons: SQLSTATE
• A required column is missing. 57023

-695 INVALID VALUE seclabel Programmer response
SPECIFIED FOR SECURITY LABEL
COLUMN OF TABLE table-name Remove the invalid correlation name or transition table
name along with the preceding keyword.
Explanation
SQLSTATE
For an insert or an update operation to table table-
name, the value that was specified for the security 42898
label was invalid. -697 OLD OR NEW CORRELATION
NAMES ARE NOT ALLOWED IN
System action A TRIGGER DEFINED WITH THE
FOR EACH STATEMENT CLAUSE.
The statement cannot be processed. OLD_TABLE OR NEW_TABLE
NAMES ARE NOT ALLOWED IN
Programmer response A TRIGGER WITH THE BEFORE
CLAUSE.
Ensure that the value that is specified for the security
label column is a valid security label. Alternatively,
insert the row that specifies DEFAULT for the security Explanation
label column, or remove the security label column The trigger, as defined, includes a REFERENCING
from the insert column list. clause with one of the following invalid combinations:
• OLD or NEW correlation names specified (or both)
SQLSTATE and the FOR EACH STATEMENT clause.
23523 • NEW_TABLE or OLD_TABLE correlation names
specified (or both) and the BEFORE clause.
-696 THE DEFINITION OF TRIGGER
trigger-name INCLUDES AN
INVALID USE OF CORRELATION System action
NAME OR TRANSITION
The statement cannot be processed. The trigger was
TABLE NAME name. REASON
not defined.
CODE=reason-code
Programmer response
Explanation
Remove invalid correlation names or change the
The trigger definition included an invalid use of name
trigger granularity to FOR EACH ROW.
trigger-name
The trigger that encountered the error
SQLSTATE
name
The transition variable correlation name or 42899
transition table name -713 THE REPLACEMENT VALUE FOR
reason-code special-register IS INVALID
A reason-code indicating the specific problem as
follows: Explanation
1. NEW correlation name and NEW_TABLE name The value specified in the SET special-register
are not allowed in a DELETE trigger. statement is not a valid value of the indicated special
2. OLD correlation name and OLD_TABLE name register.
are not allowed in an INSERT trigger.
3. OLD_TABLE name and NEW_TABLE name are System action
not allowed in a BEFORE trigger.
System action
Programmer response
The statement cannot be processed. The trigger was
not created. See the description of the special register statement
and correct the replacement value.

SQLSTATE the contents of the DBRM have been modified after the
precompilation phase.
42815 or 3F000
Related reference User response
Special registers (Db2 SQL)
Precompile the named program again using the
General rules for special registers (Db2 SQL) current precompiler. Reissue the BIND subcommand.
-715 PROGRAM program-name WITH
MARK release-dependency-mark Problem determination
FAILED BECAUSE IT DEPENDS
If the program was precompiled at an appropriate
ON FUNCTIONS OF THE RELEASE
release, and the problem persists, collect the
FROM WHICH FALLBACK HAS
following:
OCCURRED
• A hexadecimal print of the first record of the failing
DBRM
Explanation
• The listing from the precompile job that generated
Program program-name depends on a function of Db2 the DBRM
that is not supported by the current active release.
• Output from the BIND attempt.
program-name
Name of the application program.
SQLSTATE
release-dependency-mark
A 1-character mark showing the oldest Db2 56065
release supporting this program.
-717 bind-type FOR object-type
object-name WITH MARK
System action release-dependency-mark FAILED
BECAUSE object-type DEPENDS
The BIND operation for this plan or package is not
ON FUNCTIONS OF THE RELEASE
performed.
FROM WHICH FALLBACK HAS
OCCURRED
Operator response
Notify the system programmer. Explanation
The plan or package indicated depends on a function
System programmer response of Db2 which is not supported by the currently active
release.
Warn users not to use plans or packages containing
this program until the Db2 subsystem has been bind-type
remigrated to the newer release. REBIND
object-type
User response PLAN | PACKAGE
The program cannot be used until the Db2 subsystem object-name
is remigrated to the newer release. Name of the application plan, or the package
release-dependency-mark
SQLSTATE A one-character mark showing the oldest
release of Db2 can support this plan or
56064 package. The release dependency mark for
the plan is kept in the IBMREQD columns in
-716 PROGRAM program-name
the Db2 catalog in SYSIBM.SYSPLAN (plans),
PRECOMPILED WITH INCORRECT
SYSIBM.SYSPACKAGE(packages).
LEVEL FOR THIS RELEASE
System action
Explanation
The REBIND operation for this plan or package is not
Program program-name was precompiled under a
performed.
release not supported by the current level of Db2, or

Operator response auth-id
Authorization ID of the invoker of the BIND
Notify the system programmer. subcommand.
package-name
System programmer response Name of the package
Warn users not to use the plan or package until the (location.collection.package.version).
Db2 subsystem has been remigrated to the newer
release. System action
No package is created.
User response
The plan or package cannot be used until the Db2 System programmer response
subsystem is remigrated to the newer release.
Check the SYSIBM.SYSPACKAGE catalog table
for names of existing application packages.
SQLSTATE Call the BIND subcommand again, with a
56066 'location.collection.package.version' that is not in use.
-718 REBIND OF PACKAGE package-

SQLSTATE
name FAILED BECAUSE IBMREQD
OF ibmreqd IS INVALID 42710
-720 BIND ERROR, ATTEMPTING
Explanation TO REPLACE PACKAGE =
The IBMREQD column of the SYSIBM.SYSPACKAGE package_name WITH version=
catalog table for the named package contains an version2 BUT THIS VERSION
unrecognizable character. ALREADY EXISTS
package-name
Name of the package Explanation
(location.collection.package.version) An attempt is made to create a version of a
package that already exists. The version specified in
System action the REPLVER keyword is different from the version
specified for the precompile. The version specified
The REBIND failed. for the precompile already exists in the catalog. The
combination of 'location.collection.package.version'
User response must be unique in the SYSIBM.SYSPACKAGE catalog
table. A common mistake is that the user may believe
You must do a BIND ACTION(REPLACE) for this that the version he is creating is the one specified
package. in the REPLVER keyword. This is not the case. The
version specified in the REPLVER keyword is the name
SQLSTATE of the version being replaced. The version that will be
created is the version that was given to the program
56067 when it was precompiled.
-719 BIND ADD ERROR USING auth- package_name
id AUTHORITY PACKAGE package- Fully qualified package name
name ALREADY EXISTS
version2
Version-id of package that is to be created
Explanation
An attempt is made to add a package System action
that already exists. The combination
The bind will fail.
of 'location.collection.package.version' must
be unique in the SYSIBM.SYSPACKAGE
table. In addition, the combination of System programmer response
'location.collection.package.consistency-token' must
There are two approaches to solve this problem.
be unique.
The first is to precompile the program again with

a new version name and reissue the original BIND bind-type
subcommand. The other approach is not to do the Type of bind subcommand (BIND | REBIND |
precompile but reissue the BIND subcommand with FREE).
REPLVER(SAME). auth-id
Authorization ID of the invoker of the BIND
SQLSTATE subcommand.
42710 package-name
Name of the package
-721 BIND ERROR FOR PACKAGE = pkg- (location.collection.package.version)
id CONTOKEN = contoken'X IS
NOT UNIQUE SO IT CANNOT BE
CREATED
System action
Package not rebound or freed.
Explanation
An attempt is made to add or replace a package
with a consistency token that is not unique for Check the SYSPACKAGE catalog table for the correct
that package. In other words, the combination of 'location.collection.package.version' to use.
location.collection.package.consistency-token already
exists.
SQLSTATE
pkg-id
Fully qualified name of the package. 42704
contoken -723 AN ERROR OCCURRED IN A

Consistency token in hexadecimal. TRIGGERED SQL STATEMENT
IN trigger-name. INFORMATION
RETURNED: SQLCODE: sql-code,
System action SQLSTATE: sql-state, MESSAGE
The BIND will fail. TOKENS token-list, SECTION
NUMBER section-number
Explanation
Check the SYSIBM.SYSPACKAGE catalog table
for names of existing application packages During execution of an UPDATE, MERGE, INSERT, or
with the indicated consistency token. Reissue DELETE statement, a trigger was activated. One of
the BIND subcommand such that the the triggered SQL statements received an SQL error
location.collection.package.consistency-token is unique condition.
within the catalog. The following SQL statement can be trigger-name
used to query the catalog: The trigger that was activated when the error
SELECT COLLID,NAME occurred.
FROM loc-id.SYSIBM.SYSPACKAGE
WHERE HEX(CONTOKEN) = contoken
section-number
The section number that is associated with the
failing triggered SQL statement. For triggers that
SQLSTATE contain a WHEN clause, the WHEN clause is
section number one. The triggered SQL statements
42710 are numbered sequentially, beginning with section
-722 bind-type ERROR USING auth-id number two. This is true for triggers with or
AUTHORITY PACKAGE package- without a WHEN clause.
name DOES NOT EXIST sql-code
A numeric value that indicates why the SQL
Explanation statement execution was unsuccessful. This code
is received by the activated trigger.
The indicated subcommand was issued against a sql-state
package that does not exist. The individual variable The corresponding SQLSTATE for the SQLCODE.
fields contain:

token-list Note that recursive situations where a trigger includes
The list of tokens from the original SQL error. This a triggered SQL statement that directly or indirectly
list might be truncated. causes the same trigger to be activated are very likely
to cause this error. The trigger should contain logic to
System action check for a terminating condition to prevent this error.
object-type
The trigger and the original statement cannot be
Names the type of object being called. Object type
processed. The triggering table is unchanged.
is TRIGGER, FUNCTION, or PROCEDURE.
object-name
System programmer response Specifies the name of the trigger, user-defined
Identify the failing SQL statement by using one of the function or stored procedure that would have be
following methods: activated at the seventeenth level of cascading.
• Use the trigger name and section number.
System action
• If the trigger definition is available, use the section
number. The original statement could not be executed. All
• Use the following SELECT statement to retrieve the SQL statements executed by all triggers, user-defined
statement from the SYSIBM.SYSPACKSTMT catalog functions, and stored procedures in the cascade chain
table: are rolled back. External actions performed by the
indirect SQL, such as sending a network message
SELECT STMT, SEQNO FROM SYSIBM.SYSPACKSTMT might have already occurred.
WHERE COLLID = 'schema-name' AND
NAME = 'trigger-name' AND
SECTNOI = section-number Programmer response
ORDER BY SEQNO
Start with the indirect SQL that is activated by the
The STMT result is in Unicode, unless the trigger was original SQL operation. Check for recursive patterns in
created in DB2 version 7 or earlier. To view a Unicode any invoked user-defined functions or in any triggers
result as EBCDIC, issue the DISPLAY UTF8 command defined on the subject of an update operation. If
in the ISPF browse program within SPUFI. the chain is not recursive, the cascade chain must
Refer to the explanation of the SQLCODE that is be simplified by altering the triggers, user-defined
indicated by sql-code in this code and take the functions, or stored procedures involved.
appropriate action or actions.
SQLSTATE
Contact your database administrator to determine why -725 THE SPECIAL REGISTER register
the trigger named in the message received the error. AT LOCATION location WAS
SUPPLIED AN INVALID VALUE
SQLSTATE
09000 Explanation
-724 THE ACTIVATION OF THE object- Db2 received a SET statement with an invalid value.
type OBJECT object-name WOULD Valid SETs might be allowed or retained. Further
EXCEED THE MAXIMUM LEVEL OF processing stops at the named site until the SET
INDIRECT SQL CASCADING statement is corrected.

Cascading of indirect SQL occurs when a trigger, user- All SQL statements at the named remote site are
defined function or stored procedure invokes another rejected until the SET statement that was in error is
trigger, user-defined function or stored procedure corrected.
which in turn invokes another. The activation of some
of the triggers in this chain might be due to the Programmer response
enforcement of referential constraint delete rules. The
depth of this cascading is limited to 16. The SET statement should be reissued with a valid
value. This situation can be corrected with a local SET

statement or with a DRDA SET statement executed at SQLSTATE
the remote site. Once the special register has been
supplied a valid value, the application can resume 429B1
execution. -730 THE PARENT OF A TABLE IN A
READ-ONLY SHARED DATABASE
SQLSTATE MUST ALSO BE A TABLE IN A
READ-ONLY SHARED DATABASE
42721
-726 BIND ERROR ATTEMPTING TO Explanation
REPLACE PACKAGE = package-
name. THERE ARE ENABLE OR An attempt was made to define a relationship between
DISABLE ENTRIES CURRENTLY a table in a read-only shared database and a table that
ASSOCIATED WITH THE PACKAGE is not.

The BIND subcommand was issued to replace a The statement cannot be processed.
package that has ENABLE or DISABLE entries currently
associated with the package. Programmer response
Ensure that the correct tables are being used for the
System action relationship being defined.
Package not bound.
SQLSTATE
System programmer response 56053
FREE the package first and then BIND the package. -731 USER-DEFINED DATASET dsname
MUST BE DEFINED WITH
SQLSTATE SHAREOPTIONS(1,3)
55030
Explanation
-729 A STORED PROCEDURE
SPECIFYING COMMIT ON RETURN The VSAM SHAREOPTIONS must be (1,3) for all of
CANNOT BE THE TARGET OF A the indexes and table spaces in the database. The
NESTED CALL STATEMENT user-defined data set identified did not meet this
requirement.
Explanation
System action
A stored procedure defined with the COMMIT ON
RETURN attribute was called from a stored procedure, The statement cannot be processed.
user-defined function, or trigger. Stored procedures
defined with COMMIT ON RETURN cannot be nested Programmer response
in this way.
Ensure that the data sets used in the shared database
are defined with the proper SHAREOPTIONS.
System action
The SQL statement is not executed. If the CALL SQLSTATE
statement references a remote server, the unit of work
is placed in a must rollback state. 56054
-732 THE DATABASE IS DEFINED ON
Programmer response THIS SUBSYSTEM WITH THE
ROSHARE READ ATTRIBUTE BUT
Remove the CALL to the stored procedure that was THE TABLE SPACE OR INDEX
defined with the COMMIT ON RETURN attribute. SPACE HAS NOT BEEN DEFINED
ON THE OWNING SUBSYSTEM

Prior to creating a table space or index in a database The statement cannot be processed.
with the ROSHARE READ attribute, that object must
first be defined on the owning subsystem. Programmer response
Ensure that the definition of the table space, index, or
System action
table is consistent with that in the ROSHARE OWNER
The statement cannot be processed. database.

Verify that the table space or index has been 56056
defined on the owning system in a ROSHARE OWNER
database. -734 THE ROSHARE ATTRIBUTE OF A
DATABASE CANNOT BE ALTERED
FROM ROSHARE READ
SQLSTATE
56055 Explanation
-733 THE DESCRIPTION OF A TABLE An attempt was made to ALTER a database from
SPACE, INDEX SPACE, OR TABLE ROSHARE READ to either ROSHARE OWNER or
IN A ROSHARE READ DATABASE ROSHARE NONE.
MUST BE CONSISTENT WITH ITS
DESCRIPTION IN THE OWNER System action
SYSTEM
Explanation
Programmer response
This code is issued while creating a table space,
index, or table in the ROSHARE READ database. These Verify that the correct database was specified on the
objects must be consistent with their descriptions in ALTER DATABASE statement. The ROSHARE attribute
the ROSHARE OWNER database as follows: of a read-only shared database cannot be altered. To
change this, DROP and re-create the database.
• For a table space, the following attributes must be
the same:
SQLSTATE
– Page size
56057
– Segment size
– Number of partitions -735 DATABASE dbid CANNOT BE
ACCESSED BECAUSE IT IS NO
• For an index, the following attributes must be the
LONGER A SHARED DATABASE
same:
– Number of partitions Explanation
– Number of subpages
An attempt was made to access an object in the
– Table OBID database identified by dbid, that is known to the
– Total key length system as having the ROSHARE READ attribute. The
– Index type (Type 1 or Type 2 Index) database, however, is no longer defined as ROSHARE
OWNER on the owning subsystem.
– Number of key columns
• For a table, the following attributes must be the System action
same:
– Table OBID
– Maximum record length
Programmer response
– Number of columns
Verify that the correct object is specified on the
– Whether an edit procedure exists statement.

55004 A CREATE TABLE statement was issued using an
implicit table space. An implicit table space may not
-736 INVALID OBID obid SPECIFIED be used in a database that has been defined as a read-
only shared database.
Explanation
An invalid OBID value was given or encountered. The System action
OBID is invalid for one of the following reasons: The statement cannot be processed.
• The specified OBID for the CREATE TABLE statement
does not fall within the acceptable range for OBIDs, Programmer response
which is 2 to 32767.
CREATE a table space for the table, using the same
• The specified OBID for the CREATE TABLE statement
name as is given on the owning system. Then resubmit
is already in use for the given database.
the CREATE TABLE statement.
• The ALTER statement encountered an existing object
with an OBID that does not fall within the acceptable
range for OBIDs, which is 2 to 32767. SQLSTATE
56056
System action -739 CREATE OR ALTER FUNCTION
The statement cannot be processed. function-name FAILED BECAUSE
FUNCTIONS CANNOT MODIFY
DATA WHEN THEY ARE
Programmer response PROCESSED IN PARALLEL.
For the CREATE TABLE statement, verify that the given
OBID is a valid value for an OBID. If so, ensure that the Explanation
OBID is correct for the object to be created, then query
the catalog to find the object that is already defined The function cannot be created or altered because
as having the same OBID in the database. If an invalid ALLOW PARALLEL and MODIFIES SQL DATA were both
OBID was given for the object to be created, correct specified explicitly or implicitly. A function cannot be
the statement and execute it again. If the existing parallelized if it modifies data.
object is in error, then DROP and CREATE that object
using the correct OBID value. System action
For the ALTER statement, query the catalog to find the The statement cannot be processed.
object that is already defined as having the same OBID
in the database. DROP and CREATE that object using a
valid OBID value. Programmer response
It is possible that the OBID “in use” is the OBID for Specify DISALLOW PARALLEL or change the MODIFIES
an object that had been previously dropped. If that is SQL DATA to NO SQL, CONTAINS SQL or READS SQL
the case, and the CREATE was issued for a table in a DATA.
non-ROSHARE READ database, then select a different
OBID for use in the OBID clause. If the object had SQLSTATE
been previously dropped and the CREATE was issued
for a table in a ROSHARE READ database, COMMIT and 56088
re-submit the CREATE TABLE request. -740 FUNCTION name IS DEFINED
WITH THE OPTION MODIFIES SQL
SQLSTATE DATA WHICH IS NOT VALID IN
THE CONTEXT IN WHICH IT WAS
53014 INVOKED
Related reference
CREATE TABLE (Db2 SQL) Explanation
-737 IMPLICIT TABLE SPACE NOT A user-defined function that is defined with the
ALLOWED MODIFIES SQL DATA clause was invoked in an invalid
context.

name SQLSTATE
The name of the user-defined function.
55020
A user-defined function that is defined with MODIFIES
SQL DATA is only allowed in a: -742 DSNDB07 IS THE IMPLICIT WORK
FILE DATABASE
• VALUES clause of an insert operation
• SET clause of an update operation Explanation
• VALUES statement in a trigger
The WORKFILE clause cannot be used on a CREATE
• SET assignment statement DATABASE statement to create a work file database
• CALL procedure statement for a Db2 subsystem that is not a member of a Db2
data sharing group. The system database, DSNDB07, is
• subselect
the implicit work file database.
System action
System action
The SQL statement failed.
Programmer response
Programmer response
Remove the user-defined function from the failing
To create the work file database for a Db2 subsystem
statement, or remove the MODIFIES SQL DATA option
that is not a member of a Db2 data sharing group,
from the definition of the function.
create database DSNDB07 without the WORKFILE
clause.
SQLSTATE
51034 SQLSTATE
-741 A database-type DATABASE IS 53004
ALREADY DEFINED FOR MEMBER
-746 THE SQL STATEMENT IN
member-name
FUNCTION, TRIGGER, OR IN
STORED PROCEDURE name
Explanation VIOLATES THE NESTING SQL
A CREATE DATABASE statement was issued for a RESTRICTION
WORK FILE or TEMP database, but the database can
not be created because one is already defined for the Explanation
named Db2 subsystem or data sharing group member.
If a table is being modified (by INSERT, DELETE,
database-type UPDATE, or MERGE), the table can not be accessed
WORK FILE or TEMP by the lower level nesting SQL statement.
member-name If any table is being accessed by a SELECT statement,
Name of the Db2 subsystem or data sharing no table can be modified (by INSERT, DELETE,
group member that already has a database-type UPDATE, or MERGE) in any lower level nesting SQL
database. statement.

The statement cannot be processed. The SELECT, INSERT, DELETE, UPDATE or MERGE SQL
statement failed.
Programmer response
Verify the identity and validity of the existing Programmer response
database-type database for the named Db2 subsystem Remove the failing statement from the named
or data sharing member. The existing database can function, trigger or the stored procedure.
be altered or dropped if necessary. If the existing
database is dropped, resubmit the CREATE DATABASE
statement. SQLSTATE
57053

-747 TABLE table-name IS NOT SQLSTATE
AVAILABLE UNTIL THE AUXILIARY
TABLES AND INDEXES FOR ITS 54042
EXTERNALLY STORED COLUMNS -750 THE SOURCE TABLE source-name
HAVE BEEN CREATED CANNOT BE RENAMED OR
ALTERED AS SPECIFIED
Explanation
An attempt was made to access or reference a table Explanation
with one or more LOB columns, however either An attempt was made to rename a table, index, or
• an auxiliary table for storing one of the LOB columns column, but the source object could not be renamed.
has not been created, or source-name
• an index has not been created for an auxiliary table, The name of the source table, index, or column.
or Possible reasons for this error include, but are not
• there is not an auxiliary table for each partition of the limited to:
table space.
RENAME TABLE statements
System action • The table is referenced as the triggering table in

one or more existing triggers.
• The table is a system-period temporal table or
history table.
Programmer response • The table is defined as an active resource limit
• Use CREATE TABLESPACE to create a LOB table table.
space. • The table is a clone table.
• Use CREATE TABLE to create the auxiliary table for • The table has a clone table defined for it.
storing the column.
• The table is referenced in one or more view
• Use CREATE INDEX to create an index on the definitions.
auxiliary table.
• The table has a synonym defined for it.
• Resubmit the statement that failed.
• The table is an archive-enabled table.
• The table is an archive table.
SQLSTATE
• The table is an accelerator-only table.
57054
• The table is defined as a Db2ZAI table.
-748 AN INDEX index-name ALREADY
RENAME INDEX statements
EXISTS ON AUXILIARY TABLE
table-name • The table is defined as an active resource limit
table.
Explanation • The table is defined as a Db2ZAI table.
The CREATE INDEX statement would create a second ALTER TABLE statements with RENAME COLUMN
index on the specified auxiliary table. An auxiliary clause
table can have only one index. • The table is a materialized query table.
• The definition of one or more materialized query
System action tables references the table.
The statement cannot be processed. • The table is a system period temporal table or
history table.
Programmer response • The table is referenced as the triggering table in
one or more existing triggers.
An index already exists. Another index cannot be
created. • The column is referenced in one or more view
definitions.
• The column is referenced in a check constraint.
• The column has a field procedure defined.

• The table has a valid procedure or an edit All further SQL statements are rejected until
procedure that is defined with row attribute the SQL application that issued the SQL CALL
sensitivity. statement rolls back the unit of work. When
• An index is defined on the table with an control returns to the SQL application that
expression that references the column. issued the SQL CALL statement, the SQL
application must roll back the unit of work.
• The table is an archive-enabled table. This can be done by issuing an SQL ROLLBACK
• The table is an archive table. statement or the equivalent IMS or CICS
• The table is defined as a Db2ZAI table. operation.
User-defined function
System action The external function that is indicated by
object-name issued either a COMMIT or
The statement cannot be processed. ROLLBACK statement.
object-name
Programmer response The name of the object.
Change the source name to the name of an object that specific-name
can be renamed or altered, and reissue the statement. The specific function name, which is unique within
the schema.
Drop any triggers defined on the table before issuing
the RENAME statement. To find these triggers, query sql-statement
the system catalog. The SQL statement that was issued.
Drop any view that reference the table before issuing
the RENAME statement. To find these views, query the System action
system catalog. The statement cannot be processed.
If there is a clone defined on the table, drop the clone
table before issuing the RENAME statement. Programmer response
Either remove all COMMIT and ROLLBACK statements
SQLSTATE from the stored procedure, or modify the client
42986 application so that it establishes an environment that
allows the stored procedure to execute statements.
Related reference Remotely called stored procedures can execute
ALTER TABLE (Db2 SQL) embedded COMMIT or ROLLBACK statements if the
RENAME (Db2 SQL) following conditions are met:
• The connection with the requester system must use
-751 object-type object-name (SPECIFIC
one phase commit protocols.
NAME specific name) ATTEMPTED
TO EXECUTE AN SQL STATEMENT • The requester system must indicate that commits
sql-statement THAT IS NOT are allowed by sending a DRDA RDBCMTOK=TRUE
ALLOWED indication when the stored procedure is called.
For Db2 Connect requester systems, the client
Explanation application must use either Connect Type 1 or
Remote Unit of Work connections. Other connections
A stored procedure or user-defined function
cause Db2 Connect to indicate that commits are not
attempted to execute an SQL statement that is not
allowed, which will cause COMMIT and ROLLBACK
allowed.
statements in a stored procedure to fail.
object-type
The type of object: SQLSTATE
Stored procedure
38003
A stored procedure issued an SQL statement
that forced the Db2 thread to roll back the unit 2F003
of work. The SQL statement that caused the
Related reference
thread to be placed in the MUST_ROLLBACK
state is either COMMIT or ROLLBACK: COMMIT (Db2 SQL)
ROLLBACK (Db2 SQL)

-752 THE CONNECT STATEMENT IS • It is a LOB table space and COMPRESS YES was
INVALID BECAUSE THE PROCESS specified, but the associated base table space is not
IS NOT IN THE CONNECTABLE a universal table space.
STATE • It is a hash table and therefore can exist only in
a partition-by-range table space or a partition-by-
Explanation growth table space. Hash tables cannot be created
XML table spaces or in any other type of table space,
The application process attempted to execute a and tables cannot be altered to use hash access
CONNECT statement while in the unconnectable state. unless they are of one of those types.

The statement cannot be processed. The connection The statement cannot be processed.
state of the application process is unchanged.
Programmer response
Programmer response
Take the appropriate action:
Modify the application program to execute a commit
or rollback operation prior to executing the CONNECT • Create the LOB table space in a non-workfile
statement. database.
• Create the table in a non-LOB table space.
SQLSTATE • Create the auxiliary table in a LOB table space.
0A001 • Create a LOB table space and do not specify
LOGGED.
Related concepts
• For a hash-organized table, create a universal table
SQL connection states (Introduction to Db2 for
space that is not an XML or LOB table space.
z/OS)
Distributed relational databases (Introduction
to Db2 for z/OS) SQLSTATE
Explicit CONNECT statements (Introduction to 560A1
Db2 for z/OS)
-764 A LOB TABLE SPACE AND ITS
Related reference
ASSOCIATED BASE TABLE SPACE
CONNECT (Db2 SQL) MUST BE IN THE SAME DATABASE
-763 INVALID TABLE SPACE NAME
space-name Explanation
An attempt was made to create an auxiliary table in a
Explanation LOB table space that is not in the same database as
the associated base table space.
The named table space is invalid.
space-name System action
The name of the table space.
Possible reasons for this error include:
• It is a LOB table space and therefore cannot reside in Programmer response
a work file database.
Correct the statement to specify a LOB table space in
• It is a LOB table space and therefore cannot contain
the same database as the associated base table space.
a non-auxiliary table.
• It is not a LOB table space and therefore cannot
contain an auxiliary table. SQLSTATE
• It is a LOB table space and LOGGED was specified, 560A2
but the associated base table space is defined as -765 TABLE IS NOT COMPATIBLE WITH
NOT LOGGED. DATABASE

Explanation A security label column cannot be added to an
archive table.
A CREATE TABLE or ALTER TABLE statement defines
a LOB column in a table whose database attribute Archive-enabled table
is ROSHARE OWNER or ROSHARE READ. This is not An archive-enabled table must be the only table
permitted. in the table space, and it must not be any of the
following types of tables:
System action • An incomplete table
The statement cannot be processed. • An auxiliary table
• A clone table or a table with a clone defined on it
Programmer response • A table that was implicitly created for an XML
column
If CREATE TABLE, either assign the table to an
ROSHARE NONE database or create the table without • A table that contains a security label column
a LOB column. If ALTER TABLE, redefine the column as A security label column cannot be added to an
a non-LOB column or move the table to an ROSHARE archive-enabled table.
NONE database.
Auxiliary table
An auxiliary table for a LOB column must not be
SQLSTATE specified as the target of the following statements:
560A3 • ALTER TABLE
-766 THE OBJECT OF A STATEMENT • CREATE ALIAS
IS A TABLE FOR WHICH THE • CREATE FUNCTION
REQUESTED OPERATION IS NOT
PERMITTED • CREATE SYNONYM
• CREATE VIEW
Explanation • DELETE
The requested operation is not valid for the table that • DESCRIBE TABLE
was specified in the SQL statement. • INSERT
This error can occur when the statement violates one • MERGE
of the following requirements, depending on the type • SELECT
of table:
• TRUNCATE
Accelerator-only table • UPDATE
An accelerator-only table must not be specified in
any of the following statements: Attributes of an auxiliary table cannot be altered.
However, the APPEND attributes of auxiliary tables
• A CREATE SYNONYM statement to define a can be altered.
synonym.
Aliases and synonyms cannot be created on an
• A CREATE TRIGGER statement to define a trigger
auxiliary table.
for the accelerator-only table.
• A LOCK TABLE statement. Data in an auxiliary table cannot be accessed by
specifying the auxiliary table name in the SELECT,
• A CREATE INDEX statement. INSERT, DELETE, UPDATE, MERGE, CREATE
Archive table PROCEDURE, or CREATE FUNCTION statement.
An archive table must be the only table in the table Data in an auxiliary table can be accessed only
space, and it must not be any of the following through operations on the base table columns.
types of tables: CLUSTER cannot be specified on an ALTER TABLE
• An incomplete table statement if the table is an auxiliary table.
• An auxiliary table Implicitly created table for an XML column
• A clone table or a table with a clone defined on it An implicitly created table for an XML column must
not be specified as the target of the following
• A table that was implicitly created for an XML statements:
column
• ALTER TABLE
• A table that contains a security label column

• CREATE ALIAS LOB table spaces (Db2 Administration Guide)
• CREATE FUNCTION XML table spaces (Db2 Administration Guide)
• CREATE INDEX -767 MISSING OR INVALID COLUMN
• CREATE SYNONYM SPECIFICATION FOR INDEX index-
• CREATE TRIGGER name
• CREATE VIEW
Explanation
• DELETE
• DESCRIBE TABLE The CREATE INDEX statement failed for one of the
following reasons:
• INSERT
• An index on a non-auxiliary table must specify the
• MERGE
columns on which the index is defined.
• REVOKE
• An index on an auxiliary table must not have a
• SELECT column specification.
• TRUNCATE
• UPDATE System action
Table with system-period data versioning The statement cannot be processed.
A table with system-period data versioning must
be the only table in the table space, and it must not Programmer response
be any of the following types of tables:
Correct the syntax of the CREATE INDEX statement.
• An incomplete table
• An auxiliary table • To create an index on a non-auxiliary table, specify
the columns on which the index is defined.
• A clone table or a table with a clone defined on it
• To create an index on an auxiliary table, do not
• A table that was implicitly created for an XML specify the name of any column.
column
• A table that contains a security label column SQLSTATE
A security label column cannot be added to a 42626
system-period temporal table.
-768 AN AUXILIARY TABLE ALREADY
This error can also occur when a TRANSFER
EXISTS FOR THE SPECIFIED
OWNERSHIP statement is specified for transferring
COLUMN OR PARTITION
the ownership of a table that contains a SECURITY
LABEL column.
Explanation
System action An attempt was made to create an auxiliary table, but
an auxiliary table for the specified column or partition
already exists. When the base table belongs to a non-
partitioned table space, there can be only one auxiliary
Programmer response table per LOB column of the table. When the base
table belongs to a partitioned table space, for any
Correct the statement to specify the corresponding
given LOB column, all values of the LOB column for
base table instead of the specified table, and resubmit
a given partition are stored in their own auxiliary table.
the statement.
There must be one auxiliary table per partition of the
base table space.
SQLSTATE
560A4 System action
(Introduction to Db2 for z/OS) Programmer response
Administration Guide) Check that the correct table name, column name, and
if applicable, partition number have been specified. If

the existing auxiliary table needs to have a different of column in the same table. This error can occur in the
name, execute the RENAME TABLE statement to following situations:
rename the auxiliary table.
• The statement attempted to create a table with a
LOB column or to add a LOB column to a table, but
SQLSTATE the table does not have a ROWID column. A table
with a LOB column must also have a ROWID column.
560A5
• The statement attempted to create a table with an
-769 SPECIFICATION OF CREATE AUX XML column or to add an XML column to a table,
TABLE DOES NOT MATCH THE but the table does not have a DOCID column. A
CHARACTERISTICS OF THE BASE table with an XML column must also have a DOCID
TABLE column.

Either an attempt was made to create an auxiliary The statement cannot be processed.
table
• using the PART clause and the specified base table is Programmer response
not partitioned or
If creating a table, define an additional column for the
• without using the PART clause and the specified ROWID or DOCID column in the same table.
base table is partitioned
If the base table is not partitioned, then the PART SQLSTATE
keyword is not allowed on the CREATE AUXILIARY
TABLE statement. If the base table is partitioned, then 560A6
the PART keyword must be specified.
-771 INVALID SPECIFICATION OF A
ROWID COLUMN
System action
The auxiliary table was not created. Explanation
For an ALTER TABLE or CREATE TABLE statement, the
Programmer response specification of a ROWID column might be invalid for
Check whether the name of the base table specified
in the CREATE AUXILIARY TABLE statement is correct. • A ROWID column cannot be added to a temporary
If it is correct and the table is not partitioned, remove table.
the PART clause from the statement. If it is correct and • A ROWID column cannot be specified in a
the table is partitioned, add the PART clause to the referential-constraint clause as a column of a foreign
statement. If the table name is not correct, correct the key.
name and also check that the correct column name is
specified. • A ROWID column cannot be a column of a primary
key or unique key.
SQLSTATE • A ROWID column cannot be a column in a table with

an edit procedure that is defined with row attribute
53096 sensitivity.
-770 TABLE table-name CANNOT HAVE • A ROWID column cannot be part of the implicit
A LOB COLUMN UNLESS IT ALSO or explicit column list for fullselect in the as-result-
HAS A ROWID, OR AN XML table clause of a CREATE TABLE or DECLARE
COLUMN UNLESS IT ALSO HAS A GLOBAL TEMPORARY TABLE statement.
DOCID COLUMN • A ROWID column that is implicitly generated cannot
be dropped.
Explanation • A ROWID column that is defined as GENERATED BY
table-name DEFAULT cannot be dropped if the table contains an
The name of the table. implicitly generated ROWID column.
An attempt was made to create a table, table-name,

with a column that has a dependency on another type

• A ROWID column cannot be dropped if the table SQLSTATE
contains LOB columns that are dependent on the
ROWID column. 428D4
-778 ENDING LABEL label-name DOES
System action NOT MATCH THE BEGINNING
LABEL
Explanation
Programmer response
The label that is specified at the end of a compound,
Correct the syntax and resubmit the statement. WHILE, REPEAT, or LOOP statement in an SQL routine
is not the same as the label at the beginning of the
SQLSTATE statement. The end label cannot be specified if the
begin label is not specified.
428C7
label-name
Related reference The name given for the ending label.
System action
-773 CASE NOT FOUND FOR CASE The statement cannot be processed.
STATEMENT
User response
Explanation
Ensure that the end label is the same as the begin
A case statement without an ELSE clause was label for the compound, WHILE, REPEAT, or LOOP
specified in the body of an SQL routine. None of the statement.
conditions specified in the CASE statement were met.
SQLSTATE
System action
428D5
-779 LABEL label SPECIFIED ON
A GOTO, ITERATE, OR LEAVE
Programmer response STATEMENT IS NOT VALID
Change the CASE statement to handle all of the
conditions that can occur. Explanation
Label label is specified as the target label for a GOTO,
SQLSTATE ITERATE or LEAVE statement. label is not defined, is
20000 not defined in a scope that is accessible to the current
statement, or to the current statement, or it is not a
-776 USE OF CURSOR cursor-name IS valid label for the failing statement.
NOT VALID
This error can occur with a GOTO, ITERATE or LEAVE
statement for one of the following reasons:
Explanation
• If the failing statement is in a condition handler, then
Cursor cursor-name is specified as the cursor name label must be defined in that condition handler.
on a FOR statement in an SQL procedure. The cursor
• If the failing statement is not in a condition handler,
cannot be specified on a CLOSE, FETCH, or OPEN
then label must not be defined in a condition
statement within the FOR statement.
handler.
System action Additionally, this error can be issued for ITERATE or

LEAVE statements for one of the following reasons:
• If the failing statement is an ITERATE statement,
then label must be defined as a label for a
Programmer response FOR, LOOP, REPEAT, or WHILE statement, and the
Remove the CLOSE, FETCH, or OPEN statement. ITERATE statement must be in that FOR, LOOP,

REPEAT, or WHILE statement, or in a block of System action
code that is directly or indirectly nested within that
statement. The statement cannot be processed.
• If the failing statement is a LEAVE statement, then
label must be defined as a label for a compound, User response
FOR, LOOP, REPEAT, or WHILE statement, and the Define the condition using the DECLARE CONDITION
LEAVE statement must be in that compound, FOR, statement in a compound statement, and verify that
LOOP, REPEAT, or WHILE statement, or in a block of the reference is in the same scope as the declaration.
code that is directly or indirectly nested within that Alternately, you can remove the reference to the
statement. condition.

Related reference
User response
compound-statement (Db2 SQL)
Specify a valid label for the target of the GOTO,
ITERATE, or LEAVE statement. -782 A CONDITION OR SQLSTATE
condition-value SPECIFIED IS NOT
VALID
SQLSTATE
42736 Explanation
-780 UNDO SPECIFIED FOR A HANDLER An SQL routine specified a condition value that is not
valid.
Explanation condition-value
In an SQL routine, a compound statement contains an Either a specific condition value, which is provided
UNDO handler. UNDO handlers are not supported. as an SQLSTATE value, or a general condition
value, such as SQLEXCEPTION, SQLWARNING, or
NOT FOUND.
System action
The condition or SQLSTATE value is not valid for one of
• The handler declaration or condition declaration
User response
specifies an SQLSTATE value that is not valid.
Change the UNDO handler to a CONTINUE or EXIT • The condition or SQLSTATE value has already been
handler. specified by another handler in the same scope.
• The condition or SQLSTATE was specified in the
SQLSTATE same handler as SQLEXCEPTION, SQLWARNING, or
428D6 NOT FOUND.
-781 CONDITION condition-name IS

NOT DEFINED OR THE
System action
DEFINITION IS NOT IN SCOPE The statement cannot be processed.
Explanation User response

A condition was specified in a handler declaration, Correct the condition or SQLSTATE value.
SIGNAL, or RESIGNAL statement, but either the
condition is not defined in the routine or the reference
SQLSTATE
to the condition name is not in the scope of the
declaration of the condition name. 428D7
condition-name -783 SELECT LIST FOR CURSOR cursor-
The name of the condition that is not defined. name IN FOR STATEMENT IS NOT

VALID. COLUMN column-name IS Explanation
NOT UNIQUE
The use of SQLCODE or SQLSTATE in an SQL routine
body is invalid for one of the following reasons:
Explanation
• SQLCODE or SQLSTATE was specified as a parameter
The SELECT list in the FOR statement must contain name.
unique column names. The SELECT list specified
• SQLCODE is not declared as INTEGER in a return-
either contains duplicate column names or unnamed
codes-declaration clause.
expressions.
• SQLSTATE is not declared as CHAR(5) in a return-
• If two column names are the same, the column codes-declaration clause.
name is column-name.
• SQLCODE or SQLSTATE is assigned the value NULL.
• If the problem is the result of unnamed expressions
then *N is returned for column-name.
System action
The statement cannot be processed. User response

Correct the parameter list, declaration of an SQLCODE
Programmer response or SQLSTATE variable, or correct the assignment of a
Specify unique column names in the SELECT list value to an SQLCODE or SQLSTATE variable.
specified in the FOR statement.
SQLSTATE
SQLSTATE 428D8
42738
-787 RESIGNAL STATEMENT ISSUED
-784 CONSTRAINT constraint-name OUTSIDE OF A HANDLER
CANNOT BE DROPPED.
Explanation
Explanation The RESIGNAL statement, specified in an SQL
A constraint that is implicitly generated when a procedure, must be specified inside a handler.
BUSINESS_TIME period is defined cannot be dropped
using an ALTER TABLE statement with either a DROP System action
CHECK or DROP CONSTRAINT clause.
constraint-name
The name of the constraint that cannot be
dropped. Programmer response
Remove the RESIGNAL statement or use a SIGNAL
System action statement. Try the request again.
SQLSTATE
User response 0K000
No action is required. -788 THE SAME ROW OF TARGET TABLE
table-name WAS IDENTIFIED
MORE THAN ONCE FOR AN
SQLSTATE
UPDATE, DELETE, OR CHANGE
42860 OPERATION OF THE MERGE
STATEMENT
Related reference
Explanation
-785 USE OF SQLCODE OR SQLSTATE IS The ON search-condition of the MERGE statement
NOT VALID matched a single row from the target table with

multiple rows of the source table-reference. This could Programmer response
result in the target row being operated on more than
once with an update or delete operation, and is not Do not specify a default value for a parameter of type
allowed. ARRAY.
table-name Do not specify a table parameter.

The name of the target table of the MERGE
statement. SQLSTATE
429BB
System action
Related reference
The statement cannot be processed. CREATE VARIABLE (Db2 SQL)
CREATE PROCEDURE (Db2 SQL)
Programmer response
-797 THE TRIGGER trigger-name
IS DEFINED WITH AN
• Correct the search condition to ensure that each UNSUPPORTED TRIGGERED SQL
row in the target table matches only one row in the STATEMENT
source table.
• Aggregate the rows in the source table that match Explanation
the row in the target table by using GROUP BY
functions. The trigger definition includes an unsupported
triggered SQL statement. The SQL statements allowed
• Use the ROW_NUMBER() OLAP expression to as a triggered SQL statement are defined in the
generate unique rows. appropriate CREATE TRIGGER (basic or advanced)
trigger topic. The SQL-trigger-body, and triggered-
SQLSTATE SQL-statement syntax fragments, and the associated
descriptions, document additional rules about what is
21506 allowed in the body of a trigger.
Related reference
MERGE (Db2 SQL) System action
The CREATE TRIGGER statement cannot be executed,
OLAP specification (Db2 SQL) and the trigger is not created.
-789 THE DATA TYPE OR OTHER
ATTRIBUTES FOR PARAMETER OR Programmer response
SQL VARIABLE name ARE NOT Check the triggered SQL statements in the trigger for
SUPPORTED IN THE ROUTINE any statement that is not listed in CREATE TRIGGER
(basic) (Db2 SQL) or SQL-procedure-statement (SQL
Explanation PL) (Db2 SQL), and remove the statement.
This error is issued for the following situations:
SQLSTATE
• A default value cannot be specified for a parameter
of type ARRAY. Only DEFAULT NULL can be explicitly 42987
specified if array-type-name is specified. Related reference
• A table parameter (TABLE LIKE) cannot be specified CREATE TRIGGER (basic) (Db2 SQL)
when adding or replacing a version of an existing SQL-procedure-statement (SQL PL) (Db2 SQL)
procedure with a CREATE OR REPLACE statement.
name -798 A VALUE CANNOT BE SPECIFIED
The name of the parameter or SQL variable. FOR COLUMN column-name
WHICH IS DEFINED AS
GENERATED ALWAYS
System action

Explanation Parts of exception-type, operation-type, data-type, and
position-number might not be returned to the SQL
When inserting or updating a row in a table, a value communication area, depending on where the error
was specified for a column that is defined with was detected.
GENERATED ALWAYS attributes, its value is not being
set with the DEFAULT keyword, and: exception-type
Indicates the type of error.
• Extended indicator variable values are not enabled.
Possible values for exception-type are:
• Extended indicator variable values are enabled, but
neither of the expected values DEFAULT (-5) or • FIXED POINT OVERFLOW
UNASSIGNED (-7) were provided. • DECIMAL OVERFLOW
column-name • ZERO DIVIDE
• DIVIDE EXCEPTION
GENERATED ALWAYS columns should not be specified • EXPONENT OVERFLOW
in the column list for an insert operation, or in the
SET clause for an update operation unless the keyword • INVALID OPERATION
DEFAULT is specified. • SUBNORMAL
• UNDERFLOW
System action • OVERFLOW
The statement cannot be processed. • OUT OF RANGE
operation-type
Programmer response Indicates the operation that was being performed
at the time of the error. Possible operation-type
Remove the column from the column list or SET
includes the following arithmetic operations:
clause, or specify DEFAULT as the column value.
• ADDITION
You can use the OVERRIDING USER VALUE clause on
an INSERT statement as a possible solution for this • SUBTRACTION
situation. • MULTIPLICATION
• DIVISION
SQLSTATE
• NEGATION
428C9
operation-type might also be one of the following
Related reference operations:
INSERT (Db2 SQL) • A built-in function
UPDATE (Db2 SQL)
• An aggregate function
-802 EXCEPTION ERROR exception- • Java conversion
type HAS OCCURRED DURING data-type
operation-type OPERATION ON The data types of the items being manipulated.
data-type DATA, POSITION
position-number Possible values for data-type include the following
data types:
Explanation • BIGINT
An exception error has occurred in the processing of • INTEGER
an SQL arithmetic function or arithmetic expression. • SMALLINT
The exception error occurred in one of the following • DECIMAL
areas:
• FLOAT
• In the SELECT list of an SQL SELECT statement.
The data type displayed in the message might
• In the search condition of a SELECT, UPDATE, indicate the data type of the temporary internal
MERGE, or DELETE statement. copy of the data, which can differ from the actual
• In the SET clause of the UPDATE operation. column or literal data type due to conversions by
• During the evaluation of an aggregate function. Db2.

position-number • One or more non-zero digits are lost because the
The position of the expression in a SELECT list if destination field in any decimal operation is too short
the error was in the SELECT list of an outer SELECT to contain the result.
statement. • A Java stored procedure or user-defined function
sets a decimal value in an output parameter
System action that has a precision or scale too small for
the value. operation-type is Java conversion. data-
The statement cannot be processed. In the case of type is DECIMAL. position-number indicates which
an insert or update operation, no data is updated parameter of the CALL statement or user-defined
or deleted. If the statement was a cursor-controlled function invocation is in error.
FETCH, the cursor will remain open unless the
exception occurred while processing an aggregate Any of the exception or overflow conditions can occur
function (indicated by operation-type of AGGREGATE during the processing of a built-in function. If the
FUNCTION), in which case the cursor will be closed. operation-type is FUNCTION, the error occurred while
If the cursor is closed, subsequent attempts to use processing either an input, intermediate, or final value.
that cursor without first doing an OPEN for it receive The exception can occur because the value of a
an SQLCODE -501. If the statement was a cursor- parameter is out of range.
controlled OPEN, the cursor will remain closed.
SQLSTATE
Programmer response 22012 if ZERO DIVIDE.
Examine the SQL statement to see if the cause of the 22003 if other than ZERO DIVIDE.
problem can be determined. The problem might be
data-dependent, in which case it will be necessary to -803 AN INSERTED OR UPDATED VALUE
examine the data that was being processed at the time IS INVALID BECAUSE THE INDEX
the error occurred. IN INDEX SPACE indexspace-name
CONSTRAINS COLUMNS OF THE
If the arithmetic expression in error was within the
TABLE SO NO TWO ROWS CAN
SELECT list of the outer SELECT statement, it is
CONTAIN DUPLICATE VALUES
advisable to include an indicator variable for all
IN THOSE COLUMNS. RID OF
expressions in the SELECT list. This allows processing
EXISTING ROW IS X record-id
to continue so that non-error column and expression
values can be returned.
Explanation
See the explanation of SQLCODE -405 for allowed
ranges of numeric data types. The table that is the object of the insert or update
operation is constrained to have unique values
If exception-type is FIXED POINT OVERFLOW,
in certain columns. Completion of the requested
operation-type is COLUMN FUNCTION, and the
operation would result in duplicate values.
function is COUNT(*), specify COUNT_BIG(*) instead.
indexspace-name
The name of a hash overflow index or the name of
Problem determination
the index space that contains the unique index that
A fixed point overflow can occur during any arithmetic enforces a primary key.
operation on BIGINT, INTEGER, or SMALLINT fields. record-id
A divide exception can occur on a decimal division The record ID of the row where the duplicate
operation when the quotient exceeds the specified values would exist.
data field size. A zero divide occurs on a division by When indexspace-name identifies a hash overflow
zero. index, the error occurred because a table with hash
An exponent overflow can occur when the result organization cannot have two rows with identical hash
characteristic of any floating-point operation exceeds key values.
127 and the result fraction is not zero, for example, If the index space is an XML index, the duplicate
the magnitude of the result exceeds approximately values can be caused by the values in the XML
7.2E+75. document or by the result of data type conversion and
A decimal overflow exception can occur under either of rounding.
the following circumstances: Otherwise, a primary key, unique constraint, or unique
index exists over one or more columns of the table.

The operation cannot be performed because one or Related reference
more values would have produced a duplicate key in SYSINDEXES catalog table (Db2 SQL)
the unique index or constraint.
-804 AN ERROR WAS FOUND IN THE
If a view is the object of the insert or update
APPLICATION PROGRAM INPUT
statement, the table that defines the view is
PARAMETERS FOR THE SQL
constrained. The update might also be caused by a
STATEMENT, REASON reason
delete operation of a parent row that cascades to a
dependent row with a delete rule of SET NULL.
Explanation
System action The call parameter list or the SQLDA is invalid.
The statement cannot be processed. • The call parameter list, which is created by the
precompiler, might be invalid if the application
Programmer response programmer has modified the output of the
precompiler, used a variable name beginning with
Examine the definitions for UNIQUE INDEX or the 'SQL' in the application program, or overwritten the
HASH key that is specified in the index space that call parameter list in some other way.
is identified by indexspace-name to determine the
• The SQLDA, which is created by the application
uniqueness constraint that is imposed. Refer to
program, has an invalid data type or data length.
SYSIBM.SYSINDEXES for the index space name and
the associated index name. • The value of SQLDABC is not consistent with the
value of SQLD.
Update operation
Verify that the specified operation is consistent The following is the list of reason codes:
with the uniqueness constraint. If this does not 01
indicate the error, examine the object table to Open issued for non-cursor.
determine the cause of the problem.
02
Insert operation Close issued for non-cursor.
Examine the object table to determine which
03
values violate the uniqueness constraint. If the
Prepare of EXECUTE IMMEDIATE.
INSERT statement contains a subquery, match the
contents of the table addressed by the subquery 04
and the contents of the object table to determine Statement is not recognized.
the cause of the problem. 05
Delete operation No statement string present.
Examine the index key columns in the table that 06
defines the index. These columns contain a foreign Bad SQLDA format in parameter list.
key, which when set NULL on a cascade delete
07
from the object table, causes the duplicate values.
SQLDA length is invalid.
Merge operation
08
Verify that the specified operation is consistent
Unrecognized input data type.
with the uniqueness constraint. If this does not
indicate the error, examine the object table to 09
determine the cause of the problem. In very Invalid length for input variable.
rare cases, the error can be caused by another 10
INSERT/UPDATE statement which modified the Invalid data length for output variable.
object table during the processing of MERGE
11
statement. Under such circumstances, examine
The value of SQLDABC is not consistent with the
your applications and make appropriate changes
value of SQLD.
to handle concurrency. For example, changing the
isolation level or running the MERGE statement 12
again might avoid the problem. Invalid input data pointer. If the error occurs in a
REXX application, a value might not have been set
for an input host variable or indicator variable.
SQLSTATE
13
23505 Invalid output data pointer.

14 01
SQLN has too many items for SQLDABC.
• The package name was not found because
15 there is no package list for the plan.
Input RDI pointer is invalid.
Problem determination: Query 2
16
Unrecognized output data type. Corrective action: Add the PKLIST option
with the appropriate package list entry to
17
the REBIND subcommand and rebind the
The value of the 7th byte of SQLDAID is not
application plan that is identified by plan-
consistent with the data types contained in the
name.
SQLDA. The SQLDA contains a LOB type host
variable, but the 7th byte of SQLDAID is not set 02
to '2' or greater to indicate that the extended The DBRM name dbrm-name did not match an
SQLVARs have been allocated. entry in the package list. Any of the following
18 conditions could be the problem:
An ARRAY SQLTYPE was specified in an SQLDA. BIND conditions
19 • The collection-id in the package list
Invalid program name. was not correct when the application
plan that is identified by plan-name was
System action bound.
The statement cannot be processed. Problem determination: Query 2

Corrective action: Correct the collection
System programmer response ID of the entry in the PKLIST option and
use the REBIND subcommand to rebind
Examine the application program for any of the errors the application plan that is identified by
noted under the explanation above. In general, the plan-name.
application programmer should not attempt to modify
the output of the precompiler. • The location-name in the package list
was not correct when the application
plan that is identified by plan-name was
SQLSTATE bound.
07002 Problem determination: Query 2
-805 PACKAGE Corrective action: Correct the location
NAME location-name.collection- name of the entry in the PKLIST option
id.dbrm-name.consistency-token and use the REBIND subcommand to
NOT FOUND IN PLAN plan-name. rebind the application plan that is
REASON reason-code identified by plan-name.
• The location-name in the
Explanation CURRENTSERVER option for the BIND
subcommand was not correct when the
An application program attempted to use a package
application plan that is identified by plan-
that was not found.
name was bound.
location-name.collection-id.dbrm-name.consistency-
token
The package that was not found. The collection- Corrective action: Correct the location
id is blank if the CURRENT PACKAGESET special name in the CURRENTSERVER option and
register was blank for the local program execution. use the REBIND subcommand to rebind
plan-name the application plan that is identified by
The name of the plan. plan-name.
reason-code Application conditions
A numeric value that indicates the reason for the • The CURRENT PACKAGESET special
failure. register was not set correctly by the
application.

When using SET CURRENT PACKAGESET if it refers to an object on a remote server, additional
= :HV, be sure to use the correct packages must be bound using BIND COPY. Whenever
encoding scheme, which must match the native SQL procedure is changed such that a
the :HV in subsystem parameter options. regeneration is needed, the additional package also
This statement does not require package needs to be bound with the copy option.
or DBRM bound into the plan, so it
uses the encoding scheme defined for System action
system. The same condition applies to
SET CURRENT PACKAGE PATH. The statement cannot be processed.
Corrective action: Set the CURRENT
PACKAGESET special register correctly. Programmer response
• The application was not connected to the Use the information that is provided for the reason-
proper location. code to resolve the problem.
Corrective action: Connect to the correct
location. Problem determination
03 The following queries aid in determining the problem.
The DBRM name that is identified by dbrm- Run these queries at the local location.
name matched one or more entries in the
Query 2: Display the entries in the package list for
package list and the search of those entries did
the plan
not find the package. Any of the conditions that
are listed for reason-code value 02 are possible SELECT LOCATION, COLLID, NAME
causes for reason-code value 03, as are the FROM SYSIBM.SYSPACKLIST
WHERE PLANNAME = 'plan-name';
following additional conditions:
• The DBRM of the version of the application If no rows are returned, then the plan was bound
program being executed was not bound. (A without a package list.
package with the same consistency token
Query 3: Display the CURRENTSERVER value
as that of the application program was not
specified on the BIND subcommand for the plan.
found.)
Problem determination: Query 4 SELECT NAME, CURRENTSERVER
FROM SYSIBM.SYSPLAN
WHERE NAME = 'plan-name';
Corrective action: Bind the DBRM of the
version of the application program to be
Query 4: Determine if there is a matching package in
executed into the collection that is identified
SYSPACKAGE
by collection-id.
• The incorrect version of the application If the package is remote, put the location name in
program is being executed. the FROM clause.
Corrective action: Execute the correct version If the collection-id value in the message is blank,
of the application program. The consistency use this version of the query:
token of the application program is the same
SELECT COLLID, NAME, HEX(CONTOKEN), VERSION
as the package that was bound. FROM location-name.SYSIBM.SYSPACKAGE
WHERE NAME = 'dbrm-name'
04 AND HEX(CONTOKEN) = 'consistency-token';
The package does not exist at the remote site,

If the collection-id value in the message is not
which is identified by the location-name value.
blank, use this version of the query:
SELECT COLLID, NAME, HEX(CONTOKEN), VERSION
blank FROM location-name.SYSIBM.SYSPACKAGE
The reason-code value is blank if the length of WHERE NAME = 'dbrm-name'
AND HEX(CONTOKEN) = 'consistency-token'
location-name is 16, the length of collection-id AND COLLID = 'collection-id';
is 18, and the length of dbrm-name is 8 due to
the length of SQLERRMT. If no rows are returned, the correct version of the
package was not bound.
In a native SQL procedure, if the affected SQL
statement follows a SET CURRENT PACKAGESET, SET
CURRENT PACKAGE PATH, or CONNECT statement, or

51002 The CONNECT semantics that apply to an application
process are determined by the first CONNECT
-807 ACCESS DENIED: PACKAGE statement executed (successfully or unsuccessfully)
package-name IS NOT ENABLED by the application process. One of the following rules
FOR ACCESS FROM connection- was violated:
type connection-name
• A type 2 CONNECT statement cannot be executed
after a type 1 CONNECT statement was executed.
Explanation
• A type 1 CONNECT statement cannot be executed
Access is denied for one of the following reasons: after a type 2 CONNECT statement was executed.
• It is disabled, either from the 'connection-type'
or from the 'connection-type' with the specific System action
'connection-name'.
• The attach library that you are using is from a
previous release of Db2 that does not support the
ENABLE and DISABLE options of the bind operation. Programmer response
The variables are: The probable cause of this error is that different
programs in the application process were precompiled
package-name
with different CONNECT options.
The package name (collection.package-id).
connection-type Ensure that the application process uses either type 1
One of the following: BATCH, DB2CALL, REMOTE, or type 2 CONNECT statements and then resubmit the
IMSBMP, IMSMPP, CICS, DLIBATCH, or UNKNOWN. job. The type of CONNECT to be used is a precompiler
option. The default is type 2 CONNECT.
connection-name
Name of the connection that is restricted. If all
connection names from a specific connection-type SQLSTATE
are restricted, this value is not specified. 08001
-811 THE RESULT OF AN EMBEDDED
System action SELECT STATEMENT OR A
The statement is not executed and the package is not SUBSELECT IN THE SET CLAUSE
allocated. OF AN UPDATE STATEMENT IS A
TABLE OF MORE THAN ONE ROW,
OR THE RESULT OF A SUBQUERY
System programmer response OF A BASIC PREDICATE IS MORE
One of the following: THAN ONE VALUE
• Rebind the package to enable it to execute with the
required connection type and name. Explanation
• Check the SYSPLSYSTEM or SYSPKSYSTEM catalog Execution of an embedded SELECT statement or a
table to find a connection from which the package subselect in the SET clause of an UPDATE statement
can be executed. has resulted in a result table that contains more than
• Correct the attach library. one row. Alternatively, a subquery contained in a basic
predicate has produced more than one value.
SQLSTATE
System action
23509
-808 THE CONNECT STATEMENT IS NOT
CONSISTENT WITH THE FIRST
CONNECT STATEMENT
Programmer response
Examine the syntax of the statement to ensure that
it contains the proper condition specifications. If the
statement syntax is correct, there might be a problem

with the data that is causing more than one row or Explanation
value to be returned when you do not expect it.
The application attempted to execute an SQL
statement that would result in updates to user data
SQLSTATE or to the subsystem catalog. This is prohibited for one
21000 of the following reasons:
-812 THE SQL STATEMENT CANNOT BE • The application is running as an IMS inquiry-only
PROCESSED BECAUSE A BLANK transaction.
COLLECTION-ID WAS FOUND • The application is an IMS, CICS, or RRSAF
IN THE CURRENT PACKAGESET application that is attempting to update data at
SPECIAL REGISTER WHILE a remote DBMS that does not support two-phase
TRYING TO FORM A QUALIFIED commit.
PACKAGE NAME FOR PROGRAM • The application is attempting to update data at
program-name.consistency-token multiple locations and one of the locations does not
USING PLAN plan-name support two-phase commit.
• A trigger defined with activation time BEFORE was
Explanation activated and its triggered action caused updates to
The last entry or the only entry in the package list the database.
for the plan contained an asterisk (*) as the value of • The application is executing with a package that was
the collection ID. The CURRENT PACKAGESET special bound with bind option DBPROTOCOL(DRDACBF),
register must be set to a nonblank collection ID to which enables package-based continuous block
form a qualified package name. fetch. When package-based continuous block fetch
is in effect, updates at a remote server are not
System action allowed.
• A CREATE TABLE statement for an accelerator-only
table was followed by a data change operation for an
accelerator-only table.
Programmer response
These SQL statements include INSERT, UPDATE,
Set the CURRENT PACKAGESET special register to the MERGE, DELETE, CREATE, ALTER, DROP, GRANT, and
correct collection ID, or ask your system administrator REVOKE.
to check the plan's package list for correctness.
If this error occurs in an application that System action
is running under the IBM Data Server
Driver for JDBC and SQLJ, you might
have too many concurrently open Statement,
PreparedStatement, or CallableStatement Programmer response
objects. Modify your application to decrease the If the application is running as an IMS inquiry-only
number of concurrently open objects, or run the transaction, see your IMS system programmer about
DB2Binder utility again with a larger -size parameter changing the inquiry-only status of the transaction
value to increase the number of packages that are under which your application is running.
available to the driver.
If the IMS, CICS, or RRSAF application is attempting
a remote update, either the application must be
SQLSTATE changed to run as a local application on the server
22508 DBMS, or the server DBMS must be upgraded to
support two-phase commit.
BE EXECUTED BECAUSE THE If the application is attempting to update data at
STATEMENT WILL RESULT IN multiple locations, either the application must be
A PROHIBITED DATA CHANGE changed, or all DBMSs involved must be upgraded to
OPERATION. support two-phase commit.
If the connection to the remote system is through
VTAM®, ensure that the VTAM APPL statement
specifies SYNCLVL=SYNCPT.

If the error is due to an invalid statement during a application program were not the result of the same
trigger activation, contact your system administrator to precompile operation.
correct the trigger definition.
This problem can occur in the following cases:
If the application package is bound with
• The application was precompiled, compiled, and
DBPROTOCOL(DRDACBF), take one of the following
linked, but was not bound.
actions:
• The application was precompiled and bound, but
• Rebind the package without the was not compiled and linked for the application
DBPROTOCOL(DRDACBF) option to disable package- program.
based continuous block fetch.
• The application was bound using a DBRM that
• Remove any SQL statements from the application resulted from a different precompile of the
that cause updates on the remote site, and prepare application program than that which produced the
the application again. object module that is linked into the application
module.
SQLSTATE
25000 System action
The APPL statement (Db2 Installation and
Migration) Programmer response
-818 THE PRECOMPILER-GENERATED Bind the application again, using the DBRM for the
TIMESTAMP x IN THE LOAD application program that matches the load module.
MODULE IS DIFFERENT FROM THE
BIND TIMESTAMP y BUILT FROM SQLSTATE
THE DBRM z
51003
Explanation Related tasks

Preparing an application to run on Db2 for z/OS
The timestamp that is stored in the application load (Db2 Application programming and SQL)
module does not match the timestamp that is stored
Related reference
in the plan or package. If the timestamps do not
match, the application is not allowed to process the BIND PACKAGE (DSN) (Db2 Commands)
SQL statement. BIND PLAN (DSN) (Db2 Commands)
x -819 THE VIEW CANNOT BE
The timestamp that was generated by the PROCESSED BECAUSE THE
precompiler. This timestamp is a Db2 internal LENGTH OF ITS PARSE TREE IN
timestamp. It does not have an external THE CATALOG IS ZERO
interpretation.
y Explanation
The bind timestamp. This timestamp is a Db2
internal timestamp. It does not have an external SYSIBM.SYSVTREE.VTREE is a varying-length string
interpretation. column that contains the parse trees of views. In
processing a view, the length control field of its parse
z
tree was found to be zero.
The name of the database request module
(DBRM).
System action
The SQL precompiler places timestamp y in the
DBRM and timestamp x in the parameter list in The statement cannot be processed.
the application program for each SQL statement.
At bind time, Db2 stores the DBRM timestamp for Programmer response
run time use. At run time, timestamp x for the
SQL statement being processed is compared with This is a system error. If you suspect an error in Db2,
timestamp y derived from the DBRM z at bind time. If you might need to report the problem. For information
the two timestamps do not match, the DBRM and the about identifying and reporting the problem, see
Collecting diagnostic data (Collecting data).

SQLSTATE SQLSTATE
58004 51004
-820 THE SQL STATEMENT CANNOT -840 TOO MANY ITEMS RETURNED IN
BE PROCESSED BECAUSE catalog- A SELECT, INSERT LIST, FROM
table CONTAINS A VALUE THAT IS MERGE, OR FROM UNNEST
NOT VALID IN THIS RELEASE
Explanation
Explanation
The number of items returned in the SELECT list,
A column of the indicated catalog table contains specified in an INSERT list, specified in a MERGE
a value that prevents further processing of an SQL statement, or returned from an invocation of UNNEST
statement. The meaning of the value is unknown to the exceeds the allowable maximum of 750.
release of Db2. If a fall back has occurred, the value is
probably the result of the use of new function prior to System action
the fall back.
System action
Programmer response
Determine whether all the information is actually
needed. For example, the number of items that are
Programmer response
returned by the SQL statement SELECT * FROM A, B, C
Verify that the statement refers to the intended tables is the sum of the number of columns in all three tables.
or views and that the problem is the result of a fall Not all column data might be needed.
back. If this is the case, the statement cannot be
Rewrite the SQL statement so that only the necessary
corrected because it depends on a function that is
items of information are returned, or break the SQL
not supported in the current release. If the problem
statement into two or more statements.
is not the result of a fallback, -820 is a system error.
If you suspect an error in Db2, you might need to
report the problem. For information about identifying SQLSTATE
54004
-842 A CONNECTION TO location-name
SQLSTATE ALREADY EXISTS
58004
Explanation
-822 THE SQLDA CONTAINS AN
One of the following situations occurred:
INVALID DATA ADDRESS OR
INDICATOR VARIABLE ADDRESS • A CONNECT statement identifies a location with
which the application process has a private
connection, using system-directed access.
Explanation
• SQLRULES(STD) is in effect and a CONNECT
The application program has placed an invalid address statement identifies an existing SQL connection.
in the SQLDA.
• A private connection, using system-directed access,
cannot be established because of an existing SQL
System action connection to that location.
The statement cannot be processed. • A CONNECT (type 2) request that includes the USER/
USING clause identifies an existing SQL connection.
Programmer response
System action
Correct the application program such that valid
addresses are placed in SQLDA. The statement cannot be processed.

Programmer response • If the location name is not the intended name,
correct it.
The correction depends on the error, as follows:
• If the location name does not identify an existing
• If the location name is not the intended name, SQL connection, replace the SET CONNECTION with
correct it. a CONNECT statement.
• If SQLRULES(STD) is in effect and the CONNECT • If RELEASE CURRENT was executed in the
statement identifies an existing SQL connection, unconnected state or the specified location name
replace the CONNECT with SET CONNECTION or does not identify an existing SQL or Db2 private
change the option to SQLRULES(Db2). connection, delete the RELEASE statement.
• If the CONNECT statement identifies an existing Correct the error in the application, rebind, the plan
private connection, destroy that connection (by using and resubmit the job.
the RELEASE statement in a previous unit of work)
before executing the CONNECT statement. If the SQL
statements following the CONNECT can be executed SQLSTATE
using system-directed access, an alternative solution 08003
is to change the application to use that method.
-845 A PREVIOUS VALUE EXPRESSION
• If system-directed access cannot be used, destroy
CANNOT BE USED BEFORE
the conflicting SQL connection (by using the
THE NEXT VALUE EXPRESSION
RELEASE statement in a previous unit of work)
GENERATES A VALUE IN THE
before executing the SQL statement that requires
CURRENT APPLICATION PROCESS
system-directed access. An alternative solution is
FOR SEQUENCE sequence-name
to change the application so that only application-
directed access is used.
• Destroy the connection (by using the RELEASE
Explanation
statement in a previous unik of work) before A PREVIOUS VALUE expression specified sequence
executing the CONNECT statement which includes sequence-name, but a value has not yet been
the USER/USING clause. generated for this sequence. A NEXT VALUE
Correct the error in the application, rebind the plan or expression must be issued in this application process
package, and resubmit the job. to generate a value for this sequence before a
PREVIOUS VALUE expression for the sequence can be
issued.
SQLSTATE
This error can also occur after a sequence has been
08002 dropped, and the DROP statement is rolled back.
-843 THE SET CONNECTION OR
RELEASE STATEMENT MUST System action
SPECIFY AN EXISTING
CONNECTION

Issue at least one NEXT VALUE expression for
One of the following rules was violated:
a sequence before issuing any PREVIOUS VALUE
• A SET CONNECTION statement must identify an expression for the same sequence in a connection.
existing SQL connection of the application process.
• A RELEASE statement must identify an existing SQLSTATE
connection of the application process.
51035
System action -846 INVALID SPECIFICATION OF AN

IDENTITY COLUMN OR SEQUENCE
The statement cannot be processed. OBJECT object-type object-name.
Programmer response
The correction depends on the error, as follows:

For an identity column or sequence, the specification The statement cannot be processed.
of an attribute in a CREATE or ALTER statement might
be invalid. Programmer response
This message is also issued if object-name identifies a
DB2_GENERATED_DOCID_FOR_XML column.
object-type SQLSTATE
The type of object.
42815
object-name
The name of the object. -867 INVALID SPECIFICATION OF A
reason-code ROWID COLUMN
by one of the following values: Explanation
1 For an ALTER TABLE or CREATE TABLE statement, the
The underlying data type of the identity column specification of a ROWID column might be invalid for
or sequence object is not supported. Identity one of the following reasons:
columns and sequence objects support the
following data types: SMALLINT, INTEGER, • A ROWID column can not be added to a temporary
BIGINT, and DECIMAL (or NUMERIC) with a table.
scale of zero. • The referential-constraint clause can not specify a
2 ROWID column as a column of a foreign key.
The value for START WITH, INCREMENT • A ROWID column can not be a column of a primary
BY, MINVALUE, MAXVALUE, or RESTART key.
WITH is outside the range for the data
• A ROWID column can not be a column in a table with
type of the identity column or sequence
an edit procedure that is defined with row attribute
object. If the sequence being altered
sensitivity.
is DSNSEQ_IMPLICITDB, the value for
MAXVALUE is outside the range between 1 and If more than one exchange is attempted consecutively,
60000, inclusive. then there must be a COMMIT between them. This
3 COMMIT is already required before DML can be done.
MINVALUE must be less than or equal to If a COMMIT is not done between exchanges, then a
MAXVALUE. -909 SQL code will be issued.
4
An invalid value was specified for CACHE. The System action
value must be an INTEGER with a minimum The statement cannot be processed.
value of 2.
An edit procedure that is defined with row
attribute sensitivity was specified for the Correct the syntax and resubmit the statement.
identity column.
6 SQLSTATE
An identity column was specified for a global
428C7
temporary table that was already defined
by a CREATE GLOBAL TEMPORARY TABLE Related reference
statement. This error could occur for a CREATE ALTER TABLE (Db2 SQL)
GLOBAL TEMPORARY TABLE statement, or an CREATE TABLE (Db2 SQL)
ALTER TABLE statement for a global temporary
table when there is an attempt to add an -870 THE NUMBER OF HOST
identity column to an existing global temporary VARIABLES IN THE STATEMENT IS
table that was already defined by a CREATE NOT EQUAL TO THE NUMBER OF
GLOBAL TEMPORARY TABLE statement. DESCRIPTORS

Explanation reference is not allowed. This error can occur for one
of the following reasons:
The number of host variables in the SQL statement
does not match the number of host variable • The definition of a new table is specified to be 'like'
descriptors. an existing view which references data from multiple
encoding schemes.
System action • The parent and child tables referenced in the
definition of a referential constraint containing one
The statement cannot be processed. or more non-numeric columns are encoded with
different encoding schemes.
Programmer response • The definition of a materialized query table uses a
different encoding scheme than the containing table
Correct the application program. The most likely cause
space.
of this problem is a missing colon before a host
variable. • The SELECT statement references data that is
encoded in multiple encoding schemes, and also
contains an INSERT, DELETE, UPDATE, or MERGE
statement that references data that is encoded with
If the SQL statement is bound locally, descriptors a single encoding scheme.
are built by the Db2 precompiler. For a remote SQL • An INSTEAD OF trigger is created on a view that
statement, descriptors are built by DDF and are references multiple encodings or CCSIDs.
passed in the array SQLSTTVRB.
• The GRAPHIC or VARGRAPHIC built-in function, or
CAST specification, was invoked with numeric data
SQLSTATE for the first argument and the containing statement:
58026 – is a multiple encoding scheme statement but
the application encoding scheme is not set
-872 A VALID CCSID HAS NOT YET
to Unicode, or a CAST specification does not
BEEN SPECIFIED FOR THIS
explicitly specify Unicode in the CCSID clause for
SUBSYSTEM
the target data type.
– is a single encoding scheme statement and the
Explanation
statement references tables or views that are not
A valid CCSID was not specified on either the ASCII Unicode.
CCSID, EBCDIC CCSID, or UNICODE CCSID subsystem
For information about how to determine whether
parameter on installation panel DSNTIPF.
a context supports Unicode data, see Determining
the encoding scheme and CCSID of a string
System action (Introduction to Db2 for z/OS).
System action
Contact your system administrator to have the
necessary CCSID defined for your system. Programmer response
SQLSTATE
51032 SQLSTATE
-873 THE STATEMENT REFERENCED 53090
DATA ENCODED WITH DIFFERENT
-874 THE ENCODING SCHEME
ENCODING SCHEMES OR CCSIDS
SPECIFIED FOR THE object-type
IN AN INVALID CONTEXT
MUST BE THE SAME AS THE
CONTAINING OR TARGET TABLE
Explanation SPACE OR OTHER PARAMETERS
The SQL statement references data from multiple
encoding schemes or CCSIDs in a context where the

Explanation • FL 508 For an ALTER TABLESPACE statement with
a MOVE TABLE clause, specify a target table space
A CCSID clause was incorrectly specified in one of the that has the same CCSID attributes as the source
following situations: table space.
• In a CREATE TABLE or ALTER TABLE statement:
– CCSID ASCII was specified, and the containing SQLSTATE
table space is EBCDIC or UNICODE. 53091
– CCSID EBCDIC was specified, and the containing
-875 operand CANNOT BE USED WITH
table space is ASCII or UNICODE.
THE ASCII DATA REFERENCED
– CCSID UNICODE was specified, and the containing
table space is ASCII or EBCDIC.
Explanation
• In a fullselect that creates a table, the following
items were not the same: ASCII data was referenced in one of the following
situations:
– The encoding scheme of the result table of the
fullselect • A LIKE predicate refers to a mixed data column in an
ASCII table. The LIKE predicate is not supported for
– The encoding scheme in the CCSID clause (if
mixed ASCII data.
specified)
• A VARGRAPHIC function was specified for a column
– The encoding scheme of the target table space
in an ASCII table. The VARGRAPHIC function is not
• In a CREATE TYPE statement for an array, the CCSID supported for ASCII data.
clause was specified for the data type of array
elements and for the data type of the index. The
CCSID specifications for the array elements and for
System action
the index were not the same. The statement cannot be processed.
• FL 508 In an ALTER TABLESPACE statement with
a MOVE TABLE clause, the CCSID attributes of the Programmer response
table space that is being altered (the source table
space) were not the same as the CCSID attributes of Correct the SQL statement.
the target table space.
SQLSTATE
System action 42988
The statement cannot be processed. -876 object-type CANNOT BE CREATED
OR ALTERED, REASON reason-code
Programmer response
Correct the SQL statement in one of the following Explanation
ways: The object in the SQL statement cannot be created or
• For a CREATE TABLE or ALTER TABLE statement, altered.
make the CCSID value in the CREATE TABLE or object-type
ALTER TABLE statement the same as the CCSID of The type of object that could not be created or
the containing table space. altered:
• For a fullselect that creates a table, make all of the TYPE 1 INDEX
following items the same: The object that the SQL statement attempted
– The encoding scheme of the result table of the to create is a type 1 index.
fullselect INDEX
– The encoding scheme in the CCSID clause (if The object that the SQL statement attempted
specified) to create is an index.
– The encoding scheme of the target table space TABLE
The object that the SQL statement attempted
• For a CREATE TYPE statement for an array, make the
to create or alter is a table.
CCSID specification for the array elements and for
the index the same.

TABLESPACE controlled partitioned table with an ALTER
The object that the SQL statement attempted TABLE statement.
to alter is a table space.
reason-code System action
A value that indicates the reason for the failure.
TABLE DEFINED AS ASCII
The underlying table is defined as ASCII. Only
type 2 indexes are supported for ASCII tables.
Programmer response
PIECESIZE IS NOT VALID Correct the SQL statement for the object that is being
PIECESIZE is only valid for non-partitioned created or altered.
indexes.
COLUMN NAME IN EBCDIC EXCEEDS 18 BYTES, SQLSTATE
OR THE CONVERSION FROM UNICODE TO 53092
EBCDIC FAILED
The table that is being created or altered Related reference
has an edit procedure that is defined with PREVENT_NEW_IXCTRL_PART in macro
row attribute sensitivity, a field procedure, or DSN6SPRM (Db2 Installation and Migration)
a validation procedure. In these cases, the PREVENT ALTER LIMITKEY field
column name in EBCDIC cannot exceed 18 (PREVENT_ALTERTB_LIMITKEY subsystem
EBCDIC bytes in length, or the conversion of a parameter) (Db2 Installation and Migration)
column name from UNICODE to EBCDIC failed.
BASE TABLESPACE IS LOG YES, LOB -877 CCSID ASCII OR CCSID UNICODE
TABLESPACE IS LOG NO IS NOT ALLOWED FOR THIS
A spatial index cannot be created because DATABASE OR TABLE SPACE
the following table spaces have the indicated
attributes: Explanation
• The table space that contains base table has The database or table space specified is required to be
the LOG YES (or LOGGED) attribute. in EBCDIC.
• The LOB table space that stores the LOB
column has the LOG NO (or NOT LOGGED) System action
attribute.
CONTAINS A SPATIAL COLUMN
The LOG YES attribute of a LOB table space
cannot be altered to LOG NO if an index Programmer response
depends on the LOB column. Remove the CCSID ASCII or CCSID UNICODE clause
The LOG NO attribute of a table space cannot from the statement.
be altered to LOG YES if it contains a table with
an index that depends on a LOB column of the SQLSTATE
table.
53093
6
The value of one of the following subsystem -878 THE explain-object USED FOR
parameters disallowed the definition of an EXPLAIN MUST BE ENCODED IN
index-controlled partitioned table: UNICODE. IT CANNOT BE IN ASCII
PREVENT_NEW_IXCTRL_PART OR EBCDIC.
The value of the PREVENT INDEX PART
CREATE subsystem parameter disallowed Explanation
the creation of an index-controlled
partitioned table with a CREATE TABLE An EXPLAIN table object was encoded in the wrong
statement. format. It must be encoded in Unicode for use with
EXPLAIN.
PREVENT_ALTERTB_LIMITKEY
The value of the PREVENT ALTER LIMITKEY explain-object
subsystem parameter disallowed the The name of the explain table object.
alteration of the limit key of an index-

System action even though the keywords FOR MIXED DATA do not
appear in the failing statement. This situation occurs
The statement was not executed. when the MIXED value in the application defaults
module is YES. In this case, the default subtype for
Programmer response the character types is FOR MIXED DATA.
Migrate the current release format EXPLAIN tables to
UNICODE for the current schema. System action
SQLSTATE
-879 CREATE or ALTER STATEMENT Contact your system administrator to properly set up
FOR object-name CANNOT the installation options, or change the data types of
DEFINE A COLUMN, TYPE, the elements in columns in your CREATE or ALTER
VARIABLE, FUNCTION OR STORED statement.
PROCEDURE PARAMETER AS
MIXED OR GRAPHIC WITH SQLSTATE
ENCODING SCHEME encoding-
scheme 53095
-880 SAVEPOINT savepoint-name DOES
Explanation NOT EXIST OR IS INVALID IN THIS
CONTEXT
A CREATE or ALTER TABLE statement or SQL variable
declaration for object-name attempted to define a
column, distinct type, or parameter of a user-defined Explanation
function or stored procedure as mixed data or graphic The RELEASE TO SAVEPOINT or ROLLBACK TO
when the system does not have an appropriate CCSID SAVEPOINT statement does not identify a savepoint
defined for the encoding-scheme encoding scheme. that exists.
• A CREATE TYPE statement cannot define a distinct
type, on EBCDIC or ASCII data, with a source System action
type of character FOR MIXED DATA, or GRAPHIC,
VARGRAPHIC, or DBCLOB, when the MIXED DATA Db2 does not process the statement.
installation option is set to NO.
• A CREATE TYPE statement for an array type cannot Programmer response
be defined with EBCDIC or ASCII data, and with a Correct the statement to use a valid savepoint name.
data type for the array elements that is character
FOR MIXED DATA, GRAPHIC, VARGRAPHIC, or
DBCLOB, when the MIXED DATA installation option SQLSTATE
is set to NO. An associative array type cannot be 3B001
defined with EBCDIC or ASCII data, and with a data
type for the array index that is character FOR MIXED -881 A SAVEPOINT WITH NAME
DATA, when the MIXED DATA installation option is savepoint-name ALREADY EXISTS,
set to NO. BUT THIS SAVEPOINT NAME
CANNOT BE REUSED
• A CREATE FUNCTION or CREATE PROCEDURE
statement cannot define a parameter or specify
a RETURNS data type, for ASCII or EBCDIC Explanation
data, as character FOR MIXED DATA, GRAPHIC,
The SAVEPOINT statement uses the same savepoint
VARGRAPHIC, or DBCLOB, when the MIXED DATA
name as another savepoint, and it cannot be created
installation option is set to NO.
because at least one of the savepoints was defined
This error occurs only when the encoding scheme with the UNIQUE clause to indicate that the name
that is in use is EBCDIC or ASCII. The MIXED DATA cannot be reused within the transaction.
installation option does not affect Unicode data.
This error can occur when the a column, type, variable,
or parameter is defined as character FOR MIXED DATA,

The statement is not executed and a new savepoint is It is possible that no response is required because
not set. The old savepoint still exists. checking for -900 is one way of detecting the
unconnected state. If this error is the result of another
Programmer response situation, the logic of the application program must be
changed.
Correct the statement. Either use a different savepoint
name, or omit the UNIQUE clause if the other
SQLSTATE
savepoint was created without the UNIQUE clause and
your intention is to reuse that savepoint name. 08003
Related concepts
SQLSTATE Connection management (Introduction to Db2
3B501 for z/OS)
Connection management (Introduction to Db2
-882 SAVEPOINT DOES NOT EXIST for z/OS)
Connections (Introduction to Db2 for z/OS)
A ROLLBACK TO SAVEPOINT statement was specified Statements (Db2 SQL)
without a savepoint name to rollback to the last active
savepoint, but no savepoint exists. -901 UNSUCCESSFUL EXECUTION
CAUSED BY A SYSTEM ERROR
THAT DOES NOT PRECLUDE
System action THE SUCCESSFUL EXECUTION OF
The statement cannot be processed. SUBSEQUENT SQL STATEMENTS

Correct the application logic to either set a savepoint A system error occurred that prevented successful
or to not attempt to rollback to a savepoint. execution of the current SQL statement.
Multiple forms: This message has two forms. The
SQLSTATE form that is shown above applies if the SQL statement
is not a query that was sent to an accelerator server.
3B502 The following form applies if the SQL statement is a
-900 THE SQL STATEMENT CANNOT query that was sent to an accelerator server:
BE EXECUTED BECAUSE THE UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM
APPLICATION PROCESS IS NOT ERROR THAT DOES NOT PRECLUDE THE SUCCESSFUL
CONNECTED TO A SERVER EXECUTION OF SUBSEQUENT SQL STATEMENTS
accelerator-info
Explanation accelerator-info
A previous failure has placed the application process An error message that was returned by the
in the unconnected state. An unsuccessful request accelerator server.
to switch the user in a trusted connection can cause If the SQL statement is not a query that was sent to
the connection to go into an unconnected state. The an accelerator server, possible causes for this error
only SQL statements that can be successfully executed include:
from the unconnected state are CONNECT, COMMIT,
ROLLBACK, and local SET statements. • Statement length: The length of the SQL statement
is either less than 0 or greater than the permitted
maximum length for a statement.
System action
• Distributed commit processing: Distributed commit
The statement cannot be processed. processing encountered an error. All servers in the
unit of work that support distributed two-phase
commit back out the unit of work. If a server that
does not support distributed two-phase commit has
updates in the unit of work, that server must be

queried to determine if its updates were committed initiated by the Db2 subcomponent involved in
or backed out. the error.
• Incomplete post-processing work: The transaction
-902 POINTER TO THE ESSENTIAL
is aborted and commit failed. Typical causes for
CONTROL BLOCK (CT/RDA) HAS
incomplete post-processing include:
VALUE 0, REBIND REQUIRED
– An update that changes the partition of a row
– Resource availability Explanation
– The existence of held cursors Pointer to the essential control block, either the CT
– Violations of uniqueness constraints or the RDA, is zeros. This precludes the successful
execution of the current SQL statement, as well as any
If the SQL statement is a query that was sent to an
subsequent SQL statements.
accelerator server, the error is returned because the
accelerator server could not execute the query.
System action
System action The statement cannot be processed. The application
program is not permitted to issue additional
The statement cannot be processed. A X'04E' abend
SQL statements. For example, a recovery routine
might be requested for the application. The application
associated with the application program may not issue
program can have a recovery routine to recover from
additional SQL statements.
such an abend and can retry SQL statements.
The error does not prevent successful execution of
Programmer response
further SQL statements.
Rebind the failing application program and try again. If
Programmer response the problem persists, examine your DBRM and make
sure it matches your program.
If an abend occurred, notify the system programmer
for analysis of the abend that caused this return
SQLSTATE
code. Even if an abend occurred, an application
program receiving this return code can retry and is not 58005
prohibited from executing further SQL statements.
-904 UNSUCCESSFUL EXECUTION
If the error occurred during a commit, examine CAUSED BY AN UNAVAILABLE
any detailed resource unavailable information that RESOURCE. REASON reason-code,
is posted to the system operator console or in the TYPE OF RESOURCE resource-type,
system services address space (ssnmMSTR) job log to AND RESOURCE NAME resource-
determine if a resource unavailable problem prevented name
commit post-processing from completing.
If the error occurred for a query that was sent to an Explanation
accelerator server, check whether the SQL statement
The SQL statement could not be executed because a
contains a logical error. An example of a logical error in
required resource was not available.
an SQL statement is a division operation that results in
division by 0. If you determine that your application is reason-code
not the source of the error, contact IBM Support, and The Db2 reason code value that indicates the
provide the value in the accelerator-info token. reason for the failure. For explanations of reason
SQLSTATE 373.
resource-type and resource-name
58004 The type and name of the resource that the
Related reference message identifies. For an explanation of resource-
Db2 abend completion codes (X'04E' and type and resource-name values, see Resource
X'04F) types (Db2 Messages).
X'04E' and X'04F' system abend completion When resource-type is 402, the value of resource-name
codes identify internal errors encountered is the z/OS Security Server return and reason codes for
during Db2 operation, diagnostic information for the unavailable resource.
problem determination, and subsystem actions

When reason-code is 00E7000E and resource-type is (limit-amount2 SERVICE UNITS)
00001080, SQLCODE -904 was issued by IBM Db2 DERIVED FROM limit-source
Analytics Accelerator for z/OS, and resource-name is
message text from the accelerator that indicates the Explanation
cause of the failure.
The execution of the SQL statement was terminated
because a resource limit was exceeded.
System action
resource-name
The SQL statement cannot be processed.
The name of the resource whose limit was
If the SQL statement being processed was a cursor exceeded. It is also the name of the column in
FETCH, Db2 closes the cursor. Subsequent attempts the Db2 table from which the limit was derived.
to use that cursor without first opening it receive an The resource-name can be ASUTIME, which is the
SQLCODE -501. number of CPU seconds permitted for each SQL
statement.
Programmer response limit-amount1
The maximum number of CPU seconds permitted
Collect a listing of the SYSLOG data set for the period
of time that spans the failure. Search the SYSLOG data limit-amount2
set for messages that are related to the error. The maximum number in service units permitted
limit-source
Verify the identity of the resource that was not
The source used to derive the limit-amount: the
available. To determine why the resource was
name of a resource limit specification table, a
unavailable, refer to the specified reason-code.
system parameter, or the SYSIBM.SYSROUTINES
If resource-name identifies the optimum buffer pool, catalog table. If the source is a system parameter,
either define the buffer pool with that name or create the resource limit specification table did not
the table in a table space that is defined with that contain an applicable entry or an error occurred
buffer pool. while accessing the table.
If SQLCODE -904 was issued by IBM Db2 Analytics
Accelerator for z/OS, contact IBM Support for IBM Db2 System action
Analytics Accelerator for z/OS, and provide them with
If the limit-source was a resource limit specification
the resource-name message text.
table or a system parameter, the execution of this SQL
statement is terminated.
SQLSTATE
In the case of a routine exceeded ASUTIME threshold,
57011 the current transaction is rolled back to the previous
commit point. The thread is placed into a must
Related concepts
rollback state, and no SQL statements can be
Db2 reason codes processed before a ROLLBACK is issued.
Reason codes are typically presented as a value
in a message that Db2 issues. The reason codes A trace record containing more detailed information
provide specific details about the circumstances about this failure is generated. If an SQL cursor is
of a particular instance of the message. associated with the failed instruction, its position is
unchanged and a CLOSE or PREPARE statement can
Related reference be issued. If any other operation is attempted with
z/OS Security Server RACROUTE Macro the cursor, it cannot be executed and SQLCODE -905
Reference is returned. If there is no cursor, this statement was
Related information rolled back.
Resource types (Db2 Messages)
-501 Programmer response
THE CURSOR IDENTIFIED IN A FETCH OR
CLOSE STATEMENT IS NOT OPEN Determine why this SQL statement or stored
procedure took so long and take appropriate action.
-905 UNSUCCESSFUL EXECUTION DUE Consider simplifying the SQL statement, restructuring
TO RESOURCE LIMIT BEING tables and indexes, or contacting the installation
EXCEEDED, RESOURCE NAME group responsible for maintaining the resource limit
= resource-name LIMIT = specification tables.
limit-amount1 CPU SECONDS

If the limit-source was a resource limit specification SQLSTATE
table or a system parameter, the application program
that receives this return code can execute additional 51005
SQL statements. -907 AN ATTEMPT WAS MADE TO
If SQLCODE -905 is issued in response to a statement MODIFY THE TARGET TABLE,
that is monitored by the resource limit facility, increase table-name, OF THE MERGE
the ASUTIME value that is specified for the routine in STATEMENT BY CONSTRAINT OR
the resource limit table. TRIGGER trigger-name.
57014 The MERGE statement caused a constraint or trigger to
activate. The trigger attempted to update, insert into or
Related tasks delete from the target table or a table within the same
Limiting resources for a stored procedure (Db2 table hierarchy of the MERGE statement. This is not
Performance) allowed.
Setting limits for system resource usage
table-name
by using the resource limit facility (Db2
The name of the target table of the MERGE
Performance)
statement.
Related information
trigger-name
00E70123
The name of the trigger that attempted to modify
the target table.
BE EXECUTED BECAUSE THIS
FUNCTION IS DISABLED DUE TO A System action
PRIOR ERROR

Execution of the SQL statement failed because the
Change the MERGE statement to remove the operation
requested function had been disabled by a prior error.
that causes the constraint or trigger to activate, or
This situation can arise if the application program has
alter the table that has the constraint or trigger to
intercepted an abend (for instance, by an ON ERROR
remove the reference to the target table.
condition in a PL/I program) and continued to execute
SQL statements. This situation may also arise if a Db2
CICS transaction encountered a create thread error SQLSTATE
yet continued to issue SQL requests without issuing a
27000
SYNCPOINT ROLLBACK first.
-908 bind-type ERROR USING auth-id
System action AUTHORITY. BIND, REBIND OR
AUTO-REBIND OPERATION IS NOT
The statement cannot be processed. ALLOWED

In general, an application program should terminate For BIND and REBIND, the indicated authorization
upon receipt of this return code. All subsequent ID is not allowed to perform the indicated bind-
attempts by the application to execute other SQL type against a plan or package. An entry in the
statements will also fail with the same return code. resource limit specification table (RLST) prohibits
In the case of a Db2 CICS transaction, if the binding and rebinding by this authorization ID, or
SQLERRP field in the SQLCA contains the module all authorization IDs. For AUTO-REBIND, the system
name DSNCEXT1, the transaction may issue a parameter controlling AUTO-REBIND operations is set
SYNCPOINT ROLLBACK and continue processing. If to disallow AUTO-REBIND.
the transactions chooses to ROLLBACK and continue
bind-type
processing, it must be capable of correcting the
Type of bind operation (BIND, REBIND or AUTO-
situation that caused the create thread error to occur
REBIND).
originally.

auth-id statement after the EXCHANGE statement and
Authorization ID of the invoker of the BIND before accessing the table.
subcommand or primary authorization ID of the
invoker of the plan for AUTO-REBIND operations. SQLSTATE
57007
System action
Related tasks
The plan or package is not bound.
Exchanging data between a base table and
clone table (Db2 Administration Guide)
System programmer response Related reference
If the indicated authorization id should be allowed EXCHANGE (Db2 SQL)
to bind, change the entry in the active RLST table.
If AUTO-REBIND operations are disabled, rebind the -910 THE SQL STATEMENT CANNOT
package before reexecuting the package. ACCESS AN OBJECT ON WHICH
UNCOMMITTED CHANGES ARE
PENDING
SQLSTATE
23510 Explanation
-909 THE OBJECT HAS BEEN DELETED The application program attempted to access an
OR ALTERED object that has been modified and the changes have
not yet been committed. This error is issued in the
Explanation following situations:
The application program has performed one of the • An application program issues a DROP, ALTER,
following actions: CREATE, or RENAME statement against an object,
and then attempts to access that object before the
• Dropped or altered a table and then accessed it.
operation is complete.
• Dropped or altered an index and then accessed the
• An application program issues an ALTER or CREATE
table on which the index was defined.
statement, and an INSERT, UPDATE, DELETE,
• Executed the EXCHANGE statement on a table more MERGE, or SELECT statement is processed for the
than once without executing a COMMIT statement same object in the same commit scope.
between consecutive EXCHANGE statements.
• An application program issues a CREATE TABLE
• Executed the EXCHANGE statement on a table and statement and an ALTER TABLE statement that
then accessed it. creates a new table space version in the same
commit scope.
System action • An application program issues a DROP, ALTER,
CREATE, or RENAME statement against an object,
and then attempts to access that object using
an INSERT, UPDATE, DELETE, MERGE, or SELECT
System programmer response statement before the DROP, ALTER, CREATE, or
RENAME statement completes.
Correct the application program in one of the following
ways:
System action
• Do not drop or alter a table, and then access it in the
same application program. The statement cannot be processed.
• Do not drop or alter an index, and then access the
table on which it is defined in the same application Programmer response
program.
Modify the logic of the application program, other than
• If the application program contains consecutive the logic for DROP, so that a COMMIT (or the IMS
EXCHANGE statements for a table, include a or CICS equivalent) is executed between the data
COMMIT statement between the EXCHANGE definition statement and the failing SQL statement,
statements. or between the data manipulative statement and the
• If the applications contains an EXCHANGE statement data definition statement. In cases where open held
and then accesses the table, add a COMMIT

cursors are associated with the failing SQL statement, A long-running application, or an application that is
the cursor must be closed prior to COMMIT. likely to encounter a deadlock, should (if possible)
issue frequent COMMIT commands. This can lessen
For DROP, the logic of the application program should
the possibility of a deadlock occurring. See message
be modified so that no attempt is made to access an
DSNT376I for other possible ways to avoid future
object after the DROP has been executed. Attention:
deadlocks or timeouts. On receipt of the SQLCODE
DROP includes cases when rollback to a savepoint
-911, the application should, in general, terminate.
includes rolling back to a CREATE.
SQLSTATE
SQLSTATE
40001
57007
Related concepts
-911 THE CURRENT UNIT OF WORK
Lock contention, suspension, deadlock, and
HAS BEEN ROLLED BACK DUE TO
DEADLOCK OR TIMEOUT. REASON timeout (Db2 Performance)
reason-code, TYPE OF RESOURCE Related tasks
resource-type, AND RESOURCE Improving concurrency (Db2 Performance)
NAME resource-name Programming for concurrency (Db2
Performance)
Explanation Related information
DSNT500I (Db2 Messages)
The current unit of work was the victim in a deadlock,
or experienced a timeout, and had to be rolled back. DSNT376I (Db2 Messages)
00C90088
reason-code
The Db2 reason code value that indicates the 00C9008E
codes, see Part 2, “Db2 reason codes,” on page -913 UNSUCCESSFUL EXECUTION
373. CAUSED BY DEADLOCK OR
TIMEOUT. REASON CODE reason-
resource-type and resource-name code, TYPE OF RESOURCE
The type and name of the resource that the resource-type, AND RESOURCE
message identifies. For an explanation of resource- NAME resource-name
type and resource-name values, see Resource
Explanation
Attention: The changes associated with the
unit of work must be entered again. The application was the victim in a deadlock or
experienced a timeout. The reason code indicates
SQLERRD(3) also contains the reason-code which whether a deadlock or timeout occurred.
indicates whether a deadlock or timeout occurred. The
most common reason codes are: reason-code
The Db2 reason code value that indicates the
• 00C90088 - deadlock reason for the failure. For explanations of reason
• 00C9008E - timeout codes, see Part 2, “Db2 reason codes,” on page
373.
The changes associated with the unit of work must be
entered again. resource-type and resource-name
The type and name of the resource that the
message identifies. For an explanation of resource-
System action type and resource-name values, see Resource
The statement cannot be processed. The application is types (Db2 Messages).
rolled back to the previous COMMIT.
System action
Programmer response The statement cannot be processed. If the SQL
Collect a listing of the SYSLOG data set for the period statement being executed was a cursor FETCH, Db2
of time that spans the failure. Search the SYSLOG data closes the cursor.
set for messages that are related to the error.

SQLERRD(3) also contains the reason-code value Problem determination
which indicates whether a deadlock or timeout
occurred. The most common reason codes are: Inspect the SQLCODES issued for the SQL statements
of the package.
• 00C90088 - deadlock
• 00C9008E - timeout SQLSTATE
42969
Programmer response
Collect a listing of the SYSLOG data set for the period
BE EXECUTED BECAUSE A
of time that spans the failure. Search the SYSLOG data
CONNECTION HAS BEEN LOST
set for messages that are related to the error.
The application should either commit or roll back to Explanation
the previous COMMIT. Then, generally, the application
should terminate. See message DSNT376I for possible Execution of the SQL statement failed because a
ways to avoid future deadlocks or timeouts. communications link between the local Db2 and at
least one remote server no longer exists. A previous
failure caused this condition.
SQLSTATE
57033 System action
Related concepts In the IMS and CICS environments, all SQL statements
Lock contention, suspension, deadlock, and are rejected until the rollback occurs. In the other
timeout (Db2 Performance) environments, all SQL statements other than a static
Related tasks ROLLBACK are rejected until a static ROLLBACK is
Improving concurrency (Db2 Performance) executed.
Programming for concurrency (Db2
Performance) Programmer response
Related information
In general, an application program should issue a
DSNT500I (Db2 Messages) static ROLLBACK. Attempts by the application to issue
DSNT376I (Db2 Messages) SQL statements other than static ROLLBACK might fail.
00C90088 Once the static ROLLBACK is issued, the application
00C9008E can resume execution.
SQLERRP contains the name of the module that
-917 BIND PACKAGE FAILED detected the previous failure and placed the
application in the must-abort state.
Explanation
An error has occurred which prevents the package SQLSTATE
from being created. This SQLCODE can be issued 51021
during bind or commit processing.
-919 A ROLLBACK OPERATION IS
REQUIRED
System action
The bind fails and the package is not created. If issued Explanation
during commit processing, all changes to the database
are rolled back. If issued during bind processing, The unit of work was placed in a state where a
only package creation fails. Other changes within the rollback operation is required. This can happen for the
logical unit of work are committable. following reasons:
• An SQL statement updated a distributed database
Programmer response server, but the database server can be used only for
read-only operations. Either updates are currently
Correct the cause of the problem and try again. restricted to servers that support distributed two-
phase commit and this application server does not
support distributed two-phase commit, or updates
are restricted to a single server that does not

support distributed two-phase commit and this reason-code
application server is not that server. The Db2 reason code associated with authorization
failure
The unit of work must be terminated by a rollback
operation because the update made (but not
committed) at the application server cannot be System action
committed consistently with other current or future
The statement cannot be processed. The connection
updates made to this distributed unit of work.
to Db2 is not established.
• An abend occurred during the execution of a stored
procedure, or a restricted SQL statement was issued
from a stored procedure.
Programmer response
• An abend occurred during the execution of a If error-type is 'USER AUTHORIZATION', the
function, or a restricted SQL statement was issued authorization-ID specified to Db2 through your
from a function. attachment facility is not valid for Db2. Contact the
system programmer or your CICS, IMS, or TSO system
• The unit of work is part of a Global Transaction, and administrator.
another unit of work in the Global Transaction has
initiated a ROLLBACK. All units of work in the Global If error-type is 'PLAN ACCESS', then the authorization
Transaction must now ROLLBACK. ID associated with this connection is not authorized
to use the specified plan name or the specified plan
name does not exist. See your system administrator.
System action
If error-type is 'DUPLICATE EXIT', then you requested a
In the IMS and CICS environments, all SQL statements
duplicate exit.
are rejected until the rollback occurs. In the other
environments, all SQL statements other than a static If error-type is 'INSTALLATION ERROR', a connection
ROLLBACK are rejected until a static ROLLBACK is or sign-on exit denied your request. See your system
executed. programmer.
If error-type is 'CONNECT', an SQL CONNECT request
Programmer response failed to connect to the local Db2 with USER/USING
specified. See the reason code for a description of
Correct the application, function, or stored procedure,
the failure. The application program has been placed
rebind it, and resubmit the job.
in the connectable and unconnected state. The only
SQLERRP contains the name of the module that SQL statements that can be successfully completed
detected the previous failure and placed the in this state are CONNECT, COMMIT, ROLLBACK, and
application in the must-abort state. local SET statements. Any attempt to execute other
SQL statements will result in an error (SQLCODE -900).
SQLSTATE Any attempts to issue SQL statements following the
-922 SQLCODE when error-type is not Connect cause
56045
unpredictable results.
-922 AUTHORIZATION FAILURE: error-
type ERROR. REASON reason-code SQLSTATE
42505
Explanation
Related concepts
Authorization failed because of the error indicated by
error-type Db2 reason codes
error-type in a message that Db2 issues. The reason codes
The types of authorization failure: provide specific details about the circumstances
• User authorization of a particular instance of the message.
• Plan access Related information
• Duplicate exit requested -900
• Installation error
• Connect

THE SQL STATEMENT CANNOT BE EXECUTED systems (for example, IMS or CICS) the plan can be
BECAUSE THE APPLICATION PROCESS IS NOT executed.
CONNECTED TO A SERVER
If the condition is "CICS attachment not up", then
-923 CONNECTION NOT ESTABLISHED: NAME indicates the Db2 subsystem that is not
DB2 condition REASON reason- available. The reason-code indicates the reason the
attachment is not available.
code, TYPE resource-type, NAME
resource-name If the condition is "CICS entry disabled", then NAME
indicates the entry that is disabled.
Explanation
The connection to Db2 failed for the reason indicated
System action
by condition. The statement cannot be processed. The connection
reason-code to Db2 is not established.
reason for the failure. For explanations of reason Programmer response
373. If the connection failed because either Db2 or a
required database, table space, table, or index was
condition unavailable, wait until it is available before invoking
• Db2 not up the application again.
• Db2 not operational If allocation failed for an application plan, REBIND
• Db2shutdown in progress the plan to determine the problem. Error messages
are produced explaining why the plan could not be
• Db2 restricted access mode allocated.
• Allocation error
For other types of allocation errors, installation action
• Db2 - CICS attachment not up might be required to correct the problem.
• Db2 - CICS ENTRY disabled For CICS attachment failures, resolve the primary
• The object is dependent on facilities of a release cause as noted by the reason code. Then restart the
of Db2 that is newer than the release that you attachment.
are currently running (fall back).
• Db2restarted in light mode Problem determination
reason-code The reason-code, resource-type, and resource-name
The Db2 reason code value that indicates the might not be available. If they are not available,
reason for the failure. For explanations of reason nothing appears.
Any attempts to issue SQL statements after receiving
373.
SQLCODE -923 will cause unpredictable results.
resource-type and resource-name
The type and name of the resource that the
message identifies. For an explanation of resource- SQLSTATE
type and resource-name values, see Resource 57015
Related information
Possible causes of an allocation error are: -923
• The application plan does not exist. CONNECTION NOT ESTABLISHED: DB2
condition REASON reason-code, TYPE resource-
• A required database, table space, table, or index is
type, NAME resource-name
unavailable.
• Data set allocation failed for a required data set. DSNT500I (Db2 Messages)
• There is insufficient virtual storage. -924 DB2 CONNECTION INTERNAL

• The application is trying to execute the plan ERROR, function-code,return-
from a system (environment) that was restricted code,reason-code
when the plan was bound or rebound. Check
the SYSPLSYSTEM table to determine from which

Explanation -926 ROLLBACK NOT VALID IN IMS,
CICS OR RRSAF ENVIRONMENT
Connection to Db2 has failed because of an
unexpected internal error, identified by the reason-
code value. Explanation
An application executing in either an IMS or CICS
System action environment or an application executing in an RRSAF
environment when Db2 is not the only resource
The statement cannot be processed. The connection manager has attempted to execute a ROLLBACK
to Db2 is not established. statement. The SQL ROLLBACK statement cannot be
executed in these environments.
Programmer response
The requested function-code and return-code values System action
might provide additional information. Any attempts to The statement cannot be processed. No rollback is
issue SQL statements after the SQLCODE -924 might performed.
have unpredictable results.
Programmer response
SQLSTATE
The IMS, CICS or RRS protocols should be used to roll
58006 back work in these environments.
Related concepts
Db2 reason codes SQLSTATE
in a message that Db2 issues. The reason codes 2D521
provide specific details about the circumstances -927 THE LANGUAGE INTERFACE
of a particular instance of the message. (LI) WAS CALLED WHEN THE
CONNECTING ENVIRONMENT
-925 COMMIT NOT VALID IN IMS, CICS WAS NOT ESTABLISHED. THE
OR RRSAF ENVIRONMENT PROGRAM SHOULD BE INVOKED
UNDER THE DSN COMMAND
Explanation
An application executing in either an IMS or CICS Explanation
environment or an application executing in an RRSAF In the TSO environment, the user has attempted
environment when Db2 is not the only resource to execute an application program without first
manager has attempted to execute a COMMIT establishing the correct execution environment by
statement. The SQL COMMIT statement cannot be issuing the DSN command. In the IMS, CICS, RRSAF,
executed in these environments. or call attachment facility (CAF) environment, the user
has attempted to execute an application program that
System action is not using the correct language interface module.
The statement cannot be processed. No commit is
performed. System action
Programmer response
The IMS, CICS or RRS protocols should be used to Programmer response
commit work in these environments. In the TSO environment, Db2 application programs
If a stored procedure is being called from IMS or CICS, should be invoked under the RUN subcommand of the
ensure that the stored procedure is not defined to DSN command processor. In the IMS, CICS, RRSAF,
perform a commit on return. or CAF environment check that the application was
link-edited with or is dynamically allocating the correct
language interface module. The language interface
SQLSTATE modules required in each environment are as follows:
2D521 • TSO: DSNELI

• IMS: DFSLI000 System action
• CICS: DSNCLI In the IMS and CICS environments, all SQL statements
• RRSAF: DSNRLI are rejected until the rollback occurs. In the other
• CAF: DSNALI environments, all SQL statements other than a static
ROLLBACK are rejected until a static ROLLBACK is
The DYNAM option can result in the incorrect language executed.
interface module being loaded at run time.
Programmer response
SQLSTATE
Issue the appropriate (depending on the environment)
51006 request to cause a rollback. Re-establish any cursor
-929 FAILURE IN A DATA CAPTURE positioning and continue the application with the first
EXIT: token request that received the -939 SQLCODE.
SQLERRP contains the name of the module that
Explanation detected the previous failure and placed the
application in the must-abort state.
'token' is an information string provided by DPROP's
exit routine which captures data changes in tables
defined with DATA CAPTURE CHANGES.
SQLSTATE
51021
System action -947 THE SQL STATEMENT FAILED
The information string is placed in in the SQLERRM BECAUSE IT WILL CHANGE A
area of the SQLCA. TABLE DEFINED WITH DATA
CAPTURE CHANGES, BUT THE
DATA CANNOT BE PROPAGATED
For documentation of the actions associated with Explanation
this SQLCODE, refer to the Data Propagator (DPROP)
publications. The DPROP SUPPORT option on the installation
panel is set to 2 (support DPROP only). The SQL
statement would have changed a table defined with
SQLSTATE DATA CAPTURE CHANGES. However, the data cannot
58002 be propagated because the SQL statement did not
originate from an IMS subsystem, or monitor trace
-939 ROLLBACK REQUIRED DUE TO class 6 was not active at the beginning of the unit of
UNREQUESTED ROLLBACK OF A work for that change.
REMOTE SERVER
System action
Explanation
A dynamic commit was executed preceding the
execution of this request. The remote server to which
the application was CONNECTed during the dynamic System programmer response
COMMIT successfully committed. However, at least Take one of the following actions:
one other remote server (which was read-only) rolled
back its portion of the distributed unit of work during • Change the installation option to 1 (no propagation)
the dynamic commit. or 3 (permit changes from any subsystem).
• Change the application program that receives this
To ensure that an application that uses cursor-hold
SQLCODE so that it can be run in an IMS subsystem,
cursors does not incorrectly assume cursor position
and activate monitor trace class 6.
is being maintained at any remote server that
rolled back, the application must perform a rollback If the installation option is changed to 3, SQL changes
operation. to tables defined with DATA CAPTURE CHANGES are
permitted from any subsystem, but they are not
Communications are still established with all remote
propagated unless the environment is set up for
servers.
propagation.

56038 If the location name is specified as the value of a
host variable, ensure that the name is left justified
-948 DISTRIBUTED OPERATION IS
in the host variable and, if necessary, padded on
INVALID
the right with blanks. If this is not the problem,
either SYSIBM.LOCATIONS must be updated to include
Explanation the specified name, or the specified name must be
changed to match a name in SYSIBM.LOCATIONS.
The unit of work was initiated before DDF was started,
and the application attempted to perform a distributed
operation. The unit of work must be terminated by a SQLSTATE
rollback operation. 42705
System action -951 OBJECT object-name OBJECT

TYPE object-type IS IN USE AND
In the IMS and CICS environments, all SQL statements CANNOT BE THE TARGET OF THE
are rejected until a rollback occurs. In the other SPECIFIED ALTER STATEMENT
environments, all SQL statements other than a static
ROLLBACK are rejected until a static ROLLBACK is
Explanation
executed.
The options for the SQL routine or trigger cannot
Programmer response be altered if the version of the routine is currently
active under the same thread that issued the ALTER
An application that performs local database updates statement, and one or more of the options that is being
before DDF is started cannot perform distributed altered result in the rebinding or regeneration of the
operations within the same unit of work. The current package for the object.
unit of work must be terminated by a rollback
object-name
operation and a new unit of work must be initiated
before any SQL operations can be performed.
object-type
Restart the current unit of work. The type of object.
If the failing statement was either an ALTER statement
SQLSTATE with an ACTIVATE VERSION clause, the active version
56062 of a currently active object under nested routine
invocation by the same thread cannot be changed.
-950 THE LOCATION NAME SPECIFIED
IN THE CONNECT STATEMENT IS
INVALID OR NOT LISTED IN THE System action
COMMUNICATIONS DATABASE The statement cannot be processed.

One of the following conditions applies: Review the information about altering options
• The location name is blank. and which alterations result in the rebinding or
regeneration of associated packages.
• The data type of the host variable is not character
string. Verify that the logic for nested routine invocation
• The length attribute of the host variable is greater involving SQL routines and the ALTER statements
than 16. are working as intended. With SQL procedures, pay
additional attention to CALL :HV statements with
• The location name does not appear in the the setting of special register CURRENT ROUTINE
LOCATIONS column of the SYSIBM.LOCATIONS VERSION, as the combination of these statements can
table, nor is it the name of the local Db2 subsystem. produce unwanted logic flows. If it is necessary to
use multiple versions of the same SQL routine in the
System action nested recursive chain, consider using CALL :HV and
the special register CURRENT ROUTINE VERSION to
The statement cannot be processed. The application control which version is used, instead of the ALTER
process is placed in the unconnected state. ACTIVATE VERSION clause.

SQLSTATE provide specific details about the circumstances
of a particular instance of the message.
55007
Related tasks
Related reference Controlling RRSAF connections (Db2
ALTER PROCEDURE (SQL - native) (Db2 SQL) Administration Guide)
-952 PROCESSING WAS INTERRUPTED -989 AFTER TRIGGER trigger-name

BY A CANCEL REQUEST FROM A ATTEMPTED TO MODIFY A ROW
CLIENT PROGRAM IN TABLE table-name THAT WAS
MODIFIED BY AN SQL DATA
Explanation CHANGE STATEMENT WITHIN A
FROM CLAUSE
A client program issued a cancel request that
terminated processing of the SQL statement.
Explanation
System action An SQL data change statement was specified in the
FROM clause where FINAL TABLE was specified, but
The SQL statement was terminated and any changes the underlying target base table of the SQL data
made by that statement have been undone. If an change statement has an AFTER trigger defined which
SQL cursor is associated with the interrupted SQL modifies the same table. This is disallowed.
statement, that cursor is closed.
System action
SQLSTATE
57014
-981 THE SQL STATEMENT FAILED Programmer response
BECAUSE THE RRSAF
CONNECTION IS NOT IN A STATE Avoid using the SQL data change statement within a
THAT ALLOWS SQL OPERATIONS, FROM clause, or change the trigger so that it does not
REASON reason-code. modify the table that is the target of the SQL data
change statement.
Explanation
SQLSTATE:
The application attempted to execute an SQL
operation, but the Resource Recovery Services 560C3
attachment facility (RRSAF) connection was not in a -991 CALL ATTACH WAS UNABLE
state that allows the processing of SQL statements. TO ESTABLISH AN IMPLICIT
CONNECT OR OPEN TO DB2. RC1=
System action rc1 RC2= rc2

Explanation
Programmer response Call attach attempted to perform an implicit connect
and open as the result of an SQL statement. The
Correct the error in the application, REBIND, and run connect or open failed with the returned values.
the application again.
rc1
The value returned in FRBRC1 for the failed
SQLSTATE CONNECT or OPEN request.
57015 rc2
The value returned in FRBRC2 for the failed
Related concepts
CONNECT or OPEN request.
Implicit connections to RRSAF (Db2 Application
Db2 reason codes System action
Reason codes are typically presented as a value The statement cannot be processed.
in a message that Db2 issues. The reason codes

Verify that the application intended to use the call The statement cannot be processed.
attachment facility (CAF) as the mechanism to connect
to Db2. For functions or stored procedures running Programmer response
in the WLM-established stored procedure address
space the application must be link-edited with or If this condition occurs when deploying a SQL routine,
dynamically allocate the RRS attachment language try again after Db2 at location-name is updated to
interface module (DSNRLI), not CAF. the release or maintenance level that can support the
package that is being deployed.
SQLSTATE If this condition occurs in contexts other than
deployment (for example, a package that was created
57015
prior to application of a PTF is no longer supported
-992 PACKAGE package-name CANNOT by the level of Db2 after the application of that
BE EXECUTED OR DEPLOYED ON PTF), then execute the ALTER PROCEDURE or ALTER
LOCATION location-name FUNCTION statement with the REGENERATE clause
for that version of the SQL routine at the current
server to regenerate the package using the current
Explanation
maintenance level. The ALTER PROCEDURE or ALTER
A mismatch in Db2 code levels prevents the package FUNCTION statement with the REGENERATE clause
from being executed or deployed. will cause a rebind of the package at the local server.
package-name If the SQL routine required package replication at
The name of the package. different servers, the process must be repeated for the
location-name regenerated SQL routine.
The Db2 system where the deployment or If variations of the package have been created
execution was attempted. locally with different collection IDs, those additional
One of the following conditions has occurred: packages should also be explicitly rebound.
• The package cannot be executed or deployed

because of a mismatch in the level of the Db2 code
SQLSTATE
between the system identified by location-name 51008
and the current server. The current server and the
system identified by location-name might be the -1403 THE USERNAME AND/OR
same system. PASSWORD SUPPLIED IS
INCORRECT
• The representation of an SQL routine cannot be
executed on the system. The package was bound
at a different release or maintenance level than the Explanation
system can support. The username and/or password supplied is incorrect.
Deployment is the process of establishing an SQL If either a username or password is supplied, then
routine at a remote location without regenerating both must be supplied and both must have a non-zero
the representation of that routine. The deployment length.
requires that the remote server be able to understand
the structures generated by the current server for System action
the identified package. The difference in code level
between the current server and the remote location The statement cannot be processed.
makes this impossible. The difference might be in
release levels or maintenance levels, but it is large User response
enough that the package cannot be deployed from the
current server to the remote location. Supply the correct username and password
combination.
This condition might be specific to this particular
package. Other packages might successfully be
executed on this system or deployed from the current
SQLSTATE
server to the remote location. 08004

-1760 CREATE PROCEDURE FOR SQLSTATE
procedure-name MUST HAVE
VALID LANGUAGE AND EXTERNAL 53089
CLAUSES -4302 JAVA STORED PROCEDURE
OR USER-DEFINED FUNCTION
Explanation routine-name (SPECIFIC NAME
specific-name) HAS EXITED WITH
A LANGUAGE or EXTERNAL clause is missing in the AN EXCEPTION exception-string
CREATE statement for procedure procedure-name.
This clause must be specified.
Explanation
System action User-defined function or stored procedure routine-
name exited with a Java exception that was not a
The statement cannot be processed. java.sql.SQLException.
If present, exception-string contains as much as will fit
Programmer response of the toString() of the exception that was uncaught.
Change the CREATE statement to include the missing
clause and reissue the statement. System action
Execution of the SQL statement is terminated.
SQLSTATE
-2001 THE NUMBER OF HOST VARIABLE The user-defined function or stored procedure
PARAMETERS FOR A STORED probably needs to be corrected. See your database
PROCEDURE IS NOT EQUAL TO administrator, or the author of the routine to find out
THE NUMBER OF EXPECTED HOST if the exception can be avoided, or if the user-defined
VARIABLE PARAMETERS. ACTUAL function or stored procedure needs to be fixed before
NUMBER sqldanum, EXPECTED it can be used.
NUMBER opnum
SQLSTATE
Explanation
38000
Db2 received an SQL CALL statement for a stored
procedure. However, the number of host variable -4700 ATTEMPT TO USE NEW FUNCTION
parameters supplied on the CALL statement does BEFORE FUNCTION LEVEL IS
not match the expected number of host variable ACTIVATED
parameters.
sqldanum Explanation
The number of host variable parameters as An attempt was made to use a new capability before
determined by examining the SQLDA. the required function level is activated. Capabilities
opnum that are introduced in a Db2 function level cannot be
The expected number of host variable parameters used before that function level is activated.
as determined by parsing the statement.
System action
System action
Programmer response
Programmer response
Either delay running your program until the required
If the SQL CALL statement is coded incorrectly, modify function level is activated, or restrict your program to
the SQL application to provide the correct number of capabilities that are supported at the current function
parameters on the SQL CALL statement. level.

56038 Correct the problem and reissue the statement. The
corrective action to take depends on reason-code
Related tasks
value:
Activating Db2 12 new function at migration
(Db2 Installation and Migration) 1. Increase the number of maximum table space
Related reference partitions by increasing the value of the
MAXPARITIONS to satisfy the constraint.
Db2 12 function levels (Db2 for z/OS What's
New?) 2. Increase the number of maximum table space
-ACTIVATE (Db2) (Db2 Commands) partitions by changing the table space page size
and DSSIZE. For more information, see Limits in
-4701 TABLE SPACE PARTITIONS Db2 for z/OS (Db2 SQL).
EXCEED SYSTEM LIMIT (system- 3. Increase the number of maximum XML table space
limit) REASON reason-code partitions by changing the XML table space page
size and DSSIZE. For more information, see Limits
Explanation in Db2 for z/OS (Db2 SQL).
4. The attempted partition design is not supported by
system-limit
the internal storage for the limit keys in the object
The system limit which was exceeded. The value
descriptor (OBD). Try adjusting the design to uses a
can be a size or a number of partitions.
smaller limit keys, fewer partitions, or both.
reason-code
Identifies the reason the that statement exceeded
the system-limit value:
SQLSTATE
1 54054
An ALTER TABLE statement attempted to Related reference
add partitions to a partition-by-growth (PBG) Limits in Db2 for z/OS (Db2 SQL)
table space, but the resulting total number
of partitions would exceed the specified
MAXPARTITIONS value for the table space. CREATE INDEX (Db2 SQL)
CREATE TABLESPACE (Db2 SQL)
2
An ALTER TABLE statement attempted to add ALTER TABLESPACE (Db2 SQL)
partitions to a partition-by-range (PBR) or
partitioned (non-UTS) table space, but the -4704 AN UNSUPPORTED DATA TYPE
resulting total number of partitions would WAS ENCOUNTERED AS AN
exceed the maximum number of supported INCLUDE COLUMN
partitions for a table space of that type.
3 Explanation
An ALTER TABLE statement attempted to An unsupported data type was specified in the
add partitions to an XML table space, but include-column specification.
the resulting total number of partitions
would exceed the maximum number that is
supported. System action
An ALTER TABLE or CREATE INDEX statement
attempted to create or change partition limit Programmer response
keys, but the internal storage for the limit keys
in the object descriptor (OBD) would exceed Change the statement to exclude the unsupported
the maximum supported size. datatype.

Related tasks
Adding columns to the set of index keys of a
unique index (Db2 Administration Guide)

Related reference NOT THE SAME AS THOSE THAT
CREATE INDEX (Db2 SQL) WERE IN EFFECT (ENVID defined-
envid) WHEN THE OBJECT OR
-4705 option SPECIFIED ON ALTER VERSION WAS FIRST DEFINED
STATEMENT FOR object-name
(object-type) IS NOT VALID Explanation
The statement attempted to recreate or alter a routine
Explanation or advanced trigger, and the environment settings
An ALTER statement specified an option that is not that are in effect for the current statement are not
valid for the type of routine or trigger. the same as when the object was first defined. The
statement is a CREATE or ALTER statement.
option
The invalid option. current-envid
The environment settings that are in effect for the
object-name
current statement.
The name of the procedure, function, or trigger.
defined-envid
object-type
The environment settings that were in effect when
The type of object: procedure, function, or trigger.
the object was first defined.
The valid options vary by object type:
For the recreation or alteration of an object to
PROCEDURE be successful, the environment settings that are in
The options that can be specified when altering effect for the statement must be the same as the
an SQL procedure depend on the type of the environment settings that were in effect when the
SQL procedure being changed. Two types of object was first defined if any of the following options
SQL procedures exist: native SQL procedures and are specified as part of the statement's option-list
external SQL procedures. clause:
FUNCTION • QUALIFIER
The options that can be specified when altering
• PACKAGE OWNER
an SQL scalar function depend on whether the
SQL function is an inlined function or a compiled • OPTHINT
function. • SQL PATH
TRIGGER • DECIMAL if the value includes a comma
The options that can be specified when altering a
trigger. This message can be issued when an object is
recreated or altered, or when a specific version of an
object is recreated or altered.
System action
This message is also issued when the WLM FOR
The statement cannot be processed. DEBUG MODE option is specified for a statement and
the specified name cannot be represented correctly in
User response the CCSID of the original statement that defined the
object. The CCSIDs of the current statement and the
Review the appropriate ALTER statement to determine original statement that defined the object are part of
which options can be changed for the specified object, the environment settings identified by current-envid
correct the syntax, and reissue the statement. and defined-envid.

530A3 The statement cannot be processed.
Related reference
Statements (Db2 SQL) User response
-4706 THE STATEMENT FOR AN SQL Specify the name of an object that was created with
ROUTINE OR ADVANCED TRIGGER the same environment settings in effect as the current
CANNOT BE PROCESSED BECAUSE settings, or do not specify the options named above.
THE OPTIONS CURRENTLY IN
EFFECT (ENVID current-envid) ARE

530A4 The statement cannot be processed.
Related reference
Statements (Db2 SQL) Programmer response
Verify that the table names in the EXCHANGE DATA
-4709 EXPLAIN MONITORED STMTS statement are related where one is a base table and
FAILED WITH REASON CODE = the other is defined as a clone of the base table.
yyyyy
SQLSTATE
Explanation
530A7
The EXPLAIN statement specified MONITORED
STMTS, but the statement could not be processed for -4727 SYSTEM PARAMETER system-
one of the following reasons: parameter VALUE parameter-value
IS INCONSISTENT WITH CLAUSE
01
clause SPECIFIED ON statement-
Profiling is not active.
name STATEMENT.
02
A matching profile scope is not found.
Explanation
System action A statement was processed with a clause that is
invalid for the system parameter and parameter value
The statement cannot be processed. that were used.
system-parameter
Programmer response The name of the system parameter.
Take the appropriate corrective action for the failing parameter-value
reason code: The value of the system parameter.
01 clause
Execute the START PROFILE command to activate The statement clause that is not permitted in this
profiling. case.
02 statement-name
Specify a scope that matches a profile entry in the The name of the statement that was processed.
profile table.
System action
SQLSTATE
560CK
-4710 EXCHANGE DATA STATEMENT Programmer response
SPECIFIED table1 and table2 BUT Review the syntax and parameter descriptions for
THE TABLES DO NOT HAVE A the statement identified in the message, or contact
DEFINED CLONE RELATIONSHIP the system administrator to find out more about the
setting of the system parameter.
Explanation
An EXCHANGE DATA statement was issued. The SQLSTATE
EXCHANGE DATA statement is only supported for pairs 530A8
of tables that have been defined such that one is a
base table and the other is a clone of the base table. Related reference
Table table1 is not defined as a clone table of table Statements (Db2 SQL)
table2, and table table2 is not defined as a clone table
of table1. -4728 ANOTHER VERSION OF OBJECT
object-name EXISTS AND
IS DEFINED WITH AN

INCOMPATIBLE OPTION. THE IS NOT DEFINED IN THE XML
OPTION IS option-name. VERSIONING FORMAT, REASON
reason-code
Explanation
Explanation
The option that is identified by option-name must be
the same for all versions of an SQL routine or advanced The indicated column is not valid in the context
trigger. specified. The column must be defined in the XML
versioning format.
System action table-name
column-name
User response
reason-code
Query the applicable option on the existing versions The reason for the message or SQL code, indicated
of the SQL routine or advanced trigger and ensure the by one of the following values:
same option is used across all versions.
1
The target of the SET assignment clause
SQLSTATE containing the XMLMODIFY function invocation
428HL is a column that is not XML in the versioning
format. The target of an assignment involving
Related concepts an invocation of the XMLMODIFY function must
Autonomous procedures (Db2 Application be an XML column that is in the XML versioning
programming and SQL) format.
2
-4729 PROCEDURE IS DEFINED AS
A SELECT FROM UPDATE or SELECT FROM
AUTONOMOUS, AND CANNOT
DELETE statement specified OLD TABLE, and
BE INVOKED BECAUSE THE
referenced an XML column that is not defined
NESTED ENVIRONMENT ALREADY
in the XML versioning format.
INVOKED AN AUTONOMOUS
PROCEDURE.
System action
Explanation The statement cannot be processed.
Within an environment of nested procedures and
functions, only one invocation of an autonomous User response
procedure is allowed.
Correct the syntax, and reissue the statement.
1
System action
Change the SET assignment clause to specify an
The CALL statement cannot be processed. XML column that is defined in the XML versioning
format, or remove the XMLMODIFY function in the
User response assignment clause.
2
Ensure that multiple autonomous procedures are not Change the column specified in the SELECT FROM
invoked within the nested environment. UPDATE or SELECT FROM DELETE statement to
specify an XML column that is defined in the XML
SQLSTATE versioning format.
51043
SQLSTATE
Related concepts
Autonomous procedures (Db2 Application 55079
programming and SQL) Related reference
XMLMODIFY (Db2 SQL)
-4730 INVALID SPECIFICATION OF XML
COLUMN table-name.column-name REORG TABLESPACE (Db2 Utilities)

-4731 THE NATIVE SQL Explanation
ROUTINE STATEMENT
FOR PACKAGE location- The ALTER statement cannot be processed because
name.collection-id.program- the maximum number of alters for the object has
name.consistency-token already been exceeded. This can occur for the
STATEMENT NUMBER statement- following reasons:
number CANNOT BE PROCESSED. • The SET DATA TYPE keyword was specified on an
ALTER TABLE ALTER COLUMN statement, but the
Explanation maximum number of ALTER statements for this table
has already been reached.
The SQL routine for the statement must be running at
• The statement attempts to alter an index, but the
the location where the statement is requested. Either
maximum number of ALTER statements for this
no SQL routine is running at the indicated location, or
index has already been reached.
the SQL routine that is running is not the SQL routine
for the indicated package.
System action
location-name
The name of the server where the statement The statement cannot be processed.
cannot be processed.
collection-id Programmer response
The name of the collection of the package that
Follow the instructions in Removing in-use table space
contains the statement that cannot be processed.
versions (Db2 Administration Guide) to decrease the
program-name number of table version numbers.
The name of the package that contains the
statement that cannot be processed.
SQLSTATE
consistency-token
The consistency token of the package that contains 54055
the statement that cannot be processed. Related tasks
statement-number Removing in-use table space versions (Db2
The package statement number of the statement Administration Guide)
that cannot be processed.
-4733 THE ALTER TABLE STATEMENT
System action CANNOT BE EXECUTED BECAUSE
COLUMN column-name IS MIXED
The statement cannot be processed. DATA, OR THE DATA TYPE OR
LENGTH SPECIFIED DOES NOT
System programmer response AGREE WITH THE EXISTING DATA
TYPE OR LENGTH
Take either of the following corrective actions:
• Use a BIND PACKAGE COPY command instead of Explanation
the BIND PACKAGE DEPLOY command to bind the
package at that location. The ALTER TABLE statement for column column-name
could not be processed for one of the following
• Change the application logic to run the routine at reasons:
that location where the statement executes.
• the existing column is MIXED and the statement
attempted to convert the column to SBCS. This
SQLSTATE conversion is not supported.
560C5 • the data type or length in the ALTER statement did
Related reference not match the existing data type or length of the
column in the table being altered.
-4732 THE MAXIMUM NUMBER OF System action

ALTERS ALLOWED HAS BEEN
EXCEEDED FOR object-type

Programmer response the definition of the table specified for the table
locator parameter on the CREATE PROCEDURE or
Correct the SQL statement to specify a conversion that CREATE FUNCTION statement for the routine.
is supported.
The use of TABLE LIKE syntax provides an implicit
definition of the transition table. It specifies that the
SQLSTATE transition table has the same number of columns
429BQ as the identified table or view. The columns must
have the same data type, length, precision, scale,
-4734 THE LOAD MODULE FOR subtype, and encoding scheme as the identified table
THE PROCEDURE ASSUMES A or view, as described in catalog tables SYSCOLUMNS
PARAMETER VARCHAR OPTION and SYSTABLESPACES. The number of columns and
THAT IS NOT CONSISTENT WITH the attributes of those columns are determined at the
THE OPTION SPECIFIED ON THE time the CREATE PROCEDURE or CREATE FUNCTION
CREATE PROCEDURE STATEMENT statement is processed. Any subsequent changes to
FOR procedure-name the number of columns in the table or the attributes of
those columns does not affect the parameters of the
Explanation routine.
The C load module for the SQL procedure was built

assuming a PARAMETER VARCHAR option that is not System action
the same as what was specified on the CREATE The statement cannot be processed.
PROCEDURE statement for the procedure.
procedure-name Programmer response
The name of the SQL procedure.
Change the table name in the table locator reference
The PARAMETER VARCHAR option assumed when the to the name of a table that has the same definition
load module for the procedure is created should be the as the table name used on the CREATE PROCEDURE
same as the one that is specified when the procedure or CREATE FUNCTION statement for the table locator
is defined to Db2. The consequences of a mismatch parameter.
include errors at execution time, and invalid data
output with no error to indicate that a problem exists.
SQLSTATE
System action 560CV
The statement cannot be processed. Related concepts

Queries (Db2 SQL)
SYSCOLUMNS catalog table (Db2 SQL)
Rebuild the procedure so that the options match.
SYSTABLESPACE catalog table (Db2 SQL)
SQLSTATE
-4736 A PERIOD SPECIFICATION
560CU
OR PERIOD CLAUSE IS NOT
-4735 INVALID TABLE REFERENCE FOR SUPPORTED AS SPECIFIED FOR
TABLE LOCATOR OBJECT object-name. REASON
CODE = reason-code.
Explanation
Explanation
At execution time, an SQL statement in the body of
a routine has a table-locator-reference in the FROM A period specification or period clause is not valid as
clause to reference a transition table of the trigger specified.
invoking the routine. For example:
object-name
TABLE (table-locator-var LIKE table-name) The name of the object.
reason-code
SQLCODE -4735 is issued when the definition of the A numeric value that indicates why the period
table that follows the LIKE keyword is different than specification or period clause is invalid:

1 -4738 TABLE table-name CANNOT
In a CREATE FUNCTION statement for object- BE DEFINED AS SPECIFIED
name, the definition of the function contains IN THE statement STATEMENT
a period specification that is not supported. IN A COMMON CRITERIA
The routine body of an SQL scalar function ENVIRONMENT
must not contain a period specification or
period clause. A RETURN statement in a
Explanation
table function must not contain a period
specification. A CREATE, DECLARE, or ALTER statement attempted
2 to define a new table or change an existing table in a
In a CREATE VIEW statement for object- Common Criteria environment, but the specification is
name, a fullselect must not contain a period not valid for one of the following reasons:
specification. • A CREATE TABLE statement included an explicit list
3 of column definitions, but did not include a security
In an UPDATE statement for the view object- label column. In a Common Criteria environment
name, the result table of the outer fullselect each table must be defined with a security label
of the view definition, explicitly or implicitly, column.
must include the start and end columns of the • A CREATE TABLE statement included a LIKE clause
BUSINESS_TIME period. or AS FULLSELECT clause with the WITH NO DATA
clause, to define a new base table. The LIKE
System action clause and AS FULLSELECT fullselect clauses are not
supported in a Common Criteria environment.
• A CREATE TABLE statement included an AS fullselect
clause to define a materialized query table, and
User response the WITH NO DATA clause was not specified.
Either remove the period specification or period Materialized query tables are not supported in a
clause, or change the statement to reference a Common Criteria environment.
different object. • A DECLARE GLOBAL TEMPORARY TABLE statement
included a LIKE clause, or AS FULLSELECT clause
with the WITH NO DATA clause to define a
SQLSTATE
new temporary table. The LIKE clause and AS
560CY FULLSELECT clauses are not supported in a Common
Criteria environment.
-4737 STATEMENT statement IS NOT
ALLOWED WHEN USING A • An ALTER TABLE statement attempted to change
TRUSTED CONNECTION a table to a materialized query table. Materialized
query tables are not supported in a Common Criteria
environment.
Explanation
The statement was issued from a session that is System action
using a trusted connection. This statement is not
supported with trusted connections. The statement The statement cannot be processed.
can be CREATE SYNONYM.
Programmer response
System action Change the statement so that it is valid in a Common
The statement cannot be processed. Criteria environment.
• For a CREATE TABLE statement that includes a lit
Programmer response of column definitions, if the statement is issued
in a Common Criteria environment (DSN6SPRM
Change the statement to one that is supported when COMCRIT=YES), then every table created must have
running under a trusted connection. a security label. Designate a column AS SECURITY
LABEL or change the subsystem parameter.
SQLSTATE • For a CREATE or DECLARE statement that includes
429BY a LIKE or AS FULLSELECT clause, remove the clause

and explicitly specify the attributes of the table that • ORIGINAL_ ENCODING_ CCSID
is being defined. • DECIMAL_POINT
• Do not issue a CREATE or ALTER TABLE statement • MIN_DIVIDE_SCALE
that attempts to define a materialized query table in
a Common Criteria environment. • SQL_STRING_ DELIMITER
• MIXED_DATA
SQLSTATE • DECIMAL_ARITHMETIC
56038 • DATE_FORMAT
• TIME_FORMAT
-4739 ENVIRONMENT SETTINGS
(IDENTIFIED BY ENVID envid1) • ROUNDING
USED BY object-name ARE NOT
THE SAME AS THE ONES THAT System action
WERE IN EFFECT (IDENTIFIED
BY ENVID envid2) WHEN OTHER The statement cannot be processed.
COLUMN MASKS AND ROW
PERMISSIONS WERE DEFINED Programmer response
FOR TABLE table-name
Use the values of envid1 and envid2 in the SQL error
message to query the SYSIBM.SYSENVIRONMENT
Explanation catalog table to locate the expected environment
A CREATE MASK or CREATE PERMISSION statement setting values. Correct the syntax, and reissue the
was issued with environment settings that do not statement.
match the settings that were previously used.
All column masks and row permissions defined SQLSTATE
for the same table must use the same set of
environment settings. The set of environment settings 530A4
is determined when the first column mask or row Related reference
permission is defined for the table. To create a new SYSENVIRONMENT catalog table (Db2 SQL)
column mask or row permission, the environment
CREATE MASK (Db2 SQL)
settings in effect when the CREATE statement is
issued must be the same as the environment set. CREATE PERMISSION (Db2 SQL)
envid1 -4742 THE STATEMENT CANNOT BE

The environment settings that are used by the EXECUTED BY DB2 OR IN THE
object that is identified by object-name. ACCELERATOR (REASON reason-
object-name code)
envid2 Explanation
The environment settings that were in use when A statement cannot be executed by Db2 or by an
existing column masks and row permissions were accelerator server.
defined for the table that is identified by table-
name. The statement cannot be executed by Db2 if any of the
following conditions are true:
table-name
The name of the table. • Special register CURRENT GET_ACCEL_ARCHIVE is
set to YES, and the statement needs to access data
The SYSIBM.SYSENVIRONMENT catalog table
that is stored only in the accelerator server.
contains the list of environment settings. The following
set of environment settings must be the same among • Special register CURRENT QUERY ACCELERATION is
the multiple column masks and row permissions that set to ALL, so the statement must be executed in the
are defined for a single table: accelerator server.
• ENVID • A function that was referenced can be run only on an
accelerator server.
• CURRENT_SCHEMA
• The statement references an accelerator-only table.
• PATHSCHEMAS
• APPLICATION_ ENCODING_ CCSID

The statement cannot be executed by an accelerator 13
server if any condition that is indicated by a reason The accelerator server that contains the tables
code is true. that are referenced in the query is not started.
reason-code 14
A numeric value that provides additional A column that is referenced in the query was
information about why the statement cannot be altered in Db2 after the data was loaded in the
executed in the accelerator server. accelerator server.
Tip: If you need more information about why the 15

statement cannot be executed in the accelerator, The query uses functionality that is available
issue the EXPLAIN statement and examine the only in DB2 10 or later, and the functionality is
output in the DSN_QUERYINFO_TABLE table. not supported by the accelerator server.
17
1
The query is an INSERT from
No active accelerator server was found or the
SELECT statement. Subsystem parameter
table was not enabled for query acceleration
QUERY_ACCEL_OPTIONS does not specify
when the statement was executed.
option 2 to enable the acceleration of INSERT
2 from SELECT statements.
The CURRENT QUERY ACCELERATION special
18
register is set to NONE.
The query uses functionality that is available
3 only in Db2 11 or later, and the functionality is
Db2 classified the query as a short-running not supported by the accelerator server.
query, or Db2 determined that sending the
19
query to an accelerator server provided no
The accelerator server is not at the correct
performance advantage.
level and does not support a function in the
4 SQL statement.
The query is not read-only.
20
6 The query is a rowset cursor that is declared
The cursor is defined as scrollable or is a WITH RETURN, executes remotely, or executes
rowset-positioned cursor. under an SQL PL routine.
7 21
The query references objects with multiple The query contains a correlated subquery that
encoding schemes. is not supported for acceleration.
8 22
The FROM clause of the query specifies a data- The statement references an accelerator-only
change-table-reference. table, but the statement cannot run on the
9 accelerator. For example:
The query contains a nested table expression. • MERGE statement references an accelerator-
10 only table.
The query contains a recursive reference to a • UPDATE or DELETE statement references an
common table expression. accelerator-only table, but the target table of
11 the UPDATE, DELETE is a normal Db2 table:
The query contains an unsupported UPDATE DB2_TABLE SET .. (SELECT .. FROM
expression. The text of the expression is in ACCEL_ONLY_TABLE).
QI_DATA. • INSERT, UPDATE or DELETE of a
12 row-fullselect with subselect. UPDATE
The query references a table that has any of ACCEL_ONLY_TABLE SET (C1, C2) = (SELECT
the following characteristics: C3, C4 FROM TABLE2);
• Is not defined in the accelerator server 23
• Is defined in a different accelerator server The SELECT INTO statement is bound for
from another table in the query acceleration but is run as a remote SELECT
INTO statement, which is not supported for
• Is defined in the accelerator server, but is not acceleration.
enabled for query acceleration

24 was originally bound for acceleration
The DDL or DML statement cannot run on with the QUERYACCELERATION bind option
the accelerator because the connection to the value of ELIGIBLE or ENABLE (not
accelerator server does not allow updates. ENABLEWITHFAILBACK), the query cannot be
This problem can occur when a two-phase bound for acceleration to the target accelerator
commit requester (for example, a Db2 for z/OS that Db2 has selected for this particular run
requester) connects to a Db2 for z/OS server to of the query. This special incremental bind
run a DDL or DML statement on an accelerator. usually occurs for one of the following reasons:
25 • The user table has been dropped and re-
The statement contains a reference to a created in Db2 for z/OS but has not been
column with an unsupported data type. refreshed in the target accelerator since the
26 last time the static query was bound for
FL 509 The CREATE TABLE statement clause acceleration.
IN ACCELERATOR specifies an accelerator alias • The archive status of the user table in the
that resolves to more than one accelerator and target accelerator has changed since the
at least one of the following conditions is true: last time the static query was bound for
• Your Db2 function level is lower than acceleration.
V12R1M509. Failure to bind the static query for acceleration
• The SYSACCEL.SYSACCELERATEDTABLES during this incremental bind can occur if the
table does not have the FEATURE column. user table in the target accelerator is down-
level from the current definition of that table
27 in the Db2 for z/OS catalog. This failure might
The DROP TABLE statement specifies a also occur due to other reasons.
referencing accelerator-only table, which
cannot be removed by using the DROP TABLE 30
statement. Accelerator WAITFORDATA behavior is
requested but cannot be achieved for this
28
query. The query will not be accelerated. The
FL 509 The SQL INSERT, UPDATE, or DELETE
query specifies a Db2 accelerated table, but
statement references a high availability
the same Db2 unit of work includes a previous
accelerator-only table (AOT) that is defined in
uncommitted Db2 change that will not be
multiple accelerators and one of the following
available to the query when it is run on the
conditions is true:
accelerator. The Db2 change might or might
• Neither the CURRENT ACCELERATOR special not be related to the Db2 accelerated table
register nor the ACCELERATOR bind option is that is referenced in the query.
used. 31
• The CURRENT ACCELERATOR special register Accelerator WAITFORDATA behavior is
or the ACCELERATOR bind option specifies requested but cannot be achieved for this
one of the following values: query that specifies both an accelerator-only
table (AOT) and a Db2 accelerated table. The
– An alias that resolves to multiple
query will not be accelerated and cannot be
accelerators. The alias must resolve to one
run in Db2. The same Db2 unit of work includes
V7 or later accelerator.
a previous uncommitted Db2 change that will
– An accelerator that is not a V7 or later not be available to the query when it is run on
accelerator. A V7 or later accelerator is the accelerator. The change might or might not
required to execute the SQL statement. be related to the Db2 accelerated table that is
– An accelerator that does not exist or is referenced in the query.
not available when the SQL statement is 32
executed. Accelerator WAITFORDATA behavior is
– An accelerator that is not qualified to requested but cannot be achieved for this
execute the SQL statement for a high query. The query will not be accelerated. The
availability AOT. query specifies a Db2 accelerated table, but
the same Db2 unit of work includes a previous
29 uncommitted accelerator-only table (AOT)
During a Db2 for z/OS special runtime change. This uncommitted change resulted
incremental bind of a static query that in the creation of an accelerator database

snapshot isolation (SI) for this unit of work Programmer response
before the query was run. This accelerator
database SI can prevent committed and Use the reason code to determine the cause of the
replicated Db2 changes, made either by this failure, and take the appropriate action:
transaction or by a different transaction, from 1
being available to the accelerated query, even Start the accelerator server or enable the table for
if the Db2 changes are replicated to the query acceleration.
accelerator before the query is run there.
2
33 Set the CURRENT QUERY ACCELERATION special
The query could not run on the accelerator due register to ENABLE, ENABLE WITH FAILBACK,
to different reasons on different versions of the ELIGIBLE, or ALL.
accelerator.
3
34 None.
The statement included an expression that
4
can run on an accelerator server only
Ensure that the query meets the criteria for a
when the CURRENT QUERY ACCELERATION
read-only query. See the information on read-only
special register is set to ALL, ENABLE, or
cursors in DECLARE CURSOR (Db2 SQL).
ELIGIBLE. However, the CURRENT QUERY
ACCELERATION special register is set to NONE 6
or ENABLE WITH FAILBACK. Remove the SCROLL clause or WITH ROWSET
POSITIONING clause from the cursor declaration.
See the programmer responses for the
two different REASON_CODE values for the 7
corresponding version of the accelerator. Ensure that all objects to which the query refers
have the same encoding scheme.
35
8
The query uses functionality that is available
Rewrite the FROM clause of the query so that
only in Db2 12 or later, and the accelerator
it does not include a data-change-table-reference
server does not support the functionality.
clause.
36
9
The USE ONLY NEW ACCELERATOR_TYPE
Ensure that the FROM clause of the query does not
subsystem parameter is set to YES; however,
contain a subquery.
either an active V7 or later accelerator was not
found or the table was not enabled for query 10
acceleration in the V7 or later accelerator when Ensure that the FROM clause of the query does not
the statement was executed. reference a common table expression.
37 11
The USE ONLY NEW ACCELERATOR_TYPE Remove the unsupported functionality from the
subsystem parameter is set to YES, but the V7 query.
or later accelerator that contains the tables of 12
the query is not started. Ensure that all tables that are referenced by the
38 query are in the same accelerator server, and that
The USE ONLY NEW ACCELERATOR_TYPE all tables are enabled for query acceleration.
subsystem parameter is set to YES, but the V7 13
or later accelerator is not at the correct level. Start the accelerator server that contains the
42 tables that are referenced in the query.
The SYSACCEL.SYSACCELERATORS or 14
SYSACCEL.SYSACCELERATEDTABLES tables Load the altered table into the accelerator server
are not found. again.
15
System action Ensure that the query does not use any
The statement cannot be processed. functionality that is not supported by the
accelerator server.

17 • Ensure that the IN ACCELERATOR clause in
Enable the acceleration of INSERT from SELECT the CREATE TABLE statement specifies one
statements by updating subsystem parameter accelerator or an alias that resolves to only one
QUERY_ACCEL_OPTIONS to include option 2. accelerator.
18 • Upgrade your Db2 function level to V12R1M509
Ensure that the query does not use any and add the FEATURE column to the
functionality that is not supported by the SYSACCEL.SYSACCELERATEDTABLES table.
accelerator server.
27
19 To drop a referencing accelerator-only table,
Update the accelerator server to enable invoke the IBM Db2 Analytics Accelerator
acceleration of the SQL statement that contains for z/OS ACCEL_REMOVE_REFERENCE_TABLES
the function text or expression text. Check that stored procedure.
your QUERY_ACCEL_OPTIONS values are properly
28
specified. Pay special attention to options 4, 7, and
FL 509 Set the CURRENT ACCELERATOR special
13 which, if not set properly, can cause -4742 with
register or ACCELERATOR bind option to specify
return code 19.
an accelerator or an alias that resolves to only
20 one accelerator that meets all of the following
If the rowset cursor query usage cannot be requirements:
changed, use QUERY ACCELERATION NONE.
• It must be a V7 or later accelerator.
21
Rewrite the correlated subquery that is not • It must be available.
supported for acceleration as a JOIN expression. • It must be qualified to execute the SQL INSERT,
For some examples, see How IBM Db2 UPDATE, or DELETE statement for the high
Analytics Accelerator for z/OS handles correlated availability accelerator-only table (AOT).
subqueries.
29
22 Take one of the following actions:
Ensure the statement does not reference an
accelerator-only table, or replace the accelerator- • Rebind the Db2 application package
only table with a Db2 table so that the query can for the static query with bind option
be executed in Db2. QUERYACCELERATION(ENABLEWITHFAILBACK).
23 • If a Db2 for z/OS accelerator contains a down-

Remove the SELECT INTO statement, or level version of the referenced user table, take
REBIND the package with bind option one of the following actions on that accelerator:
QUERYACCELERATION(NONE). If the program is – Refresh and reload the user table in that
an SQL PL procedure or function, use one of accelerator to match the current table
the following methods instead of using BIND or definition that is in the Db2 for z/OS catalog.
REBIND PACKAGE:
– Permanently remove the user table from that
• Alter the procedure or function by using ALTER accelerator.
PROCEDURE or ALTER FUNCTION
For more information about the actions on the
• Drop and then re-create the procedure or accelerator, see IBM Db2 Analytics Accelerator
function by using CREATE PROCEDURE or for z/OS documentation.
CREATE FUNCTION
After completing one of these actions, rerun the
24 application for the static query.
Issue the DDL or DML statement directly from
the Db2 for z/OS server or from a requester that If the QUERYACCELERATION bind option is set to
does not require two-phase commit protocols, for ENABLEWITHFAILBACK, failure to accelerate the
example, the IBM Data Server Driver for JDBC. query results in failback to Db2 and the query is
run only on Db2 for z/OS. This failure does not
25 return an error code for your application. If you
Remove the reference to the column with an are using the ENABLEWITHFAILBACK setting and
unsupported data type. the conditions for reason code 29 occur during the
26 special incremental bind, the query is run only on
FL 509 Take one of the following actions: Db2 for z/OS and SQLCODE -4742 is not returned
for your application or transaction.

30 your QUERY_ACCEL_OPTIONS values are specified
Either commit the previous Db2 change in the properly.
Db2 unit of work before running the query to 42
be accelerated, or do not specify an accelerator Ensure that all tables that are required for query
WAITFORDATA delay for this unit of work. acceleration are created. For more information,
31 see Tables that support query acceleration (Db2
Either commit the previous Db2 change in the SQL).
Db2 unit of work before running the query to
be accelerated, or do not specify an accelerator SQLSTATE
WAITFORDATA delay for this unit of work.
32 560D5
Either commit the previous accelerator-only table Related reference
(AOT) change in the Db2 unit of work before ACCELERATION OPTIONS field
running the query, or do not specify an accelerator (QUERY_ACCEL_OPTIONS subsystem
WAITFORDATA delay for this unit of work. parameter) (Db2 Installation and Migration)
33 DSN_QUERYINFO_TABLE (Db2 Performance)
Request EXPLAIN output and check
the REASON_CODE column in the -4743 ATTEMPT TO USE NEW FUNCTION
DSN_QUERYINFO_TABLE table. For situations that WHEN THE APPLICATION
result in reason code 33, two rows are returned COMPATIBILITY SETTING IS SET
with different REASON_CODE values: FOR A PREVIOUS LEVEL
• A row that contains the REASON_CODE value
that explains why the query cannot run on an Explanation
accelerator version earlier than V7.
An application or SQL object attempted to use a
• A row that contains the REASON_CODE value Db2 capability that is not supported by the current
that explains why the query cannot run on a application compatibility level. At function level 100
V7 or later accelerator. In this case, the error Db2 environments can use application compatibility
description might be prefixed by (Vx) to indicate levels for previous releases. At otherDb2 12 function
the specific accelerator version. The (Vx) prefix is levels, the application compatibility level can be
displayed only when reason code 33 is returned equivalent to the current function level, lower function
by the original query. levels in the current release, or previous releases.
See the programmer responses for the two This message is issued for a data definition statement
different reason codes for the corresponding that specifies functionality, or attempts to alter an
version of the accelerator. existing object definition, that requires a higher
34 application compatibility setting than is currently in
Set the CURRENT QUERY ACCELERATION special use.
register to ALL, ENABLE, or ELIGIBLE to execute If the message is issued for a CREATE TRIGGER
passthrough-only expressions. or ALTER TRIGGER statement and the application
35 compatibility level is V11R1 or lower, the following
Ensure that the query does not use any situations might apply:
functionality that is not supported by the • The trigger body contains an SQL PL statement.
accelerator server.
• The trigger body contains an SQL statement that was
36 not allowed in a trigger body in Db2 11.
Start the V7 or later accelerator or enable the table
for query acceleration. • The MODE DB2SQL clause is not present.
37 • An unsupported trigger option that was not allowed

Start the V7 or later accelerator that contains the in Db2 11 was specified. The only trigger options
tables that are referenced in the query. that are allowed in Db2 11 are SECURED and NOT
SECURED.
38
Update the V7 or later accelerator server to enable This message can be issued for an ALTER statement
acceleration of the SQL statement that contains if the CURRENT APPLICATION COMPATIBILITY
the function text or expression text. Verify that special register value is lower than the application
compatibility level of the existing object definition.
Altering an object might result in this error even if the

content of the ALTER statement is valid at the current • The CURRENT TEMPORAL SYSTEM_TIME
level. The errors can occur when the existing object special register is set to a non-null value.
definition contains some functionality that requires • The SYSTIMESENSITIVE bind option is set to
a higher level than the CURRENT APPLICATION YES.
COMPATIBILITY special register setting.
2
An application-period temporal table cannot
System action be referenced in the body of an SQL table
The statement cannot be processed. function when both of the following conditions
are true:
Programmer response • The CURRENT TEMPORAL BUSINESS_TIME
special register is set to a non-null value.
Check the application compatibility level of your
application or SQL object, and take one of the • The BUSTIMESENSITIVE bind option is set to
following actions: YES.
• Rebind the application or modify the SQL object to 3

use an application compatibility level that supports A system-period temporal table cannot be
the capability. referenced in the definition of a row permission
or column mask when all of the following
• Remove use of the unsupported capability from the
conditions are true:
application or SQL object.
• The row permission or column mask is
For details, see Application compatibility levels in Db2
activated by a data change statement or
(Db2 Application programming and SQL).
query.
• The CURRENT TEMPORAL SYSTEM_TIME
SQLSTATE special register is set to a non-null value.
56038 • The SYSTIMESENSITIVE bind option is set to
Related reference YES.
APPLCOMPAT bind option (Db2 Commands) 4
SET CURRENT APPLICATION COMPATIBILITY An application-period temporal table cannot
(Db2 SQL) be referenced in the definition of a row
SYSPACKAGE catalog table (Db2 SQL) permission or column mask when all of the
following conditions are true:
Db2 12 function levels (Db2 for z/OS What's
New?) • The row permission or column mask is
activated by a data change statement or
-4744 THE STATEMENT EXPLICITLY query.
OR IMPLICITLY REFERENCED • The CURRENT TEMPORAL BUSINESS_TIME
TEMPORAL TABLE table-name special register is set to a non-null value.
IN AN UNSUPPORTED CONTEXT.
REASON CODE reason-code. • The BUSTIMESENSITIVE bind option is set to
YES.
Explanation System action:
A reference to the specified temporal table is not
supported.
User response
table-name
The name of the table. Change the query or statement to remove the
reference to the temporal table and specify another
reason-code table.
A numeric value that indicates why the reference
is not supported. reason-code can have one of the
following values: SQLSTATE
1 530A9
A system-period temporal table cannot be
Related tasks
referenced in the body of an SQL table function
when both of the following conditions are true: Creating row permissions (Managing Security)

Creating column masks (Managing Security) 22
Related reference The Db2 table
BIND and REBIND options for packages, plans, SYSACCEL.SYSACCELERATEDPACKAGES or its
and services (Db2 Commands) indexes do not exist or are not defined
correctly.
CURRENT TEMPORAL SYSTEM_TIME (Db2 SQL)
CURRENT TEMPORAL BUSINESS_TIME (Db2 23
SQL) Option QUERY ACCELERATION or
GET_ACCEL_ARCHIVE is used but is invalid
CREATE FUNCTION (SQL table) (Db2 SQL)
because the Db2 SYSACCEL tables or indexes
do not exist or are not defined correctly.
-4746 THE STATEMENT CANNOT
BE PROCESSED FOR AN 24
ACCELERATED QUERY. REASON The Db2 SYSACCEL tables or indexes do not
CODE reason-code. exist or are not defined correctly.
Note: Reason codes 20 through 24 apply to
Explanation the CREATE PROCEDURE and ALTER PROCEDURE
statements for native SQL procedures or to the
The statement that involves an accelerated query
CREATE FUNCTION and ALTER FUNCTION statements
cannot be processed for the reason indicated by
for SQL scalar functions. They also apply to a
reason-code.
remote bind request with Db2 for z/OS as the target.
reason-code These reason codes map to the following BIND or
A numeric value that indicates why the statement REBIND PACKAGE messages: DSNT320I, DSNT321I,
cannot be processed. reason-code can have one of DSNT322I, DSNT323I, and DSNT324I.
the following values:
System action:
The only FETCH statement that is allowed for a
rowset cursor that is run by the accelerator is
User response
FETCH NEXT ROWSET.
2 Use the reason code to determine the cause of the
The FOR n ROWS clause must be specified on failure and take the appropriate action.
a FETCH NEXT ROWSET statement for a rowset
cursor that is run by the accelerator. SQLSTATE
3 560D5
The value of n in the FOR n ROWS clause of
a FETCH NEXT ROWSET statement does not Related information
match the value in the previous FETCH NEXT DSNT320I (Db2 Messages)
ROWSET statement. DSNT321I (Db2 Messages)
4 DSNT322I (Db2 Messages)
Target host variables must be specified for a DSNT323I (Db2 Messages)
FETCH NEXT ROWSET statement for a rowset DSNT324I (Db2 Messages)
cursor that is run by the accelerator.
20 -4747 THE CREATE OR ALTER
Option QUERY ACCELERATION or TABLE STATEMENT FAILED
GET_ACCEL_ARCHIVE is used but is invalid BECAUSE SOME FUNCTIONALITY
because the Db2 system parameter ACCEL WAS SPECIFIED IN THE
is set to NO, and the Db2 subsystem is not TABLE DEFINITION THAT IS
enabled for query acceleration. NOT SUPPORTED WITH THE
TABLE TYPE. UNSUPPORTED
21
FUNCTIONALITY:functionality-
Option QUERY ACCELERATION or
keyword.
GET_ACCEL_ARCHIVE is used but
is invalid because the Db2 table
SYSACCEL.SYSACCELERATEDPACKAGES or its Explanation
indexes do not exist or are not defined
An accelerator-only table cannot be defined with the
correctly.
following keywords or clauses:

• APPEND Explanation
• AUDIT The package copy that was specified for the
• BUFFERPOOL APRESOURCE bind option does not exist.
• CHECK constraint package-name
• COMPRESS The name of the package.
• DATA CAPTURE bind-type
The type of bind command.
• DSSIZE
copy-type
• EDITPROC
The type of package copy.
• FIELDPROC
• FOREIGN KEY System action
• GENERATED
• HASH
• IMPLICITLY HIDDEN User response
• IN TABLESPACE
Provide a package name and copy type that exists.
• INLINE LENGTH
• KEY LABEL SQLSTATE
• LOGGED or NOT LOGGED 56067
• MEMBER CLUSTER
Related concepts
• PARTITION BY Package copies for plan management (Db2
• PERIOD Performance)
• PRIMARY KEY Related reference
• TRACKMOD APREUSESOURCE bind option (Db2 Commands)
• UNIQUE -4750 csect-name PACKAGE package-
• VALIDPROC name SWITCH TO THE copy-
• VOLATILE indicator COPY FAILED. THIS COPY
IS NOT EXECUTABLE WITHOUT AN
• WITH DEFAULT EXPLICIT REBIND OR AUTOBIND
(REASON = reason-code).
System action
The package copy specified is invalid because VALID
Programmer response = 'N', or because the package copy was bound in a
release earlier than DB2 10.
Respond to this message in one of the following ways:
csect-name
• Reissue the CREATE TABLE statement without The name of the control section that issued the
specifying the unsupported functionality given in the message.
message token functionality-keyword.
package-name
The name of the package.
SQLSTATE
reason-code
429CB A numeric value that indicates why the copy is not
executable.
-4749 PACKAGE = package-name
bind-type ERROR WITH 01
APREUSESOURCE(copy-type), THE The copy is invalid.
copy-type COPY DOES NOT EXIST 02
The copy is from a prior release that is no
longer executable without an explicit REBIND
or automatic bind.

The command cannot be completed. The package is not rebound.
User response SQLSTATE

Use a package copy where SYSPACKAGE.VALID='Y' 56095
and the RELBOUND value corresponds to DB2 10
Related tasks
or later. Alternately, you can use REBIND PACKAGE
with APREUSE(ERROR) and specify a particular copy Reusing and comparing access paths at bind
with the APREUSESOURCE option to optimize the and rebind (Db2 Performance)
statement by using the access path as input. Related reference
APCOMPARE bind option (Db2 Commands)
SQLSTATE APREUSE bind option (Db2 Commands)
EXPLAIN bind option (Db2 Commands)
56067
Related information
Related concepts DSNT336I (Db2 Messages)
Automatic rebinds (Db2 Application
programming and SQL) -4753 function-name FUNCTION
Related tasks FAILURE, RC=return-code
Reverting to saved access paths for static SQL REASON=reason-code WAS
statements (Db2 Performance) RECEIVED FROM z/OS UNICODE
SERVICES
-4751 bind-type FOR PACKAGE =
package-name FAILED BECAUSE Explanation
OF THE USE OF keyword. ONE
OR MORE STATEMENTS WERE NOT An error was detected while using z/OS Unicode
SUCCESSFULLY PROCESSED. Services.
function-name
Explanation The name of the function that could not be
processed.
The subcommand failed because APCOMPARE or
return-code
APREUSE was not successfully processed for remote
The return code that was issued by z/OS Unicode
BIND or REBIND PACKAGE. This message is issued
Services.
for remote BIND or REBIND only. One of the following
conditions occurred: reason-code
The reason code that was issued by z/OS Unicode
• APCOMPARE(ERROR) was specified and the use of Services.
APCOMPARE resulted in some statements where
comparison is not successful or comparison could
not be performed. System action
• APREUSE(ERROR) was specified and the use of The statement cannot be processed.
APREUSE resulted in some statements where
APREUSE is either not successful or partially System programmer response
successful, or APREUSE could not be performed, or
APREUSE was suppressed by other hints. Correct the condition that is described by the return-
code and reason-code values that were received from
bind-type
z/OS Unicode Services.
The type of bind command: BIND or REBIND
package-name
The name of the package, in the format location-
SQLSTATE
id.collection-id.package-id. 560DC
keyword Related reference
APCOMPARE or APREUSE. Return code meanings (z/OS: Unicode Services
User’s Guide and Reference)

-4755 AUTHORIZATION ID auth-id IS Explanation
NOT AUTHORIZED TO ACCESS KEY A data change operation was specified for a system-
LABEL key-label-name SPECIFIED period temporal table and an invalid combination of
IN SQL sql-statement STATEMENT replication overrides are in effect. The error can be
FOR object-name. issued for the following operations.
RACROUTE FASTAUTH REQUEST
FAILED WITH SYSTEM An insert or update operation specified a value
AUTHORIZATION FACILITY for a row-begin, row-end, transaction-start-ID, or
RETURN CODE saf-return-code a generated expression column, and a replication
SECURITY SERVER RETURN CODE override setting is not in effect for the application
security-server-return-code compatibility level.
SECURITY SERVER REASON CODE • For an application that is run with application
security-server-reason-code. compatibility 502 (or lower), the
SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPO
Explanation RALHISTORY stored procedure was not invoked
before the data change operation and the
key-label-name is specified in the SQL statement SYSIBMADM.REPLICATION_OVERRIDE built-in
statement for object-name that can be used during global variable is set to 'Y'. This combination is not
allocation of the data set associated with the object. supported.
Authorization ID auth-id does not have access in the
• For an application that is run with application
security server to use the key-label-name.
compatibility 503 (or higher), the
auth-id SYSIBMADM.REPLICATION_OVERRIDE built-in
The authorization ID that must be permitted global variable is set to 'N' and the
access to the key label being used. SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPO
key-label-name RALHISTORY stored procedure has been invoked.
The key label specified for the data set. This combination is not supported.
object-name A delete operation was specified for a system-

The name of the data set encrypted. period temporal table and an invalid combination of
replication overrides are in effect.
saf-return-code
The error code that was returned from system • For an application that is run with application
authorization facility (SAF). compatibility 502 (or lower), the
security-server-return-code SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPO
The return code that was returned from a security RALHISTORY stored procedure was not invoked and
server such as RACF. the SYSIBMADM.REPLICATION_OVERRIDE built-in
global variable is set to 'Y'. This combination is not
security-server-reason-code supported.
The reason code that was returned from a security
server such as RACF. • For an application that is run with application
compatibility 503 (or higher), the
statement SYSIBMADM.REPLICATION_OVERRIDE built-in
The statement that can't be processed. global variable is 'N' and the
SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPO
System action RALHISTORY stored procedure has been invoked.
Programmer response: System action
To correct the error, permit access by the authorization
ID to the key label in the security server. The statement cannot be processed.

Change your application in one of the following ways:
42527
• Use a valid replication override for the application
-4756 INVALID COMBINATION OF compatibility level that is in effect
REPLICATION OVERRIDES IN
EFFECT WHEN A DATA CHANGE
OPERATION IS ATTEMPTED

• Run the application at an application compatibility you entered is not valid for one of the following
level that is appropriate for the replication override reasons:
that is used by the application
• The name is not defined to be a table designator in
this SQL statement.
SQLSTATE • The table designator cannot be referenced where it
428IC is specified in the SQL statement.
-4758 INVALID SPECIFICATION ON • An unexposed name is used as a table-designator.

CREATE STATEMENT. (REASON In this case, the statement does not conform to the
CODE reason-code) guidelines for using only unique exposed names as
qualifiers.
• An alias or synonym cannot be used as a table
Explanation
designator.
The CREATE PROCEDURE statement included an
invalid specification. This error is issued for the
situation identified by the reason code. System action
reason-code The statement cannot be processed.
01
The SPECIFIC clause was specified with a value
Programmer response
that is not the same as the procedure name. The
specific name for a procedure must be the same as Correct the syntax and resubmit the statement.
the procedure name.
02 SQLSTATE
A CREATE statement with an OR REPLACE clause
attempted to replace an existing procedure. A 42703
procedure with the same name exists, but is a Related concepts
different type of procedure than what is specified Resolution of column name qualifiers and
in the CREATE statement. An external procedure column names (Db2 SQL)
can only be replaced if the new definition is
Related reference
also for an external procedure. Likewise, a native
SQL procedure can only be replaced if the new RID (Db2 SQL)
definition is also for a native SQL procedure. ROW CHANGE expression (Db2 SQL)
03 -5012 HOST VARIABLE host-variable
A CREATE statement with an OR REPLACE or IS NOT EXACT NUMERIC WITH
SPECIFIC clause was specified on a CREATE SCALE ZERO
PROCEDURE statement for an external SQL
procedure.
Explanation
System action A host variable was specified in one of the following
statements, but it is not valid in the context in which it
The SQL statement cannot be executed. was used.
Programmer response: • In a FETCH statement, as part of an ABSOLUTE or
Correct the identified problem with the statement and RELATIVE position definition
retry the statement.
• In a MERGE, FETCH, or INSERT statement, as part of
a ROWS clause
SQLSTATE
host-variable
530A3 The name of the host variable.
-5001 TABLE table-name IS NOT VALID The host variable was not usable for one of the
following reasons:
Explanation • It is not an exact numeric type.
The table designator was specified as the operand of • The scale is not zero.
the built-in function RID, ROW CHANGE TIMESTAMP
expression, or ROW CHANGE TOKEN expression. The
table designator that you specified or the table name

System action 20
No index expression-based index can be
The statement cannot be processed. created after the inline length is altered until
the base table is reorganized.
Change the host variable to be an exact numeric with a A CREATE VIEW statement was issued, but
scale of zero. the view cannot be created because a view
cannot be defined on another view for which
an INSTEAD OF trigger exists.
SQLSTATE
52
42618 A CREATE TRIGGER statement was issued,
but the trigger cannot be created because an
Related reference
INSTEAD OF trigger cannot be defined on a
FETCH (Db2 SQL) view that has other views dependent on it, or
INSERT (Db2 SQL) the view references an accelerator-only table,
MERGE (Db2 SQL) or an AFTER trigger cannot be defined on a
table that has a clone defined.
-7008 object-name NOT VALID FOR
62
OPERATION (reason-code)
A DELETE statement with a fetch-clause was
issued, and the target of the statement is
Explanation a view that is defined with an INSTEAD
OF trigger. A DELETE statement with a fetch-
The object that is specified is not valid for the
clause is not supported when issued against
requested operation.
a view that is defined with an INSTEAD OF
object-name trigger.
reason-code System action
by one of the following values: The statement cannot be processed.
10
A CREATE VIEW statement was issued, but Programmer response
the view cannot be created because a view Specify an object for which the operation would be
cannot be defined on another view for which allowed, and reissue the statement.
an INSTEAD OF trigger exists.
17 SQLSTATE
A CREATE TRIGGER statement was issued,
but the trigger cannot be created because an 55019
INSTEAD OF trigger cannot be defined on a -16000 AN XQUERY EXPRESSION
view that has other views dependent on it, or CANNOT BE PROCESSED
the view references an accelerator-only table, BECAUSE THE context-component
or an AFTER trigger cannot be defined on a COMPONENT OF THE STATIC
table that has a clone defined. CONTEXT HAS NOT BEEN
18 ASSIGNED. ERROR QNAME =
A CREATE INDEX or ALTER INDEX statement err:XPST0001
was issued for an index on a table that is not
empty. One of the columns in the index key is a
Explanation
row change timestamp column that was added
to the table after it was created. Issue REORG Static analysis of an expression relies on a component
on the table space containing the table, and of the static context, context-component, that has not
then try to create the index. been assigned a value.
19
A MERGE statement was issued, but the target System action
of a MERGE statement cannot be a view that
has an instead of trigger defined for it. The XQuery expression cannot be processed.

Assign a value to the context-component. The XQuery expression cannot be processed.

10501 Use the correct syntax for the expression.
-16001 AN XQUERY EXPRESSION
STARTING WITH TOKEN token SQLSTATE
CANNOT BE PROCESSED BECAUSE 10505
THE FOCUS COMPONENT OF THE
DYNAMIC CONTEXT HAS NOT -16003 AN EXPRESSION OF DATA
BEEN ASSIGNED. ERROR QNAME = TYPE value-type CANNOT BE
err:XPDY0002 USED WHEN THE DATA TYPE
expected-type IS EXPECTED IN
THE CONTEXT. ERROR QNAME=
Explanation
err:XPTY0004
Evaluation of the expression starting with token token
requires that the focus component of the dynamic Explanation
context be assigned. The token is being considered
as the beginning of a path expression which does not An XQuery expression includes a value of the type
have an associated context item or context sequence. value-type in a context where the expected type is
This might be the result of not specifying an XQuery expected-type. The following situations might cause
context item expression in the passing clause or the this error:
value of the XQuery context item expression is a null
• For a constructor function of an XML Schema atomic
value. Another common cause of this error is that the
type, atomization to its argument must not result in
value in the XPath expression was intended to be a
more than one atomic value.
literal string but delimiting quotation characters are
missing. • The cast of a value of value-type to target expected-
type must be a supported cast.
System action
System action
The XQuery expression cannot be processed.
Programmer response
Programmer response
Pass a value that is not null as the XQuery context item
expression to XMLQuery or XMLExists. Specify a value of the correct type.
SQLSTATE SQLSTATE
10501 10507
-16002 AN XQUERY EXPRESSION HAS -16005 AN XQUERY EXPRESSION

AN UNEXPECTED TOKEN token REFERENCES AN ELEMENT NAME,
FOLLOWING text. EXPECTED ATTRIBUTE NAME, TYPE NAME,
TOKENS MAY INCLUDE: token-list. FUNCTION NAME, NAMESPACE
ERROR QNAME= ERR:XPST0003 PREFIX, OR VARIABLE NAME
undefined-name THAT IS NOT
DEFINED WITHIN THE STATIC
Explanation CONTEXT. ERROR QNAME=
The token that follows text is not valid where it occurs ERR:XPST0008
in the expression. The token-list includes one or more
possible tokens that are valid replacements for the Explanation
unexpected token.
During the static analysis phase, the static context
is used to resolve element names, attribute names,
type names, function name, namespace prefixes, and

variable names. If an expression uses an undefined- System action
name that is not found in the static context, a static
error is raised. The XQuery expression cannot be processed.

The XQuery expression cannot be processed. Try one of the following actions:
• Verify that you are passing the correct number of
Programmer response parameters to the function call.
Use a name that is defined within the static context. • If the function call uses a function name with no
If the QName includes a prefix, verify that the prefix, verify that the local name of the function
namespace prefix has been bound to a namespace matches a function that is in the default function
through a namespace declaration. If the error resulted namespace, or use the correct prefix.
from a variable reference, verify that the variable is
in-scope for the expression. SQLSTATE
10506
SQLSTATE
-16011 THE RESULT OF
10506 AN INTERMEDIATE STEP
-16007 -16007 THE XQUERY PATH EXPRESSION IN AN XQUERY
EXPRESSION REFERENCES AN PATH EXPRESSION CONTAINS AN
AXIS axis-type THAT IS NOT ATOMIC VALUE. ERROR QNAME =
SUPPORTED. ERROR QNAME = err:XPTY0019
err:XQST0010
Explanation
Explanation Each intermediate step in an XQuery expression
The axis-type that is specified is not supported must evaluate to a sequence of XQuery nodes. Such
because Db2 XQuery does not support the Full Axis sequences might be empty. They must not include any
Feature. The supported axes include child, attribute, XQuery atomic values.
descendant, self, descendant-or-self, and parent.
System action
System action The XQuery expression cannot be processed.
Programmer response
Programmer response Modify the expression to ensure that each
Specify an axis that is supported. intermediate step in an XQuery expression returns a
sequence of nodes.
SQLSTATE
SQLSTATE
10505
10507
-16009 AN XQUERY FUNCTION NAMED
function-name WITH number-of- -16012 THE CONTEXT ITEM IN AN AXIS
parms PARAMETERS IS NOT STEP MUST BE A NODE. ERROR
DEFINED IN THE STATIC QNAME = err:XPTY0020
CONTEXT. ERROR QNAME=
err:XPST0017 Explanation
In an axis step, the context item, which is the item
Explanation currently being processed, must be a node of the
In a call to the function function-name, the expanded XQuery Data Model.
QName and number-of-parms do not match the
function name and number of parameters of a function
signature in the static context.

System action -16016 THE ATTRIBUTE NAME attribute-
name CANNOT BE USED MORE
The XQuery expression cannot be processed. THAN ONCE IN AN ELEMENT
CONSTRUCTOR. ERROR QNAME =
Programmer response err:XQTY0025
Modify the axis step or the input to ensure that the
context item is a node. Explanation
An XQuery expression uses an attribute-name more
SQLSTATE than once in an element constructor. This is not
allowed because the attribute names that are used in
10507
an element constructor must be unique.
-16015 AN ELEMENT CONSTRUCTOR
CONTAINS AN ATTRIBUTE NODE System action
NAMED attribute-name THAT
FOLLOWS AN XQUERY NODE THAT The XQuery expression cannot be processed.
IS NOT AN ATTRIBUTE NODE.
ERROR QNAME = err:error-name Programmer response
Specify a unique name for each attribute.
Explanation
The content sequence of an element constructor SQLSTATE
contains an attribute node that follows anXQuery node
that is not an attribute node. 10503
attribute-name -16020 THE CONTEXT NODE IN A PATH

The name of the attribute node. EXPRESSION THAT BEGINS WITH
AN INITIAL "/" OR "//" DOES
err:error-name
NOT HAVE AN XQUERY DOCUMENT
The error. Expected values are:
NODE ROOT. ERROR QNAME =
err:XQTY0024 err:XPDY0050
The content sequence of an element
constructor contains an attribute node that
Explanation
follows an XQuery node that is not an attribute
node. Attribute nodes can occur only at the The root node above the context node in an absolute
beginning of the content sequence. path expression (The symbols / or // at the beginning
err:XUTY0004 of the path expression) must be an XQuery document
The content of an insertion sequence based on node.
the source expression of an insert expression
or a replace expression contains an attribute System action
node that follows an XQuery node that is not an
attribute node. Attribute nodes can occur only The XQuery expression cannot be processed.
at the beginning of the insertion sequence.
Programmer response
System action Change each path expression that begins with an initial
The XQuery expression cannot be processed. "/" or "/ /" so that the context node has a root node
that is an XQuery document node.
Programmer response
SQLSTATE
Modify the content sequence to ensure that attribute
nodes follow other attribute nodes. 10507
-16022 OPERANDS OF TYPES xquery-
SQLSTATE data-types ARE NOT VALID
FOR OPERATOR operator-name .
10507 ERROR QNAME = err:XPTY0004

One or both operands of the operator have invalid data 10503
types. The following situations might cause this error:
-16024 THE NAMESPACE PREFIX prefix-
• The types of the operands are not a valid name CANNOT BE REDECLARED
combination for the given operator. For example, OR CANNOT BE BOUND TO THE
the operands of an arithmetic operator are not of SPECIFIED URI. ERROR QNAME =
numeric types. Or a comparison operator compares err:XQST0070
xs:string with xs:integer.
• One or both operands of an arithmetic operator are Explanation
a sequence of more than one items, but the given
operator requires single item operands. The notation A namespace declaration cannot redeclare the
(item(), item()+) represents the type of a sequence of predefined namespace prefixes XML or XMLNS. If the
more than one item. prefix name is not XML, then it cannot be bound
to the namespace URI 'http://www.w3.org/XML/1998/
• The content sequence of a document node namespace'. No prefix can be bound to the namespace
constructor (e.g XMLDOCUMENT) cannot contain URI 'http://www.w3.org/2000/xmlns/' either.
attribute nodes.
System action
System action
Programmer response
Programmer response
Perform one of the following actions:
Use operands that have the correct types for the
operator. • If the prefix name is XML or XMLNS, then change
the prefix name to a different namespace prefix or
remove the namespace declaration.
SQLSTATE
• If the namespace URI is 'http://www.w3.org/XML/
10507 1998/namespace' or 'http:// www.w3.org/2000/
-16023 THE XQUERY PROLOG xmlns/', then change the namespace URI specified
CANNOT CONTAIN MULTIPLE in the declaration of the namespace prefix.
DECLARATIONS FOR THE SAME
NAMESPACE PREFIX ns-prefix. SQLSTATE
ERROR QNAME = err:XQST0033
10503
Explanation -16026 THE NAME attribute-name IS USED

FOR MORE THAN ONE ATTRIBUTE
The prolog contains multiple declarations for the IN THE CONSTRUCTOR FOR THE
namespace prefix nsprefix. Although a namespace ELEMENT NAMED element-name.
declaration in a prolog can override a prefix that ERROR QNAME=err:XQST0040
has been predeclared in the static context, the same
namespace prefix cannot be declared more than once
in the prolog. Explanation
The name attribute-name in the element element-
System action name cannot be used more than one time. Element
constructors must use unique names for attributes.
attribute-name
The name of the attribute that is not unique.
Programmer response
element-name
Remove any extra declarations for the prefix from the The name of the element that contains non-unique
prolog, or change the prefix that is assigned to the attribute names.
extra declarations. Verify that the prefixes used in the
query reference the correct namespaces.

The XQuery expression is not processed. The XQuery expression includes the syntax indicated
in string that is defined by the standard XQuery
User response language specifications but is not supported in Db2.
System action
Programmer response The XQuery expression cannot be processed.
Update the expression so that all attributes in the

Programmer response
element have unique names.
Remove the unsupported expression starting with the
SQLSTATE syntax string from the XQuery expression.
10503
SQLSTATE
-16029 TWO OR MORE NAMESPACES 10509
WITHIN THE SAME XQUERY
ELEMENT CONSTRUCTOR USE -16032 THE STRING string IS NOT A
THE SAME NAMESPACE VALID URI. ERROR QNAME =
PREFIX prefix-name. ERROR err:XQST0046
QNAME=err:XQST0071
Explanation
Explanation
A namespace declaration or namespace declaration
The namespace prefix prefix-name cannot be used attribute specifies a string value that is not a valid URI.
more than one time in a single XQuery element
constructor. A prefix-name of "xmlns" indicates that System action
more than one default namespace is specified in the
XQuery element constructor. The XQuery expression cannot be processed.
prefix-name
The name of the namespace prefix that is not Programmer response
unique. Specify a string value that is a valid URI. A valid URI
must conform to the generic URI syntax specified by
System action the World Wide Web Consortium (W3C).
The XQuery expression is not processed.
SQLSTATE
User response 10504
No action is required. -16033 THE TARGET DATA TYPE
type-name OF A CASTABLE
Programmer response EXPRESSION IS NOT AN ATOMIC
DATA TYPE DEFINED FOR
Use unique namespace prefixes for local namespace THE IN-SCOPE XML SCHEMA
declarations in the element constructor. Verify that TYPES OR IS A DATA TYPE
the expression does not include more than one local THAT CANNOT BE USED IN A
namespace declaration that has no prefix. CASTABLE EXPRESSION. ERROR
QNAME=err:XPST0080
SQLSTATE
10503
Explanation
The castable expression specifies a target data type
-16031 XQUERY LANGUAGE FEATURE
that cannot be used. The predefined XML schema
USING SYNTAX string IS NOT
types xs:anySimpleType and xdt:anyAtomicType
SUPPORTED
cannot be used as the target type of a castable
expression. If the data type is not one of these

restricted types, then either the data type is not TIMEZONES. ERROR
defined for the in-scope XML schema types or the data QNAME=ERR:FORG0008.
type is not an atomic type.
type-name Explanation
The name of the target data type used in the
The function fn:dateTime includes arguments that
expression.
reference different time zones. The time zone of either
argument might be an explicit part of the value or the
System action result of using the implicit time zone for the XQuery
execution environment for the argument.
User response System action


Make sure that the same time zone is used for both
If the target data type is xs:anySimpleType or
arguments of function fn:dateTime.
xdt:anyAtomicType, specify a different target data type
or remove the castable expression.
SQLSTATE
If the target data type is not defined by the in-scope
XML types, specify a data type that is in scope or 10608
change the XML schema to include the data type.
-16041 AN IMPLICIT OR EXPLICIT
If the target data type is not atomic, specify a different INVOCATION OF THE
target data type or remove the castable expression. fn:boolean FUNCTION IN
THE XQUERY EXPRESSION
SQLSTATE COULD NOT COMPUTE THE
EFFECTIVE BOOLEAN VALUE
10507 OF THE SEQUENCE. ERROR
QNAME=err:FORG0006
-16036 THE URI THAT IS SPECIFIED
IN A NAMESPACE DECLARATION
CANNOT BE A ZERO-LENGTH Explanation
STRING
The effective boolean value of the argument passed
to fn:boolean could not be computed. The effective
Explanation boolean value can be computed only if the sequence
operand is one of the following sequences:
The URI that is specified in a namespace declaration
must be a valid URI that conforms to the generic URI • An empty sequence
syntax specified by the World Wide Web Consortium • A sequence where the value of the first item is a
(W3C). The URI cannot be a zero-length string. node
• A singleton sequence with a value of type xs:string,
System action xdt:untypedAtomic or a type derived from one of
The XQuery expression cannot be processed. these types
• A singleton sequence with a value of any numeric
Programmer response type or derived from any numeric type
Specify a valid URI in the namespace declaration.

System action
SQLSTATE The XQuery expression is not processed.
10504
User response
-16038 THE ARGUMENTS OF
FN:DATETIME HAVE DIFFERENT

Determine the possible expressions within the XQuery Modify the expression to result in a number that does
expression where an effective boolean value is not result in an arithmetic overflow or underflow.
calculated either implicitly or explicitly. An implicit
invocation of the fn:boolean function can occur when SQLSTATE
processing the following types of expressions:
10601
• The logical expressions AND and OR
• An fn:not function invocation -16048 AN XQUERY PROLOG CANNOT
CONTAIN MORE THAN ONE
• The WHERE clause of an FLWOR expression declaration-type DECLARATION.
• Certain types of predicates, such as a[b] ERROR QNAME = error-qname
• Conditional expressions, such as IF
Ensure that the sequence operand of each effective Explanation
boolean value calculation has a valid sequence An XQuery prolog contained more than one declaration
operand, as described in the explanation. of a particular type.
declaration-type
SQLSTATE
The type of declaration. Only one declaration of the
10608 indicated type is permitted in the XQuery prolog.
-16046 A NUMERIC XQUERY EXPRESSION Possible declaration values include:
ATTEMPTED TO DIVIDE BY ZERO. • copy-namespaces
ERROR QNAME = err:FOAR0001
• default element namespaces
• boundary-space
Explanation
error-qname
A division or modulus operation attempted to divide an The XML qualified name (QName) static error,
integer or decimal value by zero. such as err:XQST0055, err:XQST0066, and
err:XQST0068.
System action
The XQuery expression cannot be processed. System action
Programmer response
Use a value for the divisor that is not equal to zero. Programmer response
Remove extra declarations from the prolog.
SQLSTATE
10601 SQLSTATE
-16047 AN XQUERY EXPRESSION 10502
RESULTED IN ARITHMETIC -16049 THE LEXICAL VALUE value IS NOT
OVERFLOW OR UNDERFLOW. VALID FOR THE type-name DATA
ERROR QNAME= err:FOAR0002 TYPE IN THE FUNCTION OR CAST.
ERROR QNAME= err:FOCA0002
Explanation
An arithmetic operation resulted in a number that Explanation
either exceeded the maximum or was below the A cast expression or function call includes a value that
minimum value allowed. does not have the correct lexical form for the type-
name data type.
System action

Try one of the following actions: The XQuery expression was not processed.
• If the error results from a function invocation, verify
that the string parameters used for QNames or local Programmer response
names have the correct lexical form.
Pass a valid float or double value to the datetime
• If the error results from a cast expression, verify that operation.
the source value is not one of the special float or
double values NaN, INF, or -INF.
SQLSTATE
SQLSTATE 10602
10602 -16055 AN ARITHMETIC OPERATION

INVOLVING A DATETIME VALUE
-16051 THE VALUE value OF DATA TYPE RESULTED IN OVERFLOW. ERROR
source-type IS OUT OF RANGE FOR QNAME=ERR:FODT0001.
AN IMPLICIT OR EXPLICIT CAST
TO TARGET DATA TYPE target-type.
ERROR QNAME = err:error-qname
Explanation
An arithmetic operation involving a datetime value
Explanation returned a number that exceeded the maximum value
allowed.
An XQuery expression requires that the value with a
data type of source-type be cast, either implicitly or
explicitly to the target data type target-type. The value
System action
is outside the defined range of values for that data The XQuery expression was not processed.
type.
This error could be returned for a variety of Programmer response
error QNames such as FOAR0002, FOCA0001, or
Modify the XQuery expression so that the result does
FOCA0003.
not exceed the maximum allowed value.
System action
SQLSTATE
10605
Programmer response -16056 AN ARITHMETIC OPERATION

INVOLVING A DURATION VALUE
Change the XQuery expression to use a target data RESULTED IN OVERFLOW. ERROR
type with a range that supports the specific value, or QNAME=ERR:FODT0002.
change the value to be within the defined range of the
target data type.
Explanation
SQLSTATE An arithmetic operation involving a duration value
returned a number that exceeded the maximum value
10602 allowed.
-16052 NAN CANNOT BE USED AS A
FLOAT OR DOUBLE VALUE IN A System action
DATETIME OPERATION. ERROR
The XQuery expression was not processed.
QNAME=ERR:FOCA0005.

Modify the XQuery expression so that the result does
The value "NaN" was passed as an argument to a
not exceed the maximum allowed value.
datetime operation, but that value is not valid for
datetime operations.

SQLSTATE cast is not supported, either remove the expression
or cast the value to a different data type.
10605
• Check for expressions that would result in implicit
-16057 A TIMEZONE VALUE IS NOT VALID. casting with values that may not conform to the data
ERROR QNAME=ERR:FODT0003. type of the implicit cast and add conditions to the
expression to avoid the error.
Explanation
SQLSTATE
An XQuery expression specifies a time zone value that
is less than -PT14H00M or greater than PT14H00M. 10608
-16065 AN EMPTY SEQUENCE CANNOT
System action BE CAST TO THE DATA TYPE
The XQuery expression was not processed. data-type, ERROR QNAME =
err:FORG0006
Programmer response
Explanation
Specify a time zone value that is greater than or equal
to -PT14H00M and less than or equal to PT14H00M. A namespace declaration or namespace declaration
attribute specifies a string value that is not a valid URI.
SQLSTATE
System action
10605
-16061 THE VALUE value CANNOT BE
CONSTRUCTED AS, OR CAST
Programmer response
(USING AN IMPLICIT OR EXPLICIT
CAST) TO THE DATA TYPE Specify a string value that is a valid URI. A valid URI
data-type. ERROR QNAME = must conform to the generic URI syntax specified by
err:FORG0001 the World Wide Web Consortium (W3C).
An XQuery expression attempted to use the value 10608
value as a data-type value but the value is not valid
for the data type. The following situations might cause -16066 THE ARGUMENT PASSED TO THE
this error: AGGREGATE FUNCTION function-
name IS NOT VALID. ERROR
• A value was explicitly passed to a cast function or QNAME = err:FORG0006
specified in a cast expression with a target data type
of data-type.
Explanation
• An expression that included value implicitly cast the
value to the target data type of data-type. Many The argument that was passed to the aggregate
XQuery expressions use implicit casting to process function function-name is not valid because the
the expressions. For example, implicit casting is argument does not meet any of the conditions that are
used in general comparisons of numeric values that required for arguments to the function function-name.
require the values to be of data type xs:double.
System action
System action The XQuery expression cannot be processed.
Programmer response
Programmer response If the function is fn:sum, verify that the following
Try one of the following actions: conditions are met:
• If the error occurs in an expression that casts from • All items in the input sequence must be numeric or
one primitive type to another, verify that casting from derived from a single base type.
the source type to the target type is supported. If the • The type must support addition.

• The values must all be promotable to a single Related concepts
common type if the input sequence contains XQuery prologs and expressions (Db2
numeric values. Programming for XML)
Related reference
SQLSTATE Regular expressions (Db2 Programming for
XML)
10608
-16067 THE FLAGS ARGUMENT VALUE -16069 A REGULAR EXPRESSION
PASSED TO THE FUNCTION ARGUMENT value PASSED TO
function-name IS NOT VALID. THE FUNCTION function-name
ERROR QNAME= err:FORX0001 MATCHES A ZERO-LENGTH
STRING. ERROR QNAME=
err:FORX0003
Explanation
The function function-name includes a value that was Explanation
passed to the function as a regular expression flag
parameter. However, the string that was passed to the The value that was specified for the pattern parameter
function includes characters that are not defined as in a call to the function function-name matches a zero-
flags. length string. A zero-length string is not a valid pattern
for this function because the pattern will never match
a substring in the input string.
Programmer response
Modify the function call to pass in a string argument Programmer response
that contains only characters that are defined as flags.
Valid characters include s, m, i or x. Pass a valid pattern to the function call, or remove the
function call from the expression.
SQLSTATE
SQLSTATE
10609
10609
-16068 THE REGULAR EXPRESSION
ARGUMENT VALUE PASSED TO -16075 THE SEQUENCE TO BE
THE FUNCTION function-name SERIALIZED CONTAINS AN ITEM
IS NOT VALID. ERROR QNAME= THAT IS AN ATTRIBUTE NODE.
err:FORX0002 ERROR QNAME = err:SENR0001
The value that was passed to the function function- A request was made to serialize an XML value. The
name is not valid according to the rules that are XML value is a sequence containing an item that is an
specified for regular expressions in XQuery. These XQuery attribute node. There is no defined sequence
rules are based on the regular expression syntax normalization for an attribute node as an item in
specified for XML Schemas, with some extensions a sequence and therefore the sequence cannot be
added to the syntax to accommodate XQuery. serialized.
One reason that this error can occur is if the regular
expression has more than 64 characters with a code System action
point higher than X'FF'. The statement cannot be processed.

Specify a valid value for the regular expression. Remove any items in the sequence containing just
an attribute node or do not attempt to serialize the
SQLSTATE sequence.
10609
SQLSTATE
2200W

-16080 AN XQUERY expression-type constant must be an updating expression or an empty
UPDATING EXPRESSION IS USED sequence expression.
IN AN INVALID CONTEXT. ERROR
QNAME=err:XUST0001. System action
Explanation
An updating expression is specified in an invalid Programmer response
context.
Ensure that the xquery-update-constant in the
expression-type XMLMODIFY function is an updating expression, or is
The type of expression. the empty sequence expression.
Only the following contexts are valid:
• The xquery-update-constant of an XMLMODIFY SQLSTATE
function. 10702
• The return clause of a FLWOR expression.
Related concepts
• The then and else clauses of a conditional Expressions (Db2 Programming for XML)
statement. The then and else clauses must contain
Related reference
either an updating expression or an empty sequence
expression. XMLMODIFY (Db2 SQL)
• An operand of a comma expression. The operand -16083 INCOMPATIBLE EXPRESSION-

must be either an updating expression or an empty TYPE EXPRESSIONS EXIST IN
sequence expression. THE XQUERY-UPDATE-CONSTANT
IN THE XMLMODIFY FUNCTION.
System action QNAME=err:error-name.

Explanation
Programmer response The xquery-update-constant in the XMLMODIFY
function includes multiple expression-type expressions
Correct the expression that is indicated by expression- that operate on the same target node. These basic
type. Use expression-type only in contexts that allow updating expressions are not compatible, because the
an updating expression. result would be non-deterministic, based on the order
of processing the expression-type expressions.
SQLSTATE error-name
10701 An error identifier that indicates the reason why
the expression is not valid.
Related concepts
XUTY0016
Expressions (Db2 Programming for XML)
The expression-type is a replace expression,
Related reference and there exist at least two replace
XMLMODIFY (Db2 SQL) expressions, without keyword values specified,
that apply to the same target node.
-16081 THE XQUERY-UPDATE-CONSTANT
IN THE XMLMODIFY FUNCTION XUTY0017
IS NOT AN UPDATING The expression-type is a replace value of
EXPRESSION OR AN EMPTY expression, and there exist two or more
SEQUENCE EXPRESSION. ERROR replace expressions, with keyword values
QNAME=err:XUST0002. specified, that apply to the same target node.

The xquery-update-constant in the XMLMODIFY The XQuery expression cannot be processed.
FUNCTION is a non-updating expression other than
an empty sequence expression. The xquery-update-

Programmer response XUDY0020
The value of expression-type is "delete" and the
Change the expression in the xquery-update-constant parent property of the target node of a delete
in the XMLMODIFY FUNCTION to ensure that no two expression is empty.
expression-type expressions have the same target
node. XUTY0022
The value of expression-type is "insert into",
"insert as first into", or "insert as last into" the
SQLSTATE insertion sequence includes attribute nodes
10704 and the target node of an insert expression is a
document node.
Related reference
XUDY0027
XMLMODIFY (Db2 SQL) The value of expression-type is "insert before",
"insert after", "insert into", "insert as first into",
-16085 THE TARGET NODE OF
"insert as last into", "replace", or "replace
AN XQUERY expression-type
value of" and the target node is empty.
EXPRESSION IS NOT VALID.
ERROR QNAME=err:error-name. XUDY0029
The value of expression-type is "insert before"
or "insert after" and the parent property of the
Explanation target node of an insert expression is empty.
The target node of a basic updating expression is not XUDY0030
valid. The value of expression-type is "insert before"
expression-type or "insert after", the insertion sequence
The type of expression. includes attribute nodes, and the parent node
of the target node is a document node.
error-name
An error identifier that indicates the reason why
the expression is not valid. System action
XUTY0005 The XQuery expression cannot be processed.
The value of expression-type is "insert into",
"insert as first into", or "insert as last into" and Programmer response
the target node of an insert expression is not a
single element node or document node. Modify the expression to use a valid target node.
XUTY0006
The value of expression-type is "insert before" SQLSTATE
or "insert after" and the target node of an
10703
insert expression that specifies before or
after is not a single element, text, processing- -16086 THE REPLACEMENT SEQUENCE
instruction, or comment node whose parent OF A REPLACE EXPRESSION
property is not empty. CONTAINS INVALID NODES FOR
XUTY0007 THE SPECIFIED TARGET NODE.
The value of expression-type is "delete" and the ERROR QNAME=err:error-name.
target expression does not return a sequence
of zero or more nodes. Explanation
XUTY0008 A node in the replacement sequence cannot be used
The value of expression-type is "replace" or to replace the target node.
"replace value of" and the target node of a
replace expression is not a single node or is error-name
a document node. An error identifier that indicates the reason why
the expression is not valid.
XUTY0009
The value of expression-type is "replace" and XUDY0010
the parent property of the target node of a The value of keywords are not specified
replace expression is empty. and the target node is not an attribute
node. The replacement sequence must contain
only element, text, comment, or processing

instruction nodes, but at least one item in the Related concepts
sequence is an attribute node. Basic updating expressions (Db2 Programming
XUDY0011 for XML)
The value of keywords are not specified Related reference
and the target node is an attribute node. XMLMODIFY (Db2 SQL)
The replacement sequence must contain only
attribute nodes, but at least one item in the -16088 AN expression-type EXPRESSION
sequence is not an attribute node. HAS A BINDING OF A
NAMESPACE PREFIX prefix-string
System action TO NAMESPACE URI uri-string,
INTRODUCED TO AN ELEMENT
The XQuery expression cannot be processed. NAMED element-name, THAT
CONFLICTS WITH AN EXISTING
Programmer response NAMESPACE BINDING OF
THE SAME PREFIX TO A
Correct the source expression in the WITH clause of DIFFERENT URI IN THE
the replace expression to ensure that the replacement IN-SCOPE NAMESPACES OF
sequence contains only valid nodes for the target THAT ELEMENT NODE. ERROR
node. QNAME=err:XUDY0023.
10706 An expression has introduced a new namespace
-16087 THE RESULT OF APPLYING THE binding for a prefix into an element node that conflicts
UPDATING EXPRESSIONS IN THE with one of the existing namespace bindings of the
XMLMODIFY FUNCTION IS NOT in-scope namespaces of that node.
A VALID INSTANCE OF THE expression-type
XQUERY AND XPATH DATA MODEL. The type of expression.
ADDITIONAL INFORMATION:
prefix-string
information-1, information-2.
The prefix.
ERROR QNAME=err:XUDY0021.
uri-string
The URI in the new namespace binding.
Explanation
element-name
The result of applying the updating expressions The name of the XML element.
contained in the XMLMODIFY function would result
in an invalid instance of the XQuery and XPath data The element node could be the target in the updating
model. expression or the parent of the target in the updating
expression. For example, an insert expression might
information-1 and information-2 insert an attribute into an existing element. If the
Additional information that was provided, which QName of the inserted attribute binds prefix P to some
can help identify the constraint violation in the URI, but an in-scope namespace of the element node
XQuery and XPath data model instance. binds the same prefix P to a different URI, a conflict is
detected and this error is issued.
System action
Programmer response
Modify the updating expressions in the XMLMODIFY Programmer response
function to ensure that the resulting instance of the If the expression is intentionally introducing a new
XDM is correct. namespace binding, modify the expression so that
is uses a namespace prefix that is different from all
SQLSTATE existing prefixes of the in-scope namespaces of the
indicated element. Otherwise, modify the expression
10707 so that the binding of the prefix string uses the same

URI as the existing namespace binding of the in-scope Programmer response
namespaces of the indicated element.
If the expression is intentionally introducing a new
namespace binding, modify the expression so that
SQLSTATE is uses a namespace prefix that is different from all
10708 other prefixes used in the updating expressions of the
same XMLMODIFY function that have the indicated
-16089 AN expression-type EXPRESSION element as the target or parent of an attribute node
AND POSSIBLY OTHER target. Otherwise, modify the expression so that the
UPDATING EXPRESSIONS IN binding of the prefix uses the same URI as the other
AN XMLMODIFY FUNCTION namespace bindings used in the updating expressions
INTRODUCE CONFLICTING of the same XMLMODIFY function that have the
NAMESPACE BINDINGS INTO indicated element as the target or parent of an
AN ELEMENT NAMED element- attribute node target.
name. THE PREFIX prefix-string
IS BOUND TO uri-string
WHILE ANOTHER BINDING OF
SQLSTATE
THE SAME PREFIX USES A 10708
DIFFERENT NAMESPACE URI.
ERROR QNAME=err:XUDY0024. Related reference
XMLMODIFY (Db2 SQL)
Explanation -16246 INCOMPLETE ANNOTATION
The combined effect of updating expressions in the MAPPING AT OR NEAR LINE lineno
XMLMODIFY function has been to introduce conflicting IN XML SCHEMA DOCUMENT uri.
namespace bindings into an element node. REASON CODE = reason-code.
expression-type
The type of expression. Explanation
element-name The annotation mapping the XML schema item near
The name of the XML element. line in uri, to a database object is missing some
information. Possible values for reason code include:
prefix-string
The prefix. 1. A rowset name is not specified or is not fully
uri-string qualified.
The URI in the current namespace binding. 2. Any mapping must specify either a target column or
a condition. Neither a target column nor a condition
is specified.
• Two attributes might have been inserted whose 3. The annotation has an unexpected format.
QNames have the same namespace prefix but
different namespace URIs. The XML schema document can be determined by
matching uri to the SCHEMALOCATION column of table
• If expression-type is "insert" or "replace", the
SYSIBM.XSROBJECTCOMPONENTS.
conflicting namespace bindings might be between
two attribute nodes in the sequence of attribute The XML schema is not enabled for decomposition.
nodes in the insertion sequence or replacement
sequence.
User response
• A namespace binding might have been introduced to
the indicated element for an attribute node that was Modify the annotations in the XML schema. Possible
inserted or replaced by another updating expression actions based on the reason-code include:
in the same XMLMODIFY function. 1. Specify a rowset name or fully qualify the rowset
name.
System action 2. Specify either a target column or a condition.
The XQuery expression cannot be processed. 3. Correct the format of the annotation.
Consult annotated XML schema documentation on the
specified annotation to make sure that all required
components have supplied values.

SQLSTATE SQLSTATE
225DE 225DE
-16247 SOURCE XML TYPE source-data- -16249 THE db2-xdb:expression
type CANNOT BE MAPPED TO ANNOTATION expression AT OR
TARGET SQL TYPE target-data- NEAR LINE lineno IN XML SCHEMA
type IN THE ANNOTATION AT OR DOCUMENT uri IS TOO LONG.
NEAR LINE lineno IN XML SCHEMA
DOCUMENT uri Explanation
String length of the specified expression exceeded the
Explanation
maximum allowed. The XML schema document can be
Annotation at or around line lineno in XML schema determined by matching uri to the SCHEMALOCATION
document uri maps a XML schema type source-data- column of table SYSIBM.XSROBJECTCOMPONENTS.
type to an incompatible SQL type target-data-type.
The XML schema document can be determined by The XML schema is not enabled for decomposition.
matching uri to the SCHEMALOCATION column of table The XSR_COMPLETE invocation fails with this
SYSIBM.XSROBJECTCOMPONENTS. SQLCODE.
The XML schema is not enabled for decomposition.
User response
User response Consult annotated XML schema documentation on
the limit for strings specified in db2-xdb:expression
Consult annotated XML schema documentation on
expression annotations. Correct the expression
compatibility between XML schema types and SQL
appropriately.
types. Correct the annotation appropriately.
SQLSTATE SQLSTATE
225DE
225DE
-16250 THE db2-xdb:defaultSQLSchema
-16248 UNKNOWN ANNOTATION
WITH VALUE schema-name AT
annotation-name AT OR NEAR
OR NEAR LINE lineno IN
LINE lineno IN XML SCHEMA
XML SCHEMA DOCUMENT uri
DOCUMENT uri
CONFLICTS WITH ANOTHER db2-
xdb:defaultSQLSchema SPECIFIED
Explanation IN ONE OF THE XML SCHEMA
DOCUMENTS WITHIN THE SAME
The annotated XML schema document uri contains an
XML SCHEMA.
error in the annotation at or near the line containing
lineno. The unrecognized name given in the annotation
tag is annotation-name. Explanation
The XML schema document can be determined by There can only be one value for the db2-
matching uri to the SCHEMALOCATION column of table xdb:defaultSQLSchema annotation across all XML
SYSIBM.XSROBJECTCOMPONENTS. schema documents that comprise an annotated XML
schema. The specified SQL schema name schema-
System action name at or near the line number lineno in the XML
schema document uri conflicts with another value
The XML schema is not enabled for decomposition. for db2-xdb:defaultSQLSchema annotation in this or
The XSR_COMPLETE invocation fails with this another XML schema document of the XML schema.
SQLCODE. The XML schema document can be determined by
User response SYSIBM.XSROBJECTCOMPONENTS.
Consult annotated XML schema documentation for The XML schema is not enabled for decomposition.
list of legal annotations and their syntax. Correct or
remove the unknown annotation.

User response matching uri to the SCHEMALOCATION column of table
SYSIBM.XSROBJECTCOMPONENTS.
Correct the annotated XML schema such that
all specifications of db2-xdb:defaultSQLSchema are The XML schema is not enabled for decomposition.
consistent.
User response
SQLSTATE Correct the annotated XML schema such that each
225DE rowset name is uniquely associated with exactly one
table across the annotated XML schema documents of
-16251 DUPLICATE ANNOTATION the XML schema.
DEFINED FOR object-name AT OR
NEAR location IN XML SCHEMA
DOCUMENT uri SQLSTATE
225DE
Explanation -16253 THE db2-xdb:condition
There is more than one annotation for object- ANNOTATION condition AT OR
name in the annotated XML schema. A duplicate NEAR LINE lineno IN XML SCHEMA
annotation has been found for this object at or DOCUMENT uri IS TOO LONG.
around location in XML schema document uri.
The XML schema document can be determined by Explanation
SYSIBM.XSROBJECTCOMPONENTS. The length of the string associated with db2-
xdb:condition that starts with condition exceeds the
maximum allowed. The db2-xdb:condition is found
System action at or around line number lineno in XML schema
The XML schema is not enabled for decomposition. document uri. The XML schema document can be
The XSR_COMPLETE invocation fails with this determined by matching uri to the SCHEMALOCATION
SQLCODE. column of table SYSIBM.XSROBJECTCOMPONENTS.
Programmer response
Correct the annotated XML schema by removing the User response
duplicate annotation from the XML schema documents Reduce the size of the condition string for db2-
of the XML schema. xdb:condition in the XML schema document. Consult
annotated XML schema documentation on the limit for
SQLSTATE strings specified in db2-xdb:condition annotations.
225DE
SQLSTATE
-16252 THE db2-xdb:rowSet NAME rowset-
name SPECIFIED AT OR NEAR 225DE
LINE lineno IN THE XML SCHEMA -16254 A db2-xdb:locationPath
DOCUMENT uri IS ALREADY locationpath AT OR NEAR
ASSOCIATED WITH ANOTHER LINE lineno IN XML SCHEMA
TABLE DOCUMENT uri IS NOT VALID
WITH REASON CODE reason-code.
Explanation
A rowset in an annotated XML schema must Explanation
correspond to exactly one table. The rowset A value specified in the annotated schema
declaration at or near line lineno declares an for db2-xdb:locationPath is not valid. The XML
association between rowset rowsetname and the table schema document can be determined by matching
specified in the enclosing db2-xdb:table annotation. uri to the SCHEMALOCATION column of table
The specified rowset has already been associated to SYSIBM.XSROBJECTCOMPONENTS. Possible values
a different table in another db2-xdb:table annotation. for reason code include:
The XML schema document can be determined by

1. Some element or attribute has a namespace prefix of rowset-name, and at the same time declare a table
that is not mapped to a URI. All namespace named rowset-name using a db2-xdb:table annotation.
prefixes used in the location path must have been The XML schema document can be determined by
associated with a namespace in the XML schema matching uri to the SCHEMALOCATION column of table
document containing the annotation specifying this SYSIBM.XSROBJECTCOMPONENTS.
location path.
2. Invalid syntax for a location path.
3. The specified path does not match any possible User response
path from a root node to a location where the
element or attribute may appear in an instance Correct the annotated XML schema by adding a
document. db2-xdb:rowSet child element to the db2-xdb:table
element with name rowset-name. This will explicitly
associate the rowset to the table.
System action
The XML schema is not enabled for decomposition. SQLSTATE
The XSR_COMPLETE invocation fails with this 225DE
SQLCODE
-16257 XML SCHEMA FEATURE feature
SPECIFIED IS NOT SUPPORTED
User response FOR DECOMPOSITION.
Modify the annotations in the XML schema. Possible
actions based on the reason-code include: Explanation
1. Ensure that namespace prefixes in the db2- Decomposition on an XML schema with feature is not
xdb:locationPath are correct or add a declaration supported. This feature is used in the XML schema. In
for the missing namespace. some cases, the presence of the unsupported feature
2. Ensure that the syntax of the value for db2- in the XML schema results in failure to enable for
xdb:locationPath is valid syntax for a location path. decomposition. In other cases, having annotations in
3. Ensure that the value for db2-xdb:locationPath the decomposition namespace on the unsupported
corresponds to a possible path from the root node feature results in failure to enable for decomposition.
to the element or attribute at the end of the
location path. System action
SQLSTATE The XSR_COMPLETE invocation fails with this
225DE SQLCODE.
-16255 A db2-xdb:rowSet VALUE rowset-

name USED AT OR NEAR
User response
LINE lineno IN XML SCHEMA Remove the feature from the XML schema or remove
DOCUMENT uri CONFLICTS WITH the decomposition annotations associated with
A db2-xdb:table ANNOTATION the feature, as appropriate. Consult decomposition
WITH THE SAME NAME. documentation on the restrictions on use of the
specified XML schema feature.
Explanation
The annotated XML schema contains a db2-xdb:table
SQLSTATE
annotation which declares a table named rowsetname, 225DE
but the annotated XML schema does not have any
db2-xdb:rowSet annotation declaration to associate -16258 THE XML SCHEMA CONTAINS
rowsetname to any table. If a rowset is not declared A RECURSIVE ELEMENT
in any db2-xdb:table annotation, it is implicitly WHICH IS AN UNSUPPORTED
associated to a table with the same name qualified FEATURE FOR DECOMPOSITION.
by the value of db2-xdb:defaultSQLSchema. The THE RECURSIVE ELEMENT
annotated XML schema cannot use a db2-xdb:rowSet IS IDENTIFIED AS
annotation that relies on an implicit association elementnamespace : elementname
between a rowset and a table with the same name

OF TYPE typenamespace : Explanation
typename.
The XML schema contains no annotations that map an
XML element or attribute to any column of any table.
Explanation
The XML schema is not enabled for decomposition
XML schemas with recursive elements are since it provides no information for performing
not supported for decomposition. At least decomposition.
one recursive element was found identified
as elementnamespace:elementname of type
typenamespace:typename. User response
The XML schema is not enabled for decomposition. Add annotations to the XML schema so that at least
one XML element or attribute is mapped to a column of
a table.
User response
Remove the use of recursion from the XML schema. SQLSTATE
225DE
SQLSTATE
-16262 THE ANNOTATED XML SCHEMA
225DE HAS NO COLUMNS MAPPED FOR
-16259 INVALID MANY-TO-MANY ROWSET rowsetname.
MAPPINGS DETECTED IN XML
SCHEMA DOCUMENT uri1 NEAR Explanation
LINE lineno1 AND IN XML SCHEMA
DOCUMENT uri2 NEAR LINE The set of annotations involving rowset rowsetname
lineno2. contain no mappings to any column. In order for a
rowset to be target for decomposition, at least one
column must be mapped to some XML element or
Explanation attribute.
The two identified annotations specify an invalid
many-to-many relationship between elements that User response
map to the same rowset. If two element declarations
have a sequence model group as their lowest Add an annotation that maps a column of the specified
common ancestor then only one of the paths from rowset to some XML element or attribute. If the rowset
the element declaration up to that model group is not intended to be a target for decomposition,
can have maxOccurs>1 on one or more elements remove references to the rowset from the annotated
declarations or modelgroups in that path. The XML XML schema.
schema documents can be determined by matching
uri1 and uri2 to the SCHEMALOCATION column of SQLSTATE
catalog view SYSCAT.XSROBJECTCOMPONENTS.
225DE
-16265 THE XML DOCUMENT CANNOT
BE DECOMPOSED USING
User response XML SCHEMA xsrobject-name
Correct the annotations such that there are no many- WHICH IS NOT ENABLED
to-many mappings. Consult annotated XML schema OR IS INOPERATIVE FOR
documentation for rules on mapping elements and DECOMPOSITION.
attributes.
sqlcode: -16259 Explanation
sqlstate: 225DE The XML schema identified by xsrobject-name is not in
the correct state to perform decomposition. The XML
-16260 XML SCHEMA ANNOTATIONS schema could be in one of the following states:
INCLUDE NO MAPPINGS TO ANY
COLUMN OF ANY TABLE. • Not enabled for decomposition (possibly never
enabled)
• Disabled for decomposition

• Inoperative for decomposition because of changes -20003 GBPCACHE NONE CANNOT BE
to the definitions of one or more tables specified in SPECIFIED FOR TABLESPACE OR
the annotations. INDEX IN GRECP
Decomposition can only be performed using XML
schemas that are enabled for decomposition. Explanation
XML decomposition was not started. GBPCACHE NONE was specified on an ALTER
TABLESPACE or ALTER INDEX statement, but the table
User response space, index, or the partition to be altered is in GRECP.
Ensure that the XML schema is enabled for

System action
decomposition before attempting to use it
for decomposition of an XML document. The The statement cannot be processed.
decomposition status of an XML schema can be
checked by selecting the DECOMPOSITION column of
User response
SYSCAT.XSROBJECTS for the XML schema identified
by xsrobject-name. Use the START DATABASE command to recover the
table space or index from the GRECP then STOP
SQLSTATE the table space or index before reissuing the ALTER
statement.
225DE
-16266 AN SQL ERROR OCCURRED SQLSTATE
DURING DECOMPOSITION OF 560A7
DOCUMENT docid WHILE
ATTEMPTING TO INSERT DATA. -20004 8K or 16K BUFFERPOOL PAGESIZE
INFORMATION RETURNED FOR INVALID FOR A WORKFILE
THE ERROR INCLUDES SQLCODE OBJECT
sqlcode, SQLSTATE sqlstate, AND
MESSAGE TOKENS token-list. Explanation
This message is issued when a statement specifies an
Explanation
8K or 16K pagesize in the BUFFERPOOL clause for a
An SQL error occurred during decomposition of an XML workfile object. The error can occur for the following
document with document identifier docid. The error SQL statements:
occurred while attempting an SQL insert operation
• A CREATE or ALTER DATABASE statement.
based on some piece of data from the XML document.
Some possible causes: format of data is incompatible • A CREATE or ALTER TABLESPACE statement.
with the target column's data type; length of data
exceeds column size; providing null value for a System action
column defined as non-null. The sqlcode, sqlstate
and message token list (each token is separated by The statement cannot be processed.
the vertical bar character) are provided. The message
tokens may be truncated. See the corresponding User response
message for the sqlcode for further explanation of the
error. Correct the statement to specify a 4K or 32K
bufferpool pagesize.
The XML document docid was not decomposed.
SQLSTATE
User response
560A8
Check the message associated with the SQLCODE.
Follow the action suggested by that message. See -20005 THE INTERNAL ID LIMIT OF
db2diag.log for complete information about the error limit HAS BEEN EXCEEDED FOR
condition. OBJECT TYPE object-type
SQLSTATE
225DE

Explanation 3
TYPE 1 indexes are no longer supported. Only
An internal ID is used to uniquely identify objects of TYPE 2 can be specified, beginning in DB2
type object-type. The limit for internal IDs for this type version 6.
of object is limit, and this limit has been exceeded.
4
This could occur during a CREATE ALIAS, The
CREATE FUNCTION, CREATE PROCEDURE, CREATE SYSPROC.SET_MAINT_MODE_RECORD_NO_TE
SEQUENCE, CREATE TYPE, or CREATE or ALTER TABLE MPORALHISTORY stored procedure is no
statement that defines an identity column. longer supported beginning with Db2 12
V12R1M503.
System action 5
FL 504 Synonyms are deprecated and cannot
The SQL statement cannot be executed.
be created with application compatibility
V12R1M504 or higher.
Drop objects of object-type that are not being used, FL 504 Hash-organized tables are deprecated
and retry the statement. and cannot be created with application
compatibility V12R1M504 or higher.
SQLSTATE 7
FL 504 Partitioned (non-UTS) table spaces
54035 are deprecated and cannot be created
-20008 ATTEMPT TO USE UNSUPPORTED with application compatibility V12R1M504 or
FEATURE msg-token. REASON higher.
CODE: reason-code 8
FL 504 New tables cannot be created in non-
Explanation UTS table spaces with application compatibility
V12R1M504 or higher.
The statement attempted to use a feature or format
that is not supported.
System action
msg-token
The statement or EXPLAIN operation cannot be
Text that identifies the unsupported feature.
processed.
reason-code
A numeric value that identifies the unsupported
feature: Programmer response
1 Take appropriate action based on the reason-code
The statement attempted to call the value. In most cases, remove references to the
SYSPROC.XSR_COMPLETE stored procedure unsupported clause or keyword from the SQL
and specified 1 for fourth argument value, statement, to avoid using the unsupported feature.
which indicates use of the XML schema For reason-code 2, either migrate the EXPLAIN tables
decomposition feature. The only supported to the current format or redefine them by dropping
value for this argument is 0. The XMLTABLE and re-creating them in the required format. For more
function replaces use of XSR_COMPLETE for information, see Migration step 25: Convert EXPLAIN
XML schema decomposition, which is not tables to the current format (Db2 Installation and
supported beginning in DB2 10. Migration).
2 For reason code 4, update your application to use the
The table that is indicated by msg-token SYSIBMADM.REPLICATION_OVERRIDE built-in global
is defined with a format that is no longer variable instead of the
supported by EXPLAIN. Only one instance SYSPROC.SET_MAINT_MODE_RECORD_NO_TEMPORA
of this message is issued per package for LHISTORY stored procedure.
EXPLAIN tables in supported formats during
bind or rebind.
SQLSTATE
560A9

Related concepts SQLSTATE
Function that Db2 12 no longer supports (Db2
429B2
for z/OS What's New?)
Related reference Related reference
Deprecated function in Db2 12 (Db2 for z/OS Statements (Db2 SQL)
What's New?)
Related information -20019 THE RESULT TYPE RETURNED
FROM THE FUNCTION BODY
+20520
CANNOT BE ASSIGNED TO THE
ATTEMPT TO USE A DEPRECATED FEATURE
DATA TYPE DEFINED IN THE
msg-token. REASON CODE reason-code
RETURNS CLAUSE
DSNH20008I (Db2 Messages)
-20016 THE VALUE OF THE INLINE

Explanation
LENGTH ASSOCIATED WITH The data type of the value returned by the function
object-name IS TOO BIG OR THE body must be assignable to the parameter specified in
INLINE LENGTH CLAUSE IS NOT the RETURNS clause.
ALLOWED IN THE CONTEXT.
System action
Explanation
The inline length that is associated with the distinct
type or column is too large or is invalid in the current
Programmer response
context.
Change the RETURNS type or change the expression
object-name
in the RETURN statement so that the result type of
the expression returned from the function body can be
Possible causes for this error include: made.
• A CREATE TYPE statement specifies the INLINE
LENGTH attribute, but the source data type is not SQLSTATE
LOB.
42866
• A CREATE TABLE statement specifies the INLINE
LENGTH attribute, but the data type is not LOB. -20038 THE STATEMENT COULD NOT
BE PROCESSED BECAUSE
• An ALTER TABLE statement with ADD COLUMN THE STATEMENT CONTAINS
specifies an INLINE LENGTH attribute, but the data THE FOLLOWING INCOMPATIBLE
type is not LOB. CLAUSES OR ELEMENTS:
• A CREATE TABLE statement, an ALTER TABLE keywords1 AND keywords2.
statement with an ADD attribute, or a CREATE TYPE
statement specifies an inline length that is greater
Explanation
than the maximum length.
• An ALTER TABLE statement attempted to alter the The two indicated clauses cannot be specified
inline length of a non-LOB column. together.
• The INLINE attribute is not allowed for basic row keywords1

format (BRF). A clause in the SQL statement.
keywords2
System action A clause in the SQL statement.

System action
User response The statement cannot be processed.

User response
Remove either the keywords1 clause or the keywords2
clause from the statement.

SQLSTATE • No more than one table in the fullselect can contain
a security label column.
42613
• The fullselect must not contain a period
Related reference specification.
Statements (Db2 SQL) • The object that is specified in the FROM clause of the
fullselect cannot be a view with columns of length 0.
-20046 THE SELECTIVITY CLAUSE
FOLLOWING predicate-string CAN • The fullselect cannot contain a reference to a
ONLY SPECIFIED FOR A SPATIAL created global temporary table, a declared global
PREDICATE FUNCTION. temporary table, an accelerator-only table, or
another materialized query table.
Explanation • The fullselect cannot directly or indirectly reference

a base table that has been activated for the row or
The SELECTIVITY clause is specified with a predicate column access control or a base table for which a
that does not include a valid spatial predicate function. row permission or a column mask has been defined.
predicate-string • The fullselect must not refer to host variables or
The predicate string. include parameter markers.
This error is also issued when the SELECTIVITY clause • The fullselect must not refer to global variables.
is specified with the ARRAY_EXISTS predicate. This Additional restrictions when ENABLE QUERY
combination is not supported. OPTIMIZATION is in effect:
• The fullselect must be a subselect.
System action
• The outermost SELECT list of the subselect must not
The statement cannot be processed. reference data that is encoded with different CCSID
sets.
User response • The subselect cannot include the following:
Remove the SELECTIVITY clause that follows the – A special register
predicate. – A scalar fullselect
– A row change timestamp column
SQLSTATE
– A ROW CHANGE expression
428E5 – An expression for which implicit time zone values
Related reference apply (for example, cast a timestamp to a
Search conditions (Db2 SQL) timestamp with time zone)
– The RAND built-in function
-20058 THE FULLSELECT SPECIFIED FOR
– The RID built-in function
MATERIALIZED QUERY TABLE
table-name IS NOT VALID. – A user-defined scalar or table function that is not
deterministic or that has external actions
Explanation – Any predicates that include a subquery
– A row-value-expression in a predicate
The materialized query table definition has specific
rules regarding the contents of the fullselect, and the – A join using the INNER JOIN syntax, or an outer
fullselect that was specified did not conform to these join
rules. – A lateral correlation
table-name – a nested table expression or view that requires
The name of the materialized query table. temporary materialization
General restrictions: The following restrictions apply: – A direct or indirect reference to a table that uses
activated row or column access controls, or a
• The length of each result column of the fullselect table for which row or column access controls
must not be 0. have been defined.
• The fullselect cannot contain a column of a LOB or – A FETCH FIRST clause
XML data type.
– A reference to a global variable

– A collection-derived table (UNNEST) SQLSTATE
– A GROUPING SETS or super-groups clause 560AB
– A reference to the LISTAGG, MEDIAN,
Related reference
PERCENTILE_CONT, or PERCENTILE_DISC
function Statements (Db2 SQL)
• If a table with a security label is referenced, the -20070 AUXILIARY TABLE table-name
security label column must be referenced in the CANNOT BE CREATED BECAUSE
outer select list of the subselect. COLUMN column-name IS NOT A
• If the subselect references a view, the fullselect in LOB COLUMN
the view definition must satisfy all other restrictions.
Explanation
System action
An auxiliary table cannot be created for a non-LOB
The statement cannot be processed. column. A CREATE AUXILIARY TABLE statement must
refer to a LOB column in the associated base table.
Programmer response
System action
Change the fullselect in the CREATE TABLE or ALTER
TABLE statement so that it conforms to the rules listed The statement cannot be processed. The specified
above. table was not created.

428EC Change the name of the column to correctly refer to a
LOB column in the base table.
Related reference
SQLSTATE
53098
-20060 UNSUPPORTED DATA TYPE data-
type ENCOUNTERED IN SQL object- -20071 WLM ENVIRONMENT NAME MUST
type object-name BE SPECIFIED function-name
The data type that was specified in the definition of an The WLM ENVIRONMENT option was not specified on
object is not supported for that type of object. CREATE FUNCTION, CREATE PROCEDURE, or CREATE
TRIGGER for an advanced trigger, and there is no
data-type default WLM environment for the installation.
The data type that was specified.
object-type System action
The type of object: an SQL parameter or variable.
object-name
Programmer response
System action Select a WLM ENVIRONMENT name and include
it in the CREATE FUNCTION statement, CREATE
PROCEDURE statement, or CREATE TRIGGER
statement for an advanced trigger. Contact your
User response system administrator to find out the names of the
WLM environments that have been defined for your
Review the appropriate CREATE statement to
installation.
determine which data types are supported for the
specified object, correct the syntax, and reissue the
statement. SQLSTATE
53099

-20072 csect-name bind-type bind-subtype System action
ERROR USING authorization-id
AUTHORITY. OPERATION IS NOT The package that is specified is not deployed,
ALLOWED ON A package-type rebound, or freed.
PACKAGE package-name
Explanation Use the appropriate rebind subcommand to rebind the
The bind subcommand bind-type with bind-subtype is package:
not valid for the type of package specified for one of • For a trigger package that was created prior to Db2
the following reasons: 12 with new function activated, or a basic trigger,
• The subcommand REBIND TRIGGER PACKAGE can use the REBIND TRIGGER PACKAGE subcommand.
be used only for trigger packages that were created • For an advanced trigger package that was created
prior to Db2 12 with new function activated, or basic starting in Db2 12 with new function activated, use
triggers. the REBIND PACKAGE subcommand.
• The subcommand BIND PACKAGE DEPLOY can be • For any other type of package, use the REBIND
used only for SQL functions or native SQL procedure PACKAGE subcommand.
packages, or for advanced triggers. • To drop a REST SERVICE, use the FREE SERVICE
• The subcommand FREE PACKAGE can be used only subcommand instead of the DROP SERVICE
for packages that are not associated with triggers, statement.
native SQL procedures, or compiled SQL functions.
• The DROP PACKAGE statement cannot be used to SQLSTATE
drop a REST SERVICE package. Use subcommand
56052
FREE SERVICE instead
csect-name -20073 THE FUNCTION function-name
The name of the control section that issued the CANNOT BE ALTERED BECAUSE
message. IT IS REFERENCED IN EXISTING
VIEW OR MATERIALIZED QUERY
bind-type TABLE DEFINITIONS
The type of bind subcommand: REBIND, FREE, or
DROP.
Explanation
bind-subtype
The subtype of bind subcommand: TRIGGER or The function-name in an ALTER FUNCTION statement
DEPLOY. cannot be altered to NOT DETERMINISTIC or
authorization-id EXTERNAL ACTION. It is referenced in one or more
The authorization ID that is attempting the existing view definitions or materialized query table
prohibited action. definitions.
If you are using a trusted context, the token

System action
authorization-id might return a role instead of an
authorization ID. A role is returned if a role was in The statement cannot be processed.
effect and the authorization checking is performed
against the role rather than the authorization ID of
Programmer response
the session when the condition was encountered.
Drop the views that reference the function before
role-name
issuing the ALTER FUNCTION statement. Drop the
The name of the role, in the format: 'Role:
materialized query tables that reference the functions
role-name'
or alter the materialized query tables that reference
package-type the functions into base tables before issuing the ALTER
The type of package: trigger, SQL function, native FUNCTION statement.
SQL procedure, or REST SERVICE.
package-name SQLSTATE
The name of the package, in the format
'collection.package'. 42927

-20074 THE OBJECT object-name CANNOT Programmer response
BE CREATED BECAUSE THE
FIRST THREE CHARACTERS ARE Select a name that does not start with a reserved
RESERVED FOR SYSTEM OBJECTS string.
An attempt was made to create an object, but the 42939
name that was specified cannot be used because it Related reference
begins with reserved characters. Statements (Db2 SQL)
object-name Reserved schema names and reserved words
The name of the object. (Db2 SQL)
The following restrictions apply to object names: Administrative authorities (Managing Security)
Reserved prefix "SYS" -20091 A VIEW NAME WAS SPECIFIED

With a few exceptions, the string "SYS" is not AFTER LIKE IN ADDITION TO THE
permitted in the first three characters of an object INCLUDING IDENTITY COLUMN
name. ATTRIBUTES CLAUSE
This message is also issued for a GRANT
statement in response to an attempt to grant Explanation
the CREATEIN, ALTERIN or DROPIN privileges
The LIKE clause specified the name of a view in
on a schema with the "SYS" prefix. The same
combination with the INCLUDING IDENTITY COLUMN
restrictions apply in this case.
ATTRIBUTES clause. This usage is not supported.
Prefix "DSN"
A database name cannot consist of the string System action
"DSN" followed by five digits.
Role names The statement cannot be processed.
Role names cannot start with any of the following
strings: Programmer response
• ACCESSCTRL Remove the INCLUDING IDENTITY COLUMN
• DATAACCESS ATTRIBUTES clause and resubmit the statement to
copy the existing view definition without the identity
• DBADM column attributes.
• DBCTRL
In the case of DECLARE GLOBAL TEMPORARY TABLE,
• DBMAINT it is possible to get the identity column attributes for
• NONE a column of a view using the AS subselect clause
with INCLUDING IDENTITY COLUMN ATTRIBUTES
• NULL
instead. For example:
• PACKADM
DECLARE GLOBAL TEMPORARY TABLE ....
• PUBLIC AS (SELECT * FROM view-name) DEFINITION ONLY
• SECADM INCLUDING IDENTITY COLUMN ATTRIBUTES
• SQLADM
• SYS SQLSTATE
This condition is similar to the condition reported in 560AD
precompiler message DSNH794I.
-20092 A TABLE OR VIEW WAS
SPECIFIED IN THE LIKE CLAUSE,
System action BUT THE OBJECT CANNOT BE
USED IN THIS CONTEXT
Explanation
The LIKE clause specified the name of a table or view
that is not valid for one of the following reasons:

• If the object is a view, it is not allowed in the LIKE 7
clause because the view includes a ROWID or XML The table has at least one referential constraint
column. This is not supported. defined.
• If the object is a table, it is not allowed in the LIKE 8
clause because it is defined as a clone of another The table is referenced in one of the following
table. definitions:
• The definition of an existing materialized
System action query table
The statement cannot be processed. • The definition of a view when altering to a
system-maintained materialized query table
The table is referenced directly or indirectly
Specify the name of a view that does not contain a
(through a view, for example) in the fullselect.
ROWID column (or distinct type column for which the
source type is ROWID), or specify the name of a table 10
and resubmit the statement. The table is already a materialized query table.
Specify the name of a table that is not a clone table, if 11

you specified a table in the LIKE clause that is defined The number of columns of the existing table
as the clone of another table. does not match the number of columns that
are defined in the select list of the fullselect.
12
SQLSTATE
The data types of the columns of the existing
560AE table do not exactly match the corresponding
columns in the select list of the fullselect.
-20093 THE TABLE table-name CANNOT
BE CONVERTED TO OR FROM A 13
MATERIALIZED QUERY TABLE, OR The column names of the columns of the
THE MATERIALIZED QUERY TABLE existing table do not exactly match the
PROPERTY CANNOT BE ALTERED. corresponding column names in the select list
REASON CODE = reason-code. of the fullselect.
14
Explanation The nullability, default, or other characteristics
of the columns of the existing table do not
The ALTER TABLE statement was not able to make one match the characteristics of the corresponding
of the following changes: columns in the select list of the fullselect.
• Change a table from a materialized query table to a 15
base table. The conversion cannot be performed if the
• Change a base table to a materialized query table. same ALTER TABLE statement has other table
alterations.
• Change the materialized query table properties.
16
reason-code The table is not a materialized query table,
The reason for the message or SQL code, indicated and alteration of materialized query table
by one of the following values: properties was specified.
2 17
The table is not a materialized query table, and The table identifies a base table that is
DROP MATERIALIZED QUERY is specified. activated for row or column access control or
4 for which a row permission or a column mask is
The table has at least one trigger defined. defined.
5 19
The table has at least one check constraint The table cannot be defined as a materialized
defined. query table because it is a system-period
temporal table, a history table, an archive-
6 enabled table, or an archive table.
The table has at least one unique constraint or
index or has hash organization.

System action 15
Perform the other table alterations in an ALTER
The statement cannot be processed. TABLE statement that do not include the ADD
MATERIALIZED QUERY clause.
Take the action that corresponds to the reason-code Take one of the following actions:
value: • Correct the table name to specify a materialized
2 query table.
You do not need to convert this table. No action is • Use the ALTER TABLE statement to convert the
required. table to a materialized query table with the
4 required properties.
Drop any triggers, and resubmit the ALTER TABLE 17
statement. Take one of the following actions:
5 • Deactivate the access control and drop row
Drop any check constraints, and resubmit the permissions and column masks for the table.
ALTER TABLE statement.
• Choose a different base table to convert to a
6 materialized query table.
Drop any unique constraint and unique indexes,
and resubmit the ALTER TABLE statement. 19
7
Drop the referential constraints, and resubmit the • Correct the table name to specify a table that
ALTER TABLE statement. is not a system-period temporal table, a history
8 table, an archive-enabled table, or an archive
Drop the materialized query table that references table.
the table, and resubmit the ALTER TABLE • Alter the system-period temporal table with an
statement. ALTER TABLE statement that includes a DROP
9 VERSIONING clause.
A materialized query table cannot reference itself. • Alter the archive-enabled table with an ALTER
Modify the fullselect to remove the direct or TABLE statement that includes a DISABLE
indirect reference to the table that is being altered. ARCHIVE clause.
10
The operation is not allowed since the table is SQLSTATE
already a materialized query table.
428EW
11
Modify the fullselect to include the correct number Related concepts
of columns in the select list. Archive-enabled tables and archive tables
Modify the fullselect so that the result column Related reference
data types exactly match the data types of the Statements (Db2 SQL)
corresponding existing columns. ALTER TABLE (Db2 SQL)
13
Modify the fullselect so that the result column -20094 THE COLUMN column-name IS
names exactly match the column names of the A GENERATED COLUMN AND
corresponding existing columns. CANNOT BE USED IN THE BEFORE
TRIGGER trigger-name.
14
The table cannot be converted to a materialized
query table unless the nullability characteristics Explanation
can be matched. Create a new materialized query The value for the indicated column is generated using
table instead. an expression and cannot be named in the column
name list of a BEFORE UPDATE trigger or set in a
BEFORE trigger.

column-name reported SQLCODE. Follow the action suggested by
The name of the column. that message.
trigger-name
The name of the trigger. SQLSTATE
56059
System action
-20101 THE FUNCTION function-name
The statement cannot be processed. FAILED WITH REASON reason-
code
User response
Remove either the generated column from the column Explanation
name list or the SET assignment statement that sets The statement attempted to process a function, but
the new transition variable of a generated column, processing failed.
then resubmit the statement.
function-name
The name of the function that could not be
SQLSTATE processed, either a Db2 for z/OS function or a Db2
42989 DLL and routine.
reason-code
-20100 AN ERROR OCCURRED WHEN
A hexadecimal value that indicates the reason for
BINDING A TRIGGERED SQL
the failure. Possible values are Db2 for z/OS codes
STATEMENT. INFORMATION
00E73001, 00E73002, 00E73003, and 00E73004,
RETURNED: SECTION NUMBER :
and the following values:
section-number SQLCODE sqlerror,
SQLSTATE sqlstate, AND MESSAGE 00A0C11C
TOKENS token-list CELAAUTH services attempted to load a DLL
that does not exist. The DLL load failed.
The DLL is identified by the first part of the
Explanation
function-name value: dll-name!routine-name.
During execution of a CREATE TRIGGER statement, the 00A103B0
SQL statements specified in the triggered action are All existing Language Environment®
bound into a trigger package. During that processing, environments are in use and the maximum
an error was discovered in one of those statements. number of Language Environments permitted
section-number has been reached. No additional environments
The section number associated with the failing can be created.
triggered SQL statement. 00A14348
sqlcode During CELAAUTH services infrastructure
The SQLCODE received when binding the initialization, CELAAUTH attempted to load the
statement. 64-bit Language Environment library. However,
sqlstate the load failed.
The corresponding SQLSTATE for the SQLCODE 00D50006
received when binding the statement. The XMLPARSE or DSN_XMLVALIDATE function
token-list might be called implicitly. This reason code
The list of tokens from the original SQL error. This might also be issued when the XMLPARSE
list might be truncated. or DSN_XMLVALIDATE functions are implicitly
invoked.
00D50007
System action
The XMLPARSE or DSN_XMLVALIDATE function
The CREATE TRIGGER statement was not processed. might be called implicitly. This reason code
The trigger and the trigger package were not created. might also be issued when the XMLPARSE
or DSN_XMLVALIDATE functions are implicitly
Programmer response invoked.
00D50008
Use the section number determine the failing triggered The XMLPARSE or DSN_XMLVALIDATE function
SQL statement. Refer to the explanation of the might be called implicitly. This reason code

might also be issued when the XMLPARSE 00E73002
or DSN_XMLVALIDATE functions are implicitly Use the information provided for code
invoked. “00E73002” on page 1210.
00D50009 00E73003
The XMLPARSE or DSN_XMLVALIDATE function Use the information provided for code
might be called implicitly. This reason code “00E73003” on page 1210.
might also be issued when the XMLPARSE 00E73004
or DSN_XMLVALIDATE functions are implicitly Use the information provided for code
invoked. “00E73004” on page 1211.
00D5000A
The XMLPARSE or DSN_XMLVALIDATE function SQLSTATE
might be called implicitly. This reason code
might also be issued when the XMLPARSE 56060
or DSN_XMLVALIDATE functions are implicitly
Related tasks
invoked.
Requesting data sharing environment Db2 SLIP
traps (Collecting data)
System action
-20102 CREATE OR ALTER STATEMENT
FOR ROUTINE routine-name
SPECIFIED THE option OPTION
Programmer response WHICH IS NOT ALLOWED FOR THE
Correct the condition that is described by the reason- TYPE OF ROUTINE
code value.
00A0C11C
Explanation
Make sure that the DLL that is identified An option was specified that is not allowed for the type
by function-name is properly installed and is of routine being created or altered.
accessible to the Db2 subsystem.
• MODIFIES SQL DATA is not allowed for table
00A103B0 functions.
No immediate action is required. If this situation
occurs frequently, consider increasing the LEMAX • ALLOW PARALLEL is not allowed for table functions.
parameter, which controls the maximum number • CARDINALITY is not allowed for non-table functions.
of environments within the Db2 subsystem. • LANGUAGE SQL is not allowed for non-SQL functions
00A14348 or procedures.
Make sure that CELQLIB is in the library load • LANGUAGE specifying something other than SQL is
search path. not allowed for SQL functions or procedures.
00D50006 • LANGUAGE JAVA is not allowed for table functions.
If you determine that your application is not the
source of the error, contact IBM Software Support. • PARAMETER STYLE JAVA is not allowed for table
functions.
00D50007
If you determine that your application is not the • STOP AFTER FAILURE, STOP AFTER n FAILURES,
source of the error, contact IBM Software Support. or CONTINUE AFTER FAILURE are not allowed for
sourced functions or SQL functions.
00D50008
source of the error, contact IBM Software Support. System action
00D50009 The statement cannot be processed.
source of the error, contact IBM Software Support. Programmer response
00D5000A
Remove the option from the statement and reissue the
failing statement.
source of the error, contact IBM Software Support.
00E73001
Use the information provided for code
SQLSTATE
“00E73001” on page 1210. 42849

-20104 AN ATTEMPT TO ALTER A CCSID 1. Drop any existing view or materialized query table
FROM from-ccsid TO to-ccsid definitions that refer to tables contained in the
FAILED identified space.
2. Drop all of the extended indexes created on the
Explanation table.
The statement attempted to alter the CCSID for a 3. Reissue the ALTER statement.
database or table space and the statement failed.
from-ccsid represents the CCSID that is currently in
SQLSTATE
use for the database or table space. 42945
to-ccsid is the CCSID that specified on the alter -20107 HOST VARIABLE OR PARAMETER
statement. NUMBER position-number CANNOT
BE USED AS SPECIFIED BECAUSE
System action REASON reason

Explanation
Programmer response Db2 received data that could not be used as specified
in the statement because it is not convertible to an
The SQL REFERENCE contains a list of CCSIDs that can acceptable format in this machine environment.
be specified on this statement. Only these CCSIDs can
be altered, and then, only to the corresponding value position-number identifies either the host variable
listed in the table. Altering the CCSID of a database number (if the message is issued as a result of an
or table space to a value not listed in the table is not INSERT, UPDATE, MERGE, DELETE, SELECT, SET, or
permitted. VALUES statement), or the parameter number (if the
message is issued as the result of a CALL statement, or
the invocation of a function).
SQLSTATE
reason
42856
01
-20106 THE CCSID FOR THE TABLE IEEE (BFP) floating point instructions or instruction
SPACE OR DATABASE CANNOT BE emulation is not available. This support is called
CHANGED BECAUSE THE TABLE the basic-floating-point-extensions facility, and is
SPACE OR DATABASE ALREADY discussed in detail in .
CONTAINS A TABLE THAT IS
REFERENCED IN EXISTING VIEW, System action
OR MATERIALIZED QUERY TABLE
DEFINITIONS OR AN EXTENDED The statement cannot be processed.
INDEX
Programmer response
Explanation
This host variable or parameter requires machine
An ALTER statement cannot be used to alter the CCSID instructions that are not available on this machine.
for a table space or database that contains a table These instructions must be available to Db2 to
that is referenced in an existing view, or materialized perform the requested operation. Run this statement
query table definitions, or a table that already has an on a machine that is capable of supporting
extended index. the required operations. Contact your system
administrator.
System action
SQLSTATE
53022
Programmer response -20108 A RESULT SET CONTAINS
To alter the CCSID for the specified space, complete AN UNSUPPORTED DATA TYPE
the following steps: IN POSITION NUMBER position-
number FOR CURSOR cursor-name

OPENED BY STORED PROCEDURE Explanation
procedure-name
The following statements cannot be used in the
body of a trigger, global transaction, or user-defined
Explanation function:
Stored procedure procedure-name cannot return one • SAVEPOINT
or more query result sets. cursor-name indicates the
• RELEASE SAVEPOINT
first query result set that the stored procedure cannot
return. The column at position-number in the query • ROLLBACK TO SAVEPOINT
result set contains a data type that is not supported by
the requester or the server. System action
System action
The CALL statement cannot be executed. Programmer response
Programmer response this error does not occur.
Modify the stored procedure at the server to return
result sets that include only data types that are SQLSTATE
supported by the requester. You may also upgrade the
level of code at the requester to one that supports the 3B503
data type(s) that were returned by the server. Related reference
SAVEPOINT (Db2 SQL)
SQLSTATE RELEASE SAVEPOINT (Db2 SQL)
56084 ROLLBACK (Db2 SQL)
-20110 CANNOT IMPLICITLY CONNECT -20117 A WINDOW SPECIFICATION FOR

TO A REMOTE SITE WITH A AN OLAP SPECIFICATION IS NOT
SAVEPOINT OUTSTANDING VALID. REASON CODE = reason-
code.
Explanation
The statement referenced an object at a remote DBMS Explanation
with an alias or a three-part name when an active The window specification (OVER clause) of an OLAP
savepoint exists. Such a reference requires an implicit specification invocation is not correctly specified.
connection to the remote DBMS, which is not allowed
when there is an outstanding savepoint. reason-code
The incorrect specification:
System action 1
RANGE or ROWS is specified without an
The statement cannot be processed. ORDER BY clause in the window specification.
2
Programmer response RANGE is specified and the ORDER BY clause
Either release the savepoint, or move the data. in the window specification includes more than
one sort key expression.
3
SQLSTATE
RANGE is specified and the data type of the
51036 range value cannot be used in a subtraction
expression with the data type of the sort key
-20111 CANNOT ISSUE SAVEPOINT, expression in the ORDER BY clause in the
RELEASE SAVEPOINT, ROLLBACK window specification.
TO SAVEPOINT FROM A
TRIGGER, FROM A USER-DEFINED
FUNCTION, OR FROM A GLOBAL System action
TRANSACTION The statement cannot be processed.

Take the action that corresponds to the reason-code A scrollable result set for a cursor has been returned
value: by a call to a stored procedure, and one or more of
these cursors is not positioned before the first row.
For reason-code:
1 procedure-name
Add a window ORDER BY clause to each The name of the stored procedure.
window specification that specifies RANGE or cursor-name
ROWS. The name of the cursor.
2
Ensure that each window specification that System action
includes RANGE has exactly one sort key
The call to the stored procedure was unsuccessful.
expression in the window ORDER BY clause.
All result set cursors that are defined in the stored
3 procedure were closed before returning to the caller.
For each window specification that includes The scrollable cursor can not be used to fetch from the
RANGE, ensure that the range value can be result set. Actions completed by the stored procedure
subtracted from the sort key expression in the are not rolled back, and any external actions initiated
window ORDER BY clause, which must be a by the stored procedure have completed because the
numeric type or datetime type. For datetime error was detected upon completion of the stored
sort key expressions, the range value must be procedure.
the specific datetime duration decimal type
with the correct precision and scale.
Programmer response
SQLSTATE Modify the content of the stored procedure to ensure
that the result set cursors are positioned before the
428EZ first row before returning to the caller.
-20120 AN SQL TABLE FUNCTION MUST
RETURN A TABLE RESULT. SQLSTATE
560B1
Explanation
Related reference
An SQL function that specifies TABLE in the RETURNS CALL (Db2 SQL)
clause must return a result that is a table.
-20124 OPEN CURSOR cursor FAILED
System action BECAUSE THE CURSOR IS
SCROLLABLE BUT THE CLIENT
The statement cannot be processed. DOES NOT SUPPORT THIS

Either remove the TABLE keyword from the RETURNS The cursor cursor has been defined as scrollable, but
clause to make it a scalar function or specify a the client is downlevel and does not support scrollable
fullselect in the RETURN statement of the TABLE cursors. The DRDA Application Requester is not able to
function body. process scrollable result sets.

428F1 The statement cannot be processed.
-20123 CALL TO STORED PROCEDURE
procedure-name FAILED BECAUSE Programmer response
THE RESULT SET RETURNED
FOR CURSOR cursor-name IS Modify the definition of the cursor to not be scrollable.
SCROLLABLE, BUT THE CURSOR
IS NOT POSITIONED BEFORE THE SQLSTATE
FIRST ROW
560B2

-20125 CALL TO STORED PROCEDURE Programmer response
procedure-name FAILED BECAUSE
THE RESULT SET FOR CURSOR Take the action that corresponds to the reason-code
cursor-name IS SCROLLABLE, BUT value:
THE CLIENT DOES NOT SUPPORT 0
THIS, REASON reason-code. Modify the content of stored procedure procedure-
name to not define result set cursors as scrollable.
Explanation 1
Make sure that fetches performed by the stored
A scrollable result set for a cursor has been returned
procedure do not cause the server to return XML
by a CALL for a stored procedure, but the cursor has
columns as binary XML data.
an attribute or is in a state that prevents it from being
returned to the calling application.
SQLSTATE
procedure-name
The stored procedure that failed. 560B3
cursor-name -20127 VALUE SPECIFIED ON FETCH
The scrollable cursor. STATEMENT FOR ABSOLUTE OR
reason-code RELATIVE IS TOO LARGE FOR
A numeric value that indicates the reason for the DRDA
failure. Possible values are:
0 Explanation
The cursor is scrollable, but the client is The value that was specified after ABSOLUTE or
downlevel and does not support scrollable RELATIVE on a FETCH statement is larger than 64 bits.
cursors. The DRDA Application Requester is DRDA limits this specification to 64 bits.
not able to process scrollable result sets
1
System action
The cursor is declared on a server different
from the one on which the stored procedure The statement cannot be processed.
executes, and it contains one or more columns
with an SQL type of XML. The calling Programmer response
application might be executing on the local
Db2 system or on another DRDA requester Modify the scroll specification on the FETCH
system. The stored procedure executed one statement.
or more remote FETCH requests against the
cursor, and the last remote FETCH request SQLSTATE
had one or more binary XML targets. Because
the cursor is declared on another server, the 54051
last stored procedure FETCH request defines
-20142 SEQUENCE sequence-name
the format of XML data returned by the DRDA
CANNOT BE USED AS SPECIFIED
server to be binary XML. Returning such a
cursor as a result set is not allowed for the
local Db2 system or for the DRDA requester on Explanation
which the calling application is executing.
The sequence was referenced in a context in which it
cannot be used.
System action
sequence-name
The statement cannot be processed. All result set The name of the sequence.
cursors that are defined in the stored procedure were
The sequence was an invalid reference to
closed before returning to the caller. The scrollable
a system-generated sequence object. The
cursor cannot be used to FETCH from the result set.
sequence was generated by the system for
Actions that were completed by the stored procedure
one of the following column types: catalog,
are not rolled back, and any actions that were initiated
identity, or DB2_GENERATED_DOCID_FOR_XML.
by the stored procedure have completed because the
These sequences cannot be referenced in:
error was detected at the end of the execution of the
stored procedure. • An ALTER SEQUENCE statement

• A DROP SEQUENCE statement Explanation
• A COMMENT statement to specify a comment for a The data must be encrypted with a password length
sequence between 6 and 127 bytes.
• A CREATE ALIAS statement to define an alias for a
sequence
System action
• A GRANT or REVOKE statement that references the
sequence The statement cannot be processed.
• A NEXT VALUE or PREVIOUS VALUE expression.

Programmer response
This error can also be issued when Db2 is implicitly
creating a sequence which makes the incomplete Ensure that your password length is between 6 and
definition of an existing alias for a sequence invalid, 127 bytes in length.
because an alias for a sequence cannot be defined on
a system-generated sequence. SQLSTATE
428FC
System action
-20146 THE DECRYPTION FAILED. THE
The statement cannot be processed. DATA IS NOT ENCRYPTED

Specify the name of a user-defined sequence object in The data must be encrypted before it is decrypted.
this context.
System action
SQLSTATE
428FB
-20143 THE ENCRYPTION OR Programmer response
DECRYPTION FUNCTION FAILED,
BECAUSE THE ENCRYPTION Ensure that the data being decrypted has been
PASSWORD VALUE IS NOT SET encrypted using the ENCRYPT_TDES built-in-function.
The ENCRYPTION PASSWORD value is not set. 428FE
-20147 THE ENCRYPTION FUNCTION
System action FAILED. MULTIPLE PASS
ENCRYPTION IS NOT SUPPORTED
Explanation
Programmer response
Data that has already been encrypted, cannot be
Issue the SET ENCRYPTION PASSWORD statement to encrypted again.
set the ENCRYPTION PASSWORD value. The length of
the PASSWORD must be a minimum of 6 bytes and a
maximum of 127 bytes. System action
SQLSTATE
-20144 THE ENCRYPTION IS INVALID Ensure that the data that is being encrypted has not
BECAUSE THE LENGTH OF THE already been encrypted.
PASSWORD WAS LESS THAN 6
BYTES OR GREATER THAN 127 SQLSTATE
BYTES
55048

-20148 A RETURN STATEMENT DOES NOT application encoding scheme is UNICODE, use a UX
EXIST OR WAS NOT INVOKED hexadecimal constant instead of GX.
DURING THE EXECUTION OF
ROUTINE routine-name WITH SQLSTATE
SPECIFIC NAME specific-name.
560B9
Explanation -20165 AN SQL DATA CHANGE
STATEMENT WITHIN A FROM
The SQL function must contain at least one RETURN
CLAUSE IS NOT ALLOWED IN
statement and a RETURN statement must be
THE CONTEXT IN WHICH IT WAS
processed when the function is invoked.
SPECIFIED
routine-name
The name of the routine Explanation
specific-name
The specific function name, which is unique within An SQL data change statement cannot be specified in
the schema the FROM clause in specific contexts.
The SQL data change statement must be the only
System action table-reference in the FROM clause that is used in:
The statement cannot be processed. • the outer fullselect of a SELECT statement (a

subselect)
User response • a SELECT INTO statement

An SQL data change statement cannot be specified
Ensure that a RETURN statement is executed when the
in the FROM clause of a fullselect that is used in the
function is invoked.
default clause of the definition of a global variable.
SQLSTATE
System action
429BD
-20163 HEXADECIMAL CONSTANT GX IS
NOT ALLOWED Programmer response
Change the statement so that the SQL data change
Explanation
statement within a FROM clause is used in a supported
A hexadecimal graphic string constant, GX, was context or is the only table-reference in the FROM
used in a statement when one of the following two clause.
conditions was true:
• The MIXED DATA installation option is set to NO. SQLSTATE
• The application encoding scheme is UNICODE. 428FL
• The GX constant was specified as a column default -20166 AN SQL DATA CHANGE
value in a WITH DEFAULT clause. STATEMENT WITHIN A SELECT
• The GX constant was specified as a limit key value in SPECIFIED A VIEW view-name
an ENDING AT clause. WHICH IS NOT A SYMMETRIC
VIEW OR COULD NOT HAVE BEEN
System action DEFINED AS A SYMMETRIC VIEW

Explanation
Programmer response The target view of the SQL data change statement
within a SELECT statement must be defined WITH
If your data is not graphic, use an X hexadecimal CASCADED CHECK OPTION, or the fullselect in the
constant instead of a GX constant. If your MIXED view definition (or the fullselect of a view definition of
DATA installation option is set to NO, contact your a referenced view) must be able to be defined using
system administrator to set up the installation options WITH CASCADED CHECK OPTION.
properly for use with the GX constant. If your

A symmetric view is a view defined implicitly or SQLSTATE
explicitly with the WITH CASCADED CHECK OPTION.
428FP
System action -20179 THE INSTEAD OF TRIGGER

CANNOT BE CREATED BECAUSE
The statement cannot be processed. THE VIEW view-name IS DEFINED
USING THE WITH CHECK OPTION
Programmer response
Do not use the SQL data change statement within a Explanation
SELECT with the specified view. An INSTEAD OF trigger cannot be defined on a
symmetric view, which is a view defined using WITH
SQLSTATE CHECK OPTION. It also cannot be defined on a view
on which a symmetric view has been defined directly
428FM or indirectly. The view view-name might be the target
-20177 SET DATA TYPE CLAUSE ON ALTER view of the INSTEAD OF trigger, or it might be a view
TABLE SPECIFIED FLOATING that depends directly or indirectly on the target view of
POINT, BUT THIS CHANGE IS the trigger.
DISALLOWED
System action
Explanation The statement cannot be processed. The INSTEAD OF
The SET DATA TYPE clause of an ALTER TABLE trigger was not created.
statement specified floating point as the new data
type. However, there is an existing unique index or Programmer response
constraint that is defined on the column. This type
of change is not allowed when unique indexes or The INSTEAD OF trigger cannot be defined on the view
constraints are defined on the column to be changed. unless the symmetric view is replaced by a view that
is not symmetric. The view has to be dropped and
re-created in order to allow an INSTEAD OF trigger.
Programmer response
Change the statement to specify a different SQLSTATE
compatible data type, and resubmit the statement.
428FQ
SQLSTATE -20180 COLUMN column-name IN TABLE
table-name CANNOT BE ALTERED
530A1 AS SPECIFIED
-20178 VIEW view-name ALREADY HAS
AN INSTEAD OF operation Explanation
TRIGGER DEFINED
The column could not be altered.
Explanation column-name
The view view-name already has an INSTEAD OF
trigger defined for the indicated operation (UPDATE, table-name
DELETE, INSERT). Only one INSTEAD OF trigger can be The name of the table that contains the column.
defined for each operation on the view. Possible reasons for this error include a violation of
one of the following restrictions:
System action • ALTER COLUMN cannot be specified in an ALTER
The statement cannot be processed. The INSTEAD OF TABLE statement if any of the following conditions
trigger was not created. are true:
– The table is defined with DATA CAPTURE
Programmer response CHANGES.
If a new INSTEAD OF trigger is required, drop the

existing trigger and then create the new trigger.

– The column is involved in a referential integrity Programmer response
constraint (either as part of the parent key or
foreign key). Perform one of the following actions:
– The column is involved in an extended index • Change the name of the column in the statement to a
definition. column that can be altered.
– The column has a field procedure defined. • Drop and re-create the table with the necessary
attributes.
– The column is an identity column or a row change
timestamp column. • If the column is used in an index that contains an
expression, drop the index and alter the column with
– The column is a LOB column that is referenced in
the necessary attributes. Then, re-create the index.
an expression-based index, and the change would
reduce the inline length of the column.
– The table is defined as a history table, system- SQLSTATE
period temporal table, archive table, or archive- 428FR
enabled table.
Related concepts
– The column is defined as ROW BEGIN, ROW END,
or TRANSACTION START ID.
– The column is involved in a hash key definition. Related reference
– The table is referenced, directly or indirectly, in ALTER TABLE (Db2 SQL)
the definition of a materialized query table. CREATE TABLE (Db2 SQL)
– The column is a generated expression column.
-20181 COLUMN CANNOT BE ADDED TO
• ALTER COLUMN cannot be specified in an ALTER
INDEX index-name
TABLE statement with either a SET NOT NULL or SET
DATA TYPE clause if the column is defined as part of
a period definition. Explanation
• ALTER COLUMN cannot be specified in an ALTER An attempt was made to add a column to an index, but
TABLE statement with a DROP DEFAULT or SET DATA the column could not be added.
TYPE clause if both of the following conditions are
true: index-name
The name of the index.
– The table is defined with DATA CAPTURE
CHANGES. The column could not be added because of limitations
on the clause specified for the ALTER INDEX
– The subsystem parameter statement:
RESTRICT_ALT_COL_FOR_DCC is set to YES.
ALTER INDEX ADD COLUMN
• SET DATA TYPE cannot be specified in an ALTER
The column cannot be added for any of a variety of
TABLE statement if any of the following conditions
reasons, including those shown below:
are true:
• The index is an auxiliary index.
– The table is a materialized query table.
• The index enforces uniqueness of values for a
– The table has an edit procedure or valid
ROWID column.
procedure.
• The index is a partitioning index, and index-
– The column is involved in an extended index
based partitioning is being used.
definition.
• The index is an XML index.
– VARBINARY was specified as the target data type
and the column is defined with the following • The index is an extended index.
attributes: • The index is defined with a period with the
- As CHAR FOR BIT DATA, VARCHAR FOR BIT WITHOUT OVERLAPS clause.
DATA, or BINARY • The index has at least one INCLUDE column.
- With the DESC attribute in an index • The index enforces a primary key, unique key, or
referential constraint.
System action • The index is required for a temporal referential
constraint.

ALTER INDEX ADD INCLUDE System action
The column cannot be added for any of a variety of
reasons, including those shown below: The statement cannot be processed.
• The index is an auxiliary index.

Programmer response
• The index is a non-unique index.
Change the name of the index to an index for which the
• The index is a partitioning index, and index-
values partitioning clause would be valid, and resubmit
based partitioning is being used.
the statement.
• The index is an XML index.
• The index is an extended index (such as an SQLSTATE
expression-based index).
530A2
• The index is defined with a period with the
WITHOUT OVERLAPS clause. -20183 THE PARTITIONED, ADD
• The index is required for a temporal referential PARTITION, ADD PARTITIONING
constraint. KEY, ALTER PARTITION, ROTATE
PARTITION, OR PARTITION BY
RANGE CLAUSE SPECIFIED ON
System action CREATE OR ALTER FOR table-name
The statement cannot be processed. IS NOT VALID

Change the statement to refer to an index that can A clause was specified for a statement, but the clause
have a column added to it, or drop and re-create the is not valid for the indicated table.
index, including all of the required columns. table-name
SQLSTATE The PARTITIONED, ADD PARTITION, ADD
428FS PARTITIONING KEY, ALTER PARTITION, and ROTATE
PARTITION clauses cannot be specified on ALTER
Related reference TABLE, CREATE INDEX, or CREATE TABLE in the
ALTER INDEX (Db2 SQL) following cases:
-20182 PARTITIONING CLAUSE clause ON • The table is a non-partitioned table.

stmt-type STATEMENT FOR index- • The table is a materialized query table or a
name IS NOT VALID materialized query table is defined on this table. This
restriction does not apply if the clause was an ALTER
Explanation PARTITION clause to alter the limit key or a ROTATE
PARTITION clause to rotate partitions.
The values PARTITIONING clause was not accepted • The table is in a partition-by-growth table space. (If
on CREATE or ALTER INDEX statement for one of the a PARTITION BY size clause was specified on the
following reasons: CREATE TABLE statement, the table is created in a
• On ALTER INDEX, if the table uses table-based partition-by-growth table space.)
CONTROLLED partitioning, or if the index is a • The ENDING clause of the ADD PARTITION clause
partitioning index created in Version 8 or later on the ALTER TABLE statement cannot be specified
releases. for the partition-by-growth table space.
• On CREATE INDEX, values partitioning attributes • The ENDING clause of the ADD PARTITION clause
were specified on a previous CREATE or ALTER on the ALTER TABLE statement must be specified for
TABLE statement for the table. the partition-by-range table space.
• On CREATE INDEX, if the partitioning scheme of the • The index is defined with the BUSINESS_TIME
index is predetermined by that of the underlying WITHOUT OVERLAPS clause.
data.
• The ADD PARTITIONING KEY clause cannot be
• On ALTER TABLE, when altering partition limit key specified if the table is already complete by having
values, if there are any large object (LOB) columns in established either table-based partitioning or index-
the table. based partitioning.

• The ADD PARTITION clause must not be specified • An ATOMIC or NOT ATOMIC clause was
for an implicitly created XML table that is defined specified. However, the statement that was being
with range partitioning. prepared was not an INSERT statement with a
• The ROTATE PARTITION clause cannot be specified multiple-row-insert clause.
if: • A rowset-positioning clause was specified.
However, the statement that was being prepared
– The table definition is incomplete.
was not a select-statement.
– The table contains only one partition.
• A SENSITIVE DYNAMIC clause and SCROLL
clause were specified. However, the content of
System action the query requires the use of a temporary table
for processing.
• A SENSITIVE DYNAMIC clause and an OFFSET
clause, or a FETCH clause were specified.
SQLSTATE
This error can be issued when one of the
428FT
conflicting clauses is specified in the statement
-20185 CURSOR cursor-name IS NOT being prepared and the other clause is specified as
DEFINED TO ACCESS ROWSETS, a prepare attribute; or when one clause is specified
BUT A CLAUSE WAS SPECIFIED as a prepare attribute and the other clause is
THAT IS VALID ONLY WITH specified as part of the declaration of a cursor.
ROWSET ACCESS On an EXECUTE statement:
• A source-row-data clause was specified.
Explanation However, the statement that was being executed
The FOR ROW n OF ROWSET clause was specified on was not an INSERT with a multiple-row-insert
a FETCH statement, but the cursor is not defined for clause or a MERGE statement.
rowset access. • A source-row-data clause was not specified.
However, the statement that was being executed
System action was an INSERT with a multiple-row-insert clause
or MERGE statement and FOR MULTIPLE ROWS
The statement cannot be processed. was specified as part of the ATTRIBUTES clause
on the PREPARE statement.
Programmer response • A multiple-row-insert clause was specified.
Remove the FOR n ROWS clause from the FETCH However, the statement that was being executed
statement, or redefine the cursor for multiple row was not an INSERT statement with a multiple-
access with the WITH ROWSET POSITIONING clause row-insert clause.
on DECLARE CURSOR or PREPARE. • A multiple-row-insert clause was specified.
However, the statement that was being executed
SQLSTATE was not an INSERT statement with a multiple-
row-insert clause that was prepared with FOR
24518 MULTIPLE ROWS specified as part of the
ATTRIBUTES clause on the PREPARE statement.
-20186 A CLAUSE SPECIFIED FOR THE
DYNAMIC SQL STATEMENT BEING • A FOR n ROWS clause was specified. However,
PROCESSED IS NOT VALID the INSERT statement or the MERGE statement
that was being executed also contained a FOR n
ROWS clause.
Explanation
• Host-variable arrays were provided. However,
A clause was not valid for one of the following reasons: the FOR n ROWS clause was not specified
On a PREPARE statement: (on either the EXECUTE or INSERT or MERGE
statement).
• A FOR SINGLE ROW or FOR MULTIPLE ROWS
clause was specified. However, the statement
that was being prepared was not an INSERT
System action
with a multiple-row-insert clause or a MERGE The statement cannot be processed.
statement.

Programmer response valid. For example, this message is issued for the
following reasons:
Remove the clause that was not valid in the context in
which it was used. • The JAR name has the improper format.
• The JAR cannot be installed because it already
SQLSTATE exists.
• The JAR cannot be altered, replaced, or removed
07501
because it does not exist.
PREPARE (Db2 SQL)
The following list shows the possible values for
EXECUTE (Db2 SQL) reason-code-(reason-string):
-20200 THE INSTALL OR REPLACE OF 1 (UNDEFINED JAR)
jar-id WITH URL url FAILED DUE A JAR with the name specified
TO REASON reason-code-(reason- on ALTER_JAVA_PATH, REPLACE_JAR, or
string). REMOVE_JAR does not exist in Db2.
2 (SCHEMA LENGTH)
Explanation In the jar-name parameter, the schema delimiter
period ('.') appears after more than 128 bytes, but
The URL that was specified on the install or replace the schema has a maximum length of 128 bytes.
JAR procedure did not identify a valid JAR file.
3 (NAME LENGTH)
jar-id In the jar-name parameter, more than 128 bytes
Name of the JAR that was specified for appear after the schema delimiter or the default
SQLJ.INSTALL_JAR or SQLJ.REPLACE_JAR schema is used, and the JAR name exceeds the
url maximum length of 128 bytes.
Up to 80 characters of the URL are displayed. 4 (PARSER ERROR)
The following list shows the possible values for During ALTER_JAVA_PATH, INSTALL_JAR, or
reason-code -(reason-string): REMOVE_JAR processing, the Db2 parser was
invoked and returned an error message. This error
1 (FILE NOT FOUND) can occur due to invalid characters or an invalid
No HFS file was found with the name specified. length of the jar-name parameter.
2 (URL FORMAT) 5 (DUPLICATE JAR)
The URL must begin with 'file:/' or 'file://'. A JAR with the name specified on INSTALL_JAR
3 (FILE SIZE) already exists in Db2.
The file must not be larger than 100MB.
System action
User response
User response Take the following actions as appropriate:
Reissue the install or replace the JAR procedure with a • Ensure that the JAR identifier has the correct format.
URL that identifies a valid JAR file.
• If the JAR already exists, remove it before you
reinstall it.
SQLSTATE
• If you want to alter, remove, or replace procedures
46001 within the JAR, ensure that the JAR exists.
-20201 THE INSTALL, REPLACE, REMOVE,
OR ALTER OF jar-name FAILED SQLSTATE
DUE TO REASON reason-code-
46002
(reason-string)
-20202 THE REMOVE OF jar-name FAILED
Explanation AS class IS IN USE
The JAR name jar-name that was specified on the

alter, install, replace, or remove JAR procedure is not

The specified JAR file is currently in use by an existing 46007
routine.
-20204 THE USER-DEFINED FUNCTION
jar-name OR PROCEDURE routine-name
The JAR that is being removed. WAS UNABLE TO MAP TO A
class SINGLE JAVA METHOD
The string, 'CLASS'
Explanation
System action A CREATE or ALTER FUNCTION or PROCEDURE
The statement cannot be processed. statement for routine-name specified a Java method in
the EXTERNAL NAME clause that cannot be used. The
EXTERNAL NAME clause did not contain a matching
User response Java method, or contained more than one matching
Ensure that all routines that reference the JAR file Java method.
that is being removed are dropped, and resubmit the
remove procedure. System action
SQLSTATE
-20203 USER-DEFINED FUNCTION OR The EXTERNAL NAME clause of the identified function
PROCEDURE name HAS A JAVA or procedure must be altered to uniquely identify a
METHOD WITH AN INVALID valid Java method for the routine, or the Java class
SIGNATURE. THE ERROR IS AT OR must be changed to have a single method with the
NEAR PARAMETER number. THE specified or implicit signature.
SIGNATURE IS signature.
SQLSTATE
Explanation
46008
The signature of the java method that was used to
implement the function or procedure was invalid. For -20207 THE INSTALL OR REMOVE OF jar-
example, the method may have parameters that are name SPECIFIED THE USE OF A
not mappable to the parameters on the corresponding DEPLOYMENT DESCRIPTOR.
CREATE PROCEDURE statement.
name Explanation
identifies the specific name of the external Java The DEPLOY or UNDEPLOY parameter of the install or
function or procedure whose signature caused the remove jar procedure for jar-name was non-zero. Use
error of deployment descriptors is not supported, and this
number parameter must be zero.
indicates the position of the parameter within the
signature closest to the error
System action
signature
provides at most the first 100 characters of the The JAR is not installed, or removed.
invalid signature
User response
System action Reissue the INSTALL_JAR or REMOVE_JAR procedure
The statement cannot be processed. call with the DEPLOY or UNDEPLOY parameter set to
zero.
Programmer response
SQLSTATE
Reissue the corresponding CREATE statement
specifying parameters that match the Java method, or 46501
correct the specified procedure or function signature.

-20210 THE SQL STATEMENT CANNOT • In the outer fullselect in the RETURN statement of
BE EXECUTED BECAUSE IT an SQL table function
WAS PRECOMPILED AT A LEVEL An OFFSET or FETCH FIRST n ROWS ONLY clause is
THAT IS INCOMPATIBLE WITH
not allowed:
THE CURRENT VALUE OF THE
ENCODING BIND OPTION OR • In the outer fullselect of a materialized query table
SPECIAL REGISTER definition

The SQL statement was precompiled at a level prior to The statement cannot be processed.
DB2 version 7, but the current value of the ENCODING
bind option or special register does not represent Programmer response
the system EBCDIC CCSIDs. The information that is
necessary to execute the SQL statement is unavailable Correct the failing statement. If the failing statement
for processing, and the SQL statement cannot be is CREATE VIEW, specify the invalid clause in SQL
successfully completed. Additional processing of the statements that refer to the view instead.
SQL statement is terminated.
An application that was precompiled prior to DB2 SQLSTATE
version 7 may not be bound, either implicitly or 428FJ
explicitly, with an ENCODING bind option of anything
other than ENCODING(EBCDIC) or ENCODING(ccsid) -20212 USER-DEFINED ROUTINE name
where ccsid represents the system EBCDIC CCSID. ENCOUNTERED AN EXCEPTION
If the value of MIXED DATA for the system is YES, ATTEMPTING TO LOAD JAVA
then ccsid must be the default EBCDIC mixed CCSID. CLASS class-name FROM JAR
Otherwise, ccsid must be the default EBCDIC single jar-name. ORIGINAL EXCEPTION:
byte CCSID. exception-string

The statement cannot be processed. A Java exception occurred while Db2 was trying to
load a Java class. The error can occur when loading
the class that is identified in the EXTERNAL NAME
Programmer response
clause, or a referenced class.
To correct the situation, you can:
The error can also occur when accessing the installed
• Precompile the program again using the current JAR identified in the EXTERNAL NAME clause, or an
precompiler and reissue the BIND command installed JAR in the Java path of the installed JAR
• Reissue the BIND command using that referenced this class. Possible reasons why this
ENCODING(EBCDIC) or ENCODING(ccsid) where message could occur include:
ccsid represents the system EBCDIC CCSID. • A class was not found.
• An I/O error occurred when the class loader reads
SQLSTATE the JAR file.
560B8 • An SQL error occurred when the BLOB that contains
the JAR file from the Db2 catalog is being read by the
-20211 THE SPECIFICATION ORDER BY, class loader.
OFFSET, OR FETCH FIRST N ROWS
ONLY IS INVALID name
The specific name of the external Java
function or procedure that caused the
Explanation ClassNotFoundException.
An ORDER BY, OFFSET, or FETCH FIRST n ROWS ONLY class-name
clause is not allowed: The Java class that Db2 was trying to load when
• In the outer fullselect of a view definition the error occurred.
• In a subselect that is not the outermost fullselect

jar-name SQLSTATE
The JAR file that the class was being loaded from
(if any JAR files happen to be involved in the class 46502
loading process). -20223 THE OPERATION FAILED.
exception-string ENCRYPTION FACILITY NOT
The partial text of the underlying JAVA AVAILABLE return-code, reason-
exception of the toString(), which resulted in this code
ClassNotFoundException (if any class is found in
the search). Explanation
The encryption facility is not available, or not able to
System action
service the encryption or decryption request.
The statement cannot be processed. A DSNX961
message describing the error will be displayed on the System action
z/OS system console.
Programmer response
Programmer response
Correct the condition that is reported by the exception-
string. If the encryption facility is not installed,
install it before you use the ENCRYPT_TDES,
DECRYPT_BINARY, DECRYPT_BIT, DECRYPT_CHAR,
SQLSTATE
and DECRYPT_DB, HASH_CRC32, HASH_MD5,
46103 HASH_SHA1, HASH_SHA256 functions or data set
encryption. If the encryption facility is installed, verify
-20213 STORED PROCEDURE procedure- that it is working correctly. The return-code and
name HAS RETURNED A DYNAMIC reason-code might give further information about why
RESULT SET, PARAMETER number, this message was issued.
THAT IS NOT VALID
Check for RACF and Db2 messages on the console for
additional information.
Explanation
A Java Stored Procedure has either returned a SQLSTATE
DYNAMIC RESULT SET parameter that is not an
instance of the Java class that was used by the 560BF
JDBC driver to represent a ResultSet, or it returned Related reference
a DYNAMIC RESULT SET produced by a nested stored
APPENDIX1.1 Appendix A. ICSF and TSS Return
procedure.
and Reason Codes
procedure-name ENCRYPT_TDES or ENCRYPT (Db2 SQL)
identifies the external Java procedure whose DECRYPT_BINARY, DECRYPT_BIT,
returned parameter caused the error. DECRYPT_CHAR, and DECRYPT_DB (Db2 SQL)
number HASH_CRC32, HASH_MD5, HASH_SHA1, and
indicates the position of the parameter whose HASH_SHA256 (Db2 SQL)
returned class was invalid.
-20224 ENCRYPTED DATA THAT WAS
System action ORIGINALLY A BINARY STRING
CANNOT BE DECRYPTED TO A
The CALL statement fails. CHARACTER STRING

Recreate the Java method to make all returned The DECRYPT_BIT, DECRYPT_CHAR, or DECRYPT_DB
DYNAMIC RESULT SET parameters be instances of function was invoked with an argument that
the class produced by the Db2 Universal JDBC represents an encrypted string that was originally
Driver (com/ibm/db2/jcc/t2zos/SPResultSet), and not a binary string. A binary string cannot be cast
be a DYNAMIC RESULT SET from a nested stored to a character string using the DECRYPT_BIT,
procedure. DECRYPT_CHAR, or DECRYPT_DB function.

The statement cannot be processed. 0Z002
-20232 CHARACTER CONVERSION FROM
Programmer response CCSID from-ccsid TO to-
The encrypted value can only be decrypted using the ccsid FAILED WITH ERROR
DECRYPT_BINARY function. CODE error-code FOR TABLE
dbid.obid COLUMN column-number
REQUESTED BY csect-name
SQLSTATE
22528 Explanation
-20227 REQUIRED CLAUSE IS MISSING A conversion error occurred during the conversion of a
FOR ARGUMENT number OF string to a different coded character set.
expression
from-ccsid
identifies the coded character set of the string to
Explanation be converted.
The expression expression requires that a clause be to-ccsid
specified for argument number number. identifies the coded character set to which it must
be converted.
• If expression is XMLATTRIBUTES, then an AS clause
is required for the XML attribute name. error-code
indicates the type of error as defined as follows:
• If expression is XMLFOREST, then an AS clause is
required for the XML element name. • 8 - Length exception (for example, expansion
required for PC MIXED data exceeds the
maximum length of the string).
System action
• 20 -Conversion procedure error (for example, an
The statement cannot be processed. error during Unicode/390 stage 2 conversions or
an exit set the length control field of the string to
Programmer response an invalid value).
Correct the statement by providing the required clause • 24 - The conversion services have not been
for the argument. setup correctly or the conversion is not
supported.
SQLSTATE dbid.obid
gives the database id and the table obid of the
42633 object with the conversion error. This could be
either the target or the source of the conversion.
-20228 A STACKED DIAGNOSTICS AREA
IS NOT AVAILABLE column-number
gives the column number of the failing object. This
could be either the target or the source of the
Explanation
conversion.
A stacked diagnostics area is only accessible from csect-name
within a handler in a native SQL routine. describes the reason codes returned from Db2.
Reason codes returned from Db2 begin with 'DSN'
System action and identify the context in which the conversion
was requested. Values other than those that
The statement was processed. start DSN' are returned from other Db2 platforms
and are described in the documentation for the
Programmer response platform.
Modify the application logic so that the STACKED
diagnostic is only accessed from within a handler. If System action
the routine is an external SQL procedure, STACKED The statement cannot be processed.
cannot be used.

Programmer response GLOBAL TEMPORARY TABLE statement might be
invalid.
If the error-code is 24 and the conversion request
is correct, you might need to set up character table-name
conversion. The name of the table.
If you suspect an error in Db2, you might need to column-name

report the problem. For information about identifying The name of the column.
and reporting the problem, see Collecting diagnostic reason-code
data (Collecting data). The reason for the message or SQL code, indicated
SQLSTATE 1
The underlying data type of the security label
57017
column is not supported. A security label
Related concepts column must be defined as CHAR(8) for single-
Introduction to character conversion (Db2 byte data.
Internationalization Guide) 2
Related tasks An edit procedure that is defined with row
Setting up Db2 to ensure that it interprets attribute sensitivity was specified for the table
characters correctly (Db2 Internationalization with a security label column.
Guide) 3
A security label column must be defined as
-20235 THE COLUMN column-name NOT NULL WITH DEFAULT.
CANNOT BE ADDED, ALTERED, or
4
DROPPED BECAUSE table-name IS
A security label column DEFAULT cannot be
A MATERIALIZED QUERY TABLE
altered.
5
Explanation A security label column cannot be defined for a
The alter table statement attempted to add, alter, or created global temporary table.
drop column column-name of materialized query table 6
table-name. This is not allowed. The data type of a security label column cannot
be altered.
System action 7
The statement cannot be processed. A security label column cannot be defined for a
table that is the source for a materialized query
table.
Programmer response
8
Columns of materialized query tables cannot be A check constraint cannot specify a security
added, altered, or dropped. Alter the materialized label column.
query table to become a regular table before adding, 9
altering, or dropping a column. A security label column cannot be defined for
an accelerator-only table.
SQLSTATE
428FY System action
-20240 INVALID SPECIFICATION OF A The statement cannot be processed.
SECURITY LABEL COLUMN table-
name.column-name REASON CODE Programmer response
reason-code
Correct the syntax, and resubmit the statement.
Explanation
SQLSTATE
For a security label column the specification of
an attribute in a CREATE TABLE, or ALTER TABLE, 42963
DECLARE GLOBAL TEMPORARY TABLE, or CREATE

-20248 ATTEMPTED TO EXPLAIN Related reference
STATEMENT WITH STMTID SYSDYNQRY catalog table (Db2 SQL)
OR STMTTOKEN ID-token BUT
THE REQUIRED EXPLAIN -20249 THE PACKAGE package-name
INFORMATION IS NOT NEEDS TO BE REBOUND IN ORDER
ACCESSIBLE. REASON reason- TO BE SUCCESSFULLY EXECUTED
code (required-maintenance)
The EXPLAIN statement cannot be executed because A version inconsistency exists between one or more
the required EXPLAIN information is not accessible for SQL statements in a package and the system that is
reason identified by the reason-code value. attempting to process the statement or statements.
ID-token package-name
The identifier or token of the SQL statement. The name of the package that contains the
reason-code statement or statements.
One of the following values: required-maintenance
An IBM APAR number that identifies required
01
maintenance, if applicable.
The current user is not authorized to capture to
invoke EXPLAIN for the qualified statement in Possible reasons for this message include:
the dynamic statement cache.
• The package was bound on a system with an older
02 maintenance level that is no longer supported.
The dynamic statement cache contains no
• The package was bound on a newer maintenance
qualified statements.
level, but it was sent to execute on a system with an
07 older maintenance level.
The current user is not authorized to invoke
• The package contains a static cursor statement that
EXPLAIN for the stabilized dynamic query.
was bound on a system with an older release than
08 the UPDATE or DELETE WHERE CURRENT OF cursor
The SYSIBM.SYSDYNQRY catalog table statement.
contains no qualified statements.
09 System action
The identified statement is not an explainable
statement. The statement cannot be processed.

The statement cannot be processed. Take the action that is indicated by the required-
maintenance value:
Programmer response An APAR number
Review the instructions provided with the
If the reason-code value indicates an authorization indicated APAR, and apply the APAR to the data
problem, complete the following steps: sharing member where the SQL code is issued.
1. Correct the authorization problem and reissue the Any other value
EXPLAIN statement. Rebind the package on a system with the
2. Re-prepare the statement that is to be explained. appropriate maintenance level.
SQLSTATE SQLSTATE
26501 560C5
Related tasks Related concepts
Improving dynamic SQL performance by Considerations for binding packages at a
enabling the dynamic statement cache (Db2 remote location (Db2 Application programming
Performance) and SQL)

REBIND PACKAGE (DSN) (Db2 Commands)
DELETE (Db2 SQL)
UPDATE (Db2 SQL)
Programmer response
-20252 DIAGNOSTICS AREA FULL. NO Drop the INSTEAD OF trigger, and reissue the
MORE ERRORS CAN BE RECORDED statement.
FOR THE NOT ATOMIC STATEMENT
SQLSTATE
Explanation
428G3
A statement with the NOT ATOMIC CONTINUE
ON SQLEXCEPTION clause encountered more errors -20258 INVALID USE OF INPUT
than could be recorded in the diagnostics area. SEQUENCE ORDERING
NOT ATOMIC processing with CONTINUE ON
SQLEXCEPTION allows Db2 to continue processing a Explanation
statement after one or more errors is encountered.
Db2 will continue processing until it is no longer able The ORDER BY clause specifies INPUT SEQUENCE,
to record errors in the diagnostic area (See the GET and the FROM clause of the fullselect does not specify
DIAGNOSTICS statement for information on how to an INSERT or MERGE statement. If the input data is
retrieve error information). When Db2 is no longer not specified using a VALUES clause, or a fullselect
able to record error diagnostics, processing of the with an ORDER BY clause on the outermost fullselect,
statement is terminated, and this error is returned. then the ORDER BY INPUT SEQUENCE clause has no
effect.
System action
System action
The statement is terminated.
Programmer response
Programmer response
Analyze the warning and error conditions using
the GET DIAGNOSTICS statement. Determine how Specify a valid sort key or ensure that the input to the
to change the statement to eliminate or reduce INSERT is a VALUES clause or an ordered fullselect.
the number of warnings and errors. It is up to
the programmer to determine if a ROLLBACK or SQLSTATE
COMMIT should be issued for this message. Either is
appropriate depending on the application logic. 428G4
-20260 THE ASSIGNMENT CLAUSE OF THE
SQLSTATE UPDATE OPERATION AND THE
VALUES CLAUSE OF THE INSERT
429BI OPERATION MUST SPECIFY AT
-20257 FINAL TABLE IS NOT VALID LEAST ONE COLUMN THAT IS NOT
WHEN THE TARGET VIEW view- AN INCLUDE COLUMN
name OF THE SQL DATA CHANGE
STATEMENT IN A FULLSELECT Explanation
HAS AN INSTEAD OF TRIGGER
DEFINED The SQL data change statement specified INCLUDE
columns, and the only assignments are made to
INCLUDE columns. At least one of the assignments in
Explanation a data change statement must be to a column of the
The fullselect includes an INSERT, UPDATE, or MERGE target of the data change statement.
statement that targets a view that has an INSTEAD OF
trigger defined for the SQL data change operation. The System action
FINAL TABLE results of an INSTEAD OF trigger cannot
be returned. The statement cannot be processed.

Change the statement to specify an assignment to a The operation that was attempted could not be
column of the target of the UPDATE operation. performed.

428G5 Ensure the value that was specified for the security
label of this user is a valid security label. If it is valid,
-20264 FOR TABLE table-name, primary-
then this error may be caused if the SECLABEL class in
auth-id WITH SECURITY LABEL
the Security Server has not been activated.
primary-auth-id-seclabel IS NOT
AUTHORIZED TO PERFORM
operation ON A ROW WITH SQLSTATE
SECURITY LABEL row-seclabel. 42501
THE RECORD IDENTIFIER (RID)
OF THIS ROW IS rid-number. -20266 ALTER VIEW FOR view-name
FAILED
Explanation
Explanation
primary-auth-id attempted an MLS READWRITE
operation on a row without having the proper An ALTER VIEW statement was issued for view-name,
Multilevel Security (MLS) authorization. The RID but the view cannot be successfully regenerated.
identifies this row.
The RID might be *N when a RID identifier is not System action
available for the row. The statement cannot be processed.

The operation that was attempted could not be 560C7
performed.
-20267 THE FUNCTION function-name
Programmer response (SPECIFIC specific-name)
MODIFIES SQL DATA AND
If this user is authorized to perform this operation, IS INVOKED IN AN ILLEGAL
ensure that this user has been properly defined CONTEXT. REASON CODE reason-
to MLS. If the row data needs to be viewed, use code
DSN1PRINT.
In the case of a view or cursor, where the primary Explanation
authorization ID is able to access more rows than it
The function is defined with the MODIFIES SQL DATA
can update or delete, you can add the WHERE clause
option. A function that is defined with MODIFIES SQL
to limit the rows accessed, based on the security label
DATA is only allowed in:
of the primary authorization ID. The security label can
be retrieved using GETVARIABLE(SYSIBM.SECLABEL). • VALUES clause of an insert operation
• SET clause of an update operation
SQLSTATE • VALUES statement in a trigger
42512 • SET assignment statement
-20265 SECURITY LABEL IS reason FOR • CALL procedure statement
primary-auth-id function-name
Explanation specific-name
User primary-auth-id has a blank security label, or the The specific function name, which is unique within
security label is not accessible. reason is BLANK or the schema.
INACCESSIBLE.

reason-code 5
A numeric value that indicates the reason for the The name of the XML processing instruction
failure. cannot contain the letter string "xml" in any
1 combination of upper or lower case characters.
The function is referenced in the DEFAULT 6
clause of the definition of a global variable. The name for an argument of XMLTABLE,
XMLQUERY or XMLEXISTS expression is not an
5
XML NCName.
The select list of a fullselect that contains an
OFFSET clause.
System action
Programmer response
Programmer response Correct the XML name and resubmit the statement.
Remove the reference to the function from the
DEFAULT clause of the definition of the global variable. SQLSTATE
42634
SQLSTATE
-20276 The XML namespace prefix xml-
429BL namespace-prefix is not valid.
Related reference Reason code = reason-code
CREATE VARIABLE (Db2 SQL)
CREATE FUNCTION (Db2 SQL) Explanation
The XML namespace prefix violates the constraint that
-20275 The XML NAME xml-name IS NOT is indicated by the reason code.
VALID. REASON CODE = reason-
code xml-namespace-prefix
The XML namespace prefix.
The statement contains an invalid XML name. by one of the following values:
xml-name 1
The invalid name string. The namespace prefix contains a colon.
reason-code 2
by one of the following values: The namespace prefix is named xml or xmlns.
1 3
The value "xmlns" is used either as an attribute Duplicate namespace prefixes were declared.
name or as a prefix for an element or attribute
name. System action
The namespace prefix in a qualified name is
not declared within its scope.
Programmer response
3
The name for an element or attribute is not an Perform the action that corresponds to the reason
XML QName. code.
4 1
The name of the XML processing instruction is Choose a name that does not include a colon.
not an XML NCName.
2
Do not name the namespace prefix xml or xmlns.

3 SQLSTATE
Declare only one namespace prefix.
428G8
SQLSTATE -20281 primary-auth-id DOES NOT

HAVE THE MLS WRITE-DOWN
42635 PRIVILEGE
-20279 THE VIEW view-name CANNOT
BE ENABLED FOR QUERY Explanation
OPTIMIZATION. REASON CODE =
reason-code This operation requires the Multilevel Security write-
down privilege.
Explanation
System action
The view cannot allow the ENABLE QUERY
OPTIMIZATION option because the fullselect does not This operation cannot be performed.
conform to the set of queries that can take advantage
of this capability. Programmer response
view-name Ensure that the user has the MLS write-down privilege
The view that cannot be enabled for query when write-down is in effect.
optimization.
reason-code SQLSTATE
by one of the following values: 42513
1 -20283 A DYNAMIC CREATE STATEMENT
The view directly or indirectly references an CANNOT BE PROCESSED WHEN
existing materialized query. THE VALUE OF CURRENT SCHEMA
2 DIFFERS FROM CURRENT SQLID
The view references a random function or a
function with external action. Explanation
3 A dynamic CREATE statement was issued when
The view is inoperative. the value of the CURRENT SCHEMA special register
contained a value different from the content of the
System action CURRENT SQLID special register.

System action
Perform the action that corresponds to the reason

code. Programmer response
1 Change the value of the CURRENT SCHEMA special
Remove the reference to the materialized query register to be the same as the content of the CURRENT
table. SQLID special register.
2
Remove the following references from the query SQLSTATE
that defines the view: 429BN
• A reference to a random function
-20286 DB2 CONVERTED STRING token-
• A reference to a function with an external action type tokenFROM from-ccsid TO
3 to-ccsid, AND RESULTED IN
Correct the condition that caused the view to be SUBSTITUTION CHARACTERS
inoperative.

Explanation • Binary data was specified with unit. CODEUNITS16,
or CODEUNITS32 are not valid with binary string
A conversion error occurred during the conversion data.
of a string for token-type token to a different coded
character set. One or more substitution characters • Graphic data was specified with OCTETS as the
have been placed in the string during the conversion string length unit. OCTETS is not valid with graphic
process. data.
token-type
The type of token.
System action
token The statement cannot be processed.
The token that was converted.
from-ccsid Programmer response
The coded character set of the string to be Change the invocation of the function to remove the
converted. invalid string length unit or change it to a valid unit for
to-ccsid the data type being processed.
The coded character set to which the string must
be converted.
SQLSTATE
System action 428GC
The statement cannot be processed. -20295 THE EXECUTION OF A BUILT IN

FUNCTION function RESULTED IN
AN ERROR REASON CODE reason-
Programmer response code
Ensure that the data that is provided to Db2 can be
converted from from-ccsid to to-ccsid without data Explanation
loss.
The execution of a built-in function (BIF), function,
If the -20286 code was issued during the conversion resulted in an error. The reason code, reason-code,
of security labels, use only security labels that further explains the reason for the error:
characters that are not substituted during conversion
4
from one CCSID to another. For example, the following
A string longer than allowed returned as a result
national characters might be substituted:
of an UPPER or LOWER function execution. Correct
• @ (X'7C') the usage of the function by using a varying-length
• # (X'7B') string long enough to contain the expanded result.
• $ (X'5B')
System action
428GB
Programmer response
Related concepts
Security labels (Managing Security) Correct the use of the built-in function, function.
Possible consequences of character conversion
(Db2 Internationalization Guide) SQLSTATE
22531
-20289 INVALID STRING UNIT unit
SPECIFIED FOR FUNCTION -20300 THE LIST OF COLUMNS SPECIFIED
function-name FOR THE clause CLAUSE IS NOT
ALLOWED IN COMBINATION WITH
Explanation THE LIST OF COLUMNS FOR THE
PARTITIONING KEY FOR THE
The statement invoked a built-in function using a TABLE.
string unit that is not valid with the type of data that
is provided to the function. This can occur for the
following reasons:

Explanation 6
The pattern expression does not have a name test
The list of columns that was specified for a clause is or kind test following the '/'.
not valid when used with the list of columns of the
partitioning key for the table. 7
The pattern expression uses an unsupported
clause axis in an axis step. Only forward axes child,
The clause that was specified attribute, descendant, self and descendant-or-self
When the PARTITION BY RANGE and ORGANIZE BY are supported.
KEY SEQUENCE clauses are used on the same table 8
and the column list for the PARTITION BY RANGE The pattern expression specifies an invalid kind
clause includes a single column, the hash key must test or some syntax that is not a valid name test or
have that column as its first hash key column kind test supported in a pattern expression.
When the PARTITION BY RANGE and ORGANIZE BY 9
HASH clauses are used on the same table, the column The pattern expression specifies a predicate
list for the PARTITION BY RANGE clause must be (an expression enclosed in square brackets).
identical to or be a subset of the column list for the Predicates are not supported in a pattern
ORGANIZE BY HASH clause and the column names expression of an XMLPATTERN clause.
must be in the same order. 10
The pattern expression includes XQuery syntax
System action that is not supported in an XMLPATTERN clause
and is not specifically covered by one of the other
The statement cannot be processed. reason codes.
11
User response On a z/OS database server, the pattern expression
exceeds the limit of 50 steps if the pattern
Change the list of columns in the appropriate clause or
expression does not contain a function, or 44 steps
clauses.
if it contains a function.
12
SQLSTATE
The argument of the function in the pattern
428GD expression does not conform to the required
syntax, or the index data type is not correct.
-20304 INVALID INDEX DEFINITION
INVOLVING AN XMLPATTERN
CLAUSE OR A COLUMN OF DATA System action
TYPE XML. REASON CODE = The statement cannot be processed.
reason-code
User response
Explanation
Modify the statement based on the reason specified by
A column defined with a data type of XML is included the reason-code. Use one of the following suggestions
(or missing) in the columns for the index. The index to modify the statement:
definition is not valid for one of the following possible
reason codes: 2
If the index is intended as a key for XML data,
2 ensure that only one column defined with a data
An XMLPATTERN clause is present but multiple type of XML is specified. Otherwise, remove the
index columns are specified. XMLPATTERN clause.
4 4
An XMLPATTERN clause is present but the single Either remove the XMLPATTERN clause or change
index column specified is not defined with data the specified column to a single column defined
type XML. with a data type of XML.
5 5
The path expression specified for the Ensure that the pattern expression begins with '/'
XMLPATTERN Clause does not start with a '/' or or '//'. The XQuery syntax for which '/' or '//' is an
'//'. abbreviation is not supported in the XMLPATTERN
clause of the CREATE INDEX statement.

6 TABLE table-name. REASON CODE
Add a name test or kind test following the '/' in the = reason-code
pattern expression.
7 Explanation
Remove any reverse axes from the pattern
expression. For example, 'parent::' must not be The insertion or update of an XML value failed
used as an axes in a pattern expression. during insertion or update of the specified index. The
statement cannot proceed, and the table and index
8 remain unchanged.
Check the pattern expression for kind tests
or name tests that do not match the syntax index-id
specification of the XMLPATTERN clause of the The index ID.
CREATE INDEX statement. Correct or remove table-name
unsupported syntax. The name of the table.
9 reason-code
Remove any predicates from the pattern The reason for the message or SQL code, indicated
expression in the XMLPATTERN clause. by one of the following values:
10 1
Change the pattern expression to remove any One or more XML node values in an XML value
syntax that is not valid according to the syntax being inserted or updated exceeds a length
specification of the XMLPATTERN clause of constraint imposed by the identified index.
the CREATE INDEX statement. If the pattern The index on an XML column is defined to
expression includes an asterisk character (*), use the SQL type VARCHAR with a specific
ensure that the name tests in the pattern length specified. The length of one or more
expression correctly use the wildcard. If used with XMLPATTERN result values exceeds the user-
a Qname, there must be a colon before or after specified length constraint for the VARCHAR
the wildcard character, otherwise it is considered data type.
a multiplication operator. Remove any attempt to
use the asterisk as a multiplication operator from 4
the pattern expression. You should also ensure At least one XML node value is a valid XML
that the XMLPATTERN clause does not include value that cannot be cast to the index data
other XQuery operators, XQuery functions or type for the identified index. That value is
XQuery FLWR (for, let, where, return) expressions. outside the supported range of values.
11 6
Reduce the number of steps in the pattern One or more XML node values are XML values,
expression. If the value that is to be indexed in the but those XML values span multiple records.
XML documents is longer than 50 steps when the Db2 cannot create an index key on an XML
pattern does not contain a function or longer than value that spans multiple records.
44 steps when the pattern does contain a function,
the index cannot be created. System action
Check the argument of the function in the pattern
expression that does not conform to the required
syntax of the XMLPATTERN clause of the CREATE Programmer response
INDEX statement, and check the index data type. Use the following query to determine the table name
Correct or remove unsupported syntax, or modify and index ID:
the index data type.
SELECT NAME as IndexName,
TBNAME as TableName
SQLSTATE FROM SYSIBM.SYSINDEXES
WHERE index-id;
429BS
Take the action indicated by the reason code:
-20305 AN XML VALUE CANNOT BE
INSERTED OR UPDATED BECAUSE 1
OF AN ERROR DETECTED WHEN Use the XML pattern information to identify the set
INSERTING OR UPDATING THE of matching XML nodes to inspect to determine
INDEX IDENTIFIED BY index-id ON

which string values are beyond the limit of the Programmer response
length constraint specified by the index.
Determine the XMLPATTERN clause from the index
4 definition.
Use the XML pattern information to identify the set
of matching XML nodes to inspect and compare 1
against the data type specified for the identified Use the XML pattern information to identify the set
index. Determine which node values exceed the of matching XML nodes to inspect to determine
range of values supported by Db2 for the index which string values are beyond the limit of the
data type. length constraint specified by the index.
6 4
Use the XML pattern information to identify the set Use the XMLPATTERN information to identify the
of matching XML nodes to inspect to determine set of matching XML nodes to inspect and compare
which values might be spanning multiple records. against the data type specified for the index being
Generally, large values might lead to multiple created. Determine which node values exceed the
records. Large values might arise from a single range of values supported by Db2 for the index
large text node, or an element node with many data type.
descendant text nodes.
SQLSTATE
SQLSTATE 23526
23525 -20310 THE REMOVE OF jar-name1
-20306 AN INDEX ON AN XML COLUMN FAILED, AS IT IS IN USE BY jar-
CANNOT BE CREATED BECAUSE name2
OF AN ERROR DETECTED WHEN
INSERTING THE XML VALUES Explanation
INTO THE INDEX. REASON CODE
= reason-code The JAR being removed exists in the JAVA path of
another JAR.
Explanation jar-name1
The JAR being removed.
The statement cannot proceed and the table remains
jar-name2
unchanged. The schema data type and schema
A JAR file that contains a JAVA path with a
identifier are not applicable for all reason codes. See
reference to jar-name1.
specific reason codes for details. The creation of the
index on an XML column failed for one of the following
possible reason codes: System action
One or more XML node values in an XML value
being inserted or updated exceeds a length
User response
constraint imposed by the index that is being
created. The index on an XML column is defined to Remove the dependency by altering the JAVA path for
use the SQL type VARCHAR with a specific length JARjar-name2 so it does not include the reference to
specified. The length of one or more XMLPATTERN jar-name1.
result values exceeds the user-specified length
constraint for the VARCHAR data type. SQLSTATE
4
One or more XML node values is a valid XML value 4600C
but cannot be cast to the index data type for the -20311 THE VALUE PROVIDED FOR THE
index being created because of Db2 limitations. NEW JAVA PATH IS ILLEGAL
Db2 does not support the entire range of XML
values.
Explanation
System action The Java path cannot be resolved for one of the
following reasons:

• The provided value for the Java path is not valid. The MODE or DISALLOW DEBUG MODE with an ALTER
value must be either a blank or a zero-length string. statement.
• The Java path does not conform to its required
syntax. System action
System action
The statement cannot be processed. User response
To change the setting of the DEBUG MODE option, drop
User response and re-create the object with the correct option.
Based on the specific error, correct the Java path by
using one of the following solutions: SQLSTATE
• Change the specified value to a blank or a zero- 55058
length string.
-20314 THE PARAMETER LIST (OR AN
• Change the Java path to conform to its required OPTION) DOES NOT MATCH THE
syntax. PARAMETER LIST (OR OPTION)
FOR ALL OTHER VERSIONS OF
SQLSTATE ROUTINE routine-name
4600D
Explanation
-20312 THE ALTER OF JAR jar-id FAILED
BECAUSE THE SPECIFIED PATH An inconsistency exists between the parameters for
REFERENCES ITSELF the currently active version of the routine and other
versions of the routine. This error can be issued for any
Explanation
• The number of parameters, data types, CCSID
You attempted to alter the JAR jar-id to contain a JAVA specifications, and character data attributes (FOR
path that references the jar-id. A JAR cannot have a BIT, SBCS, or MIXED DATA) in the parameter
path that contains a reference to itself. list must be the same as the attributes of the
jar-id corresponding parameters of the currently active
The JAR file that is being altered. The reference to version of the routine and all of the other existing
the jar-id also appears in a specified Java path. versions of the routine.
• The data type, CCSID specification, and character
System action data attributes (FOR BIT, SBCS, or MIXED DATA)
for the RETURNS parameter must be the same as
The statement cannot be processed. the attributes of the RETURNS parameter of the
currently active version of the routine and all of the
User response other existing versions of the routine.
Correct the specified JAVA path value so that it does • An ALTER PROCEDURE statement was specified with
not reference the JAR that is being altered. the PARAMETER CCSID clause with a value that
is different from the value determined when the
procedure was initially created.
SQLSTATE
• An existing routine is defined with a table parameter.
4600E
-20313 DEBUG MODE OPTION FOR System action
OBJECT object-name CANNOT BE The statement cannot be processed.
CHANGED
User response
Explanation
Correct the specification of the parameter list
The object, object-name, was originally created with or RETURNS clause, or change or remove the
DISABLE DEBUG MODE. An object created with this PARAMETER CCSID clause.
attribute cannot be changed to either ALLOW DEBUG

SQLSTATE PREFIX, OR URI ENDING WITH
string-end EXCEEDS THE LIMIT OF
428GH 1000 BYTES
-20315 THE CURRENTLY ACTIVE VERSION
FOR OBJECT object-name (object- Explanation
type) CANNOT BE DROPPED
The Db2 database manager generated an internal
identifier for an element name, attribute name,
Explanation namespace prefix, or URI. After conversion of the
One of the following has occurred: identifier to the Unicode UTF-8 encoding scheme, the
length of the identifier exceeded the limit of 1000
• An ALTER statement for the SQL routine or trigger bytes.
specified a DROP VERSION clause that identified the
currently active version to be dropped. You cannot string-end
drop the active version of a routine or advanced The ending characters of the string that exceeded
trigger. the limit.
clause was specified without a VERSION clause and System action
the existing trigger is defined with more than a single The statement cannot be processed.
version. This combination is not supported.
• A CREATE TRIGGER statement with an OR REPLACE User response
clause was specified without a VERSION clause and
the existing trigger is defined with a single version Modify the element name, attribute name, namespace
but the version id is not V1. This combination is not prefix, or URI to be shorter. Issue the SQL statement
supported. again.
object-name
The name of the routine or trigger. SQLSTATE
object-type 54057
The type of routine or trigger.
-20327 THE DEPTH OF AN XML
DOCUMENT EXCEEDS THE LIMIT
System action OF 128 LEVELS
Explanation
User response An XML document that is being parsed or validated, or
To drop all of the versions of the object, drop the an XML value that is being stored, is nested too deep.
object without identifying a particular version.
To drop the currently active version and make a System action
different version active, complete the following steps: The statement cannot be processed.
1. Issue the ALTER statement for the object with
the ACTIVATE VERSION clause. This statement User response
changes which version is active.
For a document or constructed XML value, reduce the
2. Issue the ALTER statement for the object with a number of levels of elements and attributes that are
DROP VERSION clause. This statement identifies used.
and drops the previously active version.
SQLSTATE
SQLSTATE
54058
55059
-20328 THE DOCUMENT WITH TARGET
Related reference NAMESPACE namespace AND
Statements (Db2 SQL) SCHEMA LOCATION location HAS
ALREADY BEEN ADDED FOR THE
-20326 AN XML ELEMENT NAME,
ATTRIBUTE NAME, NAMESPACE

XML SCHEMA IDENTIFIED BY SQLSTATE
schema name
428GI
Explanation -20330 THE object-type IDENTIFIED BY

XML uri-type1 uri1 AND XML uri-
This error can occur while invoking the type2 uri2 IS NOT FOUND IN THE
XSR_ADDSCHEMADOC stored procedure. There XML SCHEMA REPOSITORY
cannot be two documents with the same
targetnamespace and schemalocation within an XML
schema. Explanation
The processing of the statement or command required
System action the use of an XML SCHEMA from the XML schema
repository that could not be found. uri-type1 is
The operation fails with this SQLCODE. NAMESPACE and uri-type2 is LOCATION. If either
value was null on the request, the corresponding uri1
Programmer response or uri2 is the empty string.
Change either the namespace or schemalocation of the object-type
document that is being added. The type of object.
uri-type1
SQLSTATE NAMESPACE.
42749 uri1
The URI that corresponds to the namespace. If
-20329 THE COMPLETION CHECK FOR uri-type1 was null on the request, uri1 is an empty
THE XML SCHEMA FAILED string.
BECAUSE ONE OR MORE uri-type2
XML SCHEMA DOCUMENTS LOCATION.
IS MISSING. ONE MISSING
XML SCHEMA DOCUMENT IS uri2
IDENTIFIED BY uri-type AS uri The URI that corresponds to the location. If uri-
type2 was null on the request, uri2 is an empty
string.
Explanation
The XML schema registration completion processing System action
determined that more than one XML schema
document is required for a complete XML schema. The statement cannot be processed.
The processing also determined that at least one XML
schema document is missing from the XML schema Programmer response
repository. The missing XML schema document is
identified by the uri type with value uri. The reference Add the missing XML schema to the XML schema
to the missing XML schema document may be included repository, and reissue the statement.
in one of the XML schema documents that is defined
for the XML schema. SQLSTATE
4274A
System action
22532
The invocation of SYSPROC.XSR_COMPLETE fails with
this SQLCODE. -20331 THE XML COMMENT VALUE string
IS NOT VALID
Programmer response
Explanation
Add any missing XML schema documents to
the XML schema repository, and then re-invoke The XML comment cannot contain two adjacent
SYSPROC.XSR_COMPLETE. hyphens and cannot end in a hyphen.
System action

Ensure the value for the XML comment is valid. Use the unique XML schema ID to identify the XML
schema.
SQLSTATE
SQLSTATE
2200S
22533
-20332 THE XML PROCESSING
INSTRUCTION VALUE string IS -20338 THE DATA TYPE OF EITHER THE
NOT VALID SOURCE OR TARGET OPERAND
OF AN XMLCAST SPECIFICATION
Explanation MUST BE XML
The XML processing instruction must not contain the

Explanation
substring "?>".
The XMLCAST specification must have one operand
System action that has the data type XML. The XMLCAST operation
can be from one the following:
• an XML type value to an SQL type value
• from an SQL type value to and XML type value
User response
The XMLCAST specification also accepts having both
Ensure the value for the XML processing instruction is
the source and target operands as XML, but if you
valid.
specify the source and target operands as XML, then
no actual casting operation is performed.
SQLSTATE
2200T System action
-20335 MORE THAN ONE xsrobject-type The expression cannot be processed.
EXISTS IDENTIFIED BY XML uri-
type1 uri1 AND uri-type2 uri2 Programmer response
EXISTS IN THE XML SCHEMA
REPOSITORY. If both operands are SQL data types other than
XML, then use the CAST specification. Otherwise,
change the XMLCAST specification so that at least one
Explanation operand is the XML data type.
There is more than one registered XML schema that SQLSTATE:
matches the URIs used to identify it. 42815
xsrobject-type -20339 XML SCHEMA name IS NOT IN
The type of object. THE CORRECT STATE TO PERFORM
uri-type1 OPERATION operation
Either NAMESPACE or null.
uri1 Explanation
The XML schema target namespace. If uri-type1
was null on the request, uri1 is an empty string. The operation operation cannot be performed on the
XML schema identified by name because it is not
uri-type2 in the correct state. For example, the XML schema
Either LOCATION or null. has already been completed and the operation is
uri2 attempting to add additional XML schema documents.
The XML schema location. If uri-type2 was null on
the request, uri2 is an empty string. System action
operation is failed with this SQLCODE.
System action
The invocation of DSN_XMLVALIDATE fails with this
SQLCODE.

Programmer response transfer failed due to one or more of the following
conditions:
If the schema has not yet been completed, invoke
SYSPROC. XSR_COMPLETE and try the operation again. • The authorization ID does not have the required
If the schema has already been completed and needs privilege to own the object.
to be updated, you must first remove it or register it • The authorization ID does not have the required
using a different name. privilege to specify a different schema for the
ownership transfer of a table or a view.
SQLSTATE • The current owner does not have the required
privilege to maintain the dependency on the
55063
package.
-20340 XML SCHEMA xmlschema-name
If the ownership is transferred to a role, the role name
INCLUDES AT LEAST ONE
is returned as a single token in the format of ROLE:
XML SCHEMA DOCUMENT IN
role-name.
NAMESPACE namespace THAT IS
NOT CONNECTED TO THE OTHER
XML SCHEMA DOCUMENTS System action
Explanation
The XML schema identified by identifier xmlschema- Programmer response
name includes multiple XML schema documents. Grant authorization ID auth-ID all the privilege on
At least one of these XML schema documents is object object-name that is required for the ownership
not connected to the other XML schema documents transfer.
registered to this XML schema.
SQLSTATE
System action
42514
The XSR_COMPLETE call fails with this SQLCODE.
-20345 THE XML VALUE IS NOT A WELL-
FORMED DOCUMENT WITH A
Programmer response
SINGLE ROOT ELEMENT
Correct the XML schema documents, or add
a new XML schema document, so that all Explanation
XML schema documents in an XML schema
are connected using import, include, or redefine, Db2 attempted to use an XML value that was not well-
beginning from the primary schema document. Use formed.
SYSPROC.XSR_REMOVE to remove the invalid schema
Well-formed XML is required when:
and re-invoke the XSR stored procedures to register
it with the corrected and/or new XML schema • Storing an XML value into a table.
documents. • Processing an XML value that has been returned
from a remote site within an SQL procedural
SQLSTATE language stored procedure.
22534
System action
-20342 AUTHORIZATION ID auth-ID
DOES NOT HAVE THE REQUIRED The statement cannot be processed.
PRIVILEGE privilege-name ON
OBJECT object-name OF TYPE User response
type-name FOR OWNERSHIP
TRANSFER. Modify the XML value so that it is well-formed with a
single root element.
Explanation
SQLSTATE
A TRANSFER OWNERSHIP statement is issued to
transfer ownership to authorization ID auth-ID. The 2200L

-20353 AN OPERATION INVOLVING Programmer response
COMPARISON CANNOT USE
OPERAND name DEFINED AS Correct the syntax and resubmit the statement.
DATA TYPE type-name
SQLSTATE
Explanation 429BV
The use of the value identified by name defined as -20355 THE STATEMENT COULD NOT
data type type-name is not permitted in an operation BE PROCESSED BECAUSE ONE
that involves comparisons. This error can be returned OR MORE IMPLICITLY CREATED
for an expression that results in a type-name data type OBJECTS ARE INVOLVED reason-
in the following contexts: code
• A SELECT DISTINCT statement.
• A GROUP BY clause. Explanation
• An ORDER BY clause. The statement failed for one of the following reasons,
• An aggregate function with DISTINCT. indicated by the reason-code:
• A SELECT or VALUES statement of a set operator 1

other than UNION ALL. The statement attempted to create a table or a
table space within a database that was implicitly
created by Db2.
System action
2
The statement cannot be processed. The statement attempted to define a new
column (using CREATE or ALTER TABLE) as
Programmer response LONG VARCHAR or LONG VARGRAPHIC, but the
associated table space was implicitly created by
The requested operation on the data type type-name Db2.
is not supported. You can change the data type of the
value to a data type that is supported using a cast or 3
some other function. The statement attempted to create an auxiliary
table or auxiliary index because these objects have
already been implicitly created by Db2.
SQLSTATE
4
42818 The statement attempted to drop a LOB table
space, auxiliary table, or auxiliary index that was
-20354 INVALID SPECIFICATION OF implicitly created by Db2.
A ROW CHANGE TIMESTAMP
COLUMN FOR TABLE table-name 5
The statement attempted to alter an implicitly
created hash overflow index, either by adding the
Explanation clustering option, by adding columns, or by making
The specification of a row change timestamp column it padded.
is invalid. The specification is invalid because a row 6
change timestamp column cannot be: The statement attempted to transfer the
• A column of a foreign key. ownership of a table space or a table that was
implicitly created by Db2.
• A column of a partitioning key for a table that uses
index-controlled partitioning.
System action
• Defined for a temporary table.
The specification might also be invalid because a row
change timestamp column cannot have a FIELDPROC
defined for it. User response
Change the statement to refer to an object that is not
System action involved with implicitly created objects.

SQLSTATE This error can also occur for one of the following
reasons:
429BW
• The authorization ID is allowed to use the trusted
-20356 THE TABLE WITH DBID = dbid context, but authentication is required and the
AND OBID = obid CANNOT BE request to switch users did not include the
TRUNCATED BECAUSE DELETE authentication token.
TRIGGERS EXIST FOR THE
TABLE, OR THE TABLE IS THE
context , but the security label for the user is not one
PARENT TABLE IN A REFERENTIAL
of the RACF SECLABEL values defined for the user.
CONSTRAINT
context, but the trusted context is disabled.
Explanation
• The system authorization ID attribute of the
The TRUNCATE statement could not be processed for trusted context object associated with the trusted
one of the following reasons: connection has been changed.
• The TRUNCATE statement would result in the • The trusted context object associated with the
activation of DELETE triggers, but the statement trusted connection has been dropped.
specified RESTRICT WHEN DELETE TRIGGERS,
either implicitly or explicitly. This can occur when
System action
enabled DELETE triggers exist for the table to
be truncated, and the result of the TRUNCATE The statement cannot be processed.
statement would activate the triggers.
• The table to be truncated is the parent table of a Programmer response
child table, regardless of whether the child table
contains rows or not, that are in a referential Establish a valid authorization ID to be associated with
constraint. the trusted connection.
dbid.obid Gives the database id and the table obid of • If the authorization ID is valid but requires
the object with the truncation error. authentication, provide the authentication token.
• If the trusted context object is either disabled,
System action dropped, or its system authorization ID is altered,
then only the authorization ID that established
The statement cannot be processed. the trusted connection is allowed. Provide this
authorization ID.
User response • If the authorization ID is valid but requires a RACF
security label, then define the security label in RACF
If the statement failed because of the existence
for the authorization ID.
of DELETE triggers, specify the IGNORE DELETE
TRIGGERS clause on the TRUNCATE statement. If the
statement failed because of referential constraints, SQLSTATE
use the ALTER TABLE statement to drop the referential 42517
integrity constraints, and then re-issue the TRUNCATE
statement. -20362 ATTRIBUTE attribute-name WITH
VALUE value CANNOT BE
DROPPED BECAUSE IT IS NOT
SQLSTATE
PART OF THE DEFINITION OF
428GJ TRUSTED CONTEXT context-name
-20361 AUTHORIZATION ID authorization-
name IS NOT DEFINED FOR THE Explanation
TRUSTED CONTEXT context-name Attribute attribute-name was specified for a trusted
context, but the trusted context is not defined with an
Explanation attribute with this name.
authorization-name attempted to reuse a trusted
connection using trusted context context-name. The System action
trusted context name context-name cannot be used The statement cannot be processed.
under the authorization-name.

Programmer response aggregate function. If the exception occurred while
processing an aggregate function, it is indicated
Remove the name of the unsupported attribute and by an operation-type of AGGREGATE FUNCTION. If
re-issue the statement. this is the case, the cursor will be closed. If the
cursor is closed, subsequent attempts to use that
SQLSTATE cursor without first doing an OPEN for it, receive
an SQLCODE-501. If the statement was a cursor-
4274C controlled OPEN, then the cursor will remain closed.
-20363 ATTRIBUTE attribute-name WITH
VALUE value IS NOT A UNIQUE User response
SPECIFICATION FOR TRUSTED
CONTEXT context-name Examine the expression which prompted the warning
to see if the cause of the problem can be determined.
The problem might be data-dependent, in which case
Explanation you must examine the data that was being processed
During the create or alter of a trusted context context- at the time the error occurred.
name, a duplicate value was specified for the attribute- If the arithmetic expression in error was within the
name attribute. Attribute attribute-name was specified SELECT list of the outer SELECT statement, then you
for the trusted context with value value, but the should include an indicator variable for all expressions
combination is not unique. Each pair of attribute name in the SELECT list. This allows processing to continue
and value must be unique for a trusted context. so that non-error column and expression values can be
returned.
System action See the explanation of SQLCODE -405 for allowed
The statement cannot be processed. ranges of numeric data types.
Programmer response SQLSTATE:

Remove the non-unique specification of attribute- 22502
name and value and re-issue the statement. -20366 TABLE WITH DBID=database-id
AND OBID=object-id CANNOT
SQLSTATE BE TRUNCATED BECAUSE
UNCOMMITTED UPDATES EXIST
4274D
ON THE TABLE WITH 'IMMEDIATE'
-20365 A SIGNALING NAN WAS OPTION SPECIFIED IN THE
ENCOUNTERED, OR AN STATEMENT
EXCEPTION OCCURRED IN
AN ARITHMETIC OPERATION Explanation
OR FUNCTION INVOLVING A
DECFLOAT A TRUNCATE statement was issued with the
IMMEDIATE option, but the statement could not be
processed.
Explanation
database-id
A signaling NaN (sNaN) was encountered in an The database ID.
expression, arithmetic operation, or function. This
message could also be issued because an expression, object-id
arithmetic operation, or function involving a DECFLOAT The table object ID (OBID) of the object with the
column or value resulted in an exception. In either truncation error.
case, the result is a NAN, and an error is issued. A TRUNCATE statement with the IMMEDIATE option
cannot be processed if either of the following are true:
System action • Any table in the same table space as the target table
The statement cannot be processed. In the case of has uncommitted CREATE, ALTER or DROP changes.
an INSERT, MERGE, or UPDATE operation, no data • Any table in the same table space as the target table
is updated or deleted. If the statement is a cursor- has uncommitted data changes.
controlled FETCH, then the cursor will remain open,
unless the exception occurred while processing an

The statement cannot be processed. A CREATE or ALTER TRUSTED CONTEXT statement
for context-name specified SYSTEM AUTHID
User response authorization-name, but this authorization ID is
already defined to use a different trusted context. A
Issue a COMMIT statement, and then issue the system authorization ID that is defined as the SYSTEM
TRUNCATE statement with the IMMEDIATE option. AUTHID for a trusted context cannot be associated
with any other trusted context as the SYSTEM AUTHID.
SQLSTATE
System action
57007
Related reference
COMMIT (Db2 SQL)
TRUNCATE (Db2 SQL) Programmer response
Change the authorization ID to be the system
-20369 AN ALTER TRUSTED CONTEXT authorization ID for the trusted context and reissue
STATEMENT FOR context-name the CREATE or ALTER statement.
ATTEMPTED TO REMOVE THE LAST
CONNECTION TRUST ATTRIBUTE
ASSOCIATED WITH THE TRUSTED SQLSTATE
CONTEXT 428GL
-20373 A CREATE OR ALTER TRUSTED
Explanation CONTEXT STATEMENT SPECIFIED
An ALTER TRUSTED CONTEXT statement for context- authorization-name MORE THAN
name specified the DROP ATTRIBUTES clause that ONCE OR THE TRUSTED CONTEXT
would have resulted in removing the last connection IS ALREADY DEFINED TO BE
trust attribute defined for the trusted context. This USED BY THIS AUTHORIZATION
result is not allowed. ID, PROFILE NAME, OR PUBLIC.

The statement cannot be processed. The statement specified that authorization-name be
allowed to use the trusted context, but cannot due to
Programmer response
• The specified authorization ID, profile name, or
Specify the ADD ATTRIBUTES clause to specify PUBLIC is already defined to use the trusted context
new values for the connection trust attributes being
removed, or, use the ALTER ATTRIBUTES clause • The profile name or authorization ID was specified
to specify new values without needing a DROP more than once in the statement
ATTRIBUTES clause. The authorization ID, profile name, or PUBLIC must
not already be allowed to use the trusted context, and,
SQLSTATE it can only be specified once within a statement for a
trusted context.
428GK
The token authorization-name might return a RACF
-20372 THE SYSTEM AUTHID profile name. A profile name is returned as a single
CLAUSE OF A CREATE OR token in the following format: PROFILE: profile-name.
ALTER TRUSTED CONTEXT
STATEMENT FOR context-name
SPECIFIED authorization-name,
System action
BUT ANOTHER TRUSTED CONTEXT The statement cannot be processed.
IS ALREADY DEFINED FOR THAT
AUTHORIZATION ID.
Programmer response
Complete one of the following actions based on what
the error is:

• If an ALTER TRUSTED CONTEXT statement that -20377 AN ILLEGAL XML CHARACTER hex-
contained an ADD USE FOR clause, and the trusted char WAS FOUND IN AN SQL/XML
context already was defined for use by that EXPRESSION OR FUNCTION
authorization ID, profile name, or PUBLIC, use the ARGUMENT THAT BEGINS WITH
REPLACE USE FOR clause instead to redefine the STRING start-string
usage characteristics for the specified users to use
the trusted context.
Explanation
• If the authorization ID, profile name, or PUBLIC
was specified more than once, remove the extra An SQL expression, XML expression, or function
specification of authorization-name, and re-issue the attempted to convert an SQL string value from one of
statement. the arguments to an XML string, but the string included
a character at Unicode code point hexchar that is not a
legal XML 1.0 character. The character is included in a
SQLSTATE string that begins with the string start-string. The value
428GM for hex-char represents a Unicode character code
point in the form "#xH", where H is a hexadecimal
-20374 AN ALTER TRUSTED CONTEXT character. The following set of characters, expressed
STATEMENT FOR context-name in Unicode are allowed: #x9 | #xA | #xD | [#x20-
SPECIFIED authorization-name #xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
BUT THE TRUSTED CONTEXT IS
NOT CURRENTLY DEFINED TO BE
USED BY THIS AUTHORIZATION
System action
ID, PROFILE NAME, OR PUBLIC The statement cannot be processed.

An ALTER TRUSTED CONTEXT statement for context- Remove the illegal character hex-char or replace it
name attempted to replace or remove the ability for with a character that is allowed.
authorization-name to use the trusted context, but the
specified authorization ID, profile name, or PUBLIC is
not currently defined to use the trusted context.
SQLSTATE
0N002
The token authorization-name might return a RACF
profile name. A profile name is returned as a single -20379 AN AUTHORIZATION ID OR A
token in the following format: PROFILE:profile-name. ROLE CANNOT USE ITS SECADM
AUTHORITY TO TRANSFER THE
System action OWNERSHIP OF AN OBJECT TO
ITSELF.
Explanation
Programmer response
An authorization ID or a role that has the SECADM
Complete one of the following actions based on what authority cannot transfer the ownership of an object
the error is: to itself. It can transfer the ownership of the object to
• If an ALTER TRUSTED CONTEXT statement that another authorization ID or role.
contained a REPLACE USE FOR clause, and the
trusted context was not already defined for use System action
by that authorization ID, profile name, or PUBLIC,
use the ADD USE FOR clause instead to define the The statement cannot be processed.
trusted context to be used by the specified users.
• If the ALTER TRUSTED CONTEXT statement Programmer response
contained the DROP USE FOR clause, none of the Choose a different authorization ID or role as the new
specified authorization IDs, profile name, or PUBLIC owner of the object.
were currently defined to use the trusted context.
SQLSTATE
SQLSTATE
42502
428GN

-20380 ALTER INDEX WITH REGENERATE System action
OPTION FOR index-name FAILED.
INFORMATION RETURNED: The statement cannot be processed.
SQLCODE sqlcode, SQLSTATE
sqlstate, MESSAGE TOKENS token- User response
list
Specify a sequence with a single item as the context
item.
Explanation
An ALTER INDEX statement was issued for index- SQLSTATE
name, but the index cannot be successfully
2200V
regenerated.
-20385 THE STATEMENT CANNOT BE
System action PROCESSED BECAUSE THERE ARE
PENDING DEFINITION CHANGES
The statement cannot be processed. FOR OBJECT object-name OF TYPE
object- type (REASON reason-code)
Programmer response
Drop and re-create the index. Explanation
The statement could not be processed because
SQLSTATE definition changes are pending for the indicated
object.
560CC
object-name
-20381 ALTER INDEX WITH REGENERATE The name of the object that has pending definition
OPTION IS NOT VALID FOR index- changes.
name
object-type
The type of object that object-name is.
The REGENERATE option is allowed only if the index is A numeric indicator that provides a more detailed
an expression-based index. explanation for why the statement was not
processed.
System action 1
An ALTER statement cannot contain a mixture
The statement cannot be processed. of immediate and pending options.
2
Programmer response An ALTER TABLE statement is not allowed
Change the statement so that it refers to an index that when either of the following conditions is true:
can be regenerated. • The ALTER TABLE statement is issued with
immediate options and definition changes
SQLSTATE are pending for the table space or any
objects within the table space.
530A5
• FL 508 The ALTER TABLE statement is issued
-20382 CONTEXT ITEM CANNOT BE A with any option, immediate or pending, and
SEQUENCE WITH MORE THAN a MOVE TABLE operation is pending for the
ONE ITEM table.
3
Explanation A CREATE TABLE statement is not allowed
if any definition changes are pending for the
The initial context item specified as an argument of
table space.
XMLQUERY function, or the XMLEXISTS predicate, is a
sequence of more than one item. 4
FL 506 A DROP TABLE statement is not
allowed if the containing table space is not

being implicitly dropped and any definition 16
changes are pending for the table space. An ALTER TABLESPACE statement to change
5 CCSID is not allowed if any definition changes
An ALTER TABLESPACE statement to change are pending for the table space or table.
from a Db2-managed data set to a user- 17
managed data set is not allowed if any A CREATE INDEX statement is not allowed
definition changes are pending for the table if any definition changes are pending for the
space unless the table space uses partition-by- table space or any objects within the table
growth organization. space.
6 18
An ALTER INDEX statement to change from a A DROP INDEX statement is not allowed when
Db2-managed data set to a user-managed data all of the following conditions are true:
set is not allowed if any definition changes are
• The index is a unique index defined
pending for the index or table space.
on a ROWID column that is defined as
7 GENERATED BY DEFAULT
A pending option is not allowed if the table
• Definition changes are pending for the table
space is in an incomplete state.
space or any objects within the table space.
8
• The table space was explicitly created.
A pending option is not allowed if the table
contained in the table space or associated with 19
the index is in an incomplete state. A DROP INDEX statement is not allowed when
both of the following conditions are true:
An ALTER TABLE statement with a DROP
COLUMN clause is not allowed if the table • The index is an empty index on an auxiliary
definition is in an incomplete state. table that resides in an explicitly-created LOB
table space.
9
An ALTER INDEX statement to change from • Definition changes are pending for the base
COMPRESS NO to COMPRESS YES is not table space or any objects within the base
allowed if any definition changes are pending table space.
for the index. 20
10 A DROP TABLE statement is not allowed when
An ALTER INDEX statement to change both of the following conditions are true:
PIECESIZE is not allowed if any definition
• The table is an empty auxiliary table.
changes are pending for the index or the table
space. • Definition changes are pending for the base
table space or any objects within the base
11
table space.
A RENAME TABLE or RENAME INDEX
statement is not allowed if any definition 21
changes are pending for the object. A CREATE VIEW statement is not allowed if
13 any pending definition changes exist for the
An ALTER INDEX REGENERATE statement is column.
not allowed if any definition changes are 22
pending for the table space or objects within A CREATE TRIGGER statement that creates
the table space. an INSTEAD OF trigger is not allowed if the
14 view is dependent on any tables with pending
An ALTER INDEX ADD COLUMN statement definition changes.
is not allowed if any definition changes are 23
pending for the table space or objects within A CREATE TRIGGER statement is not allowed
the table space. if the triggering table has pending definition
15 changes.
An ALTER TABLESPACE statement to change 24
FREEPAGE is not allowed if any definition A CREATE PERMISSION statement is not
changes are pending for the table space. allowed on a table if the table or any
referenced tables have pending definition
changes.

25 31
A CREATE MASK statement is not allowed on a An ALTER TABLE statement to alter limit key is
table if the table or any referenced tables have not allowed if there are pending changes due
pending definition changes. to the insertion of new partitions.
26 32
A CREATE FUNCTION statement that creates An ALTER INDEX statement that changes an
an SQL table function is not allowed if any index to NOT PADDED is not allowed if the
referenced tables have pending definition index references a column that has pending
changes. definition changes.
27 33
A CREATE TABLE statement or an ALTER TABLE A CREATE TABLE or ALTER TABLE statement
statement that defines a materialized query is not allowed if a FOREIGN KEY clause
table is not allowed if any referenced tables references a parent column that has pending
have pending definition changes. definition changes.
28 35
After RECOVER is run on the specified table An ALTER INDEX statement to change DSSIZE
space to a point in time before materialization at the index level is not allowed if there is any
of pending definition changes, and before pending definition change for the index or table
REORG is run on the table space to complete space.
the recovery, none of the following statements 36
are allowed: ALTER TABLE ADD PARTITION ENDING AT x
• An ALTER TABLESPACE statement with the or ALTER TABLE ADD PARTITION ENDING AT
DROP PENDING CHANGES clause. x ALTER PARTITION n ENDING at y is not
allowed on a partition-by-range table space
The following statements are not allowed on that has unmaterialized limit key changes at
objects in the table space: the last logical partition.
• CREATE TABLE 37
• ALTER TABLE FL 508 A data definition statement for an
object is not allowed if the object references
• RENAME
a table space that has a pending MOVE TABLE
• DROP TABLE operation, or if the object references a table or
The following statements are not allowed on index in a table space that has a pending MOVE
indexes on tables in the table space: TABLE operation.
38
• CREATE INDEX
An ALTER TABLESPACE statement that results
• ALTER INDEX in a pending definition change for a LOB table
The following statements are not allowed on space is not allowed if the table space contains
auxiliary objects that are associated with the an auxiliary table that has an index with data
table space: sets that are not yet defined.
41
• CREATE AUXILIARY TABLE
An ALTER TABLE ADD CLONE statement is not
• ALTER TABLE allowed on the base table if an associated
• DROP TABLE LOB or XML table space has pending definition
changes.
29
There are pending definition changes for the
associated table. System action
An ALTER TABLESPACE statement to change
DSSIZE at the partition level is not allowed User response
if any definition changes are pending for the
table space. Take the action that corresponds to the reason-code
value:

1 to complete the point-in-time recovery process.
Separate the options so that all of the immediate Then execute the SQL statement that caused this
options are in one ALTER statement that is error again.
processed first, and all of the pending options 29
are in a separate ALTER statement that is issued Apply all pending definition changes to the
afterward. associated table, and process the statement again.
2 38
1. Use REORG TABLESPACE with SHRLEVEL Re-create the auxiliary index with DEFINE YES or
CHANGE or SHRLEVEL REFERENCE to apply all re-create the LOB table space as DEFINE NO.
pending definition changes for the table space
and its objects. All other values
2. Issue the ALTER TABLE statement with 1. Run REORG TABLESPACE with SHRLEVEL
immediate options for the table. CHANGE or SHRLEVEL REFERENCE to apply all
pending definition changes.
3
Specify a different table space that does not have 2. Process the statement again.
any pending definition changes and process the
statement again. SQLSTATE
4
57007
1. Use ALTER TABLESPACE DROP PENDING
Related reference
CHANGES to drop the pending definition
changes for the table space. SYSTABLESPACE catalog table (Db2 SQL)
SYSTABLES catalog table (Db2 SQL)
2. Issue the DROP TABLE statement for the table.
6, 9, or 11
-20398 ERROR ENCOUNTERED DURING
1. Apply all pending definition changes to the
XML PARSING AT LOCATION n text
table, the index, or the table space and index,
as appropriate:
Explanation
• If no pending changes exist for the table
space, use REORG INDEX with SHRLEVEL XML parsing failed during Db2 processing.
CHANGE or SHRLEVEL REFERENCE to apply
n
all pending definition changes for the index.
A byte offset into the XML code being processed
• If pending changes exist for the table space, after the conversion of the XML to codepage
use REORG TABLESPACE with SHRLEVEL UTF-8.
CHANGE or SHRLEVEL REFERENCE to apply
text
all pending definition changes for the index
Additional information describing the parsing error.
and table space.
This information includes the z/OS XML System
2. Process the statement again. Services return and reason code.
7
Check the status of the table space definition, System action
which is indicated in the STATUS column of
the SYSIBM.SYSTABLESPACE table. Complete or The statement cannot be processed.
correct the table space definition and process the
statement again. User response
8 Correct the XML coding and re-issue the SQL
Check the status of the table definition, which statement.
is indicated in the TABLESTATUS column of the
SYSIBM.SYSTABLES table. Complete or correct the
table definition and process the statement again. SQLSTATE
28 2200M
Run REORG TABLESPACE with SHRLEVEL
-20399 ERROR ENCOUNTERED DURING
REFERENCE on the entire table space to remove
XML VALIDATION: LOCATION n;
the REORG-pending (REORP) restrictive state, and
TEXT: text; XSRID schema-ID

XML parsing failed during validation. The statement cannot be processed.
n
A byte offset into the XML instance document that User response
is being validated after the conversion of the XML
Correct the problem with the XML schema
to codepage UTF-8.
document and re-issue the invocation of the
text SYSPROC.XSR_COMPLETE stored procedure.
Additional information describing the parsing error.
Db2 might also include a text description of the
error when possible. The Db2 special register value
SQLSTATE
CURRENT LOCALE_LC_CTYPE is used to determine 2200M
the language of the error message from the XML
parser. If this value is not set, the default language -20409 AN XML DOCUMENT OR
is EN_US. CONSTRUCTED XML VALUE
CONTAINS A COMBINATION OF
schema-ID XML NODES THAT CAUSES AN
The schema ID of the XML schema against which INTERNAL IDENTIFIER LIMIT TO
the instance XML document is being validated. BE EXCEEDED

The statement cannot be processed. An internal identifier that must be associated with
each XML node of an XML value cannot be generated
Programmer response because the combination of the number of levels of
XML nodes and the number of children nodes within
Update the XML instance document to correct the these levels causes the identifier to overflow.
problem and resubmit the statement.
System action
SQLSTATE
2201R
-20400 XML SCHEMA ERROR n text Programmer response
For a document or constructed XML value, reduce
Explanation the number of levels of XML nodes or the number of
The XML schema document did not process. children nodes especially at the deeper levels of XML
nodes.
n
Location of the error in the schema document
being processed. SQLSTATE
text 560CG
Additional information describing the parsing
-20410 THE NUMBER OF CHILDREN
error. This information includes the XML4J parser
NODES OF AN XML NODE IN
error codes and text. The special register value
AN XML VALUE HAS EXCEEDED
CURRENT LOCALE_LC_CTYPE is used to determine
THE LIMIT NUMBER OF CHILDREN
the language of the error message from the XML
NODES
parser. If this value is not set, the default language
is EN_US.
Explanation
Attention: For Db2, there is not a value
for n (offset), so Db2 will return *N. In the An expression generated an XML value with an XML
future, if there is a value for the location, node that has a number of children nodes. This
Db2 will be able to plug it in for the first number exceeds the limit of 232 -1 children nodes.
token.
System action

Programmer response CHARACTERS THAT COULD NOT
BE REPRESENTED IN THE TARGET
Rewrite the expression generating the XML value such ENCODING
that the number of children nodes does not exceed the
limit.
Explanation
SQLSTATE Serialization of XML data may require conversion to an
encoding different from the source UTF-8 encoding. If
560CH characters exist in the source encoding that cannot
-20411 A FETCH CURRENT CONTINUE be represented in the target encoding, code page
OPERATION WAS REQUESTED conversion produces substitution characters which are
FOR cursor-name BUT THERE not allowed in the result of XML serialization.
IS NO PRESERVED, TRUNCATED
DATA TO RETURN System action
Explanation
The application issued a FETCH request with the Programmer response
CURRENT CONTINUE clause for cursor cursor-name,
however, there is no preserved, truncated data that Choose a target encoding that can represent all
can be returned. One of the following errors might characters in the XML value. Unicode encodings are
have occurred: recommended as they can represent all characters.
• An operation has occurred since the previous FETCH

for this cursor that caused Db2 to discard the
SQLSTATE
preserved, truncated data. 2200W
• CONTINUE was specified on the FETCH statement, -20422 A CREATE TABLE, DECLARE
but the previous FETCH for this cursor did not GLOBAL TEMPORARY TABLE, or
specify the WITH CONTINUE clause to enable ALTER TABLE STATEMENT FOR
preservation of truncated data. table-name WOULD RESULT IN A
• The cursor is open but not positioned on a row. TABLE WITH ALL THE COLUMNS
• A FETCH WITH CONTINUE was executed DEFINED AS HIDDEN
successfully, but the LOB or XML columns were not
truncated. Explanation
An attempt was made to run one of the following
System action statements:
The statement is not processed. No data is written to • A CREATE TABLE or DECLARE GLOBAL TEMPORARY
the output host variable referenced on the FETCH. TABLE statement that would create a table in which
all of the columns are considered hidden. This can
Problem determination occur when A CREATE TABLE statement specifies
HIDDEN as a part of the definition of all of the
Verify that the application has successfully completed columns.
a FETCH using the WITH CONTINUE clause, and, that it
received a truncation warning for a LOB or XML column • An ALTER TABLE statement with a DROP COLUMN
prior to performing the FETCH CURRENT CONTINUE clause that would drop a column from a table where
operation. This verification can be done by checking all of the remaining columns are defined as HIDDEN.
the SQLWARN1 field in the SQLCA following the FETCH This process is not allowed. At least one column in a
and by examining the output length for LOB and XML table must not be defined as hidden.
columns.
System action
SQLSTATE
24524
-20412 SERIALIZATION OF AN
XML VALUE RESULTED IN

One of the text search administration tables
Verify that the resulting table definition includes at was not found (SYSIBMTS.SYSTEXTINDEXES,
least one column that is not defined as hidden. SYSIBMTS.SYSTEXTCOLUMNS,
SYSIBMTS.SYSTEXTSTATUS,
SQLSTATE SYSIBMTS.SYSTEXTCONNECTINFO, or
SYSIBMTS.SYSTEXTSERVERS).
428GU
2
Related reference There are no rows in the
ALTER TABLE (Db2 SQL) SYSIBMTS.SYSTEXTSTATUS text search
CREATE TABLE (Db2 SQL) administration table.
DECLARE GLOBAL TEMPORARY TABLE (Db2 3
SQL) The SYSTEMSTATUS column in the
SYSIBMTS.SYSTEXTSTATUS table has a value of -1
-20423 ERROR OCCURRED DURING TEXT indicating that text search support is not installed.
SEARCH PROCESSING (server,
4
index-name, text)
The SYSTEMSTATUS column in the
SYSIBMTS.SYSTEXTSTATUS table has a value of
Explanation 0 indicating that the support for text search is
'stopped'.
An error occurred during the text search processing of
a CONTAINS or SCORE function. 5
The SYSTEMSTATUS column in the
server SYSIBMTS.SYSTEXTSTATUS table has an invalid
The server the error was encountered on. value.
index-name 6
The name of the index used in the text search There are no rows in the
processing. Note: include schema and period with SYSIBMTS.SYSTEXTCONNECTINFO table.
the index name in a single token.
7
text No OmniFind servers have been defined.
The text returned from the OmniFind text search
product. The text is in the language specified by 8
the CURRENT LOCALE_LC_CTYPE special register. All servers have reached the maximum number of
indexes.
System action 9
The Db2 local location name is not defined.
10
The Db2 local host IP address is not defined.
Programmer response
Contact your system administrator to check that the System action
OmniFind text search product is successfully installed.
Refer to the documentation for the OmniFind text
search product for more information about text.
Programmer response
SQLSTATE Contact your system administrator to make sure that
support for text searching is successfully setup on your
38H10
system.
-20424 TEXT SEARCH SUPPORT IS NOT
AVAILABLE reason-code SQLSTATE
38H11
Explanation
-20425 column-name (IN table-name)
A problem with one of the text search administration
WAS SPECIFIED AS AN
tables used by Db2 was detected. The reason-code
ARGUMENT TO A TEXT SEARCH
provides more information about the error situation:
FUNCTION, BUT A TEXT INDEX

DOES NOT EXIST FOR THE System action
COLUMN
The CALL statement fails with this SQLCODE.
Explanation
Programmer response
A CONTAINS or SCORE text search function
specified column-name (in table table-name) as an Fix the problem indicated by error and re-invoke the
argument, but a text index does not exist for this administration stored procedure.
column. Therefore, text search processing cannot be
performed for the column. It is possible that the SQLSTATE
column or table is not registered to OmniFind.
38H14
System action -20428 URI SPECIFIED IN THE

XMLSCHEMA CLAUSE IS AN
The statement cannot be processed. EMPTY STRING.

Make sure that the column and table are registered to Either the target namespace URI that was specified
OmniFind. following the URI keyword or the schema location URI
that was specified following the LOCATION keyword is
SQLSTATE an empty string.
38H12
System action
-20426 CONFLICTING TEXT SEARCH
ADMINISTRATION STORED The statement cannot be processed.
PROCEDURE RUNNING ON THE
SAME INDEX Programmer response
Make sure that every target namespace URI and every
Explanation schema location URI in the XMLSCHEMA clause is a
There are conflicting administration stored procedures valid URI, and that it is not an empty string.
running on the same index.
SQLSTATE
System action 428GV
The statement cannot be processed. -20430 GLOBAL VARIABLE variable-name
CANNOT BE SET IN THIS
Programmer response CONTEXT.
Invoke the administration stored procedure after the
currently running stored procedure completes. Explanation
An attempt was made to set the value of the identified
SQLSTATE global variable in one of the following contexts:
38H13 • An autonomous procedure is executing.
-20427 ERROR OCCURRED DURING variable-name

TEXT SEARCH ADMINISTRATION Identifies a global variable that exists at the
STORED PROCEDURE error current server.

The error text describes the problem found, in the The statement cannot be processed.
language specified by the CURRENT LOCALE LC_CTYPE
special register.

Remove any direct or indirect calls to an autonomous 22540
procedure that includes an assignment to a global
Related reference
variable.
MERGE (Db2 SQL)
UPDATE (Db2 SQL)
SQLSTATE
428GX -20435 THE SELECT CLAUSE INCLUDES
MULTIPLE INVOCATIONS OF THE
-20433 AN UNTYPED EXPRESSION ARRAY_AGG FUNCTION. ALL
WAS SPECIFIED, BUT AN INVOCATIONS THAT EXPLICITLY
ASSUMED DATA TYPE CANNOT BE SPECIFY AN ORDER BY CLAUSE
DETERMINED FROM ITS USE MUST SPECIFY THE SAME ORDER.
An untyped expression was specified and Db2 cannot The SELECT clause includes multiple invocations
determine the data type. This error can occur with a of the ARRAY_AGG function. One of the following
MERGE statement when an untyped expression like conditions is also true:
a parameter or the NULL keyword is specified for a
column of the source data, and the column of the • More than one invocation of the ARRAY_AGG
source data is referenced in multiple contexts with function includes an ORDER BY clause. The sort keys
different assumed data types. in some of those ORDER BY clauses specify different
sort orders. The sort orders in all ORDER BY clauses
in the ARRAY_AGG function invocations must be the
System action same.
System action
Specify an explicit CAST specification to provide the
correct data type for the expression. Programmer response
SQLSTATE
• Change the sort keys in the ORDER BY clauses of the
429C1 ARRAY_AGG invocations in the SELECT list so that
-20434 AN UPDATE OPERATION HAS SET they are all identical.
ALL OF ITS TARGET COLUMNS TO • Remove the ORDER BY clause from all except one
UNASSIGNED ARRAY_AGG invocation in the SELECT list.
Extended indicator variables are enabled, and all 428GZ
of the target columns in the assignment clause
Related reference
of an UPDATE or MERGE statement were set to
UNASSIGNED. At least one of the extended indicator ARRAY_AGG (Db2 SQL)
variable's values must be something other than XMLAGG (Db2 SQL)
UNASSIGNED.
-20436 THE DATA TYPE SPECIFIED FOR
AN ARRAY TYPE IS NOT VALID.
System action
The data type that is specified for an array in one of the
System programmer response following contexts is not valid:
Correct the value and reissue the statement. • CREATE TYPE statement

• Array constructor SQLSTATE
• Argument to UNNEST 428H0
• Argument to ARRAY_AGG
Related concepts
• Target of ARRAY_AGG Array values (Db2 SQL)
The following restrictions apply to the data type for an Variables (Db2 SQL)
array:
-20438 THE DATA TYPE OF THE
• These data types are not supported:
EXPRESSION FOR AN ARRAY
– ROWID INDEX VALUE IS NOT CASTABLE
– XML TO THE DATA TYPE OF THE ARRAY
INDEX.
– A user-defined data type other than an array data
type
Explanation
• The data type for an array index of an associative
array must be INTEGER or VARCHAR, with a length If the object is an ordinary array, the data type of the
attribute no greater than 32704. expression that is specified for an array index value, in
syntax of the form object[array-index], cannot be cast
to the INTEGER data type.
System action
If the object is an associative array, the data type of
the expression that is specified for an array index value
cannot be cast to the INTEGER or VARCHAR data type.
Programmer response
Use a supported data type. System action
SQLSTATE
429C2 Programmer response
Related reference Change the expression for the value of the array index
Array constructor (Db2 SQL) to an expression with a data type that is supported:
collection-derived-table (Db2 SQL) • For an ordinary array, the data type of the expression
CREATE TYPE (Db2 SQL) that is specified for the array index value must be
castable to the INTEGER data type.
-20437 AN ARRAY INDEX CANNOT BE • For an associative array, the data type of the
APPLIED TO AN OBJECT THAT IS expression that is specified for the array index value
NOT AN ARRAY. must be castable to the INTEGER or VARCHAR data
type.
Explanation
A reference of the form object[array-index] was SQLSTATE
specified, but the object is not an array. An index 428H1
cannot be specified for an object that is not an array
type. Related concepts
Casting between data types (Db2 SQL)
Array element specification (Db2 SQL)
-20439 AN ARRAY INDEX VALUE, value,
Programmer response IS NULL OR OUT OF RANGE, OR
AN ARRAY ELEMENT WITH THAT
Change the variable or parameter to a variable or INDEX VALUE DOES NOT EXIST.
parameter of type ARRAY.
Explanation
One of the following situations exists:

• For a FETCH, SELECT INTO, VALUES INTO, or SET Related reference
assignment statement where the target is an array Array element specification (Db2 SQL)
element, the value of the array index is null. TRIM_ARRAY (Db2 SQL)
• For an array element specification for an ordinary
array, the value of an array index is null or out of -20440 THE ARRAY VALUE WITH
range. CARDINALITY cardinality HAS
TOO MANY ELEMENTS FOR THE
• For an array element specification for an associative
REQUESTED OPERATION. THE
array, the value of an array index is null, is out of
MAXIMUM NUMBER OF ELEMENTS
range, or does not exist in the array.
ALLOWED FOR THE REQUESTED
• For the second argument to the TRIM_ARRAY OPERATION IS value.
function, the value of an array index is null or out
of range.
Explanation
value
The array index value that is out of range, or the A cast operation cannot be performed because the
index value for the array element that does not operation would cause elements of the array to be
exist. truncated.
cardinality
System action The cardinality of the array value on which an
operation is being performed.
value
The maximum number of array elements on which
Programmer response the operation can be performed.
Take the appropriate action, depending on the context Truncation of the array value is not allowed where the
in which the array index value is used: array value is used. The array value is being used in
• For a FETCH, SELECT INTO, VALUES INTO, or SET one of the following contexts:
assignment statement where the target is an array • An argument to a procedure call or function
element, and an array index value is null, specify a invocation
non-null value for the array index value.
• The result of an invocation of the ARRAY_AGG
• For an array element specification for an ordinary function
array:
• The result of an array constructor that is used
– Specify an array index value that is not null. as a source value for a SET assignment-statement
– Specify an array index value that is greater than statement
or equal to 1 and the less than or equal to the • An argument to a cast specification
cardinality of the array.
The input to the cast operation contains too many
• For an array element specification for an associative array elements, or the target is defined with a
array: maximum cardinality that is too small.
– Specify an array index value that is not null.
– Specify an array index value for an array element System action
that exists in the array. The statement cannot be processed.
– If the array index data type is INTEGER, specify
a value that is a number within the range of Programmer response
integers.
Examine the SQL statement to determine where
• For the second argument of the TRIM_ARRAY
truncation of the array can occur. Reduce the
function, specify a value that is greater than or equal
cardinality of the input array, or increase the
to 1, and less than or equal to the cardinality of the
cardinality that the target can support.
array.
SQLSTATE SQLSTATE
2202F
2202E

Related concepts 2
Array values (Db2 SQL) A global variable was defined as a distinct
Related reference type. A global variable cannot be defined as a
distinct type.
Array constructor (Db2 SQL)
ARRAY_AGG (Db2 SQL) 3
An untyped array value was specified in an
-20441 type-name TYPE IS NOT VALID unsupported context.
WHERE SPECIFIED. REASON 4
CODE reason-code. A non-array value was specified in a context
where an array value is expected.
Explanation 5
An array global variable, or element of an
The identified data type is not valid in the specified
array global variable, was specified in an
context for the reason indicated by the reason code.
unsupported context. An array global variable,
type-name or element of an array global variable, that
The name of the array type. is the target of a FETCH statement must
reason-code be specified only in an SQL PL context. An
A numeric value that indicates the reason that EXECUTE or OPEN statement that specifies an
the statement cannot be executed. Possible values array global variable or element of an array
are: global variable in the USING clause can only
be issued in an SQL PL context.
1
System action
• An array data type was specified in an
unsupported context. An array data type can The statement cannot be processed.
be specified in multiple contexts within SQL
PL, including the following contexts: Programmer response
– A parameter to a non-inline SQL function See the documentation for the SQL statement on
– A return data type from a non-inline SQL which the error occurred for a complete list of
function restrictions on the use of the identified data type.
Change the SQL statement to use the data type in a
– A parameter to an SQL procedure
supported context.
– An SQL variable that is declared in an SQL
function
SQLSTATE
– An SQL variable that is declared in an SQL
procedure 428H2
– A global variable Related reference
Array constructor (Db2 SQL)
Some of the contexts in which an array data
type is not supported are: ARRAY_DELETE (Db2 SQL)
TRIM_ARRAY (Db2 SQL)
– A parameter or variable for an external
EXISTS predicate (Db2 SQL)
routine
– A parameter for an inline SQL function
CREATE FUNCTION (external scalar) (Db2 SQL)
– A return type of an inline SQL function CREATE FUNCTION (external table) (Db2 SQL)
– A column in a table CREATE PROCEDURE (external) (Db2 SQL)
– The SELECT list of the outer fullselect of a CREATE TABLE (Db2 SQL)
scrollable cursor DECLARE GLOBAL TEMPORARY TABLE (Db2
A value that is not an array value was specified SQL)
for the UNNEST operator. An array value is
the only type of value that is allowed for the -20442 THERE IS NOT ENOUGH STORAGE
UNNEST operator. TO REPRESENT THE ARRAY
VALUE.

Explanation System programmer response
The amount of memory that is required to represent an Use the index name and RID number to determine
array value is larger than the maximum allowed for the the failing row of the table. If the index definition is
system. available, use the column values of the failing row to
determine the failing key-expression.
System action
Programmer response
Contact your database administrator to determine why
Programmer response the index specified in the message received the error.
Examples of actions that you can take are:

SQLSTATE
• Reduce the number of elements in the array or the
560CM
size of some of the elements.
• Correct the statement that is attempting to create -20447 FORMAT STRING format-string IS
the array value. NOT VALID FOR THE function-
name FUNCTION
SQLSTATE
Explanation
57011
An invalid format string was specified for the function.
Related reference
CREATE TYPE (array) (Db2 SQL) format-string
The invalid format string. The format might be
-20444 AN ERROR OCCURRED IN A invalid for one or more of the following reasons:
KEY-EXPRESSION EVALUATION • The format string contains unsupported format
IN index-name INFORMATION elements or separator characters.
RETURNED: SQLCODE: sqlcode,
• The format string does not contain a format
SQLSTATE: sqlstate, MESSAGE
element, is the empty string, or is all blanks.
TOKEN token-list AND RID X rid
• The length of the format string argument
exceeds the maximum allowable length.
Explanation
• A format element is specified multiple times.
During evaluation of an index key-expression for a
• The format string contains too many format
data change statement, an SQL error condition was
elements.
encountered:
• The format string contains multiple format
index-name
elements that represent the same component.
The index involved when the error occurred.
For example, the TIMESTAMP_FORMAT function
sqlcode must not specify both YYYY and YY, which are
The SQLCODE received by the key-expression format elements to indicate the year, in the
evaluation. format string.
sqlstate • A parameter marker was specified for the first
The corresponding SQLSTATE for the SQLCODE argument and the format string includes a time
received by the key-expression evaluation. zone format element
token-list function-name
The list of tokens from the original SQL error. This The name of the function.
list might be truncated.
rid System action
The RID of the row which fails the key-expression
evaluation. The statement cannot be processed.

The statement cannot be processed. Change the format string argument for the function.

SQLSTATE: Explanation
22007
Related reference The version, version, specified for the parameter in
ordinal position number is not supported by the
Built-in functions (Db2 SQL)
procedure procedure-name.
-20448 string-expression CANNOT BE
INTERPRETED USING FORMAT User response
STRING format-string FOR THE
Call the procedure and specify a supported version
TIMESTAMP_FORMAT FUNCTION.
number for the parameter. The highest supported
version number for the parameter can be obtained
Explanation by calling the procedure and specifying NULL for the
The string expression that was specified for the value of this parameter.
TIMESTAMP_FORMAT function cannot be interpreted
with the specified format string to produce a SQLSTATE
timestamp value.
38554
function-name
The name of the function. The name used to -20465 THE BINARY XML VALUE IS
invoke the function could also be TO_DATE or INCOMPLETE OR CONTAINS
TO_TIMESTAMP. UNRECOGNIZED DATA AT
LOCATION position WITH THE HEX
string-expression DATA text
The string expression.
Possible reasons for this error include: Explanation
• The string expression is too long or too short for the An error occurred when processing a binary XML value.
specified format string.
position
• The string expression does not conform to the
A byte offset into the binary XML value.
template specified in the format string. For example,
92007 is not a valid value for YYYY, which indicates text
the year. The first eight bytes of XML data in hexadecimal.
If the unrecognized data is located within the last
• A value in the string expression is not valid for the
eight bytes of the binary XML data, only the data
corresponding format element in the format string.
starting at the location position up to the end of the
For example, 45 is not a valid value for DD, which
binary XML data is returned.
indicates the day of the month.
System action
System action
Programmer response
Programmer response
Modify the binary XML value so that it conforms to the
Change the format string argument for the function.
binary XML format, or change the application to use
SQLSTATE: the textual XML format for data transfer.
22007
Related reference SQLSTATE
TIMESTAMP_FORMAT (Db2 SQL)
22541
-20457 THE PROCEDURE procedure- -20467 THE STATEMENT WAS NOT
name HAS ENCOUNTERED AN EXECUTED BECAUSE AN
UNSUPPORTED VERSION, version, EXPRESSION IS NOT A CONSTANT
FOR PARAMETER number OR VARIABLE. THE INVALID
EXPRESSION IS IN THE
STATEMENT NEAR THE SYNTAX
ELEMENT syntax-element

Explanation 36
The object-name view is defined on the table
The expression in the statement near the syntax and the view is defined with the WITH CHECK
element syntax-element must result in a single value, OPTION clause.
and must consist of one of the following elements:
37
• A constant The object-name trigger is defined for the table
• A special register and the trigger is not defined as secure.
• A parameter marker 38
A view is defined on the table, the object-name
• A variable
trigger is defined for that view, and the trigger
• A deterministic function with no external action is not defined as secure.
• An expression whose operands are any of the above 39
elements The table is directly or indirectly referenced in
The expression cannot include any of the following the definition of a materialized query table.
elements: 40
The table is a created temporary table.
• A column name
41
• A non-deterministic function
The table has a row permission or a column
• A function with external action mask that is not valid because a previous
• An expression whose operands are any of the above attempt to regenerate it was unsuccessful.
42
System action The table cannot be activated for the row
access control because the table contains a
The statement cannot be processed. security label column.
43
User response The table cannot be activated for the row
access control or column access control,
Change the statement to specify an expression that
because the table is a system-period temporal
results in a single value, and contains only elements
table, history table, archive-enabled table, or
in the list of allowed elements. Issue the statement
archive table.
again.
79
The table cannot be activated for the row
SQLSTATE
access control or column access control
428H7 because the table has been granted federated
access to another Db2 for z/OS subsystem in
-20469 ROW OR COLUMN ACCESS IBM Db2 Analytics Accelerator.
CONTROL CANNOT BE ACTIVATED
FOR TABLE table-name FOR object-type
REASON reason-code. object-type The type of object.
object-name IS NOT IN A VALID object-name
STATE FOR ACTIVATING ACCESS The name of the object.
CONTROL FOR THIS TABLE
System action
Explanation
Row access control cannot be activated explicitly
or implicitly, or column access control cannot be
activated explicitly for the table.
Programmer response
Correct the error and reissue the statement to activate
table-name
row or column access control for the table. For the
invalid state, disable the row permission or column
reason-code mask. Then, drop and re-create it with the modified
The reason for the message or SQL code, indicated definition.

55019 Row access control is enforced for the object of the
insert or update operation. Consequently, all attempts
Related concepts
to insert or update rows in that table are checked
Row and column access control (Managing to ensure that the resulting rows conform to the row
Security) permissions defined for that table.
System action
(Introduction to Db2 for z/OS) The statement cannot be processed. No insert or
update operations were performed, and the contents
-20470 object-type1 object-name1 MUST of the table remain unchanged.
BE DEFINED AS SECURE BECAUSE
object-type2 object-name2 IS
Programmer response
DEPENDENT ON IT.
Examine the definitions of the row permissions
Explanation to determine why the requested insert or update
operation was not successful. This error might be a
An object that must be defined as secure is not data-dependent condition.
defined as secure.
object-type1 and object-name1 SQLSTATE
The type and name of the object that must be
22542
defined as secure, but that is not.
object-type2 and object-name2 -20472 PERMISSION OR MASK object-
The type and name of the object that depends on name CANNOT BE ALTERED
the object that is identified by object-name1. AS SPECIFIED. REASON CODE
reason-code.
The object that is identified by object-name2 depends
on object-name1 for row or column access control.
Explanation
In most cases, object-type2 is a row permission or
column mask. But if object-type2 is a sourced user- The ALTER MASK or ALTER PERMISSION statement
defined function, object-name2 must be referenced in could not be processed.
a row permission or column mask and object-name1 object-name
must be the underlying source of the user-defined The name of the object.
function.
reason-code
System action by one of the following values:
A default row permission cannot be altered.
ENABLE cannot be specified because the
Alter the object that is identified by object-name1 to object is invalid after a previous attempt to
make it secure. regenerate it was unsuccessful.

428H8 The statement cannot be processed.
-20471 THE INSERT OR UPDATE IS NOT
ALLOWED BECAUSE A RESULTING Programmer response
ROW DOES NOT SATISFY ROW
PERMISSIONS. Specify the name of a row permission that can
be changed. For the invalid state, disable the row
permission or column mask, then drop and re-create
it with the modified definition.

428H9 The CREATE PERMISSION or CREATE MASK statement
Related reference
ALTER MASK (Db2 SQL) object-name
ALTER PERMISSION (Db2 SQL) The name of the object.
object-type
-20473 THE INPUT ARGUMENT OF The type of object.
FUNCTION function-name THAT reason-code
IS DEFINED WITH THE NOT- The reason for the message or SQL code, indicated
SECURED OPTION MUST NOT
REFERENCE COLUMN column-
name FOR WHICH A COLUMN 1
MASK IS ENABLED AND THE The definition references the table for which
COLUMN ACCESS CONTROL IS the row permission or the column mask is
ACTIVATED FOR THE TABLE being defined.
2
Explanation The definition references a table function or a
collection-derived table (UNNEST).
The input argument of a function references a column
3
when it must not do so. When a column mask is
The definition references a user-defined
enabled and column access control is activated for a
function that is not secure.
table, the input argument of an insecure function must
not reference the column. 4
The definition references one of the following
function-name functions:
• A function that is defined as not deterministic
column-name
The name of the column. • A function that is defined to have an external
action
System action • A function that is defined with the MODIFIES
SQL DATA option
5
The definition references an OLAP
Programmer response specification.
Take either of the following actions, and reinvoke the 6
function. The definition references an XMLEXISTS
• Update the function invocation so that it does not predicate.
reference the column that is identified by column- 7
name. The definition references a ROW CHANGE
• Disable or drop the column mask. expression.
8
SQLSTATE The definition references a sequence
reference.
428HA 9
Related concepts The definition references a created or declared
Column mask (Managing Security) temporary table.
Functions (Db2 SQL) 10
The definition references a table that was
-20474 PERMISSION OR MASK CANNOT implicitly created for an XML column.
BE CREATED FOR THE object-name 11
OBJECT OF THE object-type TYPE. The definition references * or name.* in a
REASON CODE reason-code. SELECT clause.

12 36
The definition references a column that is The subtype, encoding scheme, or CCSID of
defined with a FIELDPROC. the return expression is not the same as
13 the corresponding attribute of the column on
The definition references a language element which the column mask is defined.
that requires multiple encoding scheme 37
processing. An attribute of the return expression is not
14 the same as the corresponding attribute of the
The definition references an ordinary SQL column on which the column mask is defined.
identifier that contains a dash (-). The attribute is not one of the attributes that
are described in reason codes 33-36.
16
The body of a row permission or column mask 39
includes a period specification. The definition references an accelerator-only
table.
17
One of the following situations occurred: 51
A row permission cannot be created for a table
• An attempt was made to create a row that has a security label column.
permission or column mask on one of the
52
following table types:
A row permission cannot reference a table that
– A table that is defined with a period has a security label column.
– A history table 53
– An archive-enabled table GROUPING SETS or super-groups cannot be
specified in the definition of a column mask or
– An archive table a row permission control.
– An accelerator-only table
You cannot create row permissions or System action
column masks on these types of tables.
• An attempt was made to implicitly create a
default row permission for an ACTIVATE ROW
ACCESS CONTROL specification.
Programmer response
18
The definition references a Db2 11 Unicode
column in an EBCDIC table. SQLSTATE
19 428HB
A column mask cannot be defined for a Db2 11
Unicode column in an EBCDIC table. Related concepts
Column mask (Managing Security)
32
The column for which the mask is defined was Row permission (Managing Security)
done so with a field procedure (FIELDPROC). Temporal tables and data versioning (Db2
33
The data type of the return expression is not Archive-enabled tables and archive tables
the same as the data type of the column on (Introduction to Db2 for z/OS)
which the column mask is defined. Related reference
34 CREATE MASK (Db2 SQL)
The length attribute of the return expression CREATE PERMISSION (Db2 SQL)
is not the same as the length attribute of the
column on which the column mask is defined. -20475 A COLUMN MASK IS ALREADY
DEFINED FOR THE COLUMN
35
column-name IN TABLE table-
The null attribute of the return expression
name (EXISTING MASK NAME
is not the same as the null attribute of the
mask-name)
column on which the column mask is defined.

Explanation • Contain only supported format elements.
An attempt was made to define a mask on a column,

but a mask already exists on the column. Only one System action
mask can be defined for a column. The statement cannot be processed.
column-name
The name of the column. User response
table-name Change the format string argument of the function-
The name of the table. name function.
mask-name
The name of the column mask that already exists.
SQLSTATE
System action 22018
Related reference
DECFLOAT_FORMAT (Db2 SQL)
VARCHAR_FORMAT (Db2 SQL)
Programmer response
To create the new mask, drop the existing mask, then -20477 THE function-name FUNCTION
reissue the statement. IS NOT ABLE TO USE
FORMAT STRING format-string
TO INTERPRET THE ARGUMENT
SQLSTATE string-expression.
428HC
CREATE MASK (Db2 SQL) The function-name function was invoked with format-
string and string-expression. This function-name value
-20476 THE function-name FUNCTION is DECFLOAT_FORMAT, even if the name used to
WAS INVOKED WITH AN INVALID invoke the function is TO_NUMBER. The value of
FORMAT STRING format-string. the argument string-expression cannot be interpreted
with the format string format-string to produce a
Explanation DECFLOAT(34) value. This error can occur for any of
An invalid format string was specified for the function-
name function. • string-expression is too long for the specified format
string
function-name
The name of the function. The value is either • string-expression does not conform to the template
VARCHAR_FORMAT or DECFLOAT_FORMAT, even specified in the format string; for example: Too many
if the name used to invoke the function was digits were specified in string-expression for the
TO_CHAR or TO_NUMBER. corresponding format element in the format string,
such as in the specific case where 1234 is not a valid
format-string value for 999
The invalid format string.
• A value in string-expression is not valid for the
A valid format string for the VARCHAR_FORMAT corresponding format element in the format string,
function must: such as in the specific case where $ is not a valid
• Have a data type length not greater than 254 bytes value for S
• Contain only supported format elements.

System action
• Not result in a string with an actual length that is
greater than the length attribute of the result The statement cannot be processed.
A valid format string for the DECFLOAT_FORMAT User response:
function must: Change the arguments of the function-name function
to valid values.
• Have a data type length not greater than 254 bytes
• Contain at least one format element

SQLSTATE 21
A column in the select list is an INCLUDE
22018 column for a data change statement that is
Related reference derived from the column for which the mask
DECFLOAT_FORMAT (Db2 SQL) is defined. The column mask cannot be applied
in this context.
TO_NUMBER (Db2 SQL)
22
-20478 THE STATEMENT CANNOT BE The result table is derived from a table function
PROCESSED BECAUSE COLUMN and the column was specified as an input
MASK mask-name (DEFINED FOR argument to the table function.
COLUMN column-name) EXISTS 23
AND THE COLUMN MASK CANNOT A column in the select list is derived from
BE APPLIED OR THE DEFINITION an OLAP specification and the column is
OF THE MASK CONFLICTS WITH referenced in the partitioning expression or
THE REQUESTED STATEMENT. sort key expression of the OLAP specification.
REASON CODE reason-code.
24
The column is referenced in a WHEN clause of
Explanation a CASE expression.
The statement could not be processed because of 27
a conflict with a column mask that is defined on a A sort key expression for
column. ARRAY_AGG, LISTAGG, PERCENTILE_CONT,
PERCENTILE_DISC or MEDIAN references a
mask-name
column for which a column mask is defined.
The name of the column mask.
30
column-name
An insert or update operation uses a masked
value that is returned from the mask and
reason-code column that are identified in the message, and
The reason for the message or SQL code, indicated the expression that is specified in the THEN or
by one of the following values: ELSE clause of the column mask definition is
1 not a simple reference to the column.
The result table of the select is derived from a When the object table is column access control
set operation that involves one of the following activated, for an insert or update operation,
set operators: the return expression in the column mask
• EXCEPT ALL definition must be a simple reference to the
column for which the mask is defined.
• EXCEPT DISTINCT
31
• INTERSECT ALL
The query includes a GROUPING SETS, CUBE
• INTERSECT DISTINCT or ROLLUP clause.
2
The column is referenced in the select list of System action
the scalar fullselect and the result of the scalar
fullselect expression is derived from one of the The statement cannot be processed.
following set operators:
• EXCEPT ALL
Programmer response
• EXCEPT DISTINCT Check the application compatibility value that is used
by your application to ensure that it is set properly. The
• INTERSECT ALL
behavior of the statement might change based on the
• INTERSECT DISTINCT application compatibility level.
20 Take the action that corresponds to the reason-code
The result table is derived from a recursive value, and reissue the statement.
common table expression and the column is
specified in the fullselect of the recursive 1
common table expression. Either do not reference the column in the select list
or do not use the set operation in this context.

2 table-name
Either do not reference the column in the select The name of the table.
list of the scalar-fullselect expression or do not use reason-code
a set operator to derive the result of the scalar- The reason for the message or SQL code, indicated
fullselect expression in this context. by one of the following values:
20 1
Either remove the reference to the column of The table is referenced in one or more column
the recursive common table expression from the mask or row permission definitions.
select list or do not use the recursive common
table expression in this context. 2
A column in the table is referenced in one
21 or more column mask or row permission
Either remove the INCLUDE column from the definitions.
select list or do not derive the INCLUDE column
from the column name.
System action
22
Either do not reference the table function or do not The statement cannot be processed.
specify the column as input to the table function.
23 User response
Either do not reference the column in the OLAP
expression or do not use the OLAP expression in Correct the syntax, and reissue the statement.
this context.
24 SQLSTATE
Either change the query to remove the reference 42917
to the column in the CASE expression or do not
reference the CASE expression in this context. -20487 HASH ORGANIZATION CLAUSE IS
NOT VALID FOR table-name
30
Either change the statement to remove the
reference to the column in the insert or update Explanation
operation, or contact the security administrator
The table cannot be altered as specified.
to ask them to deactivate the column access
control from the object table or modify the return table-name
expression in the column mask definition. The name of the table.
31 Possible causes for this error include:
Remove the GROUPING SETS, CUBE or ROLLUP
clause from the query. • A clause was specified on an ALTER TABLE
statement, but the attribute cannot be set or
changed because the table is not defined with hash
SQLSTATE organization.
428HD • ADD ORGANIZE BY HASH was specified on an ALTER
TABLE statement, but the table is already defined
Related concepts
with hash organization.
Application compatibility levels in Db2 (Db2
Application programming and SQL) • ADD ORGANIZE BY HASH was specified on an ALTER
TABLE statement, but the table is already defined
-20479 THE SOURCE TABLE table-name with a clustering index. Hash organization cannot be
CANNOT BE ALTERED AS added to a table with a clustering index.
SPECIFIED BECAUSE THE TABLE • ADD ORGANIZE BY HASH was specified on an ALTER
IS INVOLVED IN ROW OR COLUMN TABLE statement, but either the table is defined with
ACCESS CONTROLS. REASON APPEND YES, or it is a materialized query table.
CODE reason-code.
• ADD ORGANIZE BY HASH was specified on an ALTER
TABLE statement, but the table is defined in a table
Explanation space that is defined with MEMBER CLUSTER. Or,
hash organization was specified on a CREATE TABLE
An unsuccessful attempt was made to alter or rename
statement that specifies a table space which is
a table that is involved in row or column access
defined with MEMBER CLUSTER.
controls.

• HASH SPACE was specified on a table that is not System action
defined to be organized by hash. If the table is not
defined with hash organization, the HASH SPACE The statement cannot be processed.
keyword is invalid in a partition element.
• HASH SPACE was specified on a table that resides in User response
a table space which is not in reordered row format. Take either of the following actions:
• FL 509 ADD ORGANIZE BY HASH was specified on
• Explicitly create a table space with a larger DSSIZE
an ALTER TABLE statement, but the table is defined
specification, and specify that table space in the
in a table space that is defined to use Huffman
CREATE TABLE statement.
compression, or hash organization was specified on
a CREATE TABLE statement that specifies a table • Reduce the HASH SPACE specification.
space which is defined to use Huffman compression.
SQLSTATE
System action 428HK
The statement cannot be processed. Related reference
User response
-20490 A VERSIONING CLAUSE WAS
Either correct the syntax of the statement or specify a
SPECIFIED FOR TABLE table-
different table. Then reissue the statement.
name, BUT THE TABLE CANNOT
BE USED AS A SYSTEM PERIOD
SQLSTATE TEMPORAL TABLE. REASON CODE
= reason-code.
428HJ
The ALTER TABLE statement attempted to make the
-20488 SPECIFIED HASH SPACE table into a system-period temporal table, but the
IS TOO LARGE FOR THE table definition is not valid.
IMPLICITLY CREATED TABLE table-name
SPACE. REASON reason-code. The name of the table.
(PARTITION partition-number)
reason-code
Explanation by one of the following values:
Db2 attempted to implicitly create a table space, but 1
the specified hash space is too large for the associated The table is already defined as a system-period
table space. temporal table or history table.
reason-code 2
A numeric value that indicates the type of table The table does not have a SYSTEM_TIME
space: period or a transaction start ID column. A
1 system-period temporal table must have both
A partition-by-range table space. a SYSTEM_TIME period and a transaction start
ID column.
2
3
A partition-by-growth table space.
The table is a materialized query table.
partition-number
5
For a partition-by-range table space, partition-
The transaction-start-ID column must be
number value indicates the partition for which the
defined with the same data type, length,
HASH SPACE value is too large. For partition-by-
precision, and scale as the row-begin column
growth table spaces, the partition number is not
and row-end column of the SYSTEM_TIME
relevant, and is indicated as *N.
period in the table.

8 • The start column definition is GENERATED
The table is an archive-enabled table or an ALWAYS AS ROW BEGIN and the end column
archive table. definition is GENERATED ALWAYS AS ROW
END.
System action • The start column definition is GENERATED
BY DEFAULT AS ROW BEGIN and the
The statement cannot be processed. end column definition is GENERATED BY
DEFAULT AS ROW END.
User response
Correct the syntax, and resubmit the statement. System action
SQLSTATE
428HM User response
Related concepts Correct the syntax, and resubmit the statement.
Administration Guide) SQLSTATE
428HN
-20493 A TIMESTAMP WITHOUT TIME
-20491 INVALID SPECIFICATION OF ZONE VALUE CANNOT BE
PERIOD period-name. REASON ASSIGNED TO A TIMESTAMP
CODE = reason-code. WITH TIME ZONE TARGET
The specification of an attribute in a CREATE or ALTER The statement attempted to assign a timestamp
statement for a period is invalid. without time zone value to a target that is defined as
period-name timestamp with time zone. This error can occur on a
The period that contains the invalid specification. FETCH, SELECT INTO, or CALL statement.
reason-code
A numeric value that indicates why the attribute System action
might be invalid: The statement cannot be processed.
1
The start column name must not be the same User response
as the end column name for the period.
Change the application to first cast the timestamp
2
without a time zone value to a timestamp with a time
The name of a column in a period must not be
zone value before making the assignment to the target.
the same as a column used in the definition of
another period for the table.
3
SQLSTATE
The data type, length, precision, and scale for 22007
the start column must be the same as for the
end column. -20494 A PUBLIC ALIAS NAME, name,
CAN ONLY BE QUALIFIED WITH
5 SYSPUBLIC AND NOT THE
For a BUSINESS_TIME period, the column SCHEMA NAME schema-name.
must not be a column defined with a
GENERATED clause.
Explanation
6
For a SYSTEM_TIME period, the attributes of A qualified name was specified for a public alias but
the start column and end column must be one the qualifier was not SYSPUBLIC.
of the combinations:


Change the two-part name to a one-part name or Remove the WITH ORDINALITY clause, or change the
specify the qualifier SYSPUBLIC. If a public alias argument of UNNEST to an ordinary array.
was not intended and PUBLIC was specified in the
statement, remove the keyword PUBLIC. SQLSTATE
428HT
SQLSTATE
Related reference
428EK
collection-derived-table (Db2 SQL)
-20497 A STRING REPRESENTATION table-reference (Db2 SQL)
OF A DATETIME VALUE THAT
CONTAINS A TIME ZONE CANNOT -20517 XMLMODIFY ATTEMPTED TO
BE IMPLICITLY OR EXPLICITLY UPDATE A COLUMN WHICH WAS
CAST TO A TARGET DEFINED AS NOT SPECIFIED IN THE UPDATE
DATETIME WITHOUT TIME ZONE SET CLAUSE
The statement attempted to cast a string The XQuery updating expression in the XMLMODIFY
representation of a datetime value that contains a time function invocation attempted to update XML nodes
zone to a datetime target that is defined to not have a that are not part of the column that is the target of the
time zone. This action is not supported. SET assignment clause that contains the XMLMODIFY
function invocation. The XMLMODIFY function can
System action update XML nodes in the target column only.

System action
User response The statement cannot be processed.
Change the application to first cast the string value

with a time zone to a datetime value with a time zone, Programmer response
and then cast the result to a datetime value without a Change the XQuery updating expression in the
time zone. Then make the assignment to the target. XMLMODIFY function to only refer to XML nodes
that are part of the column that is a target of the
SQLSTATE assignment.
22007
SQLSTATE
-20505 THE WITH ORDINALITY CLAUSE
428I1
IS NOT VALID WITH UNNEST OF
AN ASSOCIATIVE ARRAY. Related reference
XMLMODIFY (Db2 SQL)
Explanation
-20522 INVALID SPECIFICATION OF
A collection-derived table reference contained the WITHOUT OVERLAPS OR PERIOD
WITH ORDINALITY clause and an UNNEST invocation CLAUSE. REASON CODE reason-
in which the argument was an associative array. An code.
associative array and the WITH ORDINALITY clause
are not compatible because an associative array is not
organized according to ordinal position. Explanation
The specification of the WITHOUT OVERLAPS clause
was invalid.

reason-code Explanation
The reason why the specification was invalid:
A table is specified as a history table in a CREATE
2 TABLE statement or an ALTER TABLE statement, but
The columns of the specified period must not the table definition is invalid.
be specified in the constraint clause.
table-name
3
WITHOUT OVERLAPS can be specified in a
CREATE INDEX statement only if the index is reason-code
defined as UNIQUE. It cannot be specified if A numeric value that indicates the requirement
the index is defined as UNIQUE WHERE NOT that might make the definition invalid:
NULL. 1
5 The table must not be any of the following
The columns of the specified period must not tables:
be specified in the index specification. • System-period temporal table. The table was
7 defined as a system-period temporal table
WITHOUT OVERLAPS cannot be specified for by a previous statement, or the current
an index that is defined with PARTITION BY statement defines the table as a system-
RANGE. period temporal table.
8 • History table.
A key expression that is not a simple column • Declared global temporary table.
reference must not be specified for the key
or index when WITHOUT OVERLAPS is also • Created global temporary table.
specified. • Materialized query table.
9 • View.
WITH OVERLAPS can be specified in a CREATE • Auxiliary table.
INDEX statement only if the index is not
defined as UNIQUE or UNIQUE WHERE NOT • Clone table.
NULL. • Table that has a clone.
10 • Table that was implicitly created for an XML
WITHOUT OVERLAPS cannot be specified for column.
an index, if the table is defined with a • An archive-enabled table or archive table.
partitioning key that includes any columns of
the BUSINESS_TIME period. 2
The table definition must be complete.
System action 3
The table must be the only table in the table
The statement cannot be processed. space.
4
User response The table must not contain any of the following
Correct the syntax, and resubmit the statement. columns:
• Identity column
SQLSTATE • Row change timestamp column
428HW • Row begin column
-20523 TABLE table-name WAS • Row end column

SPECIFIED AS A HISTORY TABLE, • Transaction start ID column
BUT THE TABLE DEFINITION IS • Generated expression column
NOT VALID FOR A HISTORY TABLE.
REASON CODE = reason-code. 5
The table must not include a period definition.
6
The table must not be involved in any
referential integrity constraints.

7 CREATE TABLE (Db2 SQL)
The history table must have the same number
and order of columns as the table that is to be -20524 INVALID PERIOD SPECIFICATION
used as a system-period temporal table. OR PERIOD CLAUSE FOR PERIOD
period-name. REASON CODE =
8
reason-code.
The table must not contain a security label
column.
9 Explanation
If a column in the system-period temporal A period specification or period clause is invalid.
table is defined as ROWID, the corresponding
history column must be defined as ROWID with period-name
the GENERATED ALWAYS attribute. The period that is invalid.
10 reason-code
The corresponding columns of the system- A numeric value that indicates why the period is
period temporal table and associated history invalid:
table must have the same value for the 1
following attributes: The period name was specified more than one
• Column name time for the table reference.
• Data type 2
The SYSTEM_TIME period was specified, but
• Data type length (excluding inline LOB length the table is not a system-period temporal
or XML length in the base table), precision, table.
and scale
3
• Null attribute period-name violated the following
• Hidden attribute requirement: each expression must return a
• Field procedure value of a built-in data type and can contain
any of the following supported operands:
• FOR MIXED, BIT, or SBCS DATA attribute and
CCSID • A constant
11 • A special register
The table must not have a column mask or row • A variable, which can be either a host
permission. variable, an SQL variable, an SQL parameter,
a transition variable, or a global variable
System action • A parameter marker
The statement cannot be processed. • A CAST specification, where the cast operand
is a supported operand
User response • An expression that uses arithmetic operators

and operands
Correct the syntax, and resubmit the statement. • A scalar function whose arguments are
supported operands (Nested function
SQLSTATE invocations are not permitted.)
428HX These rules have the following exceptions:
Related concepts • A period specification or period clause for a
Temporal tables and data versioning (Db2 view must not contain an untyped parameter
Administration Guide) marker.
Archive-enabled tables and archive tables • The source expression of SET CURRENT
(Introduction to Db2 for z/OS) TEMPORAL BUSINESS_TIME and SET
Related tasks CURRENT TEMPORAL SYSTEM_TIME
Creating a system-period temporal table (Db2 statements must not contain a parameter
Administration Guide) marker or a transition variable.
Related reference

4 Related tasks
The period specification or period clause was Querying temporal tables (Db2 Administration
specified for a view where the view definition Guide)
includes a user-defined function. Related reference
5 CURRENT TEMPORAL BUSINESS_TIME (Db2
The precision of an expression must be greater SQL)
than the precision of the columns of the period. CURRENT TEMPORAL SYSTEM_TIME (Db2 SQL)
If the expression is a string, it is first converted
to a timestamp, and the value must not contain -20525 THE REQUESTED ACTION IS NOT
more significant fractional seconds digits than VALID FOR TABLE table-name
the precision of the column. BECAUSE THE TABLE IS THE
6 WRONG TYPE OF TABLE. REASON
FOR SYSTEM_TIME was specified. However, CODE = reason-code
the value of the CURRENT TEMPORAL
SYSTEM_TIME special register is not null, and Explanation
the SYSTIMESENSITIVE bind option is set
to YES. Therefore, you cannot also explicitly The table cannot be used as specified.
specify FOR SYSTEM_TIME. table-name
7 The name of the table.
FOR BUSINESS_TIME was specified. However, reason-code
the value of the CURRENT TEMPORAL The reason for the message or SQL code, indicated
BUSINESS_TIME special register is not null, by one of the following values:
and the BUSTIMESENSITIVE bind option is set
to YES. Therefore, you cannot also explicitly 1
specify FOR BUSINESS_TIME. An ALTER TABLE statement with an ADD
PERIOD clause was specified for a history
8
table, an archive-enabled table, or an archive
The period specification or period clause was
table. A period cannot be specified for these
specified for one of the following items:
types of tables.
• A table that is not an application-period 4
temporal table An ALTER TABLE statement with a DROP
• A view for which an application-period VERSIONING clause was specified, but the
temporal table is not referenced in the table is not a system-period temporal table.
outermost FROM clause of the view 5
definition, or an INSTEAD OF trigger is An ALTER TABLE statement with a DROP
defined on the view. VERSIONING clause was specified. However,
9 system-period data versioning cannot be
An expression must not return a value with dropped if there are any triggers, functions,
a time zone if the begin and end columns of procedures, views, or materialized query tables
the specified period are defined as timestamp that reference historical versions of rows in the
without time zone. table.
7
System action An ALTER TABLE statement with a ROTATE
PARTITION clause was specified for a system-
The statement cannot be processed. period temporal table, a history table, an
archive-enabled table, or an archive table.
User response 8
An ALTER TABLE statement with an ADD
CLONE clause was specified for a system-
period temporal table, a history table, an
SQLSTATE archive-enabled table, or an archive table.
428HY 9
A TRUNCATE statement attempted to truncate
a system-period temporal table. A system-
period temporal table cannot be truncated.

10 System action
An ALTER TABLESPACE statement attempted
to alter the CCSID of a table space that The statement cannot be processed.
contains a system-period temporal table, a
history table, an archive-enabled table, or an User response
archive table.
Verify that the SQL statement contains the correct
11 period and table names, including any required
A CREATE TABLE or ALTER TABLE statement qualifiers.
attempted to define a referential constraint
where either the parent or child table is a
history table or an archive table. SQLSTATE
13 4274M
An ALTER TABLE statement with an ADD
-20528 THE TARGET OF THE DATA
COLUMN clause was specified for a history
CHANGE OPERATION IS A TABLE
table or an archive table.
table-name, WHICH INCLUDES
16 A PERIOD period-name. A ROW
An ALTER TABLE statement was specified to THAT THIS DATA CHANGE
add a generated column other than a ROWID OPERATION ATTEMPTED TO
to a system-period temporal table or archive- MODIFY WAS ALSO MODIFIED BY
enabled table. ANOTHER TRANSACTION.
19
An ALTER TABLE statement with a DISABLE Explanation
ARCHIVE clause was specified, but the table is
not an archive-enabled table. An attempt was made to change a row in a system-
period temporal table, but the row has been modified
by another transaction. The requested change would
System action result in a row in the associated history table whose
The statement cannot be processed. row-begin column is higher than the row-end column.
table-name
User response The name of the system-period temporal table.
Change the statement to specify the name of a table period-name
for which the action is valid, or specify a different The name of the period.
action for the current table. This error can occur when two concurrent transactions
are accessing the same row for data changes.
SQLSTATE
428HZ System action
Administration Guide) User response
Archive-enabled tables and archive tables Reissue the statement.
-20527 period-name IS NOT A PERIOD IN SQLSTATE

TABLE table-name 57062
-20529 THE ARGUMENT OF THE WRAP
Explanation
FUNCTION OR CREATE_WRAPPED
The specified period does not exist in the specified PROCEDURE IS NOT VALID
table.
period-name Explanation
The name of the period.
The argument of the WRAP function or the
table-name CREATE_WRAPPED procedure is not a valid SQL
The name of the table. statement. The valid statements are:

• CREATE FUNCTION (compiled SQL scalar) Programmer response
• CREATE FUNCTION (inlined SQL scalar) Ensure that the statement was wrapped on a
• CREATE FUNCTION (SQL table) supported platform, and that the statement is not
• CREATE PROCEDURE (SQL - native) corrupted.
• CREATE TRIGGER (basic)
SQLSTATE
• CREATE TRIGGER (advanced)
42638
System action Related tasks
The statement that contains the WRAP function or Obfuscating source code of SQL procedures,
CREATE_WRAPPED procedure cannot be processed. SQL functions, and triggers (Db2 Administration
Guide)
Related reference
Programmer response
WRAP (Db2 SQL)
Make sure the argument to the WRAP function or the CREATE_WRAPPED stored procedure (Db2 SQL)
CREATE_WRAPPED procedure is a valid statement.
-20531 THE VERSION NUMBER actual-
SQLSTATE version SPECIFIED IN A BINARY
XML VALUE IS NOT SUPPORTED.
5UA0O THE HIGHEST SUPPORTED
Related tasks VERSION IS supported-version.
Obfuscating source code of SQL procedures,
SQL functions, and triggers (Db2 Administration Explanation
Guide)
The version number contained in a binary XML value
Related reference specifies a version of the binary XML specification that
WRAP (Db2 SQL) is not supported. The binary XML value cannot be
CREATE_WRAPPED stored procedure (Db2 SQL) parsed.
-20530 AN OBFUSCATED STATEMENT IS actual-version

NOT VALID. REASON CODE= The version that is specified.
reason-code. supported-version
The highest version of the binary XML specification
that is known to be supported.
Explanation
An error occurred during processing of a data System action
definition statement that includes the WRAPPED
clause. The statement cannot be processed.
reason-code
The Db2 reason code value that indicates the Programmer response
reason for the failure. For explanations of reason Make sure that XML values either are formatted as
codes, see Part 2, “Db2 reason codes,” on page binary XML data conforming to a version of the binary
373. XML specification that the server supports or are
reason-code is one of the following values: formatted as textual XML data.
1
The statement was wrapped on a platform or SQLSTATE
version that is not supported. 22544
2
-20535 THE DATA CHANGE OPERATION
The obfuscated portion of the statement is
operation IS NOT SUPPORTED
corrupted.
FOR THE TARGET OBJECT object-
name BECAUSE OF AN IMPLICIT
System action OR EXPLICIT SYSTEM PERIOD
The statement cannot be processed. SPECIFICATION INVOLVING

period-name. REASON CODE: • Set the CURRENT TEMPORAL SYSTEM_TIME
reason-code. special register to the null value and try the data
change operation again.
Explanation • If the statement is in a package that you
do not want to be affected by the setting
Db2 cannot perform the specified data change of the CURRENT TEMPORAL SYSTEM_TIME
operation, because the target of the operation special register, bind the package with
references a temporal table for which a period SYSTIMESENSITIVE NO.
specification is in effect. The period specification was
either implicitly specified by a special register or
explicitly specified in the fullselect that was specified SQLSTATE
as the target. 51046
operation Related tasks
The data change operation.
Manipulating data in a system-period temporal
object-name table (Db2 Administration Guide)
The name of the target object. Related reference
period-name BIND and REBIND options for packages, plans,
The name of the period that is invalid. Possible and services (Db2 Commands)
values are BUSINESS_TIME or SYSTEM_TIME. CURRENT TEMPORAL SYSTEM_TIME (Db2 SQL)
reason-code
A numeric value that indicates why the operation is -20539 THE QUERY FAILED BECAUSE A
invalid. reason-code can have one of the following NEGATIVE VALUE OR THE NULL
values: VALUE IS USED IN THE clause
CLAUSE
1
The data in a system-period temporal table
cannot be changed when a period specification Explanation
is in effect. In this case, this restriction
A query can include an OFFSET clause to begin
was violated, because both of the following
fetching rows starting at a specified row number. A
conditions exist:
query can include a FETCH FIRST clause or a LIMIT
• The data change operation directly or clause, with or without an associated OFFSET clause,
indirectly references a system-period to control the number of rows that are returned from
temporal table. The target of the operation the query. The row count value for these clauses can
is one of the following objects: be specified as a constant or variable that must be a
positive numeric value or zero. The value must not be
– A system period temporal table
the null value.
– A view that is defined with an outer
fullselect that either directly or indirectly clause
references a system-period temporal table The clause that contains the negative value or the
in the FROM clause NULL value.
• A period specification is in effect, because

the CURRENT TEMPORAL SYSTEM_TIME System action
special register contains a non-null value, The statement cannot be processed.
and the SYSTIMESENSITIVE bind option is
set to YES.
User response
System action Change the clause to specify a positive number or
zero, and issue the query again.
SQLSTATE
User response
2201W, 2201X
Take the action for the specified reason code:
-20547 THE STATEMENT FAILED BECAUSE
1 THE TARGET OF AN ASSIGNMENT

IS A READ-ONLY VARIABLE. System action
VARIABLE NAME: variable-name.
Explanation
Programmer response
Global variables can generally be used as the target
of an assignment in various SQL statements, with the Change the array arguments or the operator.
appropriate write access. However, the definition of If the operator name is UNNEST, take one of the
some global variables makes them read-only. This following actions:
applies to some built-in global variables and also
to user-defined variables that are defined using the • Specify only one associative array argument.
CONSTANT clause. A variable that is read-only cannot • Specify ordinary array arguments only with other
be used in an SQL statement as the target of an ordinary array arguments.
assignment. • Specify an expression that does not include a scalar
variable-name fullselect.
The name of the variable that is read-only.
SQLSTATE
System action 428I4
The statement cannot be processed. Related reference
collection-derived-table (Db2 SQL)
Programmer response
-20551 CONSTRUCTING AN ASSOCIATIVE
Change the target variable to a variable that is not
ARRAY FAILED BECAUSE THE
read-only.
INPUT DATA INCLUDES AT LEAST
ONE DUPLICATE ARRAY INDEX
SQLSTATE VALUE. DUPLICATED INDEX
VALUE: value.
428I3
Related reference
Explanation
Built-in global variables (Db2 SQL)
compound-statement (Db2 SQL) In an associative array, each element is associated
with a unique index value. When the ARRAY_AGG
-20550 AN ARGUMENT, OR COMBINATION aggregate function is used to construct an array, if
OF ARGUMENTS, SPECIFIED FOR more than one element is associated with the same
THE operator-name OPERATOR array index value, only one of the element values can
ARE NOT VALID. be included in the array. This potential loss of element
data is the reason that index values must be unique
within the input data that is used to construct an
Explanation associative array.
An operator was specified with an argument, or value
combination of arguments, that are not valid in the The duplicate array index value.
context where they were used.
operator-name System action
The name of the operator with the invalid
arguments. The statement cannot be processed.
If the operator name is UNNEST, the error was issued

for one of the following reasons: User response
• More than one associative array argument was Change the input data so that there are no duplicate
specified. array index values. When you use the ARRAY_AGG
aggregate function, you might need to add predicates
• One ordinary array argument was specified with an to the query that produces the aggregation grouping
associative array argument. sets to ensure that none of the rows include duplicate
• An argument must not include a scalar fullselect. values for the index-expression argument of the
ARRAY_AGG function.

SQLSTATE -20554 TABLE table-name WAS
SPECIFIED AS AN ARCHIVE
22545 TABLE, BUT THE TABLE
Related reference DEFINITION IS NOT VALID FOR
ARRAY_AGG (Db2 SQL) AN ARCHIVE TABLE. REASON
CODE = reason-code.
-20553 AN ENABLE ARCHIVE CLAUSE
WAS SPECIFIED FOR TABLE table- Explanation
name, BUT THE TABLE CANNOT BE
USED AS AN ARCHIVE-ENABLED An ALTER TABLE statement attempted to define a
TABLE. REASON CODE = reason- table as an archive table, but the table definition is not
code. valid.
table-name
Explanation The name of the table that was specified to be an
archive table.
The ALTER TABLE statement attempted to define
a table as an archive-enabled table, but the table reason-code
definition is not valid. A numeric value that identifies the reason for the
error. reason-code can have one of the following
table-name values:
1
reason-code The table is an existing archive table or one of
A numeric value that identifies the reason for the the following types of tables:
values: • Archive-enabled table. The table was defined
as an archive-enabled table by a previous
1 statement, or the current statement defines
The table is already defined as an archive- the table as an archive-enabled table.
enabled table or an archive table.
• System-period temporal table.
3
• History table.
The table is a materialized query table.
• Declared global temporary table.
4
The table has a column mask or row • Created global temporary table.
permission. • Materialized query table.
8 • View.
The table is a system-period temporal table or
• Auxiliary table.
history table.
• Clone table.
9
The table includes a period definition. • Table with a clone defined on it.
• Table that was implicitly created for an XML
System action column.
The statement cannot be processed. None of these tables can be defined as an

archive table.
User response 2
The table has an incomplete table definition.
3
The table is not the only table in the table
SQLSTATE space. An archive table must be the only table
428HM in the table space.
4
Related concepts
The table contains an identity column, a
Archive-enabled tables and archive tables row-begin column, a row-end column, a
(Introduction to Db2 for z/OS) transaction-start-ID column, or a generated
Related reference expression column. Archive tables cannot
ALTER TABLE (Db2 SQL) contain any of these columns.

5 corresponding archive table column must be
The table includes a period definition, which is a row change timestamp column with the
not allowed for an archive table. GENERATED ALWAYS attribute.
6
The table is involved in a referential integrity System action
constraint, which is not allowed for an archive
table. The statement cannot be processed.
7
The archive table does not have the same User response
number of columns as the table that is to Correct the syntax and resubmit the statement.
be used as the archive-enabled table. Both of
these tables must have the same number of
columns. SQLSTATE
8 428HX
The table contains a security label column, Related concepts
which is not allowed in an archive table.
The table does not have a ROWID column to Related reference
correspond to the one in the table that is to
be used as the archive-enabled table. If the
archive-enabled table has a ROWID column, CREATE TABLE (Db2 SQL)
the corresponding archive table column must
be a ROWID column with the GENERATED -20555 AN ARCHIVE-ENABLED TABLE IS
ALWAYS attribute. NOT ALLOWED IN THE SPECIFIED
CONTEXT. REASON CODE reason-
10 code.
One of the following column attributes does
not match the attribute for the corresponding
column in the table that is to be used as the Explanation
archive-enabled table: The statement or query cannot reference an archive-
• Name enabled table for the indicated reason.
• Data type reason-code
A numeric value that identifies the reason for the
• Data type length (excluding inline LOB length
or XML length in the base table), precision,
values:
and scale
• Null attribute 1
The SQL statement cannot reference both an
• Hidden attribute archive-enabled table and a temporal table.
• Field procedure (The temporal table can be either a system-
• FOR BIT, SBCS, or MIXED DATA attribute period temporal table or an application-period
temporal table.) For example, a query, a view
• CCSID definition, or an INSERT, UPDATE, or DELETE
These attributes for the corresponding statement cannot reference both of these table
columns of an archive-enabled table and the types.
associated archive table must be the same. 2
11 You cannot insert rows into or update an
The table has a column mask or row archive-enabled table when the value of
permission, neither of which are allowed for an the SYSIBMADM.MOVE_TO_ARCHIVE global
archive table. variable is Y.
12 3
The table does not have a row change An SQL table function cannot reference an
timestamp column to correspond to the one archive-enabled table when both of the
in the table that is to be used as the archive- following conditions are true:
enabled table. If the archive-enabled table
has a row change timestamp column, the

• The value of the SYSIBMADM.GET_ARCHIVE function-name
global variable is Y. Identifies the name of the function that returned
• The value of the ARCHIVESENSITIVE bind the error.
option is YES.
4
System action
The definition of a row permission or column The statement cannot be processed.
mask that is activated by a data change
statement or query cannot reference an
archive-enabled table when both of the
User response
following conditions are true: One of the following options can be used to avoid the
error:
• The value of the SYSIBMADM.GET_ARCHIVE
global variable is Y. • Change the values of the input arguments to the
• The value of the ARCHIVESENSITIVE bind scalar function to return a single value from the
option is YES. multiple value result.
• As an alternative to the scalar function invocation,
System action create a user-defined table function, if possible, to
return a result with multiple values.
SQLSTATE
User response
22547
Change the query or statement to remove the
reference to the archive-enabled table and specify Related reference
another table. CREATE FUNCTION (Db2 SQL)
-20565 THE REPLACEMENT VALUE FOR

SQLSTATE built-in-global-var IS INVALID
428I6
Archive-enabled tables and archive tables The value specified for assignment to a built-in global
(Introduction to Db2 for z/OS) variable is not a valid for that built-in global variable.
Administration Guide) System action
Related reference
Built-in session variables (Db2 SQL)
ARCHIVESENSITIVE bind option (Db2
Commands) Programmer response
CREATE FUNCTION (SQL table) (Db2 SQL) Correct the replacement value.
CREATE PERMISSION (Db2 SQL)
CREATE MASK (Db2 SQL) SQLSTATE
CREATE TRIGGER (basic) (Db2 SQL)
42815
-20556 THE OPERATION FAILED BECAUSE Related reference
MULTIPLE RESULT VALUES Built-in global variables (Db2 SQL)
CANNOT BE RETURNED FROM
SET assignment-statement (Db2 SQL)
A SCALAR FUNCTION function-
name. -20567 TABLE table-name CANNOT BE
DEFINED AS A DEPENDENT
Explanation OF REFERENTIAL CONSTRAINT
constraint-name. REASON reason-
A scalar function was invoked with arguments that do
codereason-code.
not allow the return of multiple result values for a
single invocation. The processing of the scalar function
determined a result the consisted of multiple values.

The object of an ALTER TABLE statement cannot be The statement cannot be processed. The SQLCA is
defined as a dependent table in a referential constraint formatted. Message DSNL031I or DSNL032I, which
for the reason indicated by the reason code. might contain additional diagnostic information, might
be issued to the MVS console.
table-name
The name of the table that is named as the
dependent table. Programmer response
constraint-name Notify the DBA for assistance in analysis of the SQL
The name of the referential constraint in which the statement which yielded this SQLCODE.
altered table that is the dependent table.
reason-code Problem determination
by one of the following values: The 'reason-code' identifies the DDM code point which
represents the DDM reply message received from the
1 remote server in response to the attempt to execute
PERIOD BUSINESS_TIME was specified as part the SQL statement. These represent internal errors
of a temporal referential constraint definition detected at the remote server or possibly, by the local
that would result in a referential cycle. The Db2 functions.
parent and child tables must not be the same
table in a temporal referential constraint, and The 'reason-code' value is the two-byte hexadecimal
the child table must not be a descendent, code point for the DDM reply message that represents
directly or indirectly, of another table that is a the error and is one of the following:
descendent of the parent table. • X'1254' - CMDCHKRM
2 • X'220A' - DSCINVRM
An index that enforces a temporal referential • X'220E' - DTAMCHRM
constraint contains an INCLUDE column. This
• X'1245' - PRCCNVRM
is not allowed.
• X'2202' - QRYNOPRM
System action • X'220F' - QRYPOPRM
• X'2207' - RDBACCRM
• X'2204' - RDBNACRM
User response • X'124C' - SYNTAXRM
Correct the constraint definition. A two-byte 'sub-code' accompanies 'reason-codes'

X'220A' (DSCINVRM), X'1245' (PRCCNVRM), and
X'124C' (SYNTAXRM). In all other cases, the 'sub-
SQLSTATE code' is zero.
42915 The 'sub-code' when nonzero, consists of two bytes
-30000 EXECUTION FAILED DUE TO A such that the high-order byte indicates the site at
DISTRIBUTION PROTOCOL ERROR which the error was detected. This is X'01' if the error
THAT WILL NOT AFFECT THE was detected by the local Db2; it is X'02' if the error
SUCCESSFUL EXECUTION OF was detected by the remote server. The low-order byte
SUBSEQUENT COMMANDS OR SQL is dependent on the 'reason-code' as follows:
STATEMENTS: REASON reason- • Description Error Code (DSCERRCD) if 'reason-code'
code (sub-code) = X'220A' (DSCINVRM).
• Syntax Error Code (SYNERRCD) if 'reason-code' =
Explanation X'124C' SYNTAXRM).
A DRDA protocol error has resulted which prevented • Conversational Protocol Error Code (PRCCVNCD) if
successful execution of the current SQL statement. 'reason-code' = X'1245' (PRCCNVRM).
The error was such that it will not preclude the
For a detailed discussion of the semantics of the
successful execution of further SQL statements.
DDM terms DSCERRCD, SYNERRCD, and PRCCNVCD,
see DRDA Volume 3 "Distributed Data Management

Architecture" (Open Group Library - Data Management The product identifier (PRDID) value is an 8-byte
Standards). character value in pppvvrrm format, where: ppp is
a 3-letter product code; vv is the version;rr is the
SQLSTATE release; and m is the modification level. In Db2 12
for z/OS, the modification level indicates a range of
58008 function levels:
-30002 THE SQL STATEMENT CANNOT DSN12015 for V12R1M500 or higher.
BE EXECUTED DUE TO A PRIOR DSN12010 for V12R1M100.
CONDITION IN A CHAIN OF
STATEMENTS For more information, see Product identifier
(PRDID) values in Db2 for z/OS (Db2
Administration Guide).
Explanation
reason-code
An SQL statement was chained to PREPARE, but the A numeric value that identifies the function.
PREPARE statement has received a warning SQLCODE Possible values are:
that requires the program or user to either re-issue
0010
the chained statement or issue a different SQL
LONG_STMTS
request. This error can occur only in a client/server
environment. 0020
LONG255_IDS
• A distributed client using DRDA has chained an
OPEN statement to a PREPARE, but the PREPARE 0030
statement received SQLCODE +495. EXTENDED_DESCRIBE
0040
System action EXTENDED_DIAGNOSTICS
0050
The statement cannot be executed as chained.
KEEP_DYNAMIC
0060
Programmer response UNICODE_CONVERSION
The statement must be sent again as a separate 0070
request. ROWSET_CURSOR
0080
SQLSTATE DYNAMIC_SCROLLABLE_CURSOR
57057 0090
FLEX_BLOCKING
-30005 EXECUTION FAILED BECAUSE
FUNCTION NOT SUPPORTED BY 0100
THE SERVER: LOCATION location- PACKAGE_PATH
name PRODUCT ID product- 0110
identifier REASON reason-code REOPT_ONCE
(sub-code) 0120
REOPT_ALWAYS
Explanation 0130
The current SQL statement failed because the SQL REOPT_NONE
statement was routed to a server that does not 0140
support the requested function. The error was such SCROLL_ORIENTATION
that it will not preclude the successful processing of 0150
further SQL statements. DIV_SCALE
location-name 0160
The name of the server that could not support QUERY_INSTANCE
the required database protocols to perform the
0170
requested function.
MULTIROW_INPUT
product-identifier
0180
An alphanumeric string that identifies the product.
SQL_ATTRIBUTES

0190 SQLSTATE
SQL_GET
56072
0200
SET -30020 EXECUTION FAILED DUE TO A
0210 DISTRIBUTION PROTOCOL ERROR
BIND_DEPLOY THAT CAUSED DEALLOCATION OF
THE CONVERSATION: REASON
0220 reason-code (sub-code)
DUP_QUERY_SEMANTICS
0230 Explanation
BINARY_XML_FORMAT
A DRDA protocol error has occurred that prevented the
0240
successful execution of the current SQL statement or
BIND_DEPLOY_FUNCTION
command, as well as any subsequent SQL statements.
0250
REMOTE_QUERY_OFFLOAD The 'reason-code' identifies the DDM code point which
represents the DDM reply message received from the
0260 remote server in response to the attempt to execute
ORDINARY_ARRAY_PARM the SQL statement. These represent internal errors
sub-code detected at the remote server site or possibly, by the
A single-byte value that indicates how the error local Db2 functions.
was detected in the network. If no additional
The 'reason-code' value is the two-byte hexadecimal
information is available, this value is 0.
code point for the DDM reply message that represents
'01'x the error and is one of the following:
The local Db2 that is acting as the
• X'1232' - AGNPRMRM
requester detected the error. The values that
are provided for location-name and product- • X'1254' - CMDCHKRM
identifier identify the server in error. • X'220A' - DSCINVRM
'02'x • X'220E' - DTAMCHRM
The server detected the error. The values that
• X'0010' - FDODSC
are provided for location-name and product-
identifier identify the location and level of the • X'1218' - MGRDEPRM
local Db2 server. • X'1245' - PRCCNVRM
'03'x or '04'x • X'241A' - QRYDSC
An intermediate server (hop site) detected the
• X'2202' - QRYNOPRM
error. The values that are provided for location-
name and product-identifier identify the server • X'220F' - QRYPOPRM
in error. • X'2207' - RDBACCRM
• X'2204' - RDBNACRM
System action
• X'124C' - SYNTAXRM
The statement cannot be processed. The SQLCA is
A two byte sub-code accompanies 'reason codes'. The
formatted.
sub-code, when nonzero, consists of two bytes such
that the high-order byte indicates the site at which
Programmer response the error was detected. This is X'01' if the error was
detected by the local Db2; It is X'02' if the error was
Notify the DBA for assistance in analyzing the SQL
detected by the remote server. The low-order byte is
statement that prompted this SQLCODE.
dependent upon the 'reason code' as follows:
Problem determination • Description Error Code (DSCERRCD) if reason code=

X'220A ' (DSCINVRM).
Use the reason-code value that was specified in the • Syntax Error Code (SYNERRCD) if reason code =
code to determine which function was not supported. X'124C ' (SYNTAXRM).
Use the sub-code value to further identify the problem.
• Conversational Protocol Error Code (PRCCVNCD) if
reason code = X'1245' (PRCCNVRM).

• Manager Dependency Error Code (DEPERRCD) if supported in the EXCSATRD that reported the error.
reason code = X' 1218' (MGRDEPRM). Refer to the DDM term MGRLVL in the DRDA Volume
3 "Distributed Data Management Architecture" (Open
For a detailed discussion of the semantics of the
Group Library - Data Management Standards) for the
DDM terms DSCERRCD, SYNERRCD, PRCCNVCD, and
2-byte hexadecimal values.
DEPERRCD, see DRDA Volume 3 "Distributed Data
Management Architecture" (Open Group Library - Data
Management Standards). System action
System action
The statement cannot be processed. The SQLCA is Programmer response
formatted and the conversation on which the error
Notify the system programmer for analysis of the
was detected is deallocated. Message DSNL031I or
condition that caused this SQLCODE.
DSNL032I, which might contain additional diagnostic
information, might be issued to the MVS console.
SQLSTATE
The connection to the server has been broken, and -30025 EXECUTION FAILED BECAUSE
the server has, therefore, rolled back the unit of work. FUNCTION IS NOT SUPPORTED
In this case, the only SQL statement that may be BY THE SERVER WHICH
successfully executed is ROLLBACK. However, if the CAUSED TERMINATION OF THE
requester detects this error on a COMMIT, then it is CONNECTION: LOCATION location
unknown whether the unit of work was committed or PRODUCT ID identifier REASON
rolled back at the server. reason-code (sub-code)
58009 The current SQL statement failed because the SQL
statement was routed to a server that does not
Related information
support the requested function. A new connection is
DSNL031I (Db2 Messages) required to allow the successful execution of further
DSNL032I (Db2 Messages) SQL statements.
-30021 EXECUTION FAILED DUE TO location-name

A DISTRIBUTION PROTOCOL The name of the server that could not support
ERROR THAT WILL AFFECT THE the required database protocols to perform the
SUCCESSFUL EXECUTION OF requested function.
SUBSEQUENT COMMANDS OR SQL identifier
STATEMENTS: MANAGER manager A string in one of the following forms:
AT LEVEL level NOT SUPPORTED
ERROR • product-identifier
• product-identifier:clientapplcompat-
value:package-applcompat-value
Explanation
product-identifier
A DRDA error occurred that prevented the successful
An alphanumeric string that identifies the
execution of the current SQL statement or command
product.
and any subsequent SQL statements.
The product identifier (PRDID) value is an
A manager-level conflict was detected during the
8-byte character value in pppvvrrm format,
processing of the DDM EXCSAT command. Refer to
where: ppp is a 3-letter product code; vv is
the DRDA Volume 3 "Distributed Data Management
the version;rr is the release; and m is the
Architecture" (Open Group Library - Data Management
modification level. In Db2 12 for z/OS, the
Standards) for a detailed description of EXCSAT
modification level indicates a range of function
processing and errors.
levels:
The manager value is the 2-byte hexadecimal code
DSN12015 for V12R1M500 or higher.
point of the DDM manager class identified as not
DSN12010 for V12R1M100.

For more information, see Product identifier 0110
(PRDID) values in Db2 for z/OS (Db2 REOPT_ONCE
Administration Guide). 0120
clientapplcompat-value REOPT_ALWAYS
The client application compatibility value that 0130
is provided by a client application: REOPT_NONE
• For applications that use Java drivers, 0140
clientapplcompat-value is the value of SCROLL_ORIENTATION
the clientApplcompat Connection or 0150
DataSource property for the connection to DIV_SCALE
the Db2 for z/OS data server.
0160
• For applications that use other clients QUERY_INSTANCE
or drivers, such as the CLI driver,
clientapplcompat-value is the value of the 0170
ClientApplCompat configuration keyword. MULTIROW_INPUT
0180
If the application does not provide a client
SQL_ATTRIBUTES
application compatibility value, this value is an
asterisk (*). 0190
SQL_GET
package-applcompat-value
The APPLCOMPAT bind option value for the 0200
package that was used to execute the first SET
SQL statement in the application. For more 0210
information, see: BIND_DEPLOY
Application compatibility on Db2 for z/OS 0220
Setting the Db2 for z/OS application DUP_QUERY_SEMANTICS
compatibility for your JDBC and SQLJ 0230
applications (Db2 Application Programming BINARY_XML_FORMAT
for Java) 0240
reason-code BIND_DEPLOY_FUNCTION
A numeric value that identifies the function. 0600
Possible values are: CLIENTAPPLCOMPAT_INCONSISTENCY
0010 For special instructions on actions to take when
LONG_STMTS reason-code is 0600, see “Database administrator
0020 response” on page 362.
LONG255_IDS
sub-code
0030 A single-byte value that indicates how the error
EXTENDED_DESCRIBE was detected in the network. If no additional
0040 information is available, this value is 0.
EXTENDED_DIAGNOSTICS '01'x
0050 The local Db2 that is acting as the
KEEP_DYNAMIC requester detected the error. The values that
0060
identifier identify the server in error.
UNICODE_CONVERSION
'02'x
0070
The server detected the error. The values that
ROWSET_CURSOR
0080 identifier identify the location and level of the
DYNAMIC_SCROLLABLE_CURSOR local Db2 server.
0090 '03'x or '04'x
FLEX_BLOCKING An intermediate server (hop site) detected the
0100 error. The values that are provided for location-
PACKAGE_PATH

name and product-identifier identify the server If you bind copies of the driver packages, you
in error. need to modify the configuration keyword or bind
option that controls the current package set so
System action that applications use the correct set of driver
packages.
The statement cannot be processed. The current unit
See V12R1Mnnn application compatibility levels
of work is rolled back. The SQLCA is formatted.
for data server clients and drivers (Db2
If the reason-code is 0600, a companion DSNL076I Application programming and SQL) for more
message might also be issued to the Db2 server information.
system console. • If identifier is in the format product-
identifier:*:package-applcompat-value, a client
Programmer response application compatibility value was not set for the
application. In addition, package-applcompat-value
Contact the database administrator for assistance
is greater than V12R1M500, and the client or
in analyzing the SQL statement that prompted this
driver is not at a level that supports the package
SQLCODE.
APPLCOMPAT level package-applcompat-value. Take
one of the following actions.
– Upgrade the client or driver. Refer to V12R1Mnnn
Use the reason-code value that was specified in the application compatibility levels for data server
code to determine which function was not supported. clients and drivers (Db2 Application programming
Use the sub-code value to further identify the problem. and SQL) for information on required client driver
levels.
Database administrator response Tip: It is recommended that after you upgrade
the client or driver, set the client application
If reason-code is 0600, use clientapplcompat-value
compatibility level for the application to a value
and package-applcompat-value to determine the
that is less than or equal to package-applcompat-
cause of the error and fix the problem:
value.
• If identifier is in the – If it is not yet possible to upgrade the client or
format product-identifier:clientapplcompat- driver, bind or rebind the client or driver packages
value:package-applcompat-value, with the APPLCOMPAT value set to V12R1M500 or
clientapplcompat-value is greater than package- lower.
applcompat-value. clientapplcompat-value must be
less than or equal to package-applcompat-value. For drivers only, you can use the DSNTIJLC job
to bind copies of the driver packages, or the
Determine whether the application uses any DSNTIJLR job to rebind the driver packages, at the
capabilities for which the minimum function level is correct application compatibility level.
greater than package-applcompat-value. Then take
one of the following actions: If you bind copies of the driver packages, you
need to modify the configuration keyword or bind
– If the application does not use any capabilities option that controls the current package set so
that require a higher application compatibility that applications use the correct set of driver
setting, change the client application compatibility packages.
setting to package-applcompat-value.
– If the application uses capabilities that require
SQLSTATE
clientapplcompat-value, use a version of the IBM
data server driver or client for which the package 56073
application compatibility is greater than or equal
-30030 COMMIT REQUEST WAS
to clientapplcompat-value.
UNSUCCESSFUL, A DISTRIBUTION
Query SYSIBM.SYSPACKAGES to find existing IBM PROTOCOL VIOLATION HAS BEEN
data server driver or client packages at the right DETECTED, THE CONVERSATION
application compatibility level. If no packages HAS BEEN DEALLOCATED.
exist, bind or rebind driver or client packages. For ORIGINAL SQLCODE=original-
drivers only, you can use the DSNTIJLC job to bind sqlcode AND ORIGINAL
copies of the driver packages, or the DSNTIJLR SQLSTATE=original-sqlstate
job to rebind the driver packages, at the correct
application compatibility level.

Explanation codes, see Part 2, “Db2 reason codes,” on page
373.
The application requested COMMIT operation was
unsuccessful and the response from the remote resource-type and resource-name
server and the SQLCODE that was returned from the The type and name of the resource that the
remote server are inconsistent. For example, the reply message identifies. For an explanation of resource-
message from the remote server indicates that a type and resource-name values, see Resource
COMMIT operation did not complete successfully but types (Db2 Messages).
the SQLCODE returned from the remote server was product-identifier
greater than or equal to zero. The unit of work has An alphanumeric string that identifies the product.
been rolled back and the connection with the remote
The product identifier (PRDID) value is an 8-byte
server has been deallocated.
character value in pppvvrrm format, where: ppp is
a 3-letter product code; vv is the version;rr is the
System action release; and m is the modification level. In Db2 12
An alert was generated. A DSNL031I message may
function levels:
have been written to the console. Refer to the
description of this message for further information. DSN12015 for V12R1M500 or higher.
The SQLCODE returned by the remote server is DSN12010 for V12R1M100.
replaced with -30030 and the SQLSTATE returned by For more information, see Product identifier
the AS is replaced with '158013' and the connection (PRDID) values in Db2 for z/OS (Db2
with the remote server has been deallocated. Administration Guide).
The SQLCODE and SQLSTATE values that were rdbname
returned from the remote server are stored in the A sixteen-byte string that identifies the RDBNAME.
SQLERRM field in a string of the following format:
'original-sqlcode 'FF'X original-sqlstate' System action

The statement cannot be processed. The local Db2 is
Programmer response disconnected from the remote server.
Notify the system programmer for assistance in

Programmer response
analyzing the trace data that was generated.
Verify the identify of the resource that was not
SQLSTATE available. The reason the resource is unavailable is
identified by the reason-code value.
58013
Collect the following diagnostic items to help
-30040 EXECUTION FAILED DUE TO determine the cause of the unavailable resource:
UNAVAILABLE RESOURCES THAT
• Console output from the system identified by
WILL NOT AFFECT THE
RDBNAME, and a listing of SYSLOG data set for the
SUCCESSFUL EXECUTION OF
period of time spanning the failure.
SUBSEQUENT COMMANDS OR
SQL STATEMENTS. REASON • Information described for the reason code received.
reason-code TYPE OF RESOURCE
resource-type RESOURCE NAME SQLSTATE
resource-name PRODUCT ID
product-identifier RDBNAME 57012
rdbname -30041 EXECUTION FAILED DUE
TO UNAVAILABLE RESOURCES
Explanation THAT WILL AFFECT THE
SUCCESSFUL EXECUTION OF
The SQL statement or command requires a non-RDB SUBSEQUENT COMMANDS AND
resource that is currently unavailable. SQL STATEMENTS. REASON
reason-code reason-code TYPE OF RESOURCE
The Db2 reason code value that indicates the resource-type RESOURCE NAME
reason for the failure. For explanations of reason resource-name PRODUCT ID

product-identifier RDBNAME -30045 EXECUTION FAILED BECAUSE THE
rdbname DEFINITION OF OBJECT object-
name OF TYPE object-type BEING
Explanation ACCESSED AT server-name-1
DIFFERS FROM THE DEFINITION
The SQL statement or command requires a non-RDB OF THE OBJECT AT server-name-2
resource that is currently unavailable.
reason-code Explanation
The definition of the object, object-name, at server-
codes, see Part 2, “Db2 reason codes,” on page name-1 does not match the definition of the object
at server-name- 2. object-name must have identical
373.
definitions at both servers if either of the following SQL
resource-type and resource-name statement processing occurs, otherwise, the attempt
The type and name of the resource that the to access object-name will fail:
message identifies. For an explanation of resource-
type and resource-name values, see Resource • An SQL statement is system directed at server-
types (Db2 Messages). name-2 to run at server-name-1, and object-name
is referenced or updated in the processing of that
product-identifier statement.
An alphanumeric string that identifies the product.
• An SQL statement is processed at server-name-1
The product identifier (PRDID) value is an 8-byte which is local to the application, and prior SQL
character value in pppvvrrm format, where: ppp is statements of the application session had been
a 3-letter product code; vv is the version;rr is the directed to run at server-name-2 and had referenced
release; and m is the modification level. In Db2 12 or updated object-name.
function levels: object-name
DSN12015 for V12R1M500 or higher.
object-type
DSN12010 for V12R1M100.
The type of object.
For more information, see Product identifier server-name-1
(PRDID) values in Db2 for z/OS (Db2 The name of the server that attempted to access
Administration Guide). the object. Up to 16 characters of the server name
rdbname are displayed.
A sixteen-byte string that identifies the RDBNAME. server-name-2
The name of the server from which the definition
System action of the object was used to create an instance of the
object on server-name-1. Up to 16 characters of
The statement cannot be processed. The local Db2 is the location name are displayed.
disconnected from the remote server.
System action
Programmer response
Verify the identity of the resource that was not
available. The reason the resource is unavailable is
identified by the reason-code value:
Programmer response
Collect the following diagnostic items to help Correct the definition of object-name at either server-
determine the cause of the unavailable resource. name-1 or server-name-2 so that the definitions at
both servers are identical. Then rebuild and rerun the
• Console output from the system identified by application.
RDBNAME, and a listing of SYSLOG data set for the
period of time spanning the failure.
SQLSTATE
• Information described for the reason code received.
428I5
SQLSTATE -30047 STATEMENT FAILED BECAUSE
OBJECT OF TYPE object-
57013 type CANNOT BE ACCESSED

USING DIFFERENT DISTRIBUTED SQLSTATE
PROTOCOLS ON A CONNECTION
FROM server-name-1 TO server- 58008
name-2 Related concepts
Accessing distributed data by using three-part
Explanation table names (Db2 Application programming and
SQL)
SQL statements that reference object-type objects
Related tasks
cannot be processed in the following cases:
Accessing distributed data by using explicit
• The same connection between server-name-1 CONNECT statements (Db2 Application
and server-name-2 uses both application-directed programming and SQL)
access and system-directed access.
• Use of application-directed access and system- -30050 command-or-SQL-statement-type
directed access are mixed in the application. COMMAND OR SQL STATEMENT
INVALID WHILE BIND PROCESS
object-type IN PROGRESS
The type of object.
server-name-1 Explanation
The name of the server that attempted to access
the object. Up to 16 characters of the server name A remote command or remote SQL execution was
are displayed. attempted while a remote bind was in progress.
server-name-2 The only commands allowed during bind are, BIND
The name of the server from which the definition STATEMENT, END BIND, ROLLBACK, or COMMIT.
of the object was used to create an instance of the
object on server-name-1. Up to 16 characters of System action
the location name are displayed.
The request is rejected. The local Db2 is disconnected
from remote server.
System action
Ensure the remote bind has completed before
Programmer response attempting to execute an SQL statement or process
If the application is controlled by a plan bound a remote command. COMMIT and ROLLBACK will
at a Db2 for z/OS requester, and the application terminate the bind processing.
performs commits or rollbacks before any change in
the distributed protocol used by the application, the SQLSTATE
plan should be rebound with the DISCONNECT bind
58011
option set to AUTOMATIC or CONDITIONAL. This will
permit the requester to automatically terminate any -30051 BIND PROCESS WITH
remote server connection during commit or rollback SPECIFIED PACKAGE NAME
processing. AND CONSISTENCY TOKEN NOT
If the application is not controlled by a plan, SQL ACTIVE
RELEASE statements should be executed before
a commit or rollback statement so that remote Explanation
server connections can be terminated before the
application changes distributed protocols. Because the Binding of a statement or end bind was attempted
introduction of extra commit or rollback statements while the package was not undergoing bind
into an application can jeopardize the data integrity processing.
of the application, the application and any stored
procedures it invokes should be changed to use the System action
same distributed protocol for remote SQL statement
The bind statement request or end bind request is
processing.
rejected. The local Db2 is disconnected from the
remote server.

Ensure that the server processing the bind request The user is not authorized to access an RDB.
was not abending when this request was being
processed, or that the package name hasn't changed System action
before terminating the remote bind package request.
The request is rejected.
SQLSTATE
Programmer response
58012
Correct the authorization problem and resubmit the
-30052 PROGRAM PREPARATION job.
ASSUMPTIONS ARE INCORRECT
SQLSTATE
Explanation
08004
The program preparation assumptions in effect for
binding a statement (i.e. BINDSQLSTT command) are -30061 RDB NOT FOUND
incorrect.
Explanation
System action
An attempt was made to access an RDB which
The statement is rejected. cannot be found. This usually means that a requester
specified the server location name incorrectly. The
server responded by indicating that the requester's
Programmer response
specification of the server location name is incorrect.
The creation of the package following this error is Requester or server changes are needed to make the
dependent on the package creation options specified location names consistent. Location names for Db2
at begin bind time. systems are defined in the BSDS DDF record and are
also in the DSNL004I console message when DDF is
SQLSTATE started.
42932
System action
-30053 OWNER AUTHORIZATION FAILURE The request is not processed.

An authorization error associated with the package Ensure the RDB name was correctly specified and
owner is detected. The AS, for example, has resubmit the job.
determined that the binder has specified a package
owner that the binder has no authorization to specify.
SQLSTATE
System action 08004
The begin bind request is rejected. Related concepts
Management of the bootstrap data set (Db2
Programmer response Administration Guide)
Related tasks
Correct the authorization problem and reissue the
Populating the communications database
request.
for use with TCP/IP (Db2 Installation and
Migration)
SQLSTATE Populating the communications database for
42506 use with VTAM (Db2 Installation and Migration)
Starting DDF (Db2 Administration Guide)
-30060 RDB AUTHORIZATION FAILURE
Related information
DSNL004I (Db2 Messages)

-30062 RDB ACCESS FAILURE Explanation
The target does not support a particular object.
Explanation The error causes the termination of the connection
Access to the database failed because the session between the local Db2 and the remote server.
data is expired. Values for object-type
• Two byte hexadecimal DDM code point.
System action
The request is rejected. System action
The command/SQL statement is rejected. The local
User response Db2 is disconnected from the remote server.
Review the application for long periods of inactivity. If
necessary, issue -MODIFY DDF command and specify Programmer response
the SESSIDLE keyword to increase the time-out value
of session data token on the server, and resubmit the Ensure the object has been correctly specified and
job. resubmit the job or reissue the command.
Severity SQLSTATE
0 (informational) 58015
-30072 parameter subcode PARAMETER
SQLSTATE NOT SUPPORTED ERROR
08004
Explanation
Related reference
-MODIFY DDF (Db2) (Db2 Commands) A particular parameter is not supported by either the
application requester or the remote server.
-30070 command COMMAND NOT Values for parameter
SUPPORTED ERROR
• Two byte hexadecimal DDM code point.
Explanation Values for subcode
The target does not support a particular command. • Two byte hexadecimal number defined as follows:
The error causes termination of the connection This subcode is composed of two distinct parts, but
between the local Db2 and the remote server. may optionally be zero. The high-order byte (when
not zero) indicates the site at which the error was
Values for command detected. This is X'01' if the error was detected by
• Two byte hexadecimal DDM code point. the local Db2; it is X'02' if the error was detected by
the remote server. The low order byte is always zero.
System action Common parameters that are not supported include:
The command is rejected. The local Db2 is X'2450'

disconnected from the remote server. Usually this means that the server does not
support the attribute clause on prepare.
Programmer response
System action
Ensure the proper command was issued.
The command/SQL statement is rejected. A
disconnect has occurred.
SQLSTATE
-30071 object-type OBJECT NOT The connection to the server has been broken, and
SUPPORTED ERROR the server has therefore rolled back the unit of work.
In this case, the only SQL statement that may be
successfully executed is ROLLBACK. However, if the

requester detects this error on a COMMIT, then it is X'2110'.
unknown whether the unit of work was committed or Usually means that a requester specified the
rolled back at the server. server location name incorrectly. The server
responded by indicating that the requester's
SQLSTATE specification of the server location name is
incorrect, and the length of the location name
58016 is longer than that supported by the server.
Requester or server changes are needed so the
-30073 parameter subcode PARAMETER
location names are consistent. Location names for
VALUE NOT SUPPORTED ERROR
Db2 systems are defined in the BSDS DDF record
and can also be seen in the DSNL004I console
Explanation message when DDF is started.
The specified parameter value is not supported by X'2120'
either the local Db2 or the remote server. Usually means that the server does not support
the use of double quote string delimiters in SQL
The parameter, is a 2-byte hexadecimal DDM statements. Db2 COBOL applications can use
code point. See DRDA Volume 3 "Distributed Data double quote string delimiters in SQL statements.
Management Architecture" (Open Group Library - Data This requires that the program be precompiled
Management Standards) for a definition of the valid with the SQLDELIM(QUOTESQL) option. If the
code points. Common values for parameter include: server product does not support double quote
X'0035' SQL statement string delimiters, then the program
Usually means that a Db2 server does not support must be modified to use single quote SQL
the single-byte coded character set identifier string delimiters and be precompiled with the
(CCSID) sent by the requester, or a Db2 requester SQLDELIM(APOSTSQL) option.
does not support the single-byte CCSID received X'2121'
from a server. See X'119C' for more information. Usually means that the there is a semantic error
X'1144' with the string that specifies the character used as
DRDA servers return this code point when a Db2 a decimal delimiter in SQL statements.
client specifies a version for a package and the X'213F'
DRDA server does not support versions. Means that the server was processing a bind or
X'119C' rebind command that specified an unsupported
If the subcode information contains X'01', the value for the DYNAMICRULES bind parameter. If
requester does not support the single-byte CCSID the server is a Db2 Version 3 system, specify
that the server wants to use. If the subcode DYNAMICRULES(RUN) or omit the DYNAMICRULES
information contains X'02', the server does not parameter.
support the single-byte CCSID that the requester
The 'subcode', which is a 2-byte hexadecimal number,
wants to use.
consists of two distinct parts and can optionally be
Determine the single-byte CCSIDs for the zero. The high-order byte (when not zero) indicates
requester and server systems. The single-byte the site at which the error was detected. If the error
CCSID for Db2 subsystems is defined in was detected by the local Db2, it is X'01'. If the error
the DSNHDECP module or in a user-supplied was detected by the remote server, it is X'02'. The
application defaults module. One or both partners low-order byte is always zero.
might be using an incorrect CCSID, or support
might need to be added. System action
X'147A' The command or SQL statement is rejected. A
Db2 servers can return this code point when disconnect occurred.
a numeric input host variable is not within the
range that Db2 supports. See the explanation of
SQLCODE -406 for more information. Programmer response
X'14AC' The connection to the server was broken, and the
Db2 servers return this code point when a DRDA server rolled back the unit of work. The only SQL
client requests an authentication mechanism that statement that can be successfully executed is
is not supported by the Db2 server. See the ROLLBACK. However, if the requester detects this error
explanation of Db2 reason code 00D3010E for on a COMMIT, then it is unknown whether the unit of
more information. work was committed or rolled back at the server.

SQLSTATE SQLSTATE
58017 58018
Related concepts -30080 COMMUNICATION ERROR code
Member names (Db2 Installation and Migration) (subcode)
Related tasks
Specifying subsystem CCSIDs (Db2 Explanation
A SNA communications error was detected. SNA
Populating the communications database for Programmer's LU 6.2 Reference contains the valid
use with VTAM (Db2 Installation and Migration) code and subcode values that can appear in this
Populating the communications database message.
for use with TCP/IP (Db2 Installation and
Migration) • code is VTAM's primary LU6.2 return code (RCPRI).
Related reference • subcode takes one of the following forms:
Subsystem CCSIDs and encoding schemes (Db2 – rcsec-sense
– rcsec
DSNTIPF: Application programming defaults
panel 1 (Db2 Installation and Migration) The rcsec portion of subcode is VTAM's secondary
LU6.2 return code (RCSEC).
-30074 REPLY MESSAGE WITH codepoint
The sense portion of subcode is VTAM's sense code.
(svrcod) NOT SUPPORTED ERROR
See for descriptions of sense codes that are often
associated with SNA network definition errors.
Explanation
A reply message codepoint is not recognized or System action
the reply message SVRCOD is not recognized. The
The statement is not executed. The application
error does not affect the processing of subsequent
was disconnected from the server because of
DRDA commands and SQL statements issued by the
a communication failure. A DSNL500I message
application program.
containing additional diagnostic information might be
Values for codepoint issued to the MVS console.
• The codepoint is a two-byte hexadecimal value that
represents a DDM reply message. DRDA Volume 3 Programmer response
"Distributed Data Management Architecture" (Open Review the diagnostic information described in SNA
Group Library - Data Management Standards) Programmer's LU 6.2 Reference for the particular
defines the valid code points for reply messages. LU6.2 return codes. Consult with a communications
Values for SVRCOD expert to determine the cause of the communication
failure.
• The SVRCOD is a one-byte hexadecimal value
which represents the reply messages severity code.
DRDA Volume 3 "Distributed Data Management SQLSTATE
Architecture" (Open Group Library - Data 08001
Management Standards) defines the valid SVRCOD
for reply messages. -30081 prot COMMUNICATIONS
ERROR DETECTED. API=api,
LOCATION=loc, FUNCTION=func,
System action
ERROR CODES=rc1 rc2 rc3
Explanation
Programmer response
A communications error was detected while
The cause of this error could be a mismatch in source communicating with a remote client or server.
and target manager levels or might be an internal error. prot
Identifies the communication protocol that
encountered the error. Currently, 'TCP/IP' is the
only possible value.

api is described by the reason-code and reason-string
Identifies the communication application values.
programming interface (API) used by Db2.
The possible values for reason-code and reason-string
Currently, 'SOCKETS' is the only possible value.
appear below:
loc
The network location of the partner system. • 1 (PASSWORD EXPIRED) -- the password used to
connect to the remote server has expired.
For TCP/IP partners, this field contains the IP
• 2 (PASSWORD INVALID) -- the password used to
address of the partner.
connect to the remote server does not match the
func password stored at the remote server.
The communication function that failed. • 3 (PASSWORD MISSING) -- the remote server
For TCP/IP partners, this field identifies name of rejected the connection request because the request
the socket call that failed. did not include a password.
rc1 • 4 (PROTOCOL VIOLATION) -- the remote server

The first return code indicator. rejected the connection request because the request
did not contain the proper security information.
For TCP/IP partners, this field contains the Error messages or trace records should be produced
TCP/IP return code in decimal format. The return by the server system to explain the nature of the
code values are documented in z/OS UNIX security violation.
System Services: Messages and Codes or z/OS
• 5 (USER-ID MISSING) -- the remote server rejected
Communications Server: IP and SNA Codes.
the connection request because the request did not
rc2 specify a user-id.
The second return code indicator. • 6 (USER-ID INVALID) -- the user-id specified in the
For TCP/IP partners, this field contains the connection request is not defined at the remote
TCP/IP reason code in hexadecimal format. The server system.
reason code values are documented in z/OS UNIX • 7 (USER-ID REVOKED) -- the user-id specified in the
System Services: Messages and Codes orz/OS connection request has been revoked.
Communications Server: IP and SNA Codes.
• 15 (SECURITY FAILURE:secchkcd:svcerrno)—
rc3 Authentication failed at the remote server system.
The third return code indicator. Refer to DRDA Volume 3 "Distributed Data
Management Architecture" (Open Group Library
For TCP/IP partners, this field contains zero.
- Data Management Standards) for a detailed
discussion of the semantics of the DDM terms
System action SECCHKCD and SVCERRNO.
The statement is not executed. The application is • 16 (NEW PASSWORD INVALID) -- the password
disconnected from the server. specified on a change password request did not
meet the server's requirements.
Programmer response • 17 (UNSUPPORTED FUNCTION) -- the security
mechanism specified by the client is invalid for this
Consult with a communications expert to determine server. Some typical examples:
the cause of the communication failure.
– The client is configured to send an Already
Verified userid but the server does not support
SQLSTATE Already Verified userids. Client or server changes
08001 must be made to correct the inconsistency.
-30082 CONNECTION FAILED FOR - Db2 for z/OS server acceptance of Already
SECURITY REASON reason-code Verified userids over TCP/IP connections
(reason-string) is controlled by the TCPALVER value of
the DSNTIP5 installation panel (DSN6FAC
TCPALVER).
Explanation
- Db2 for z/OS client usage of Already Verified
The attempt to connect to a remote database userids is controlled by the SECURITY_OUT
server was rejected due to invalid or incorrect column of the SYSIBM.LUNAMES or
security information. The cause of the security error SYSIBM.IPNAMES table.

– The client is configured to use one of the following connection was not established and so the switch
security mechanisms but the server does not user request is invalid.
support the mechanism:
- Encrypted userid and encrypted security- System action
sensitive data.
The attempt to connect to the remote database server
- Encrypted userid, encrypted password, and fails. If the server system is a Db2 for z/OS server, a
encrypted security-sensitive data. DSNL030I message at the server system describes the
Client changes must be made to correct the cause.
inconsistency.
- Db2 for z/OS server acceptance of Already
Programmer response
Verified userids over TCP/IP connections Db2 uses the communications database (CDB)
is controlled by the TCPALVER value of to control network security functions. Make the
the DSNTIP5 installation panel (DSN6FAC appropriate changes to the CDB to correct the security
TCPALVER). failure.
- Db2 for z/OS client usage of Already Verified
userids is controlled by the SECURITY_OUT SQLSTATE
column of the SYSIBM.LUNAMES or
SYSIBM.IPNAMES table. 08001
– The client is configured to use one of the following -30090 REMOTE OPERATION INVALID
security mechanisms but the server does not FOR APPLICATION EXECUTION
support the mechanism: ENVIRONMENT
- Encrypted userid and encrypted security-
sensitive data. Explanation
- Encrypted userid, encrypted password, and An update operation or a dynamic commit or rollback
encrypted security-sensitive data. was attempted at a server that was supporting
an application that was in a read-only execution
Client changes must be made to correct the
environment (IMS, CICS, or RRSAF.)
inconsistency.
When SQLERRD=-199, the error is related to a
- Db2 for z/OS client usage of encryption security
package bound with DBPROTOCOL(DRDACBF) for one
mechanism is controlled by the SECURITY_OUT
column of the SYSIBM.IPNAMES table.
• The client sent a new password value to a server • The cursor referenced in the failing statement is not
that does not support the DRDA change password open at the remote server.
function. • Running packages bound with and without
• The client sent DCE authentication information to a DBPROTOCOL(DRDACBF) is not allowed to the same
server that does not support DCE. remote server.
• The client is configured to send an Already Verified • The statement is ineligible for continuous block fetch
userid but the server does not support Already processing.
Verified userids. Client or server changes must be
made to correct the inconsistency. System action
– Db2 for z/OS server acceptance of Already Verified The request is rejected.
userids over TCP/IP connections is controlled by
the TCPALVER value of the DSNTIP5 installation
panel (DSN6FAC TCPALVER).
Programmer response
– Db2 for z/OS client usage of Already Do not attempt to update data or issue dynamic
Verified userids is controlled by the commits or rollbacks from IMS, CICS, or RRSAF
SECURITY_OUT column of the SYSIBM.LUNAMES applications that are accessing remote data.
or SYSIBM.IPNAMES tables.
• 26 (SWITCH USER INVALID) - The client is SQLSTATE
configured to request a trusted connection and 25000
switch user in the trusted connection. A trusted

-30104 ERROR IN BIND OPTION option- -30105 BIND OPTION option1 IS NOT
name AND BIND VALUE option- ALLOWED WITH BIND OPTION
value. option2
Bind parameters were passed from the requester site, While processing the bind parameters that were
but could not be processed. passed from the requester site, it was found that there
is a conflict in bind options that are mutually exclusive.
option-name
The name of the bind option.
option-value
Programmer response
The value of the named option. The BIND or REBIND command failed. Examine the
Possible causes for this error include: command options, determine the cause of the conflict,
and resubmit the command.
• Either the bind option or the corresponding value is
not acceptable to the server database.
SQLSTATE
• The specific bind option and value combination is not
supported by the server database. 56096
• The GENERIC option was specified on the BIND -30106 INVALID INPUT DATA DETECTED
PACKAGE or REBIND PACKAGE command, and at FOR A MULTIPLE ROW
least one of the following conditions is true: INSERT OPERATION. INSERT
PROCESSING IS TERMINATED
– The string contains more than 4096 characters.
– The string contains an uneven number of
tokens, resulting in an option name without a
Explanation
corresponding value. An error was detected with the input data for one row
– A bind option name in the string contains more of a multiple row insert operation. No further rows
than 255 characters. will be inserted. For an atomic operation, all inserted
rows are rolled back. For a non-atomic operation, rows
– A bind option value in the string contains more
inserted successfully before the row containing the
than 255 characters.
invalid input data was encountered are not rolled back.

The BIND or REBIND command failed.

Examine the command options and values, determine
Correct the row containing the invalid input data and
the error, and resubmit the command.
submit the multiple-row INSERT statement again for
the rows that did not get inserted.
SQLSTATE
56095 SQLSTATE
Related reference 22527

Part 2. Db2 reason codes
Reason codes are typically presented as a value in a message that Db2 issues. The reason codes provide
specific details about the circumstances of a particular instance of the message.

Chapter 3. X'C1......' codes
Reason code identifiers that begin with 00C1 communicate normal and error situations with the call
attachment facility (CAF).
00C10002 User response
Notify your system programmer.
Explanation
The Db2 call attachment facility control block (the Problem determination
CAB) indicated that a thread was present when it
should not have been present. This is probably a call attachment facility error.
00C10005
Collect a DSNTRACE trace stream and request a Explanation
SYSABEND or SYSUDUMP dump. The application program passed an ECB address of 0
to the call attachment facility on a CONNECT call. The
User response trace message preceding the abend indicates whether
the ECB was a start-up or termination ECB.
Notify your system programmer.
User response
Correct the application program that makes the
This is probably a call attachment facility error. CONNECT call to DSNALI. Ensure that the CONNECT
00C10003 call uses a valid ECB address.
Explanation Problem determination

The Db2 call attachment facility received control See the Explanation above.
after a nonstandard entry that did not use the call 00C10201
attachment facility language interface.
Explanation
User response
The application program passed two CONNECT calls to
Modify or repair your application so that DSNACA00, the call attachment facility (CAF) from the same TCB.
the main call attachment facility code will receive The first CONNECT could have been either implicit or
control only through the language interface. explicit.
Problem determination User response

This is probably a user error. You can continue processing with a corrected request.
00C10004
Explanation See the Explanation above.
The call attachment facility encountered an error 00C10202
retrieving a trace message during processing of a call
attachment facility request.
Explanation
System programmer response The application program passed two OPEN commands
to the call attachment facility (CAF) from the same
Collect a DSNTRACE trace stream and request a TCB. The first OPEN could have been either implicit or
SYSABEND or SYSUDUMP dump. explicit.

User response • The end-of-list bit was off.
You can continue processing with a corrected request.

User response
Problem determination You can continue processing with a corrected request.
See the Explanation above.

00C10203
Explanation 00C10207
A CLOSE command was issued when there was no

active OPEN. Explanation
The application program passed an unrecognized
User response function parameter to the call attachment facility
(CAF).
User response
00C10204 Problem determination
Explanation
00C10208
A DISCONNECT command was issued when there was
no active CONNECT.
Explanation
User response The call attachment facility (CAF) received requests
from the same TCB to CONNECT to the Db2 subsystem
You can continue processing with a corrected request. and to another subsystem.

See the Explanation above. You can continue processing with a corrected request.
00C10205
Explanation See the Explanation above.
A TRANSLATE command was issued when the Db2 00C10209
subsystem was not connected to the call attachment
facility (CAF).
Explanation
User response The call attachment facility (CAF) received an explicit
call to DSNALI from a Db2 stored procedure. This is
You can continue processing with a corrected request. not allowed.

See the Explanation above. You can continue processing with a corrected request.
00C10206 00C10210
One of the following conditions exists: The DSN ASUSER userid is not defined in this trusted
• The wrong number of parameters were issued. context context name.

The DSN ASUSER processing failed. The call attachment facility (CAF) has detected a
release level incompatibility between itself and Db2.
User response Either the current CAF or Db2 release levels do not
support coexistence, or the SPE level of the lower level
Contact the system administrator to arrange for the release does not meet the compatibility requirements
required Trusted Context authorization. for coexistence between the two releases.
00C10211
System action
Explanation The connection is not successful.
The call attachment facility (CAF) failed because
the requester's authorization ID has exceeded the User response
maximum number of concurrent sessions allowed. If you used JCL or a TSO logon procedure to invoke
CAF, check to ensure that the correct Db2 libraries
System action are defined in your JOBLIB and STEPLIB allocations.
See your system programmer if you invoke CAF
The connection request is not processed.
using procedures that are supplied by your system
programmer.
Determine the value of the USER.CSDATA.DSNMUCTL Problem determination
defined for the primary authorization ID in RACF and
If CAF trace (DSNTRACE) is active, message
determine if that value needs to be updated.
DSNA831E will indicate the release levels of CAF and
the Db2 subsystem.
Programmer response
00C12001
Close or end some of the existing connections, and try
the request again.
Explanation
Problem determination The Db2 RRSAF attachment facility function AUTH
SIGNON was invoked by a program that was not
Db2 12 for z/OS in a Common Criteria APF authorized. This condition can indicate a security
environment (DSN6SPRM COMCRIT= YES) restricts violation.
the number of concurrent threads for a primary
authorization ID based upon the custom field
System action
USER.CSDATA.DSNMUCTL.
The application is abended.
00C10824
User response
Explanation
The AUTH SIGNON function can only be invoked
The previous Db2 connection was reset, and cleanup
from an APF authorized program. Either modify your
processing was performed. The call attachment facility
program to use the RRSAF attachment facility function
is ready to process new connection requests.
SIGNON which may be invoked from a non-authorized
program, or contact your security administrator to
User response make the changes required to make your program an
APF authorized program.
Problem determination Problem determination

This is a user error.
See the explanation for message DSNA824I in Call
attachment facility trace messages (Diagnosing Db2 00C12002
problems).
00C10831
Chapter 3. X'C1......' codes 377

Explanation • Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the
An abend has occurred during an attempt to access period of time that spans the failure.
the caller-provided subsystem name parameter while
executing in the PSW key of the caller. This is probably • Listing of SYS1.LOGREC data set, obtained by
the result of a logic error in the requesting program. executing IFCEREP1.
• All dumps taken by the attachment facility or
requesting application.
System action
The application is abended. 00C12004

A dump should be taken for problem analysis. An abend has occurred during an attempt to access
the caller-provided eibptr parameter while executing in
the PSW key of the caller. This is probably the result of
Problem determination a logic error in the requesting program.
This reason code is placed in register 15 during
any access to caller-provided information. When any System action
abend occurs, this register indicates which parameter
caused the error. The application is abended.
Collect the following diagnostic items:

User response
• Console output from the system on which the job
A dump should be taken for problem analysis.
period of time that spans the failure.
• Listing of SYS1.LOGREC data set, obtained by Problem determination
executing IFCEREP1. This reason code is placed in register 15 during
• All dumps taken by the attachment facility or any access to caller-provided information. When any
requesting application. abend occurs, this register indicates which parameter
caused the error.
00C12003
the caller-provided ribptr parameter while executing in
the PSW key of the caller. This is probably the result of • Listing of SYS1.LOGREC data set, obtained by
a logic error in the requesting program. executing IFCEREP1.
System action

A dump should be taken for problem analysis. The Db2 RRSAF attachment facility received control
after a nonstandard entry that did not use the call
attachment facility language interface.
This reason code is placed in register 15 during System action
any access to caller-provided information. When any
abend occurs, this register indicates which parameter The application is abended.
caused the error.

User response User response
Modify or repair your application so that DSNACA00, A dump should be taken for problem analysis.
the main call attachment facility code, will receive
control only through the language interface. Problem determination
This is probably a user error. abend occurs, this register indicates which parameter
caused the error.
00C12006
An abend has occurred during an attempt to access
the caller-provided termination ECB parameter while
System action requesting application.

A dump should be taken for problem analysis. An abend has occurred during an attempt to
access the caller-provided correlation parameter while
executing in the PSW key of the caller. This is probably
Problem determination the result of a logic error in the requesting program.
any access to caller-provided information. When any System action

User response
was run, and a listing of the SYSLOG data set for the A dump should be taken for problem analysis.
executing IFCEREP1. This reason code is placed in register 15 during
caused the error.
00C12007
the caller-provided startup ECB parameter while

the caller-provided accounting token parameter while
System action
.
00C12011
User response
Explanation
Problem determination the caller-provided authid parameter while executing
in the PSW key of the caller. This is probably the result
This reason code is placed in register 15 during of a logic error in the requesting program.
caused the error.
System action
Collect the following diagnostic items: The application is abended.

User response
period of time that spans the failure. A dump should be taken for problem analysis.
• Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1. Problem determination
• All dumps taken by the attachment facility or This reason code is placed in register 15 during
requesting application. any access to caller-provided information. When any
. abend occurs, this register indicates which parameter
caused the error.
00C12010
the caller-provided accounting interval parameter
while executing in the PSW key of the caller. This is • Listing of SYS1.LOGREC data set, obtained by
probably the result of a logic error in the requesting executing IFCEREP1.
program. • All dumps taken by the attachment facility or
System action 00C12012
Explanation
User response An abend has occurred during an attempt to access
A dump should be taken for problem analysis. the caller-provided secondary authid parameter while
the result of a logic error in the requesting program.
caused the error.

A dump should be taken for problem analysis. An abend has occurred during an attempt to access
the caller-provided plan name parameter while
Problem determination executing in the PSW key of the caller. This is probably
System action
User response
executing IFCEREP1.
00C12013 caused the error.
An abend has occurred during an attempt to access was run, and a listing of the SYSLOG data set for the
the caller-provided ACEE parameter while executing in period of time that spans the failure.
the PSW key of the caller. This is probably the result of • Listing of SYS1.LOGREC data set, obtained by
a logic error in the requesting program. executing IFCEREP1.

A dump should be taken for problem analysis. An abend has occurred during an attempt to
access the caller-provided collection parameter while
Problem determination executing in the PSW key of the caller. This is probably
System action
User response
executing IFCEREP1.
00C12014 caused the error.

• Console output from the system on which the job Problem determination
period of time that spans the failure. This reason code is placed in register 15 during
• Listing of SYS1.LOGREC data set, obtained by abend occurs, this register indicates which parameter
executing IFCEREP1. caused the error.
requesting application. 00C12019
00C12016
Explanation
Explanation An abend has occurred during an attempt to
access the caller-provided applname parameter while
An abend has occurred during an attempt to access executing in the PSW key of the caller. This is probably
the caller-provided reuse parameter while executing in the result of a logic error in the requesting program.
a logic error in the requesting program.
System action
System action The application is abended.

User response
User response A dump should be taken for problem analysis.

Problem determination This reason code is placed in register 15 during
This reason code is placed in register 15 during abend occurs, this register indicates which parameter
any access to caller-provided information. When any caused the error.
caused the error. 00C12020

Explanation
the caller-provided ws parameter while executing in
• Listing of SYS1.LOGREC data set, obtained by a logic error in the requesting program.
executing IFCEREP1.
• All dumps taken by the attachment facility or System action
00C12018
User response
Explanation
the caller-provided user-id parameter while executing
in the PSW key of the caller. This is probably the result Problem determination
of a logic error in the requesting program. This reason code is placed in register 15 during
System action abend occurs, this register indicates which parameter
caused the error.
00C12021
User response

An abnormal termination has occurred during an An abend has occurred during an attempt to access
attempt to access the caller-provided xid parameter the caller-provided thread token parameter while
while executing in the PSW key of the caller. This is executing in the PSW key of the caller. This reason
probably the result of a logic error in the requesting code is probably the result of a logic error in the
program. requesting program.

The application is abnormally terminated. The application is abended.

Correct the problem and submit your job again. A dump should be taken for problem analysis.

This reason code is placed in register 15 during any This reason code is placed in register 15 during
access to caller-provided information. Register 15 any access to caller-provided information. When any
indicates which parameter caused the error when any abend occurs, this register indicates which parameter
abnormal termination occurs. caused the error.
00C12022 Collect the following diagnostic items:
Explanation was run, and a listing of the SYSLOG data set for the
the caller-provided package list parameter while • Listing of SYS1.LOGREC data set, obtained by
executing in the PSW key of the caller. This error has executing IFCEREP1.
probably occurred as a result of a logic error in the • All dumps taken by the attachment facility or
requesting program. requesting application.
00C12024
System action
The application is abended. Explanation
While executing in the PSW key of the caller, an abend
User response occurred during an attempt to access the accounting-
A dump should be taken for problem analysis. string parameter that was provided by the caller. This
is probably the result of a logic error in the requesting
program.
caused the error.
Collect the following diagnostic items: User response
• Console output from the system on which the job A dump should be taken for problem analysis.
period of time that spans the failure. Problem determination
• Listing of SYS1.LOGREC data set, obtained by This reason code is placed in register 15 during any
executing IFCEREP1. access to information that was provided by the caller.
• All dumps taken by the attachment facility or When any abend occurs, this register indicates which
requesting application. parameter caused the error.
00C12023 00C12025

While executing in the PSW key of the caller, an abend The application abends.
occurred during an attempt to access the trusted user
parameter that was provided by the caller. This is User response
probably the result of a logic error in the requesting
program. Review the dump to determine the reason for the
problem.
System action
If necessary, add a SYSDUMP or SYSABEND DD
statement to your execution JCL, and run the job
User response
again. Then review the dump to determine the reason
A dump should be taken for problem analysis. for the problem.
00C12028
This reason code is placed in register 15 during any Explanation
access to information that was provided by the caller.
When any abend occurs, this register indicates which While executing in the PSW key of the caller, an abend
parameter caused the error. occurred during an attempt to access the trusted
registry parameter that was provided by the caller.
00C12026 This problem is probably the result of a logic error in
the requesting program.
Explanation
System action
occurred during an attempt to access the trusted The application abends.
password parameter that was provided by the caller.
This problem is probably the result of a logic error in User response
the requesting program.
Review the dump to determine the reason for the
problem.
System action
The application abends. Problem determination
If necessary, add a SYSDUMP or SYSABEND DD
User response
Review the dump to determine the reason for the again. Then review the dump to determine the reason
problem. for the problem.
00C12029
If necessary, add a SYSDUMP or SYSABEND DD Explanation
again. Then review the dump to determine the reason While executing in the PSW key of the caller, an abend
for the problem. occurred during an attempt to access the trusted
original authorization ID parameter that was provided
00C12027 by the caller. This problem is probably the result of a
logic error in the requesting program.
Explanation
System action
occurred during an attempt to access the trusted The application abends.
location name parameter that was provided by the
caller. This problem is probably the result of a logic
error in the requesting program.

User response Problem determination
Review the dump to determine the reason for the This reason code is placed in register 15 during any
problem. access to caller-provided information. Register 15
indicates which parameter caused the error when any
Problem determination abnormal termination occurs. information.
If necessary, add a SYSDUMP or SYSABEND DD 00C12032

again. Then review the dump to determine the reason Explanation
for the problem.
An abnormal termination occurred during an attempt
00C12030 to access the caller-provided activea parameter while
Explanation the result of a logic error in the requesting program.

System action
occurred during an attempt to access the trusted
security token parameter that was provided by the The application is abnormally terminated.
caller. This problem is probably the result of a logic
error in the requesting program. User response
Correct the problem and resubmit your job.
System action
The application abends. Problem determination
This reason code is placed in register 15 during any
User response
access to caller-provided information. Register 15
Review the dump to determine the reason for the indicates which parameter caused the error when any
problem. abnormal termination occurs.
00C12033
If necessary, add a SYSDUMP or SYSABEND DD Explanation
An abnormal termination has occurred during
again. Then review the dump to determine the reason
an attempt to access the caller-provided arraysz
for the problem.
parameter while executing in the PSW key of the
00C12031 caller. This is probably the result of a logic error in the
requesting program.
Explanation
System action
An abnormal termination has occurred during
an attempt to access the caller-provided ssnma The application is abnormally terminated.
caller. This is probably the result of a logic error in the User response
requesting program.
Correct the problem and resubmit your job.
System action
The application is abnormally terminated.
User response
indicates which parameter caused the error when any
Correct the problem and submit your job again. abnormal termination occurs.
00C12034

An abnormal termination has occurred during an The application program invoked IDENTIFY while it
attempt to access the caller-provided decpptr was already connected to Db2.
caller. This is probably the result of a logic error in the User response
requesting program.
System action Problem determination:
The application is abnormally terminated. 00C12202

Correct the problem and resubmit your job. The application program invoked the CREATE THREAD
function request while there was already a thread
Problem determination created.

User response
indicates which parameter caused the error when any You can continue processing with a corrected request.
abnormal termination occurs.
Problem determination:
00C12035
00C12203
The Db2 RRSAF attachment facility function
A TERMINATE THREAD command was issued when
SET_REPLICATION was invoked by a program that
there was no active thread.
was not APF authorized. This condition can indicate
a security violation.
User response
System action You can continue processing with a corrected request.
The application is abended. Problem determination:
00C12204
User response
The SET_REPLICATION function can only be invoked Explanation
from an APF authorized or supervisor state program.
The application issued a function request other than
Either modify your program to use the RRSAF
IDENTIFY when no connection with Db2 existed. Only
attachment facility function SIGNON which may be
IDENTIFY may be issued when a connection does not
invoked from a non-authorized program, or contact
exist.
your security administrator to make the changes
required to make your program an APF authorized
program or to have your program run in supervisor User response
state. You can continue processing with a corrected request.
Related reference Problem determination:
SET_REPLICATION function for RRSAF (Db2
Application programming and SQL) 00C12205
SIGNON function for RRSAF (Db2 Application
programming and SQL) Explanation
The task that invoked the Db2 RRSAF attachment
00C12201
facility function SWITCH TO has not yet identified to
the Db2 subsystem specified in the request.

The SWITCH TO function is performed. The application program issued an IDENTIFY function
request but omitted the eibptr parameter from the
User response parameter list. An eibptr parameter is a required
parameter on an IDENTIFY request.
Use IDENTIFY to connect to a Db2 subsystem
before attempting to invoke any other function at the
System action
specified subsystem.
The IDENTIFY request is rejected.
00C12206 User response
Explanation
00C12211
• The wrong number of parameters were issued.
• The end-of-list bit was off.
Explanation
User response The application program issued a CREATE THREAD
function request and specified an invalid package list
You can continue processing with a corrected request. entry.
00C12207
User response
The application program either omitted the function
name parameter or passed an unrecognized function Explanation
parameter to the RRSAF.
The application program issued a CREATE THREAD
function request and did not specify a plan name
User response and also did not specify a collection name. If a plan
Modify or repair your application to pass a valid name is not provided, then a collection name must be
function request to RRSAF. supplied.
00C12208
User response
Explanation You can continue processing with a corrected request.
The application program issued an IDENTIFY function Problem determination:

request but omitted the ribptr parameter from the 00C12214
parameter list. An ribptr parameter is a required
parameter on an IDENTIFY request.
Explanation
System action The application program issued a TRANSLATE function
request but omitted the sqlca parameter from the
The IDENTIFY request is rejected. parameter list. An sqlca parameter is a required
parameter on a TRANSLATE request.
User response
You can continue processing with a corrected request. User response
Problem determination: You can continue processing with a corrected request.
00C12209 Problem determination:

00C12217

The application program issued a CREATE THREAD The application program issued a CALL DSNRLI
function request without having completed SIGNON statement with the SET_TRUSTED function, but did not
processing. At least one successful SIGNON must be complete processing of the CREATE THREAD function.
completed before a CREATE THREAD request can be SET_TRUSTED requests cannot be issued until CREATE
issued. THREAD processing is complete.

You can continue processing with a corrected request. The SET_TRUSTED request is not processed.
User response
00C12219
Correct the request.
The application program issued an SQL or IFI
function request without completing CREATE THREAD Explanation
processing. SQL or IFI requests cannot be issued until
The application program issued a CALL DSNRLI
CREATE THREAD processing is complete.
statement with the SWITCH_USER function, but did
not complete processing of the CREATE THREAD
User response function. SWITCH_USER requests are permitted only
after a plan is allocated.
System action
00C12220
The SET_TRUSTED request is not processed.
Explanation
User response
The application program issued a CALL DSNRLI with
Correct the request.
function SET_ID without completing CREATE THREAD
processing. SET_ID requests cannot be issued until 00C12230
CREATE THREAD processing is complete.
Explanation
User response
The Db2 RRSAF attachment facility function
You can continue processing with a corrected request. FIND_DB2_SYSTEMS was invoked with a ssnma and
activea array size that is not large enough to contain
00C12221
the information on all the defined Db2 systems on this
LPAR.
Explanation
The application program issued a CALL DSNRLI System action
with function SET_CLIENT_ID without completing
The request for information failed with Return Code 4.
CREATE THREAD processing. SET_CLIENT_ID requests
cannot be issued until CREATE THREAD processing is
complete. SET_CLIENT_ID request are permitted only User response
after a plan is allocated.
Increase the size of the storage allocated for the
ssnma and activea arrays, and change the arraysz
User response parameter to indicate the new size.
You can continue processing with a corrected request. 00C12231
00C12222

The Db2 RRSAF attachment facility failed because The previous connection to Db2 has been terminated.
the requester's authorization ID has exceeded the Cleanup processing was performed and the RRSAF is
maximum number of concurrent sessions allowed. now ready to process additional IDENTIFY requests.

The connection request is not processed. You can continue processing, and issue an IDENTIFY
request.
System programmer response Problem determination:
Determine the value of the USER.CSDATA.DSNMUCTL 00C12825
defined for the primary authorization ID in RACF and
determine if that value needs to be updated.
Explanation
Programmer response An attempt was made to terminate a stored procedure
for a task, but no stored procedure exists. This is not
Close or end some of the existing connections, and try allowed.
the request again.
User response
Db2 12 for z/OS in a Common Criteria
environment (DSN6SPRM COMCRIT= YES) restricts
the number of concurrent threads for a primary 00C12831
authorization ID based upon the custom field
USER.CSDATA.DSNMUCTL.
Explanation
00C12822 The release of the RRSAF code is not compatible with
the earlier release of the Db2 program.
Explanation
The RRSAF received an explicit call to DSNRLI from a System action
Db2 stored procedure. This is not allowed. The connection is not made.

You can continue processing with a corrected request. Ensure that the release of the RRSAF library is not
Problem determination: later than the release of Db2 to which you are
attempting to connect.
00C12823
Explanation
This problem can be caused by improper Db2 data set
An attempt was made to initiate a stored procedure for allocation in a LOGON procedure or CLIST.
a task, but one already exists. This is not allowed.
00C12832
User response
Explanation
The RRSAF SIGNON processing is performed in a
trusted context. The USER authorization ID is not
00C12824 defined in this trusted context context name.
System action
The RRSAF SIGNON request is not processed.

Contact the system administrator to add the user to The stored procedure requests an SVC dump and
the trusted context. terminates.
00C12850
Explanation If the dump was requested to diagnose a problem in
user exit DSNACICX, use IPCS to examine the contents
Db2 stored procedure DSNACICS issues this abend
of the dump. If the dump was requested because of a
code when the JCL startup procedure for the stored
possible error in the Db2 stored procedure, you might
procedure address space in which DSNACICS runs need to report the problem. For information about
contains a DSNDUMP DD statement. DSNACICS takes identifying and reporting the problem, see Collecting
an SVC dump when it generates an error message. At diagnostic data (Collecting data).
the time of the dump:
Related reference
• Register 2 contains the address of the message that
DSNACICS stored procedure (Db2 SQL)
was being generated.
The DSNACICX user exit routine (Db2
• Register 3 contains the address of the first Administration Guide)
parameter that was passed to DSNACICS.
• Register 4 contains the address of the XPL
parameter area that was passed to DSNACICX.

Reason code identifiers that begin with 00C2 communicate normal and error situations with the buffer
manager.
00C20021 reason code indicating that the object cannot be
automatically recovered.
Explanation Otherwise, a 'resource not available' return code,
reason code and object name are sent back to the
A member of a Db2 data sharing group was unable to
requesting function. DSNT501I is sent to the console
perform a global drain because a physical close failure
to report the condition.
occurred in a peer Db2 due to an exceptional state
or CASTOUT process failure. DSNT501I is sent to the
console to report the condition. System programmer response
If DSNB350I or DSNB351I messages were issued,
System action wait for the failed Db2 member to complete its restart
processing and then recover the GRECP objects as
A 'resource not available' return code, reason code,
indicated in the "System Programmer Response" for
and object name are sent back to the requesting
DSNB350I or DSNB351I.
function.
00C2006A
00C20031
Explanation
Explanation
Db2 was unable to perform the drain function on an
An attempt to acquire a page latch in either shared
object (table space, index space, or partition) because
mode or exclusive mode was rejected due to a timeout
the object was held by one or more indoubt threads.
on the agent's wait time.
System action
System action
If the problem was encountered by Db2 when trying
A 'resource not available' return code, reason code,
to automatically recover a group buffer pool recovery
pending (GRECP) object following the failure of a
function.
group buffer pool (GBP), then Db2 issues message
DSNB350I or DSNB351I to the console with this
System programmer response reason code indicating that the object cannot be
automatically recovered.
A diagnostic dump with reason code 00C2010F should
follow 00C20031.
00C20069
Use the Db2 DISPLAY DB CLAIMERS command to find
the indoubt threads. If the threads have been left
Explanation indoubt because Db2 or a transaction manager was
Db2 is unable to perform the drain function on an unable to automatically resolve the indoubts, you can
object (a table space, an index space, or a partition) use the Db2 RECOVER INDOUBT command to resolve
because a Db2 member in the data sharing group was the indoubt thread and remove the indoubt claimer
in the process of restarting. on the object (the Db2 RECOVER INDOUBT command
should only be used when automatic resolution does
not work).
System action
If DSNB350I or DSNB351I messages were issued,
then after you resolve the indoubt threads, recover
the GRECP objects as indicated in the "System
pending (GRECP) object following the failure of a
Programmer Response" for DSNB350I or DSNB351I.
group buffer pool (GBP), then Db2 issues message
DSNB350I or DSNB351I to the console with this 00C200A1

This is a Db2 internal error. The caller of the buffer Collect the following diagnostic items:
manager (BM) is trying to release a page latch that is
not currently held.
System action • Dynamic dump, taken to SYS1.DUMPxx data set, by
The requesting application process is abended. Db2 (04E and 04F abends).
Operator response executing IFCEREP1.
Notify the system programmer, print the 00C200A3

SYS1.LOGREC, and request the SVC dump.
Explanation
System programmer response This is a Db2/MVS internal error. The execution unit
If you suspect an error in Db2, you might need to driving a buffer manager (BM) asynchronous function,
report the problem. For information about identifying which would normally run indefinitely, has been
and reporting the problem, see Collecting diagnostic canceled. However, work being done by the execution
data (Collecting data). unit is allowed to complete before the execution unit
terminates.
System action
The affected asynchronous function is terminated. If
• Console output from the system on which the job the affected function is the deferred write processor
was run, and a listing of the SYSLOG data set for the (DSNB1CMS), Db2 is abended with the abend code
period of time that spans the failure. '00C200D3'.
• Dynamic dump, taken to SYS1.DUMPxx data set, by
Db2 (04E and 04F abends). Operator response
executing IFCEREP1. Notify the system programmer, print the
SYS1.LOGREC, and request the SVC dump. Start Db2
00C200A2 if it is abended.

This is a Db2 internal error. The caller of the buffer If you suspect an error in Db2, you might need to
manager (BM) is trying to get a page latch that is report the problem. For information about identifying
currently held on the requesting page. and reporting the problem, see Collecting diagnostic
System action
The requesting application process is abended.
Operator response • Console output from the system on which the job
Notify the system programmer, print the was run, and a listing of the SYSLOG data set for the
SYS1.LOGREC, and request the SVC dump. period of time that spans the failure.
Db2 (04E and 04F abends).
If you suspect an error in Db2, you might need to executing IFCEREP1.
report the problem. For information about identifying
and reporting the problem, see Collecting diagnostic 00C200A4

Explanation preparation for page set cleanup processing. This
might be caused by one of the following events:
This code usually indicates a problem internal to Db2;
however, the problem can result from errors in other • An IRLM out-of-storage condition
products. An unexpected reason code was returned by • An internal error in the lock acquisition function
the media manager function when it was invoked to
process a database I/O request.
System action
System action The execution unit driving this function proceeds
normally. The abend status is recorded in
The requesting execution unit is abended. SYS1.LOGREC.
Operator response Operator response

Notify the system programmer, print the Notify the system programmer and print the
SYS1.LOGREC, and request the SVC dump. SYS1.LOGREC.
User response System programmer response

Notify the system programmer and rerun the If you suspect an error in Db2, you might need to
application. report the problem. For information about identifying
Problem determination data (Collecting data). Restart Db2.

and reporting the problem, see Collecting diagnostic The unexpected reason code returned by the drain
data (Collecting data). functionin register 8 might help determine the cause
The unexpected media manager reason code is saved of the problem. If the problem is caused by an
in register 8. unavailable Db2 resource, message DSNT500I might
also be issued.
Check the MVS console log for an IOS (I/O subsystem)
error message indicating the type of I/O error that Collect the following diagnostic items:
occurred. If an IOS message was issued, follow the • Console output from the system on which the job
problem determination directions for that message. was run, and a listing of the SYSLOG data set for the
Collect the following diagnostic items: period of time that spans the failure.
executing IFCEREP1.
period of time that spans the failure. 00C200A6
Db2 (04E and 04F abends). Explanation
• Listing of SYS1.LOGREC data set, obtained by This is a Db2/MVS internal error. The execution unit
executing IFCEREP1. scheduled by the buffer manager (BM) subcomponent
• IDCAMS LISTCAT output for the ICF (VSAM) catalog of Db2 to drive the page set cleanup function has been
that contains the Db2 subsystem catalog that canceled.
defined the failing index or table.
• VTOC listing of the disk volume on which the failing System action
operation occurred.
Db2 is abended.
00C200A5
Operator response
Explanation
Notify the system programmer, print the
Typically, this indicates a problem internal to Db2; SYS1.LOGREC, and request the SVC dump. Restart
however, the problem can result from errors in other Db2.
products. Db2 was unable to drain a pageset in

System programmer response 00C200A9
report the problem. For information about identifying Explanation
and reporting the problem, see Collecting diagnostic A return code greater than 4 was returned by the IRLM
data (Collecting data). UNLOCK request invoked by Db2 to release any of the
following locks:
Problem determination • SYSLGRNG or SYSLGRNX recording lock on a table
Refer to similar reason code '00E50013'. space
Collect the following diagnostic items: • Group buffer pool dependent conversion lock on a
page set or partition
• Group buffer pool start or stop lock
period of time that spans the failure. • ALTER BUFFERPOOL lock.
• Dynamic dump, taken to SYS1.DUMPxx data set, by This is a Db2 or IRLM error.
• Listing of SYS1.LOGREC data set, obtained by System action
executing IFCEREP1.
The requesting execution unit is abended.
00C200A8
Operator response
Explanation
An error code other than timeout, insufficient storage, SYS1.LOGREC, and request the SVC dump.
or an MVS system error was returned by the IRLM
LOCK request invoked by Db2 to acquire any of the
User response
following locks:
Notify the system programmer and rerun the
• SYSLGRNG or SYSLGRNXrecording lock on a table
application.
space
• Group buffer pool-dependent conversion lock on a
page set or partition Problem determination
• Group buffer pool start or stop lock If you suspect an error in Db2, you might need to
• ALTER BUFFERPOOL lock
This is a Db2 or IRLM internal error. data (Collecting data).
The unexpected IRLM reason code is saved in register
System action 8. It might help determine the cause of the error.
The requesting execution unit abends. Collect the following diagnostic items:
Operator response was run, and a listing of the SYSLOG data set for the
Notify the system programmer, print the period of time that spans the failure.
SYS1.LOGREC, and request the SVC dump. • Dynamic dump, taken to SYS1.DUMPxx data set, by
User response • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Notify the system programmer and rerun the
application. 00C200AA
Problem determination Explanation

If you suspect an error in Db2, you might need to This is a Db2 internal error. The caller of the buffer
report the problem. For information about identifying manager (BM) is trying to change a page latch type, but
and reporting the problem, see Collecting diagnostic the requesting agent already holds this latch type on
data (Collecting data). this page.

System action • Console output from the system on which the job
The requesting application process is abended. period of time that spans the failure.
Operator response Db2 (04E and 04F abends).
Notify the system programmer, print the • Listing of SYS1.LOGREC data set, obtained by
SYS1.LOGREC, and request the SVC dump. executing IFCEREP1.
00C200AD
If you suspect an error in Db2, you might need to Explanation
and reporting the problem, see Collecting diagnostic This is a Db2 internal error. The caller of the buffer
data (Collecting data). manager (BM) is trying to get a page latch for a page
that belongs to one type of page set (index or data).
However, the caller already holds a page latch on
Problem determination another page that belongs to a different type of page
Collect the following diagnostic items: set.

System action
period of time that spans the failure. The requesting application process is abended.
• Listing of SYS1.LOGREC data set, obtained by Notify the system programmer, print the
executing IFCEREP1. SYS1.LOGREC, and request the SVC dump.
00C200AB
Explanation If you suspect an error in Db2, you might need to
This is a Db2 internal error. The caller of the buffer report the problem. For information about identifying
manager (BM) is trying to get another page latch, and reporting the problem, see Collecting diagnostic
which would cause the total number of page latches data (Collecting data).
held by the caller to exceed the maximum allowable
number of 2. Problem determination
System action
The requesting application process is abended. was run, and a listing of the SYSLOG data set for the
Operator response • Dynamic dump, taken to SYS1.DUMPxx data set, by
Notify the system programmer, print the Db2 (04E and 04F abends).
SYS1.LOGREC, and request the SVC dump. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
System programmer response .
If you suspect an error in Db2, you might need to 00C200AE
Explanation
This is a Db2 internal error. The caller of the buffer
Problem determination manager (BM) is trying to get a page latch on a page for
which there are latch waiters, but no latch holders.

The requesting application process is abended. period of time that spans the failure.
Notify the system programmer, print the • Listing of SYS1.LOGREC data set, obtained by
SYS1.LOGREC, and request the SVC dump. executing IFCEREP1.
00C200B0
and reporting the problem, see Collecting diagnostic Typically, this indicates a problem internal to Db2,
data (Collecting data). however the problem can result from errors in other
products. The buffer address passed by the buffer
manager (BM) invokers does not contain the requested
Problem determination page. The buffer manager detected this error by
Collect the following diagnostic items: comparing the information stored in the buffer control
block (BB) with the information passed with the
• Console output from the system on which the job buffer manager by its invokers. The information that
was run, and a listing of the SYSLOG data set for the is compared is the page set piece block, the page
period of time that spans the failure. number, and the buffer address.
Db2 (04E and 04F abends). System action
executing IFCEREP1.
00C200AF Operator response
Explanation SYS1.LOGREC, and request the SVC dump.
manager(BM) is attempting to update a page under the System programmer response
critical mode without holding an exclusive latch on the
page. If you suspect an error in Db2, you might need to
System action data (Collecting data).
Operator response
The following general purpose registers (GPRs) contain
Notify the system programmer, print the the indicated diagnostic information:
GPR
Content
7
If you suspect an error in Db2, you might need to Address of the page buffer
8
Address of the page set block (PB)
Problem determination • Console output from the system on which the job

• Listing of SYS1.LOGREC data set, obtained by Operator response
executing IFCEREP1.
• IDCAMS LISTCAT output for the ICF (VSAM) catalog SYS1.LOGREC, and request the SVC dump.
that contains the Db2 subsystem catalog that
• VTOC listing of the disk volume on which the failing
operation occurred. If you suspect an error in Db2, you might need to
00C200B1 and reporting the problem, see Collecting diagnostic
Explanation
This is a Db2 internal error. Either the buffer manager Problem determination
(BM) subcomponent of Db2 is unable to locate the Collect the following diagnostic items:
requesting page in the buffer pool or the invoker of the
buffer manager is attempting to decrease the buffer • Console output from the system on which the job
use count which is already 0. was run, and a listing of the SYSLOG data set for the
executing IFCEREP1.
Operator response
00C200B3
Explanation
System programmer response This is a Db2 internal error. The buffer manager (BM)
subcomponent of Db2 is unable to open a page set
If you suspect an error in Db2, you might need to required by the requesting function. The page size or
report the problem. For information about identifying the page set piece size passed by the buffer manager
and reporting the problem, see Collecting diagnostic invoker is invalid. The page set piece size is expressed
data (Collecting data). by n, where 2 to the power of n is the total number
of pages that can be contained within a page set
Problem determination piece. This error was detected during open page set
processing.
• Console output from the system on which the job System action
period of time that spans the failure. The requesting execution unit is abended.
00C200B2
This is a Db2 internal error. The buffer's write intent
count is already 0 and the buffer manager (BM) invoker
is attempting to decrease it.
System action

• Console output from the system on which the job the buffer manager invoker were in conflict with the
was run, and a listing of the SYSLOG data set for the same page set that was opened earlier. The page set
period of time that spans the failure. options are the writing protocol (SYSTEM or UW), the
• Dynamic dump, taken to SYS1.DUMPxx data set, by recovery option (recoverable or unrecoverable), and
Db2 (04E and 04F abends). the page size.
executing IFCEREP1. System action
00C200B4 The requesting execution unit is abended.
Explanation Operator response

This is a Db2 internal error. The buffer manager Notify the system programmer, print the
(BM) subcomponent of Db2 is unable to open a page SYS1.LOGREC, and request the SVC dump.
set required by the requesting function. The highest
page set piece number passed by the buffer manager System programmer response
invoker exceeds the maximum value allowed. The
maximum number of data sets that can be defined for If you suspect an error in Db2, you might need to
a given page set is dependent on the page set piece report the problem. For information about identifying
size. This error was detected during open page set and reporting the problem, see Collecting diagnostic
processing. data (Collecting data).
System action Problem determination

The requesting execution unit is abended. Collect the following diagnostic items:
System programmer response executing IFCEREP1.
00C200B6
data (Collecting data). Explanation
Typically, this indicates a problem internal to Db2;
Problem determination however, the problem can result from errors in other
products. The buffer manager (BM) subcomponent of
Db2 is unable to reallocate a data set that is required
• Console output from the system on which the job after extending a data set to a new volume. The data
was run, and a listing of the SYSLOG data set for the set reallocation was requested and the corresponding
period of time that spans the failure. data set was not opened. This error was detected
• Dynamic dump, taken to SYS1.DUMPxx data set, by during open page set piece processing.
executing IFCEREP1. The requesting execution unit is abended.
00C200B5
Operator response
Explanation Notify the system programmer, print the
This is a Db2 internal error. The buffer manager (BM) SYS1.LOGREC, and request the SVC dump.
subcomponent of Db2 is unable to open a page set
required by the requesting function. During the open
page set processing, the page set options passed by

System programmer response • Console output from the system on which the job
If you suspect an error in Db2, you might need to period of time that spans the failure.
and reporting the problem, see Collecting diagnostic • Dynamic dump, taken to SYS1.DUMPxx data set, by
data (Collecting data). Db2 (04E and 04F abends).
executing IFCEREP1.
• IDCAMS LISTCAT output for the ICF (VSAM) catalog
Collect the following diagnostic items: that contains the Db2 subsystem catalog that
• Console output from the system on which the job defined the failing index or table.
was run, and a listing of the SYSLOG data set for the • VTOC listing of the disk volume on which the failing
period of time that spans the failure. operation occurred.
00C200B8
Explanation
executing IFCEREP1.
• IDCAMS LISTCAT output for the ICF (VSAM) catalog This is a Db2 internal error. Db2 is unable to update
that contains the Db2 subsystem catalog that the SYSLGRNG or SYSLGRNXpage set. The utility
defined the failing index or table. returned an unexpected reason code.
operation occurred. System action
00C200B7 A 'resource not available' code is returned. This reason
code and the table space name are recorded in the
cursor table (CT) and made available to the user in the
Explanation SQLCA or in messages.
Typically, this indicates a problem internal to Db2;
however, the problem can result from errors in other System programmer response
products. The buffer manager (BM) subcomponent
of Db2 is unable to open a page set required by If you suspect an error in Db2, you might need to
the requesting function. The linear page set was not report the problem. For information about identifying
formatted contiguously. This error was detected during and reporting the problem, see Collecting diagnostic
open page set processing. data (Collecting data).

The requesting execution unit is abended. Collect the following diagnostic items:
SYS1.LOGREC, and request the SVC dump. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
System programmer response 00C200BA

and reporting the problem, see Collecting diagnostic This reason code is a Db2 internal error. Db2 has
data (Collecting data). encountered an unexpected error while attempting to
access a system page of a page set.
Collect the following diagnostic items: System action
The requesting execution unit is abended. The SVC
dump and the SYS1.LOGREC recording are requested.

Operator response .
Notify the system programmer, print the SYS1.LOGREC 00C200BC

and the SVC dump.
Explanation
System programmer response This is a Db2 internal error. The Buffer Manager (BM)
If you suspect an error in Db2, you might need to subcomponent of Db2 has discovered that the BM
report the problem. For information about identifying invoker is attempting to release the page which does
and reporting the problem, see Collecting diagnostic not belong to the work file database.
System action
Problem determination The requesting execution unit is abnormally
Collect the following diagnostic items: terminated.
was run, and a listing of the SYSLOG data set for the Operator response
period of time that spans the failure. Notify the system programmer, and print the
• Dynamic dump, taken to SYS1.DUMPxx data set, by SYS1.LOGREC and the SVC dump.
• Listing of SYS1.LOGREC data set, obtained by System programmer response
executing IFCEREP1.
00C200BB report the problem. For information about identifying
Explanation data (Collecting data).
This is a Db2 internal error to indicate that an invalid

buffer pool ID is specified.
Operator response
executing IFCEREP1.
00C200BD
System programmer response Explanation

manager (BM) is still holding a page latch on the page
which is currently being released by the application.
System action
Problem determination The requesting application process is abended.
Operator response
was run, and a listing of the SYSLOG data set for the Notify the system programmer, print the
period of time that spans the failure. SYS1.LOGREC, and request the SVC dump.
Db2 (04E and 04F abends). System programmer response
• Listing of SYS1.LOGREC data set, obtained by If you suspect an error in Db2, you might need to
executing IFCEREP1. report the problem. For information about identifying

and reporting the problem, see Collecting diagnostic permanent I/O error) was returned by the media
data (Collecting data). manager during the I/O backend processing.
Problem determination System action

Collect the following diagnostic items: The requesting execution unit is abended.
was run, and a listing of the SYSLOG data set for the Operator response
• Dynamic dump, taken to SYS1.DUMPxx data set, by SYS1.LOGREC, and request the SVC dump.
executing IFCEREP1.
00C200BE report the problem. For information about identifying
This is a Db2 internal error. The buffer manager (BM)

is trying to dequeue a page latch waiter from the wait Problem determination
queue, but there are no waiters. The unexpected media manager reason code is saved
in register 8. It might help determine the cause of the
System action failure.
The requesting application process is abended. Check the MVS console log for an IOS (I/O subsystem)
error message indicating the type of I/O error that
occurred. If an IOS message was issued, follow the
Operator response problem determination directions for that message.
Notify the system programmer, print the Collect the following diagnostic items:
System programmer response period of time that spans the failure.
If you suspect an error in Db2, you might need to • Dynamic dump, taken to SYS1.DUMPxx data set, by
report the problem. For information about identifying Db2 (04E and 04F abends).
executing IFCEREP1.
Problem determination that contains the Db2 subsystem catalog that
Collect the following diagnostic items: defined the failing index or table.
• Console output from the system on which the job • VTOC listing of the disk volume on which the failing
was run, and a listing of the SYSLOG data set for the operation occurred.
period of time that spans the failure. 00C200C1
The page version number in the database page header
executing IFCEREP1.
is outside the valid range of values. This can be caused
. by one of the following errors:
00C200C0 • Copying data sets improperly from another Db2
subsystem.
Explanation • In a CREATE TABLESPACE statement, specifying a
VCAT catalog name that is the same as the name
Db2 is unable to perform I/O processing for the of an object in another Db2 subsystem on the same
requesting function. An error code (other than a processor.

• Conditionally starting Db2 to a prior time with an 7
invalid RBA range. Address of the page buffer
• Incorrect use of the REPAIR utility (modifying the 8
page RBA). Address of the page set block (PB)
• The page was damaged by a Db2 system error. Collect the following diagnostic items:
• TOD clock values are out of synch between systems • Console output from the system on which the job
in a Parallel Sysplex®. was run, and a listing of the SYSLOG data set for the
The requesting execution unit is abended. If Db2 (04E and 04F abends).
DSNB1SWS issues the ABEND, then it is preceded by • Listing of SYS1.LOGREC data set, obtained by
a DSNT500I message indicating which page is in error executing IFCEREP1.
and a DSNI004I message indicating the page set is put • Dump of the index or table space that failed.
in STOPE mode.
• Db2 log output, including any Db2 recovery log
archive tapes.
Operator response
00C200C2
Explanation
User response This is a Db2 internal error. The buffer manager (BM)
subcomponent of Db2 has discovered that the BM
One of the following actions: invoker is attempting to decrease the page's write
• If the data set was copied from another Db2 intent count (WIC), but the invoker has no write intent
subsystem, run DSN1COPY with the RESET option request outstanding.
to set the log RBAs in each page to 0.
• If a table space was created with the wrong VCAT System action
catalog name, drop the object and create it again.
The BM does not decrease the page's WIC as
• If Db2 was conditionally started with an invalid RBA requested, and the execution unit driving this function
range, correct the RBA range and restart Db2 with is abended. An SVC dump is requested and the abend
conditions again. status is recorded in the SYS1.LOGREC.
• If the page was damaged by the REPAIR utility,
restore it with the RECOVER utility using the PAGE Operator response
option.
• If you are running data sharing, check the
connectivity of the systems to the sysplex timers.
The TOD clock values of all systems in the sysplex
should all be within one microsecond. TOD clock System programmer response
values will not drift more than one microsecond If you suspect an error in Db2, you might need to
apart unless a sysplex timer is malfunctioning. report the problem. For information about identifying
• Otherwise, inform your system programmer that you and reporting the problem, see Collecting diagnostic
suspect an error. data (Collecting data).

If you suspect an error in Db2, you might need to Collect the following diagnostic items:
The following general purpose registers (GPRs) contain • Dynamic dump, taken to SYS1.DUMPxx data set, by
the indicated diagnostic information: Db2 (04E and 04F abends).
GPR
Content

• Listing of SYS1.LOGREC data set, obtained by was attempting to decrease the write dependency
executing IFCEREP1. count (WDC) for a buffer. However, the buffer contains
• Dump of the index or table space that failed. database updates that have not yet been written
back to DASD. The buffer manager makes the buffer
• Output of the GTF trace (if requested by IBM). available for reassignment.
archive tapes. System action
00C200C3 The buffer manager does not decrease the WDC as
requested, and the execution unit driving this function
Explanation proceeds normally. An SVC dump is requested and the
abend status is recorded in SYS1.LOGREC.
This is a Db2 internal error. The buffer manager (BM)
subcomponent of Db2 discovered that the BM invoker
is attempting to set the page's write intent count Operator response
(WIC), but the invoker has no read intent request Notify the system programmer, print the
outstanding. SYS1.LOGREC, and request the SVC dump.
System action System programmer response

The BM does not increase the page's WIC as If you suspect an error in Db2, you might need to
requested, and the execution unit driving this function report the problem. For information about identifying
is abended. An SVC dump is requested and the abend and reporting the problem, see Collecting diagnostic
status is recorded in the SYS1.LOGREC. data (Collecting data).
Operator response Problem determination

Notify the system programmer, print the Collect the following diagnostic items:
executing IFCEREP1.
• Dump of the index or table space that failed.
• Output of the GTF trace (if requested by IBM).
• Console output from the system on which the job archive tapes.
period of time that spans the failure. 00C200C6
• Listing of SYS1.LOGREC data set, obtained by This is a Db2 internal error. The buffer manager (BM)
executing IFCEREP1. subcomponent of Db2 has discovered that the BM
• Output of the GTF trace (if requested by IBM). invoker is attempting to release a page that was not
held by the invoker or the page has an unbalanced
• Db2 log output, including any Db2 recovery log write intent (for example, reset write intent has not yet
archive tapes. been issued prior to releasing the page).
00C200C5
System action
Explanation The BM does not release the page as requested, and
This is a Db2 internal error. The buffer manager (BM) the execution unit driving this function terminates
subcomponent of Db2 discovered that its invoker

abnormally. An SVC dump is requested and the abend User response
status is recorded in the SYS1.LOGREC.
Rerun the application.
Operator response
SYS1.LOGREC, and request the SVC dump. The unexpected IRLM reason code is saved in register
8. It may help determine the cause of the error.
System programmer response Collect the following diagnostic items:
If you suspect an error in Db2, you might need to • Console output from the system on which the job
report the problem. For information about identifying was run, and a listing of the SYSLOG data set for the
and reporting the problem, see Collecting diagnostic period of time that spans the failure.
data (Collecting data). • Dynamic dump, taken to SYS1.DUMPxx data set, by
Problem determination • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
00C200C8
period of time that spans the failure. Explanation
• Dynamic dump, taken to SYS1.DUMPxx data set, by A return code greater than 4 was returned by the IRLM
Db2 (04E and 04F abends). UNLOCK request invoked to release a open lock after
• Listing of SYS1.LOGREC data set, obtained by completing a physical open or close.
executing IFCEREP1.
• Dump of the index or table space that failed. System action
• Output of the GTF trace (if requested by IBM). The requesting execution unit is abended.
archive tapes. Operator response
00C200C7 Print the SYS1.LOGREC and request the SVC dump.

An error code, other than timeout, insufficient storage, If you suspect an error in Db2, you might need to
or MVS system error, was returned by the IRLM LOCK report the problem. For information about identifying
request. The IRLM LOCK request was invoked to and reporting the problem, see Collecting diagnostic
acquire an open lock to perform a physical open or data (Collecting data).
close.
User response
System action
Operator response
The unexpected IRLM reason code is saved in register
Print the SYS1.LOGREC and request the SVC dump. 8. It may help determine the cause of the error.
If you suspect an error in Db2, you might need to was run, and a listing of the SYSLOG data set for the
report the problem. For information about identifying period of time that spans the failure.

executing IFCEREP1.
00C200C9 SYS1.LOGREC, and request the SVC dump. Restart
Db2.
Explanation
The buffer manager (BM) subcomponent of Db2
discovered a damaged PBG control block while If you suspect an error in Db2, you might need to
attempting to write a check point log record. report the problem. For information about identifying
Db2 is abended.
Operator response Collect the following diagnostic items:
Notify the system programmer, print the • Console output from the system on which the job
SYS1.LOGREC, and request the SVC dump. Restart was run, and a listing of the SYSLOG data set for the
Db2. period of time that spans the failure.
If you suspect an error in Db2, you might need to 00C200CC

and reporting the problem, see Collecting diagnostic Explanation
discovered a close task has been waiting for prefetch
Problem determination to complete for two checkpoints.
System action
was run, and a listing of the SYSLOG data set for the An SVC dump is produced and checkpointing
period of time that spans the failure. continues.
archive tapes.
00C200CB If you suspect an error in Db2, you might need to
Explanation and reporting the problem, see Collecting diagnostic
discovered a damaged ABG or AB control block while
attempting to write a checkpoint. Problem determination
System action
Db2 is abnormally terminated; if processing were was run, and a listing of the SYSLOG data set for the
to continue, an invalid checkpoint would be created period of time that spans the failure.
which would damage data on a subsequent Db2 • Dynamic dump, taken to SYS1.DUMPxx data set, by
restart. Db2 (04E and 04F abends).
executing IFCEREP1.

00C200CF • Console output from the system on which the job
Explanation
Db2 could not acquire enough virtual storage for Db2 (04E and 04F abends).
allocating private buffers for an internal castout
process. The castout operation is queued until an • Listing of SYS1.LOGREC data set, obtained by
existing castout process becomes available. executing IFCEREP1.
00C200D1
System action
The requesting execution unit is abended. No dump is Explanation
produced. The buffer manager (BM) subcomponent of Db2 is
Problem determination: unable to perform I/O processing for the requesting
function. A prior abend has occurred in the buffer
00C200D0 manager I/O termination exit routine. An attempt
to retry and to continue main line processing (after
Explanation completion of processing of this prior abend) resulted
in recursion to the I/O termination exit routine's
The buffer manager (BM) subcomponent of Db2 is functional recovery routine (FRR).
unable to perform I/O processing for the requesting
function. A prior abend has occurred in the buffer
manager (BM) I/O termination exit routine. Retry of the System action
prior abend is not allowed by MVS. Db2 is abended.
System action Operator response

Db2 is abended. Notify the system programmer, print the
SYS1.LOGREC, and request the SVC dump. Restart
Operator response Db2.

SYS1.LOGREC, and request the SVC dump. Restart Problem determination
Db2. The FRR parameter list was recorded in the SDWA
variable recording area (VRA) when the original abend
System programmer response occurred. Examine the VRA to determine whether
the media manager request block (MMRB) is properly
If you suspect an error in Db2, you might need to passed by the media manager.
and reporting the problem, see Collecting diagnostic If you suspect an error in Db2, you might need to
data (Collecting data). report the problem. For information about identifying
The functional recovery routine (FRR) parameter list
was recorded in the SDWA variable recording area • Console output from the system on which the job
(VRA) when the original abend occurred. Examine was run, and a listing of the SYSLOG data set for the
the VRA to determine whether the media manager period of time that spans the failure.
request block (MMRB) is properly passed by the media • Dynamic dump, taken to SYS1.DUMPxx data set, by
manager. Db2 (04E and 04F abends).
If you suspect an error in Db2, you might need to • Listing of SYS1.LOGREC data set, obtained by
report the problem. For information about identifying executing IFCEREP1.
00C200D2

The buffer manager (BM) subcomponent of Db2 is Notify the system programmer, print the
unable to perform I/O processing for the requesting SYS1.LOGREC, and request the SVC dump. Restart
function. A prior abend has occurred in the buffer Db2.
manager I/O error exit routine during processing of a
database I/O error. System programmer response
System action
Db2 is abended. and reporting the problem, see Collecting diagnostic
Operator response
SYS1.LOGREC, and request the SVC dump. Restart See the Problem Determination section of the original
Db2. abend code.
Problem determination executing IFCEREP1.
The functional recovery routine (FRR) parameter list 00C200D4
was recorded in the SDWA variable recording area
(VRA) when the original abend occurred. Examine
the VRA to determine whether the media manager Explanation
request block (MMRB) is properly passed by the media A prior abend occurred in an I/O processing window
manager. If you suspect an error in Db2, you might of a buffer manager (BM) function. I/O functional
need to report the problem. For information about recovery cannot be reliably performed because the
identifying and reporting the problem, see Collecting tracking data required to do so is incomplete.
diagnostic data (Collecting data). The required data is probably missing because the
Collect the following diagnostic items: functional recovery routine (FRR) that is protecting the
abending I/O processing function was bypassed by
• Console output from the system on which the job MVS.
System action
Db2 (04E and 04F abends). Db2 is abended.
executing IFCEREP1. Operator response
00C200D3 Notify the system programmer, and print the
SYS1.LOGREC and the SVC dump. Restart Db2.
Explanation
A prior abend occurred in a 'must complete'
processing window of a buffer manager (BM) function. If you suspect an error in Db2, you might need to
System action
Db2 is abended.

See the Problem Determination section of the original An abend occurred in the I/O termination exit routine
abend code. while resuming the suspended execution unit. The
status of resume was 'indoubt' at the time of the
abend.
was run, and a listing of the SYSLOG data set for the System action
• Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 is abended.
executing IFCEREP1. Notify the system programmer, print the
00C200D5 SYS1.LOGREC, and request the SVC dump. Restart
Db2.
Explanation
An abend occurred in the I/O termination exit routine
while resuming the suspended execution unit. The If you suspect an error in Db2, you might need to
status of resume was 'indoubt' at the time of the report the problem. For information about identifying
abend. and reporting the problem, see Collecting diagnostic
System action
Db2 is abended.
The functional recovery routine (FRR) parameter list is
recorded in the SDWA variable recording area (VRA)
Operator response when the original abend occurred. Examine the VRA to
Notify the system programmer, print the determine whether the media manager request block
SYS1.LOGREC, and request the SVC dump. Restart (MMRB) is properly passed by the media manager. If
Db2. If you suspect an error in Db2, you might need to you suspect an error in Db2, you might need to report
report the problem. For information about identifying the problem. For information about identifying and
and reporting the problem, see Collecting diagnostic reporting the problem, see Collecting diagnostic data
data (Collecting data). (Collecting data).
The functional recovery routine (FRR) parameter list was run, and a listing of the SYSLOG data set for the
was recorded in the SDWA variable recording area period of time that spans the failure.
(VRA) when the original abend occurred. Examine • Dynamic dump, taken to SYS1.DUMPxx data set, by
the VRA to determine whether the media manager Db2 (04E and 04F abends).
request block (MMRB) is properly passed by the media • Listing of SYS1.LOGREC data set, obtained by
manager. If you suspect an error in Db2, you might executing IFCEREP1.
need to report the problem. For information about
identifying and reporting the problem, see Collecting 00C200D7
diagnostic data (Collecting data).
Collect the following diagnostic items: Explanation
• Console output from the system on which the job A prior abend occurred while resuming a suspended
was run, and a listing of the SYSLOG data set for the execution unit. The status of resume was 'indoubt' at
period of time that spans the failure. the time of the abend.
• Listing of SYS1.LOGREC data set, obtained by Db2 is abended.
executing IFCEREP1.
00C200D6

Notify the system programmer, print the period of time that spans the failure.
Db2. • Dynamic dump, taken to SYS1.DUMPxx data set, by
executing IFCEREP1.
report the problem. For information about identifying 00C200E0
A table space or index space cannot be accessed
Problem determination because Db2 is unable to create the referenced buffer
See the Problem Determination section of the original pool. The referenced buffer pool size was zero, which
abend code. indicates to Db2 that this buffer pool should not
be activated. Db2 message DSNB602I was issued to
Collect the following diagnostic items: inform the operator of the error. This reason code and
• Console output from the system on which the job the table space or index space name are recorded in
was run, and a listing of the SYSLOG data set for the the cursor table (CT) and made available to the user in
period of time that spans the failure. the SQLCA.

• Listing of SYS1.LOGREC data set, obtained by An SQLCODE -904 (resource not available) is returned
executing IFCEREP1. to the user. The SVC dump and the SYS1.LOGREC
recording are not requested.
00C200D8

Explanation
Analyze the virtual storage content of the database
This is a Db2 internal error. The buffer manager (BM) services address space (ssnmDBM1) to determine
subcomponent of Db2 discovered that some buffer further action. If appropriate, use the ALTER
manager resources are inconsistent. TABLESPACE or ALTER INDEX statement to modify
the affected table space or index to indicate a usable
System action buffer pool. To determine a usable buffer pool, use
the DISPLAY BUFFERPOOL command. If necessary,
Db2 is abended. use the ALTER BUFFERPOOL command to activate the
failing buffer pool by setting its VPSIZE to a nonzero
Operator response value.
Notify the system programmer, print the 00C200E1
Db2. Explanation
The buffer manager (BM) subcomponent of Db2 is
unable to open a data set that is required to be
If you suspect an error in Db2, you might need to accessed by the requesting function. An error was
report the problem. For information about identifying returned by the media manager CONNECT function,
and reporting the problem, see Collecting diagnostic which was invoked to open a VSAM data set. Db2
data (Collecting data). message DSNB204I was issued to inform the operator
of the error condition. This reason code and the
Problem determination data set name are recorded in the cursor table (CT)
and made available to the user in the SQLCA or in
Collect the following diagnostic items: messages.

System action explanation of this error code. Correct the situation,
and notify the user to invoke the application again.
A 'resource not available' code is returned to the user.
Abend status is recorded in SYS1.LOGREC.
User response
Operator response Notify the system programmer. Invoke the application
again after the system programmer has corrected the
Notify the system programmer. error.
System programmer response Problem determination

Refer to system message IEC161I and Db2 message The unexpected dynamic allocation return code is
DSNB204I for assistance in determining the cause of saved in register 8. It may help determine the cause
the error. Correct the situation, and notify the user to of the failure.
invoke the application again.
The unexpected media manager return code is saved period of time that spans the failure.
in register 8. It may help determine the cause of the
failure. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
• Console output from the system on which the job that contains the Db2 subsystem catalog that
was run, and a listing of the SYSLOG data set for the defined the failing index or table.
period of time that spans the failure. • VTOC listing of the disk volume on which the failing
• Listing of SYS1.LOGREC data set, obtained by operation occurred.
executing IFCEREP1.
00C200E5
defined the failing index or table. Explanation
• VTOC listing of the disk volume on which the failing The buffer manager (BM) subcomponent of Db2 is
operation occurred. unable to perform the I/O operation on a data
set that is required by the requesting function. A
00C200E2 logical I/O error was detected by the buffer manager
I/O functions. The logical I/O error indicates that a
Explanation requested page (read operation) resides within the
error page range of the data set. This reason code and
The buffer manager (BM) subcomponent of Db2 the data set name are recorded in the cursor table
is unable to open a data set that is required by (CT) and made available to the user in the SQLCA or in
the requesting function. An error was returned by messages.
the dynamic allocation function that was invoked to
allocate a VSAM data set. Db2 message DSNB207I
was issued to inform the operator of the error System action
condition. This reason code and the data set name are A 'resource not available' code is returned to the user.
recorded in the cursor table (CT) and made available to
the user in the SQLCA or in messages.
Operator response
System action Use the -DISPLAY DB command to obtain the error
page range. Notify the system programmer.
Abend status is recorded in SYS1.LOGREC.
System programmer response The error page range can be located from the console
sheet or through the -DISPLAY DB command. Correct
The error code returned from the dynamic allocation the error pages with the recovery utility, and notify the
function was externalized in the DSNB207I message. user to invoke the application again. If you suspect an
Refer to the appropriate MVS publication for an

error in Db2, you might need to report the problem. • Console output from the system on which the job
For information about identifying and reporting the was run, and a listing of the SYSLOG data set for the
problem, see Collecting diagnostic data (Collecting period of time that spans the failure.
data). • IDCAMS LISTCAT output for the ICF (VSAM) catalog
User response defined the failing index or table.
Notify the system programmer. Invoke the application • VTOC listing of the disk volume on which the failing
after the system programmer has corrected the error. operation occurred.
Check the MVS console log for an IOS (I/O subsystem)
Problem determination error message indicating the type of I/O error that
Collect the following diagnostic items: problem determination directions for that message.
• Console output from the system on which the job 00C200E8
Explanation
that contains the Db2 subsystem catalog that The buffer pool (indicated in the SQLCA) cannot
defined the failing index or table. be created because of insufficient virtual storage.
• VTOC listing of the disk volume on which the failing Message DSNB603I or DSNB605I was issued to
operation occurred. inform the operator of the error. This reason code and
the buffer pool ID are recorded in the cursor table
00C200E6 (CT) and made available to the user in the SQLCA or in
messages.
Explanation
System action
unable to perform the I/O operation on a data set that An SQLCODE -904 (resource not available) is returned
is required by the requesting function. A permanent to the user. The SVC dump and the SYS1.LOGREC
I/O error was detected by the media manager during recording are not requested.
preformat processing. This reason code and the data
set name are recorded in the cursor table (CT)
Operator response
and made available to the user in the SQLCA or in
messages. Notify the system programmer.

A 'resource not available' code is returned to the user. Analyze the virtual storage content of the database
services address space (ssnmDBM1) to determine
System programmer response further action. If appropriate, use the ALTER
TABLESPACE or ALTER INDEX statement to indicate
Recover the entire data set with the recovery utility, use of a different buffer pool. Otherwise, use ALTER
and notify the user to invoke the application again. BUFFERPOOL commands to balance virtual storage
If you suspect an error in Db2, you might need to usage for all buffer pools.
and reporting the problem, see Collecting diagnostic 00C200E9
Explanation
User response A buffer could not be assigned in the buffer pool
Notify the system programmer. Invoke the application (indicated in the SQLCA) because all buffers in the
after the system programmer has corrected the error. buffer pool are in a nondisplaceable state. (Buffers are
in a nondisplaceable state when they contain actively
referenced pages or updated pages for which writes
Problem determination are pending.)
Collect the following diagnostic items: Message DSNB601I was issued to inform the operator
of the error. This reason code and the buffer pool

ID are recorded in the cursor table (CT) and made If DSNB350I or DSNB351I messages were issued,
available to the user in the SQLCA or in messages. then after you take one of the actions above, recover
the GRECP objects as indicated in the "System
System action Programmer Response" for DSNB350I or DSNB351I.
An SQLCODE -904 (resource not available) is returned 00C200EB

to the user. The SVC dump and the SYS1.LOGREC
recording are not requested. Explanation
A data sharing group member is not able to perform
Operator response a global drain request on an object (a table space,
Notify the system programmer. an index space, or a partition). One or more peer
members in the group hold retained locks on the
object. Message DSNT501I is sent to the console to
System programmer response report the condition.
Reduce concurrent activity by reducing the number of
Db2 threads, or, if necessary, increase the size of the System action
failing buffer pool by using the ALTER BUFFERPOOL
command. A 'resource not available' return code, reason code,
00C200EA function.

Db2 is unable to perform the drain function on an Use the DISPLAY DATABASE command with the LOCKS
object (a table space, an index space, or a partition) option to display the member names owning the
because the object was held by other claimers and the retained locks. You must restart those subsystems to
drain request timed out waiting for the claim count to remove the 'resource unavailable' condition.
reach zero.
System action 00C200EC

Explanation
pending (GRECP) object following the failure of a A member of a Db2 data sharing group was unable
group buffer pool (GBP), then Db2 issues message to perform a global drain request on an object (a
DSNB350I or DSNB351I to the console with this table space, an index space, or a partition). One or
reason code indicating that the object cannot be more peer DB2s in the group failed to drain the object
automatically recovered. because some error occurred. Both the Db2 running
the request and the peer Db2 send Db2 message
Otherwise, a 'resource not available' return and reason
DSNT500I to the console to report the problem.
code are sent back to the requesting function. Db2
message DSNT500I may be sent to the console. The
reason code and the object name are recorded in the System action
cursor table (CT) and made available to the user in the
A 'resource not available' return code, reason code and
SQLCA or in the message.
object name are sent back to the requesting function.
System programmer response Operator response

Take one of these actions:
Notify the system programmer.
• Reevaluate the utility timeout factor on installation
panel DSNTIPI and increase it, if necessary. System programmer response
• Find the threads holding the object through the
-DISPLAY DB CLAIMERS command on the object. Retrieve the DSNT501I messages from the console
Either terminate those threads or wait until no one and analyze the corresponding reason and error codes.
holds the object. Then invoke the application again. Problem determination:
00C200ED

Db2, in a data sharing environment, detected that the If you suspect an error in Db2, you might need to
requested use of a type 1 index with a SUBPAGES report the problem. For information about identifying
value greater than 1 would have caused the index to and reporting the problem, see Collecting diagnostic
become group buffer pool dependent. Db2 does not data (Collecting data).
allow type 1 indexes with a SUBPAGES value greater
than 1 to become group buffer pool dependent. 00C200F1

The use of the index is not allowed. The buffer manager (BM) subcomponent of Db2 is
unable to unallocate a Db2 data set. An error was
returned by the dynamic unallocation function that
User response was invoked to unallocate a data set. This reason code
If the index is to be used in group buffer pool and the data set name are recorded in the cursor table
dependent mode, then either the index should be (CT) and made available to the user in the SQLCA or in
converted to a type 2 index or it should be converted messages.
to a type 1 index with SUBPAGES 1.
System action
00C200EF
Explanation The SVC dump and the SYS1.LOGREC recording are
requested.
Db2 was unable to open a required data set because
the data set does not have the extended addressability
Operator response
attribute.
System action
A "resource not available" code is returned. This
reason code and the data set name are recorded in If you suspect an error in Db2, you might need to
the SQLCA and in message DSNT500I. report the problem. For information about identifying
System programmer response data (Collecting data).
Associate the data set with an extended addressability

data class.
The unexpected dynamic unallocation reason code is
Related information
saved in register 8. It may help determine the cause
DSNT500I (Db2 Messages) of the failure. Refer to the appropriate MVS publication
for an explanation of the error code.
00C200F0
Db2 encountered an error on an IXLCACHE request
while trying to write a page to the group buffer pool
during physical lock (P-lock) negotiation. • Dynamic dump, taken to SYS1.DUMPxx data set, by
System action • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
The requesting execution unit abends. The error
is recorded to SYS1.LOGREC, but the dump is
suppressed and the abend is retried in the functional
recovery. Another group member, requesting the P-
lock that caused the negotiation on this member, • VTOC listing of the disk volume on which the failing
receives a resource not available code of 00C20252, operation occurred.
and its P-lock request is denied.
00C200F2

Explanation • Group buffer pool dependent conversion lock on a
page set or partition
unable to close a Db2 data set. An error was returned • Group buffer pool start or stop lock
by the media manager DISCONNECT function that was • ALTER BUFFERPOOL lock
invoked to close a data set. This reason code and the
The IRLM LOCK request detected a timeout error.
data set name are recorded in the cursor table (CT)
and in the SQLCA or in messages.
System action
System action A 'resource not available' code is returned to the user.
This reason code and the data set name are recorded
in the cursor table (CT) and are available to the user in
The SVC dump and the SYS1.LOGREC recording are
the SQLCA or in messages.
requested.
User response
Operator response
Resubmit the failing application.
System programmer response 00C200F4
Db2 is unable to obtain one of the following locks:
• SYSLGRNG or SYSLGRNXrecording lock on a table
space
• Group buffer pool dependent conversion lock on a
The unexpected media manager disconnect reason page set or partition
code is saved in register 8 and may help determine
the cause of the failure. Locate the corresponding • Group buffer pool start or stop lock
IEC161I message in the operator console sheet, and • ALTER BUFFERPOOL lock
refer to the appropriate MVS publication for assistance
The IRLM LOCK request detected an out-of-storage
in determining the cause of the error.
condition.
A 'resource not available' code is returned to the
user. This reason code is recorded in the cursor table
• Dynamic dump, taken to SYS1.DUMPxx data set, by (CT) and is available to the user in the SQLCA or in
Db2 (04E and 04F abends). messages.
executing IFCEREP1. User response
defined the failing index or table. Problem determination:
• VTOC listing of the disk volume on which the failing 00C200F6
operation occurred.
00C200F3 Explanation
Explanation unable to open a data set that is required to be
accessed by the requesting function. The data set has
Db2 is unable to obtain one of the following locks:
been migrated by DFHSM and the data set must be
• SYSLGRNG or SYSLGRNXrecording lock on a table recalled before being accessed. Since the RECALL(yes)
space option was selected by the installation, a recall for
the migrated data set has been initiated. A recall was

not complete after the amount of time specified in the Problem determination
RECALL option had elapsed.
This reason code and the data set name are recorded the indicated diagnostic information:
in the cursor table (CT) and made available to the
user in the SQLCA or in messages. The data set name GPR
and the reason code indicated are the last migrated Content
data set requested. Other migrated data sets within 7
the table space may exist. For each one that exists, a Address of the page buffer
DSNT500I message containing the data set name and 8
reason code has been sent to the console. Address of the page set block (PB)
System action
A 'resource not available' code is returned to the user. was run, and a listing of the SYSLOG data set for the
A DSNT500I message is sent to the console. period of time that spans the failure.
User response that contains the Db2 subsystem catalog that
After the data set has been restored, rerun defined the failing index or table.
the application program, transaction, or query. If • VTOC listing of the disk volume on which the failing
necessary, contact the operator to find out the status operation occurred.
of the migrated data set. • VVDS dump of the volumes that contain the data set.
00C200F7 • Db2 REPAIR dump of the requested page.
• DSN1LOGP detail report that contains log records
Explanation associated with the damaged page.
The page found in the buffer is not the page requested 00C200F8
by the buffer manager. The buffer manager detected
the error by comparing the page number of the page
Explanation
returned with the requested page number. This error
may be caused by one of the problems: The buffer manager (BM) subcomponent of Db2 is
unable to perform the I/O operation on a data set. A
• Either the VTOC or VVDS is damaged, causing
physical I/O error was detected by the buffer manager
multiple data sets to occupy the same extents on
I/O functions.
DASD.
• The page was altered incorrectly by a non-Db2 This reason code and the data set name are recorded
facility or a Db2 service aid. in the cursor table (CT) and made available to the user
in the SQLCA or in messages.
• An internal Db2 error damaged the page.
The recovery log will be required for problem
determination. System action
System action A DSNB224I message is issued, unless it has already
been issued 10 times for the data set.
If the I/O is a write operation, or if the I/O is a read
operation performed during restart or rollback, then
Operator response the error page range of the data set is updated. A
Notify the system programmer, print the DSNU086E message is issued indicating the data set
SYS1.LOGREC, and request the SVC dump. name and its corresponding I/O error page range,
unless it has already been issued 10 times for the data
set.
If you suspect an error in Db2, you might need to Operator response
and reporting the problem, see Collecting diagnostic Use the -DISPLAY DB command to obtain the error
data (Collecting data). page range. Notify the system programmer.

System programmer response User response
The error page range can be located from the console Issue the HSM command (HRECALL) to restore the
sheet or with the -DISPLAY DB command. Correct the migrated data set. Rerun your application program,
error pages with the recovery utility, and notify the transaction, or query after the data set is restored.
user to invoke the application again. If you suspect an
error in Db2, you might need to report the problem.
For information about identifying and reporting the 00C200FA
problem, see Collecting diagnostic data (Collecting
data). Explanation
User response
unable to obtain an open lock to perform a physical
Notify the system programmer. Invoke the application open or close of a page set. A timeout error was
after the system programmer has corrected the error. detected by the IRLM LOCK request. The reason code
and the database and page set names are recorded in
Problem determination the cursor table (CT). They are made available to the
user in the SQLCA or in messages.
A common reason for this failure is when IRLMRWT is
• Console output from the system on which the job less than RECALLD, and an HSM recall for the migrated
was run, and a listing of the SYSLOG data set for the data set exceeds IRLMRWT.
• IDCAMS LISTCAT output for the ICF (VSAM) catalog System action
defined the failing index or table. A 'resource not available' code is returned to the user.
operation occurred. User response
Check the MVS console log for an IOS (I/O subsystem) Resubmit the failing application.
error message indicating the type of I/O error that 00C200FB
problem determination directions for that message.
Explanation
00C200F9
unable to obtain an open lock to perform a physical
Explanation open or close of a page set. An out-of-storage
Db2 is unable to open a data set that the requesting condition was detected by the IRLM LOCK request. The
function must access. The data set was migrated by reason code and the database and page set names are
HSM and must be recalled before being accessed. Db2 recorded in the cursor table (CT). They are available to
attempted to initiate a recall of the migrated data set the user in the SQLCA or in messages.
but was unsuccessful.
This reason code and the data set name are recorded System action
in the cursor table (CT) and made available to the A 'resource not available' code is returned to the user.
user in the SQLCA or in messages. The data set name
and the reason code indicated are the last requested
migrated data set. Other migrated data sets might User response
exist. For each existing data set, message DSNT500I Resubmit the failing application.
containing the data set name and reason code was
sent to the console. 00C200FC

A 'resource not available' code is returned to the user. The buffer manager (BM) subcomponent of Db2 is
A DSNT500I message is sent to the console. unable to obtain an open lock to perform a physical
open or close of a page set. A system error was
detected by the IRLM LOCK request. The reason code

and the database and page set names are recorded in Explanation
the cursor table (CT). They are made available to the
user in the SQLCA or in messages. Db2 is unable to open a data set that the requesting
function must access. The data set was migrated by
DFHSM and must be recalled before being accessed.
System action Since the RECALL(no) option was selected by the
A 'resource not available' code is returned to the user. installation, recall for the migrated data set was not
initiated.
User response This reason code and the data set name are recorded
in the cursor table (CT) and made available to the user
Resubmit the failing application. in the SQLCA or in messages. The data set name and
00C200FD the reason code indicated are the last migrated data
set requested. Other migrated data sets within the
table space might exist. For each existing data set,
Explanation message DSNT500I containing the data set name and
The buffer manager is unable to perform the I/O reason code has been sent to the console.
operation on a data set due to an error on page's parity
flag detected by the buffer manager's I/O function. System action
System action A DSNT500I message is sent to the console.
A 'resource not available' return code is returned to
the user. The related reason code 00C200FD, the page System programmer response
number, the page set name, and the database name
in question are recorded in the cursor table (CT) and Issue the DFHSM command (HRECALL) to restore the
made available to the user in the SQLCA. migrated data set.
Operator response User response

Notify the system programmer. Notify the system programmer. After the data set is
restored, rerun the application program, transaction,
or query.
00C200FF
The error page can be found via SQLCA. Correct the
error pages with the recovery utility, and notify the
user to invoke the application again. Explanation
If you suspect an error in Db2, you might need to An attempted open of a page set failed because Db2
report the problem. For information about identifying has reached the MVS limit on concurrent open data
and reporting the problem, see Collecting diagnostic sets.
System action
Problem determination A 'resource not available' (SQLCODE -904) is returned
Collect the following diagnostic items: to the user and the requested open is not performed.
This reason code and the data set name are recorded
• Console output from the system on which the job in the cursor table (CT) and made available to the
was run, and a listing of the SYSLOG data set for the user in the SQLCA. A DSNB207I message is displayed
period of time that spans the failure. on the operator console. The SVC dump and the
• IDCAMS LISTCAT output for the ICF (VSAM) catalog SYS1.LOGREC recording are not requested.
defined the failing index or table. Operator response
operation occurred. Notify the system programmer.
00C200FE

Reduce the number of page sets that must be kept Notify the system programmer.
open by Db2 by limiting the amount of concurrent
activity. Problem determination
Collect the following diagnostic item:
• Console output from the system on which the job period of time that spans the failure.
period of time that spans the failure. 00C20102
00C20101 Explanation
A read-only system attempted to access an
Explanation
inconsistent data set. This reason code and the data
The sharing attribute is inconsistent between the set name are made available to the user in the SQLCA
header page of a data set and the DBD. This reason or in messages.
code and the data set name are made available to the
user in the SQLCA or in messages. System action
A "resource not available" code is returned to the user.
System action
A "resource not available" code is returned to the user. System programmer response
On the system in which the database is defined as
ROSHARE OWNER, perform the following tasks:
First determine whether the database is shared,
• Use the -DISPLAY DATABASE command to ensure
and whether it is owned by this system. This
there is no exceptional state for this table space or
can be achieved by issuing a SELECT on the
index.
SYSIBM.SYSDATABASE catalog table, where the
database name is the database you are checking, and • Issue the -STOP DATABASE command with the
by examining the ROSHARE column. SPACENAM parameter to stop this table space or
index.
If the Db2 catalog indicates that it is a ROSHARE
OWNER database, the problem can be corrected by
the REPAIR utility or the -STOP DATABASE command. User response
The -STOP DATABASE command will reformat the Notify the system programmer.
header page and make it consistent with the DBD.
If the database is ROSHARE READ on this system, then Problem determination
check the definition of the database on the owning
system. If, on the owning system, the database is no Collect the following diagnostic items:
longer defined as ROSHARE OWNER, then the table • Console output from the system on which the job
space or index should be dropped on the system on was run, and a listing of the SYSLOG data set for the
which the error was detected, since the database has period of time that spans the failure.
been altered to nonshared by the owning system.
However, if the database is defined as ROSHARE 00C20103
OWNER on the owning system, then issue a -STOP
DATABASE with the SPACENAM parameter from the Explanation
owning system, which will make the header page
consistent with the owner's DBD, and force this Db2 is unable to access a data set because its system
change to DASD, making it available to other systems. page is inaccessible. This reason code and the data
set name are available to the user in the SQLCA or in
If it is a nonshared database, then the sharing attribute messages.
can only be corrected via the REPAIR utility.

A "resource not available" code is returned to the user. period of time that spans the failure.
00C20105
Determine why the system page is inaccessible by Explanation
examining any error messages that appeared on the
console at the time of the error, or by issuing a The page set creation timestamp is inconsistent
-DISPLAY DATABASE command. Take the appropriate between the header page and the DBD. This reason
action to correct the situation. code and the data set name are made available to the
User response
System action
First determine whether the database is shared,
• Console output from the system on which the job and whether it is owned by this system. This
was run, and a listing of the SYSLOG data set for the can be achieved by issuing a SELECT on the
period of time that spans the failure. SYSIBM.SYSDATABASE catalog table, where the
00C20104 database name is the database you are checking, and
examining the ROSHARE column.
Explanation For a data set in a ROSHARE OWNER database, if the
failure occurs on a CREATE TABLESPACE or CREATE
Db2 is unable to access a shared data set because it INDEX, the timestamp mismatch indicates that the
was down leveled by a DSN1COPY job, or a REPAIR table space or index was previously dropped, but Db2
utility with REPLACE RESET specified. This reason was unable to delete the data set. In this case, the
code and the data set name are made available to the data set must be deleted using AMS DELETE CLUSTER
user in the SQLCA or in messages. before the CREATE can take place.
For a data set in a ROSHARE OWNER database at
System action any time other than CREATE TABLESPACE or CREATE
A "resource not available" code is returned to the user. INDEX, the inconsistent timestamp can be corrected
by first stopping the table space or index via the -STOP
DATABASE command with the SPACENAM parameter,
and then issuing the -START DATABASE command to
On the system in which the database is defined as start it. The -STOP DATABASE command will reformat
ROSHARE OWNER, perform the following tasks: the header page using the information retrieved from
the DBD.
• Use the -DISPLAY DATABASE command to ensure
there is no exceptional state for this table space or For a data set in a ROSHARE READ database, a
index. timestamp mismatch indicates that the table space or
• Issue the -STOP DATABASE command with the index has been dropped and re-created on the owning
SPACENAM parameter to stop this table space or system, and must also be dropped and re-created on
index. this system.
For a data set in a nonshared database, the timestamp
User response value in the header page can only be corrected via the
REPAIR utility.
User response

Collect the following diagnostic items: Notify the system programmer.
was run, and a listing of the SYSLOG data set for the Problem determination
00C20106 • Console output from the system on which the job
Explanation period of time that spans the failure.
An update was attempted on a database defined as 00C20108
ROSHARE READ. This reason code and the data set
name are made available to the user in the SQLCA or in Explanation
messages.
An object in a ROSHARE OWNER database cannot
be accessed. At least one system with the database
System action
defined as ROSHARE READ is still accessing it. This
A "resource not available" code is returned to the user. reason code and the data set name are made available
to the user in the SQLCA or in messages.
User response
System action
An update operation is not allowed in this database.
Check to ensure that the target of the update was A "resource not available" code is returned to the user.
correct and that the database is defined as ROSHARE
READ. If the update should occur, issue the update System programmer response
on the system in which the database was defined as
ROSHARE OWNER. Ensure that there are no systems on which the
database is defined as ROSHARE READ that are still
accessing the database. Issue the -STOP DATABASE
command with the SPACENAM parameter on the
Collect the following diagnostic items: ROSHARE READ systems that are accessing the
database.
period of time that spans the failure. User response
, Notify the system programmer.
00C20107
Explanation Collect the following diagnostic items:
An update was attempted in a ROSHARE OWNER • Console output from the system on which the job
database, but the data set was opened in RO mode. was run, and a listing of the SYSLOG data set for the
This reason code and the data set name are made period of time that spans the failure.
available to the user in the SQLCA or in messages.
00C20109

An object in a ROSHARE READ database cannot be
accessed. The system with the database defined as
System programmer response ROSHARE OWNER still has RW access. This reason
code and the data set name are made available to the
Issue the -STOP DATABASE command with the
SPACENAM parameter to explicitly stop this table
space/index space and then issue the -START
DATABASE ACCESS(RW) command. System action

System programmer response 00C2010B
On the system in which the database is defined as
ROSHARE OWNER, perform the following tasks: Explanation
• Use the -DISPLAY DATABASE command to ensure Db2 is attempting to open a shared data set in a
there are no exceptional states for this table space database defined for ROSHARE, but the data set
or index. cannot be accessed because it is not defined with
SHAREOPTIONS(1,3).
• Issue the -STOP DATABASE command with the
SPACENAM parameter to stop this table space or
index. System action
User response This reason code and the data set name are made

Ensure that this data set belongs to a shared database,
and check the SHAREOPTIONS using IDCAMS
• Console output from the system on which the job LISTCAT. If so, use AMS ALTER SHAREOPTIONS
was run, and a listing of the SYSLOG data set for the to alter the data set to SHAREOPTIONS(1,3), and
period of time that spans the failure. resubmit the failing application.
00C2010A
User response
Explanation Notify the system programmer.
Db2 is attempting to open a shared data set in a
ROSHARE READ database, but the system cannot Problem determination
locate the data set. The table space or index might Collect the following diagnostic items:
already be dropped from the owning system.
System action period of time that spans the failure.
00C2010C
This reason code and the data set name are made
Explanation
System programmer response Db2 was unable to update the high-used RBA in the
VSAM volume data set (VVDS) when it was ready to
Run IDCAMS LISTCAT to verify the existence of this
close a data set. VVDS must be updated to reflect
data set. Verify whether the associated table space
data loaded by a RECOVER, LOAD, or REORG utility job.
or index exists in the database defined as ROSHARE
Message DSNB200Iis issued to the console with the
OWNER. If not, issue DROP TABLESPACE or INDEX
VSAM media manager return codes.
on all systems in which the database is defined as
ROSHARE READ. This reason code and the data set name are recorded
in the cursor table (CT) and made available in the
User response SQLCA or in messages.

System action
Problem determination A 'resource not available' code is returned to the user.
A DSNB200Imessage is issued to the console. Db2
Collect the following diagnostic items: continues to close the data set.

Refer to system messages IEC161I and Db2 message This is a Db2 internal error. Db2 encountered a
DSNB200A for assistance in determining the cause of problem while trying to add a page to the logical page
the error. Correct the condition, and notify the user to list (LPL).
reinvoke the application.
System action
User response
Contact the system programmer. Restart or rerun
the RECOVER, LOAD, or REORG job after the system Operator response
programmer corrects the error.
Notify the system programmer, print SYS1.LOGREC,
and request an SVC dump.
Collect the following diagnostic items: Problem determination
• IDCAMS LISTCAT output for the ICF (VSAM) catalog data (Collecting data).
defined the failing index or table. 00C2010F
• IDCAMS LISTCAT output that shows the attributes
of all active log data sets for the Db2 member that Explanation
failed. This dump provides assistance for diagnosing the page
00C2010D latch timeout problem after 00C20031 is returned as
the reason code for 'resource not available'.
Explanation
System action
Db2 was unable to open a required data set because
an unexpected level ID was encountered. The requesting execution unit is abended to take a
diagnostic dump then recovered to return an SQLCODE
The reason code and the data set name are made -904 (resource not available) to the user with the
available in the SQLCA or in messages. 00C20031 reason code. The resource name is also
provided.
System action
A 'resource unavailable' code is returned to the user. User response
Message DSNB232I is issued to the console if it was Contact the system programmer to determine why the
not already issued for the data set. Db2 failed to open resource is unavailable. Print the SYS1.LOGREC and
the data set. the SVC dump.
00C20110
Operator response
Db2 cannot access a table space, index, or partition
System programmer response because the highest formatted page (as recorded by
Refer to message DSNB232I for help in determining Db2 in the header page) is higher than that derived
the cause of the error. Run the utility REPAIR LEVELID from the VSAM high-used RBA.
or recover the table space or index, and then tell the The reason code and the data set name for this error
user to rerun the application. are available in the SQLCA or in messages.
00C2010E System action
Db2 returns a 'resource unavailable' code to the user.

To enable access to the object, take one of the An attempt was made to access a Db2 data set which
following actions: was defined with incompatible Control Interval (CI)
size. A compatible CI size is either 4K or the page size.
• Restore the object to a consistent state with the
RECOVER or REBUILD utility, DSN1COPY, or some
other means. System action
• Replace the data using the LOAD REPLACE utility. A 'resource not available' code is returned to the user.
• Allow access to the data in its current state. Use the This reason code and the data set name are made
REPAIR LEVELID utility to reset the high-used page available to the user in the SQLCA.
number in the header page to be consistent with the
VSAM high-used RBA. This may result in inconsistent System programmer response
data.
Ensure that the data set is defined with the compatible
CI size.
Determine the high-formatted page number in the User response
header page by running DSN1PRNT with the FORMAT
option, and checking the value of HPGHPREF. Convert the data set attribute 'control interval size' of
the associated table space from 4K CI into the one
You can also determine the VSAM high-used RBA by matching the page size. Db2 Utilities REORG table
running an IDCAMS LISTCAT on the data set. space, LOAD with REPLACE, and RECOVER can be
00C20111 used to convert the table space.

Db2 attempted to access a striped data set with a Obtain an access method services LISTCAT for the
page size of 8 KB, 16 KB, or 32 KB. The data set is named data set's attributes.
defined with a 4 KB control interval (CI) size. Db2 does 00C20113
not allow this because partial writes cannot always be
detected.
Explanation
System action Db2 reached the limit for concurrent open data sets.
The OPEN statement fails with this reason code when
SQLCODE -904 is returned. The SQLCA contains a the number of concurrent open data sets reaches
resource-not-available reason code and the data set the greater of 32,768 or the value of the DSMAX
name. subsystem parameter.

System action
Ensure that the data set is defined with a control
interval size that matches its page size. SQLCODE -904 is issued and the requested open is
not performed. Reason code 00C20113 and the data
set name are recorded in the SQLCA. SVC dump and
User response SYS1.LOGREC recording are not requested.
Convert the control interval size of the associated
table space from 4 KB to a control interval size that Operator response
matches the page size. The REORG TABLESPACE,
LOAD REPLACE, or RECOVER utility can be used to Notify the system programmer.
convert the control interval size for the table space.
Problem determination Take one of the following actions:
Run access method services LISTCAT to determine the • Reduce the number of data sets that must be kept
data set attributes. open by Db2 by limiting the amount of concurrent
00C20112 activity.

• Increase the value of the DSMAX parameter Explanation
Related tasks Db2 cannot retry automatic GRECP or LPL recovery
Managing the opening and closing of data sets because AUTOREC is set to NO.
(Db2 Performance)
DSMAX field (DSMAX subsystem parameter)
(Db2 Installation and Migration) Processing continues.
OPEN (Db2 SQL)
Related information User response
-904 Recover the objects manually.
UNSUCCESSFUL EXECUTION CAUSED BY AN
UNAVAILABLE RESOURCE. REASON reason- Related concepts
code, TYPE OF RESOURCE resource-type, AND Normal restart and recovery (Db2
RESOURCE NAME resource-name Administration Guide)
Related reference
00C20120 Data sharing status descriptions (Db2 Data
Sharing Planning and Administration)
Explanation Group buffer pool RECOVER-pending status
(Db2 Utilities)
This abend reason code is issued because of
an unexpected return code from IWM4MREG, 00C20203
IWM4MDRG, or IWM4MCHS.
Explanation
System action
Db2 cannot connect to a group buffer pool. The group
A dump is requested, then Db2 retries the abend and buffer pool is not usable by this release of Db2. This
processing continues. Db2 subsystem is a member of a data sharing group
00C20200 containing Db2 members of different release levels. A
later release level of Db2 specified an option for this
group buffer pool that is not supported by the previous
Explanation Db2 releases. The presence of this option makes the
Db2 was unable to open a required index data set group buffer pool inaccessible to the previous Db2
because the index was formatted incorrectly. For releases.
example, it may have been formatted as a Type 1 index
when the Db2 catalog indicates that it should be Type System action
2.
Db2 takes the following actions:
The reason code and index data set name are made
available in the SQL communication area or in related • Unless already issued, message DSNB301E is sent
messages. to the console with this reason code to indicate that
a connect failure occurred.
System action • SQLCODE -904 (resource not available) is returned
to the user with this reason code. The resource type
A 'resource unavailable' code is returned to the user. and resource name are also returned.
Operator response System programmer response

Notify the system programmer. Take one of the following actions:
• Issue the -ALTER GROUPBUFFERPOOL command
System programmer response from a Db2 that is at the later release level to
Use the RECOVER utility to restore the index to a remove the new option so that previous release
consistent state. levels of Db2 can access the group buffer pool.
• Migrate the previous release levels to the current
release.
00C20202

Contact the system programmer. The action Db2 takes depends on the situation, as
follows:
• If Db2 tries to read a page from the group buffer pool
00C20204
and finds that the group buffer pool is in DAP status,
the following actions are taken:
Explanation
– SQLCODE -904 (resource not available) is
Db2 is unable to connect to a group buffer pool returned to the user with this reason code. The
because MVS detected a problem on the IXLCONN name of the group buffer pool is also returned.
request. • If Db2 tries to read a page from the group buffer
pool for rollback, backout, or restart and finds that
System action the group buffer pool is in DAP status, the following
actions are taken:
SQLCODE -904 (resource not available) and the
group buffer pool name are returned to the user. – The page is added to the logical page list (LPL) for
Unless already issued for the IXLCONN code, message the page set.
DSNB301E, which contains this reason code and the – Message DSNB250E is issued to the console with
IXLCONN code, is issued to the console. this reason code.
• If Db2 tries to write a page to the group buffer pool
User response and finds that the group buffer pool is in DAP status,
Contact the system programmer. the following actions are taken:
– The page is added to the logical page list (LPL) for
Problem determination the page set.
– Message DSNB250E is issued to the console with
The reason code returned by the IXLCONN request is
this reason code.
given in message DSNB301E.
• If Db2 detects DAP status when it tries to connect
If the connection problem was caused by insufficient the group buffer pool, or if Db2 detects a group
storage in a coupling facility, tell the MVS system buffer pool version ID mismatch after a successful
administrator to alleviate the storage constraint connection, the following actions are taken:
problem by making additional storage available to
the involved coupling facility, or by changing the – The damage assessment process is triggered for
active MVS CFRM administrative policy to redefine this group buffer pool.
the coupling facility structure to a different coupling – SQLCODE -904 (resource not available) is
facility. Another alternative is to have the database returned to the user with this reason code. The
administrator reassign those inter-Db2 sharing page name of the group buffer pool is also returned.
sets to a different Db2 buffer pool.
– Unless already issued, message DSNB301E,
Related reference which contains this reason code, is issued to the
Return and Reason Codes console.
Related information
-904 System programmer response
Message DSNB304I is issued when the group buffer
UNAVAILABLE RESOURCE. REASON reason-
pool is entered into DAP state and message DSNB305I
code, TYPE OF RESOURCE resource-type, AND
is issued when the DAP status is cleared. During the
damage assessment process, Db2 must determine
DSNB301E (Db2 Messages) which page sets or partitions might have had changed
pages in the failed coupling facility structure and need
00C20205 to be recovered. Each page set/partition fitting this
criteria is entered into 'group buffer pool REBUILD
Explanation pending (GRECP)' status. A page set/partition in
GRECP status remains unavailable for read or update
Db2 is unable to access a group buffer pool because until it is recovered.
of a damage assessment pending (DAP) status against
the group buffer pool.

Contact the system programmer. The user attempted to access a group-buffer-pool-
dependent page set or partition. However, the Db2
00C20206 member was unable to connect to the group buffer
pool because there was not enough hardware system
Explanation area (HSA) storage in which to allocate the local cache
vector (LCV).
An attempt was made to access a page which is
currently in the logical page list (LPL). LPL pages are
unavailable until recovery on the affected page set System action
completes. Db2 disconnects from the group buffer pool and issues
message DSNB301E with this reason code, if it has not
System action yet been issued. DSNB301E is usually preceded by a
DSNB306I message.
SQLCODE -904 (resource not available) is returned to
the user with this reason code. The resource name is SQLCODE -904 is returned to the user with this reason
also given. code.
System programmer response System programmer response

For those page sets in the LPL, use the RECOVER utility Refer to message DSNB306I.
or the -START DATABASE command.
User response
User response
Contact the system programmer.
Contact the system programmer.
Problem determination: Problem determination
00C20207 Collect the following diagnostic items:
Db2 is unable to connect to a group buffer pool
because of a Db2 system error during connect 00C20210
processing. This is an internal Db2 problem.
Explanation
System action
An attempt was made to access a page set or partition
A SYS1.LOGREC entry is produced and an SVC dump which is currently in group buffer pool recovery
is requested for the original abend which caused this pending (GRECP) status.
condition. After doing resource and latch recovery, Db2
retries the abend if retry is allowed. SQLCODE -904
System action
(resource not available) is returned to the user with
this reason code and the group buffer pool name. SQLCODE -904 (resource not available) is returned
Unless already issued, message DSNB301E, which with this reason code. The resource name is
contains this reason code, is issued to the console. also given. GRECP page sets or partitions remain
unavailable until recovery against the affected page
Problem determination set or partition is complete.

and reporting the problem, see Collecting diagnostic Use the START DATABASE command with the ACCESS
data (Collecting data). RW option to recover the page set or partition and
remove the GRECP status. In extreme or unusual
00C20208 circumstances, you can also remove GRECP status as
follows:

• RECOVER, either to currency, or to a prior point in z/OS MVS Sysplex Services Reference for the MVS
time IXLCACHE reason code.
• REPAIR SET with NORCVRPEND If you suspect an error in Db2, you might need to
• LOAD REPLACE report the problem. For information about identifying
• START DATABASE with ACCESS FORCE (Not
recommended. Specifying this option can result in
inconsistent data.) 00C20221

Contact the system programmer to determine when While accessing a group buffer pool, Db2 received
the resource will be available for use. an unexpected error from MVS, which detected an
invalid parameter on an IXLCACHE request from Db2.
00C20211
This code usually indicates a Db2 internal problem.
However, the problem can result from errors in other
Explanation products.
Db2 is unable to access a group buffer pool because
the group buffer pool is rebuilding, and the attempt to System action
access the group buffer pool timed out waiting for the
The requesting execution unit abends.
rebuild to complete.

The IXLCACHE reason code saved in register 8 can
'Resource not available' return and reason codes are
help determine the cause of the error. Refer to
sent back to the requesting function.
z/OS MVS Sysplex Services Reference for the MVS
IXLCACHE reason code.
Use the Db2 DISPLAY GROUPBUFFERPOOL command report the problem. For information about identifying
or the MVS D XCF,STR command to monitor the and reporting the problem, see Collecting diagnostic
status of the rebuild. Also, monitor the status data (Collecting data).
messages that the Db2 members issue as the rebuild
progresses (refer to messages DSNB331I, DSNB332I, 00C20222
and DSNB338I). If the rebuild is not progressing
satisfactorally, you can use the MVS command Explanation
SETXCF,STOP,REBUILD to stop the rebuild.
While accessing a page in a buffer pool, Db2 received
an unexpected error from MVS, which detected an
User response invalid parameter on an IXLVECTR request from Db2.
Resubmit the request. This code usually indicates a Db2 internal problem.
However, the problem can result from errors in other
00C20220 products.

While Db2 was accessing a group buffer pool, MVS The requesting execution unit abends.
detected an environmental error during an IXLCACHE
request from Db2.
System action See the IXLVECTR return code in register 8 to help
determine the cause of the error. Refer to z/OS MVS
The requesting execution unit abends. Sysplex Services Reference for the MVS IXLVECTR
reason code.
Problem determination If you suspect an error in Db2, you might need to
The IXLCACHE reason code saved in register 8 can report the problem. For information about identifying
help determine the cause of the error. Refer to

While accessing a group buffer pool, Db2 received an
00C20223 unexpected error from z/OS MVS, which detected an
invalid parameter in an IXLAXISN request from Db2.
Explanation This code usually indicates that there is an internal
error in Db2. However, the problem might result from
Db2 encountered an error while invoking the an error in another product.
IXLCACHE macro.
System action
System action
The requesting execution unit abnormally terminates.
The requesting execution unit abends. Db2 terminates
abnormally causing MVS to reset the castout locks. System programmer response:
Use the IXLAXISN reason code, which is saved in
register 8, to help you to determine the cause of the
Problem determination error.
report the problem. For information about identifying Problem determination
data (Collecting data). Refer to z/OS MVS Sysplex Services Reference for
information about IXLAXISN reason codes.
00C20224
Db2 received an unexpected return and reason code data (Collecting data).
from the MVS IXLFCOMP macro for a group buffer 00C20230
pool.
Explanation
System action
Db2 could not establish duplexing for a group buffer
Db2 abends the agent and requests a dump. If the pool because a coupling facility with CFLEVEL = 5
group buffer pool is in duplex mode, then Db2 may functionality was not available in which to allocate the
stop duplexing for the group buffer pool in response to secondary group buffer pool.
this error.
System action
The group buffer pool is entered back into simplex
If the group buffer pool was duplexed and is entered mode. Message DSNB741I is issued indicating the
back into simplex mode as a result of this error, and reason code as the reason why the process to
duplexing is not automatically reestablished, then use establish duplexing failed.
the MVS SETXCF command to enter the group buffer
pool back into duplex mode if duplexing is needed.
If DUPLEX(ENABLED) is specified in the active CFRM System programmer response
policy for the group buffer pool, then the system Upgrade the coupling facilities to CFLEVER = 5
attempts to automatically reestablish duplexing for the or above. Or change the PREFLIST for the group
structure. buffer pool to name only coupling facilities that have
CFLEVER = 5 functionality.
Problem determination 00C20231
See z/OS MVS Sysplex Services Reference for an
explanation of the MVS IXLREBLD reason code. Explanation
If you suspect an error in Db2, you might need to Db2 could not establish duplexing for a group buffer
report the problem. For information about identifying pool because the primary structure instance of that
and reporting the problem, see Collecting diagnostic group buffer pool is allocated in a coupling facility that
data (Collecting data). does not have CFLEVEL = 5 functionality.
00C20225

The group buffer pool is entered back into simplex If duplexing is needed for the group buffer pool and
mode. Message DSNB741I is issued indicating the duplexing is not automatically reinitiated, then use the
reason code as the reason why the process to MVS SETXCF command to initiate duplexing for the
establish duplexing failed. group buffer pool.
00C20250
Upgrade the coupling facilities to CFLEVER = 5 Explanation
or above. Or change the PREFLIST for the group
buffer pool to name only coupling facilities that have A conditional pageset P-lock request failed.
CFLEVER = 5 functionality.
User response
00C20232
Contact IBM Software Support.
Db2 could not establish duplexing for a group buffer
pool because the group buffer pool is defined with Explanation
GBPCACHE(NO). Db2 does not allow GBPCACHE(NO)
Db2 is unable to obtain a physical lock (P-lock)
group buffer pools to be duplexed.
because of an out-of-storage condition detected by
IRLM.
System action
The group buffer pool is entered back into simplex System action
mode. Message DSNB741I is issued indicating the
SQLCODE -904 is returned to the user with this reason
reason code as the reason why the process to
code. This reason code and the resource name are
establish duplexing failed.
returned in the cursor table (CT) and made available to
the user in the SQLCA.
If duplexing is needed for the group buffer pool, Operator response
issue the Db2 ALTER GROUPBUFFERPOOL command
to specify GBPCACHE(YES) before trying to initiate
duplexing.
00C20233
IRLM exhausted the amount of virtual storage
available to it to represent locks. Refer to code
Explanation
00C90092 for methods to reduce the storage needed
Db2 detected a version id mismatch for the secondary by IRLM.
group buffer pool when connecting to a duplexing
group buffer pool. The version ID mismatch indicates
that the process to establish duplexing completed 00C20252
prematurely (for example due to a system failure), and
the secondary group buffer pool is not in synch with Explanation
the primary.
Db2 is unable to obtain a physical lock (P-lock).
Another Db2 holds the P-lock in an incompatible state,
System action
but is unable to downgrade because it does not have
Db2 stops duplexing for the group buffer pool. The access to the corresponding group buffer pool.
group buffer pool is entered back into simplex mode.
Message DSNB743I is issued indicating the reason System action
code as the reason why the process to establish
duplexing was stopped. If DUPLEX(AUTO) is specified SQLCODE -904 (resource not available) is returned to
for the group buffer pool in the active CFRM policy, the user. The other Db2 produces additional diagnostic
then duplexing is automatically reinitiated. information in the form of messages, trace records,
SYS1.LOGREC entries, and/or an SVC dump. This

reason code and the resource name are returned in 00C20256
the cursor table (CT) and made available to the user in
the SQLCA.
Explanation
Db2 is unable to obtain a physical lock (P-lock). This is
00C20254 a Db2 internal error.

Db2 is unable to acquire or upgrade a physical lock SQLCODE -904 (resource not available) is returned to
(P-lock) because of an incompatible retained lock held the user. This reason code and the resource name are
by one or more other Db2 subsystems in the Db2 data returned in the cursor table (CT) and made available
sharing group. Retained locks are locks that persist to the user in the SQLCA. The other Db2 produces
across Db2 abnormal terminations. SYS1.LOGREC entries, and, depending on the type of
abend, might also produce an SVC dump.
System action
SQLCODE -904 is returned to the user. This reason
code and the resource name are returned in the cursor If you suspect an error in Db2, you might need to
table (CT) and made available to the user in the report the problem. For information about identifying
SQLCA. and reporting the problem, see Collecting diagnostic
System programmer response 00C20257
Use the -DISPLAY DATABASE command to display
the Db2 member names owning the retained locks. Explanation
You must restart those subsystems to remove the
'resource unavailable' condition. To show the status Db2 is unable to obtain a physical lock (P-lock)
of the DBMS and IRLM subsystems, you can use the because of an 'out of record list storage' condition
following command: that IRLM detected. The record list is that part of
the coupling facility lock structure that IRLM uses
F irlmproc,STATUS,ALLD to record 'modify locks' (those locks that would be
retained in case of a failure).
00C20255
System action
Explanation SQLCODE -904 is returned to the user with this reason
Db2 is unable to obtain a physical lock (P-lock) code. This reason code and the resource name are
because another member holding the lock has not returned in the cursor table (CT) and made available to
responded to the P-lock request. This is a Db2 internal the user in the SQLCA.
error.
System action Allocate a larger coupling facility lock structure by
SQLCODE -904 (resource not available) is returned to using the MVS SETXCF,REBUILD command. Make
the user. This reason code and the resource name sure that the active MVS CFRM policy specifies
are returned in the cursor table (CT) and made a larger structure size for the IRLM coupling
available to the user in the SQLCA. The other Db2 facility lock structure before you initiate the rebuild.
produces additional diagnostic information in the form You can use the MVS SETXCF,STOP,POLICY and
of messages, trace records, SYS1.LOGREC entries SETXCF,START,POLICY commands to change the
and/or an SVC dump. active MVS CFRM policy. If lock size is not
already at the current POLICY maximum size,
you can increase lock size with the SETXCF
START, ALTER, STRNAME=lock_structure,
If you suspect an error in Db2, you might need to SIZE=new_size command.
00C20258

Explanation messages DSNT376I, DSNT500I, and DSNT501I for
further diagnosis.
Db2 is not able to obtain a physical lock (P-lock) until
a peer member restarts. Another Db2 holds the P-lock
in an incompatible state but cannot downgrade until it Problem determination
completes its restart. If you suspect an error in Db2, you might need to
System action and reporting the problem, see Collecting diagnostic
the user. This reason code and the resource name are 00C2025B
made available to the user in the SQLCA.
Explanation
User response Db2 encountered an unexpected error while trying to
Resubmit the failing application. The P-lock becomes read from the shared communications area (SCA) for
available after the peer member completes its restart MBA (multiple buffer pool) object.
processing.
Problem determination: System action
00C20259 The requesting execution unit abends. A SYS1.LOGREC
entry is written and an SVC dump is requested.
Explanation
This is a Db2 internal error. This reason code and the
group buffer pool name are recorded in the cursor If you suspect an error in Db2, you might need to
table (CT) and made available to the user in the SQLCA report the problem. For information about identifying
or in messages. and reporting the problem, see Collecting diagnostic
System action 00C2025C
Abend status is recorded in SYS1.LOGREC. Explanation
Db2 encountered an unexpected error while trying to
Operator response write to the shared communications area (SCA) for
MBA (multiple buffer pool) object.
System action
System programmer response The requesting execution unit abends. A SYS1.LOGREC
and reporting the problem, see Collecting diagnostic Problem determination
data (Collecting data). If you suspect an error in Db2, you might need to
00C2025A report the problem. For information about identifying
Explanation
00C20260
Db2 encountered an unexpected error from IRLM
while trying to acquire a global lock for MBA (multiple
buffer pool) object. Explanation
This is a Db2 internal error. Castout was unsuccessful
System action because Db2 lost connectivity to the group buffer pool.
The requesting execution unit abends. A SYS1.LOGREC
entry is written and an SVC dump is requested. Collect

A 'resource not available' code is returned to the user. If you suspect an error in Db2, you might need to
System programmer response and reporting the problem, see Collecting diagnostic
Connect this Db2 to the group buffer pool before
allowing operations that reference this group buffer
User response
pool.
User response Problem determination:
Notify the system programmer. 00C20263

If you suspect an error in Db2, you might need to This is a Db2 internal error. Castout was unsuccessful
report the problem. For information about identifying due to an unexpected error.
System action
00C20261 A 'resource not available' code is returned to the user.
An SVC dump and the SYS1.LOGREC recording were
Explanation requested.
This is a Db2 internal error. Castout was unsuccessful
due to a group buffer pool structure failure. System programmer response
System action report the problem. For information about identifying

Connect this Db2 to the group buffer pool before
allowing operations that reference this group buffer
pool. Problem determination:
00C20264
User response
Db2 is unable to acquire or upgrade a physical lock
Problem determination (P-lock) because at least one other Db2 subsystem
in the data sharing group is holding an incompatible
retained lock. The amount of time this Db2 can wait for
a locked resource was exceeded. This reason code is
only issued if the RETLWAIT installation parameter in
DSN6SPRM is set to 'YES'. If RETLWAIT is set to 'NO'
00C20262 (this is the default), then any IRLM lock that conflicts
with a retained lock will not wait, but instead will be
immediately rejected (see reason code 00C20254).
Explanation
This is a Db2 internal error. Castout was unsuccessful System action
due to errors in writing a page to DASD.
An SQLCODE -904, -911 , -913 or -923 is issued,
and message DSNT501I is issued. Also, message
System action
DSNT378I is issued.

System programmer response in System Recover Pending mode. When Db2 is started
in System Recover Pending mode, nothing other than
Refer to the 'System Programmer Response' in the Restore System utility is allowed to access Db2
message DSNT378I. data.
00C20267 System action
The application fails with a "resource unavailable"
Explanation condition.
Db2 is unable to recover GRECP status for a table

space or index because one or more sharing group System programmer response
members could not perform a global drain request on The application cannot be run while Db2 is in System
the object. Recover Pending mode.
00C2026A
System action
A Db2 message of DSNB350 or DSNB351 is issued. Explanation
Db2 is unable to obtain a physical lock (P-lock),
System programmer response because another member holding the lock has been in
Refer to the 'System Programmer Response' in Db2 shutdown mode for an extended amount of time.
message DSNB350 or DSNB351.
System action
User response SQLCODE -904 (resource not available) is returned to
Issue a START DB command to explicitly recover the the user. This reason code, as well as the resource
page set from GRECP/LPL status. name, are returned in the cursor table (CT) and made
available to the user in the SQLCA.
00C20268
Explanation
Check the other members of the data sharing group
Db2 is unable to recover GRECP status for a table to find the one which is stalled in shutdown. If you
space or index because one or more sharing group suspect an error in Db2, you might need to report
members could not perform a global drain request on the problem. For information about identifying and
the object. One or more peer DB2s in the group failed reporting the problem, see Collecting diagnostic data
to drain the object because some error occurred. (Collecting data). Resubmit the failing application after
the member has come down.
System action 00C2026B
A Db2 message of DSNB350 or DSNB351 is issued.
Explanation
System programmer response Db2 is unable to obtain a physical lock (P-lock),
Refer to the 'System Programmer Response' in because another member holding the lock has had
message DSNB350 or DSNB351. logging suspended for an extended amount of time.
The logging has been suspended because the active
logs are full, or because there is an outstanding SET
User response
LOG SUSPEND command.
Issue a START DB command to explicitly recover the
page set from GRECP/LPL status. System action
00C20269 SQLCODE -904 (resource not available) is returned to
the user. This reason code, as well as the resource
Explanation name, are returned in the cursor table (CT) and made
An application or utility is attempting to access Db2
data, but this is not allowed because Db2 was started

Problem determination 2. Convert the objects that are in basic format with
6-byte RBA or LRSN values to extended format with
Check the other members of the data sharing group 10-byte RBA or LRSN values.
to find the one that has logging suspended. Then take
the appropriate action by either issuing the SET LOG 3. Try the update operation again.
RESUME command or freeing up the active log data Related reference
sets. Resubmit the failing application after the logging Syntax and options of the REORG TABLESPACE
situation is resolved. control statement (Db2 Utilities)
00C2026C Syntax and options of the LOAD control
statement (Db2 Utilities)
Explanation Syntax and options of the REBUILD INDEX
control statement (Db2 Utilities)
Db2 is unable to obtain a physical lock (P-lock), Related information
because another member holding the lock has
-904
encountered an abend in its P-lock exit.
System action code, TYPE OF RESOURCE resource-type, AND
the user. This reason code, as well as the resource 00C2026E
name, are returned in the cursor table (CT) and made
available to the user in the SQLCA. The other Db2
produces additional diagnostic information in the form Explanation
of messages, trace records, SYS1.LOGREC entries, or An update to a table or index was not allowed because
an SVC dump. the object is in basic format with 6-byte RBA or LRSN
values, and the RBA or LRSN that is required for the
Problem determination update is near the end of the 6-byte range. Rollback
and abort processing are not allowed. This reason
Collect the SYS1.LOGREC and SVC dump, if available, code is typically associated with a -904 SQLCODE.
from the other Db2. If the problem persists, it might be
necessary to recycle this member to resolve the P-lock
failure. System action
00C2026D The requested update fails. Previous uncommitted
changes can be committed. No additional changes are
allowed.
Explanation
An update to a table or index was not allowed because User response
the object is in basic format with 6-byte RBA or LRSN
values, and the RBA or LRSN that is required for the You must convert the object that is in basic format with
update is near the end of the 6-byte range. Rollback 6-byte RBA or LRSN values to extended format with
and abort processing are still allowed. This reason 10-byte RBA or LRSN values before it can be updated.
code is typically associated with a -904 SQLCODE. Related reference
Syntax and options of the REORG TABLESPACE
System action control statement (Db2 Utilities)
The requested update failed. Previous uncommitted Syntax and options of the LOAD control
changes can be committed. No additional changes are statement (Db2 Utilities)
allowed. Syntax and options of the REBUILD INDEX
control statement (Db2 Utilities)
User response Related information
-904
Take the following actions: UNSUCCESSFUL EXECUTION CAUSED BY AN
1. Ensure that all catalog and directory page sets have UNAVAILABLE RESOURCE. REASON reason-
been converted to extended format. code, TYPE OF RESOURCE resource-type, AND
00C202A1

Db2 encountered an unexpected error while trying to Refer to z/OS MVS Sysplex Services Reference for the
read from or write to the shared communications area MVS IXLFORCE reason code.
(SCA).
System action
The requesting execution unit abends. A SYS1.LOGREC report the problem. For information about identifying
entry is written and an SVC dump is requested. and reporting the problem, see Collecting diagnostic
Problem determination 00C202A4
data (Collecting data). MVS detected an error on an IXLCONN request from
Db2.
00C202A2
System action
Explanation
A SYS1.LOGREC entry is written and an SVC
MVS returned an unexpected error from an IXLDISC dump is requested. Unless already issued, message
request to disconnect a group buffer pool. DSNB301E, which contains this reason code, is issued
to the console. The IXLCONN reason code is saved
System action in register 8 for SYS1.LOGREC recording and the SVC
dump. This reason code and the group buffer pool
The requesting execution unit abends. A SYS1.LOGREC name are returned to the user in the SQLCA.
The IXLDISC reason code is saved in register 8 for
SYS1.LOGREC recording and the SVC dump.
Refer to z/OS MVS Sysplex Services Reference for the
System programmer response MVS IXLCONN reason code.
Refer to z/OS MVS Sysplex Services Reference for the

MVS IXLDISC reason code.
Problem determination report the problem. For information about identifying
If you suspect an error in Db2, you might need to data (Collecting data).
and reporting the problem, see Collecting diagnostic 00C202A5
Explanation
00C202A3
The cache coupling facility structure attributes passed
Explanation back by MVS on an IXLCONN request were incorrect.
MVS returned an unexpected error from an IXLFORCE

System action
request to deallocate a group buffer pool.
A SYS1.LOGREC entry is written. The newly-connected
System action group buffer pool is disconnected.
If this is a non-rebuild connect, then message
A SYS1.LOGREC entry is written and an SVC dump
DSNB301E, which contains this reason code, is issued
is requested. The IXLFORCE reason code is saved in
to the console (unless it has already been issued). In
register 8 for SYS1.LOGREC recording and the SVC
the message this reason code and the group buffer
dump.
pool name are returned to the user in the SQLCA.

If this is a rebuild connect, then message DSNB330E, and reporting the problem, see Collecting diagnostic
which contains this reason code, is issued to the data (Collecting data).
console and this reason code is used to stop the
00C202A7
rebuild.

Check the SYS1.LOGREC variable recording area (VRA) While processing an ALTER GROUPBUFFERPOOL
for which bit is set in "VRARRK30 - Error mask": command request, Db2 encountered an unexpected
return code from the MVS IXCQUERY service.
X'04'
If bit X'04' is set, the number of allocated data
System action
elements was not sufficient to hold a single data
page. VRARRK31 contains the allocated number The requesting execution unit abends. A SYS1.LOGREC
of data elements. The number of required data entry is written. An SVC dump is requested if it
elements depends on the page size of the buffer appears to be a Db2 problem (return code 8 from
pool: IXCQUERY). Command processing is terminated.
Number of data
Page size elements Problem determination
4KB 1 If you suspect an error in Db2, you might need to
8KB 2 and reporting the problem, see Collecting diagnostic
16KB 4
00C202A8
32KB 8
X'10' Explanation
If bit X'10' is set, the allocated vector was not In connection to a group buffer pool structure, Db2
long enough to cover the corresponding buffer determined that insufficient space is allocated to hold
pool. VRARRK31 contains the requested vector any data pages. For example, the group buffer pool
length, and VRARRK32 contains the allocated GBP32K contains only 16 KB or four 4 KB pages, which
vector length. are not large enough to support one 32 KB buffer.
X'20'
If bit X'20' is set, the data element size was not System action
allocated as Db2 requested. VRARRK31 contains
the requested data element size, and VRARRK32 Db2 disconnects from the structure, issues a
contains the allocated data element size. DSNB301E message with this reason code (if not
already issued), and returns this reason code and the
00C202A6
GBP name to the user in the SQLCA. If this is a rebuild
connect, then Db2 issues message DSNB335I, which
Explanation contains this reason code, and this reason code is used
to stop the rebuild.
This is a Db2 internal error. Unless already issued,
message DSNB301E, which contains this reason code,
is issued to the console. System programmer response
Modify the z/OS coupling facility resource
System action management (CFRM) policy to make the group
buffer pool structure larger, or use the -ALTER
A SYS1.LOGREC entry is written and an SVC dump is
GROUPBUFFERPOOL command to reduce the value of
requested. The newly-connected group buffer pool is
the RATIO option to assign more space for data.
disconnected. This reason code and the group buffer
pool name are returned to the user in the SQLCA. Related concepts
Tuning group buffer pools (Db2 Data Sharing
Problem determination Planning and Administration)
Related reference
-ALTER GROUPBUFFERPOOL (Db2) (Db2
Commands)

Related information • RLPRSTAT (1 byte): Requested state of the P-lock by
DSNB301E (Db2 Messages) the other Db2 that is in conflict with the state held by
DSNB335I (Db2 Messages) this Db2
• Unused (1 byte)
00C202AA • RLPWUID (8 bytes): Owning work unit
Explanation 00C202AB
An error occurred in IRLM on a physical lock (P-lock) or

Explanation
change request from Db2. This a Db2 internal error.
The IRLM UNLOCK request returned an error code
System action when Db2 attempted to release a physical lock (P-
lock). This is a Db2 internal error.
A record is written to SYS1.LOGREC and an SVC dump
is requested. SQLCODE -904 is issued. This reason
System action
code and the resource name are returned in the
SQLCA. The requesting execution unit abends. The SVC dump
and SYS1.LOGREC recording are requested.
Examine SYS1.LOGREC for a previous error related to
IRLM. Request the SYS1.LOGREC and the SVC dump.

If you suspect an error in Db2, you might need to Resubmit the failing application.
SYS1.LOGREC contains information in the variable
recording area (VRA) of the system diagnostic work
area (SDWA). Significant fields in the VRA for this code
are: VRARRK13, VRARRK14, VRARRK15, VRARRK30,
and VRARRK33. SYS1.LOGREC contains information in the variable
The information recorded with VRARRK30 is mapped
as follows:
• IRLM return code (4 bytes) and VRARRK33.
• IRLM reason code (4 bytes) The information recorded with VRARRK30 is mapped
• IRLM function code (1 byte) as follows:
• Lock state (1 byte) • IRLM return code (4 bytes)
• Flags from RLPLFLG1 (1 byte) • IRLM reason code (4 bytes)
• Flags from RLPLFLG4 (1 byte) • IRLM function code (1 byte)
• Returned cached state (1 byte) • Lock state (1 byte)
• Unused (1 byte) • Flags from RLPLFLG1 (1 byte)
• P-lock exit reason code (2 bytes) • Flags from RLPLFLG4 (1 byte)
VRARRK33 records information from the RLPPL • Returned cached state (1 byte)
(mapped by DXRRLPPL) and is mapped as follows: • Unused (1 byte)
• RLPHSTAT (1 byte): Current held state of the P-lock • P-lock exit reason code (2 bytes)
by this Db2
VRARRK33 records information from the RLPPL
• RLPCCSTA (1 byte): New cached state of the P-lock (mapped by DXRRLPPL) and is mapped as follows:
for this Db2

• RLPHSTAT (1 byte): Current held state of the P-lock Explanation
by this Db2
Db2 could not start even one castout process. A
• RLPCCSTA (1 byte): New cached state of the P-lock probable cause is that no virtual storage is available
for this Db2 to acquire private buffers for the castout process.
• RLPRSTAT (1 byte): Requested state of the P-lock by
the other Db2 that is in conflict with the state held by
System action
this Db2
• Unused (1 byte) The requesting execution unit abends and Db2
terminates abnormally.
• RLPWUID (8 bytes): Owning work unit
00C202AC System programmer response
Restart Db2 after increasing the REGION parameter
Explanation value on the database services address space
There was an error during physical lock (P-lock) (ssnmDBM1) startup procedure to get more virtual
negotiation. This is a Db2 internal error. storage.
System action 00C202AE
An SVC dump and SYS1.LOGREC recording are
requested. A 'resource unavailable' condition is Explanation
returned to the P-lock requester that caused the
conflict and the subsequent negotiation. IRLM returned an invalid cached state on a physical
lock (P-lock) request from Db2. This is an internal
error.
Request the SYS1.LOGREC and the SVC dump. System action
SQLCODE -904 is issued. A record is written to
Problem determination SYS1.LOGREC and an SVC dump is requested.
report the problem. For information about identifying System programmer response
data (Collecting data). Examine SYS1.LOGREC for a preceding error related to
IRLM.
area (SDWA). Significant fields in the VRA for this Problem determination
code are: VRARRK13, VRARRK14, VRARRK15, and If you suspect an error in Db2, you might need to
VRARRK33. report the problem. For information about identifying
VRARRK33 records information from the RLPPL and reporting the problem, see Collecting diagnostic
(mapped by DXRRLPPL) and is mapped as follows: data (Collecting data).
• RLPHSTAT (1 byte): Current held state of the P-lock SYS1.LOGREC contains information in the variable
by this Db2 recording area (VRA) of the system diagnostic work
• RLPCCSTA (1 byte): New cached state of the P-lock are: VRARRK13, VRARRK14, VRARRK15, VRARRK30,
for this Db2 and VRARRK33.
• RLPRSTAT (1 byte): Requested state of the P-lock by
as follows:
this Db2
• Unused (1 byte) • IRLM return code (4 bytes)
• RLPWUID (8 bytes): Owning work unit • IRLM reason code (4 bytes)
• IRLM function code (1 byte)
00C202AD
• Lock state (1 byte)
• Flags from RLPLFLG1 (1 byte)

• Flags from RLPLFLG4 (1 byte) • RLPRSTAT (1 byte): Requested state of the P-lock by
• Returned cached state (1 byte) the other Db2 that is in conflict with the state held by
this Db2
• Unused (1 byte)
• Unused (1 byte)
• P-lock exit reason code (2 bytes)
• RLPWUID (8 bytes): Owning work unit
(mapped by DXRRLPPL) and is mapped as follows: 00C202B0
• RLPHSTAT (1 byte): Current held state of the P-lock

by this Db2 Explanation
• RLPCCSTA (1 byte): New cached state of the P-lock This is a Db2 internal error.
for this Db2
• RLPRSTAT (1 byte): Requested state of the P-lock by System action
An SVC dump and SYS1.LOGREC recording are
this Db2
requested. A 'resource unavailable' condition is
• Unused (1 byte) returned to the physical lock (P-lock) requester that
• RLPWUID (8 bytes): Owning work unit caused the conflict and the subsequent negotiation.
00C202AF
Explanation Request the SYS1.LOGREC and the SVC dump.
There was an incompatible physical lock (P-lock) held.

This is a Db2 internal error. User response
System action
An SVC dump and SYS1.LOGREC recording are Problem determination
requested. A 'resource unavailable' condition is If you suspect an error in Db2, you might need to
returned to the P-lock requester that caused the report the problem. For information about identifying
conflict and the subsequent negotiation. and reporting the problem, see Collecting diagnostic
System programmer response SYS1.LOGREC contains information in the variable
Request the SYS1.LOGREC and the SVC dump. recording area (VRA) of the system diagnostic work
area (SDWA). Significant fields in the VRA for this
code are: VRARRK13, VRARRK14, VRARRK15, and
Problem determination VRARRK33.
If you suspect an error in Db2, you might need to VRARRK33 records information from the RLPPL
report the problem. For information about identifying (mapped by DXRRLPPL) and is mapped as follows:
data (Collecting data). • RLPHSTAT (1 byte): Current held state of the P-lock
by this Db2
recording area (VRA) of the system diagnostic work • RLPCCSTA (1 byte): New cached state of the P-lock
area (SDWA). Significant fields in the VRA for this for this Db2
code are: VRARRK13, VRARRK14, VRARRK15, and • RLPRSTAT (1 byte): Requested state of the P-lock by
VRARRK33. the other Db2 that is in conflict with the state held by
this Db2
(mapped by DXRRLPPL) and is mapped as follows: • Unused (1 byte)
• RLPHSTAT (1 byte): Current held state of the P-lock • RLPWUID (8 bytes): Owning work unit
by this Db2 00C202B1
• RLPCCSTA (1 byte): New cached state of the P-lock
for this Db2

An error occurred during physical (P-lock) negotiation. Db2 could not obtain a page set or partition physical
This is a Db2 internal error. lock (P-lock).

An SQLCODE -904 is issued. A record is written to A 'resource unavailable' condition is returned to the
SYS1.LOGREC and an SVC dump is requested. This user. This reason code and the resource name are
reason code and the resource name are returned in returned in the cursor table (CT) and made available
the SQLCA. to the user in the SQLCA.

Examine SYS1.LOGREC for a previous error related to This problem might be caused by having multiple Db2
IRLM. release levels in the Db2 data sharing group.

If you suspect an error in Db2, you might need to If you suspect an error in Db2, you might need to
report the problem. For information about identifying report the problem. For information about identifying
and reporting the problem, see Collecting diagnostic and reporting the problem, see Collecting diagnostic
data (Collecting data). data (Collecting data).
SYS1.LOGREC contains information in the variable 00C202B3
Explanation
and VRARRK33. This is a Db2 internal error. The execution unit
encountered an error while doing damage assessment
for a group buffer pool.
as follows:
• IRLM return code (4 bytes)
System action
• IRLM reason code (4 bytes)
• IRLM function code (1 byte)
• Lock state (1 byte) Operator response
• Flags from RLPLFLG1 (1 byte)
• Flags from RLPLFLG4 (1 byte) SYS1.LOGREC, and request the SVC dump.
• Returned cached state (1 byte)
• Unused (1 byte) System programmer response
• P-lock exit reason code (2 bytes) If you suspect an error in Db2, you might need to
VRARRK33 records information from the RLPPL report the problem. For information about identifying
(mapped by DXRRLPPL) and is mapped as follows: and reporting the problem, see Collecting diagnostic
• RLPHSTAT (1 byte): Current held state of the P-lock
by this Db2 00C202B4
• RLPCCSTA (1 byte): New cached state of the P-lock
for this Db2 Explanation
• RLPRSTAT (1 byte): Requested state of the P-lock by This is a Db2 internal error. The execution unit received
the other Db2 that is in conflict with the state held by an error return code while doing damage assessment
this Db2 for a group buffer pool.
• Unused (1 byte)
• RLPWUID (8 bytes): Owning work unit System action
00C202B2 The requesting execution unit is abended.

Operator response 00C202B7
SYS1.LOGREC, and request the SVC dump. Explanation
This is a Db2 internal error. An unexpected error
System programmer response occurred during recovery processing from a group
buffer pool link failure.
and reporting the problem, see Collecting diagnostic System action
data (Collecting data). The requesting execution unit abends. A SYS1.LOGREC
00C202B5 entry is written and an SVC dump is requested.

This is a Db2 internal error. The execution unit received If you suspect an error in Db2, you might need to
an error return code while doing damage assessment report the problem. For information about identifying
for a group buffer pool. and reporting the problem, see Collecting diagnostic
System action 00C202C0
Explanation
Operator response Db2 timed out waiting for the use count on a group
buffer pool to reach zero during rebuild quiesce
Notify the system programmer, print the processing for the group buffer pool. This is a Db2
SYS1.LOGREC, and request the SVC dump. internal problem.
System programmer response System action

If you suspect an error in Db2, you might need to The Db2 system agent that is processing the rebuild
report the problem. For information about identifying abends and takes a dump. The rebuild is stopped.
and reporting the problem, see Collecting diagnostic Message DSNB335I is issued indicating this reason
data (Collecting data). code as the reason why the rebuild stopped.
00C202B6
This is a Db2 internal error. The execution unit received report the problem. For information about identifying
an error return code while trying to translate the Db2 and reporting the problem, see Collecting diagnostic
member name to a member ID. data (Collecting data).
00C202C1
System action
The requesting execution unit is abended. Explanation
Db2 encountered a problem trying to connect to the
Operator response new group buffer pool coupling facility structure while
trying to rebuild the group buffer pool.
System action
System programmer response Depending on the nature of the error, a dump might be
generated. The rebuild is stopped. Message DSNB335I
is issued indicating this reason code as the reason why
the rebuild stopped.

User response IXLEERSP request failed and message DSNB335I is
issued indicating this reason code as the reason why
Check the console log for previous error messages (for the rebuild stopped.
example, DSNB330I or DSNB306I) to determine why
Db2 could not connect to the new group buffer pool
structure. Problem determination
Problem determination explanation of the MVS IXLEERSP reason code.
Related information 00C202C4

DSNB330I (Db2 Messages) Explanation
DSNB335I (Db2 Messages) Db2 detected that the number of changed pages in the
new structure is greater than the number of changed
00C202C2 pages in the original structure at the time that the
rebuild of the group buffer pool was about to be
Explanation completed.
Db2 received an unexpected return and reason
code from the MVS IXLREBLD macro during rebuild System action
processing for a group buffer pool. Db2 abends and takes a dump. The rebuild is stopped.
Message DSNB335I is issued indicating this reason
System action code as the reason why the rebuild stopped.
The Db2 system agent that is processing the rebuild
abends and takes a dump. The rebuild is stopped. Problem determination
Message DSNB340I will be issued indicating that the If you suspect an error in Db2, you might need to
IXLREBLD request failed and message DSNB335I is report the problem. For information about identifying
issued indicating this reason code as the reason why and reporting the problem, see Collecting diagnostic
the rebuild stopped. data (Collecting data).
Problem determination 00C202C5

Explanation
explanation of the MVS IXLREBLD reason code.
During a cold start of a member of a data sharing
group, Db2 performed a query for retained locks
in order to determine whether a group buffer pool
needed to be forced off, but the query failed.
00C202C3 System action
Db2 abends and takes a dump. The Db2 subsystem is
Explanation abnormally terminated.
Db2 received an unexpected return and reason
code from the MVS IXLEERSP macro during rebuild Operator response
processing for a group buffer pool.
System action
The Db2 system agent that is processing the rebuild
abends and takes a dump. The rebuild is stopped.
Message DSNB340I is issued indicating that the

If you suspect an error in Db2, you might need to An attempt was made to cold-start a member of a
report the problem. For information about identifying data sharing group, but another member had an active
and reporting the problem, see Collecting diagnostic connection to a group buffer pool.
00C202D0 System action
The Db2 subsystem is abnormally terminated.
Explanation
Db2 is unable to respond to an event that was reported Operator response
by MVS. This is a Db2 internal error. Make sure that all other members of the group have
been shut down, and restart the failing member.
System action
00C20300
Db2 terminates abnormally.
Explanation
Operator response
This is a Db2 internal error. The execution unit
Notify the system programmer, print the attempted to access, claim, or drain a page set or
SYS1.LOGREC, and request the SVC dump. Restart partition, but the page set was not logically opened.
Db2.
System action
report the problem. For information about identifying Operator response
data (Collecting data). Notify the system programmer, print the
00C202D1

Explanation
This is a Db2 internal error. Db2 encountered an report the problem. For information about identifying
unrecoverable error while trying to add a page to the and reporting the problem, see Collecting diagnostic
logical page list (LPL). data (Collecting data).
00C20301
System action
The Db2 subsystem is abnormally terminated. Explanation
This is a Db2 internal error. The execution unit
Operator response
attempted to access, claim, or drain a logical partition,
Notify the system programmer, print SYS1.LOGREC, but the page set is not a type 2 nonpartitioned page
and request an SVC dump. set.

If you suspect an error in Db2, you might need to The requesting execution unit is abended.
and reporting the problem, see Collecting diagnostic Operator response
00C202D2 SYS1.LOGREC, and request the SVC dump.

Problem determination and reporting the problem, see Collecting diagnostic
report the problem. For information about identifying 00C20304
00C20302 This is a Db2 internal error. During force write
processing, the buffer manager detected that the write
Explanation claim class count is not zero or there are pending
updates on the page set or partition.
This is a Db2 internal error. A page set was not logically
opened by the execution unit that was attempting to
do one of the following: System action
• Logical close a page set The requesting execution unit is abended.
• Physical close a page set or partition
Operator response
System action Notify the system programmer, print the

Operator response
Notify the system programmer, print the report the problem. For information about identifying
SYS1.LOGREC, and request the SVC dump. and reporting the problem, see Collecting diagnostic
00C20305
Explanation
data (Collecting data). This is a Db2 internal error. The execution unit
attempted to access, claim, drain, open, or close a
00C20303 partition or piece, but the partition or piece number is
invalid.
Explanation
This is a Db2 internal error. A page set is not in-use, System action
but an execution unit was attempting to do one of the The requesting execution unit is abended.
following:
• Logical close a page set Operator response
• Physical close a page set or partition
System action
The requesting execution unit is abended. System programmer response
Operator response report the problem. For information about identifying
SYS1.LOGREC, and request the SVC dump. data (Collecting data).
00C20306
report the problem. For information about identifying This is a Db2 internal error.

The requesting execution unit is abended. If you suspect an error in Db2, you might need to
Operator response and reporting the problem, see Collecting diagnostic
Notify the system programmer, print SYS1.LOGREC,
User response
Problem determination Notify the system programmer.

and reporting the problem, see Collecting diagnostic Collect the following diagnostic items:
00C20307 was run, and a listing of the SYSLOG data set for the
Explanation • Dynamic dump, taken to SYS1.DUMPxx data set, by
This is a Db2 internal error.
executing IFCEREP1.
System action
00C2030C
Explanation
Operator response
Db2 could not open a data set because of a z/OS
Notify the system programmer, print SYS1.LOGREC, Global Resource Serialization (GRS) resource shortage.
System action
SQLCODE -904 is returned to the user, and the data
If you suspect an error in Db2, you might need to set is not opened. This reason code and the data
report the problem. For information about identifying set name are recorded in the SQLCA. An SVC dump
and reporting the problem, see Collecting diagnostic is not generated, and no information is recorded in
data (Collecting data). SYS1.LOGREC.
00C2030B
Explanation Work with your Db2 administrator to reduce the Db2
z/OS Global Resource Serialization (GRS) service workload, or reduce the number of open data sets.
ISGQUERY or ISGADMIN reported an error when Db2
opened or closed a data set. User response
System action
Related information
The requesting execution unit terminates abnormally. -904
Operator response UNAVAILABLE RESOURCE. REASON reason-
Notify the system programmer, print the RESOURCE NAME resource-name
SYS1.LOGREC, and request an SVC dump.

Reason code identifiers that begin with 00C5 communicate normal and error situations with the TSO
attachment facility.
For these codes, the standard documentation to be collected is a SYSUDUMP and a printout of the
DSNTRACE data set. The standard SPUFI documentation is a SYSUDUMP and a printout of the ISPF log
for this session. A SYSUDUMP data set must be allocated in advance to collect your dump. A DSNTRACE
data set must be allocated in advance to collect your DSN trace stream unless you are running in the
background, in which case the SYSTSPRT data set contains the DSNTRACE output. ISPF normally runs
with an active log data set. ISPF suppresses dumps unless it is invoked with the TEST parameter. If you
suspect an error in Db2, you might need to report the problem. For information about identifying and
reporting the problem, see Collecting diagnostic data (Collecting data).
In the TSO attachment facility, the user can control whether or not message IDs are displayed. To see
them, type PROFILE MSGID. To suppress them, type PROFILE NOMSGID.
The following abends can occur in the TSO Attachment Facility.
00C50001 the SQLTYPE field of the SQLDA. This suggests that an
illegal value was in the SQLTYPE field of the SQLDA.
Explanation
This is probably a Db2 subsystem error. DSNESM30
has detected an illegal value in the YTYPE portion of The standard SPUFI documentation should be
the SQLTYPE field of the SQLDA. collected. Refer to Chapter 5, “X'C5......' codes,” on
page 447 for information about obtaining dumps and
displaying message IDs.
The standard SPUFI documentation should be User response
collected. Refer to Chapter 5, “X'C5......' codes,” on
page 447 for information about obtaining dumps and If the problem persists, notify the system programmer.
User response An illegal value was detected in the YTYPE of the
If the problem persists, notify the system programmer. SQLDA. This may have been caused by this field being
overlaid in error. Analyze the SQLDA in the storage
dump to determine the source of the error.
An illegal value was detected in the SQLTYPE field of
the SQLDA. This may have been caused by this field • SYSABEND, SYSUDUMP, or SYSMDUMP output.
being overlaid in error. To determine the source of the • Listing of the ISPF log for the session involved in the
error, analyze the SQLDA in the storage dump. problem.
Collect the following diagnostic items: 00C50003
• SYSABEND, SYSUDUMP, or SYSMDUMP output.
• Listing of the ISPF log for the session involved in the Explanation
problem.
This could be either a user or a system error.
00C50002 SPUFI was unable to obtain the required storage via
GETMAIN.
Explanation
System action
This is probably a Db2 subsystem error. DSNESM32
has detected an illegal value in the YTYPE portion of SPUFI task abends. User returns to ISPF main menu.

System programmer response • Listing of the ISPF log for the session involved in the
problem.
If the problem persists, the standard SPUFI
documentation should be collected. Refer to Chapter 00C50007
5, “X'C5......' codes,” on page 447 for information about
obtaining dumps and displaying message IDs. Explanation
This is probably an error in the SPUFI code. The field
User response describing the record format of the output data set is
If the problem persists, notify the system programmer. not valid.
You may have to specify a larger machine size at logon
time. System action
The contents of the field are written to the ISPF log.
Register 2 contains the amount of storage that was System programmer response
requested. Message DSNE392E, in the ISPF log data
set, gives the name of the module that issued this The standard SPUFI documentation should be
abend. collected. Refer to Chapter 5, “X'C5......' codes,” on
Collect the following diagnostic items: displaying message IDs.
• Listing of the ISPF log for the session involved in the User response
problem.
If the problem persists, notify the system programmer.
00C50005
Explanation Message DSNE383A, in the ISPF log data set, gives
This could be either a user or a system error. The the record format of the output data set that was
DYNALLOC SVC returned an unexpected return code determined to be in error. The output data set record
when attempting to allocate a data set. must be in one of the following formats: F, FB, FBA, V,
VB, or VBA.
System action Collect the following diagnostic items:
The contents of the field are written to the ISPF log. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• Listing of the ISPF log for the session involved in the
System programmer response problem.
The standard SPUFI documentation should be 00C50008

collected. Refer to Chapter 5, “X'C5......' codes,” on
page 447 for information about obtaining dumps and Explanation
This could be either a user or a system error. The
DYNALLOC SVC returned an unexpected return code
User response when attempting to deallocate a data set.
System action
Problem determination The contents of the field are written to the ISPF log
Message DSNE381E, in the ISPF log data set, gives the
return code and reason code values returned from the System programmer response
dynamic allocation request. Refer to the appropriate
MVS publication to determine the source of the error The standard SPUFI documentation should be
and analyze these values. collected. Refer to Chapter 5, “X'C5......' codes,” on
Collect the following diagnostic items: displaying message IDs.

User response Collect the following diagnostic items:
If the problem persists, notify the system programmer. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• Listing of the ISPF log for the session involved in the
Problem determination problem.
Message DSNE384E, in the ISPF log data set, gives 00C50100

the return code and reason code values returned from
the dynamic allocation request. Analyze these values Explanation
to determine the source of the error.
This is probably caused by an error in the DSN
Collect the following diagnostic items: command processor code. Module DSNECP66 (in the
• SYSABEND, SYSUDUMP, or SYSMDUMP output. DSN command processor) called module DSNTIAR to
format an error message to explain an unexpected SQL
• Listing of the ISPF log for the session involved in the return code received by DCLGEN. DSNTIAR failed.
problem.
00C50009 System programmer response
The standard documentation should be collected,
Explanation including a DSN trace stream. Refer to Chapter 5,
This is probably caused by an error in the SPUFI code. “X'C5......' codes,” on page 447 for information about
The SQLCODE translation service (module DSNTIAR) obtaining dumps and displaying message IDs.
has returned an unexpected return code.
User response
System action If the problem persists, notify the system programmer.
The contents of the field have been written to the ISPF
log. Problem determination
Message DSNE004E in the output gives the return
System programmer response code value returned from DSNTIAR. For an explanation
The standard SPUFI documentation should be of these return codes, see abend reason code
collected. Refer to Chapter 5, “X'C5......' codes,” on '00C50009'.
page 447 for information about obtaining dumps and Collect the following diagnostic items:
User response • Listing of the DSNTRACE data set for the DSN (TSO
attachment facility) session involved in the problem.
00C50101
Explanation
Message DSNE387A, in the ISPF log data set, gives
the return code value returned from DSNTIAR. The The user has entered the ABEND subcommand of
meanings of these return codes are: the DSN command processor. This causes a X'04E'
abend and a dump to be requested. In order to
4 retain the dump, you must have previously allocated
More data was available than could fit into the a SYSUDUMP or SYSADUMP data set. The ABEND
message area provided. subcommand can be useful for debugging.
8
Important: The ABEND subcommand is used for
The LRECL was not within the limits: 72 ≥ LRECL≤
diagnostic purposes only, and is intended to be used
240
only under the direction of IBM Support. Use it only
12 when diagnosing a problem with DSN or Db2.
The message area was not large enough. Message
length ≥ 240
System action
16
Error in message routine (IKJEFF02). A X'04E' abend results, and a dump is requested.

System programmer response • SYSABEND, SYSUDUMP, or SYSMDUMP output.
The standard documentation may be needed. Refer • Listing of the DSNTRACE data set for the DSN (TSO
to Chapter 5, “X'C5......' codes,” on page 447 for attachment facility) session involved in the problem.
information about obtaining dumps and displaying 00C50103
message IDs.
Explanation
An error probably occurred in Db2 while it attempted
Collect the following diagnostic items: to process an ESTABLISH EXIT request from the DSN
• SYSABEND, SYSUDUMP, or SYSMDUMP output. command processor. DSN received an unexpected
return code (FRBRC1 or FRBRC2) from Db2.
• Listing of the DSNTRACE data set for the DSN (TSO
System action
Related tasks
ABEND subcommand of the DSN command Immediately after writing this message, DSN abends
processor (Diagnosing Db2 problems) with an abend code of X'04E' and an abend reason
code of '00C50103'.
Related reference
ABEND (DSN) (Db2 Commands)
DSN (TSO) (Db2 Commands)
Printing and analyzing dumps (Diagnosing Db2 See the Problem Determination section of this
problems) message.
00C50102
User response
Explanation If the problem persists, notify the system programmer.

to process an IDENTIFY request from the DSN
command processor. DSN received an unexpected Rerun the job with DSN tracing turned on. You may
return code (FRBRC1 or FRBRC2) from Db2. need a SYSUDUMP from the TSO address space.
You probably need a Db2 dump. If you suspect an
System action error in Db2, you might need to report the problem.
For information about identifying and reporting the
Immediately after writing this message, DSN abends problem, see Collecting diagnostic data (Collecting
with an abend code of X'04E' and an abend reason data).
code of '00C50102'.

See the Problem Determination section of this attachment facility) session involved in the problem.
message.
00C50104
User response
Explanation
Problem determination to process a CREATE THREAD request from the DSN
command processor. DSN received an unexpected
Rerun the job with DSN tracing turned on. You may return code (FRBRC1 or FRBRC2) from Db2.
need a SYSUDUMP from the TSO address space.
System action
For information about identifying and reporting the Immediately after writing this message, DSN abends
problem, see Collecting diagnostic data (Collecting with an abend code of X'04E' and an abend reason
data). code of '00C50104'.

See the Problem Determination section of this • SYSABEND, SYSUDUMP, or SYSMDUMP output.
message. • Listing of the DSNTRACE data set for the DSN (TSO
User response 00C50109
Explanation
Problem determination An error probably occurred in Db2 while it attempted
Rerun the job with DSN tracing turned on. You may to process a TERMINATE request from the DSN
need a SYSUDUMP from the TSO address space. command processor. DSN received an unexpected
You probably need a Db2 dump. If you suspect an return code (FRBRC1 or FRBRC2) from Db2.
For information about identifying and reporting the System action
data). Immediately after writing this message, DSN abends
with an abend code of X'04E' and an abend reason
Collect the following diagnostic items: code of '00C50109'.
• Listing of the DSNTRACE data set for the DSN (TSO System programmer response
attachment facility) session involved in the problem. See the Problem Determination section of this
00C50108 message.

An error probably occurred in Db2 while it attempted If the problem persists, notify the system programmer.
to process a BIND, REBIND, or FREE request from
the DSN command processor. DSN received an Problem determination
unexpected return code (FRBRC1 or FRBRC2) from
Db2. Rerun the job with DSN tracing turned on. You may
need a SYSUDUMP from the TSO address space.
Immediately after writing this message, DSN abends For information about identifying and reporting the
with an abend code of X'04E' and an abend reason problem, see Collecting diagnostic data (Collecting
code of '00C50108'. data).
See the Problem Determination section of this • Listing of the DSNTRACE data set for the DSN (TSO
message. attachment facility) session involved in the problem.
00C50110
User response
If the problem persists, notify the system programmer. Explanation
This is a DSN command processor error. It occurs
Problem determination when the DSN STAX routine (DSNEBP01) is entered
Rerun the job with DSN tracing turned on. You may and the DSN control blocks cannot be located; the
need a SYSUDUMP from the TSO address space. AEPLUSR field did not contain the CIB address.
error in Db2, you might need to report the problem. System action
problem, see Collecting diagnostic data (Collecting The DSN command processor abended.
data).

If you allocated a SYSUDUMP or SYSABEND dump data Control returns to the application. Your application
set, collect the dump. Otherwise, allocate SYSUDUMP can continue processing. Further attempts at
and DSNTRACE data sets, turn on DSN tracing, and try instrumentation facility interface (IFI) calls will
to re-create the error. Save these data sets. continue to produce this return and reason code.
Severity Operator response

4 Notify your system programmer.
00C50111
Explanation Modify the job to invoke DSN. Initiate the application
program using the RUN subcommand of the DSN
Your application program made an instrumentation command processor.
facility component application program interface
(instrumentation facility interface) call to Db2
language interface module DSNELI, but your User response
application program was not running under the DSN Rerun your application under the DSN command
command processor. You must run all application processor.
programs using DSNELI under DSN. To do this, first
issue the DSN command, then start your application
using the RUN subcommand of the DSN command
processor, and finally, when the application completes,
stop DSN with an END subcommand.

Reason code identifiers that begin with 00C6 communicate normal and error situations with the message
generator.
00C60001
Explanation
Db2 received return code X'20' when issuing a WTO request to display a Db2 console message. MVS sets this
return code when there are no message buffers for either Multiple Console Support (MCS) or JES3, or when
there is a JES3 WTO staging area excess. The WTO request is terminated. The current Db2 console message and
all subsequent Db2 informational console messages are ignored until the MVS problem is corrected.
At the time of the abend, general register zero contains the return code from WTO request.
System action
A record is written to SYS1.LOGREC. A retry is requested and execution continues. Db2 resumes issuing console
messages when the condition is corrected.

Reason code identifiers that begin with 00C8 communicate normal and error situations with the Db2
precompiler or the Db2 coprocessor.
Abends in the precompiler are not intercepted via ESTAE, so standard system abends might occur. The
SYNAD exit is not used, so I/O errors cause S001 or S002 abends. S04E abends are generated for
precompiler internal errors. Following is a list of reason codes.
00C89011 Explanation
An internal precompiler or parser consistency check
Explanation failed. An error occurred in storage suballocation
An internal parser consistency check failed. The parser request. Possible causes for this error include:
received a token code of 0 from a lexical scan. A lexical • Storage constraints when building the DBRM entry
scan refers to a scan of words rather than syntax. for the SQL statement
• An SQL statement exceeding the Db2 maximum
System action statement length.
An S04E abend is generated. The error type and
reason code are found in register 15 of the dump. System action
System programmer response reason code are found in register 15 of the dump.
Obtain the SVC dump and a copy of the application
program source. System programmer response
00C89012 Obtain the SVC dump and a copy of the application
program source.
failed. An error occurred in storage suballocation Explanation
control blocks. This error can be caused by a Db2 SQL
statement exceeding limitations. For example:
failed. The error is in pointer structures.
• An SQL statement might be referencing, creating,
or declaring more columns than the Db2 defined System action
maximum number allowed for an SQL statement.
• Too many host variables might be referenced in an An S04E abend is generated. The error type and
SQL statement. reason code are found in register 15 of the dump.

An S04E abend is generated. The error type and Obtain the SVC dump and a copy of the application
reason code are found in register 15 of the dump. program source.
00C89015
Obtain the SVC dump and a copy of the application Explanation
program source. An internal precompiler or parser consistency check
00C89013 failed. The host variable information in the precompiler
or parser dictionary or in the DBRM is not consistent
with host variable information for an SQL statement.
This error might occur when the precompiler
misinterprets an invalid host variable declaration.

An S04E abend is generated. The error type and Obtain the SVC dump and a copy of the application
reason code are found in register 15 of the dump. program source.
00C89019
Obtain the SVC dump, a copy of the application Explanation
program source, and a copy of the DBRM that is being
bound (IEBCOPY). An internal precompiler or parser consistency check
failed. The internal stack storage is full.
00C89016
System action
Explanation
An internal parser consistency check failed. An reason code are found in register 15 of the dump.
unexpected value was provided for a parser option.
System action
An S04E abend is generated. The error type and program source.
reason code are found in register 15 of the dump.
00C8901a

Explanation
program source. An internal precompiler or parser consistency check
failed. Language Environment required, but not
00C89017 available.

An internal precompiler or parser consistency check An S04E abend is generated. The error type and
failed. The internal limit for a fully qualified name reason code are found in register 15 of the dump.
exceeds the maximum length of 255 characters.
System action
An S04E abend is generated. The error type and program source.
00C89041

Explanation
program source. More storage is needed, but could not be obtained
during the precompiler execution. An S04E abend
00C89018 occurs. The error type and reason code are found in
register 15 of the dump.
Explanation
failed. An internal conversion error occurred during The storage required for the current statement could
conversion of a timestamp version ID. not be acquired or exceeds the maximum (64KB) for
a single request. If the region is full, determine if the
System action region can be expanded. If it cannot be expanded, the
SQL statement is too large to be processed.

Reason code identifiers that begin with 00C9 communicate normal and error situations with the data
manager.
00C9000A System action:
The requested action will not be completed.
Explanation System programmer response:
Verify that the active or archive log data set is not
A resource was unavailable. Some of the
missing by running Print Log Map (DSNJU004) Utility..
circumstances in which this reason code is issued are:
• The Db2 database manager attempted to read the User response
log for a READS request for IFCID 0306. Save one or more of the following items in order to
• Information about the maximum length of LOB determine the possible location of the problem:
column data in the SPT01 directory table space was
• The console log
not available because the Db2 catalog and directory
was undergoing point-in-time recovery. This reason • The job output
code is generated as part of DISPLAY GROUP output.
00C90026

SQLCODE -904 is returned to the user.
This message is used internally to pass back the
condition to RDS and Utilities. This message is an
User response internal reason code. No response is necessary.
If the resource was unavailable when the database 00C90060
manager attempted to read the log for a READS
request for IFCID 0306, reissue the request. If
the problem persists, you might need to report
Explanation
the problem. For information about identifying and On a READS request, the return area supplied was not
reporting the problem, see Collecting diagnostic data large enough to hold one log record. No log record is
(Collecting data). returned, but the position is held in the log.
If the resource was unavailable because information
about the maximum length of LOB column data in System action
the SPT01 directory table space was not available, no
The requested operation (decompression) is not
action is necessary.
performed.
Related information
-904 User response
UNAVAILABLE RESOURCE. REASON reason- Increase the size of the return area.
RESOURCE NAME resource-name Problem determination
00C90015 The system returns the size of the return area that is
required in field IFCABSRQ of the IFCA return area.
A problem with the active or archive log data set
was detected. Problems that result in this message Explanation
include:
On a READS request for IFCID 306, log records are
• The active or archive log data set is not available.
returned, but data is not decompressed as requested.
• An error occurred during log allocation or log data
set open.
• The data set was not cataloged.

Problem determination 00C9006D
See the reason code in field QW0306DG to
determine why decompression was not performed. Explanation
For example, if you receive 00C90064, it means that This code is used internally between components.
the decompression dictionary changed since the log Look for prior abends and messages on the console
record was written. to determine the cause of the problem.
data (Collecting data). Locate the cause of the problem using the system
dump, the LOGREC data set, the console log, or the
00C90064 job output. If you cannot determine the cause of the
problem using these resources, contact an IBM service
Explanation representative.
The decompression dictionary changed since the log

record was written. The log record is returned with User response
compressed data. You need to save one or more of the following items so
that you can determine the location of the problem:
System action • The system dump
The requested operation (decompression) is not • The LOGREC data set
performed. • The console log
• The job output
User response
If you cannot determine the cause of the problem
Specify a valid WQALLRBA value and reissue the by using these resources, consult the system
request. programmer.
00C90070
The specified RBA/LRSN value might be too old. Explanation
00C90067 The Fast Log Apply (FLA) function detected an internal
error within Db2. This error might indicate inconsistent
Explanation data or an error in internal Db2 control structures or
code. Possible causes of this error include:
An attempt was made to add or update a row
in a partitioned table space, but the value of the • The fast log apply child task was interrupted by an
partitioning key is higher than the highest limit for any unexpected error condition.
partition. • An internal abend occurred in the Data Manager
component.
System action • The job or thread was canceled.
The requested action is not performed. When SQL was
involved, SQLCODE -327 is returned to the user. System action
A record is written to SYS1.LOGREC, and an SVC dump
User response is requested.
Correct the SQL. If a REORG job with SHRLEVEL
CHANGE was materializing pending limit key changes Operator response
that reduced the highest limit key for the table, issue
Collect the console output from the system on which
the TERM UTILITY command and resubmit the REORG
the job was run for the period of time spanning
job and specify SHRLEVEL REFERENCE. Alternatively,
the failure. Save this output for use in problem
run REORG and specify SHRLEVEL CHANGE while
determination.
avoiding SQL activity that exceeds the new limit key
values.

Locate the cause of the problem using the system The table space or partition is implicitly stopped
dump, the LOGREC data set, the console log, Db2 logs, by Db2. Messages DSNT501I and DSNI004I are
or the job output. displayed to inform the operator that the dictionary
and the object for which the dictionary is defined are
User response unavailable. An SQLCODE -904 is returned to the SQL
user.
Save one or more of the following items in order to
determine the location of the problem:
Operator response
• system dump
• LOGREC data set
• console log System programmer response
• job output
Correct the problem and inform the user to resubmit
• Db2 logs covering the log apply range the request. If you suspect an error in Db2, you might
• DSN1PRNT of the page in question, if determined or need to report the problem. For information about
all pages of the object being recovered identifying and reporting the problem, see Collecting
00C9007D
00C9007F
Explanation
Explanation
The compression dictionary for the table space or
partition cannot be stored in the table space or The compression dictionary for the table space or
partition. Therefore, the LOAD or REORG utility cannot partition is invalid. Therefore, the table space or
complete successfully. partition cannot be opened.

The table space or partition is implicitly stopped The table space or partition is implicitly stopped
by Db2. Messages DSNT501I and DSNI004I are by Db2. Messages DSNT501I and DSNI004I are
displayed to inform the operator that the dictionary displayed to inform the operator that the dictionary
and the object for which the dictionary is defined are and the object for which the dictionary is defined are
unavailable. An SQLCODE -904 is returned to the SQL unavailable. An SQLCODE -904 is returned to the SQL
user. user.

Notify the system programmer. Notify the system programmer.

Correct the problem and resubmit the LOAD or REORG Recover and start the table space or partition and tell
job. If you suspect an error in Db2, you might need to the user to resubmit the request.
report the problem. For information about identifying 00C90080
Explanation
00C9007E
An attempt was made to allocate a resource for update
operations. However, the resource was already started
Explanation for read-only access.
The compression dictionary for the table space or If the value of the LOAD_RO_OBJECTS subsystem
partition was not successfully retrieved. Therefore, the parameter is YES this reason code is not issued.
data request failed.

The allocation process is not allowed.
Explanation
Operator response An attempt was made to allocate a resource that is
stopped for all access.
If this reason code appears in message DSNT501I,
determine whether the named resource should be
started for read-only access. System action
User response
Determine when the resource is started for read/write Operator response
access, and rerun the job. If this reason code appears in message DSNT500I or
DSNT501I, determine whether the resource should be
Problem determination stopped.
The requested operation is not performed. An If the resource should not be stopped, then use
SQLCODE -904 is issued, and/or message DSNT501I the -START DB db-name SPACENAM space-name
is issued. command to start the object for R/W access.
recording area (VRA) of the system diagnostic work User response
area (SDWA). Significant fields for this code are: Determine when the resource is no longer stopped,
VRARRK13, VRARRK14, and VRARRK15. and rerun the job or resubmit the command.
data (Collecting data). The requested operation is not performed. An
SQLCODE -904 or -923 is issued, and/or message
Collect the following diagnostic items: DSNT500I or message DSNT501I is issued.
• Console output from the system on which the job SYS1.LOGREC contains information in the variable
was run, and a listing of the SYSLOG data set for the recording area (VRA) of the system diagnostic work
period of time that spans the failure. area (SDWA). Significant fields for this code are:
• SVC dump (or system dump), taken to SYS1.DUMPxx VRARRK13, VRARRK14, and VRARRK15.
data set, as result of an operator-initiated dump
command or SLIP trap exit.
• Listing of SYS1.LOGREC data set, obtained by and reporting the problem, see Collecting diagnostic
executing IFCEREP1. data (Collecting data).
• SYSPRINT output, including JCL, for the application Collect the following diagnostic items:
program or batch job, and system messages that
were issued. Make sure that MSGLEVEL=(1,1) on the • Console output from the system on which the job
JOB statement so that all diagnostic information is was run, and a listing of the SYSLOG data set for the
sent to SYSPRINT. period of time that spans the failure.
Related reference • SVC dump (or system dump), taken to SYS1.DUMPxx

LOAD RO OBJECTS field (LOAD_RO_OBJECTS
Migration) • Listing of SYS1.LOGREC data set, obtained by
Related information executing IFCEREP1.
-904 • SYSPRINT output, including JCL, for the application
UNSUCCESSFUL EXECUTION CAUSED BY AN program or batch job, and system messages that
UNAVAILABLE RESOURCE. REASON reason- were issued. Make sure that MSGLEVEL=(1,1) on the
code, TYPE OF RESOURCE resource-type, AND JOB statement so that all diagnostic information is
RESOURCE NAME resource-name sent to SYSPRINT.
DSNT501I (Db2 Messages) Related information
-904

UNSUCCESSFUL EXECUTION CAUSED BY AN • Listing of SYS1.LOGREC data set, obtained by
UNAVAILABLE RESOURCE. REASON reason- executing IFCEREP1.
code, TYPE OF RESOURCE resource-type, AND • SYSPRINT output, including JCL, for the application
RESOURCE NAME resource-name program or batch job, and system messages that
-923 were issued. Make sure that MSGLEVEL=(1,1) on the
CONNECTION NOT ESTABLISHED: DB2 JOB statement so that all diagnostic information is
condition REASON reason-code, TYPE resource- sent to SYSPRINT.
type, NAME resource-name • Copy of the log for this period, so that additional
DSNT500I (Db2 Messages) DSN1LOGP reports can be produced for problem
DSNT501I (Db2 Messages) determination.
Related reference
00C90082 -TERM UTILITY (Db2) (Db2 Commands)
-DISPLAY UTILITY (Db2) (Db2 Commands)
Explanation Related information
An attempt was made to allocate a resource that is -904
already allocated to a Db2 utility function. UNSUCCESSFUL EXECUTION CAUSED BY AN
System action
-923
CONNECTION NOT ESTABLISHED: DB2
User response condition REASON reason-code, TYPE resource-
Determine when the resource is available and rerun
the job. DSNT501I (Db2 Messages)
00C90083
The requested operation is not performed. An Explanation
DSNT501I is issued. The resource allocated to the Db2 An attempt was made to allocate a resource for update
utility function might be either in use by a utility or operations. However, the resource is already allocated
reserved for a utility. If the resource is reserved for a to a Db2 utility function that allows other users to have
utility, but not currently in use, the -DISPLAY UTILITY read-only access.
command will indicate that no utilities are operating
on that object. To access a resource that is reserved System action
for a utility, use the -TERM UTILITY command.
Db2 determines whether there is a utility function that
SYS1.LOGREC contains information in the variable would prohibit allocation of the resource. If it finds
recording area (VRA) of the system diagnostic work an indication of a such a utility, the allocation of the
area (SDWA). Significant fields for this code are: resource is not allowed.
VRARRK13, VRARRK14, and VRARRK15.
If you suspect an error in Db2, you might need to User response
and reporting the problem, see Collecting diagnostic Determine when the resource is no longer restricted by
data (Collecting data). a utility and is started for read/write access, and rerun
the job.
period of time that spans the failure. The requested operation is not performed. An
• SVC dump (or system dump), taken to SYS1.DUMPxx DSNT501I is issued.
command or SLIP trap exit. The resource allocated to the Db2 utility function
might be either in use by a utility or reserved for a
utility. If the resource is reserved for a utility, but not

currently in use, the -DISPLAY UTILITY command will 00C90084
indicate that no utilities are operating on that object.
The -DISPLAY DATABASE command shows which
Explanation
restrictive states Db2 assigned to the resource in
question. Utilities set a restrictive state (for example, Db2 cannot find space for creating a temporary file
UTRO) on the resource that they are processing, and or for inserting data into a temporary file because
then remove this state when the utility successfully the work file database is full. Db2 cannot perform
completes. Therefore, if the -DISPLAY DATABASE the requested actions because of one of the following
command is issued after the successful completion of reasons:
the utility, the restrictive state set by the utility is not
• You are running a large number of concurrent
displayed. To access a resource that is reserved for a
transactions requiring the use of temporary files.
utility, use the -TERM UTILITY command.
• No space is available in any of the table spaces in the
SYS1.LOGREC contains information in the variable work file database.
area (SDWA). Significant fields for this code are: • No space is available for sorting the data.
If you suspect an error in Db2, you might need to System action
report the problem. For information about identifying The reason code appears in a DSNT501I message,
and reporting the problem, see Collecting diagnostic and the requested operation is not performed, and
data (Collecting data). SQLCODE -904 might be issued.
User response
was run, and a listing of the SYSLOG data set for the To resolve the above situation, take one of the
period of time that spans the failure. following actions:
• SVC dump (or system dump), taken to SYS1.DUMPxx • Reduce the number of concurrent transactions.
command or SLIP trap exit. • Increase primary/secondary quantity defined for the
table spaces in the temporary file database.
executing IFCEREP1. • Increase space allocated to temporary file database.
• SYSPRINT output, including JCL, for the application • Limit the amount of temporary storage in the work
program or batch job, and system messages that file database that a single thread can use by setting
were issued. Make sure that MSGLEVEL=(1,1) on the subsystem parameter MAXTEMPS to a non-zero
JOB statement so that all diagnostic information is value.
sent to SYSPRINT. • Enable warnings about excessive agent-level space
• Copy of the log for this period, so that additional usage in the work file database by setting subsystem
DSN1LOGP reports can be produced for problem parameter WFSTGUSE_AGENT_THRESHOLD to a
determination. non-zero value.
Related reference
-TERM UTILITY (Db2) (Db2 Commands)
-DISPLAY UTILITY (Db2) (Db2 Commands) The requested operation is not performed. An
SQLCODE -904 is issued, and/or message DSNT500I
-DISPLAY DATABASE (Db2) (Db2 Commands)
is issued.
Related information
-904 SYS1.LOGREC contains information in the variable
UNSUCCESSFUL EXECUTION CAUSED BY AN recording area (VRA) of the system diagnostic work
UNAVAILABLE RESOURCE. REASON reason- area (SDWA). Significant fields for this code are:
code, TYPE OF RESOURCE resource-type, AND VRARRK13, VRARRK14, and VRARRK15. If you
RESOURCE NAME resource-name suspect an error in Db2, you might need to report
the problem. For information about identifying and
-923 reporting the problem, see Collecting diagnostic data
CONNECTION NOT ESTABLISHED: DB2 (Collecting data).
type, NAME resource-name Collect the following diagnostic items:

• Console output from the system on which the job User response
period of time that spans the failure. To resolve the above situation, do one of the following:
• SVC dump (or system dump), taken to SYS1.DUMPxx • Reduce the number of concurrent transactions.
data set, as result of an operator-initiated dump • Increase primary/secondary quantity defined for the
command or SLIP trap exit. table space(s) in the temporary file database.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • Increase space allocated to temporary file database.
area (SDWA). Significant fields for this code are:
• SYSPRINT output, including JCL, for the application VRARRK13, VRARRK14, and VRARRK15. If you
program or batch job, and system messages that suspect an error in Db2, you might need to report
were issued. Make sure that MSGLEVEL=(1,1) on the the problem. For information about identifying and
JOB statement so that all diagnostic information is reporting the problem, see Collecting diagnostic data
sent to SYSPRINT. (Collecting data).
Related reference Collect the following diagnostic items:
MAX TEMP STG/AGENT field (MAXTEMPS
Migration)
AGENT LEVEL THRESHOLD field
(WFSTGUSE_AGENT_THRESHOLD subsystem • SVC dump (or system dump), taken to SYS1.DUMPxx
parameter) (Db2 Installation and Migration) data set, as result of an operator-initiated dump
Related information
DSNT500I (Db2 Messages) • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
-904 • Source listing of the failing application program.
UNSUCCESSFUL EXECUTION CAUSED BY AN • SYSPRINT output, including JCL, for the application
UNAVAILABLE RESOURCE. REASON reason- program or batch job, and system messages that
code, TYPE OF RESOURCE resource-type, AND were issued. Make sure that MSGLEVEL=(1,1) on the
RESOURCE NAME resource-name JOB statement so that all diagnostic information is
sent to SYSPRINT.
00C90085 • Precompiler listing of failing application program
with SOURCE(YES) and XREF(YES) specified.
Explanation
Related concepts
The limit of 255 extensions for an internal Db2 work Work file database storage requirements (Db2
file has been reached. Installation and Migration)
One of the following situations could be the reason: Related reference
PRIMARY QUANTITY field (PRIQTY subsystem
• Large number of concurrent transactions requiring
parameter) (Db2 Installation and Migration)
use of temporary files.
Related information
• Small primary/secondary quantity defined for table
-904
spaces in temporary file database.
• Inadequate space allocated to temporary file UNAVAILABLE RESOURCE. REASON reason-
database. code, TYPE OF RESOURCE resource-type, AND
System action DSNT500I (Db2 Messages)
The requested operation is not performed. Message DSNT501I (Db2 Messages)
DSNT501I is issued with reason code 00C90085 and
is possibly followed by SQLCODE -904. 00C90086

Explanation CONNECTION NOT ESTABLISHED: DB2
An attempt was made to allocate a resource that is type, NAME resource-name
started for Db2 utility access only.

Explanation
Operator response A page that is marked as 'broken' has been read. The
If this reason code appears in message DSNT501I, database, table space or index space, and the page
determine whether the resource should be started for number are identified in NAME.
utility access only.
System action
User response The data manager function that detected this
Determine when the resource is available for use, and condition returns a 'resource not available' condition
rerun the job. to its invoker. Access to the page is not be permitted
until it is repaired.
User response
The requested operation is not performed. An
SQLCODE -904 or -923 is issued, and/or message If the TYPE is '00000300', examine the name to
DSNT501I is issued. determine if the page is in an index space or a table
space. Use the REPAIR utility to fix the broken page.
VRARRK13, VRARRK14, and VRARRK15. The requested operation is not performed. An
If you suspect an error in Db2, you might need to SQLCODE -904 or -923 is issued, and/or message
report the problem. For information about identifying DSNT500I is issued.
and reporting the problem, see Collecting diagnostic SYS1.LOGREC contains information in the variable
data (Collecting data). recording area (VRA) of the system diagnostic work
Collect the following diagnostic items: area (SDWA). Significant fields for this code are:
VRARRK13, VRARRK14, and VRARRK15. If you
• Console output from the system on which the job suspect an error in Db2, you might need to report
was run, and a listing of the SYSLOG data set for the the problem. For information about identifying and
period of time that spans the failure. reporting the problem, see Collecting diagnostic data
• SVC dump (or system dump), taken to SYS1.DUMPxx (Collecting data).
data set, as result of an operator-initiated dump Collect the following diagnostic items:
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application
• SVC dump (or system dump), taken to SYS1.DUMPxx
were issued. Make sure that MSGLEVEL=(1,1) on the
JOB statement so that all diagnostic information is
sent to SYSPRINT. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Related information
-904
sent to SYSPRINT.
-923

Related reference • IRLM trace output.
REPAIR (Db2 Utilities) • SYSPRINT output, including JCL, for the application
Related information program or batch job, and system messages that
UNSUCCESSFUL EXECUTION CAUSED BY AN JOB statement so that all diagnostic information is
UNAVAILABLE RESOURCE. REASON reason- sent to SYSPRINT.
code, TYPE OF RESOURCE resource-type, AND • Listing of the IRLM procedure.
• Results from SELECT * from SYSIBM.SYSDATABASE.
-923
Related concepts
condition REASON reason-code, TYPE resource- Lock contention, suspension, deadlock, and
type, NAME resource-name timeout (Db2 Performance)
Related tasks
Improving concurrency (Db2 Performance)
00C90088 Related information
Explanation -911
THE CURRENT UNIT OF WORK HAS BEEN
The resource identified by NAME in message ROLLED BACK DUE TO DEADLOCK OR TIMEOUT.
DSNT501I is involved in a deadlock condition. REASON reason-code, TYPE OF RESOURCE
resource-type, AND RESOURCE NAME resource-
System action name
The requested operation is not performed. -913
UNSUCCESSFUL EXECUTION CAUSED BY
DEADLOCK OR TIMEOUT. REASON CODE
System programmer response reason-code, TYPE OF RESOURCE resource-
If the deadlock condition becomes chronic, examine type, AND RESOURCE NAME resource-name
the mix of applications running to determine why the -923
deadlock is occurring. CONNECTION NOT ESTABLISHED: DB2
User response type, NAME resource-name
Rerun the application. 00C90089

The requested operation is not performed. An The environmental descriptor manager (EDM) function
SQLCODE -911, -913, or -923 is issued, and/or of the data manager subcomponent did not have
message DSNT501I is issued. enough storage in its pool or data space to retrieve the
If statistics trace class 3 is active, IFCID 172 contains object. The object can be either a database descriptor
diagnostic information. If you suspect an error in Db2, (DBD), a skeleton cursor table (SKCT), or a skeleton
you might need to report the problem. For information package table (SKPT). The object is identified by a DBD
about identifying and reporting the problem, see ID, SKCT plan name, or SKPT package name.
• Console output from the system on which the job The requested operation is not performed.
• SVC dump (or system dump), taken to SYS1.DUMPxx Invoke the application again. If, after several attempts,
data set, as result of an operator-initiated dump EDM still reports that not enough space is available,
command or SLIP trap exit. take the following actions to reduce EDM storage
• Listing of SYS1.LOGREC data set, obtained by requirements:
executing IFCEREP1.

• Reduce the number of concurrent users that are Related tasks
using Db2. Designing EDM storage space for performance
• Try reducing the number of SQL statements in the (Db2 Performance)
plan or package and rebind. Related reference
• Try to simplify the database design. For example, DSNTIPC: CLIST calculations panel 1 (Db2
reduce the number of partitions in the database. Installation and Migration)
Related information
If EDM storage shortage is a recurring problem, change
the relevant subsystem parameters on installation -904
panel DSNTIPC to increase the EDM pool size UNSUCCESSFUL EXECUTION CAUSED BY AN
definition. Increase the number of concurrent users UNAVAILABLE RESOURCE. REASON reason-
and the number of currently active databases. Then, code, TYPE OF RESOURCE resource-type, AND
restart Db2. RESOURCE NAME resource-name
-923
If a utility that uses a LISTDEF list was run and
that list includes a large number of databases, the
EDM DBD pool might be full. To see the size of each
database DBD, use the DISPLAY DATABASE command.
If the EDM DBD pool is full, decrease the size of your DSNT501I (Db2 Messages)
LISTDEF contents to eliminate this condition. If this
condition occurs frequently, increase the size of your 00C9008A
EDM DBD pool. For guidance, see Calculating EDM
pool sizes (Db2 Installation and Migration). Explanation
The database procedure installation exit identified by
Problem determination NAME could not be loaded for execution.
The requested operation is not performed. One ore
more of the following messages are also issued: System action
• SQLCODE -904 The requested operation is not performed.
• SQLCODE -923
• DSNT500I User response
SYS1.LOGREC contains information in the variable Determine the reason the installation exit could not be
recording area (VRA) of the system diagnostic work loaded, correct the problem, and rerun the job.
area (SDWA). Significant fields for this code are
report the problem. For information about identifying The requested operation is not performed. An
and reporting the problem, see Collecting diagnostic SQLCODE -904 is issued, and/or message DSNT500I
data (Collecting data). is issued.
Collect the following diagnostic items: SYS1.LOGREC contains information in the variable
• Console output from the system on which the job area (SDWA). Significant fields for this code are:
was run, and a listing of the SYSLOG data set for the VRARRK13, VRARRK14, and VRARRK15.
• SVC dump (or system dump), taken to SYS1.DUMPxx report the problem. For information about identifying
data set, as result of an operator-initiated dump and reporting the problem, see Collecting diagnostic
command or SLIP trap exit. data (Collecting data).
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application • Console output from the system on which the job
program or batch job, and system messages that was run, and a listing of the SYSLOG data set for the
were issued. Make sure that MSGLEVEL=(1,1) on the period of time that spans the failure.
JOB statement so that all diagnostic information is • SVC dump (or system dump), taken to SYS1.DUMPxx
sent to SYSPRINT. data set, as result of an operator-initiated dump

• Listing of SYS1.LOGREC data set, obtained by • SYSPRINT output, including JCL, for the application
executing IFCEREP1. program or batch job, and system messages that
• SYSPRINT output, including JCL, for the application were issued. Make sure that MSGLEVEL=(1,1) on the
program or batch job, and system messages that JOB statement so that all diagnostic information is
were issued. Make sure that MSGLEVEL=(1,1) on the sent to SYSPRINT.
JOB statement so that all diagnostic information is Related information
sent to SYSPRINT. -904
Related information UNSUCCESSFUL EXECUTION CAUSED BY AN
-904 UNAVAILABLE RESOURCE. REASON reason-
UNSUCCESSFUL EXECUTION CAUSED BY AN code, TYPE OF RESOURCE resource-type, AND
UNAVAILABLE RESOURCE. REASON reason- RESOURCE NAME resource-name
code, TYPE OF RESOURCE resource-type, AND DSNT500I (Db2 Messages)
00C9008C
00C9008B Explanation
An attempt was made to allocate or bind to a
Explanation partitioned table space for which no partitioning key
An attempt was made to create a database, but no was defined.
DBIDs are available; that is, the system limit has been
reached. System action
The bind or allocation process is not allowed.
System action
The create is not allowed. User response
Define the partitioning key or partitioning index for the
User response partitioned table space, and rerun the job.
DROP all unused databases, and rerun the job.
Problem determination The requested operation is not performed. An
The requested operation is not performed. An SQLCODE -904 is issued, and/or message DSNT501I
SQLCODE -904 is issued, and/or message DSNT500I is issued.
is issued. SYS1.LOGREC contains information in the variable
SYS1.LOGREC contains information in the variable recording area (VRA) of the system diagnostic work
recording area (VRA) of the system diagnostic work area (SDWA). Significant fields for this code are:
area (SDWA). Significant fields for this code are: VRARRK13, VRARRK14, and VRARRK15. If you
VRARRK13, VRARRK14, and VRARRK15. suspect an error in Db2, you might need to report
If you suspect an error in Db2, you might need to reporting the problem, see Collecting diagnostic data
report the problem. For information about identifying (Collecting data).
data (Collecting data). Collect the following diagnostic items:
Collect the following diagnostic items: • Console output from the system on which the job
• SVC dump (or system dump), taken to SYS1.DUMPxx command or SLIP trap exit.
executing IFCEREP1.
• Listing of Db2 catalog tables.
executing IFCEREP1.
• Source listing of the failing application program.

• SYSPRINT output, including JCL, for the application • Listing of Db2 catalog tables.
program or batch job, and system messages that • Source listing of the failing application program.
JOB statement so that all diagnostic information is • SYSPRINT output, including JCL, for the application
sent to SYSPRINT. program or batch job, and system messages that
• Db2 log output, including any Db2 recovery log JOB statement so that all diagnostic information is
archive tapes. sent to SYSPRINT.
• Definitions of views and tables involved in the error. • Db2 log output, including any Db2 recovery log
Related information archive tapes.
DSNT501I (Db2 Messages) • Definitions of views and tables involved in the error.
-904 Related information
-904
00C9008D
Explanation
00C9008E
An attempt was made to bind to a table space that had
an incomplete clustering definition. Explanation
A lock request for the resource identified by NAME
System action
could not be granted, and the request waited for a
The bind process is not allowed. period longer than the maximum specified by the
installation.
User response
System action
Complete the clustering definition for the table space,
and rerun the job. The data manager function that detected this
condition returns 'resource not available' to its invoker.
Problem determination Message DSNT378I might also be issued.
SQLCODE -904 is issued, and/or message DSNT501I Problem determination
is issued.
SYS1.LOGREC contains information in the variable SQLCODE -904, -911, -913, or -923 is issued, and/or
recording area (VRA) of the system diagnostic work message DSNT501I is issued. If a timeout occurs, see
area (SDWA). Significant fields for this code are: also the "System Programmer Response" for message
VRARRK13, VRARRK14, and VRARRK15. If you DSNT376I for problem determination.
suspect an error in Db2, you might need to report
reporting the problem, see Collecting diagnostic data
(Collecting data).
Collect the following diagnostic items: suspect an error in Db2, you might need to report
(Collecting data).
• SVC dump (or system dump), taken to SYS1.DUMPxx Collect the following diagnostic items:
data set, as result of an operator-initiated dump • Console output from the system on which the job
command or SLIP trap exit. was run, and a listing of the SYSLOG data set for the
• Listing of SYS1.LOGREC data set, obtained by period of time that spans the failure.
executing IFCEREP1.

• SVC dump (or system dump), taken to SYS1.DUMPxx User response
command or SLIP trap exit. Create the database object in a different database or
drop unused database objects from the database. If
• Listing of SYS1.LOGREC data set, obtained by you drop an object that is an index or a table space,
executing IFCEREP1. the space becomes available in the DBD as soon as the
• IRLM trace output. drop is committed. If you drop an object that is a table,
• SYSPRINT output, including JCL, for the application the space in the DBD is made available only after all of
program or batch job, and system messages that the following events:
were issued. Make sure that MSGLEVEL=(1,1) on the • The DROP is committed.
• The Db2 REORG is run on the table space and there
sent to SYSPRINT.
is no point in time recover after the REORG.
• Listing of the IRLM procedure.
• MODIFY is run to delete all image copies of data
• Results from SELECT * from SYSIBM.SYSDATABASE. that contains rows of the dropped table, that is,
Related information copies that were taken before the REORG. Note that
MODIFY will reclaim space in the DBD only if there
-904
are SYSCOPY rows to delete.
code, TYPE OF RESOURCE resource-type, AND Problem determination
-911 SQLCODE -904 is issued, and/or message DSNT500I
THE CURRENT UNIT OF WORK HAS BEEN is issued.
ROLLED BACK DUE TO DEADLOCK OR TIMEOUT.
REASON reason-code, TYPE OF RESOURCE
resource-type, AND RESOURCE NAME resource-
name
-913 suspect an error in Db2, you might need to report
UNSUCCESSFUL EXECUTION CAUSED BY the problem. For information about identifying and
DEADLOCK OR TIMEOUT. REASON CODE reporting the problem, see Collecting diagnostic data
reason-code, TYPE OF RESOURCE resource- (Collecting data).
type, AND RESOURCE NAME resource-name
-923
CONNECTION NOT ESTABLISHED: DB2 • Console output from the system on which the job
condition REASON reason-code, TYPE resource- was run, and a listing of the SYSLOG data set for the
type, NAME resource-name period of time that spans the failure.
DSNT501I (Db2 Messages) • SVC dump (or system dump), taken to SYS1.DUMPxx
00C9008F executing IFCEREP1.
Explanation program or batch job, and system messages that
The database descriptor's size (DBD) has reached the JOB statement so that all diagnostic information is
limit of 25% of the EDM Pool size. sent to SYSPRINT.
.
System action
Related information
The request to create/alter a database object is not -904
allowed. UNSUCCESSFUL EXECUTION CAUSED BY AN

00C90090 00C90091
An attempt to lock a required resource failed. The table space or index space could not be started,
because there is an outstanding indoubt UR that must
System action be resolved before the start is allowed.
The operation is not performed.

System action
User response The START operation is not performed.
Wait for all jobs which hold a lock on the resource in an

incompatible lock state to complete before reissuing
the failing statement. Message DSNI002I is issued. See the description of
that message for additional information.
Problem determination SYS1.LOGREC contains information in the variable
The requested operation is not performed.
If the resource type is table space, table, or index, VRARRK13, VRARRK14, and VRARRK15. If you
then issue the -DISPLAY DATABASE command with the suspect an error in Db2, you might need to report
LOCKS option to get a list of jobs which currently hold the problem. For information about identifying and
locks on the required resource. reporting the problem, see Collecting diagnostic data
(Collecting data).
If the resource type is a package, then wait for BIND
activity on that package to complete before reissuing Collect the following diagnostic items:
the failing request.
If the problem persists after jobs which hold was run, and a listing of the SYSLOG data set for the
incompatible locks complete, gather diagnostic period of time that spans the failure.
information to pursue the problem. • SVC dump (or system dump), taken to SYS1.DUMPxx
SYS1.LOGREC contains information in the variable data set, as result of an operator-initiated dump
recording area (VRA) of the system diagnostic work command or SLIP trap exit.
area (SDWA). Significant fields for this code are: • Listing of SYS1.LOGREC data set, obtained by
VRARRK13, VRARRK14, and VRARRK15. If you executing IFCEREP1.
(Collecting data).
Collect the following diagnostic items: sent to SYSPRINT.
• Console output from the system on which the job • Db2 log output, including any Db2 recovery log
was run, and a listing of the SYSLOG data set for the archive tapes.
00C90092
Explanation
• Listing of SYS1.LOGREC data set, obtained by Db2 received an out-of-storage indication from IRLM
executing IFCEREP1. resulting from a lock, unlock, or lock change request.
program or batch job, and system messages that System action
were issued. Make sure that MSGLEVEL=(1,1) on the A record is written to SYS1.LOGREC only when an
JOB statement so that all diagnostic information is abend is issued. No dump is requested.
sent to SYSPRINT.
archive tapes.

Operator response reporting the problem, see Collecting diagnostic data
(Collecting data).
IRLM has exhausted the amount of virtual storage period of time that spans the failure.
available to it to represent locks. Insufficient virtual
storage remains to satisfy this request. You can use • SVC dump (or system dump), taken to SYS1.DUMPxx
the IRLM startup procedure to determine the amount data set, as result of an operator-initiated dump
of storage space available. command or SLIP trap exit.
The current mix of transactions caused all available
executing IFCEREP1.
storage to be used. You can find the number of locks
held by a particular transaction by either using the • IRLM trace output.
Db2 performance trace facility or by performing IRLM • SYSPRINT output, including JCL, for the application
tracing. program or batch job, and system messages that
Determine what transactions were running and the were issued. Make sure that MSGLEVEL=(1,1) on the
number of locks they held. You might want to schedule JOB statement so that all diagnostic information is
some of these transactions at a different time. sent to SYSPRINT.
• Definitions of views and tables involved in the error.
You can reduce the total number of page or row locks
that applications concurrently hold by changing the • Listing of the IRLM procedure.
locking protocol on one or more table spaces. Use one Related concepts
of the following statements:
Db2 trace (Db2 Performance)
• ALTER TABLESPACE...LOCKSIZE ANY Related tasks
• ALTER TABLESPACE...LOCKSIZE TABLESPACE IRLM startup procedure options (Db2
• LOCK TABLE Performance)
Analyzing concurrency (Db2 Performance)
If application logic permits, reduce the number of page
Related reference
or row locks concurrently held for SELECT statements
by re-binding application plans with isolation level START irlmproc (z/OS IRLM) (Db2 Commands)
of cursor stability instead of repeatable read or read SELECT (Db2 SQL)
stability. LOCK TABLE (Db2 SQL)
You can reduce the total number of LOB locks that ALTER TABLESPACE (Db2 SQL)
applications concurrently hold by changing the locking Related information
protocol on one or more LOB table space. Use one of -904
the following statements: UNSUCCESSFUL EXECUTION CAUSED BY AN
• ALTER TABLESPACE...LOCKSIZE TABLESPACE
• LOCK TABLE statement RESOURCE NAME resource-name
-923
Problem determination CONNECTION NOT ESTABLISHED: DB2
One or more of the following messages or codes might condition REASON reason-code, TYPE resource-
be issued: type, NAME resource-name
• An SQLCODE -904 or -923
• Message DSNT501I 00C90093
• An abend
SYS1.LOGREC contains information in the variable Explanation
recording area (VRA) of the system diagnostic work An error occurred in IRLM.
suspect an error in Db2, you might need to report System action
the problem. For information about identifying and A record is written to SYS1.LOGREC, and an SVC dump
is requested.

Operator response .

Examine SYS1.LOGREC for a preceding error related to A data set is in a different state than Db2 expects,
IRLM. which might occur as a result of the following
situations:
Problem determination • A data set was deleted and redefined, but Db2 does
not recognize the redefined data set.
One or more of the following might be issued:
• A previous Db2 failure damaged the data set in some
• An SQLCODE -904 or -923 way.
• Message DSNT501I
• An abend System action
SYS1.LOGREC contains the same diagnostic The requested action is not performed. If the invoker
information in the variable recording area (VRA) as of this module abends, a record is written to
shown for abend reason code '00C90101'. The first SYS1.LOGREC, and the invoker might initiate a dump.
four bytes of CTSIWHY contain the return code from If the invoker does not abend, no record is written, and
the IRLM function. The fifth byte of CTSIWHY contains no dump is requested. If this occurs, an SQL return
the request code, as follows: code is issued, or message DSNT500I is issued, or
X'02' both. The data set is placed in a stopped status unless
Lock the invoker of the module is a utility.
X'03'
Unlock Operator response
X'04' Notify the system programmer.
Change
SYS1.LOGREC contains information in the variable System programmer response
recording area (VRA) of the system diagnostic work If you do not have the current level of the data set,
area (SDWA). Significant fields for this code are: you must perform Db2 recovery to return the data set
VRARRK13, VRARRK14, and VRARRK15. If you to its expected state. See the Problem Determination
suspect an error in Db2, you might need to report section of this message to learn how to determine the
the problem. For information about identifying and name of the data set to be corrected. Use the DISPLAY
reporting the problem, see Collecting diagnostic data command to check the status of the data set. If the
(Collecting data). data set is stopped, use the START command before
Collect the following diagnostic items: performing recovery.
was run, and a listing of the SYSLOG data set for the User response
period of time that spans the failure. If the code was received while processing a user
• SVC dump (or system dump), taken to SYS1.DUMPxx table, Db2 determined that the data set is empty.
data set, as result of an operator-initiated dump A DROP TABLESPACE statement followed by a
command or SLIP trap exit. CREATE TABLESPACE statement and a CREATE TABLE
• Listing of SYS1.LOGREC data set, obtained by statement defines the dropped table to Db2. Use the
executing IFCEREP1. IDCAMS LISTCAT for the failing Db2 data set. Check
the HI-USED-RBA for this data set; if HI-USED-RBA =
• IRLM trace output. 0, the data set is empty.
program or batch job, and system messages that Problem determination
JOB statement so that all diagnostic information is This error is detected at a time when Db2 cannot
sent to SYSPRINT. determine the specific name of the data set involved.
• Definitions of views and tables involved in the error. However, the SQL return code or message DSNT500I
provides the name of the table space or index space

where the data set resides. When the table or index System action
space consists of a single data set, this is specific.
Otherwise, the system programmer must find the The restart of the named table space, index space, or
particular data set within the table or index space. partition is deferred by the subsystem.

recording area (VRA) of the system diagnostic work Operator response
area (SDWA). Significant fields for this code are: Notify the system programmer.
reporting the problem, see Collecting diagnostic data Correct the problem, and then use either the -START
(Collecting data). DATABASE command or the RECOVER utility to make
Collect the following diagnostic items: the table space, index space, or partition available.

period of time that spans the failure. Examine previous messages on the console to
• SVC dump (or system dump), taken to SYS1.DUMPxx determine why Db2 could not access the page.
data set, as result of an operator-initiated dump One possible reason is that a back-level pack was
command or SLIP trap exit. mounted. That is, the page to which the log record
applies was not yet formatted by VSAM. Db2 does not
• Listing of SYS1.LOGREC data set, obtained by extend data sets during restart.
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application suspect an error in Db2, you might need to report
program or batch job, and system messages that the problem. For information about identifying and
were issued. Make sure that MSGLEVEL=(1,1) on the reporting the problem, see Collecting diagnostic data
JOB statement so that all diagnostic information is (Collecting data).
sent to SYSPRINT.
archive tapes. • Console output from the system on which the job
Related tasks • SVC dump (or system dump), taken to SYS1.DUMPxx
Recovering catalog and directory objects (Db2 data set, as result of an operator-initiated dump
Utilities) command or SLIP trap exit.
Recovering user-managed data sets for • Listing of SYS1.LOGREC data set, obtained by
accidentally dropped table spaces (Db2 executing IFCEREP1.
• Dump of the index or table space that failed.
Related reference
-DISPLAY DATABASE (Db2) (Db2 Commands) • SYSPRINT output, including JCL, for the application
Related information
DSNT500I (Db2 Messages) JOB statement so that all diagnostic information is
DSNT501I (Db2 Messages) sent to SYSPRINT.
00C90095 • Db2 log output, including any Db2 recovery log

archive tapes.
An attempt was made during Db2 restart to access a

page in order to apply a log record but Db2 was unable Explanation
to access the page. This abend reason code appears as The page or row lock on the page or subpage
the reason code in message DSNI001I. identified by the NAME resource-name value in

message DSNT500I or DSNT501I caused the total Problem determination
number of page or row locks concurrently held to
reach the installation maximum number of page or An SQLCODE -904 and message DSNT500I or
row locks (NUMLKUS) allowed for a single agent in the DSNT501I are issued.
system. SYS1.LOGREC contains information in the variable
System action area (SDWA). Significant fields for this code are:
The operation that encountered this condition is not
executed. If a utility job encountered this condition, If you suspect an error in Db2, you might need to
the utility is stopped. Otherwise, any database updates report the problem. For information about identifying
for the statement that was executing are backed and reporting the problem, see Collecting diagnostic
out. Any database reads for the statement that was data (Collecting data).
executing are not executed. The position of the cursor Collect the following diagnostic items:
is unpredictable.
Operator response period of time that spans the failure.
If a utility job encountered this resource unavailable • SVC dump (or system dump), taken to SYS1.DUMPxx
condition, terminate the utility and restart it after the data set, as result of an operator-initiated dump
cause of the resource unavailable condition has been command or SLIP trap exit.
corrected.
executing IFCEREP1.
System programmer response • SYSPRINT output, including JCL, for the application
If the application should be able to run with the program or batch job, and system messages that
current page or row or locking protocol and SQL were issued. Make sure that MSGLEVEL=(1,1) on the
statements, increase the NUMLKUS value for the JOB statement so that all diagnostic information is
installation to allow a higher limit of page or row to be sent to SYSPRINT.
concurrently held by a single application. If a utility job Related tasks
encountered this resource unavailable condition, the
Estimating the storage needed for locks (Db2
NUMLKUS value must be increased to accommodate
Performance)
the utility, because utilities are programmed to use the
minimum number of page or row locks possible. Choosing an ISOLATION option (Db2
Performance)
Controlling concurrent access to tables (Db2
User response Performance)
Rerun the application after correcting the cause of this Related reference
resource unavailable condition. LOCKS PER USER field (NUMLKUS subsystem
Programmer response LOCK TABLE (Db2 SQL)
Reduce the total number of page or row locks that Related information
the application concurrently holds by changing the -904
locking protocol on one or more of the table spaces to UNSUCCESSFUL EXECUTION CAUSED BY AN
table space level locking. To do this, use the ALTER ... UNAVAILABLE RESOURCE. REASON reason-
LOCKSIZE TABLESPACE or LOCK TABLE statements. code, TYPE OF RESOURCE resource-type, AND
Review the application to see if a different choice of
SQL statements can be used to perform the same DSNT500I (Db2 Messages)
operation with less concurrent access to multiple DSNT501I (Db2 Messages)
tables with page or row locking.
00C90097
If application logic permits, reduce the number of page
or row locks concurrently held for SELECT statements
by rebinding the application plan with isolation level Explanation
of cursor stability instead of repeatable read or read An attempt was made to allocate to a table space
stability, or add more frequent commits. for update operations. However, the table space was
marked as 'image copy' required, and updates are not

allowed. This condition occurs as a result of any of the • SYSPRINT output, including JCL, for the application
following operations: program or batch job, and system messages that
• Running a REORG LOG NO or LOAD LOG NO utility on
the table space without running a copy that specifies
sent to SYSPRINT.
FULL YES.
• Execution of a RECOVER utility which specifies the Related tasks
TORBA or TOCOPY options, without following it with Using the REPAIR utility on inconsistent data
the required COPY utility. (Db2 Administration Guide)
• Execution of a -TERM UTILITY command on a COPY Changing the logging attribute for a table space
utility that failed during the copy phase or was active (Db2 Administration Guide)
in the copy phase. Until the COPY utility completes, Related reference
SQL updates are not allowed because the integrity of ALTER TABLESPACE (Db2 SQL)
the data would be compromised. REORG INDEX (Db2 Utilities)
• Execution of a MODIFY RECOVERY utility after all REORG TABLESPACE (Db2 Utilities)
back up copies of the table space or data set were RECOVER (Db2 Utilities)
deleted from the SYSCOPY catalog table. -TERM UTILITY (Db2) (Db2 Commands)
• Execution of an ALTER TABLESPACE LOGGED MODIFY RECOVERY (Db2 Utilities)
command after updates on a not logged tablespace. The LOG option of the LOAD or REORG utilities
(Db2 Administration Guide)
System action Related information
The allocation process is not allowed. -904
User response code, TYPE OF RESOURCE resource-type, AND
Run the COPY utility. However, if the table space is to RESOURCE NAME resource-name
be used for read-only access, or if recoverability of the DSNT501I (Db2 Messages)
data is not required, instead of taking a full image copy
you can run the REPAIR utility and request that the 00C90098
image copy required condition be removed.
Explanation
An attempt was made to increase read-only or write-
The requested operation is not performed. An access counts of the utility in process beyond the
SQLCODE -904 and/or message DSNT501I is issued. maximum (255) allowed.
recording area (VRA) of the system diagnostic work System programmer response
Determine why active utilities are in the stopped state.
Use the -TERM UTILITY command to terminate utilities
If you suspect an error in Db2, you might need to and reduce the UIP (utility in process) counts. If no
report the problem. For information about identifying active utilities are indicated, then use the -DISPLAY
and reporting the problem, see Collecting diagnostic DATABASE command to show which table spaces or
data (Collecting data). partitions are in a UTRO or UTRW state.
User response
was run, and a listing of the SYSLOG data set for the Use the -DISPLAY UTILITY command to determine
period of time that spans the failure. how many utility jobs are currently active. If a number
• SVC dump (or system dump), taken to SYS1.DUMPxx of utility jobs are active but not in the stopped state,
data set, as result of an operator-initiated dump notify the system programmer. If the utility jobs are
command or SLIP trap exit. running, resubmit your job after they complete.

executing IFCEREP1.

Problem determination • SYSPRINT output, including JCL, for the application
Message DSNT500I is issued. For more information, were issued. Make sure that MSGLEVEL=(1,1) on the
refer to the explanation of message DSNT500I. JOB statement so that all diagnostic information is
00C90099 sent to SYSPRINT.
• Definitions of table spaces, tables, and indexes
Explanation involved in the error.
A utility attempted to load data into a partition that is If you receive this reason code when the REORG
already full. The utility specified the correct partition utility is materializing the pending definition change
based on the high key value for the partition, but for converting a PBG table to PBR, also collect the
the requested data page number is higher than the following diagnostic item:
last data page number in the partition, based on the
DSSIZE. Related reference
This usually occurs in the following situations:
Related information
• A very large partition undergoes many inserts and DSNT500I (Db2 Messages)
updates, and a reorganization of the table space
causes expansion of the free space (specified by 00C9009A
PCTFREE and FREEPAGE) such that the data no
longer fits in the partition. Explanation
An attempt was made to create a system database
System action
which, according to the DBID space map, has
The requested action is not performed. already been created. However, the catalog shows the
database was not created. This discrepancy between
Operator response the catalog and the space map for DBIDs may be due
to an unsuccessful migration.
System action
Database is not created.
Terminate the utility.
If the terminated utility results in recover pending Operator response
(RECP) status for the target table space objects,
complete these steps:
1. Recover the affected table space or partitions. System programmer response
2. Alter the partition key.
Drop the database, then create it again. If this fails
3. Retry the reorganization. to resolve the error, follow the problem determination
steps.
User response
Adjust the high key values and retry the utility Problem determination
operation. Query the catalog to check the PCTFREE The requested operation is not performed. An
and FREEPAGE values. You might be able to decrease SQLCODE -904 is issued, and/or message DSNT500I
the amount of free space to allow the REORG utility to is issued.
complete successfully.
Problem determination area (SDWA). Significant fields for this code are:
Collect the following diagnostic items: VRARRK13, VRARRK14, and VRARRK15. If you
• Console output from the system on which the job the problem. For information about identifying and
was run, and a listing of the SYSLOG data set for the reporting the problem, see Collecting diagnostic data
period of time that spans the failure. (Collecting data).

• Console output from the system on which the job • SYSPRINT output, including JCL, for the application
was run, and a listing of the SYSLOG data set for the program or batch job, and system messages that
period of time that spans the failure. were issued. Make sure that MSGLEVEL=(1,1) on the
• SVC dump (or system dump), taken to SYS1.DUMPxx JOB statement so that all diagnostic information is
data set, as result of an operator-initiated dump sent to SYSPRINT.
command or SLIP trap exit. • Definitions of table spaces, tables, and indexes
• Listing of SYS1.LOGREC data set, obtained by involved in the error.
executing IFCEREP1. Related concepts
• SYSPRINT output, including JCL, for the application Reorganization of partition-by-growth table
program or batch job, and system messages that spaces (Db2 Utilities)
were issued. Make sure that MSGLEVEL=(1,1) on the Related tasks
JOB statement so that all diagnostic information is Reserving free spaces for indexes (Db2
sent to SYSPRINT. Performance)
• Results from SELECT * from SYSIBM.SYSDATABASE. Reserving free space in table spaces (Db2
• Print of the BSDS record with the key of Performance)
X'16000001', obtained by running IDCAMS. Related reference
Related information -TERM UTILITY (Db2) (Db2 Commands)
-904 ALTER TABLESPACE (Db2 SQL)
UNSUCCESSFUL EXECUTION CAUSED BY AN Limits in Db2 for z/OS (Db2 SQL)
UNAVAILABLE RESOURCE. REASON reason- Related information
code, TYPE OF RESOURCE resource-type, AND DSNT500I (Db2 Messages)
DSNT500I (Db2 Messages) 00C9009C
00C9009B Explanation
An attempt was made to place data into a partitioned
Explanation table space, partition-by-growth table space, index
An attempt was made to load data into a space, or fixed hash space, but the partition is full or a
nonpartitioned table space, but the table space is full. system page could not be inserted.
A nonpartitioned table space can contain a maximum For a table space partition, the data to be inserted is
of 64 GB of data. based on the high-key value that is specified in the
cluster index. For an index space partition, the index
System action entry to be inserted is also based on the high-key
value that is associated with the index.
The requested action is not performed.
System action
User response
A "resource not available" code is returned and the
Use the -TERM UTILITY command to terminate the requested action is not performed. The SVC dump and
LOAD utility. Use ALTER TABLE SPACE to reduce the SYS1.LOGREC recording are not requested.
the amount of free space within a page (PCTFREE
attribute) and the number of free pages within the
table space (FREEPAGE attribute). Then retry the load. System programmer response
If it is a resume load job, reorganize the table space Take one of the following actions:
before rerunning the load.
• If you received this reason code with message
DSNT501I, redefine the partition that is identified in
Problem determination that message and resubmit the job.
Collect the following diagnostic items: • If you received this reason code for a hash table,
• Console output from the system on which the job new system pages cannot fit in the fixed hash space.
was run, and a listing of the SYSLOG data set for the To correct this problem, reorganize the table space
period of time that spans the failure. that contains the hash table to make room for
system pages.

• If you received this reason code for a partition-by- • Create a table or complete the definition of a table
growth table space, one of the following problems in the table space. In this case, Db2 attempted to
might have occurred: insert a system page in the table space.
– The number of partitions cannot grow beyond the A nonpartitioned table space, index space or LOB table
limit that is specified by MAXPARTITIONS. In this space can contain a maximum of 64GB of data. A LOB
case, change the limit for MAXPARTITIONS. table space can contain as many as 254 data sets per
– Db2 was unable to obtain a partition lock on the table space.
table space. To determine whether this problem
occurred, collect a statistics trace for IFCID 2. System action
• If you received this reason code from an insert or A 'resource not available' code is returned to the
update transaction, a new system page cannot fit in user and the requested action is not performed. The
the partition. To correct this problem, reorganize the SVC dump and the SYS1.LOGREC recording are not
table space that contains the affected partition or requested.
partitions to make room for system pages.

User response
The table space, index space, or LOB table space name
Notify the system programmer. is identified in the DSNT501I message. If the object
is a table space or LOB table space, run the REORG
Problem determination TABLESPACE utility to attempt to reclaim additional
free space. If the object is an index space, drop and
Collect the following diagnostic items: re-create the index with a fewer number of SUBPAGEs.
• Console output from the system on which the job If free space cannot be reclaimed, notify the database
was run, and a listing of the SYSLOG data set for the administrator to redistribute the data into different
period of time that spans the failure. table spaces, LOB tables spaces, or index spaces.
• Definitions of table spaces, tables, and indexes If you suspect an error in Db2, you might need to
involved in the error. report the problem. For information about identifying
• Statistics trace for IFCID 2. and reporting the problem, see Collecting diagnostic
Related tasks
Redefining a partition (table-based partitioning) User response
Redefining a partition (index-based partitioning) Notify the system programmer to reclaim some free
(Db2 Administration Guide) space in the associated table space, index space or
Altering table spaces (Db2 Administration LOB table space and rerun the job.
Guide)
Related reference Problem determination
REORG TABLESPACE (Db2 Utilities) Collect the following diagnostic items:
Related information
DSNT501I (Db2 Messages) was run, and a listing of the SYSLOG data set for the
-904 period of time that spans the failure.
involved in the error.
RESOURCE NAME resource-name Related reference
REORG TABLESPACE (Db2 Utilities)
00C9009D
Limits in Db2 for z/OS (Db2 SQL)
Related information
Explanation DSNT501I (Db2 Messages)
An attempt was made to take one of the following
actions, but the table space or index space was full: 00C9009E
• Insert data into a nonpartitioned table space or

index space.

Explanation 00C9009F
The object depends on new facilities of the release
and is therefore unavailable for processing. For data- Explanation
sharing systems, the object will be available on a new A table has been referenced that has a primary key
release in a data-sharing group. For non-data-sharing or unique key but no index exists to enforce its
systems, the object will be available after re-migration uniqueness. The reference is usually to a parent table
if release fall back has occurred. when attempting to verify the referential constraint of
an insert or update operation to a dependent table.
System action
The operation is not allowed. The data manager System action
function that detected this condition returns 'resource The use of the table is not allowed.
not available' to its invoker.
User response
Operator response
Create a unique index on the referenced table to
Notify the system programmer. enforce the primary key or unique key.

In order to perform the operation on the object: The requested operation is not performed. An
• For non-data sharing systems a re-migration is SQLCODE -904 or -923 is issued.
required. Related concepts
• For data sharing systems, ensure that the operation Unique constraints (Introduction to Db2 for
is performed on a member at the correct level of z/OS)
Db2. Db2 keys (Introduction to Db2 for z/OS)
If you suspect an error in Db2, you might need to Related tasks
report the problem. For information about identifying Creating Db2 indexes (Db2 Administration
and reporting the problem, see Collecting diagnostic Guide)
data (Collecting data). Related information
-904
Problem determination UNSUCCESSFUL EXECUTION CAUSED BY AN
SQLCODE -904 is issued. Message DSNT500I or
message DSNT501I may also be issued.
-923
• Console output from the system on which the job condition REASON reason-code, TYPE resource-
was run, and a listing of the SYSLOG data set for the type, NAME resource-name
period of time that spans the failure. DSNT501I (Db2 Messages)
data set, as result of an operator-initiated dump 00C900A0
• Listing of SYS1.LOGREC data set, obtained by Explanation
executing IFCEREP1.
An attempt was made to allocate or access a table
Related information space or index that is in the recover pending status
-904 (RECP).
UNAVAILABLE RESOURCE. REASON reason- System action
RESOURCE NAME resource-name The use of the object is not allowed.

Determine whether the RECOVER utility should be run Run the RECOVER utility, LOAD utility or START
to complete recovering the object. DATABASE command to recover the object.

Determine when the resource is available for use and The requested operation is not performed because
rerun the job. the table space or index might be in an inconsistent
state. An SQLCODE -904 and/or message DSNT501I
Problem determination is issued. For more information, refer to Part 1, “SQL
codes,” on page 1.
The requested operation is not performed because the
table space or index might be in an inconsistent state.
An SQLCODE -904 and/or message DSNT501I and/or • Console output from the system on which the job
message DSNI005I is issued. For more information, was run, and a listing of the SYSLOG data set for the
refer to Part 1, “SQL codes,” on page 1. period of time that spans the failure.
Collect the following diagnostic items: • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
was run, and a listing of the SYSLOG data set for the Related reference
period of time that spans the failure. RECOVER (Db2 Utilities)
• Listing of SYS1.LOGREC data set, obtained by LOAD (Db2 Utilities)
executing IFCEREP1. -START DATABASE (Db2) (Db2 Commands)
. Related information
-904
Related reference UNSUCCESSFUL EXECUTION CAUSED BY AN
RECOVER (Db2 Utilities) UNAVAILABLE RESOURCE. REASON reason-
RECOVER-pending status (Db2 Utilities) code, TYPE OF RESOURCE resource-type, AND
Related information RESOURCE NAME resource-name
-904 DSNT501I (Db2 Messages)
UNAVAILABLE RESOURCE. REASON reason- 00C900A2
Explanation
A READS call for IFCID 0306 included a request to
DSNI005I (Db2 Messages)
convert returned log records to the format for the table
space version in which the data was written. However,
00C900A1
the log records could not be converted.
Explanation
System action
An attempt was made to allocate a table space or
Log records are returned, but the log records are not
index that is in group recovery pending state.
converted to the format for the table space version in
which the data was written.
System action
The use of the object is not allowed. User response
Correct the problem that caused data conversion to
Operator response fail. Then reissue the READS request.
Determine whether the RECOVER utility or START
DATABASE command should be run to complete Problem determination
recovery of the object.
In the output from the READS call, find field
QW0306DG in the IFCID 0306 record. The value in
that field contains information on why data version

conversion was not performed. A common reason is CHECK INDEX (Db2 Utilities)
00C900B0, which means that information in a system CHECK LOB (Db2 Utilities)
page for a table space version could not be retrieved. Related information
Related reference DSNT501I (Db2 Messages)
Qualifying log records for IFCID 0306 requests -904
(Db2 Administration Guide) UNSUCCESSFUL EXECUTION CAUSED BY AN
Related information UNAVAILABLE RESOURCE. REASON reason-
00C900B0 code, TYPE OF RESOURCE resource-type, AND
00C900A3 -923
Explanation condition REASON reason-code, TYPE resource-
An attempt was made to allocate a table space, index
space, or a related index space while the table space 00C900A4
or index space was in check pending status.
Explanation
System action
An attempt was made to allocate a segment for a
The operation is not allowed. table in a segmented table space, but there are no
free segments. A segmented table space can contain a
Operator response maximum of 64GB of data. A segment will be allocated
under one of the following conditions:
• When a table is ready to be created in a segmented
table space with the CREATE TABLE statement.
• When a record is inserted/loaded into a segmented
Resolve the check pending status and retry the table and free space is not available from existing
operation. segments.
If the object is a table space with referential
relationships, then run the CHECK DATA utility to System action
check for referential integrity violations.
A 'resource not available' code is returned to the user
If the object is a base table space with LOB columns, and the requested action is not performed.
then run the CHECK DATA utility to validate the
auxiliary columns. System programmer response
If the object is a LOB table space, then run the CHECK
An SQLCODE -904 is issued, and/or message
LOB utility to validate the structure of the LOB table
DSNT501I is issued. The segmented table space
space.
name is identified in SQLCA and/or in the DSNT501I
If the object is an index space, then run the CHECK message. If the requested function is the CREATE
INDEX utility to verify that the index keys are TABLE statement, create the table in a different
consistent with the data in the table space or table segmented table space. Otherwise, run the REORG
space partition. TABLESPACE utility to attempt to reclaim additional
free space. If no free space can be reclaimed, then
notify the database administrator to redistribute the
data into different table spaces.
SQLCODE -904 or -923 is issued. User response
Related tasks
Notify the system programmer to reclaim some free
Removing various pending states from LOB and space in the associated segmented table space and
XML table spaces (Db2 Administration Guide) rerun the job.
Resetting restricted status after running the
LOAD utility (Db2 Utilities)
Related reference
CHECK DATA (Db2 Utilities) Collect the following diagnostic items:

period of time that spans the failure. The requested operation is not performed. An
SQLCODE -904 or message DSNT501I is issued,
• Definitions of table spaces, tables, and indexes and/or message DSNT501I is issued.
Related reference
REORG TABLESPACE (Db2 Utilities) • Console output from the system on which the job
Related information
UNSUCCESSFUL EXECUTION CAUSED BY AN JOB statement so that all diagnostic information is
UNAVAILABLE RESOURCE. REASON reason- sent to SYSPRINT.
RESOURCE NAME resource-name • IDCAMS LISTCAT output for the ICF (VSAM) catalog
00C900A5 defined the failing index or table.
Collect definitions of the temporary files that are
Explanation involved in the error.
One or more temporary files are full, or the maximum Related reference
number of extensions for VSAM data sets has been -DISPLAY THREAD (Db2) (Db2 Commands)
exceeded for all temporary files, or the volumes have Related information
no space available in which to extend. DSNT501I (Db2 Messages)
-904
System action UNSUCCESSFUL EXECUTION CAUSED BY AN
The reason code appears in a DSNT501I message, and
the requested operation is not performed.
User response 00C900A6

If the reason code appears in a DSNT501I message,
issue -DISPLAY THREAD to determine the total Explanation
number of concurrent users. If there were a large
This message is issued in the following situations:
number of users using temporary files, resubmit the
job when concurrent users are low. IDCAMS LISTCAT • Access to the catalog was requested but denied
may be used to determine the VSAM data sets space because the catalog was not migrated to the current
allocations. release level. The object in the catalog is available
after the catalog is migrated.
• If there was no space available on a volumes, then
clear space from the volume(s) or add more volumes • You ran one of the following utility operations
to the STOGROUP or redefine the VSAM data set to that terminated prematurely in a previous attempt:
concatenate more volumes. CATMAINT UPDATE SCHEMA, CATMAINT UPDATE
VCAT, or CATMAINT UPDATE OWNER.
• If the maximum number of extensions has been
exceeded for VSAM data sets, ALTER or delete and
redefine the temporary data sets with a larger size. System action
• If all the temporary files are full, then create or The operation is not complete. The data manager
define more temporary files. function that detected this condition returns 'resource
Issue the -START DATABASE command to start the
temporary file.
Operator response

To perform the operation on the object, you must first If the problem persists after the plan or the package is
complete the Db2 12 catalog migration process, as rebound, collect the following diagnostic items:
described in Migration step 19: Tailor Db2 12 catalog:
DSNTIJTC (Db2 Installation and Migration).
If the CATMAINT UPDATE SCHEMA, CATMAINT period of time that spans the failure.
UPDATE VCAT or CATMAINT UPDATE OWNER utility • SVC dump (or system dump), taken to SYS1.DUMPxx
terminated prematurely, run it again to complete any data set, as result of an operator-initiated dump
remaining catalog updates. command or SLIP trap exit.
Check for related messages and codes, such as • SYSPRINT output, including JCL, for the application
SQLCODE -904, DSNT501I, or DSNU590I. program or batch job, and system messages that
Related tasks
Migration step 18: Start Db2 12 (Db2 sent to SYSPRINT.
Installation and Migration)
Migration step 19: Tailor Db2 12 catalog:
archive tapes.
DSNTIJTC (Db2 Installation and Migration)
Installation step 16: Tailor the Db2 catalog: 00C900A8
DSNTIJTC (Db2 Installation and Migration)
CATMAINT (Db2 Utilities)
The table space, index, or partition could not be
Related information
started because of a failure to acquire the lock. Activity
-904 on the table space, index, or partition must quiesce
UNSUCCESSFUL EXECUTION CAUSED BY AN before the START DB ACCESS(FORCE) command can
UNAVAILABLE RESOURCE. REASON reason- acquire the necessary lock.
System action
DSNU590I (Db2 Messages) The START operation is not performed.
00C900A7 User response

Wait for all activity on the table space, index, or
Explanation partition to complete before reissuing the START
At allocation of a bound plan or a bound package, a command.
lock inconsistency is detected. A Db2 internal bind
error is probably responsible for this condition. The Problem determination
plan or the package cannot be allocated.
The requested operation is not performed. Message
DSNI002I is issued. If the problem persists after
System action all activity on the table space, index, or partition
The plan or the package is not allocated. A DSNT501I completes, gather diagnostic information to pursue the
message is issued and an SQLCODE -923 is returned problem.
to the application. SYS1.LOGREC contains information in the variable
System programmer response area (SDWA). Significant fields for this code are:
Re-bind the plan or the package. suspect an error in Db2, you might need to report
(Collecting data).

• Console output from the system on which the job and reporting the problem, see Collecting diagnostic
was run, and a listing of the SYSLOG data set for the data (Collecting data).
executing IFCEREP1. • SVC dump (or system dump), taken to SYS1.DUMPxx
• SYSPRINT output, including JCL, for the application command or SLIP trap exit.
were issued. Make sure that MSGLEVEL=(1,1) on the • Listing of SYS1.LOGREC data set, obtained by
JOB statement so that all diagnostic information is executing IFCEREP1.
sent to SYSPRINT. • SYSPRINT output, including JCL, for the application
• Db2 log output, including any Db2 recovery log program or batch job, and system messages that
archive tapes. were issued. Make sure that MSGLEVEL=(1,1) on the
Related tasks sent to SYSPRINT.
Starting a table space or index space that has • Db2 log output, including any Db2 recovery log
restrictions (Db2 Administration Guide) archive tapes.
Related reference
-START DATABASE (Db2) (Db2 Commands) 00C900AA
Related information
DSNI002I (Db2 Messages) Explanation
The table space or index space could not be stopped
00C900A9 because it is indoubt.

An attempt was made to allocate a resource that is The STOP operation is not performed.
deferred.
User response
System action
Resolve the indoubt unit of recovery (UR) using the
The allocation process is not allowed. RECOVER INDOUBT command.

Determine the reason for which the resource was Message DSNI003I is issued. For more information,
deferred and take the appropriate action to correct refer to the description of this message. If the problem
the problem. Such actions include issuing the START persists after all indoubts with locks on the table
DATABASE command or running the RECOVER, space/index space are resolved, gather diagnostic
REBUILD INDEX, or LOAD REPLACE utility. information to pursue the problem.
Problem determination recording area (VRA) of the system diagnostic work
The requested operation is not performed. An area (SDWA). Significant fields for this code are:
SQLCODE -904 is issued. You might also receive VRARRK13, VRARRK14, and VRARRK15. If you
message DSNT500I or DSNT501I. For more suspect an error in Db2, you might need to report
information, refer to the SQL return code or to the the problem. For information about identifying and
description of the DSNT500I or DSNT501I message. reporting the problem, see Collecting diagnostic data
SYS1.LOGREC contains information in the variable (Collecting data).
recording area (VRA) of the system diagnostic work Collect the following diagnostic items:
VRARRK13, VRARRK14, and VRARRK15. • Console output from the system on which the job

• SVC dump (or system dump), taken to SYS1.DUMPxx DDL, GRANT/REVOKE, INSERT, DELETE, UPDATE, or
data set, as result of an operator-initiated dump MERGE. Db2 issues SQLCODE -904 in conjunction with
command or SLIP trap exit. this message. You can also find more information in
• Listing of SYS1.LOGREC data set, obtained by the description for message DSNT501I, which Db2
executing IFCEREP1. issues along with this reason code.
• SYSPRINT output, including JCL, for the application Additionally, a tracker Db2 does not allow the START
program or batch job, and system messages that DATABASE command to perform LPL/GRECP recovery.
were issued. Make sure that MSGLEVEL=(1,1) on the If you attempt a START DATABASE command on a
JOB statement so that all diagnostic information is tracker Db2, Db2 will issue message DSNI005I with
sent to SYSPRINT. this reason code.
, 00C900AD
00C900AB
Explanation
Explanation An attempt was made to access a resource that is in
the REORG pending state.
An attempt was made to access a resource that is in
the restart pending state.
System action
System action The use of the resource is not allowed.
The use of the resource is not allowed.
System programmer response Use the REORG utility with SHRLEVEL(NONE) PART
n1:n2 to resolve the REORG pending state. The
Use the DISPLAY THREAD TYPE(POSTPONED) to following methods can be used to resolve the REORG
determine the status of the resource. pending state:
Use the RECOVER POSTPONED command if recover • REORG SHRLEVER(NONE) PART (m:n)
has not already been started.
• LOAD REPLACE tablespace
Problem determination • DROP tablespace
The requested operation is not performed because

the table space might be in an inconsistent state. An
SQLCODE -904 is issued. The requested operation is not performed because
the table space might be in an inconsistent state.
00C900AC SQLCODE -904 is issued.
Explanation 00C900AE
The Db2 subsystem currently serves as a remote site

Explanation
tracker system. Users cannot have write access for
tracker systems, and a tracker Db2 will not allow the An attempt was made to allocate or access an index
use of any SQL statement that requires write access. that is in the rebuild pending status.

Db2 cannot process the operation. The use of the object is not allowed.

None. Determine whether the REBUILD utility should be run
to complete recovering the object.
A tracker Db2 does not allow the use of any
SQL statement that requires write access, such as

Determine when the resource is available for use and The requested operation is not performed because the
rerun the job. index page is in an inconsistent state. An SQLCODE
-904 is issued and message DSNT408I is issued. For
Problem determination more information, refer to the SQL return code in SQL
return codes, or to the description of the DSNT408I
The requested operation is not performed because the message in Db2 Messages.
index may be in an inconsistent state. An SQLCODE
-904 and/or message DSNT501I and/or message
DSNI005I is issued.
Collect the following diagnostic items: data (Collecting data).
• Console output from the system on which the job Collect the following diagnostic items:
executing IFCEREP1.
. data set, as result of an operator-initiated dump
Related reference
REBUILD-pending status (Db2 Utilities) • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Related information
-904 • SYSPRINT output, including JCL, for the application
UNSUCCESSFUL EXECUTION CAUSED BY AN program or batch job, and system messages that
UNAVAILABLE RESOURCE. REASON reason- were issued. Make sure that MSGLEVEL=(1,1) on the
code, TYPE OF RESOURCE resource-type, AND JOB statement so that all diagnostic information is
RESOURCE NAME resource-name sent to SYSPRINT.
DSNT501I (Db2 Messages) 00C900B0

Explanation
00C900AF
While formatting log records in response to a READS
request for IFCID 0306, the Db2 database manager
Explanation could not format a log record to match the row format
An attempt was made to decompress a compressed that was current when the log record was written. This
index page when moving the page to the bufferpool. situation might occur for one of the following reasons:
The compressed index page was in an inconsistent • A schema-changing ALTER TABLE statement was
state. issued, but no subsequent insert or update operation
was issued. The alter operation generates a higher
System action version number, but there is no insert or update
operation to trigger an update to the system page.
The decompression that was requested is not
performed. • An ALTER TABLE statement performed an update
operation, but the update was not correctly
registered in the table's system pages.
Operator response
• After the REORG utility was run on a table space, a
Notify the system programmer. READS request for IFCID 0306 was still processing
the log records that were written before REORG was
System programmer response run. Running REORG had removed all system pages
except the system page for the current version of
Recover the index page listed in the DSNT408I the table space. However, when the Db2 database
message and rerun the job. If the job is still manager processed the READS request, it attempted
unsuccessful, then recover the entire index and rerun to retrieve system pages that existed before REORG
the job. If the job is still unsuccessful, then rebuild the was run.
index.

When this code is returned in the output from a READS The operation is not allowed.
request for IFCID 0306, log records are returned, but
the data in the log records does not reflect the table User response
space format that was current when the log records
were written. Drop the index or alter the column data type, and then
rebuild the index.
If a replication product maintains the current and
previous versions of the table definition, and the PTF 00C900B3
for Db2 APAR PI93252 is applied, the replication
program converts the log record's data to the version
Explanation
that was current at the time the log record was written.
The partition number is not in the valid range for the
System programmer response table space during a system page insert.
If a schema change prevents replication from starting

System action
or continuing, and a replication product does not
maintain the current and previous versions of the table SQLCODE -904 is returned to the user with this reason
definition, try the following actions: code.
• Apply the PTF for Db2 APAR PI93252, if it is not
already applied. User response
• Update the source table definition in the replication Correct the problem and resubmit the job. If you
product. suspect an error in Db2, you might need to report
• Remap the source table in the replication product. the problem. For information about identifying and
Refer to the documentation for the replication product (Collecting data).
for details.
Related information
-904
Collect the following diagnostic items: UNAVAILABLE RESOURCE. REASON reason-
period of time that spans the failure. 00C900BA
Explanation
• Listing of SYS1.LOGREC data set, obtained by A request for a drain lock for the resource identified
executing IFCEREP1. by NAME in messages DSNT500I and DSNT501I could
not be granted. The request waited for a period longer
Related concepts than the maximum specified by the installation.
Restarting replication after schema changes
Requests for claims might also receive this code
Related information because claims sometimes need to wait for drain
00C900A2 locks.
00C900B2
System action
Explanation The requested action is not performed. The Data
Manager function that detected this condition returns
Access to the index is not allowed if the index is 'resource not available' to its caller.
defined with the DESC attribute on a VARBINARY
column or a column with a distinct type that is based
on a VARBINARY data type. Drop the index or alter System programmer response
the column data type to a compatible data type such See SQLCODE -913 or -911 and/or message
as CHAR FOR BIT DATA, VARCHAR FOR BIT DATA or DSNT501I, which accompany this abend reason code.
BINARY, and then rebuild the index.


Wait for all jobs that hold a drain lock on the resource SQL return code -904 and/or message DSNT500I is
in an incompatible state to complete before reissuing issued. For more information, refer to the explanation
the failing statement. To display drain locks, issue of message DSNT500I.
a DISPLAY DB LOCKS command. In order to avoid
00C900BE
a potential deadlock, the application should either
commit or roll back to the previous COMMIT.
Explanation
Problem determination Db2 is unable to acquire a lock on a resource because
Collect the following diagnostic items: a Db2 subsystem in the Db2 data sharing group
holds an incompatible retained lock on that resource.
• Console output from the system on which the job Retained locks are locks that persist across Db2
was run, and a listing of the SYSLOG data set for the abnormal terminations. After a successful restart of a
period of time that spans the failure. Db2 member, retained locks can continue to exist for
• SVC dump (or system dump), taken to SYS1.DUMPxx that member until all postponed abort threads have
data set, as result of an operator-initiated dump been processed.
executing IFCEREP1. The requested action is not performed. SQLCODE -904
• SYSPRINT output, including JCL, for the application is issued. A 'resource not available' code is returned to
program or batch job, and system messages that the user. This reason code and the resource name are
were issued. Make sure that MSGLEVEL=(1,1) on the returned in the cursor table (CT) and made available to
JOB statement so that all diagnostic information is the user in the SQLCA.
sent to SYSPRINT.
• Definitions of views and tables involved in the error. Problem determination
00C900BC SYS1.LOGREC contains information in the variable
Explanation area (SDWA). Significant fields for this code are:
The statement depleted the record identifier (RID)
storage available. 00C900BF

The requested action is not performed. Db2 is unable to obtain a lock because IRLM detected
an 'out of record list' storage condition. The record list
is that part of the coupling facility lock structure that
Operator response contains the 'modify locks' (those locks that would be
Notify the system programmer. retained in case of a failure).

Restructure the SQL statement so that fewer RIDs SQLCODE -904 is returned to the user with this reason
are needed. The best way to do this is to split code. This reason code and the resource name are
the statement into two or more SQL statements returned in the cursor table (CT) and made available
equivalent to the original statement. Also, in some to the user in the SQLCA. If it is active, an IFCID 0021
cases, increasing the virtual storage might eliminate trace record is written and might contain additional
the times when storage is depleted. diagnostic information.

If this becomes a prevalent problem, you will need to Use of the object is not allowed.
redistribute the coupling facility lock structure storage
resource to make more room for the record list. You Operator response
can do this in one of two ways:
Determine when the REBUILD utility should be run
• Issue a rebuild.
to complete recovering the object. Only the logical
• Dynamically change the lock structure size. partitions marked as rebuild pending need to be
Related concepts recovered.
Changing the size of the lock structure (Db2
Data Sharing Planning and Administration) User response
Lock structure size (Db2 Installation and Determine when the resource is available for use and
Migration) rerun the job.
Related information
-904 Problem determination
UNAVAILABLE RESOURCE. REASON reason- The requested operation is not performed because the
code, TYPE OF RESOURCE resource-type, AND index might be in an inconsistent state. An SQLCODE
RESOURCE NAME resource-name -904 or message DSNT501I is issued. For more
information, refer to the SQL return code in Part 1,
00C900C0 “SQL codes,” on page 1, or to the description of the
DSNT501I.
A request for an internal lock could not be granted.
The request waited for a longer period than is allowed.

The request action is not performed. A 'resource not
available' reason code is returned to the caller.
System programmer response data set, as result of an operator-initiated dump
See SQLCODE -911 or -913 and/or message command or SLIP trap exit.
DSNT500I, which accompany this reason code. If you • Listing of SYS1.LOGREC data set, obtained by
suspect an error in Db2, you might need to report executing IFCEREP1.
(Collecting data).
User response sent to SYSPRINT.
If the user is a Db2 utility, rerun or restart the utility. • Copy of the log for this period, so that additional
If it is a Db2 command, reissue the command. Db2 DSN1LOGP reports can be produced for problem
applications should either commit or roll back to the determination.
previous commit, then retry from the commit point.
.
00C900C1
00C900C4
An attempt was made to allocate an index that has one
An attempt was made to insert values into a table
or more logical partitions in a rebuild pending state.
that has a ROWID column with the GENERATED BY
DEFAULT attribute but no index exists to enforce its
uniqueness.

The use of the table is not allowed.
Create a unique single column index for the ROWID period of time that spans the failure.
column.
Problem determination command or SLIP trap exit.
The requested operation is not performed. An • Listing of SYS1.LOGREC data set, obtained by
SQLCODE -904 is issued. executing IFCEREP1.
Related concepts Related reference
ROWID data type (Introduction to Db2 for z/OS) CHECK DATA (Db2 Utilities)
Related tasks Related information
Specifying direct row access by using row IDs -904
(Db2 Application programming and SQL) UNSUCCESSFUL EXECUTION CAUSED BY AN
Providing a unique key for a table (Db2 UNAVAILABLE RESOURCE. REASON reason-
Application programming and SQL) code, TYPE OF RESOURCE resource-type, AND
Related information RESOURCE NAME resource-name
-904 DSNT500I (Db2 Messages)
UNSUCCESSFUL EXECUTION CAUSED BY AN DSNT501I (Db2 Messages)
code, TYPE OF RESOURCE resource-type, AND 00C900C6
DSNT501I (Db2 Messages) Explanation
00C900C5 Db2 detected an uncommitted read or write claim on
an index being altered in the same commit scope.
When you use the PIECESIZE or COPY clause with the
Explanation ALTER INDEX statement, then you need to have the
An attempt was made to access a table space that is in read or write claim committed BEFORE you complete
the auxiliary check pending state (ACHKP). the operation.
PIECESIZE does not allow an uncommitted write or
System action read claim on the index.
The operation is not allowed. Db2 returns 'resource COPY, set to YES or NO, does not allow an
not available' to its invoker. uncommitted write on the index.
Commit or rollback all changes to the index before
System programmer response using ALTER INDEX with one of these clauses.
Use the CHECK DATA utility to identify the invalid

LOBs. Use the SQL UPDATE statement to replace the System action
invalid LOBs or the SQL DELETE statement to remove The ALTER INDEX statement is not allowed.
the rows with the invalid LOBs. After rectifying all
invalid LOBs, run CHECK DATA again to clear the
ACHKP state from the table space. System programmer response
The requested operation is not performed and
Problem determination SQLCODE -904 is issued. For more information, refer
to the SQLCODE in "Section 2. SQL Return Codes".
An SQLCODE -904 is issued. Message DSNT500I or Commit or rollback changes to the index and retry the
message DSNT501I might also be issued. ALTER INDEX statement.

The requested operation is not performed and After being expanded to process triggers, a row has
SQLCODE -904 is issued. For more information, refer grown too large to fit into a 32K page of a workfile.
to the SQL return code in "Section 2. SQL Return
Codes." System action
00C900C7 Db2 does not perform the requested operation.

The requested function was either: Drop and re-create triggers to use less LOB columns as
• not supported by the current release or maintenance transition variables, or eliminate the use of the ROWID
level of Db2, or column as a transition variable. For a table with LOB
columns or a ROWID column whose row size is very
• deactivated by a modified the system parameters.
close to 32K, it may not be possible to use transition
In the former case, the NAME field of the tables with triggers.
accompanying message indicates the required level
of maintenance. In the latter case, the NAME field
indicates the deactivating system parameter.
Db2 does not perform the requested operation. Db2
System action issues SQLCODE -904, and may also issue message
DSNT500I or DSNT501I.
The requested action is not performed.
Collect the following information:
To permit the use of the function, take the appropriate
actions according to the situation. Apply the indicated
maintenance, migrate to the indicated release of Db2, • SVC dump (or system dump), taken to SYS1.DUMPxx
or use an alternate setting for the indicated system data set, as result of an operator-initiated dump
parameter. command or SLIP trap exit.
User response executing IFCEREP1.
Inform the system administrator. • Definitions of table spaces, tables, and indexes
00C900C8
Related information
-904
Explanation UNSUCCESSFUL EXECUTION CAUSED BY AN
Access to the index is disallowed within the same UNAVAILABLE RESOURCE. REASON reason-
commit scope as an ALTER TABLE statement that code, TYPE OF RESOURCE resource-type, AND
alters the key column in the index. If the ALTER RESOURCE NAME resource-name
TABLE statement failed, then commit the changes DSNT500I (Db2 Messages)
to the index and retry the ALTER TABLE statement. DSNT501I (Db2 Messages)
If an INSERT, DELETE, UPDATE, MERGE or SELECT
statement failed, then commit the ALTER and retry the 00C900CB
statement.
Explanation
System action
Resource is unavailable because the resource is in a
The operation is not allowed. refresh pending state.

Commit and then retry the operation. The use of the resource is not allowed.
00C900C9

Db2 does not perform the requested operation Db2 does not perform the requested operation
because the table space or index space might be in because the table space or index space might be in
an inconsistent state. Db2 issues SQLCODE -904. For an inconsistent state. Db2 issues SQLCODE -904. For
more information, refer to the SQL return code, or to more information, refer to the SQL return code or to
the description of the DSNT501I message. the description of the DSNT501I message.
00C900CC 00C900D0
Db2 does not accept the NOBACKOUT request during An attempt was made to access a value in a column
the rollback of a non-global transaction while the with one of the LOB data types (BLOB, CLOB, DBCLOB),
backout of catalog changes is in progress. but the value of the column is no longer valid.

Db2 rejects the NOBACKOUT request. The operation is not allowed. Db2 returns 'resource
Db2 does not perform the requested operation
because the backout in progress must be complete Use the CHECK LOB utility to identify the invalid LOBs.
before the NOBACKOUT request can succeed. Wait for Use update to replace or delete the invalid LOBs.
the backout to complete, then reissue the request.
00C900CD report the problem. For information about identifying
Explanation
Db2 does not accept the NOBACKOUT request during Problem determination
the rollback of a non-global transaction. At least one
of the objects of the transaction is shared by another The requested operation is not performed. An
transaction. SQLCODE -904 is issued. Message DSNT500I or
System action
Db2 rejects the NOBACKOUT request.
Problem determination • SVC dump (or system dump), taken to SYS1.DUMPxx
Db2 does not perform the requested operation data set, as result of an operator-initiated dump
because at least one object involved in the operation is command or SLIP trap exit.
also updated by other active transactions in Db2. Wait • Listing of SYS1.LOGREC data set, obtained by
for the other transactions to finish, then reissue the executing IFCEREP1.
request.
.
00C900CE
Related reference
CHECK LOB (Db2 Utilities)
Explanation
Related information
Resource is unavailable because the resource is in a -904
state that is incompatible with this version of Db2. UNSUCCESSFUL EXECUTION CAUSED BY AN
System action code, TYPE OF RESOURCE resource-type, AND
Db2 does not allow the use of the resource.

00C900D1 The amount of space allowed for processing LOB
values by a subsystem has been exceeded. The
amount of space allowed for each subsystem is 50GB.
Explanation
The amount of space allowed for processing LOB System action
values by a user has been exceeded. The amount of
space allowed per user is 2GB. The operation is not allowed. Db2 returns "resource
not available" to its invoker.
System action
The operation is not allowed. Db2 returns "resource
not available" to its invoker. Monitor applications for storage use by LOBs using
a statistics trace that includes IFCID 0002, or an
accounting trace that includes IFCID 0003. Field
System programmer response QXSTLOBV records the maximum amount of storage
Check the SQL statements in the application for LOB that is used for LOBs.
usage. Monitor the application using a statistics trace
that includes IFCID 0002, or an accounting trace that Problem determination
includes IFCID 0003. Field QXSTLOBV records the
maximum amount of storage that is used for LOBs. The requested operation is not performed. An
message DSNT501I might also be issued.
SQLCODE -904 is issued. Message DSNT500I or • Console output from the system on which the job
message DSNT501I might also be issued. was run, and a listing of the SYSLOG data set for the
• Console output from the system on which the job data set, as result of an operator-initiated dump
was run, and a listing of the SYSLOG data set for the command or SLIP trap exit.
• SVC dump (or system dump), taken to SYS1.DUMPxx executing IFCEREP1.
command or SLIP trap exit. Related concepts
Statistics trace (Db2 Performance)
executing IFCEREP1. Accounting trace (Db2 Performance)
Related information
Related concepts
-904
Statistics trace (Db2 Performance) UNSUCCESSFUL EXECUTION CAUSED BY AN
Accounting trace (Db2 Performance) UNAVAILABLE RESOURCE. REASON reason-
Related information code, TYPE OF RESOURCE resource-type, AND
-904 RESOURCE NAME resource-name
UNSUCCESSFUL EXECUTION CAUSED BY AN DSNT500I (Db2 Messages)
UNAVAILABLE RESOURCE. REASON reason- DSNT501I (Db2 Messages)
RESOURCE NAME resource-name 00C900D6
00C900D2 The number of files that are opened for LOB file
reference variables exceeds the maximum for the
subsystem.

The operation is not completed, and Db2 returns Db2 attempted to insert a row into a table, but the
a 'resource not available' code to the invoker. The hash table space does not have enough space to save
maximum number of LOB file reference variable files the system page.
is controlled by the MAXOFILR subsystem parameter.
System action
User response
SQL code -904 is issued with this reason code.
If possible, increase the value of the MAXOFILR
subsystem parameter. User response
Related concepts
Reorganize the table space that contains the hash
LOB file reference variables (Db2 Application table to make room for system pages.
Related reference Related reference
MAX OPEN FILE REFS field (MAXOFILR REORG TABLESPACE (Db2 Utilities)
subsystem parameter) (Db2 Installation and Related information
Migration) -904
00C900D7 UNAVAILABLE RESOURCE. REASON reason-
Explanation RESOURCE NAME resource-name
A logical page list (LPL) or group buffer pool recovery 00C900DA

pending (GRECP) recovery was attempted on a LOB
table space which was created as LOG NO. Explanation
The number of concurrently held application LOB
System action
locators and held cursors exceeded the maximum limit
The operation is not allowed. (65535).

If you suspect an error in Db2, you might need to The operation fails. Db2 generates a dump.
The requested operation is not performed. Message
DSNI005I is issued.
Related concepts Db2 (for 04E and 04F abends). Availability of this
Use of caching for group buffer pools (Db2 Data dump is dependent on the failing environment.
Related reference 00C900E0
Group buffer pool RECOVER-pending status
(Db2 Utilities) Explanation
Data sharing status descriptions (Db2 Data One of the following values on the header page of the
Sharing Planning and Administration) data set does not match the information in the Db2
Related information catalog table for the same object:
DSNI005I (Db2 Messages) • Database ID (DBID)
00C900D8 • Table space ID (PSID)
• Table ID (OBID)

This problem usually occurs after copying data by Related reference
using DSN1COPY. DSN1COPY (Db2 Utilities)
DEFAULT PARTITION SEGSIZE field (DPSEGSZ
System action subsystem parameter) (Db2 Installation and
Migration)
Db2 returns SQLCODE -904. You cannot access the
CREATE TABLESPACE (Db2 SQL)
data.
Related information
-904
User response UNSUCCESSFUL EXECUTION CAUSED BY AN
Obtain the correct database ID, table space ID, UNAVAILABLE RESOURCE. REASON reason-
or table ID from the catalog table of the target code, TYPE OF RESOURCE resource-type, AND
subsystem. RESOURCE NAME resource-name
Find the DSN1COPY job that might have caused this 00C900E2
error. Ensure that the SYSXLAT DD statement that
is used in that DSN1COPY job contains the correct
IDs for each object to be translated. Then rerun Explanation
DSN1COPY. The table space type on the header page of the data
Related reference set does not match the information in the Db2 catalog
Syntax and options of the DSN1COPY control table for the same object.
statement (Db2 Utilities) This problem usually occurs after copying data by
Related information using DSN1COPY.
-904
UNSUCCESSFUL EXECUTION CAUSED BY AN System action
code, TYPE OF RESOURCE resource-type, AND Db2 returns SQLCODE -904. You cannot access the
RESOURCE NAME resource-name data.
00C900E1 User response

Find the DSN1COPY job that might have caused this
Explanation error and use it to identify the source subsystem.
The segment size (SEGSIZE) value on the header page Ensure that the table space type that is defined in
of the data set does not match the information in the the Db2 catalog on the source subsystem matches the
Db2 catalog table for the same object. type on the target subsystem. Correct any inconsistent
schemas between the two subsystems and rerun
This problem usually occurs after copying data by DSN1COPY.
using DSN1COPY.
Related concepts
System action Table space types and characteristics in Db2 for
z/OS (Db2 Administration Guide)
Db2 returns SQLCODE -904. You cannot access the Related reference
data. DSN1COPY (Db2 Utilities)
Related information
User response -904
Find the DSN1COPY job that might have caused this UNSUCCESSFUL EXECUTION CAUSED BY AN
error and use it to identify the source subsystem. UNAVAILABLE RESOURCE. REASON reason-
Ensure that the SEGSIZE value that is defined in code, TYPE OF RESOURCE resource-type, AND
the Db2 catalog on the source subsystem matches RESOURCE NAME resource-name
the value on the target subsystem. Correct any
inconsistent schemas between the two subsystems 00C900E3
and rerun DSN1COPY.
Related tasks
Explanation
Determining the page size and data set size for The table schema definition or the table version
DSN1PRNT (Db2 Utilities) number in the system page does not match the

information in the Db2 catalog table for the same Explanation
object.
The information for the XML table in the header page
This problem usually occurs after DSN1COPY is used does not match the information in the Db2 catalog
to copy data. for the same object. This problem usually occurs
This code is generated if any of the following situations after copying data from one subsystem to another
occur: subsystem by using DSN1COPY.
• The information in the catalog indicates that there

are fewer columns in the table than are within the System action
rows of the table. Db2 returns SQLCODE -904. You cannot access the
• The version number is the same within the page set data.
and the catalog, one or more columns does not have
the same data type or length. User response
• The version of the table recorded in the catalog is
Find the DSN1COPY job that caused this error and use
higher than the version number of the row, one or
it to identify the source subsystem. Ensure that the
more columns does not have the same data type or
definition of the XML table on the source subsystem
length as indicated in the catalog, and conversion
matches the definition on the target subsystem.
of the column page set data rows to match the
definition in the catalog is not supported. Related information
-904
System action UNSUCCESSFUL EXECUTION CAUSED BY AN
Db2 returns SQLCODE -904. You cannot access the code, TYPE OF RESOURCE resource-type, AND
data. RESOURCE NAME resource-name
User response 00C900EF
Find the DSN1COPY job that might have caused this

error, and use it to identify the source subsystem.
Explanation
Run REPAIR CATALOG TEST to obtain additional The page size value on the header page of the data
information. Additional information may be obtained set does not match the information in the Db2 catalog
for diagnosing the problem by running REPAIR table for the same object. This problem usually occurs
CATALOG TEST. Ensure that the table schema after copying data by using DSN1COPY.
definition that is defined in the Db2 catalog on the
source subsystem matches the definition on the target
System action
subsystem. Correct any inconsistent schemas, and
rerun DSN1COPY. After the data is copied to the target Db2 returns SQLCODE -904. You cannot access the
subsystem, run the REPAIR CATALOG utility to correct data.
most version number inconsistencies.
DSN1COPY (Db2 Utilities) Find the DSN1COPY job that might have caused this
Syntax and options of the REPAIR control error and use it to identify the source subsystem.
statement (Db2 Utilities) Ensure that the PAGESIZE value that is defined in
Related information the Db2 catalog on the source subsystem matches
-904 the value on the target subsystem. Correct any
UNSUCCESSFUL EXECUTION CAUSED BY AN inconsistent schemas between the two subsystems
UNAVAILABLE RESOURCE. REASON reason- and rerun DSN1COPY.
code, TYPE OF RESOURCE resource-type, AND Related information
-904
00C900E4
00C90101

Explanation within the source control module (CSECT) where the
abend was issued.
The data manager detected an internal error within
Db2. Possible causes for this error include: SYS1.LOGREC contains information in the variable
• Improper migration or fall back procedures. area (SDWA). Significant fields for this abend code
• The Db2 directory and Db2 catalog have been are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and
restored to different points in time. VRARRK9. The name of the CSECT involved is given
• A table space was restored improperly. in VRARRK5. The full CSECT name given in the dump
title.
• An error in internal Db2 control structures or code.
The csect-name value in the associated message can
indicate possible causes or actions:
System action
DSNGxxxx
A record is written to SYS1.LOGREC, and an SVC dump If the csect-name value begins with DSNG,
is requested. regardless of the xxxx portion of the name, make
a copy of DSNDB01.DBD01, DSNDB01.SCT02, and
Operator response DSNDB01.DSNSCT02 on tape with DSN1COPY.
This might be a large copy.
the job was run for the period of time spanning DSNIDBMF:5016
the failure. Save this output for use in problem An object is already in UTUT status, and a utility is
determination. trying to place UTUT status on the same object.
The operation is denied with an abend. Two
possible causes for this condition are:
• SYSUTILX was re-initialized and the pending
If you suspect an error in Db2, you might need to states were not resolved for each object by
report the problem. For information about identifying running the appropriate utility.
data (Collecting data). • Two utilities ran against the same object with
UTUT status.
Notify the system programmer. • Console output from the system on which the job
If this abend occurred while processing data in one or Db2 (04E and 04F abends).
more pages, message DSNI014I is issued to identify • Listing of SYS1.LOGREC data set, obtained by
each page involved. In general, the data in these executing IFCEREP1.
pages is valid. However, if problems are reported that
repeatedly involve the same pages or if the same • Detailed description of events immediately prior to
pages are reported by other abends, analyze the set and during the abend.
of pages specified. • SYSPRINT output, including JCL, for the application
Run the CHECK INDEX utility to determine the extent
of index inconsistency if:
• The page type indicated in message DSNI014I is sent to SYSPRINT.
index. • Db2 log output, including any Db2 recovery log
• The page type indicated in message DSNI014I is archive tapes.
data. • Db2 REPAIR dump of the pages identified in
• An index is defined on a table in the indicated page DSNI014I messages.
set. • CHECK utility output.
The LOC keyword in the dump title gives the load- Related reference
module.csect-name:qualifier of the location where the
CHECK INDEX (Db2 Utilities)
abend occurred. The value of qualifier is a unique,
4-digit hexadecimal number that identifies the place Related information

ABEND codes associated with DSN1COPY • Dump of the index or table space that failed.
misuse • SYSPRINT output, including JCL, for the application
Several of the 00C9... codes are frequently program or batch job, and system messages that
associated with improper use of the DSN1COPY were issued. Make sure that MSGLEVEL=(1,1) on the
utility. JOB statement so that all diagnostic information is
sent to SYSPRINT.
00C90102
00C90103
Explanation
Explanation
An inconsistent page was detected. This has been
caused by a Db2 internal error. Bad data was returned from either the edit or the
validation exit.
System action
System action
is requested. A record is written to SYS1.LOGREC, and an SVC dump
is requested.
report the problem. For information about identifying If you suspect an error in Db2, you might need to
and reporting the problem, see Collecting diagnostic report the problem. For information about identifying
data (Collecting data). and reporting the problem, see Collecting diagnostic
recording area (VRA) of the system diagnostic SYS1.LOGREC contains the same diagnostic
work area (SDWA). Significant fields for this code information in the variable recording area (VRA) as
are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and in abend reason code '00C90101'. Refer to the table
VRARRK9. accompanying that abend reason code for details.
In addition, the following general purpose registers The '00C90103' abend reason code was issued
(GPRs) contain the indicated diagnostic information: because one of the checks described in the following
list failed:
GPR
Content • Save first and last byte of the input record. On return
2 from exit, see if either group has been modified. If
Address of the page set block (PB) so, abend.
3 • Check length of edited data. If greater than
Address of the log record, if any maximum allowed for this row, or less than one,
abend.
8
Address of the buffer block (BB) • Store a special character in the first byte past the
end of the output area (place for edit procedure to
9
put edited or (original unedited) row), to make sure
Address of the page buffer
the exit doesn't overrun this area. On return, check if
Collect the following diagnostic items: it is still the same special character. If not, abend.
• Console output from the system on which the job SYS1.LOGREC contains information in the variable
was run, and a listing of the SYSLOG data set for the recording area (VRA) of the system diagnostic
period of time that spans the failure. work area (SDWA). Significant fields for this code
• Dynamic dump, taken to SYS1.DUMPxx data set, by are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and
Db2 (04E and 04F abends). VRARRK9.
• Listing of SYS1.LOGREC data set, obtained by 00C90105

executing IFCEREP1.
• Listing of Db2 log output.

Explanation Also, refer to Appendix H, “ABEND codes associated
with DSN1COPY misuse,” on page 1385 for further
An inconsistent page was detected. This has been information on DSN1COPY misuse.
caused by a Db2 internal error.
A record is written to SYS1.LOGREC, an SVC dump period of time that spans the failure.
is requested, and the page will be scheduled
for automatic recovery. If automatic recovery is • Dynamic dump, taken to SYS1.DUMPxx data set, by
successful, message DSNB215I is issued. If automatic Db2 (04E and 04F abends).
recovery fails, message DSNI012I is issued, and an • Listing of SYS1.LOGREC data set, obtained by
abend '04E' with reason code 00C90102 will occur. executing IFCEREP1.
Note: If the resource required for automatic recovery • Listing of Db2 log output.
is in use, automatic recovery will be delayed until the • Dump of the index or table space that failed.
resource is available.
System programmer response were issued. Make sure that MSGLEVEL=(1,1) on the
Check whether an application issues an ALTER TABLE
sent to SYSPRINT.
statement and an INSERT statement in the same
commit scope. In such cases, you might resolve the 00C90106
situation by adding a COMMIT statement between the
ALTER TABLE and INSERT statements.
Explanation
report the problem. For information about identifying The entry is not found for a table space that is
and reporting the problem, see Collecting diagnostic being set for deferred restart. An error in Db2 logic is
data (Collecting data). probably responsible for this condition.

SYS1.LOGREC contains information in the variable A record is written to SYS1.LOGREC, an SVC dump is
recording area (VRA) of the system diagnostic requested, and the Db2 restart is terminated.
work area (SDWA). Significant fields for this code
are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and System programmer response
VRARRK9. Exceptions to the table definitions of the
VRA fields are:
• VRARRK5 is the name of the module that called the and reporting the problem, see Collecting diagnostic
check page routine that detected the error in the data (Collecting data).
page.
• VRARRK6 identifies the error in the page. Problem determination
The following general purpose registers (GPRs) contain Collect the following diagnostic items:
the indicated diagnostic information:
GPR was run, and a listing of the SYSLOG data set for the
Content period of time that spans the failure.
2 • Dynamic dump, taken to SYS1.DUMPxx data set, by
Address of the page set block (PB) Db2 (04E and 04F abends).
3 • Listing of SYS1.LOGREC data set, obtained by
Address of the log record, if any executing IFCEREP1.
8 • SYSPRINT output, including JCL, for the application
Address of the buffer block (BB) program or batch job, and system messages that
9 were issued. Make sure that MSGLEVEL=(1,1) on the
Address of the page buffer JOB statement so that all diagnostic information is
sent to SYSPRINT.

• Db2 log output, including any Db2 recovery log application is allowed to continue without notification
archive tapes. of the error.
00C90107
At commit phase 1, a nonzero write intent count was and reporting the problem, see Collecting diagnostic
detected. An error in Db2 logic is probably responsible data (Collecting data).
for this condition.
System action
A record is written to SYS1.LOGREC, an SVC dump is
requested. The thread is aborted. • Console output from the system on which the job
If you suspect an error in Db2, you might need to Db2 (04E and 04F abends).
and reporting the problem, see Collecting diagnostic • Listing of SYS1.LOGREC data set, obtained by
data (Collecting data). executing IFCEREP1.
• Detailed description of events immediately prior to
and during the abend.
Collect the following diagnostic items: program or batch job, and system messages that
• Console output from the system on which the job were issued. Make sure that MSGLEVEL=(1,1) on the
was run, and a listing of the SYSLOG data set for the JOB statement so that all diagnostic information is
period of time that spans the failure. sent to SYSPRINT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by • Db2 log output, including any Db2 recovery log
Db2 (04E and 04F abends). archive tapes.
• Listing of SYS1.LOGREC data set, obtained by 00C90109
executing IFCEREP1.
• Detailed description of events immediately prior to Explanation
At deallocate, a nonzero read intent count or write
• SYSPRINT output, including JCL, for the application intent count was detected. An error in Db2 logic is
program or batch job, and system messages that probably responsible for this condition.
sent to SYSPRINT. System action
• Db2 log output, including any Db2 recovery log A record is written to SYS1.LOGREC, and a SVC dump
archive tapes. is requested. The thread is deallocated normally.
00C90108
At commit phase 2, a nonzero read intent count or
write intent count was detected. An error in Db2 logic
is probably responsible for this condition.
System action
A record is written to SYS1.LOGREC, and a SVC
dump is requested. The thread is committed and the • Console output from the system on which the job

• Dynamic dump, taken to SYS1.DUMPxx data set, by • Dynamic dump, taken to SYS1.DUMPxx data set, by
Db2 (04E and 04F abends). Db2 (04E and 04F abends).
• Listing of SYS1.LOGREC data set, obtained by • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1. executing IFCEREP1.
• Detailed description of events immediately prior to 00C9010C
• SYSPRINT output, including JCL, for the application Explanation
were issued. Make sure that MSGLEVEL=(1,1) on the The data manager detected an internal error within
JOB statement so that all diagnostic information is Db2. This error might be in an internal Db2 control
sent to SYSPRINT. structure or code.
archive tapes. System action
00C9010B A record is written to SYS1.LOGREC, and an SVC dump
is requested.
Explanation
The data manager detected an internal error within
Db2. This error might be in an internal Db2 control If you suspect an error in Db2, you might need to
structure or code. report the problem. For information about identifying
System action
A record is written to SYS1.LOGREC, and an SVC dump User response
is requested.
report the problem. For information about identifying SYS1.LOGREC contains information in the variable
and reporting the problem, see Collecting diagnostic recording area (VRA) of the system diagnostic area
data (Collecting data). (SDWA). Significant fields for this code are:
• VRARRK5, which contains the name of the control
User response section that issued this code
Notify the system programmer. • VRARRK6
• VRARRK7
Problem determination • VRARRK8
SYS1.LOGREC contains information in the variable • VRARRK9.
recording area (VRA) of the system diagnostic area Collect the following diagnostic items:
(SDWA). Significant fields for this code are:
• VRARRK5, which contains the name of the control was run, and a listing of the SYSLOG data set for the
section that issued this code period of time that spans the failure.
• VRARRK6 • Dynamic dump, taken to SYS1.DUMPxx data set, by
• VRARRK7 Db2 (04E and 04F abends).
• VRARRK8 • Listing of SYS1.LOGREC data set, obtained by
• VRARRK9. executing IFCEREP1.
Collect the following diagnostic items: 00C9010D


The data manager detected an internal error within If you suspect an error in Db2, you might need to
Db2. This error might be in an internal Db2 control report the problem. For information about identifying
structure or code. and reporting the problem, see Collecting diagnostic
System action
User response
is requested. Notify the system programmer.

If you suspect an error in Db2, you might need to SYS1.LOGREC contains information in the variable
report the problem. For information about identifying recording area (VRA) of the system diagnostic area
and reporting the problem, see Collecting diagnostic (SDWA). Significant fields for this code are:
section that issued this code
User response • VRARRK6
Notify the system programmer. • VRARRK7
• VRARRK8
Problem determination • VRARRK9.
recording area (VRA) of the system diagnostic area
(SDWA). Significant fields for this code are: • Console output from the system on which the job
• VRARRK6
• VRARRK7
• VRARRK8 executing IFCEREP1.
• VRARRK9. 00C9010F
• Console output from the system on which the job Explanation
was run, and a listing of the SYSLOG data set for the The data manager detected an internal error within
period of time that spans the failure. Db2. This error might be in an internal Db2 control
• Dynamic dump, taken to SYS1.DUMPxx data set, by structure or code.
executing IFCEREP1.
00C9010E is requested.

The data manager detected an internal error within If you suspect an error in Db2, you might need to
Db2. This error might be in an internal Db2 control report the problem. For information about identifying
structure or code. and reporting the problem, see Collecting diagnostic
System action
User response
is requested. Notify the system programmer.

Problem determination identifying and reporting the problem, see Collecting
recording area (VRA) of the system diagnostic area
(SDWA). Significant fields for this code are: Problem determination
• VRARRK5, which contains the name of the control The DBD in use at the time of the abend is inconsistent
section that issued this code in storage and may be inconsistent on DASD. Since the
nature and extent of the damage done to the DBD is
• VRARRK6 not immediately known, an analysis of the entire DBD
• VRARRK7 must be done.
• VRARRK8 The inconsistency may be due to:
• VRARRK9.
• Incomplete recovery of Db2 catalog and/or Db2
Collect the following diagnostic items: directory.
• Console output from the system on which the job • Invalid restore of Db2 catalog and/or Db2 directory
was run, and a listing of the SYSLOG data set for the to a prior point in time.
period of time that spans the failure. • A conditional restart that bypassed recovery of a Db2
• Dynamic dump, taken to SYS1.DUMPxx data set, by catalog page set or a Db2 directory page set.
Db2 (04E and 04F abends). • A Db2 internal error.
• Listing of SYS1.LOGREC data set, obtained by Collect the following diagnostic items:
executing IFCEREP1.
Explanation • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
The data manager detected an inconsistent data
condition. This may be caused by an inconsistency • Unformatted DSN1PRNT output of the
in either the Db2 catalog or the Db2 directory. In DSNDB01.DBD01 page set. Locate the inconsistent
this case, the OBD for the requested OBID cannot DBD in the DSNDB01.DBD01 page set by using
be located in the database descriptor (DBD). The the method described in Finding a DBD in a dump
DBD in storage may be inconsistent. Specifically, the (Diagnosing Db2 problems).
OBDDMAP(OBID) array element should contain an • The results of the following SQL statements, where
offset into the DBD where the OBD should be located. dbid is the DBID of the damaged DBD:
However, in this case the OBD expected was not at the
indicated offset. SELECT * FROM SYSIBM.SYSINDEXES
WHERE DBID=dbid ORDER BY OBID;
To prevent further damage and possible loss of data, SELECT * FROM SYSIBM.SYSINDEXES
WHERE DBID=dbid ORDER BY ISOBID;
the inconsistency must be corrected before any further
SQL access is attempted to this database. SELECT * FROM SYSIBM.SYSTABLES
SELECT * FROM SYSIBM.SYSTABLESPACE
System action WHERE
SELECT *
DBID=dbid ORDER BY OBID;
FROM SYSIBM.SYSTABLESPACE
WHERE DBID=dbid ORDER BY PSID;
is requested.
Use the results to compare the information in the
Db2 catalog with the DBD. Determine which OBDs
Operator response are inconsistent with the Db2 catalog. Analyze the
DBD by using the procedure in Analyzing a DBD
(Diagnosing Db2 problems).
• DSN1LOGP output with DBID (1) OBID (1F) covering
System programmer response the period of time in which the DBD inconsistency
Determine which databases were being used when might have occurred. This period of time is
the error occurred. Prevent further SQL access to the approximately from the time of the abend back
databases. If you suspect an error in Db2, you might to the time when the Db2 catalog and DBD were
need to report the problem. For information about believed to be consistent.

• Copy of the log for this period, so that additional • Listing of SYS1.LOGREC data set, obtained by
DSN1LOGP reports can be produced for problem executing IFCEREP1.
determination. • Unformatted DSN1PRNT output of the
00C90111 DSNDB01.DBD01 page set. Locate the inconsistent
DBD in the DSNDB01.DBD01 page set by using
the method described in Finding a DBD in a dump
Explanation (Diagnosing Db2 problems).
The data manager detected an inconsistent data • The results of the following SQL statements, where
condition. In this case, the OBD for the requested dbid is the DBID of the damaged DBD:
OBID does not exist. This may be caused by an
inconsistency in either the Db2 catalog or the Db2 SELECT * FROM SYSIBM.SYSINDEXES
directory. Specifically, the OBDDMAP(OBID) entry is SELECT * FROM SYSIBM.SYSINDEXES
zero rather than an offset to an OBD within the DBD. WHERE DBID=dbid ORDER BY ISOBID;
To prevent further damage and possible loss of data, SELECT * FROM SYSIBM.SYSTABLES
the inconsistency must be corrected before any further SELECT * FROM SYSIBM.SYSTABLESPACE
SQL access is attempted to this database. WHERE DBID=dbid ORDER BY OBID;
SELECT * FROM SYSIBM.SYSTABLESPACE
System action
Use the results to compare the information in the
A record is written to SYS1.LOGREC, and an SVC dump Db2 catalog with the DBD. Determine which OBDs
is requested. are inconsistent with the Db2 catalog. Analyze the
DBD by using the procedure in Analyzing a DBD
Operator response (Diagnosing Db2 problems).
Notify the system programmer. • DSN1LOGP output with DBID (1) OBID (1F) covering
the period of time in which the DBD inconsistency
might have occurred. This period of time is
System programmer response approximately from the time of the abend back
Determine which databases were being used when to the time when the Db2 catalog and DBD were
the error occurred. Prevent further SQL access to the believed to be consistent.
databases. If you suspect an error in Db2, you might • Copy of the log for this period, so that additional
need to report the problem. For information about DSN1LOGP reports can be produced for problem
identifying and reporting the problem, see Collecting determination.
00C90112
Explanation
Since the Db2 directory does not agree with the Db2
catalog, either of these may be inconsistent. Since the The data manager detected an inconsistent data
nature and extent of the inconsistency between the condition. There may be more than one object with
Db2 catalog the DBD is not immediately known, an the same OBID in the Db2 Catalog. To prevent further
analysis of the entire DBD must be done. damage and possible loss of data, the inconsistency
must be corrected before any further SQL access is
The inconsistency may be due to: attempted to this database.
• Incomplete recovery of Db2 catalog and/or Db2
directory. System action
• Invalid restore of Db2 catalog and/or Db2 directory A record is written to SYS1.LOGREC and an SVC dump
to a prior point in time. is requested.
• A conditional restart that bypassed recovery of a Db2
catalog page set or a Db2 directory page set. Operator response
• A Db2 internal error.

System programmer response to the time when the Db2 catalog and DBD were
believed to be consistent.
Determine which databases were being used when
the error occurred. Prevent further SQL access to the • Copy of the log for this period, so that additional
databases. If you suspect an error in Db2, you might DSN1LOGP reports can be produced for problem
need to report the problem. For information about determination.
identifying and reporting the problem, see Collecting .
00C90120
Explanation
Since the extent of this inconsistency is not
immediately known, an analysis of the entire DBD The data manager detected an internal error within
must be done. Db2. This error might be in an internal Db2 control
structure or code.
The inconsistency may be due to:
• Incomplete recovery of the Db2 Catalog and/or the System action
Db2 Directory.
• Invalid restore of the Db2 Catalog and/or the Db2 is requested.
Directory to a prior point in time.
• A conditional restart that bypassed recovery of a Db2 System programmer response
catalog page set or a Db2 directory page set.
• A Db2 internal error. If you suspect an error in Db2, you might need to
Collect the following diagnostic items: and reporting the problem, see Collecting diagnostic
• Console output from the system on which the job data (Collecting data).
• Listing of SYS1.LOGREC data set, obtained by Notify the system programmer.
executing IFCEREP1.
• Unformatted DSN1PRNT output of the Problem determination
DSNDB01.DBD01 page set. Locate the inconsistent
DBD in the DSNDB01.DBD01 page set by using SYS1.LOGREC contains information in the variable
the method described in Finding a DBD in a dump recording area (VRA) of the system diagnostic area
(Diagnosing Db2 problems). (SDWA). Significant fields for this code are:
• The results of the following SQL statements, where • VRARRK5, which contains the name of the control
dbid is the DBID of the damaged DBD: section that issued this code
SELECT * FROM SYSIBM.SYSINDEXES

• VRARRK6
WHERE DBID=dbid ORDER BY OBID; • VRARRK7
SELECT * FROM SYSIBM.SYSINDEXES
WHERE DBID=dbid ORDER BY ISOBID; • VRARRK8
SELECT * FROM SYSIBM.SYSTABLES • VRARRK9.
SELECT * FROM SYSIBM.SYSTABLESPACE Collect the following diagnostic items:
SELECT * FROM SYSIBM.SYSTABLESPACE • Console output from the system on which the job
Use the results to compare the information in the period of time that spans the failure.
Db2 catalog with the DBD. Determine which OBDs • Dynamic dump, taken to SYS1.DUMPxx data set, by
are inconsistent with the Db2 catalog. Analyze the Db2 (04E and 04F abends).
DBD by using the procedure in Analyzing a DBD • Listing of SYS1.LOGREC data set, obtained by
(Diagnosing Db2 problems). executing IFCEREP1.
• DSN1LOGP output with DBID (1) OBID (1F) covering
the period of time in which the DBD inconsistency 00C90121
might have occurred. This period of time is
approximately from the time of the abend back

The data manager detected an internal error within Collect the console output from the system on which
Db2. This error might be in an internal Db2 control the job was run for the period of time spanning
structure or code. the failure. Save this output for use in problem
determination.
System action
is requested. If you suspect an error in Db2, you might need to
User response
data (Collecting data). Notify the system programmer.

Notify the system programmer. This abend can occur in migration/remigration when
some necessary migration/remigration steps are
Problem determination skipped. It indicates that some Db2 activity occurred
or was pending after the last complete checkpoint on
SYS1.LOGREC contains information in the variable the prior system. If this was the cause of the problem,
recording area (VRA) of the system diagnostic area it can be corrected by falling back to the prior version/
(SDWA). Significant fields for this code are: release long enough to bring Db2 up, then bring it
down while conforming to all migration/remigration
steps. Pay specific attention to resolving all indoubts
and to performing a stop mode quiesce.
• VRARRK6
Related concepts
• VRARRK7
Migrating to Db2 12 (Db2 Installation and
• VRARRK8 Migration)
• VRARRK9.
00C90205
period of time that spans the failure. The data manager detected an inconsistent data
condition. In this case, a row obtained from an index
entry does not point to a valid row in a data page. The
error is probably caused by an extra index entry, but it
• Listing of SYS1.LOGREC data set, obtained by could also result from a table update not being redone
executing IFCEREP1. when it should have been.
00C90124
System action
Explanation A record is written to SYS1.LOGREC, and an SVC dump
is requested.
An attempt was made to apply prior-version/release
Db2 log records other than checkpoint records.
Operator response
System action Collect the console output from the system on which
is requested.
determination.

System programmer response • SYSPRINT output, including JCL, for the application
If you suspect an error in Db2, you might need to were issued. Make sure that MSGLEVEL=(1,1) on the
report the problem. For information about identifying JOB statement so that all diagnostic information is
and reporting the problem, see Collecting diagnostic sent to SYSPRINT.
archive tapes.
User response
• CHECK utility output.
Notify the system programmer. • Db2 REPAIR dump of the pages identified in
DSNI013I messages.
00C90206
Message DSNI013I is issued to identify the index
page. It identifies the database name, table space Explanation
name, and index space name. This message is issued
for all pages in use at the time of the abend. Within The data manager detected an inconsistent data
this group of pages, at least one page is involved in condition. In this case, a row that should be pointed to
the inconsistency. The other pages were present at the by an index does not have an index entry. The error is
time of the abend. probably caused by a missing index entry, but it could
also be caused by a table update that was not backed
Run the CHECK utility to determine the extent of index
out when it should have been.
inconsistency if:
• The page type indicated in message DSNI013I is System action
index
• The page type indicated in message DSNI013I is
is requested.
data
• There is an index defined on a table in the indicated
page set. Operator response
The LOC keyword in the dump title gives the Collect the console output from the system on which
Load-module.CSECT:qualifier of the location where the job was run for the period of time spanning
the abend occurred. 'Qualifier' is a unique, 4-digit the failure. Save this output for use in problem
hexadecimal number that identifies the place within determination.
the source module (CSECT) where the abend was
issued. System programmer response
SYS1.LOGREC contains information in the variable If you suspect an error in Db2, you might need to
recording area (VRA) of the system diagnostic work report the problem. For information about identifying
area (SDWA). Significant fields for this abend code and reporting the problem, see Collecting diagnostic
are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and data (Collecting data).
VRARRK9.
The name of the CSECT involved is given in VRARRK5. User response
The full CSECT name given in the dump title.
Message DSNI013I is issued to identify the data
pages. It identifies the database name, table space
• Dynamic dump, taken to SYS1.DUMPxx data set, by name, and index space name. This message is issued
Db2 (04E and 04F abends). for all pages in use at the time of the abend. Within
• Listing of SYS1.LOGREC data set, obtained by this group of pages, at least one page is involved in
executing IFCEREP1. the inconsistency. The other pages were present at the
time of the abend.
and during the abend. Run the CHECK utility to determine the extent of index
inconsistency if:

• The page type indicated in message DSNI014I is System action
index
• The page type indicated in message DSNI014I is is requested.
data
• There is an index defined on a table in the indicated
Operator response
page set.
The LOC keyword in the dump title gives the
Load-module.CSECT:qualifier of the location where
the abend occurred. 'Qualifier' is a unique, 4-digit
determination.
hexadecimal number that identifies the place within
issued. System programmer response
Refer to Appendix H, “ABEND codes associated If you suspect an error in Db2, you might need to
with DSN1COPY misuse,” on page 1385 for further report the problem. For information about identifying
information on DSN1COPY misuse. and reporting the problem, see Collecting diagnostic
area (SDWA). Significant fields for this abend code User response
are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and Notify the system programmer.
VRARRK9.
The name of the CSECT involved is given in VRARRK5. Problem determination
Collect the following diagnostic items: pages. It also identifies the database name and the
• Console output from the system on which the job table space name. This message is issued for all
was run, and a listing of the SYSLOG data set for the pages in use at the time of the abend. Within this
period of time that spans the failure. group of pages, at least one page is involved in the
inconsistency. The other pages were present at the
time of the abend.
• Listing of SYS1.LOGREC data set, obtained by The LOC keyword in the dump title gives the
executing IFCEREP1. Load-module.CSECT: qualifier of the location where
• Detailed description of events immediately prior to hexadecimal number that identifies the place within
and during the abend. the source module (CSECT) where the abend was
• SYSPRINT output, including JCL, for the application issued.
area (SDWA). Significant fields for this abend code
sent to SYSPRINT.
are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and
• Db2 log output, including any Db2 recovery log VRARRK9.
archive tapes.
The name of the CSECT involved is given in VRARRK5.
• CHECK utility output. The full CSECT name given in the dump title.
• Db2 REPAIR dump of the pages identified in
DSNI013I messages.
00C90207
The data manager detected an inconsistent data Db2 (04E and 04F abends).
condition. In this case, a pointer record does not point • Listing of SYS1.LOGREC data set, obtained by
to a valid overflow record. The pointer record, the executing IFCEREP1.
overflow record, or the page that contains the pointer
or overflow record is in error.

• SYSPRINT output, including JCL, for the application SYS1.LOGREC contains information in the variable
program or batch job, and system messages that recording area (VRA) of the system diagnostic work
were issued. Make sure that MSGLEVEL=(1,1) on the area (SDWA). Significant fields for this abend code
JOB statement so that all diagnostic information is are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and
sent to SYSPRINT. VRARRK9.
• Db2 log output, including any Db2 recovery log The name of the CSECT involved is given in VRARRK5.
archive tapes. The full CSECT name given in the dump title.
• Db2 REPAIR dump of the pages identified in Collect the following diagnostic items:
DSNI013I messages.
The data manager detected an inconsistent data Db2 (04E and 04F abends).
condition. In this case, the subpage directory of an • Listing of SYS1.LOGREC data set, obtained by
index leaf page indicates that a given search key does executing IFCEREP1.
not belong to any of the subpages. Either this leaf • Detailed description of events immediately prior to
page is the index tree or the nonleaf portion of the and during the abend.
index tree lead to this leaf page as the one that should
contain the given key. • SYSPRINT output, including JCL, for the application
System action JOB statement so that all diagnostic information is
A record is written to SYS1.LOGREC, and an SVC dump sent to SYSPRINT.
is requested. • Db2 log output, including any Db2 recovery log
archive tapes.
System programmer response • DSN1COPY-generated copy of the index space or
table space identified in the DSNI013I messages on
If you suspect an error in Db2, you might need to tape.
and reporting the problem, see Collecting diagnostic 00C90211
Explanation
User response
Notify the system programmer. condition. In this case, a row is missing a column that
is not nullable and does not allow default values.
System action
page. It also identifies the database name and A record is written to SYS1.LOGREC, and an SVC dump
index space name. This message is issued for all is requested.
pages in use at the time of the abend. Within this
group of pages, at least one page is involved in the System programmer response
inconsistency. The other pages were present at the
time of the abend. If you suspect an error in Db2, you might need to
Load module.CSECT:qualifier of the location where
hexadecimal number that identifies the place within
the source module (CSECT) where the abend was User response
issued. Notify the system programmer.
Refer to Appendix H, “ABEND codes associated
information on DSN1COPY misuse.

Problem determination page other than the root. (Db2 removes empty pages
from the index tree.)
Message DSNI013I is issued to identify the data page.
It also identifies the database name and table space
name. This message is issued for all pages in use at System action
the time of the abend. Within this group of pages, at A record is written to SYS1.LOGREC, and an SVC dump
least one page is involved in the inconsistency. The is requested.
other pages were present at the time of the abend.
The LOC keyword in the dump title gives the System programmer response
the abend occurred. 'Qualifier' is a unique, 4-digit If you suspect an error in Db2, you might need to
hexadecimal number that identifies the place within report the problem. For information about identifying
the source module (CSECT) where the abend was and reporting the problem, see Collecting diagnostic
issued. data (Collecting data).

recording area (VRA) of the system diagnostic work User response
area (SDWA). Significant fields for this abend code Notify the system programmer.
VRARRK9.
The full CSECT name given in the dump title. Message DSNI013I is issued to identify the index
leaf page. It also identifies the database name and
Collect the following diagnostic items: index space name. This message is issued for all
• Console output from the system on which the job pages in use at the time of the abend. Within this
was run, and a listing of the SYSLOG data set for the group of pages, at least one page is involved in the
period of time that spans the failure. inconsistency. The other pages were present at the
time of the abend.
Db2 (04E and 04F abends). Run the CHECK utility to determine the extent of index
inconsistency if:
executing IFCEREP1. • The page type indicated in message DSNI014I is
• Detailed description of events immediately prior to index.
and during the abend. • The page type indicated in message DSNI014I is
• SYSPRINT output, including JCL, for the application data.
program or batch job, and system messages that • There is an index defined on a table in the indicated
were issued. Make sure that MSGLEVEL=(1,1) on the page set.
sent to SYSPRINT.
• Db2 log output, including any Db2 recovery log the abend occurred. 'Qualifier' is a unique, 4-digit
archive tapes. hexadecimal number that identifies the place within
• Db2 REPAIR dump of the pages identified in the source module (CSECT) where the abend was
DSNI013I messages. issued.
• DSN1COPY-generated copy, on tape, of the page Refer to Appendix H, “ABEND codes associated
set that contains the Db2 directory. Alternatively, with DSN1COPY misuse,” on page 1385 for further
request a dump (produced by the REPAIR utility, information on DSN1COPY misuse.
DSN1COPY, or DSN1PRNT) of the DBD for each
database identified in the DSNI013I messages.
00C90212 area (SDWA). Significant fields for this abend code
VRARRK9.
Explanation
The data manager detected an inconsistent data The full CSECT name given in the dump title.
condition. In this case, there is an empty index leaf

• Console output from the system on which the job least one page is involved in the inconsistency. The
was run, and a listing of the SYSLOG data set for the other pages were present at the time of the abend.
• Dynamic dump, taken to SYS1.DUMPxx data set, by Load module.CSECT: qualifier of the location where
Db2 (04E and 04F abends). the abend occurred. 'Qualifier' is a unique, 4-digit
• Listing of SYS1.LOGREC data set, obtained by hexadecimal number that identifies the place within
executing IFCEREP1. the source module (CSECT) where the abend was
issued.
and during the abend. Refer to Appendix H, “ABEND codes associated
• SYSPRINT output, including JCL, for the application with DSN1COPY misuse,” on page 1385 for further
program or batch job, and system messages that information on DSN1COPY misuse.
were issued. Make sure that MSGLEVEL=(1,1) on the SYS1.LOGREC contains information in the variable
JOB statement so that all diagnostic information is recording area (VRA) of the system diagnostic work
sent to SYSPRINT. area (SDWA). Significant fields for this abend code
• Db2 log output, including any Db2 recovery log are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and
archive tapes. VRARRK9.
• CHECK utility output. The name of the CSECT involved is given in VRARRK5.
• DSN1COPY-generated copy of the index space or The full CSECT name given in the dump title.
table space identified in the DSNI013I messages on Collect the following diagnostic items:
tape.
. was run, and a listing of the SYSLOG data set for the
00C90213
Explanation
The data manager detected an inconsistent data executing IFCEREP1.
condition. In this case, a row has an unexpected
OBID stored in its prefix. A possible cause is that the • Detailed description of events immediately prior to
table space was restored (via DSN1COPY or similar and during the abend.
tool) improperly. For example, the wrong data set was • SYSPRINT output, including JCL, for the application
copied for the given table space. program or batch job, and system messages that
System action
sent to SYSPRINT.
A record is written to SYS1.LOGREC, and an SVC dump • Db2 log output, including any Db2 recovery log
is requested. archive tapes.
• Db2 REPAIR dump of the pages identified in
System programmer response DSNI013I messages.
If you suspect an error in Db2, you might need to • DSN1COPY-generated copy, on tape, of the page
report the problem. For information about identifying set that contains the Db2 directory. Alternatively,
and reporting the problem, see Collecting diagnostic request a dump (produced by the REPAIR utility,
data (Collecting data). DSN1COPY, or DSN1PRNT) of the DBD for each
User response .

Message DSNI013I is issued to identify the data page. The data manager detected a condition of inconsistent
It also identifies the database name and table space data. The description of the index in the index OBD
name. This message is issued for all pages in use at does not match the attributes of an index page. The
the time of the abend. Within this group of pages, at problems consists of one of the following conditions:

• IPPNUNI does not equal OBDKNUNI, • Console output from the system on which the job
• IPPTLTH does not equal OBDKLEN, was run, and a listing of the SYSLOG data set for the
• IPPOLTH does not equal OBDLENO, or
• If the page is a leaf page, the segmentation flag Db2 (04E and 04F abends).
or number of subpages conflict (IPPNLPG does
not equal OBDINLPG or IPPSEGM conflicts with • Listing of SYS1.LOGREC data set, obtained by
OBDINLPG). executing IFCEREP1.
The index space may have been improperly restored
by using DSN1COPY or the wrong data set may have
been copied for the given index. • SYSPRINT output, including JCL, for the application
A record is written to SYS1.LOGREC, and an SVC dump sent to SYSPRINT.
is requested. • Db2 log output, including any Db2 recovery log
archive tapes.
System programmer response • Db2 REPAIR dump of the pages identified in
If you suspect an error in Db2, you might need to DSNI013I messages.
report the problem. For information about identifying • Db2 REPAIR dump of the header page (page 0) for
and reporting the problem, see Collecting diagnostic each index identified in the DSNI013I messages.
data (Collecting data). • DSN1COPY-generated copy, on tape, of the page
set that contains the Db2 directory. Alternatively,
User response request a dump (produced by the REPAIR utility,
DSN1COPY, or DSN1PRNT) of the DBD for each
Notify the system programmer. database identified in the DSNI013I messages.
.
00C90215
Message DSNI013I will be issued for each index page.
It identifies the database, and the index name. This
message is issued for all pages in use at the time of Explanation
the abend. Within this group of pages, at least one The data manager detected a condition of inconsistent
page is involved in the inconsistency. The other pages data. The index manager subcomponent has been
were present at the time of the abend. passed a key with a key length not equal to the key
The LOC keyword in the dump title gives the length in pages of the index. The index space may have
Load-module.CSECT:qualifier of the location where been improperly restored by using DSN1COPY or the
the abend occurred. 'Qualifier' is a unique, 4-digit wrong data set may have been copied for the given
hexadecimal number that identifies the place within index.
issued. System action
Refer to Appendix H, “ABEND codes associated A record is written to SYS1.LOGREC, and an SVC dump
with DSN1COPY misuse,” on page 1385 for further is requested.
SYS1.LOGREC contains information in the variable System programmer response
area (SDWA). Significant fields for this abend code If you suspect an error in Db2, you might need to
are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and report the problem. For information about identifying
VRARRK9. and reporting the problem, see Collecting diagnostic
The full CSECT name given in the dump title. A rebuild index or recover index will restore the index
to a correct condition.

executing IFCEREP1 and ISDASDA0.
• DSN1COPY-generated copy of the table and index,
taken before any recovery is performed.
.
Message DSNI013I will be issued for each index
page. It identifies the database, the index name. This 00C90216
message is issued for all pages in use at the time of
the abend. Within this group of pages, at least one Explanation
page is involved in the inconsistency. The other pages
were present at the time of the abend. The data manager has detected an inconsistent data
condition. Either the length of a record in a table space
The LOC keyword in the dump title gives the is longer than the maximum-defined record length
Load-module.CSECT:qualifier of the location where as defined in the Db2 directory or a variable-length
the abend occurred. 'Qualifier' is a unique, 4-digit column has a longer length than the length defined in
hexadecimal number that identifies the place within the Db2 directory.
issued.
System action
with DSN1COPY misuse,” on page 1385 for further A record is written to SYS1.LOGREC, and an SVC dump
information on DSN1COPY misuse. is requested.

area (SDWA). Significant fields for this abend code If you suspect an error in Db2, you might need to
are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and report the problem. For information about identifying
VRARRK9. and reporting the problem, see Collecting diagnostic
The name of the CSECT involved is given in VRARRK5. data (Collecting data).
User response
• Dynamic dump, taken to SYS1.DUMPxx data set, by Message DSNI013I is issued to identify the data page
Db2 (04E and 04F abends). that contains the record that is longer than allowed by
• Detailed description of events immediately prior to its corresponding record definition. This could occur if
and during the abend. the Db2 directory was recovered to a previous point,
allowing new object creations (with a shorter record
length) to be created having record identifiers identical
to objects previously created in the table space. Also
the table space may have been improperly restored by
using DSN1COPY or the wrong data set may have been
sent to SYSPRINT.
copied for the given table space.
archive tapes. Refer to Appendix H, “ABEND codes associated
• Db2 REPAIR dump of the pages identified in information on DSN1COPY misuse.
DSNI013I messages.
• Db2 REPAIR dump of the header page (page 0) for
each index identified in the DSNI013I messages. • Console output from the system on which the job
• DSN1COPY-generated copy, on tape, of the page was run, and a listing of the SYSLOG data set for the
set that contains the Db2 directory. Alternatively, period of time that spans the failure.
request a dump (produced by the REPAIR utility, • Dynamic dump, taken to SYS1.DUMPxx data set, by
DSN1COPY, or DSN1PRNT) of the DBD for each Db2 (04E and 04F abends).

executing IFCEREP1.
Message DSNI013I is issued to identify the space
• SYSPRINT output, including JCL, for the application map page that contains the bad segment entry. The
program or batch job, and system messages that database name and table space name will also be
were issued. Make sure that MSGLEVEL=(1,1) on the identified.
sent to SYSPRINT. SYS1.LOGREC contains information in the variable
area (SDWA). Significant fields for this abend code
archive tapes.
• Db2 REPAIR dump of the pages identified in VRARRK9.
DSNI013I messages.
• DSN1COPY-generated copy, on tape, of the page The full CSECT name given in the dump title.
set that contains the Db2 directory. Alternatively,
request a dump (produced by the REPAIR utility, Refer to Appendix H, “ABEND codes associated
DSN1COPY, or DSN1PRNT) of the DBD for each with DSN1COPY misuse,” on page 1385 for further
database identified in the DSNI013I messages. information on DSN1COPY misuse.
• Detailed description of events prior to the abend, Collect the following diagnostic items:
such as recovery or other activity affecting
DSNDB01.DBD01 or the subject table spaces.
• Definitions of table spaces, tables, and indexes period of time that spans the failure.
involved in the error. The object identifiers (OBIDs)
identified with each table in the table space with the
error can be obtained from SYSIBM.SYSTABLES.
. • SYSPRINT output, including JCL, for the application
00C90218 program or batch job, and system messages that
Explanation sent to SYSPRINT.
The data manager detected an inconsistent data • Definitions of table spaces, tables, and indexes
condition in a segmented table space. In this case, an involved in the error.
unallocated segment was found on a segment chain.
.

is requested. Explanation
Operator response condition in a segmented table space. In this case,
an allocated segment was found on a wrong segment
Collect the console output from the system on which chain (that is, a segment chain contains a segment
the job was run for the period of time spanning that belongs to a different table).
determination.
System action
System programmer response A record is written to SYS1.LOGREC and an SVC dump
is requested.
data (Collecting data). Collect the console output from the system on which
User response the failure. Save this output for use in problem
determination.

If you suspect an error in Db2, you might need to A record is written to SYS1.LOGREC, and an SVC dump
report the problem. For information about identifying is requested.
data (Collecting data). Operator response
User response
Notify the system programmer. the failure. Save this output for use in problem
determination.
Message DSNI013I is issued to identify the space
map page that contains the bad segment entry. The If you suspect an error in Db2, you might need to
database name and table space name will also be report the problem. For information about identifying
identified. and reporting the problem, see Collecting diagnostic
area (SDWA). Significant fields for this abend code User response
VRARRK9.
The name of the CSECT involved is given in VRARRK5. Problem determination
Message DSNI013I is issued to identify the data page
Refer to Appendix H, “ABEND codes associated that contains the bad data record. The database name
with DSN1COPY misuse,” on page 1385 for further and table space name will also be identified.
Collect the following diagnostic items: recording area (VRA) of the system diagnostic work
• Console output from the system on which the job area (SDWA). Significant fields for this abend code
was run, and a listing of the SYSLOG data set for the are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and
period of time that spans the failure. VRARRK9.
• SVC dump (or system dump), taken to SYS1.DUMPxx The name of the CSECT involved is given in VRARRK5.
data set, as result of an operator-initiated dump The full CSECT name given in the dump title.
• SYSPRINT output, including JCL, for the application with DSN1COPY misuse,” on page 1385 for further
program or batch job, and system messages that information on DSN1COPY misuse.
JOB statement so that all diagnostic information is Collect the following diagnostic items:
sent to SYSPRINT. • Console output from the system on which the job
• Definitions of table spaces, tables, and indexes was run, and a listing of the SYSLOG data set for the
involved in the error. period of time that spans the failure.
. • SVC dump (or system dump), taken to SYS1.DUMPxx
00C9021A command or SLIP trap exit.
condition in a segmented table space. In this case, a
sent to SYSPRINT.
data page contains a record which belongs to a table
that has not been allocated for the page. • Definitions of table spaces, tables, and indexes
00C9021B

Explanation JOB statement so that all diagnostic information is
sent to SYSPRINT.
condition in a segmented table space. In this case, • Definitions of table spaces, tables, and indexes
the space map page indicates a data page that is not involved in the error.
empty exists. However, the data page is either not 00C9021C
formatted by the data manager or it is beyond the
highest VSAM formatted area.
Explanation
System action While running a utility, the data manager detected an
inconsistent data condition. A row was encountered
A record is written to SYS1.LOGREC and an SVC dump that is not represented by a record OBD in the
is requested. database descriptor (DBD). This abend may indicate
an internal Db2 error, but most likely occurs due to a
Operator response user error. Possible user errors may include:
Collect the console output from the system on which • Data from a Db2 subsystem was copied to another
the job was run for the period of time spanning Db2 subsystem incorrectly. This is the most common
the failure. Save this output for use in problem error.
determination. • DSNDB01.DBD01 was regressed to a time prior to a
table being created.
System programmer response If you suspect an error in Db2, you might need to
If you suspect an error in Db2, you might need to report the problem. For information about identifying
report the problem. For information about identifying and reporting the problem, see Collecting diagnostic
and reporting the problem, see Collecting diagnostic data (Collecting data).
System action
User response A record is written to SYS1.LOGREC and an SVC dump
Notify the system programmer. is requested. The dump is required in the event that
the problem is determined to be a Db2 internal error.
Message DSNI013I is issued to identify the
inconsistent data page and its covering space map Determine if improper procedures were used to
page. The database name and table space name will restore the table space or DBD that would lead to the
also be identified. inconsistency.

User response
area (SDWA). Significant fields for this abend code Notify the system programmer.
VRARRK9.
Message DSNI013I will be issued.
If a Db2 internal error is indicated, collect the
following diagnostic items:
• DSN1COPY of the user table space.
period of time that spans the failure. • DSN1COPY of DSNDB01.DBD01.
• SVC dump (or system dump), taken to SYS1.DUMPxx Also collect the following diagnostic items:
• SYSPRINT output, including JCL, for the application period of time that spans the failure.

• Listing of SYS1.LOGREC data set, obtained by If a Db2 internal error is indicated, collect the
executing IFCEREP1. following diagnostic items:
• Detailed description of events immediately prior to • Console output from the system on which the job
and during the abend. was run, and a listing of the SYSLOG data set for the
• SYSPRINT output, including JCL, for the application period of time that spans the failure.
program or batch job, and system messages that • Dynamic dump, taken to SYS1.DUMPxx data set, by
were issued. Make sure that MSGLEVEL=(1,1) on the Db2 (04E and 04F abends).
sent to SYSPRINT.
executing IFCEREP1.
archive tapes.
• Definitions of table spaces, tables, and indexes defined the failing index or table.
00C9021D operation occurred.
Explanation and during the abend.
During a LOAD/REORG utility or termination of a • SYSPRINT output, including JCL, for the application
utility, the data manager detected an inconsistent data program or batch job, and system messages that
condition. A space map page was missing from the were issued. Make sure that MSGLEVEL=(1,1) on the
table space. This abend may indicate an internal Db2 JOB statement so that all diagnostic information is
error (caused by the utilities subcomponent passing a sent to SYSPRINT.
bad start position to the data manager), but most likely • Db2 log output, including any Db2 recovery log
occurs due to a user error. Possible causes are that the archive tapes.
table space data set has been deleted and redefined • Definitions of table spaces, tables, and indexes
without Db2 knowing, or that the table space was involved in the error.
incorrectly restored from an improper DSN1COPY of
the table space. • DSN1COPY-generated copy of the index space or
table space identified in the DSNI013I messages on
tape.
System action
00C9021E
is requested. The dump is required in the event that
the problem is determined to be a Db2 internal error. Explanation
System programmer response condition in a segmented table space. An invalid
page was requested. The page number is outside the
Determine if the data set was improperly restored or highest formatted RBA for the page set. Either the
deleted and redefined by the user. If you suspect an segment chain is broken, or the table space has been
error in Db2, you might need to report the problem. truncated. A truncated table space could be a possible
For information about identifying and reporting the user error.
data).
System action
User response A record is written to SYS1.LOGREC, and an SVC dump
is requested.
Operator response
Message DSNI013I will be issued. If the message the job was run for the period of time spanning
information describes page 'xx0001'X of the table the failure. Save this output for use in problem
space, this indicates that the data set was deleted and determination.
redefined without Db2 knowing.

and reporting the problem, see Collecting diagnostic User response

Notify the system programmer. Collect the following diagnostic items:
Problem determination was run and a listing of SYSLOG data set for the
Collect the following diagnostic items: period of time spanning the failure.
• Console output from the system on which the job • Listing of SYS1.LOGREC data set, obtained by
was run, and a listing of the SYSLOG data set for the executing IFCEREP1.
period of time that spans the failure. • SVC dump (or system dump), taken to SYS1.DUMPxx
• Listing of SYS1.LOGREC data set, obtained by data set, as a result of operator initiated dump
executing IFCEREP1. command or SLIP trap exit.
• SVC dump (or system dump), taken to SYS1.DUMPxx • SYSPRINT output, including JCL, for the batch job
data set, as result of an operator-initiated dump and system messages that were issued
command or SLIP trap exit. • Definitions of table spaces, tables, and indexes
• SYSPRINT output, including JCL, for the application involved in the error
program or batch job, and system messages that • Listing of the entire table space
were issued. Make sure that MSGLEVEL=(1,1) on the • Listing of the DBD, obtained by executing UTILITY
JOB statement so that all diagnostic information is DIAGNOSE OBD.
sent to SYSPRINT.
00C90220
Explanation
00C9021F
condition. In this case, free index page cannot be
Explanation
found in the index space. The problem could be
The data manager detected an inconsistent data caused by a problem detected by IRLM, such as out-
condition in a segmented table space. A duplicate of-storage, or some other problem.
first segment block for a table is found during the
rebuilding of the first segment block in a segmented System action
table space. The segment chain may be broken.
is requested.
System action
A record is written to SYS1.LOGREC, and an SVC dump Operator response
is requested.
Operator response
Collect the console output from the system on which determination.
the failure. Save this output for use in problem System programmer response
determination.

User response Operator response
Notify the system programmer. Collect the console output from the system on which
Problem determination the failure. Save this output for use in problem
determination.
pages. It identifies the database name, table space
name, and index space name. This message is issued
for all pages in use at the time of the abend. Within If you suspect an error in Db2, you might need to
this group of pages, at least one page is involved in report the problem. For information about identifying
the inconsistency. The other pages were present at the and reporting the problem, see Collecting diagnostic
time of the abend. data (Collecting data).
From the console output, determine if resource
unavailable message DSNT500I/DSNT501I was given User response
prior to the abend. If there is and the reason code
given is 00C90092, 00C90093, or 00C90096, then
refer to the description of the appropriate message in
this book for more information. Otherwise, collect the Problem determination
following diagnostic items listed in SYS1.LOGREC contains information in the variable
• Console output from the system on which the job recording area (VRA) of the system diagnostic work
was run, and a listing of the SYSLOG data set for the area (SDWA). Significant fields for this abend code
period of time that spans the failure. are: VRARRK5, VRARRK6, VRARRK7, VRARRK8, and
VRARRK9.
Db2 (04E and 04F abends). Refer to Appendix H, “ABEND codes associated
• Listing of SYS1.LOGREC data set, obtained by with DSN1COPY misuse,” on page 1385 for further
executing IFCEREP1. information on DSN1COPY misuse.
• Detailed description of events immediately prior to Collect the following diagnostic items:
and during the abend. • Console output from the system on which the job
• SYSPRINT output, including JCL, for the application was run, and a listing of the SYSLOG data set for the
program or batch job, and system messages that period of time that spans the failure.
were issued. Make sure that MSGLEVEL=(1,1) on the • Dynamic dump, taken to SYS1.DUMPxx data set, by
JOB statement so that all diagnostic information is Db2 (04E and 04F abends).
sent to SYSPRINT.
• Db2 log output, including any Db2 recovery log program or batch job, and system messages that
archive tapes. were issued. Make sure that MSGLEVEL=(1,1) on the
. Also collect a DSN1COPY output of the tables and JOB statement so that all diagnostic information is
indexes before any recover is performed. sent to SYSPRINT.
00C90221 • Definitions of table spaces, tables, and indexes


condition. In this case, a nonsegmented space map Explanation
page was read for a table space that had been defined While starting Db2, the data manager detected a utility
as segmented. This problem could be caused by in process (UTUT, UTRO or UTRW) state on an object
incorrect use of the DSN1COPY service aid or a Db2 that originated from Version 2 Release 3. This abend
internal problem reading the space map page. might indicate an internal Db2 error, but most likely
occurs because of a user error. A possible user error is
System action a result of not terminating all utilities before migrating
to this release.
is requested.

The -START Db2 command fails. A record is written Determine when the resource is started for read/write
to SYS1.LOGREC and an SVC dump is requested. The access, and rerun the job.
dump is required if the problem is determined to be a
Related reference
Db2 internal error.
SET_REPLICATION function for RRSAF (Db2
System programmer response Related information
Determine if an improper procedure was used to -904
migrate to this release. If the utilities were not UNSUCCESSFUL EXECUTION CAUSED BY AN
terminated before migrating, fall back to Version 2 UNAVAILABLE RESOURCE. REASON reason-
Release 3 and restart Db2. Use the -TERM UTILITY code, TYPE OF RESOURCE resource-type, AND
command to terminate utilities, use the -DISPLAY RESOURCE NAME resource-name
UTILITY command to make sure no utility job is
currently active, stop Db2, and remigrate to this
release. 00C90301

Notify the system programmer. The data manager detected an internal error with Db2
during RID LIST processing. The requested RIDMAP
Problem determination pointer can not be found in the specified CUB control
block.
period of time that spans the failure. A record is written to SYS1.LOGREC and an SVC dump
is requested.
executing IFCEREP1. Collect the console output from the system on which
• Detailed description of events immediately prior to the job was run from the period of time spanning
and during the abend. the failure. Save this output for use in problem
determination.
archive tapes.
00C90224
An attempt was made to allocate a resource for update data (Collecting data).
operations. However, the resource was already started
for read and replication only access. The requested User response
operation is not performed. SQLCODE -904 is issued,
and/or message DSNT501I is issued. Notify the system programmer.

The allocation process is not allowed. Collect the following diagnostic items:
If this reason code appears in message DSNT501I,
determine whether the named resource should be • Dynamic dump, taken to SYS1.DUMPxx data set, by
started for read and replication only access. Db2 (04E and 04F abends).

• SYSPRINT output, including JCL, for the application Collect the following diagnostic items:
• Definitions of table spaces, tables, and indexes • Dynamic dump, taken to SYS1.DUMPxx data set, by
involved in the error. Db2 (04E and 04F abends).
00C90303 executing IFCEREP1.
An attempt to make the database exception table

Explanation
(DBET) consistent failed after an agent failure.
The limit on the space usage of the work file storage
System action by an agent was exceeded. The space usage limit is
determined by the zparm keyword MAXTEMPS.
The Db2 subsystem abends, a record is written to
SYS1.LOGREC, and an SVC dump is requested.
System action
Problem determination The SQL statement was terminated with an SQLCODE
-904 and this reason code.
Restarting the member rebuilds the local DBET.
Analyze SYS1.LOGREC and the dump to determine why
User response
the agent failed and why the attempt to make the
DBET consistent failed. Examine the application and determine why the limit
was exceeded.
00C90304
Explanation
An application used too much work file storage space.
START DATABASE recovery of GRECP cannot proceed Examine the limit set for MAXTEMPS. Adjust the limit
because the recover base RBA value in the header as appropriate.
page for the object is invalid. The following might have
occurred: 00C90306
• The data set was restored from an earlier release
backup that does not have a starting RBA or LRSN in Explanation
the header page.
Db2 detected that Environmental Descriptor Manager
• DSN1COPY RESET utility command. (EDM) real-time statistic (RTS) information cannot be
externalized. The probable cause for this error is that
System action the SYSTSPKG table space is in a state that does
prevents updates.
The GRECP recovery for this object is terminated;
all other objects being recovered by this START
DATABASE command are not affected.
System action
Statistics are discarded because they cannot be
System programmer response externalized.
Use the RECOVER utility without the LOGONLY option. A DSNT500I message is issued to identify the resource
type and reason. Other messages might be issued,
including other instances of DSNT500I. The messages
Problem determination indicate that the EDM RTS cannot be externalized
If you suspect an error in Db2, you might need to because SYSTSPKG is in a state other than update.

User response 00C90603
Make sure that the SYSTSPKG table space is in a state
that does not prevent updates. If it is in a state that Explanation
does not prevent updates and this condition persists, This code is intended for use by IBM Support
collect the information that is identified in the problem personnel as they diagnose problems.
determination section.
00C90611
Explanation
The Security Server was unable to process this row
level, Multilevel Security (MLS) request.
System action
Related tasks
Setting up your system for real-time statistics The requested operation is not performed.
(Db2 Performance)
Related information System programmer response
DSNT500I (Db2 Messages) Refer to the RACROUTE REQUEST=AUTH: Return
codes and reason codes (Security Server RACROUTE
00C90307 Macro Reference) for an explanation of the SAF/RACF
return/reason codes in the resource name, and for
Explanation corrective action advice.
Db2 has detected that Environmental Descriptor 00C90614
Manager (EDM) real-time statistic (RTS) information
cannot be externalized. The probable cause for this
Explanation
error is that the amount of RTS information to be
externalized is greater than what the Db2 subsystem Db2 attempted to load a DBD during Db2 startup in
can handle. deferred mode.

Statistics are discarded because they cannot be Startup continues, and the DBD is not loaded.
externalized.
Message DSNT500I is issued to identify the resource System programmer response
type and reason. Other messages might be issued,
After the Db2 startup, completes, the DBD can be
including other instances of DSNT500I that indicate
loaded or recovered.
that the EDM RTS cannot be externalized because
SYSTSPKG is in a state other than update. 00C9061C

An application tried to access a declared global
Expect that the last used information for the package
temporary table that is in an inconsistent state.
might not be accurate.
A declared global temporary table is marked
inconsistent when both of the following statements
Problem determination are true:
Collect the following diagnostic items: • The table is declared with the NOT LOGGED option.
• Console output from the system on which the job • A must-complete operation such as ROLLBACK
was run, and a listing of the SYSLOG data set for the encounters an unexpected error while processing
period of time that spans the failure. the table. The operation marks the table inconsistent
to prevent the application from further accessing the
Related information table and continues.
System action:

The requested action to access the declared global System action
temporary table (for example, FETCH or INSERT) is not
completed. The statement ends with SQLCODE -904. The utility completes and issues a warning message.

• Check the console log or the job output to identify Reorganize the table space to correct the problem,
the first unexpected error, such as an abend or then run CHECK DATA again.
another SQLCODE, and resolve the error. If you suspect an error in Db2, you might need to
• If the application does not handle the SQLCODE report the problem. For information about identifying
-904 appropriately, modify the application to do so. and reporting the problem, see Collecting diagnostic
.
Related information Related concepts
-904 DSNU messages (Db2 Messages)
UNSUCCESSFUL EXECUTION CAUSED BY AN Related reference
UNAVAILABLE RESOURCE. REASON reason- CHECK DATA (Db2 Utilities)
code, TYPE OF RESOURCE resource-type, AND REORG TABLESPACE (Db2 Utilities)
00C90630
00C9062E
Explanation
Explanation
The CHECK DATA utility identified a record ID (RID)
The CHECK DATA utility identified a record ID (RID) that represents a row that locates a different RID using
that represents a row that cannot be located in the hash key column values.
fixed hash space using hash key column values.
System action
System action
The utility completes and issues a warning message.
The utility completes and issues a warning message.
User response
User response
Reorganize the table space to correct the problem,
Reorganize the table space to correct the problem, then run CHECK DATA again.
then run CHECK DATA again.
Related concepts
Related concepts
DSNU messages (Db2 Messages)
DSNU messages (Db2 Messages)
Related reference
Related reference
CHECK DATA (Db2 Utilities)
CHECK DATA (Db2 Utilities)
00C90635
00C9062F
Explanation:
An attempt was made to allocate to a table space
Explanation partition for update operations. However, the table
The CHECK DATA utility identified a record ID (RID) space partition is in a Persistent Read Only (PRO)
that represents a row that cannot be located in the restricted status, and updates are not allowed. This
hash overflow space using hash key column values to condition occurs as a result of using the REPAIR utility
probe the hash overflow index. to set the PRO restricted status for the purpose of
prohibiting updates.
System action:

The allocation process is not allowed. System programmer response
User response: If the problem persists, you might need to report
Check with the Db2 system administrator and the the problem. For information about identifying and
database administrator. Do not remove the PRO reporting the problem, see Collecting diagnostic data
restricted status without their consent, because (Collecting data).
updates to the data might cause data loss.
The requested operation is not performed. SQL error Collect the following diagnostic items:
code -904 or message DSNT501I is issued. • Console output from the system on which the job
executing IFCEREP1.
was run, and a listing of the SYSLOG data set for the • Diagnostic dumps that are generated
period of time spanning the failure. by the following command: MODIFY
irlmproc,DIAG,PLOCK
data set, as result of an operator-initiated dump Related concepts
command or SLIP trap exit. Physical locks in data sharing (Db2 Data Sharing
• Listing of SYS1.LOGREC data set, obtained by Planning and Administration)
executing IFCEREP1. Related information
• SYSPRINT output, including JCL, for the application -904
program or batch job, and the system messages that UNSUCCESSFUL EXECUTION CAUSED BY AN
were issued. Make sure that MSGLEVEL=(1,1) on the UNAVAILABLE RESOURCE. REASON reason-
JOB statement so that all diagnostic information is code, TYPE OF RESOURCE resource-type, AND
sent to SYSPRINT. RESOURCE NAME resource-name
Related information 00C90637

-904
UNSUCCESSFUL EXECUTION CAUSED BY AN Explanation
code, TYPE OF RESOURCE resource-type, AND A transaction that was waiting for consistency
RESOURCE NAME resource-name between data on two pages was unable to complete
due to resources held by another transaction.
00C90636 System action

The allocation process is not allowed. The requested
Explanation operation is not performed.
Db2 cannot obtain a physical lock (P-lock) because
another member that holds the lock has not User response
responded to the P-lock request.
Determine when the resource is available and run the
job again.
System action
SQLCODE -904 (resource not available) is returned to Problem determination
the user. This reason code and the resource name are
returned in the cursor table (CT) and made available
to the user in the SQLCA. Other Db2 members might • Console output from the system on which the job
produce additional diagnostic information in the form was run, and a listing of the SYSLOG data set for the
of messages, trace records, SYS1.LOGREC entries period of time that spans the failure.
and/or an SVC dump.

• SVC dump (or system dump), taken to SYS1.DUMPxx System action
command or SLIP trap exit. A record is written to SYS1.LOGREC and an SVC dump
is requested.
executing IFCEREP1.
program or batch job, and system messages that If you suspect an error in Db2, you might need to
were issued. Make sure that MSGLEVEL=(1,1) on the report the problem. For information about identifying
JOB statement so that all diagnostic information is and reporting the problem, see Collecting diagnostic
sent to SYSPRINT. data (Collecting data).
• Copy of the log for this period, so that additional
DSN1LOGP reports can be produced for problem Problem determination
determination.
00C906FF page. Run CHECK INDEX on the auxiliary index
followed by CHECK DATA on the base table space in
Explanation order to identify the inconsistencies. See Db2 Utility
Guide and Reference for information about CHECK
A specific table version record was not retrieved from INDEX and CHECK DATA.
the system page because the header page was not
available. This situation typically happens because of
lock contention in a high concurrency environment. • Console output from the system on which the job
SQLCODE -904 is issued, and processing stops.
Operator response • Listing of SYS1.LOGREC data set, obtained by
Notify the system programmer. executing IFCEREP1.
.
00C90D02
Lock contention usually resolves itself. Resubmit the
job. If the problem persists, you might need to report Explanation
reporting the problem, see Collecting diagnostic data The zEnterprise® data compression (zEDC) capability is
(Collecting data). not enabled for accessing the compressed LOB table
space.
Related information
-904
UNSUCCESSFUL EXECUTION CAUSED BY AN System action
UNAVAILABLE RESOURCE. REASON reason- SQLCODE -904 is returned to the user.
RESOURCE NAME resource-name Operator response:
Notify the System programmer.
00C90D01
Explanation Check the availability of the zEDC card for the
Db2 detected an inconsistent condition. An entry in subsystem that returned the SQLCODE.
the auxiliary index was not found. The error is probably Related concepts
caused by not recovering all table spaces in a table
Compressing LOB data (Db2 Performance)
space set to the same point-in-time.
Related reference
Overview and planning of zEnterprise Data
Compression (zEDC)
Requirements for zEnterprise Data Compression

Chapter 9. X'D1......' codes
Reason code identifiers that begin with 00D1 communicate normal and error situations with the recovery
log manager.
For X'D1' codes, Db2 provides the following diagnostic information in the SYS1.LOGREC variable recording
area (VRA) of the SDWA for many of the reason codes:
MODID
Name of module issuing the abend
LEVEL
Change level
COMPONENT
Subcomponent ID
REGISTERS
General purpose registers (GPRs) 0 through 15 at time of abend
00D10010 Related reference
Sample application that uses stand-alone log
Explanation services (Db2 Administration Guide)
The Db2 stand-alone log services OPEN processing 00D10011

macro (DSNJSLR) issues this reason code. The RANGE
parameter on the OPEN request specifies the address
Explanation
of a 12-byte area (if FORMAT=V1) or 20-byte area (if
FORMAT=V2 or is not specified) containing the log RBA The Db2 stand-alone log services OPEN and GET
range to be processed by subsequent GET requests. processing macro (DSNJSLR) issued this reason code.
However, the RBA specified in the second 6 bytes or During the initial processing of a FUNC=OPEN or
10 bytes of the RANGE parameter (which indicates the FUNC=GET request, storage is obtained to contain
end of the log RBA) is less than or equal to the RBA the control blocks and other information required to
specified in the first 6 bytes or 10 bytes of the RANGE process this request. An MVS GETMAIN failed when
parameter (which indicates the start of the log RBA). attempting to obtain the required storage.

In response to the DSNJSLR FUNC=OPEN call, Db2 In response to the DSNJSLR FUNC=OPEN or
places a return code of 8 in register 15 and a reason FUNC=GET call, Db2 places a return code of 8 in
code of 00D10010 in register 0. No abend is issued by register 15 and a reason code of 00D10011 in register
the stand-alone log services CSECT (DSNJRS01), and 0. No abend is issued by the stand-alone log services
no information is written to SYS1.LOGREC data set. CSECT (DSNJRS01), and no information is written to
SYS1.LOGREC data set.
The stand-alone log services program is under the
control of a user-written program that uses the The stand-alone log services program is under the
DSNJSLR macro. The user application program must control of a user-written program that uses the
therefore anticipate and react to a nonzero return code DSNJSLR macro. The user program must therefore
and a nonzero reason code, possibly by terminating anticipate and react to a nonzero return code and
the execution of the user program. a nonzero reason code, possibly by terminating the
execution of the user program.
Correct the RANGE RBA parameter input, and
resubmit the request. In all likelihood, the REGION parameter on the EXEC
statement for the user program is too small. Increase
Related tasks
the REGION size, and resubmit the user program.
Reading log records with OPEN, GET, and CLOSE

Related tasks Explanation
The Db2 stand-alone log services OPEN processing
macro (DSNJSLR) issued this reason code. A VSAM
Related reference OPEN error occurred while opening the bootstrap data
Sample application that uses stand-alone log set (BSDS).
services (Db2 Administration Guide)
00D10012 System action

In response to the DSNJSLR FUNC=OPEN call, Db2
Explanation places a return code of 12 in register 15 and a reason
code of 00D10013 in register 0. No abend is issued by
The Db2 stand-alone log services OPEN processing the stand-alone log services CSECT (DSNJRS01), and
macro (DSNJSLR) issued this reason code. The Job no information is written to SYS1.LOGREC data set.
Control Language (JCL) for the user program that uses
the DSNJSLR macro must specify either the use of the Information about the results of the OPEN request is
bootstrap data set (BSDS) or, in the absence of the also returned in the stand-alone log GET Feedback
BSDS, the active or archive data set(s) that is used Area (SLRF). The VSAM OPEN error return code is
in the processing. The FUNC=OPEN request failed placed in SLRFRG15. The ACB error code (ACBERFLG)
because the BSDS or a log data set is not allocated is placed in SLRFERCD.
for the job. The stand-alone log services program is under the
If ACTIVEn or MxxACTn data sets are used, the control of a user-written program that uses the
supplied DD names must start with the number 1 DSNJSLR macro. The user program must therefore
and increment by 1. For example, you must use anticipate and react to a nonzero return code and
ACTIVE1, ACTIVE2, ACTIVE3, and so on. You cannot a nonzero reason code, possibly by terminating the
use ACTIVE2, ACTIVE7, and ACTIVE9. execution of the user program.

In response to the DSNJSLR FUNC=OPEN call, Db2 Determine the meaning of the VSAM OPEN error
places a return code of 8 in register 15 and a reason returned in SLRFRG15, and the ACB error code
code of 00D10012 in register 0. No abend is issued by returned in SLRFERCD. Take appropriate action, and
the stand-alone log services CSECT (DSNJRS01), and resubmit the FUNC=OPEN request.
no information is written to SYS1.LOGREC data set. Related tasks
The stand-alone log services program is under the Reading log records with OPEN, GET, and CLOSE
control of a user-written program that uses the (Db2 Administration Guide)
DSNJSLR macro. The user program must therefore Related reference
anticipate and react to a nonzero return code and Sample application that uses stand-alone log
a nonzero reason code, possibly by terminating the services (Db2 Administration Guide)
Related information
DFSMS Macro Instructions for Data Sets
Correct the JCL and resubmit the user program. 00D10014
Related tasks
Explanation
(Db2 Administration Guide) The Db2 stand-alone log services OPEN processing
Related reference macro (DSNJSLR) issued this reason code. The Job
Control Language (JCL) associated with the user-
written application determines how access to the Db2
log data is achieved. Access can either be through
DSN1LOGP (Db2 Utilities) the bootstrap data set (BSDS), or through the explicit
inclusion of ddnames in the JCL for the active or
00D10013
archive log data set(s) which are to be examined. If the
BSDS method is used, the user must specify a RANGE
parameter on the FUNC=OPEN call. This reason code

indicates that the user used the BSDS method, but did The stand-alone log services program is under the
not specify the range of RBAs to be examined. control of a user-written program that uses the
DSNJSLR macro. The user program must, therefore,
System action anticipate and react to a nonzero return code and
a nonzero reason code, possibly by terminating the
In response to the DSNJSLR FUNC=OPEN call, Db2 execution of the user program.
places a return code of 8 in register 15 and a reason
the stand-alone log services CSECT (DSNJRS01), and
no information is written to SYS1.LOGREC data set. The procedure for running program DSNJCNVB or
DSNJCNVT includes making a copy of the BSDS before
conversion. Restore the BSDS to the original pre-
control of a user-written program that uses the
conversion copy, and try the conversion again. When
DSNJSLR macro. The user program must therefore
the BSDS data set is successfully converted, rerun the
anticipate and react to a nonzero return code and
original application program.
execution of the user program. Related tasks
System programmer response (Db2 Administration Guide)
Related reference
Two choices are available:
1. Continue to use the BSDS method of access. If this services (Db2 Administration Guide)
choice is made, then the FUNC=OPEN invocation
must specify a range of RBAs to be examined by 00D10016
use of the RANGE parameter.
2. Replace the use of the BSDS method of access. Explanation
This can be done be using explicit archive data set
The Db2 stand-alone log services OPEN processing
ddnames and/or active log data set ddnames in
macro (DSNJSLR) issued this reason code. In the
the JCL used to invoke the user-written application
job control language (JCL) associated with the
program.
user-written application, MxxARCHV and/or MxxACTn
Related tasks DD statements were specified for a Db2 member
Reading log records with OPEN, GET, and CLOSE while MxxBSDS was also specified for the same
(Db2 Administration Guide) member. However, the specification of MxxARCHV and
Related reference MxxACTn DD statements is mutually exclusive with the
specification of MxxBSDS DD statement for the same
member.

In response to DSNJSLR FUNC=OPEN call, Db2 places
Explanation a return code of 12 in register 15 and a reason code
The Db2 stand-alone log services OPEN processing of 00D10016 in register 0. No abend is issued by the
macro (DSNJSLR) issued this reason code. The VSAM stand-alone log services, and no information is written
OPEN of the bootstrap data set was successful but the to SYS1.LOGREC data set.
record format of the BSDS is invalid. An invalid BSDS
is the result of a failure during a prior attempt to run User response
conversion program DSNJCNVB or DSNJCNVT.
Correct the JCL and rerun the job. Specify either
the DD statements for the log data sets (MxxARCHV
System action and MxxACTN) or the DD statement for the BSDS
In response to DSNJSLR FUNC=OPEN call, Db2 places (MxxBSDS) for a given member; do not specify both.
a return code of 12 in register 15 and a reason code Related tasks
of 00D10015 in register 0. No abend is issued by the Reading log records with OPEN, GET, and CLOSE
stand-alone log services CSECT (DSNJRS01), and no (Db2 Administration Guide)
information is written to SYS1.LOGREC data set.
Chapter 9. X'D1......' codes 529

Correct the range specification on the OPEN request,
and rerun the job. If range is specified when reading
00D10017 log records from multiple members, LRSN=YES must
also be specified. Also range must be specified if
GROUP DD or a MxxBSDS (BSDS) DD is specified in
Explanation the JCL.
The Db2 stand-alone log services OPEN processing Related tasks
macro (DSNJSLR) issued this reason code. The job Reading log records with OPEN, GET, and CLOSE
control language (JCL) associated with the user- (Db2 Administration Guide)
written application indicated that the logs from more
Related reference
than one Db2 member were to be read in CI mode.
However, CI mode is allowed only when reading the Sample application that uses stand-alone log
log of a single Db2 system. services (Db2 Administration Guide)
00D10019
System action
In response to DSNJSLR FUNC=OPEN call, Db2 places Explanation
a return code of 12 in register 15 and a reason code
of 00D10017 in register 0. No abend is issued by the The Db2 stand-alone log services OPEN processing
stand-alone log services, and no information is written macro (DSNJSLR) issued this reason code. A VSAM
to SYS1.LOGREC data set. OPEN error occurred while opening the bootstrap data
set (BSDS). The error was determined to be one which
could be corrected by use of an AMS VERIFY, but the
User response VERIFY also failed.
Either remove the CI mode from the OPEN request to
read log records of more than one member or change System action
the JCL to specify only one system's log to read its log
in CI mode. In response to the DSNJSLR FUNC=OPEN call, Db2
Related tasks code of 00D10019 in register 0. No abend is issued by
Reading log records with OPEN, GET, and CLOSE the stand-alone log services CSECT (DSNJRS01), and
(Db2 Administration Guide) no information is written to SYS1.LOGREC data set.
Related reference Information about the results of the OPEN request is
Sample application that uses stand-alone log also returned in the stand-alone log GET Feedback
services (Db2 Administration Guide) Area (SLRF). The VSAM return code from the original
VSAM OPEN error is placed in SLRFRG15. The ACB
00D10018 error code (ACBERFLG) from the ACB used in the
original VSAM OPEN operation is placed in SLRFERCD.
Explanation The stand-alone log services program is under the
The Db2 stand-alone log services OPEN processing control of a user-written program that uses the
macro (DSNJSLR) issued this reason code. In the DSNJSLR macro. The user program must therefore
job control language (JCL) associated with the user- anticipate and react to a nonzero return code and
written application, more than one Db2 system's logs a nonzero reason code, possibly by terminating the
were identified. However, on the OPEN request an RBA execution of the user program.
range was specified. When reading logs from more
than one Db2 system, you cannot specify an RBA System programmer response
range; you must specify an LRSN range.
Determine the meaning of the VSAM OPEN error
returned in SLRFRG15, and the ACB error code
System action returned in SLRFERCD. take appropriate action, and
In response to DSNJSLR FUNC=OPEN call, Db2 places resubmit the FUNC=OPEN request.
a return code of 12 in register 15 and a reason code Related tasks
of 00D10018 in register 0. No abend is issued by the Reading log records with OPEN, GET, and CLOSE
stand-alone log services, and no information is written (Db2 Administration Guide)
to SYS1.LOGREC data set.

In response to the DSNJSLR FUNC=GET call, Db2
Related information code of 00D10021 in register 0. No abend is issued by
DFSMS Macro Instructions for Data Sets the stand-alone log services CSECT (DSNJRS01), and
no information is written to SYS1.LOGREC data set.
00D10020
Information about the results of the GET request is
also returned in the stand-alone log GET Feedback
Explanation Area (SLRF). A pointer to the next log record following
The Db2 stand-alone log services GET processing the gap is placed in SLRFFRAD.
macro (DSNJSLR) issued this reason code. The end The stand-alone log services program is under the
of data has been reached (end of the log, end of the control of a user-written program that uses the
user-specified log data set(s), or end of the log RBA DSNJSLR macro. The user program must therefore
range specified by the RANGE parameter). anticipate and react to a nonzero return code and
System action execution of the user program.
places a return code of 4 in register 15 and a reason System programmer response
code of 00D10020 in register 0. No abend is issued by As mentioned above, this may or may not be an
the stand-alone log services CSECT (DSNJRS01), and intentional error. Check the user's JCL to ensure that
no information is written to SYS1.LOGREC data set. a continuous string of log records has been supplied.
The stand-alone log services program is under the If the BSDS method is being used, use the print log
control of a user-written program that uses the map (DSNJU004) utility to examine the RBA ranges as
DSNJSLR macro. The user program must therefore recorded in the BSDS, and note any RBA gaps which
anticipate and react to a nonzero return code and may have resulted from the deletion of an active log
a nonzero reason code, possibly by terminating the data set or an archive log data set.
execution of the user program. If it appears that a log error may have occurred,
execute the log print utility (DSN1LOGP) to attempt to
System programmer response obtain a detailed report of the log record(s) associated
with the failure.
This is not an error; rather, this reason code denotes a
normal end of data condition. No action is necessary. Related concepts
DSN1LOGP summary report (Db2
Related tasks
Related reference
DSNJU004 (print log map) (Db2 Utilities)
Related reference
DSN1LOGP (Db2 Utilities)
services (Db2 Administration Guide) Related information
Recovering from active log failures (Db2
00D10021 Administration Guide)
Recovering from archive log failures (Db2
Explanation Administration Guide)
The Db2 stand-alone log services GET processing 00D10022

macro (DSNJSLR) issued this reason code. A gap in the
log RBA range has been encountered when switching
Explanation
log data sets, indicating missing log records.
The Db2 stand-alone log services GET processing
This condition may or may not be intentional on the
macro (DSNJSLR) issued this reason code. A gap in the
part of the user. Normally, a continuous set of log
log RBA range has been encountered when switching
records are supplied as input by the ACTIVEn and
log data sets, indicating missing log records, and the
ARCHIVE ddnames in the user's JCL. If a log data
log RBA of the next record following the gap is greater
set was intentionally (or unintentionally) removed, this
than the end RBA of the RBA range specified by the
condition will arise.
RANGE parameter.

This condition may or may not be intentional on the Explanation
part of the user. Normally, a continuous set of log
records are supplied as input by the ACTIVEn and The Db2 stand-alone log services GET processing
ARCHIVE ddnames in the user's JCL. If a log data macro (DSNJSLR) issued this reason code. A gap
set was intentionally (or unintentionally) removed, this in the log RBA range has been encountered, and
condition will arise. a conditional restart record has been found beyond
a conditional restart truncation point. This condition
exists when a log RBA gap was intentionally forced by
System action the user as part of log truncation during conditional
In response to the DSNJSLR FUNC=GET call, Db2 restart.
code of 00D10022 in register 0. No abend is issued by System action
no information is written to SYS1.LOGREC data set. In response to the DSNJSLR FUNC=GET call, Db2
Information about the results of the GET request is code of 00D10023 in register 0. No abend is issued by
also returned in the stand-alone log GET Feedback the stand-alone log services CSECT (DSNJRS01), and
Area (SLRF). A pointer to the next log record following no information is written to SYS1.LOGREC data set.
the gap is placed in SLRFFRAD.
The stand-alone log services program is under the also returned in the stand-alone log GET Feedback
control of a user-written program that uses the Area (SLRF). The length, address, and RBA of
DSNJSLR macro. The user program must therefore the conditional restart record are placed in fields
anticipate and react to a nonzero return code and SLRFRCLL, SLRFFRAD and SLRFRBA, respectively.
execution of the user program. The stand-alone log services program is under the
System programmer response anticipate and react to a nonzero return code and
As mentioned above, this may or may not be an a nonzero reason code, possibly by terminating the
intentional error. Check the RBA range specified on execution of the user program.
the RANGE parameter to determine if the end RBA
value was in error. Check the user's JCL to ensure that System programmer response
a continuous string of log records has been supplied.
If the BSDS method is being used, use the print log Use the print log map (DSNJU004) utility to examine
map (DSNJU004) utility to examine the RBA ranges as the conditional restart control records and the RBA
recorded in the BSDS, and note any RBA gaps which ranges of log data sets. Note any RBA gaps which may
may have resulted from the deletion of an active log have resulted from the truncation of the log during a
data set or an archive log data set. conditional restart.
If it appears that a log error may have occurred, If it appears that a log error may have occurred,
execute the log print utility (DSN1LOGP) to attempt to execute the log print utility (DSN1LOGP) to attempt to
obtain a detailed report of the log record(s) associated obtain a detailed report of the log record(s) associated
with the failure. with the failure.
Related concepts Related concepts

DSN1LOGP summary report (Db2 DSN1LOGP summary report (Db2
Administration Guide) Administration Guide)
Related reference Related tasks
DSNJU004 (print log map) (Db2 Utilities) Reading log records with OPEN, GET, and CLOSE
Related reference
Related information
Administration Guide) DSN1LOGP (Db2 Utilities)
Recovering from archive log failures (Db2 Sample application that uses stand-alone log
Administration Guide) services (Db2 Administration Guide)
00D10023

Related information Related tasks
Recovering from active log failures (Db2 Reading log records with OPEN, GET, and CLOSE
Administration Guide) (Db2 Administration Guide)
Recovering from archive log failures (Db2 Related reference
Administration Guide) DSNJU004 (print log map) (Db2 Utilities)
00D10024 services (Db2 Administration Guide)
Explanation 00D10025
macro (DSNJSLR) issued this reason code. A log RBA Explanation
sequence error has occurred. The RBA of the previous The Db2 stand-alone log services GET processing
log record is greater than the RBA of the current log macro (DSNJSLR) issued this reason code. A VSAM
record. error occurred while reading an active log data set.

In response to the DSNJSLR FUNC=GET call, Db2 In response to the DSNJSLR FUNC=GET call, Db2
places a return code of 8 in register 15 and a reason places a return code of 12 in register 15 and a reason
code of 00D10024 in register 0. No abend is issued by code of 00D10025 in register 0. No abend is issued by
the stand-alone log services CSECT (DSNJRS01), and the stand-alone log services CSECT (DSNJRS01), and
no information is written to SYS1.LOGREC data set. no information is written to SYS1.LOGREC data set.
Information about the results of the GET request is Information about the results of the GET request is
also returned in the stand-alone log GET Feedback also returned in the stand-alone log GET Feedback
Area (SLRF). A pointer to the next log record following Area (SLRF). The VSAM GET error return code is placed
the gap is placed in SLRFFRAD. in SLRFRG15. The RPL error code (RPLERRCD) is
The stand-alone log services program is under the placed in SLRFERCD. The ddname of the data set on
control of a user-written program that uses the which the activity occurred is placed in SLRFDDNM.
DSNJSLR macro. The user program must therefore The stand-alone log services program is under the
anticipate and react to a nonzero return code and control of a user-written program that uses the
a nonzero reason code, possibly by terminating the DSNJSLR macro. The user program must therefore
execution of the user program. anticipate and react to a nonzero return code and
System programmer response execution of the user program.
The DD statements in the user's Job Control Language
(JCL) must specify the log data sets in ascending log System programmer response
RBA range order. If both ARCHIVE and ACTIVEn DD Determine the meaning of the VSAM GET error
statements are included, the first archive data set returned in SLRFRG15, and the RPL error code
must contain the lowest log RBA value. returned in SLRFERCD. Take appropriate action to
Use the print log map (DSNJU004) utility to obtain a correct the error.
listing of the RBA ranges associated with each archive Related tasks
log data set and active log data set. If necessary:
• Adjust the concatenation sequence of the archive (Db2 Administration Guide)
data sets in the user's JCL to ensure that the log Related reference
records are read in ascending RBA sequence. Sample application that uses stand-alone log
• Adjust the order of the active log data sets such services (Db2 Administration Guide)
that the RBA range is arranged in ascending order, Related information
starting with the ACTIVE1 ddname, and progressing DFSMS Macro Instructions for Data Sets
through the ACTIVEn ddname.
Following the above adjustments, resubmit the user's 00D10026
JCL.

macro (DSNJSLR) issued this reason code. The GET Explanation
processing was unable to locate a log data set The Db2 stand-alone log services GET processing
containing the requested RBA. macro (DSNJSLR) issued this reason code. A VSAM
There could be several reasons for this error: error occurred while reading the bootstrap data set
(BSDS).
• The RBA range supplied in the RANGE parameter
may have exceeded the upper or lower bound of
RBAs available on all active log data sets and all System action
archive log data sets. This will normally occur when In response to the DSNJSLR FUNC=GET call, Db2
the user has specified the bootstrap data set (BSDS) places a return code of 12 in register 15 and a reason
method in the JCL. code of 00D10027 in register 0. No abend is issued by
• The RBA range supplied in the RANGE parameter the stand-alone log services CSECT (DSNJRS01), and
may have exceeded the upper or lower bound of no information is written to SYS1.LOGREC data set.
RBAs available on the active log data sets and/or
archive log data sets supplied in the user's JCL. This
will occur when the user has supplied log data sets
Area (SLRF). The VSAM GET error return code is placed
using the ACTIVEn and ARCHIVE ddnames.
in SLRFRG15. The RPL error code (RPLERRCD) is
placed in SLRFERCD.
System action
In response to the DSNJSLR FUNC=GET call, Db2 control of a user-written program that uses the
places a return code of 8 in register 15 and a reason DSNJSLR macro. The user program must therefore
code of 00D10026 in register 0. No abend is issued by anticipate and react to a nonzero return code and
the stand-alone log services CSECT (DSNJRS01), and a nonzero reason code, possibly by terminating the
no information is written to SYS1.LOGREC data set. execution of the user program.
also returned in the stand-alone log GET Feedback System programmer response
Area (SLRF). The RBA for which the GET request failed
Determine the meaning of the VSAM GET error
is placed in SLRFRBA.
returned in SLRFRG15, and the RPL error code
The stand-alone log services program is under the returned in SLRFERCD. Take appropriate action to
control of a user-written program that uses the correct the error.
Related tasks
a nonzero reason code, possibly by terminating the Reading log records with OPEN, GET, and CLOSE
execution of the user program. (Db2 Administration Guide)
Related reference
To resolve the problem, use the print log map Related information
(DSNJU004) utility to obtain a listing of the archive DFSMS Macro Instructions for Data Sets
and active log data sets, and their corresponding RBA
ranges. Check the user's JCL and the user's RANGE 00D10028
parameter to ensure that they are in harmony with one
another. Correct the JCL and RANGE parameters as
necessary, and rerun the application. Explanation
Related tasks The Db2 stand-alone log services OPEN processing
macro (DSNJSLR) issued this reason code. Both LRSN
range and CI mode read were specified on the OPEN
request when reading the log of a Db2 system.
Related reference However, when reading the log in CI mode, range can
DSNJU004 (print log map) (Db2 Utilities) be specified only in RBA.

System action DSNJU004 (print log map) (Db2 Utilities)
In response to DSNJSLR FUNC=OPEN call, Db2 places 00D1002A

of 00D10028 in register 0. No abend is issued by the
stand-alone log services, and no information is written Explanation
to SYS1.LOGREC data set. The Db2 stand-alone log services GET processing
macro (DSNJSLR) issued this reason code. The GET
User response processing has requested an RBA in an active log data
set which was previously not opened. A VSAM OPEN
Correct the range specification on the OPEN request, error occurred while opening the active log data set.
and rerun the job.
Related tasks System action
Related reference code of 00D1002A in register 0. No abend is issued by
Sample application that uses stand-alone log the stand-alone log services CSECT (DSNJRS01), and
services (Db2 Administration Guide) no information is written to SYS1.LOGREC data set.
00D10029 Information about the results of the GET request is

Area (SLRF). The VSAM OPEN error return code is
Explanation placed in SLRFRG15. The ACB error code (ACBERFLG)
The Db2 stand-alone log services OPEN processing is placed in SLRFERCD. The ddname of the data set on
macro (DSNJSLR) issued this reason code. The BSDS which the activity occurred is placed in SLRFDDNM.
data set of a member named in the BSDS data set The stand-alone log services program is under the
pointed to by the GROUP DD statement cannot be control of a user-written program that uses the
allocated. DSNJSLR macro. The user program must therefore
System action a nonzero reason code, possibly by terminating the
In response to DSNJSLR FUNC=OPEN call, Db2 places
of 00D10029 in register 0. No abend is issued by the System programmer response
stand-alone log services, and no information is written Determine the meaning of the VSAM OPEN error
to SYS1.LOGREC data set. returned in SLRFRG15, and the ACB error code
returned in SLRFERCD. Take appropriate action, and
User response then resubmit the application job.
Make sure the BSDS data set of every member named Related tasks
in the BSDS data set pointed to by the GROUP DD Reading log records with OPEN, GET, and CLOSE
statement is available for allocation. If the missing (Db2 Administration Guide)
BSDS data set belongs to a member that is no longer Related reference
active and its BSDS data set does not exist any more, Sample application that uses stand-alone log
then do not use GROUP DD to allocate required BSDS services (Db2 Administration Guide)
and log data sets. To read log records of other active
Related information
members, specify a MxxBSDS DD statements for each
active member. The print log map (DSNJU004) utility DFSMS Macro Instructions for Data Sets
can be used to find the name of every member's BSDS
data set. 00D1002B
Related tasks
Explanation
(Db2 Administration Guide) The Db2 stand-alone log services GET processing
Related reference macro (DSNJSLR) issued this reason code. The GET
processing has requested an RBA in an active log
data set which was previously not opened. A VSAM
OPEN error occurred while opening the active log

data set. The error was determined to be one which Explanation
could be corrected; however, a system error occurred
while executing an MVS TESTCB macro to determine The Db2 stand-alone log services GET processing
whether the active log data set which had just been macro (DSNJSLR) issued this reason code. The GET
opened was a VSAM ESDS data set or a VSAM LDS data processing has requested an RBA in an active log
set. data set which was previously not opened. A VSAM
OPEN error occurred while opening the active log data
set. The error was determined to be one which could
System action be corrected by use of an access method services
In response to the DSNJSLR FUNC=GET call, Db2 VERIFY, but the access method services VERIFY failed.
code of 00D1002B in register 0. No abend is issued by System action
no information is written to SYS1.LOGREC data set. In response to the DSNJSLR FUNC=GET call, Db2
Information about the results of the GET request is code of 00D1002C in register 0. No abend is issued by
Area (SLRF). The VSAM return code from the original no information is written to SYS1.LOGREC data set.
error code (ACBERFLG) from the ACB used in the Information about the results of the GET request is
original VSAM OPEN operation is placed in SLRFERCD. also returned in the stand-alone log GET Feedback
The ddname of the data set on which the activity Area (SLRF). The VSAM return code from the original
occurred is placed in SLRFDDNM. VSAM OPEN error is placed in SLRFRG15. The ACB
error code (ACBERFLG) from the ACB used in the
The stand-alone log services program is under the original VSAM OPEN operation is placed in SLRFERCD.
control of a user-written program that uses the The ddname of the data set on which the activity
DSNJSLR macro. The user program must therefore occurred is placed in SLRFDDNM.
a nonzero reason code, possibly by terminating the The stand-alone log services program is under the
execution of the user program. control of a user-written program that uses the
System programmer response a nonzero reason code, possibly by terminating the
Determine the meaning of the VSAM OPEN error execution of the user program.
returned in SLRFERCD. Take appropriate action, and System programmer response
resubmit the application job.
Refer to DFSMS Macro Instructions for Data Sets
If the SLRFERCD field contains X'1001' (decimal to determine the meaning of the VSAM OPEN error
4097), then the error is the result of an inconsistency returned in SLRFRG15, and the ACB error code
between the TESTCB parmlist generated in DSNJRS03 returned in SLRFERCD. Take appropriate action, and
and the level of MVS under which the application resubmit the application job.
program was executed. Contact IBM for assistance if
SLRFERCD reflects this value. Related tasks
Related tasks (Db2 Administration Guide)
Reading log records with OPEN, GET, and CLOSE Related reference
Related reference services (Db2 Administration Guide)
Sample application that uses stand-alone log Related information
DFSMS Macro Instructions for Data Sets
Related information
DFSMS Macro Instructions for Data Sets 00D1002D
00D1002C
Explanation
processing has requested an RBA in an active log data

set which was previously not opened. A VSAM OPEN to establish communication between itself and the
error occurred while opening the active log data set. invoking application program. The address to the
The open error was corrected by use of an access request block is returned to the application program
method services VERIFY, but a subsequent attempt on a FUNC=OPEN call, and is required for all
to reposition the VSAM pointer back to the beginning subsequent stand-alone FUNC=GET and FUNC=CLOSE
of the active log data set (via access method services calls in the RBR parameter. This reason code is
POINT) failed. returned to the invoking application when the RBR
does not address a valid stand-alone request block.
System action Subsequently, the application program's request
System action
code of 00D1002D in register 0. No abend is issued by
the stand-alone log services CSECT (DSNJRS01), and In response to the DSNJSLR FUNC=GET or
no information is written to SYS1.LOGREC data set. FUNC=CLOSE call, Db2 places a return code of 8 in
register 15 and a reason code of 00D10030 in register
0. No abend is issued by the stand-alone log services
CSECT (DSNJRS01), and no information is written to
Area (SLRF). The VSAM return code from the original
SYS1.LOGREC data set.
error code (ACBERFLG) from the ACB used in the The stand-alone log services program is under the
original VSAM OPEN operation is placed in SLRFERCD. control of a user-written program that uses the
The ddname of the data set on which the activity DSNJSLR macro. The user program must therefore
occurred is placed in SLRFDDNM. anticipate and react to a nonzero return code and
anticipate and react to a nonzero return code and System programmer response
On a FUNC=OPEN call, the RBR value is returned in
register 1. The application program must preserve
this value for all subsequent stand-alone FUNC=GET
System programmer response and FUNC=CLOSE calls. Due to an application
program logic error in the program which invokes the
Determine the meaning of the VSAM OPEN error
stand-alone log services, the RBR value has been
compromised. Repair the application program, and
returned in SLRFERCD. Take appropriate action (in
resubmit the application job.
most cases, the problem can be solved by use of an
AMS VERIFY against the active log data set named in Related tasks
the SLRFDDNM field of the SLRF). Once the problem is Reading log records with OPEN, GET, and CLOSE
solved, resubmit the application job. (Db2 Administration Guide)
Reading log records with OPEN, GET, and CLOSE Sample application that uses stand-alone log
(Db2 Administration Guide) services (Db2 Administration Guide)
Related reference
00D10031
Related information Explanation
DFSMS Macro Instructions for Data Sets The Db2 stand-alone log services GET processing
00D10030 processing has requested an RBA in a log data
set which was previously not opened. The user's
Explanation Job Control Language (JCL) has specified that the
bootstrap data set (BSDS) be used as the guide to
The Db2 stand-alone log services GET and CLOSE determining which log data sets are required. An
processing macro (DSNJSLR) issued this reason code. attempt to dynamically allocate the appropriate log
The stand-alone log services uses a request block data set (via MVS SVC 99) failed.

System action reason code is generated when an error was returned
from the RDJFCB macro.
code of 00D10031 in register 0. No abend is issued by System action
the stand-alone log services CSECT (DSNJRS01), and In response to the DSNJSLR FUNC=GET call, Db2
no information is written to SYS1.LOGREC data set. places a return code of 12 in register 15 and a reason
Information about the results of the GET request is code of 00D10040 in register 0. No abend is issued by
Area (SLRF). The SVC 99 error code (S99ERROR) and no information is written to SYS1.LOGREC data set.
information code (S99INFO) are placed in the SLRFRC Information about the results of the GET request is
and SLRFINFO fields, respectively. The ddname of the also returned in the stand-alone log GET Feedback
data set on which the activity occurred is placed in Area (SLRF). The RDJFCB error code is placed in
SLRFDDNM. SLRFRG15. The ddname of the data set on which the
The stand-alone log services program is under the activity occurred is placed in SLRFDDNM.
control of a user-written program that uses the The stand-alone log services program is under the
DSNJSLR macro. The user program must therefore control of a user-written program that uses the
anticipate and react to a nonzero return code and DSNJSLR macro. The user program must therefore
a nonzero reason code, possibly by terminating the anticipate and react to a nonzero return code and
execution of the user program. a nonzero reason code, possibly by terminating the
Refer to the appropriate MVS publication to determine System programmer response
the meaning of the SVC 99 error code (S99ERROR) Determine the meaning of the RDJFCB error code
returned in SLRFRG15, and SVC 99 information returned in SLRFRG15, take the appropriate action to
code (S99INFO) returned in SLRFINFO. Take the correct the error, and resubmit the application job.
appropriate action to correct the error, and resubmit
the application job. Related tasks
Related tasks
Related reference
Related reference
Related information
DFSMSdfp Advanced Services
Interpreting DYNALLOC return codes (MVS
Programming Authorized Assembler Services 00D10044
Reference)
00D10040 Explanation
TheDb2 stand-alone log services GET processing
Explanation macro (DSNJSLR) issued this reason code. The GET
processing has requested an RBA in an archive log
data set which was previously not opened. The
attempt to open the archive log data set failed.
processing has requested an RBA in an archive log
data set which was previously not opened. An attempt
is made to open the second file on the archive log System action
tape (the first file normally contains the bootstrap data In response to the DSNJSLR FUNC=GET call,Db2
set, while the second is normally the archive log data places a return code of 12 in register 15 and a reason
set). If this first attempt failed because the archive log code of 00D10044 in register 0. No abend is issued by
data set was not the second file on an archive tape, the stand-alone log services CSECT (DSNJRS01), and
then the RDJFCB macro is used to change the data no information is written to SYS1.LOGREC data set.
set sequence number from the default value of 2 to a
value of 1, before the OPEN is attempted again. This Information about the results of the GET request is

Area (SLRF). The ddname of the data set on which the Related tasks
activity occurred is placed in SLRFDDNM. Reading log records with OPEN, GET, and CLOSE
The stand-alone log services program is under the (Db2 Administration Guide)
control of a user-written program that uses the Related reference
DSNJSLR macro. The user program must therefore Sample application that uses stand-alone log
anticipate and react to a nonzero return code and services (Db2 Administration Guide)
execution of the user program. 00D10050
and reporting the problem, see Collecting diagnostic The Db2 stand-alone log services GET processing
data (Collecting data). You can also view this source macro (DSNJSLR) issued this reason code. The
for additional details about the stand-alone log bootstrap data set (BSDS) was erroneously specified
services, including a sample of an application program as one of the ARCHIVE data sets in the user's
which reacts to nonzero return codes and nonzero Job Control Language (JCL). Consequently, the GET
reason codes. request failed.

Determine the cause of the QSAM OPEN error, take the In response to the DSNJSLR FUNC=GET call, Db2
appropriate action to correct the error, and resubmit places a return code of 8 in register 15 and a reason
the application job. code of 00D10050 in register 0. No abend is issued by
00D10048 the stand-alone log services CSECT (DSNJRS01), and
Explanation Information about the results of the GET request is
The Db2 stand-alone log services GET processing Area (SLRF). The RBA of the requested log record
macro (DSNJSLR) issued this reason code. A QSAM control interval is placed in SLRFRBA.
GET error occurred while reading an archive log data
set. The stand-alone log services program is under the
System action anticipate and react to a nonzero return code and
In response to the DSNJSLR FUNC=GET call, Db2 a nonzero reason code, possibly by terminating the
places a return code of 12 in register 15 and a reason execution of the user program.
the stand-alone log services CSECT (DSNJRS01), and System programmer response
Examine the user's JCL, and remove the occurrence
Information about the results of the GET request is of the BSDS data set as one of the concatenated
also returned in the stand-alone log GET Feedback ARCHIVE data sets. Resubmit the application job.
Area (SLRF). The ddname of the data set on which the
activity occurred is placed in SLRFDDNM. Related tasks
DSNJSLR macro. The user program must therefore Related reference
anticipate and react to a nonzero return code and Sample application that uses stand-alone log
a nonzero reason code, possibly by terminating the services (Db2 Administration Guide)
00D10061
Explanation
Determine the cause of the QSAM GET error, take the
appropriate action to correct the error, and resubmit The Db2 stand-alone log services GET processing
the application job. macro (DSNJSLR) issued this reason code. The
log record control interval (CI) requested by the

application program was read successfully from an requested record was found to be a middle spanned
active log data set or an archive log data set. However, record segment, but a preceding first record segment
the physical record length returned from reading the does not exist. The GET function will complete, but will
CI is not the expected length. The GET function will issue this reason code as a warning.
complete, but will issue this reason code as a warning.
The length of a log CI in an active log data set is System action
expected to be 4089 bytes. The length of a log CI in
an archive log data set is expected to be 4096 bytes.
code of 00D10062 in register 0. No abend is issued
System action by the stand-alone log services CSECT (DSNJRS01),
and no information is written to SYS1.LOGREC data
set. The GET function will complete, but will issue this
reason code as a warning.
by the stand-alone log services CSECT (DSNJRS01), Information about the results of the GET request is
and no information is written to SYS1.LOGREC data also returned in the stand-alone log GET Feedback
set. The GET function will complete, but will issue this Area (SLRF). The length and address of the requested
reason code as a warning. record are placed in fields SLRFRCLL and SLRFFRAD,
respectively. The RBA associated with the log record
segment is placed in SLRFRBA. The ddname of the
data set on which the activity occurred is placed in
Area (SLRF). The length and address of the CI are
SLRFDDNM.
placed in fields SLRFRCLL and SLRFFRAD, respectively.
The RBA associated with the CI is placed in SLRFRBA. The stand-alone log services program is under the
The 'ddname' of the data set on which the activity control of a user-written program that uses the
occurred is placed in SLRFDDNM. DSNJSLR macro. The user program must therefore
a nonzero reason code, possibly by terminating the System programmer response
Several possibilities exist for the cause of this
condition:
• The Recovery Log Manager component of Db2 did
The RDF/CIDF control information in the CI has been not originally construct the LRH properly.
compromised. If the SLRFRCLL field indicates a value • The log record header (LRH) for the log record
greater than expected, then the data within the CI segment was damaged after it was written by the
can still be used by the application program. If the Db2 subsystem.
SLRFRCLL field indicates a value less than expected,
then the data within the CI in all likelihood can still • The application program continued to process after
be used, but with caution (additional error checking receipt of a 00D10021 reason code (gap in the log).
routines may be required by the user program). If the error was caused by the application program,
Related tasks modifications to the application program may be
required.
(Db2 Administration Guide) If the error is a suspected Db2 problem, run the log
Related reference print (DSN1LOGP) utility, specifying a range of RBAs
Sample application that uses stand-alone log which would encompass the problem RBA. Determine
services (Db2 Administration Guide) if the LRH of the log record segment is truly in error by
looking at the record segments directly preceding and
00D10062 after the record segment in question.
Related tasks
Explanation Reading log records with OPEN, GET, and CLOSE
macro (DSNJSLR) issued this reason code. The

Related reference If the error was caused by the application program,
Sample application that uses stand-alone log modifications to the application program may be
services (Db2 Administration Guide) required.
DSN1LOGP (Db2 Utilities) If the error is a suspected Db2 problem, run the log
print (DSN1LOGP) utility, specifying a range of RBAs
00D10063 which would encompass the problem RBA. Determine
if the LRH of the log record segment is truly in error by
Explanation looking at the record segments directly preceding and
after the record segment in question.
macro (DSNJSLR) issued this reason code. The Related tasks
requested record was found to be a last spanned Reading log records with OPEN, GET, and CLOSE
record segment, but a preceding first record segment (Db2 Administration Guide)
does not exist. The GET function will complete, but will Related reference
issue this reason code as a warning. Sample application that uses stand-alone log
System action DSN1LOGP (Db2 Utilities)
00D10064
by the stand-alone log services CSECT (DSNJRS01), Explanation
and no information is written to SYS1.LOGREC data The Db2 stand-alone log services OPEN processing
set. The GET function will complete, but will issue this macro (DSNJSLR) issued this reason code. During the
reason code as a warning. execution of a FUNC=OPEN request, Stand-alone Log
Information about the results of the GET request is Read encountered an invalid Stand-alone Log Read
also returned in the stand-alone log GET Feedback Request Block (SLRB).
Area (SLRF). The length and address of the requested
record are placed in fields SLRFRCLL and SLRFFRAD, System action
respectively. The RBA associated with the log record
segment is placed in SLRFRBA. The ddname of the In response to the DSNJSLR FUNC=OPEN call, Db2
data set on which the activity occurred is placed in places a return code of 12 in register 15 and a reason
SLRFDDNM. code of 00D10064 in register 0. No abend is issued by
the stand-alone services CSECT (DSNJRS01), and no
The stand-alone log services program is under the information is written to SYS1.LOGREC data set.
DSNJSLR macro. The user program must therefore The stand-alone log services program is under the
anticipate and react to a nonzero return code and control of a user-written program that uses the
a nonzero reason code, possibly by terminating the DSNJSLR macro. The user program must anticipate
execution of the user program. and react to a nonzero return code and a nonzero
reason code, possibly by terminating the execution of
the user program.
Several possibilities exist for the cause of this User response
condition:
Make necessary modifications to the user program
• The Recovery Log Manager component of Db2 did to use the updated Stand-alone Log Request Block
not originally construct the log record header (LRH) (SLRB) and recompile the DSNJSLR macro.
properly.
Related tasks
• The LRH for the log record segment was damaged
after it was written by the Db2 subsystem. Reading log records with OPEN, GET, and CLOSE
• The application program continued to process after
Related reference
receipt of a 00D10021 reason code (gap in the log).
• Striped logs are mirrored to a remote site, individual services (Db2 Administration Guide)
control intervals were propagated in a different order
than they were originally written, and the propagated 00D10101
copy did not reach a point of consistency.

Explanation 4
A request to disable data sharing is recorded in
The ENDRBA value specified in the control statement the BSDS, but the conditional restart record is not
was either greater or less than any known RBA, but correct. You cannot request a normal conditional
cold start was not specified for the conditional restart. restart with a disable request. You must use job
DSNTIJGF.
System action 8
Db2 startup is terminated. Update of the BSDS failed. Data sharing was
not disabled. See code 00D10411 for problem
determination. After the BSDS problem is fixed,
Operator response run DSNTIJGF to disable data sharing, and then
Notify the system programmer. restart Db2.
10
System programmer response A delete in the BSDS failed. Data sharing was
not disabled. See code 00D10413 for problem
Run the change log inventory (DSNJU003) utility with a determination. After the BSDS problem is fixed,
CRESTART control statement that has an RBA value run DSNTIJGF to disable data sharing, and then
known to the system in the BSDS, or that has the restart Db2.
ENDRBA and STARTRBA specifying the same RBA
12
(cold start).
Disable data sharing request was attempted on
If you suspect an error in Db2, you might need to a Db2 with a BSDS that has not been converted
report the problem. For information about identifying by the DSNJCNVT BSDS conversion utility in a
and reporting the problem, see Collecting diagnostic data sharing group that has at one point been
data (Collecting data). for more information. in Db2 11 new-function mode. Data sharing was
not disabled. Convert the surviving Db2 BSDS of
00D10102 the member, rerun job DSNTIJGF to disable data
sharing, and then restart Db2.
Explanation Related tasks
A request to disable data sharing failed. Disabling data sharing (Db2 Installation and
Migration)
System action Installation step 6: Define Db2 initialization
parameters: DSNTIJUZ, DSNTIJUA, DSNTIJUM,
Db2 startup terminates. and DSNTIJUL (Db2 Installation and Migration)
Migration step 11: Define Db2 12 initialization
Operator response parameters: DSNTIJUZ, DSNTIJUA, and
DSNTIJUM (Db2 Installation and Migration)
Collect an SVC memory dump, and contact the system
programmer. Related reference
DATA SHARING field (DSHARE subsystem
Related information
Obtain the SVC memory dump for the return code. To 00D10411
disable data sharing, you must run the disable data
sharing job (DSNTIJGF) and then restart Db2. 00D10413
00D10103
General register 2 contains a return code. Explanation Explanation
of the return code is as follows:
Db2 failed to open the shared communications area
2 (SCA) structure.
A request to disable data sharing is in the BSDS,
but a conditional restart record is not present. You
must use job DSNTIJGF for the correct conditional
System action
restart control record. Db2 startup terminates.

Operator response System action
Collect the SYS1.LOGREC and SVC dump and contact Db2 startup terminates.
the system programmer.
Operator response
Collect the SYS1.LOGREC and SVC dump and contact
Obtain the SYS1.LOGREC and SVC dump for analysis. the system programmer.
Problem determination System programmer response

Review the Db2 system console for possible DSN7xxxx Obtain the SYS1.LOGREC and SVC dump for analysis.
messages that could relate to this problem.
00D10104 Problem determination
This indicates that a new member is attempting to
Explanation join the data sharing group. If this a migration from
Db2 3.1, then catalog migration must be completed
Db2 failed to find the data sharing member record in before a new member can join this data sharing group.
the BSDS during Db2 startup. Wait until catalog migration completes, then restart
this Db2 to join the group. Otherwise, group restart
System action is required. Wait until group restart completes, then
restart this Db2 to join the group.
Db2 startup terminates.
Related concepts
Operator response Group restart phases (Db2 Data Sharing
Planning and Administration)
Collect the SYS1.LOGREC and SVC dump and contact Restart in a data sharing environment (Db2
the system programmer. Administration Guide)
System programmer response 00D10106
Obtain the SYS1.LOGREC and SVC dump for analysis.

Explanation
Problem determination Db2 failed to update an internal control record in the
BSDS for data sharing.
If this is the first startup of a new member joining
the data sharing group, run the DSNTIJUZ job created
to enable data sharing for this Db2 subsystem, and System action
then restart this Db2 subsystem. Also, check whether Db2 startup terminates.
the correct BSDS is specified in the Db2 startup
procedure. See message DSN7501A for additional
problem determination. Operator response
Related tasks Collect the SYS1.LOGREC and SVC dump and contact
Defining Db2 initialization parameters for new
data sharing members (Db2 Installation and
Migration) System programmer response
Related information Obtain the SYS1.LOGREC and SVC dump for analysis.
DSN7501A (Db2 Messages)

See Db2 code 00D10411 for problem determination.
Db2 found a mismatch in the shared communications
area (SCA) while a new member was attempting to join
a data sharing group.

Db2 failed to insert an internal control record in the Collect the SYS1.LOGREC and SVC dump and contact
BSDS for data sharing re-enable. the system programmer.

Db2 startup terminates. Display the existing SCA structures on this MVS
system.
Operator response
the system programmer. If an SCA structure already exists for this Db2 data
sharing group, use the MVS command SETXCF to
System programmer response delete this structure, then restart Db2 to complete the
re-enable process.
00D1010A
Explanation
See Db2 code 00D10412 for problem determination.
Db2 failed to write a record for re-enable in the shared
00D10108 communications area (SCA) structure.

Db2 failed to write an internal control record for Db2 startup terminates.
re-enable in the shared communications area (SCA)
structure.
Operator response
System action Collect the SYS1.LOGREC and SVC dump and contact
Operator response
System programmer response Review the Db2 system console for possible DSN7xxxx
00D1010B
Explanation
See message DSN7501A for problem determination.
Db2 failed to update an internal control record in the
00D10109 BSDS to enable data sharing.

Db2 found a shared communications area (SCA) Db2 startup terminates.
structure during the data sharing re-enable process.
This structure should not be built at this time.
Operator response
System action Collect the SYS1.LOGREC and SVC dump and contact

System programmer response a group, you can restart another Db2 subsystem that
is in the same Db2 data sharing group first, and then
Obtain the SYS1.LOGREC and SVC dump for analysis. restart. If no other Db2 subsystems exist in this group,
you must recover the BSDS before restarting.
Problem determination 00D1010E
See Db2 Code 00D10411 for problem determination.
00D1010C Explanation
Db2 failed to write an internal control record for a data
Explanation sharing restart in the shared communications area
(SCA) structure.
Db2 failed to write an internal control record in the
shared communications area (SCA) to enable data
sharing. System action
System action
Db2 startup terminates. Operator response
Operator response the system programmer.
the system programmer. System programmer response
Obtain the SYS1.LOGREC and SVC dump for analysis. Problem determination
Review the Db2 system console for possible DSN7xxxx
Problem determination messages that could relate to this problem.
Review the Db2 system console for possible DSN7xxxx 00D1010F
00D1010D Explanation
Db2 failed an attempt to change the generic LU or
Explanation location name in the shared communications area
(SCA) structure for the data sharing group.
Db2 could not find an internal control record for data
sharing in the BSDS or the shared communications
area (SCA). System action
System action
Db2 startup terminates. Operator response
Operator response the system programmer.
the system programmer. System programmer response
System programmer response All members in the data sharing group must first be
stopped, then this Db2 subsystem can be restarted to
Obtain the SYS1.LOGREC and SVC dump for analysis. make this change.

Check to be sure that this Db2 system is supposed
to be part of a data sharing group. If this Db2 is in 00D10110

Db2 failed to write an internal control record for a Db2 failed to update an internal control record in the
generic LU or location name change in the shared BSDS for a generic LU or location name change.
communications area (SCA) structure.
System action
System action
Operator response
Operator response
Collect the SYS1.LOGREC and SVC dump and contact the system programmer.
Db2 failed in an update to the BSDS for a data sharing
Db2 failed in a write to the SCA structure for a generic LU or location name change. See Db2 Code
data sharing restart change. Review the Db2 system 00D10411 for problem determination.
console for possible DSN7xxxx messages that could
relate to this problem. 00D10113
Db2 failed to update a data sharing member's
Explanation
information record in the BSDS to enable data sharing.
Db2 failed to find an internal record in the shared
communications area (SCA) that is needed to re- System action
enable data sharing.
System action
Operator response
Operator response
Collect the SYS1.LOGREC and SVC dump and contact System programmer response
To re-enable data sharing, you must start the surviving See Db2 Code 00D10411 for problem determination.
Db2 member first before other members can be
00D10114
started. If this is meant to be a re-enable attempt,
check whether the surviving member was started first.
If this re-enable is already complete, check that this is Explanation
the correct data sharing group.
Db2 failed to write a data sharing member information
Another possibility is that the SCA is damaged. Use the record in the shared communications area (SCA) for a
MVS command SETXCF to rebuild the SCA. restart of data sharing.
00D10112
System action

Collect the SYS1.LOGREC and SVC dump and contact See Db2 Code 00D10411 for problem determination.
00D10117

Explanation
Db2 failed to truncate and switch to a new log for data
sharing re-enable.
Review the Db2 system console for possible DSN7xxxx System action
00D10115
Operator response
Explanation
Db2 failed to update the data sharing record in the the system programmer.
BSDS to reset the enable flag.
System action
Operator response
Determine why Db2 failed to truncate and switch
Collect the SYS1.LOGREC and SVC dump and contact to a new log. Db2 might be using the last log. If
the system programmer. so, determine why offload has not occurred. See
Db2 messages DSNJ319I and DSNJ320I for problem
System programmer response determination.
Obtain the SYS1.LOGREC and SVC dump for analysis. 00D10130

See Db2 code 00D10411 for problem determination. An attempt was made to restart a deactivated member
of a data sharing group.
00D10116
System action
Explanation
An SVC dump is generated and restart processing for
Db2 failed to update an internal control record in the the member terminates.
BSDS for non-data sharing migration or fallback with
Db2.
System action Use the print log map utility (DSNJU004) to determine
the deactivation status of the member.
Operator response
Look for other messages that might have been issued
Collect the SYS1.LOGREC and SVC dump and contact in conjunction with the error. Use the SVC dump and
the system programmer. the LOGREC and syslog from the time of the failure to
aid in problem determination.
Obtain the SYS1.LOGREC and SVC dump for analysis. DSNJU004 (print log map) (Db2 Utilities)
00D10150

An internal logic error occurred during processing. Obtain the SYS1.LOGREC and the SVC dump. If you
System action the problem. For information about identifying and
The error is recorded in SYS1.LOGREC and an SVC (Collecting data).
dump is requested. Db2 then terminates abnormally.
Operator response
RLM standard diagnostic information is provided in
Collect the SYS1.LOGREC and SVC dump. Notify the Chapter 9, “X'D1......' codes,” on page 527.
System Programmer.
System programmer response • Dynamic dump, taken to SYS1.DUMPxx data set, by

Obtain the SYS1.LOGREC and SVC dump. This is likely
an error in Db2.
executing IFCEREP1.
• Contents of the BSDS (both copies if dual BSDS
Problem determination in use) obtained by using the Db2 print log map
If you suspect an error in Db2, you might need to (DSNJU004) utility.
report the problem. For information about identifying .
data (Collecting data). 00D10219
Explanation
was run, and a listing of the SYSLOG data set for the Db2 found that the current LRSN is less than the prior
period of time that spans the failure. LRSN after calculating a delta for the current LRSN.
• Listing of SYS1.LOGREC data set, obtained by Db2 terminates.
executing IFCEREP1.
• Contents of the BSDS (both copies if dual BSDS Operator response
in use) obtained by using the Db2 print log map
(DSNJU004) utility. Collect the SYS1.LOGREC and SVC dump and contact
00D10210
Explanation
An unsuccessful completion of a SET WRITE CURSOR
has occurred. An invalid write cursor ID was supplied.
System action This indicates that the system time is now less than
the time recorded earlier in the Db2 log data set.
An execution unit writes a record to SYS1.LOGREC Check that this Db2 subsystem is using the correct
and requests an SVC dump. The execution unit then BSDS and log data sets. Also check that the correct
terminates abnormally. system time is being used.
Collect the SYS1.LOGREC and SVC dump. Notify the and reporting the problem, see Collecting diagnostic
system programmer. data (Collecting data).
00D10220

An unsuccessful completion of a LOG WRITE has Obtain the SYS1.LOGREC and the SVC dump. If you
occurred. An invalid write cursor ID was supplied. suspect an error in Db2, you might need to report
System action reporting the problem, see Collecting diagnostic data
(Collecting data).
An execution unit writes a record to SYS1.LOGREC
and requests an SVC dump. The execution unit then
Operator response Chapter 9, “X'D1......' codes,” on page 527.
Collect the SYS1.LOGREC and SVC dump. Notify the
system programmer. • Dynamic dump, taken to SYS1.DUMPxx data set, by
System programmer response • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Obtain the SYS1.LOGREC and the SVC dump. If you
suspect an error in Db2, you might need to report • Contents of the BSDS (both copies if dual BSDS
the problem. For information about identifying and in use) obtained by using the Db2 print log map
reporting the problem, see Collecting diagnostic data (DSNJU004) utility.
(Collecting data). 00D10222

RLM standard diagnostic information is provided in An unsuccessful completion of a LOG WRITE has
Chapter 9, “X'D1......' codes,” on page 527. occurred. The record length specified was greater than
Collect the following diagnostic items: 32767.
• Listing of SYS1.LOGREC data set, obtained by An execution unit writes a record SYS1.LOGREC and
executing IFCEREP1. requests an SVC dump. The execution unit then
• Contents of the BSDS (both copies if dual BSDS terminates abnormally.
(DSNJU004) utility. Operator response
00D10221 Collect the SYS1.LOGREC and SVC dump. Notify the
system programmer.
Explanation
An unsuccessful completion of a LOG WRITE has
occurred. An invalid number of areas was specified. Obtain the SYS1.LOGREC and the SVC dump. If you
System action the problem. For information about identifying and
An execution unit writes a record to SYS1.LOGREC (Collecting data).
Operator response RLM standard diagnostic information is provided in
Chapter 9, “X'D1......' codes,” on page 527.
system programmer.

• Listing of SYS1.LOGREC data set, obtained by • Dynamic dump, taken to SYS1.DUMPxx data set, by
executing IFCEREP1. Db2 (04E and 04F abends).
• Contents of the BSDS (both copies if dual BSDS • Listing of SYS1.LOGREC data set, obtained by
in use) obtained by using the Db2 print log map executing IFCEREP1.
(DSNJU004) utility. • Contents of the BSDS (both copies if dual BSDS
00D10223 in use) obtained by using the Db2 print log map
(DSNJU004) utility.
There was an attempt to modify a log data set while
doing a conditional restart with CSRONLY specified. Explanation
A CHECK LOG was issued and the log RBA specified in
System action the macro had not been written to DASD at the time.
System action
Operator response An execution unit writes a record to SYS1.LOGREC
Notify the system programmer. terminates abnormally.

If a complete Db2 startup is needed, remove CSRONLY RLM standard diagnostic information is provided in
from the control statement. Restart Db2. Chapter 9, “X'D1......' codes,” on page 527.
00D10224 Collect the following diagnostic items:
Explanation Db2 (04E and 04F abends).
The Db2 database manager scheduled a log write • Listing of SYS1.LOGREC data set, obtained by
request for a commit log record. A request of the same executing IFCEREP1.
type is already active.
System action (DSNJU004) utility.
An execution unit writes a record to SYS1.LOGREC 00D10231
Explanation
Operator response An unsuccessful completion of a CHECK LOG has
occurred. The specified RBA is beyond the end of the
Collect the SYS1.LOGREC and SVC dump. Notify the log.
system programmer.
System action
Obtain the SYS1.LOGREC and the SVC dump. If you and requests an SVC dump. The execution unit then
suspect an error in Db2, you might need to report terminates abnormally.
(Collecting data).
Operator response
Problem determination system programmer.


Obtain the SYS1.LOGREC and the SVC dump. If you An unsuccessful completion of a CLOSE LOG FOR
suspect an error in Db2, you might need to report WRITE has occurred. An invalid write cursor ID was
the problem. For information about identifying and supplied.
(Collecting data). System action
RLM standard diagnostic information is provided in terminates abnormally.
Collect the following diagnostic items: Operator response
• Dynamic dump, taken to SYS1.DUMPxx data set, by Collect the SYS1.LOGREC and SVC dump. Notify the
Db2 (04E and 04F abends). system programmer.
executing IFCEREP1. System programmer response
• Contents of the BSDS (both copies if dual BSDS Obtain the SYS1.LOGREC and the SVC dump. If you
in use) obtained by using the Db2 print log map suspect an error in Db2, you might need to report
(DSNJU004) utility. the problem. For information about identifying and
. reporting the problem, see Collecting diagnostic data
(Collecting data).
00D10232
Explanation
A request was made to force an LRSN in non-data Chapter 9, “X'D1......' codes,” on page 527.
sharing mode.

Db2 issues an SVC dump and returns an error to the
requesting function.
executing IFCEREP1.
Operator response in use) obtained by using the Db2 print log map
Collect the SYS1.LOGREC and SVC dump and contact (DSNJU004) utility.
00D10250

An unrecoverable error occurred while updating either
the BSDS or the MVS catalog to reflect changes in
Problem determination active log data sets.
The requesting function can be determined from
the SVC dump. It has requested a data sharing log System action
manager function in non-data sharing.
If you suspect an error in Db2, you might need to and requests an SVC dump. Db2 then terminates
report the problem. For information about identifying abnormally.
00D10240 Collect the SYS1.LOGREC and SVC dump. Notify the
system programmer.

System programmer response memory dump. Examine the SYS1.LOGREC entries and
SVC memory dump to determine the primary error that
Obtain the SYS1.LOGREC and SVC dump. Correct the occurred. The SYSLOG might contain messages that
error, and restart Db2. describe the error that was encountered.

RLM standard diagnostic information is provided in RLM standard diagnostic information is provided in
Chapter 9, “X'D1......' codes,” on page 527. In addition, Chapter 9, “X'D1......' codes,” on page 527. In addition,
see abend reason code '00D10252' for a description of see abend reason code '00D10252' for a description of
the information recorded in the variable recording area the information recorded in the variable recording area
(VRA) of the SDWA. If you suspect an error in Db2, (VRA) of the SDWA.
you might need to report the problem. For information
about identifying and reporting the problem, see The ABEND can occur when the BSDS of the
Collecting diagnostic data (Collecting data). subsystem is in the format that supports only 6-byte
RBA and LRSN values if the RBA or LRSN reaches
Examine the console log for a DSNJxxxx message the limit of X'00000000FFFFFFFFFFFF' or RBA or
preceding this abend to determine whether the error X'00FFFFFFFFFFFF000000' for LRSN. If the LRSN limit
was a BSDS error or an MVS catalog update error. is reached, the BSDS must be converted to the format
Collect the following diagnostic items: that supports 10-byte values by using the DSNJCNVT
utility. Until this conversion is complete, the subsystem
• Console output from the system on which the job cannot be restarted. If the RBA limit is reached, either
was run, and a listing of the SYSLOG data set for the the RBA reset procedure can be used or the BSDS can
period of time that spans the failure. be converted by using DSNJCNVT.
• Contents of the BSDS (both copies if dual BSDS Collect the following diagnostic items:
(DSNJU004) utility. • Console output from the system on which the job
00D10251 period of time that spans the failure.
An unrecoverable error occurred in the log buffer • Listing of SYS1.LOGREC data set, obtained by
writer. executing IFCEREP1.
System action in use) obtained by using the Db2 print log map
(DSNJU004) utility.
The log buffer writer creates a record in SYS1.LOGREC
and might request an SVC memory dump. Db2 then 00D10252
terminates abnormally. An SVC memory dump might Explanation:
not be requested if the previous messages fully
describe the error.
System action
Operator response An execution unit writes a record to SYS1.LOGREC and
requests an SVC dump.
Collect the SYS1.LOGREC and SVC memory dump.
Operator response
System programmer response Collect the SYS1.LOGREC and SVC dump. Notify the
system programmer.
Obtain the SYS1.LOGREC, the SVC memory dump,
and the SYSLOG from the time the error occurred.
This error is typically caused by a previous error that System programmer response
was recorded on SYS1.LOGREC and produced an SVC Obtain the SYS1.LOGREC and SVC dump.

Problem determination • Contents of the BSDS (both copies if dual BSDS
RLM standard diagnostic information is provided in (DSNJU004) utility.
Chapter 9, “X'D1......' codes,” on page 527. In addition,
the following information is contained in the variable 00D10254
recording area (VRA) of the SDWA:
• Reason code '00D10252' stored with key=VRARC. Explanation
• The log buffer writer recovery tracking area is stored An application program check occurred in an MVCS
with key=VRARRP. These fields in the VRA are instruction that attempted to move data from the
described by the system mapping macro IHAVRA. recovery log manager address space to the caller's
address space.
An execution unit writes a record to SYS1.LOGREC and
Collect the following diagnostic items: requests an SVC dump.
• Listing of SYS1.LOGREC data set, obtained by Collect the SYS1.LOGREC and SVC dump. Notify the
executing IFCEREP1. system programmer.
00D10253
Explanation Obtain the SYS1.LOGREC and SVC dump. Examine the
area to which data was to be moved. It may be in the
An application program check occurred in an MVCP
wrong key, or the address may be the cause of the
instruction that attempted to move a parameter list
problem. The failing instruction has a DB opcode and
or other data from the caller's address space to the
indicates the registers showing address and length to
recovery log manager address space.
be moved.

An execution unit writes a record to SYS1.LOGREC and
requests an SVC dump.

executing IFCEREP1.
system programmer.
System programmer response (DSNJU004) utility.
Obtain the SYS1.LOGREC and SVC dump. Examine the
00D10255
area from which data was to be moved. It may be in
the wrong key, or the address may be the cause of the
problem. The failing instruction has a DA opcode and Explanation
indicates the registers showing address and length to
DSNJR008 attempted to resume the waiting execution
be moved.
unit, and a failure occurred leaving the state of the
resume indoubt.
RLM standard diagnostic information is provided in System action
Collect the following diagnostic items: and requests an SVC dump. The Db2 subsystem then
terminates to avoid leaving the execution unit in a
state of indefinite suspension.
executing IFCEREP1.

Collect the SYS1.LOGREC and SVC dump. Notify the period of time that spans the failure.
system programmer.
If you suspect an error in Db2, you might need to executing IFCEREP1.
report the problem. For information about identifying • Contents of the BSDS (both copies if dual BSDS
and reporting the problem, see Collecting diagnostic in use) obtained by using the Db2 print log map
data (Collecting data). (DSNJU004) utility.
Problem determination program or batch job, and system messages that
RLM standard diagnostic information is provided in were issued. Make sure that MSGLEVEL=(1,1) on the
Chapter 9, “X'D1......' codes,” on page 527. In addition, JOB statement so that all diagnostic information is
register 6 has the address of the execution block (EB). sent to SYSPRINT.
Collect the following diagnostic items: 00D10261

executing IFCEREP1. Explanation
• Contents of the BSDS (both copies if dual BSDS While scanning the records and record segments in
in use) obtained by using the Db2 print log map a log control interval (CI), it was discovered that the
(DSNJU004) utility. forward record chain was broken. This condition is the
result of an incorrect record length in the log record
00D10256 header of some record in the log CI.

Recursive abends were detected while trying to This reason code can be issued by an active Db2
reinitialize an archive log read service task. subsystem as the log buffers are scanned before they
are written to the active log, or by the Db2 stand-alone
System action log services GET processing macro (DSNJSLR) as a CI
is retrieved from a user-specified active or archive log
An execution unit writes a record to SYS1.LOGREC data set.
and requests an SVC dump. The Db2 subsystem then
terminates to avoid leaving an execution unit in a state If the reason code is issued by an active Db2
of indefinite suspension. subsystem, then an abend is issued. A diagnostic
record is written to SYS1.LOGREC, and an SVC dump
is requested.
Operator response
• If the error was detected by DSNJOFF1, then the
Collect the SYS1.LOGREC, SVC dump, and console
archiving of the active log data set is terminated and
output. Notify the system programmer.
the faulty active log data set is marked 'stopped'.
• If the error was detected by DSNJR005, then
System programmer response message DSNJ012I is issued and the calling agent
Obtain the SYS1.LOGREC, the SVC dump, and a listing is terminated.
of the BSDS by running the print log map (DSNJU004) • If the error was detected by DSNJW009, then
utility. If you suspect an error in Db2, you might message DSNJ012I is issued and the Db2
need to report the problem. For information about subsystem is terminated.
identifying and reporting the problem, see Collecting
• If the error was detected by DSNJW107 or
DSNJW127, then the Db2 subsystem is terminated.
Problem determination If this reason code is issued as the result of Db2 stand-
alone log services GET processing, no abend is issued
RLM standard diagnostic information is provided in by the stand-alone log services CSECT (DSNJRS01),
Chapter 9, “X'D1......' codes,” on page 527. and no information is written to SYS1.LOGREC data
set. Rather, in response to the DSNJSLR FUNC=GET

call, Db2 places a return code of 4 in register 15 and Explanation
a reason code of 00D10261 in register 0. Information
about the results of the GET request is also returned While scanning a log control interval (CI), the offset to
in the stand-alone log GET feedback area (SLRF). The the last record or record segment in the CI was found
RBA of the record in error is placed in SLRFRBA. to be incorrect.
The address and length of the CI which contains the
errant log record header are placed in SLRFFRAD and System action
SLRFRCLL, respectively. The ddname of the data set on
which the activity occurred is placed in SLRFDDNM. This reason code can be issued by an active Db2
subsystem as the log buffers are scanned before they
Operator response log services GET processing macro (DSNJSLR) as a CI
If the reason code is issued by an active Db2 is retrieved from a user-specified active or archive log
subsystem, collect the SYS1.LOGREC and SVC dump, data set.
and notify the system programmer. If the reason code is issued by an active Db2
subsystem, then an abend is issued. A diagnostic
System programmer response record is written to SYS1.LOGREC, and an SVC dump
is requested.
If the reason code is issued by an active Db2
subsystem, obtain the SYS1.LOGREC and the SVC • If the error was detected by DSNJOFF1, then the
dump from the operator. archiving of the active log data set is terminated and
• Dynamic dump, taken to SYS1.DUMPxx data set, by message DSNJ012I is issued and the calling agent
Db2 (04E and 04F abends). is terminated.
• Listing of SYS1.LOGREC data set, obtained by • If the error was detected by DSNJW009, then
executing IFCEREP1. message DSNJ012I is issued and the Db2
• Contents of the BSDS (both copies if dual BSDS subsystem is terminated.
in use) obtained by using the Db2 print log map • If the error was detected by DSNJW107 or
(DSNJU004) utility. DSNJW127, then the Db2 subsystem is terminated.
If this reason code is issued as the result of Db2 stand-
Problem determination alone log services GET processing, no abend is issued
If the reason code is issued by an active by the stand-alone log services CSECT (DSNJRS01),
Db2 subsystem, obtain a DSN1LOGP detail report and no information is written to SYS1.LOGREC data
containing the log record(s) associated with the failure. set. Rather, in response to the DSNJSLR FUNC=GET
call, Db2 places a return code of 4 in register 15 and
If the reason code is issued upon return of an a reason code of 00D10262 in register 0. Information
invocation of the Db2 stand-alone log services macro about the results of the GET request is also returned
(DSNJSLR), then an additional user-written exit or in the stand-alone log GET Feedback Area (SLRF).
diagnostic routine may have to be written. The RBA of the beginning of the CI is placed in
Related concepts SLRFRBA. The address and length of the CI are placed
in SLRFFRAD and SLRFRCLL, respectively. The ddname
Recovering from BSDS or log failures during
of the data set on which the activity occurred is placed
restart (Db2 Administration Guide)
in SLRFDDNM.
Related tasks
Operator response
Related reference If the reason code is issued by an active Db2
DSN1LOGP (Db2 Utilities) subsystem, collect the SYS1.LOGREC and SVC dump,
and notify the system programmer.
Related information
Administration Guide) System programmer response
Recovering from archive log failures (Db2 If the reason code is issued by an active Db2
Administration Guide) subsystem, obtain the SYS1.LOGREC and the SVC
dump from the operator.
00D10262

Collect the following diagnostic items: • If the error was detected by DSNJOFF1, then the
message DSNJ012I is issued and the calling agent
executing IFCEREP1.
is terminated.
• If the error was detected by DSNJW009, then
message DSNJ012I is issued and the Db2
(DSNJU004) utility.
subsystem is terminated.
• If the error was detected by DSNJW107 or
Problem determination DSNJW127, then the Db2 subsystem is terminated.
If the reason code is issued by an active If this reason code is issued as the result of Db2 stand-
Db2 subsystem, obtain a DSN1LOGP detail report alone log services GET processing, no abend is issued
containing the log record(s) associated with the failure. by the stand-alone log services CSECT (DSNJRS01),
If the reason code is issued upon return of an and no information is written to SYS1.LOGREC data
invocation of the Db2 stand-alone log services macro set. Rather, in response to the DSNJSLR FUNC=GET
(DSNJSLR), then an additional user-written exit or call, Db2 places a return code of 4 in register 15 and
diagnostic routine may have to be written. a reason code of 00D10263 in register 0. Information
about the results of the GET request is also returned
Related concepts in the stand-alone log GET Feedback Area (SLRF).
Recovering from BSDS or log failures during The RBA of the beginning of the CI is placed in
restart (Db2 Administration Guide) SLRFRBA. The address and length of the CI are placed
Related tasks in SLRFFRAD and SLRFRCLL, respectively. The ddname
Reading log records with OPEN, GET, and CLOSE of the data set on which the activity occurred is placed
(Db2 Administration Guide) in SLRFDDNM.
Related reference
Operator response
Related information
Recovering from active log failures (Db2 If the reason code is issued by an active Db2
Administration Guide) subsystem, collect the SYS1.LOGREC and SVC dump,
00D10263
subsystem, obtain the SYS1.LOGREC and the SVC
Explanation dump from the operator.
While scanning a log control interval (CI), the VSAM Collect the following diagnostic items:
RDF/CIDF control information was found to be
incorrect. • Dynamic dump, taken to SYS1.DUMPxx data set, by
System action
executing IFCEREP1.
This reason code can be issued by an active Db2 • Contents of the BSDS (both copies if dual BSDS
subsystem as the log buffers are scanned before they in use) obtained by using the Db2 print log map
are written to the active log, or by the Db2 stand-alone (DSNJU004) utility.
log services GET processing macro (DSNJSLR) as a CI
data set. Problem determination
If the reason code is issued by an active Db2 If the reason code is issued by an active
subsystem, then an abend is issued. A diagnostic Db2 subsystem, obtain a DSN1LOGP detail report
record is written to SYS1.LOGREC, and an SVC dump containing the log record(s) associated with the failure.
is requested. If the reason code is issued upon return of an
invocation of the Db2 stand-alone log services macro

(DSNJSLR), then an additional user-written exit or about the results of the GET request is also returned
diagnostic routine may have to be written. in the stand-alone log GET Feedback Area (SLRF). The
expected RBA of the beginning of the CI is placed in
Related concepts
SLRFRBA. The address and length of the CI are placed
Recovering from BSDS or log failures during in SLRFFRAD and SLRFRCLL, respectively. The ddname
restart (Db2 Administration Guide) of the data set on which the activity occurred is placed
Related tasks in SLRFDDNM.
(Db2 Administration Guide) Operator response
Related reference
DSN1LOGP (Db2 Utilities) If the reason code is issued by an active Db2
subsystem, collect the SYS1.LOGREC and SVC dump,
Related information
Administration Guide) If the reason code is issued by an active Db2
00D10264 dump from the operator.
Explanation
While scanning a log control interval (CI), the Db2 (04E and 04F abends).
beginning log RBA of the CI was not the expected RBA.
executing IFCEREP1.
System action • Contents of the BSDS (both copies if dual BSDS
This reason code can be issued by an active Db2 in use) obtained by using the Db2 print log map
subsystem as the log buffers are scanned before they (DSNJU004) utility.
log services GET processing macro (DSNJSLR) as a CI Problem determination
data set. If the reason code is issued by an active
Db2 subsystem, obtain a DSN1LOGP detail report
If the reason code is issued by an active Db2 containing the log record(s) associated with the failure.
record is written to SYS1.LOGREC, and an SVC dump If the reason code is issued upon return of an
is requested. invocation of the Db2 stand-alone log services macro
(DSNJSLR), then an additional user-written exit or
• If the error was detected by DSNJOFF1, then the diagnostic routine may have to be written.
the faulty active log data set is marked 'stopped'. Related concepts
• If the error was detected by DSNJR005, then Recovering from BSDS or log failures during
message DSNJ012I is issued and the calling agent restart (Db2 Administration Guide)
is terminated. Related tasks
• If the error was detected by DSNJW009, then Reading log records with OPEN, GET, and CLOSE
message DSNJ012I is issued and the Db2 (Db2 Administration Guide)
subsystem is terminated. Related reference
• If the error was detected by DSNJW107 or DSN1LOGP (Db2 Utilities)
DSNJW127, then the Db2 subsystem is terminated. Related information
If this reason code is issued as the result of Db2 stand-
alone log services GET processing, no abend is issued
by the stand-alone log services CSECT (DSNJRS01), Recovering from archive log failures (Db2
and no information is written to SYS1.LOGREC data Administration Guide)
call, Db2 places a return code of 4 in register 15 and 00D10265

While scanning the records and record segments in If the reason code is issued by an active Db2
a log control interval (CI), it was discovered the subsystem, obtain the SYS1.LOGREC and the SVC
backward record chain was broken. This condition is dump from the operator.
the result of an incorrect record length in the log
record header of some record in the log CI.
System action Db2 (04E and 04F abends).
This reason code can be issued by an active Db2 executing IFCEREP1.
are written to the active log, or by the Db2 stand-alone • Contents of the BSDS (both copies if dual BSDS
log services GET processing macro (DSNJSLR) as a CI in use) obtained by using the Db2 print log map
is retrieved from a user-specified active or archive log (DSNJU004) utility.
data set.
If the reason code is issued by an active Db2 Problem determination
subsystem, then an abend is issued. A diagnostic If the reason code is issued by an active Db2
record is written to SYS1.LOGREC, and an SVC dump subsystem:
is requested.
• Obtain a DSN1LOGP detail report containing the log
• If the error was detected by DSNJOFF1, then the record(s) associated with the failure.
archiving of the active log data set is terminated.
• If you suspect an error in Db2, you might need to
• If the error was detected by DSNJR005, then report the problem. For information about identifying
message DSNJ012I is issued and the calling agent and reporting the problem, see Collecting diagnostic
is terminated. data (Collecting data).
• If the error was detected by DSNJW009, then If the reason code is issued upon return of an
message DSNJ012I is issued and the Db2 invocation of the Db2 stand-alone log services macro
subsystem is terminated. (DSNJSLR), then an additional user-written exit or
• If the error was detected by DSNJW107 or diagnostic routine may have to be written.
Related concepts
If this reason code is issued as the result of Db2 stand- Recovering from BSDS or log failures during
alone log services GET processing, no abend is issued restart (Db2 Administration Guide)
by the stand-alone log services CSECT (DSNJRS01), Related tasks
a reason code of 00D10265 in register 0. Information Related reference
about the results of the GET request is also returned DSN1LOGP (Db2 Utilities)
in the stand-alone log GET Feedback Area (SLRF). Related information
The RBA of the record in error is placed in SLRFRBA. Recovering from active log failures (Db2
The address and length of the CI are placed in Administration Guide)
SLRFFRAD and SLRFRCLL, respectively. The ddname Recovering from archive log failures (Db2
of the data set on which the activity occurred is placed Administration Guide)
in SLRFDDNM.
If you suspect an error in Db2, you might need to 00D10266
While scanning a log control interval (CI), a unit of
recovery ID or LINK RBA in some record was found to
Operator response be inconsistent with the beginning log RBA of the CI.
subsystem, collect the SYS1.LOGREC and SVC dump,

This reason code can be issued by an active Db2 (DSNJU004) utility.
is retrieved from a user-specified active or archive log If the reason code is issued by an active
data set. Db2 subsystem, obtain a DSN1LOGP detail report
subsystem, then an abend is issued. A diagnostic If the reason code is issued upon return of an
record is written to SYS1.LOGREC, and an SVC dump invocation of the Db2 stand-alone log services macro
is requested. (DSNJSLR), then an additional user-written exit or
• If the error was detected by DSNJOFF1, then the diagnostic routine may have to be written.
archiving of the active log data set is terminated and Related concepts
the faulty active log data set is marked 'stopped'. Recovering from BSDS or log failures during
• If the error was detected by DSNJR005, then restart (Db2 Administration Guide)
message DSNJ012I is issued and the calling agent Related tasks
is terminated. Reading log records with OPEN, GET, and CLOSE
• If the error was detected by DSNJW009, then (Db2 Administration Guide)
message DSNJ012I is issued and the Db2 Related reference
• If the error was detected by DSNJW107 or Related information
If this reason code is issued as the result of Db2 stand- Administration Guide)
alone log services GET processing, no abend is issued Recovering from archive log failures (Db2
by the stand-alone log services CSECT (DSNJRS01), Administration Guide)
set. Rather, in response to the DSNJSLR FUNC=GET 00D10267
a reason code of 00D10266 in register 0. Information Explanation
in the stand-alone log GET Feedback Area (SLRF). The While scanning a log control interval (CI), a middle or
RBA of the log record with the invalid RBA is placed in last spanned record segment was not the first segment
SLRFRBA. The address and length of the CI are placed contained in the log CI.
of the data set on which the activity occurred is placed System action
in SLRFDDNM.
This reason code can be issued by an active Db2
Operator response
If the reason code is issued by an active Db2 log services GET processing macro (DSNJSLR) as a CI
subsystem, collect the SYS1.LOGREC and SVC dump, is retrieved from a user-specified active or archive log
and notify the system programmer. data set.
System programmer response subsystem, then an abend is issued. A diagnostic
is requested.
dump from the operator. • If the error was detected by DSNJOFF1, then the
• Dynamic dump, taken to SYS1.DUMPxx data set, by • If the error was detected by DSNJR005, then
Db2 (04E and 04F abends). message DSNJ012I is issued and the calling agent
• Listing of SYS1.LOGREC data set, obtained by is terminated.
executing IFCEREP1.

• If the error was detected by DSNJW009, then Related tasks
message DSNJ012I is issued and the Db2 Reading log records with OPEN, GET, and CLOSE
subsystem is terminated. (Db2 Administration Guide)
• If the error was detected by DSNJW107 or Related reference
DSNJW127, then the Db2 subsystem is terminated. DSN1LOGP (Db2 Utilities)
If this reason code is issued as the result of Db2 stand- Related information
alone log services GET processing, no abend is issued Recovering from active log failures (Db2
and no information is written to SYS1.LOGREC data Recovering from archive log failures (Db2
set. Rather, in response to the DSNJSLR FUNC=GET Administration Guide)
a reason code of 00D10267 in register 0. Information 00D10268
in the stand-alone log GET Feedback Area (SLRF).
Explanation
The RBA of the record segment in error is placed in
SLRFRBA. The address and length of the CI are placed While scanning a log control interval (CI), a first or
in SLRFFRAD and SLRFRCLL, respectively. The ddname middle spanned record segment was not the last
of the data set on which the activity occurred is placed segment contained in the log CI.
in SLRFDDNM.
System action
Operator response
If the reason code is issued by an active Db2 subsystem as the log buffers are scanned before they
subsystem, collect the SYS1.LOGREC and SVC dump, are written to the active log, or by the Db2 stand-alone
and notify the system programmer. log services GET processing macro (DSNJSLR) as a CI
System programmer response data set.
is requested.
• Dynamic dump, taken to SYS1.DUMPxx data set, by archiving of the active log data set is terminated and
Db2 (04E and 04F abends). the faulty active log data set is marked 'stopped'.
• Listing of SYS1.LOGREC data set, obtained by • If the error was detected by DSNJR005, then
executing IFCEREP1. message DSNJ012I is issued and the calling agent
• Contents of the BSDS (both copies if dual BSDS is terminated.
in use) obtained by using the Db2 print log map • If the error was detected by DSNJW009, then
(DSNJU004) utility. message DSNJ012I is issued and the Db2
Problem determination • If the error was detected by DSNJW107 or
If the reason code is issued by an active
Db2 subsystem, obtain a DSN1LOGP detail report If this reason code is issued as the result of Db2 stand-
containing the log record(s) associated with the failure. alone log services GET processing, no abend is issued
by the stand-alone log services CSECT (DSNJRS01),
If the reason code is issued upon return of an
diagnostic routine may have to be written.
Related concepts about the results of the GET request is also returned
Recovering from BSDS or log failures during in the stand-alone log GET Feedback Area (SLRF).
restart (Db2 Administration Guide) The RBA of the record segment in error is placed in

of the data set on which the activity occurred is placed System action
in SLRFDDNM.
and requests an SVC dump. The subsystem then
Operator response terminates.
subsystem, collect the SYS1.LOGREC and SVC dump, Operator response
system programmer.
If the reason code is issued by an active Db2 System programmer response
dump from the operator. Obtain the SYS1.LOGREC and the SVC dump. If you
Collect the following diagnostic items: the problem. For information about identifying and
• Dynamic dump, taken to SYS1.DUMPxx data set, by reporting the problem, see Collecting diagnostic data
Db2 (04E and 04F abends). (Collecting data).
• Contents of the BSDS (both copies if dual BSDS Collect the following diagnostic items:
(DSNJU004) utility.
If the reason code is issued by an active • Contents of the BSDS (both copies if dual BSDS
Db2 subsystem, obtain a DSN1LOGP detail report in use) obtained by using the Db2 print log map
containing the log record(s) associated with the failure. (DSNJU004) utility.
If the reason code is issued upon return of an Related concepts
invocation of the Db2 stand-alone log services macro X'D1......' codes
(DSNJSLR), then an additional user-written exit or Reason code identifiers that begin with 00D1
diagnostic routine may have to be written. communicate normal and error situations with
Related concepts the recovery log manager.
X'D1......' codes Recovering from BSDS or log failures during
Reason code identifiers that begin with 00D1 restart (Db2 Administration Guide)
communicate normal and error situations with Related information
the recovery log manager.
Related tasks Administration Guide)
Reading log records with OPEN, GET, and CLOSE Recovering from archive log failures (Db2
(Db2 Administration Guide) Administration Guide)
Related reference
DSN1LOGP (Db2 Utilities) 00D1026A
Related information
Recovering from active log failures (Db2 Explanation
Administration Guide) A scan of the records and record segments in a log
control interval (CI) detected that the forward record
00D10269 chain was broken. This condition is the result of an
incorrect record length in the log record header of
Explanation some record in the log CI.
An unrecoverable error was found in one of the
buffers, while moving the current log buffer to the
static write buffer ('shadow buffer') in preparation for
the physical write to the active log.

This reason code can be issued by an active Db2 (DSNJU004) utility.
is retrieved from a user-specified active or archive log If the reason code is issued by an active
data set. Db2 subsystem, obtain a DSN1LOGP detail report
subsystem, then an abend is issued. A diagnostic If the reason code is issued upon return of an
record is written to SYS1.LOGREC, and an SVC dump invocation of the Db2 stand-alone log services macro
is requested. (DSNJSLR), then an additional user-written exit or
• If the error was detected by DSNJOFF1, archiving of diagnostic routine may have to be written.
the active log data set is terminated and the faulty Related concepts
active log data set is marked 'stopped'. Recovering from BSDS or log failures during
• If the error was detected by DSNJR005, message restart (Db2 Administration Guide)
DSNJ012I is issued and the calling agent is Related tasks
terminated. Reading log records with OPEN, GET, and CLOSE
• If the error was detected by DSNJW009, message (Db2 Administration Guide)
DSNJ012I is issued and the Db2 subsystem is Related reference
terminated.
• If the error was detected by DSNJW107 or Related information
DSNJW127, the Db2 subsystem is terminated.
If this reason code is issued as the result of Db2 stand- Administration Guide)
alone log services GET processing, no abend is issued Recovering from archive log failures (Db2
set. Rather, in response to the DSNJSLR FUNC=GET 00D1026B
a reason code of 00D10261 in register 0. Information Explanation
in the stand-alone log GET feedback area (SLRF). The A scan of a log control interval (CI) detected that
RBA of the record in error is placed in SLRFRBA. the last record or record segment in the CI was not
The address and length of the CI which contains the terminated.
errant log record header are placed in SLRFFRAD and
SLRFRCLL, respectively. The ddname of the data set on System action
which the activity occurred is placed in SLRFDDNM.
Operator response
If the reason code is issued by an active Db2 log services GET processing macro (DSNJSLR) as a CI
subsystem, collect the SYS1.LOGREC and SVC dump, is retrieved from a user-specified active or archive log
and notify the system programmer. data set.
System programmer response subsystem, then an abend is issued. A diagnostic
is requested.
dump from the operator. • If the error was detected by DSNJOFF1, then the
the faulty active log data set is marked as stopped.
• Dynamic dump, taken to SYS1.DUMPxx data set, by • If the error was detected by DSNJR005, then
Db2 (04E and 04F abends). message DSNJ012I is issued and the calling agent
• Listing of SYS1.LOGREC data set, obtained by is terminated.
executing IFCEREP1.

• If the error was detected by DSNJW009, then Related tasks
message DSNJ012I is issued and the Db2 Reading log records with OPEN, GET, and CLOSE
subsystem is terminated. (Db2 Administration Guide)
• If the error was detected by DSNJW107 or Related reference
DSNJW127, then the Db2 subsystem is terminated. DSN1LOGP (Db2 Utilities)
If this reason code is issued as the result of Db2 stand- Related information
alone log services GET processing, no abend is issued Recovering from active log failures (Db2
and no information is written to SYS1.LOGREC data Recovering from archive log failures (Db2
set. Rather, in response to the DSNJSLR FUNC=GET Administration Guide)
a reason code of 00D10262 in register 0. Information 00D1026C
in the stand-alone log GET Feedback Area (SLRF).
Explanation
The RBA of the beginning of the CI is placed in
SLRFRBA. The address and length of the CI are placed A scan of a log control interval (CI) detected that a unit
in SLRFFRAD and SLRFRCLL, respectively. The ddname of recovery ID or LINK RBA in some record was found
of the data set on which the activity occurred is placed to be inconsistent with the beginning log RBA of the CI.
in SLRFDDNM.
System action
Operator response
If the reason code is issued by an active Db2 subsystem as the log buffers are scanned before they
subsystem, collect the SYS1.LOGREC and SVC dump, are written to the active log, or by the Db2 stand-alone
and notify the system programmer. log services GET processing macro (DSNJSLR) as a CI
System programmer response data set.
is requested.
• Dynamic dump, taken to SYS1.DUMPxx data set, by archiving of the active log data set is terminated and
Db2 (04E and 04F abends). the faulty active log data set is marked as stopped.
Recovering from BSDS or log failures during in the stand-alone log GET Feedback Area (SLRF). The
restart (Db2 Administration Guide) RBA of the log record with the invalid RBA is placed in

of the data set on which the activity occurred is placed incorrect record length in the log record header of
in SLRFDDNM. some record in the log CI.

If the reason code is issued by an active Db2 This reason code can be issued by an active Db2
subsystem, collect the SYS1.LOGREC and SVC dump, subsystem as the log buffers are scanned before they
and notify the system programmer. are written to the active log, or by the Db2 stand-alone
System programmer response is retrieved from a user-specified active or archive log
data set.
Collect the following diagnostic items: is requested.
• Dynamic dump, taken to SYS1.DUMPxx data set, by • If the error was detected by DSNJOFF1, then the
Db2 (04E and 04F abends). archiving of the active log data set is terminated.
Recovering from BSDS or log failures during in the stand-alone log GET Feedback Area (SLRF).
restart (Db2 Administration Guide) The RBA of the record in error is placed in SLRFRBA.
Related tasks The address and length of the CI are placed in
SLRFFRAD and SLRFRCLL, respectively. The ddname
of the data set on which the activity occurred is placed
in SLRFDDNM.
Related reference
DSN1LOGP (Db2 Utilities) If you suspect an error in Db2, you might need to
Related information
Recovering from active log failures (Db2 data (Collecting data).
Operator response
00D1026D subsystem, collect the SYS1.LOGREC and SVC dump,
Explanation
A scan of the records and record segments in a log
control interval (CI) detected that the backward record If the reason code is issued by an active Db2
chain was broken. This condition is the result of an subsystem, obtain the SYS1.LOGREC and the SVC

Collect the following diagnostic items: If the reason code is issued by an active Db2
is requested.
executing IFCEREP1. • If the error was detected by DSNJOFF1, then the
• Contents of the BSDS (both copies if dual BSDS the faulty active log data set is marked as stopped.
(DSNJU004) utility. • If the error was detected by DSNJR005, then
message DSNJ012I is issued and the calling agent
is terminated.
• If the error was detected by DSNJW009, then
If the reason code is issued by an active Db2 message DSNJ012I is issued and the Db2
subsystem: subsystem is terminated.
• Obtain a DSN1LOGP detail report containing the log • If the error was detected by DSNJW107 or
record(s) associated with the failure. DSNJW127, then the Db2 subsystem is terminated.
• If you suspect an error in Db2, you might need to If this reason code is issued as the result of Db2 stand-
report the problem. For information about identifying alone log services GET processing, no abend is issued
and reporting the problem, see Collecting diagnostic by the stand-alone log services CSECT (DSNJRS01),
data (Collecting data). and no information is written to SYS1.LOGREC data
in the stand-alone log GET Feedback Area (SLRF). The
Related concepts expected RBA of the beginning of the CI is placed in
Recovering from BSDS or log failures during SLRFRBA. The address and length of the CI are placed
restart (Db2 Administration Guide) in SLRFFRAD and SLRFRCLL, respectively. The ddname
Related tasks of the data set on which the activity occurred is placed
in SLRFDDNM.
Related reference Operator response
DSN1LOGP (Db2 Utilities) If the reason code is issued by an active Db2
Related information subsystem, collect the SYS1.LOGREC and SVC dump,
Recovering from active log failures (Db2 and notify the system programmer.
Recovering from archive log failures (Db2 System programmer response
00D1026E subsystem, obtain the SYS1.LOGREC and the SVC
A scan of a log control interval (CI) detected that a log • Dynamic dump, taken to SYS1.DUMPxx data set, by
RBA in the CI was too large to be a 6-byte RBA. Db2 (04E and 04F abends).
System action executing IFCEREP1.
(DSNJU004) utility.
data set.

Problem determination whose header address is in the log manager block
(LMB) at LMBRCPHB. The LMB is pointed to by register
If the reason code is issued by an active 5. Register 6 contains the address of the EB.
Db2 subsystem, obtain a DSN1LOGP detail report
containing the log record(s) associated with the failure. Collect the following diagnostic items:
If the reason code is issued upon return of an • Listing of SYS1.LOGREC data set, obtained by
invocation of the Db2 stand-alone log services macro executing IFCEREP1.
(DSNJSLR), then an additional user-written exit or • Contents of the BSDS (both copies if dual BSDS
diagnostic routine may have to be written. in use) obtained by using the Db2 print log map
Related concepts (DSNJU004) utility.
Recovering from BSDS or log failures during 00D10302
(Db2 Administration Guide) An unsuccessful completion of an OPEN LOG FOR
READ has occurred. A valid scope was not specified.
Related reference
Related information
System action
Recovering from active log failures (Db2 An execution unit writes a record to SYS1.LOGREC
Administration Guide) and requests an SVC dump. The execution unit then
Recovering from archive log failures (Db2 terminates abnormally.
Operator response
00D10301
system programmer.
Explanation
An unsuccessful completion of an OPEN LOG FOR System programmer response
READ has occurred. An open log read cursor already
exists for this execution block (EB). Only one log read Obtain the SYS1.LOGREC and the SVC dump. If you
cursor per EB is permitted. suspect an error in Db2, you might need to report
System action (Collecting data).
and requests an SVC dump. The execution unit then Problem determination
Operator response
system programmer. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
System programmer response • Contents of the BSDS (both copies if dual BSDS
Obtain the SYS1.LOGREC and SVC dump. Scan the (DSNJU004) utility.
read cursor pool for a cursor with the same EB, or
examine through the Db2 trace for the problem. Trace 00D10303
IDs 040301 and 040302 identify OPEN entries while
040303 and 040304 are for CLOSE. Explanation
An unsuccessful completion of an OPEN LOG FOR
Problem determination READ has occurred. An invalid log RBA range was
RLM standard diagnostic information is provided in specified. HIGHRBA is less than LOWRBA.
Chapter 9, “X'D1......' codes,” on page 527. All log read
cursors reside in a recovery log manager storage pool

An execution unit writes a record to SYS1.LOGREC A peer log read request was made without a peer log
and requests an SVC dump. The execution unit then read cursor.
System action
Operator response
Db2 issues a return code of 4 and reason code of
Collect the SYS1.LOGREC and SVC dump. Notify the 00D10305 to the requesting function.
system programmer.
Review the Db2 console for related errors.
suspect an error in Db2, you might need to report Problem determination
reporting the problem, see Collecting diagnostic data If you suspect an error in Db2, you might need to
(Collecting data). report the problem. For information about identifying
RLM standard diagnostic information is provided in 00D10306
Explanation
A request to read merged log records failed.
executing IFCEREP1. Db2 issues a return code of 4 and reason code of
• Contents of the BSDS (both copies if dual BSDS 00D10306 to the requesting function.
(DSNJU004) utility. System programmer response
. Review the Db2 console for related errors.
00D10304
Explanation The requesting function has put this error code out.
An unknown function was requested in an open of a Check on this function.
log read cursor. If you suspect an error in Db2, you might need to
00D10304 to the requesting function. 00D10307

Review the Db2 console for related errors. A log read open in data sharing failed because the RBA
values were not increasing or were overlapping.
System action
report the problem. For information about identifying Db2 issues a return code of 4 and reason code of
and reporting the problem, see Collecting diagnostic 00D10307 to the requesting function.
00D10305

Review the Db2 console for related errors. Db2 issues a return code of 4 and reason code of
00D1030A to the requesting function.
report the problem. For information about identifying Review the Db2 console for related errors.
data (Collecting data). Problem determination
00D10308 If you suspect an error in Db2, you might need to
A log read open in data sharing failed.
00D10310
System action
Explanation
00D10308 to the requesting function. An unsuccessful completion of a SET READ CURSOR
RANGE has occurred. The specified log read cursor
System programmer response was not opened by the execution block submitting this
request. All input requests must be submitted under
Review the Db2 console for related errors. the execution block that opened the cursor.

If you suspect an error in Db2, you might need to An execution unit writes a record to SYS1.LOGREC
report the problem. For information about identifying and requests an SVC dump. The execution unit then
and reporting the problem, see Collecting diagnostic terminates abnormally.
00D10309 Operator response
Explanation system programmer.
A peer BSDS open request failed.
System action Obtain the SYS1.LOGREC and the SVC dump. If you
00D10309 to the requesting function.
(Collecting data).
Review the Db2 console for related errors. Problem determination
Problem determination Chapter 9, “X'D1......' codes,” on page 527. In addition,
register 6 contains the address of the execution block
(EB). All log read cursors reside in a recovery log
manager storage pool whose header address is in the
log manager block (LMB) at LMBRCPHB. The LMB is
pointed to by register 5.
00D1030A
Explanation
executing IFCEREP1.
A peer log read request was made in non-data sharing.

• Contents of the BSDS (both copies if dual BSDS System action
(DSNJU004) utility. An execution unit writes a record to SYS1.LOGREC
00D10311 terminates abnormally.

An unsuccessful completion of a SET READ CURSOR Collect the SYS1.LOGREC and SVC dump. Notify the
RANGE has occurred. An invalid write cursor ID was system programmer.
specified.
System action
An execution unit writes a record to SYS1.LOGREC suspect an error in Db2, you might need to report
and requests an SVC dump. The execution unit then the problem. For information about identifying and
terminates abnormally. reporting the problem, see Collecting diagnostic data
(Collecting data).
Operator response
system programmer. RLM standard diagnostic information is provided in
Obtain the SYS1.LOGREC and the SVC dump. If you • Dynamic dump, taken to SYS1.DUMPxx data set, by
suspect an error in Db2, you might need to report Db2 (04E and 04F abends).
executing IFCEREP1.
(Collecting data).
Problem determination (DSNJU004) utility.
00D10319
all log write cursors reside in a recovery log manager
storage pool whose header address is in the log Explanation
manager block (LMB) at LMBWCPHB. The LMB is Log rollback processing has been canceled by an
pointed to by register 5. Read cursors are in a similar operator command.
pool at LMBRCPHB.
• Dynamic dump, taken to SYS1.DUMPxx data set, by The current log read request terminates and the
Db2 (04E and 04F abends). reason code is returned to the log read requester.
executing IFCEREP1.
Operator response
in use) obtained by using the Db2 print log map Examine the console for additional messages
(DSNJU004) utility. regarding the canceling of the log rollback process.
00D10312 00D10322
An unsuccessful completion of a SET READ CURSOR An unsuccessful completion of a LOG READ has
RANGE has occurred. An invalid log RBA range was occurred. MODE=DIRECT with a record matching the
specified. HIGHRBA is lower than LOWRBA. specified TYPE was not found.

An execution unit writes a record to SYS1.LOGREC RLM standard diagnostic information is provided in
and requests an SVC dump. The execution unit then Chapter 9, “X'D1......' codes,” on page 527.

executing IFCEREP1.
Collect the SYS1.LOGREC and SVC dump. Notify the • Contents of the BSDS (both copies if dual BSDS
system programmer. in use) obtained by using the Db2 print log map
(DSNJU004) utility.
00D10324
suspect an error in Db2, you might need to report Explanation
reporting the problem, see Collecting diagnostic data An unsuccessful completion of a LOG READ has
(Collecting data). occurred. MODE=DIRECT with record matching the
specified CDATA is not found.
System action
Chapter 9, “X'D1......' codes,” on page 527. An execution unit writes a record to SYS1.LOGREC
in use) obtained by using the Db2 print log map Collect the SYS1.LOGREC and SVC dump. Notify the
(DSNJU004) utility. system programmer.
00D10323 System programmer response

Explanation
An unsuccessful completion of a LOG READ has the problem. For information about identifying and
occurred. MODE=DIRECT with record matching the reporting the problem, see Collecting diagnostic data
specified SCOPE is not found. (Collecting data).


executing IFCEREP1.
Collect the SYS1.LOGREC and SVC dump. Notify the • Contents of the BSDS (both copies if dual BSDS
system programmer. in use) obtained by using the Db2 print log map
(DSNJU004) utility.
00D10325
reporting the problem, see Collecting diagnostic data An unsuccessful completion of a LOG READ has
(Collecting data). occurred. The sum of CDATA length value and CDATA
offset value is greater than 256.

executing IFCEREP1.
and requests an SVC dump. The execution unit then • Contents of the BSDS (both copies if dual BSDS
terminates abnormally. in use) obtained by using the Db2 print log map
(DSNJU004) utility.
Operator response 00D10327

system programmer. Explanation
An unsuccessful completion of a LOG READ has
System programmer response occurred because of an invalid LOGRBA value.
MODE=DIRECT with requested RBA does not match
Obtain the SYS1.LOGREC and the SVC dump. If you the start of a log record.
reporting the problem, see Collecting diagnostic data System action
(Collecting data). An execution unit writes a record to SYS1.LOGREC
Problem determination terminates abnormally.

Chapter 9, “X'D1......' codes,” on page 527. Operator response
Collect the following diagnostic items: Collect the SYS1.LOGREC and SVC dump. Notify the
system programmer.
executing IFCEREP1.
in use) obtained by using the Db2 print log map Obtain the SYS1.LOGREC and the SVC dump. If you
(DSNJU004) utility. suspect an error in Db2, you might need to report
00D10326 reporting the problem, see Collecting diagnostic data
(Collecting data).
Explanation
An unsuccessful completion of a LOG READ has Problem determination
occurred. The macro invocation specified that no RLM standard diagnostic information is provided in
wait was to occur because of a busy archive log Chapter 9, “X'D1......' codes,” on page 527.
data set (ADSWAIT(NO)). The macro invocation also
specified that, rather than returning with a condition 00D10328
code (COND(NO)), an abend should be issued by
the recovery log manager (RLM) subcomponent. The Explanation
RLM determined that the record requested was on an
archive log data set that was in use. A LOG READ completed unsuccessfully, because a
MODE request sequence was invalid. A read request
specifying a sequential MODE (any MODE except
System action DIRECT) must be preceded by an open log for read,
An execution unit writes a record to SYS1.LOGREC a set read cursor range, or a read with the same MODE
and requests an SVC dump. The execution unit then parameter value. It is invalid to intermix read requests
terminates abnormally. with different sequential mode values.

RLM standard diagnostic information is provided in An execution unit writes a record to SYS1.LOGREC
Chapter 9, “X'D1......' codes,” on page 527. and requests an SVC dump. The execution unit then

Collect the SYS1.LOGREC and SVC dump. Notify the • Listing of SYS1.LOGREC data set, obtained by
system programmer. executing IFCEREP1.
System programmer response in use) obtained by using the Db2 print log map
(DSNJU004) utility.
suspect an error in Db2, you might need to report 00D1032A
reporting the problem, see Collecting diagnostic data Explanation
(Collecting data).
occurred. BSDS does not map the specified RBA into
Problem determination a log data set. The possible causes for this condition
RLM standard diagnostic information is provided in are:
Chapter 9, “X'D1......' codes,” on page 527. • The BSDS is in error.
Collect the following diagnostic items: • The log data set has been deleted.
• Listing of SYS1.LOGREC data set, obtained by • The log data set exists but the RBA cannot be found
executing IFCEREP1. from this log data set. This situation can happen in a
• Contents of the BSDS (both copies if dual BSDS disaster recovery site if the log data set was copied
in use) obtained by using the Db2 print log map before BSDS was copied.
(DSNJU004) utility. • The RBA cannot be found because it is beyond the
earliest RBA recorded in the log data sets.
00D10329
System action
Explanation
A LOG READ completed unsuccessfully, because an and requests an SVC dump. The execution unit then
I/O error occurred while reading the log data set. terminates abnormally.
data (Collecting data). for information about recovery Collect the SYS1.LOGREC and SVC dump. Notify the
from log failures. system programmer.

An execution unit writes a record to SYS1.LOGREC Obtain the SYS1.LOGREC and the SVC dump. Also,
and requests an SVC dump. The execution unit then obtain a listing of the BSDS by running the print
terminates abnormally. log map (DSNJU004) utility. If you suspect an error
in Db2, you might need to report the problem.
Operator response problem, see Collecting diagnostic data (Collecting
Collect the SYS1.LOGREC and SVC dump. Notify the data).
system programmer.
System programmer response Review the recovery log manager standard diagnostic
Examine SYS1.LOGREC and SVC dump information. information in Chapter 9, “X'D1......' codes,” on page
Also, examine any prior messages with a DSNJ prefix 527.
from the log buffer reader. Collect the following diagnostic items:
Problem determination Db2 (04E and 04F abends).
RLM standard diagnostic information is provided in • Listing of SYS1.LOGREC data set, obtained by
Chapter 9, “X'D1......' codes,” on page 527. executing IFCEREP1.

• Contents of the BSDS (both copies if dual BSDS Explanation
(DSNJU004) utility. A LOG READ completed unsuccessfully, because an
error occurred while opening or closing a log data set.
Related concepts
Related information data (Collecting data). for information about recovery
Recovering from BSDS failures (Db2 from log failures.
00D1032B System action

Explanation and requests an SVC dump. The execution unit then
A LOG READ completed unsuccessfully because an
error occurred while trying to allocate a log data set.
Operator response
report the problem. For information about identifying Collect the SYS1.LOGREC and SVC dump. Notify the
and reporting the problem, see Collecting diagnostic system programmer.
data (Collecting data). for information about recovery
from log failures. System programmer response
Examine LOGREC and SVC dump information. Also,
System action examine prior messages from recovery log manager
An execution unit writes a record to SYS1.LOGREC and open/close processing. These messages have a prefix
might request an SVC dump. The execution unit then of DSNJ.
Operator response RLM standard diagnostic information is provided in
Collect the SYS1.LOGREC and SVC dump, if a dump Chapter 9, “X'D1......' codes,” on page 527.
was produced. Notify the system programmer. Collect the following diagnostic items:
Examine LOGREC and SVC dump information, if • Contents of the BSDS (both copies if dual BSDS
a dump was produced. Also, examine any prior in use) obtained by using the Db2 print log map
messages with a DSNJ prefix from recovery log (DSNJU004) utility.
manager allocation processing.
00D1032D
Explanation
Chapter 9, “X'D1......' codes,” on page 527. An unsuccessful completion of a LOG READ has
occurred. The specified log read cursor was not
Collect the following diagnostic items: opened by the execution block submitting this request.
• Listing of SYS1.LOGREC data set, obtained by All input requests must be submitted under the
executing IFCEREP1. execution block that opened the cursor.
in use) obtained by using the Db2 print log map System action
(DSNJU004) utility. An execution unit writes a record to SYS1.LOGREC
00D1032C and requests an SVC dump. The execution unit then

Collect the SYS1.LOGREC and SVC dump. Notify the RLM standard diagnostic information is provided in
system programmer. Chapter 9, “X'D1......' codes,” on page 527.
Collect the following diagnostic item listed in
Obtain the SYS1.LOGREC and the SVC dump. If you executing IFCEREP1.
the problem. For information about identifying and 00D1032F
(Collecting data). Explanation
A LOG READ completed unsuccessfully because the
Problem determination high range RBA provided was not the RBA of a valid log
RLM standard diagnostic information is provided in record. This is an internal error.
all log read cursors reside in a recovery log manager System action
storage pool whose header address is in the log
manager block (LMB) at LMBRCPHB. The LMB is
pointed to by register 5.
executing IFCEREP1.
• Contents of the BSDS (both copies if dual BSDS system programmer.
(DSNJU004) utility.
00D1032E
Explanation the problem. For information about identifying and
A LOG READ completed unsuccessfully due to an reporting the problem, see Collecting diagnostic data
internal error. (Collecting data).

and requests an SVC dump. The execution unit then Chapter 9, “X'D1......' codes,” on page 527. In addition,
terminates abnormally. register 6 contains the address of the execution block
Operator response log manager block (LMB) at LMBRCPHB. The LMB is
Collect the SYS1.LOGREC and SVC dump. Notify the pointed to by register 5 and described by DSNDLMB.
system programmer. 00D10330

Examine LOGREC and SVC dump information. LOG An unsuccessful completion of a Close Log for read
READ was passed a bad parameter list. The field which has occurred. The specified log read cursor was
was detected to be in error (RDPLOPT1) is the third not opened by the execution block submitting this
byte of the second word traced in the log manager request. All input requests must be submitted under
311 trace entry. The RET field of this trace entry the execution block that opened the cursor.
along with the MEPL may be used to determine which
module issued the Log Read request. Both pieces of
information are useful in isolating the failure.

and requests an SVC dump. The execution unit then Chapter 9, “X'D1......' codes,” on page 527. In addition,
terminates abnormally. register 6 contains the address of the execution block
Operator response manager storage pool whose header address is in the
Collect the SYS1.LOGREC and SVC dump. Notify the pointed to by register 5 and described by DSNDLMB.
system programmer.
00D10332

Explanation
suspect an error in Db2, you might need to report A log read completed unsuccessfully because a link
the problem. For information about identifying and RBA pointed to a log record with a different URID. This
reporting the problem, see Collecting diagnostic data is an internal error.
(Collecting data).
System action
Problem determination A record is written to SYS1.LOGREC and an SVC
RLM standard diagnostic information is provided in DUMP is requested. The requesting execution unit is
Chapter 9, “X'D1......' codes,” on page 527. In addition, abnormally terminated.
(EB). All log read cursors reside in a recovery log Operator response
log manager block (LMB) at LMBRCPHB. The LMB is Collect the SYS1.LOGREC and SVC dump. Notify the
pointed to by register 5 and described by DSNDLMB. system programmer.

While reading the log backwards using the LRHLINK
Explanation
RBAs, a log record was found that contained a
A LOG READ completed unsuccessfully because a different URID. A link read is normally done when
LINK RBA did not point to the beginning of a LOG processing a rollback or an abort. This abend is issued
record. This is an internal error. to prevent a rollback of the wrong transaction. If
this occurs during abort processing, the subsystem
System action is brought down. If the abend reoccurs on the
subsequent restart of Db2, a conditional restart is
An execution unit writes a record to SYS1.LOGREC necessary to bypass the invalid log record.
Operator response In addition to the standard RLM diagnostic
information, register 6 contains the address of the
Collect the SYS1.LOGREC and SVC dump. Notify the execution block (EB). All log read cursors reside
system programmer. in a recovery log manager storage pool whose
header address is in the log manager block (LMB) at
System programmer response LMBRCPHB. The LMB is pointed to by register 5 and
described in the DSNDLMB macro.
suspect an error in Db2, you might need to report Related concepts
the problem. For information about identifying and Recovering from BSDS or log failures during
reporting the problem, see Collecting diagnostic data restart (Db2 Administration Guide)
(Collecting data).
00D10333

A log read failed because an internal error was An execution unit writes a record to SYS1.LOGREC
detected by the Data Manager while examining the log and requests an SVC dump. The execution unit then
record during recover and deferred restart. terminates abnormally.

The execution unit writes a record to SYS1.LOGREC Collect the SYS1.LOGREC and SVC dump. Notify the
and requests an SVC dump. The execution unit then system programmer.
Operator response
Obtain the SYS1.LOGREC and the SVC dump.
Collect the SYS1.LOGREC and the SVC dump. Notify
the system programmer. Problem determination
"Recovery Log Manager Reason Codes (X'D1')".
Related tasks
the problem. For information about identifying and Requesting Db2 SVC dumps (Collecting data)
reporting the problem, see Collecting diagnostic data Related reference
(Collecting data). SYS1.LOGREC (Diagnosing Db2 problems)
00D10335
User response
An unsuccessful completion of a LOG READ occurred
because the log was not being read in ascending order
RLM standard diagnostic information is provided in for MODE=SEQUENTIAL DIRECT.
Chapter 9, “X'D1......' codes,” on page 527 (X'D1').
In addition, the following diagnostic information is System action
provided in registers:
• Register 0: the Data Mgr ERQUAL that identifies the and requests an SVC dump. The execution unit then
place within CSECT DSNILGRX where the error was terminates abnormally.
detected
• Register 2, 3: the RBA of the log record that was
Operator response
being read at the time of the error
• Register 7: the address of the DSCF selection block Collect the SYS1.LOGREC and SVC dump. Notify the
system programmer.
• Register 8: the address of the selection block for the
database services address space (ssnmDBM1).
00D10334
Obtain the SYS1.LOGREC and the SVC dump.
Explanation
An unsuccessful completion of a LOG READ
occurred because of an invalid LOGRBA value. RLM standard diagnostic information is provided in
MODE=SEQUENTIAL DIRECT with the requested RBA "Recovery Log Manager Reason Codes (X'D1')".
does not match the start of a log record. Related tasks
Requesting Db2 SVC dumps (Collecting data)
Related reference
SYS1.LOGREC (Diagnosing Db2 problems)

Explanation system programmer.
occurred. This reflects a logic failure internal to the System programmer response
recovery log manager (RLM) subcomponent and is
probably caused by a passed parameter list being lost Obtain the SYS1.LOGREC and the SVC dump. If you
or a previous abend processing a LOG READ request. suspect an error in Db2, you might need to report
and requests an SVC dump. The execution unit then Problem determination
Operator response register 6 contains the address of the execution block
Collect all relevant diagnostic materials, including (EB). All log read cursors reside in a recovery log
SYS1.LOGREC, SVC dump, and console output. Notify manager storage pool whose header address is in the
the system programmer. log manager block (LMB) at LMBRCPHB. The LMB is
pointed to by register 5 and described by DSNDLMB.
Examine LOGREC and SVC dump information for prior

abends during LOG READ processing. If you suspect an Explanation
error in Db2, you might need to report the problem. A LOG READ completed unsuccessfully because an
For information about identifying and reporting the error was detected during a backward READ of a log
problem, see Collecting diagnostic data (Collecting record. This is an internal error.
data).
System action
Collect the following diagnostic items: and requests an SVC dump. The execution unit then
• Listing of SYS1.LOGREC data set, obtained by terminates abnormally.
executing IFCEREP1.
• Contents of the BSDS (both copies if dual BSDS Operator response
in use) obtained by using the Db2 print log map Collect the SYS1.LOGREC and SVC dump. Notify the
(DSNJU004) utility. system programmer.
00D10341
Explanation Obtain the SYS1.LOGREC and the SVC dump. If you
A LOG READ completed unsuccessfully because an suspect an error in Db2, you might need to report
error was detected during a Forward READ of the log the problem. For information about identifying and
record. This is an internal error. reporting the problem, see Collecting diagnostic data
(Collecting data).
System action
and requests an SVC dump. The execution unit then RLM standard diagnostic information is provided in
terminates abnormally. Chapter 9, “X'D1......' codes,” on page 527. In addition,
pointed to by register 5 and described by DSNDLMB.

Obtain the SYS1.LOGREC and the SVC dump, if
Explanation requested. If you suspect an error in Db2, you might
A LOG READ completed unsuccessfully because an need to report the problem. For information about
error was detected during a READ of a log record due identifying and reporting the problem, see Collecting
to an invalid CI offset. This is an internal error. diagnostic data (Collecting data).

terminates abnormally. 00D10347
Operator response Explanation

Collect the SYS1.LOGREC and SVC dump. Notify the An attempt to notify a peer to force write the log buffer
system programmer. failed.

Obtain the SYS1.LOGREC and the SVC dump. If you Db2 issues a return code of 4 and reason code of
suspect an error in Db2, you might need to report 00D10347 to the requesting function.
(Collecting data). System programmer response
RLM standard diagnostic information is provided in Problem determination
Chapter 9, “X'D1......' codes,” on page 527. In addition, If you suspect an error in Db2, you might need to
register 6 contains the address of the execution block report the problem. For information about identifying
(EB). All log read cursors reside in a recovery log and reporting the problem, see Collecting diagnostic
manager storage pool whose header address is in the data (Collecting data).
pointed to by register 5 and described by DSNDLMB. 00D10348
00D10345
Explanation
Explanation The maximum retry count was exceeded while
attempting to read a log RBA.
A LOG READ completed unsuccessfully because an
error was received from a CATALOG LOCATE request
for an archive log data set. The requested archive log System action
data set might have been uncataloged or deleted. The execution unit writes a record to SYS1.LOGREC
System action terminates abnormally.
An execution unit might write a record to

SYS1.LOGREC and request an SVC dump. System programmer response
Operator response
Collect the SYS1.LOGREC and SVC dump, if requested. Problem determination
Notify the system programmer. This problem might occur if the user has added an
archive log to the BSDS with an incorrect RBA range
using Change Log Inventory (DSNJU003) or if an active
log data set has been regressed such that the log data

set does not contain the RBA range that is listed in the Related reference
BSDS. SYS1.LOGREC (Diagnosing Db2 problems)
00D10351
00D10349 A member of a Db2 data sharing group in a
GDPS® Continuous Availability with zero data loss
(GDPS Continuous Availability with zero data loss)
Explanation
environment issued a proxy log read request. The
A deadlock occurred attempting to allocate an archive operation failed for one of the following reasons:
log tape.
• The BSDS records for the data sharing member are
not in extended format.
System action • Installation parameter CDDS_MODE is not set to
Db2 issues a return code of 8 and reason code of PROXY for the data sharing member.
00D10349 to the requesting function. • The data sharing member did not start in proxy
mode.
Review the Db2 console for the terminated function. System action
Problem determination 00D10351 to the requesting function.
The requesting function was terminated. There was

another function allocating the same archive log System programmer response
tapes. Rerun the terminated function after the present Review the Db2 console output. In particular, check for
function no longer has the archive log tapes allocated. messages that were written during Db2 startup.
data (Collecting data). In the console output, check for messages that
indicate why the data sharing member did not start
00D10350 in proxy mode. One possible cause is that the
compression dictionary data set (CDDS) was not
Explanation available.
A lock or unlock failed in an attempt to allocate an If you suspect an error in Db2, you might need to
archive log tape. report the problem. For information about identifying
System action
An execution unit writes a record to SYS1.LOGREC,
requests an SVC dump, and then terminates. • Console output from the system on which the job
Operator response
Collect all relevant diagnostic materials, including Db2 (04E and 04F abends).
SYS1.LOGREC, an SVC dump, and console output. • Listing of SYS1.LOGREC data set, obtained by
Notify the system programmer. executing IFCEREP1.
This is an internal Db2 error. (DSNJU004) utility.
Related tasks 00D10401

Requesting Db2 SVC dumps (Collecting data)

A BSDS read was requested and the record was not If you suspect an error in Db2, you might need to
found. report the problem. For information about identifying
Db2 returns a return code of 4 and reason code of 00D10404

Explanation
System programmer response A BSDS insert was requested and the record already
Review the Db2 console for related errors. exists.

If you suspect an error in Db2, you might need to Db2 returns a return code of 4 and reason code of
report the problem. For information about identifying 00D10404 to the requesting function.
data (Collecting data). System programmer response
00D10402 Review the Db2 console for related errors.

A BSDS read was requested and the input area was too If you suspect an error in Db2, you might need to
small. report the problem. For information about identifying

Explanation
System programmer response A BSDS delete was requested and the record does not
Review the Db2 console for related errors. exist.

If you suspect an error in Db2, you might need to Db2 returns a return code of 4 and reason code of
report the problem. For information about identifying 00D10405 to the requesting function.
00D10403 Review the Db2 console for related errors.

A BSDS update was requested and the record was not If you suspect an error in Db2, you might need to
found. report the problem. For information about identifying

Explanation
System programmer response The bootstrap data set access service received a
Review the Db2 console for related errors. request with an invalid function code.

System action BSDS request element (BSDSRQEL) field (located at
offset X'8' in the bootstrap data set block).
If this was an unconditional request, an execution unit
writes a record to SYS1.LOGREC and requests an SVC Collect the following diagnostic items:
dump. The execution unit then terminates abnormally. • Console output from the system on which the job
Collect all relevant diagnostic materials, including • Dynamic dump, taken to SYS1.DUMPxx data set, by
SYS1.LOGREC, SVC dump, and console output. Notify Db2 (04E and 04F abends).
the system programmer. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
and reporting the problem, see Collecting diagnostic 00D10411
Explanation
An unsuccessful completion of a WRITE UPDATE BSDS
Collect the following diagnostic items: RECORD has occurred. An error has been returned
from VSAM.
executing IFCEREP1.
System action
in use) obtained by using the Db2 print log map An execution unit writes a record to SYS1.LOGREC
(DSNJU004) utility. and requests an SVC dump. The execution unit then
00D10410

An unsuccessful completion of a READ BSDS RECORD
system programmer.
has occurred. An error has been returned from VSAM.

Obtain the SYS1.LOGREC and SVC dump. Determine
the cause of the problem from the diagnostic
information in the Problem Determination section of
this message.
Operator response
system programmer.
the VSAM RPL fields RPLERRCD and RPLERREG are
System programmer response stored in the BSDS request parameter list. The address
of the BSDS request parameter list is stored in the
Use the SYS1.LOGREC and SVC dump to determine the
BSDS request element (BSDSRQEL) field (located at
cause of the problem.
offset 8 in the bootstrap data set block).
Problem determination Collect the following diagnostic items:
RLM standard diagnostic information is provided in • Console output from the system on which the job
Chapter 9, “X'D1......' codes,” on page 527. In addition, was run, and a listing of the SYSLOG data set for the
the VSAM RPL fields RPLERRCD and RPLERREG are period of time that spans the failure.
stored in the BSDS request parameter list. The address • Dynamic dump, taken to SYS1.DUMPxx data set, by
of the BSDS request parameter list is stored in the Db2 (04E and 04F abends).

executing IFCEREP1.
An unsuccessful completion of a DELETE BSDS
• Contents of the BSDS (both copies if dual BSDS RECORD has occurred. An error has been returned
in use) obtained by using the Db2 print log map from VSAM.
(DSNJU004) utility.
An unsuccessful completion of a WRITE INSERT BSDS terminates abnormally.
RECORD has occurred. An error has been returned
from VSAM. Operator response
System action
An execution unit writes a record to SYS1.LOGREC System programmer response
terminates abnormally. Obtain the SYS1.LOGREC and SVC dump. Determine
Operator response this message.
system programmer. Problem determination
System programmer response Chapter 9, “X'D1......' codes,” on page 527. In addition,
Obtain the SYS1.LOGREC and SVC dump. Determine the VSAM RPL fields RPLERRCD and RPLERREG are
the cause of the problem from the diagnostic stored in the BSDS request parameter list. The address
information in the Problem Determination section of of the BSDS request parameter list is stored in the
this message. BSDS request element (BSDSRQEL) field (located at
RLM standard diagnostic information is provided in • Console output from the system on which the job
Chapter 9, “X'D1......' codes,” on page 527. In addition, was run, and a listing of the SYSLOG data set for the
the VSAM RPL fields RPLERRCD and RPLERREG are period of time that spans the failure.
stored in the BSDS request parameter list. The address • Dynamic dump, taken to SYS1.DUMPxx data set, by
of the BSDS request parameter list is stored in the Db2 (04E and 04F abends).
BSDS request element (BSDSRQEL) field (located at
executing IFCEREP1.
Collect the following diagnostic items: • Contents of the BSDS (both copies if dual BSDS
• Console output from the system on which the job in use) obtained by using the Db2 print log map
was run, and a listing of the SYSLOG data set for the (DSNJU004) utility.
period of time that spans the failure. 00D10414
Explanation
executing IFCEREP1. Db2 cannot dynamically allocate a copy of the
requested bootstrap data set (BSDS).
(DSNJU004) utility. System action
00D10413 The system places the BSDS in disabled mode.

Restore the BSDS data set (or data sets) and restart A peer BSDS process was requested for a host BSDS.
the Db2 subsystem associated with the BSDS.
System action
User response
Notify the system programmer. 00D10417 to the requesting function.
00D10415
Explanation
The bootstrap data set (BSDS) is not a valid BSDS for
the data sharing group. Peer BSDS requests cannot be processed for the host
BSDS.
System action If you suspect an error in Db2, you might need to
The system places the BSDS in disabled mode.
00D10500
Restore the BSDS data set (or data sets) and restart
the Db2 subsystem associated with the BSDS.
Explanation
User response The recovery log manager's dynamic allocation
function has been passed a bad function code
Notify the system programmer. (LRB4FUNC in control block LRB4).
00D10416
System action
A peer BSDS process was requested in non-data
sharing.
Operator response
System action Notify the system programmer.

System programmer response the cause of the problem from the diagnostic
Review the Db2 console for related errors. this message.

Peer BSDS requests cannot occur in non-data sharing. RLM standard diagnostic information is provided in
If you suspect an error in Db2, you might need to Chapter 9, “X'D1......' codes,” on page 527. In addition,
report the problem. For information about identifying trace entry 501 provides the return address to the
and reporting the problem, see Collecting diagnostic module that passed the LRB4 with the undefined
data (Collecting data). function code. It also provides the address of the
LRB4. This address is also in register 7 at the time of
00D10417 the abend.

• Dynamic dump, taken to SYS1.DUMPxx data set, by Operator response
executing IFCEREP1.
00D10501
Explanation information in the Problem Determination section of
The recovery log manager's common access method this message.
services has been passed a bad function code
(DSPLFUNC in control block DSPL). Problem determination
System action Chapter 9, “X'D1......' codes,” on page 527. In addition,
An execution unit writes a record to SYS1.LOGREC register 0 contains the return code from SETLOCK
and requests an SVC dump. The execution unit then OBTAIN.
terminates abnormally. Collect the following diagnostic items:
Notify the system programmer. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
the cause of the problem from the diagnostic Explanation
this message. An error completion code was returned by SETLOCK
RELEASE.
System action
Chapter 9, “X'D1......' codes,” on page 527. The An execution unit writes a record to SYS1.LOGREC
address of the DSPL is provided in register 3, and the and requests an SVC dump. The execution unit then
invalid function in register 4. terminates abnormally.

Operator response
Db2 (04E and 04F abends). Notify the system programmer.
00D10700 Obtain the SYS1.LOGREC and SVC dump. Determine
Explanation this message.
An error completion code was returned by SETLOCK
OBTAIN. Problem determination
System action Chapter 9, “X'D1......' codes,” on page 527. In addition,
An execution unit writes a record to SYS1.LOGREC register 0 contains the return code from SETLOCK
and requests an SVC dump. The execution unit then RELEASE.
terminates abnormally. Collect the following diagnostic items:

executing IFCEREP1.
Collect all relevant diagnostic materials, including
00D10800 SYS1.LOGREC, an SVC dump, and console output.

The log manager command processor (DSNJC001) Review the Db2 system console for possible DSN7xxxx
was entered with an invalid Tokenized Command messages that could relate to this problem.
Segment (TCS).
See the Db2 system console for message DSNJ700I
that is issued with this Db2 condition code.
System action
A diagnostic record is written to SYS1.LOGREC, and an report the problem. For information about identifying
SVC dump is requested. The requesting execution unit and reporting the problem, see Collecting diagnostic
is abended. data (Collecting data).
00D10902
Operator response
Collect the SYS1.LOGREC and SVC dump, and notify Explanation
A dynamic allocation of a peer's BSDS failed.
System action
Obtain the SYS1.LOGREC and the SVC dump from the
operator. If you suspect an error in Db2, you might If this was an unconditional request, an execution
need to report the problem. For information about unit writes a record to SYS1.LOGREC, requests an SVC
identifying and reporting the problem, see Collecting dump, and terminates.
Operator response
Problem determination Collect all relevant diagnostic materials, including
RLM standard diagnostic information is provided under SYS1.LOGREC, an SVC dump, and console output of
Chapter 9, “X'D1......' codes,” on page 527. peer and host.
General register 1 contains the address of the TCS

as passed to log manager. The character string 'TCS' Problem determination
should appear at the address provided in R1, plus 4. Review the Db2 system console for possible errors
The address of the GCPC Pool Header Block (PHB) relating the peer's BSDS on both the host and peer
is provided in general register 2. The value X'0036' Db2 system.
should appear at the address provided in R2. If these
two items are not present, then the DSNJC001 CSECT See the Db2 system console for messages DSNJ103I
was invoked in error by an execution unit. and DSNJ700I that are issued with this Db2 condition
code.
00D10901
Db2 failed to locate a data sharing member in the SCA. data (Collecting data).
00D10903
System action
If this was an unconditional request, an execution Explanation
unit writes a record to SYS1.LOGREC, requests an SVC An open of a peer BSDS failed.
dump, and terminates.

If this was an unconditional request, an execution If this was an unconditional request, an execution
unit writes a record to SYS1.LOGREC, requests an SVC unit writes a record to SYS1.LOGREC, requests an SVC
dump, and terminates. dump, and terminates.

Collect all relevant diagnostic materials, including There is a mismatch between the two BSDS system
SYS1.LOGREC, an SVC dump, and console output. timestamps of a peer, the BSDS change log inventory
Notify the system programmer. (DSNJU003) timestamps of a peer, or both. The peer
log environment might have changed. This must be
Problem determination resolved at the peer Db2 subsystem by determining
which BSDS is in error and recovering that BSDS.
Review the Db2 system console for messages
DSNJ100I and DSNJ700I that are issued with this Db2
condition code.
00D10906
00D10904
The change log inventory (DSNJU003) timestamp does
There was a VSAM MRKBFR error for a peer BSDS.
not match the system timestamp in the peer BSDS.
System action
System action
If this was an unconditional request, an execution
unit writes a record to SYS1.LOGREC, requests an SVC
Operator response
A change log inventory (DSNJU003) job was executed
SYS1.LOGREC, an SVC dump, and console output.
against the peer BSDS after the last peer Db2
subsystem restart. The peer log environment might
Problem determination have changed. Restart the peer Db2 subsystem to
The VSAM MRKBFR error is placed in LRB1XRC. reset this condition.
See the Db2 system console for message DSNJ700I See the Db2 system console for message DSNJ700I
that is issued with this Db2 condition code. that is issued with this Db2 condition code.
00D10905 00D10907
There is a mismatch between the two BSDS Db2 could not locate a peer's active log data set in the
timestamps of a peer. peer's BSDS.

System action 00D10909
unit writes a record to SYS1.LOGREC, requests an SVC Explanation
dump, and terminates. There was no active BSDS found for the peer Db2
subsystem.
Operator response
Collect all relevant diagnostic materials including System action
SYS1.LOGREC, an SVC dump, and console output. If this was an unconditional request, an execution
Problem determination dump, and terminates.
Run a print log map (DSNJU004) job against the peer's
BSDS to compare BSDS active log entries with the Operator response
existing peer's log data sets. There is probably a Collect all relevant diagnostic materials, including
mismatch between them. SYS1.LOGREC, SVC dump, and console output of peer
See the Db2 system console for message DSNJ700I and host.
If you suspect an error in Db2, you might need to Problem determination
report the problem. For information about identifying Review the Db2 system console for possible errors
and reporting the problem, see Collecting diagnostic relating the peer's BSDSs on both the host and peer
data (Collecting data). Db2 system.
00D10908 See the Db2 system console for message DSNJ700I
Explanation The peer BSDSs have been placed in inactive mode.
An open of a peer's active log failed. There might have been an error against this peer's
BSDSs and a recovery is needed.
If this was an unconditional request, an execution and reporting the problem, see Collecting diagnostic
unit writes a record to SYS1.LOGREC, requests an SVC data (Collecting data).
00D10910
Operator response
Explanation
SYS1.LOGREC, an SVC dump, and console output of A BLDVRP/DLVRP macro failed for the BSDS buffer.
peer and host.
System action
Problem determination An execution unit writes a record to SYS1.LOGREC,
Review the Db2 system console for possible errors requests an SVC dump, and then terminates.
relating the peer's active log on both the host and peer
Db2 system. Operator response
The VSAM CONNECT return code is in LRB1XRC if an Collect all relevant diagnostic materials, including
SVC dump was taken. SYS1.LOGREC, SVC dump, and console output.
that is issued with this Db2 condition code. Problem determination
If you suspect an error in Db2, you might need to Review the Db2 system console for possible errors
report the problem. For information about identifying relating to the BSDS.
data (Collecting data). A BLDVRP/DLVRP macro for a VSAM shared resource
pool failed for the BSDS. General register 2 will

contain a value of 1 for a BLDVRP macro or a value System action
of 2 for a DLVRP macro. The macro return code is
contained in general register 3. See the appropriate Standard Db2 diagnostic information is recorded in
VSAM publication for advanced VSAM applications. SYS1.LOGREC, and an SVC dump is requested. The
subsystem will be terminated with the same reason
If you suspect an error in Db2, you might need to code.
Correct the problem with the coupling facility, and
00D10916
restart Db2.
Explanation
Db2 received an error while attempting to read shared
communications area (SCA) information from the
and DSNJxxxx messages that might relate to this
coupling facility.
problem. If you suspect an error in Db2, you might
System action identifying and reporting the problem, see Collecting
Standard Db2 diagnostic information is recorded in diagnostic data (Collecting data).
SYS1.LOGREC, and an SVC dump is requested. The Collect the following diagnostic items:
subsystem will be terminated with the same reason
code. • Console output from the system on which the job
Correct the problem with the coupling facility, and Db2 (04E and 04F abends).
restart Db2. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
00D10A00
and DSNJxxxx messages that might relate to this Explanation
problem. If you suspect an error in Db2, you might
need to report the problem. For information about A request was made to write to the compression
identifying and reporting the problem, see Collecting dictionary data set (CDDS), but the CDDS is in read-
diagnostic data (Collecting data). only access mode.
System action
was run, and a listing of the SYSLOG data set for the The write request fails.
• Dynamic dump, taken to SYS1.DUMPxx data set, by System programmer response
executing IFCEREP1.
00D10917
Db2 received an error while attempting to write
shared communications area (SCA) information to the Collect the following diagnostic items:
coupling facility.

• Dynamic dump, taken to SYS1.DUMPxx data set, by System programmer response
executing IFCEREP1.
in use) obtained by using the Db2 print log map If you suspect an error in Db2, you might need to
(DSNJU004) utility. report the problem. For information about identifying
00D10A01 data (Collecting data).
Explanation
A request was made to read a record in the
compression dictionary data set (CDDS), but the
record was not found.
System action
The read request fails. executing IFCEREP1.
(DSNJU004) utility.
• The unformatted contents of the compression
dictionary data set (CDDS), or IDCAMS PRINT output
Problem determination of the CDDS.
00D10A05
Collect the following diagnostic items: A request to perform an operation on the compression
dictionary data set (CDDS) specified an invalid function
code.
System action
Db2 (04E and 04F abends). The request fails.
• Contents of the BSDS (both copies if dual BSDS Review the Db2 console for related errors.
(DSNJU004) utility.
dictionary data set (CDDS), or IDCAMS PRINT output If you suspect an error in Db2, you might need to
of the CDDS. report the problem. For information about identifying
00D10A02 data (Collecting data).
Explanation 00D10A06
A request was made to read a record in the

Explanation
compression dictionary data set (CDDS), but the work
area was not large enough to hold the record. A request to perform an operation on the compression
dictionary data set (CDDS) abnormally terminated.
System action
The read request fails.

The request fails.
00D10A09
Explanation
A request to perform a read operation on the
compression dictionary data set (CDDS) failed because
Problem determination a read error occurred for the VSAM shared information
If you suspect an error in Db2, you might need to area (VSI).
The request fails.
00D10A07

Explanation
A request to perform an operation on the compression
dictionary data set (CDDS) failed because the CDDS
service was not started. Problem determination
The request fails. data (Collecting data).
Review the Db2 console for related errors. was run, and a listing of the SYSLOG data set for the
Problem determination • Dynamic dump, taken to SYS1.DUMPxx data set, by
If you suspect an error in Db2, you might need to Db2 (04E and 04F abends).
report the problem. For information about identifying • Listing of SYS1.LOGREC data set, obtained by
and reporting the problem, see Collecting diagnostic executing IFCEREP1.
data (Collecting data). • Contents of the BSDS (both copies if dual BSDS
00D10A08 in use) obtained by using the Db2 print log map
(DSNJU004) utility.
Explanation • The unformatted contents of the compression
A request to perform an operation on the compression of the CDDS.
dictionary data set (CDDS) failed because the CDDS
service failed. 00D10A0A

The request fails. A request to perform an operation on the compression
dictionary data set (CDDS) failed because fields in the
VSAM shared information area (VSI) were invalid.
Review the Db2 console for related errors. System action
The request fails.
If you suspect an error in Db2, you might need to System programmer response

If you suspect an error in Db2, you might need to Review the Db2 console for related errors.
Db2 (04E and 04F abends). • Console output from the system on which the job
executing IFCEREP1.
• Contents of the BSDS (both copies if dual BSDS Db2 (04E and 04F abends).
(DSNJU004) utility. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
dictionary data set (CDDS), or IDCAMS PRINT output • Contents of the BSDS (both copies if dual BSDS
of the CDDS. in use) obtained by using the Db2 print log map
(DSNJU004) utility.
00D10A0B • The unformatted contents of the compression
Explanation of the CDDS.
A request to perform a write operation on the 00D10A0D
compression dictionary data set (CDDS) failed because
data could not be written in the VSAM shared Explanation
information area (VSI).
A request to perform a read operation on the
compression dictionary data set (CDDS) control record
System action
failed because validation of the system control record
The request fails. failed.

Review the Db2 console for related errors. The request fails.

If you suspect an error in Db2, you might need to Review the Db2 console for related errors.
00D10A0C report the problem. For information about identifying
A request to perform a read operation on the Collect the following diagnostic items:
compression dictionary data set (CDDS) system
control record failed.
The request fails. Db2 (04E and 04F abends).

executing IFCEREP1.
Check whether the data set allocation attributes for
• Contents of the BSDS (both copies if dual BSDS the CDDS are specified correctly.
(DSNJU004) utility.
dictionary data set (CDDS), or IDCAMS PRINT output Run LISTCAT on the CDDS, and compare the data set
of the CDDS. attributes to those that are specified in Modifying Db2
for the GDPS Continuous Availability with zero data
00D10A0E loss solution (Db2 Administration Guide).
Explanation
A request to perform a write operation on the and reporting the problem, see Collecting diagnostic
compression dictionary data set (CDDS) system data (Collecting data).
control record failed.
System action
The request fails. period of time that spans the failure.
System programmer response Db2 (04E and 04F abends).
Review the Db2 console for related errors. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Problem determination • Contents of the BSDS (both copies if dual BSDS

and reporting the problem, see Collecting diagnostic 00D10A11
Explanation
• Console output from the system on which the job Allocation of the compression dictionary data set
was run, and a listing of the SYSLOG data set for the (CDDS) failed.
• Dynamic dump, taken to SYS1.DUMPxx data set, by System action
Db2 (04E and 04F abends). The request fails.
(DSNJU004) utility.
00D10A0F
Explanation
A request to perform a write operation on the data (Collecting data).
compression dictionary data set (CDDS) system
control record failed because the data set is not
usable. • Console output from the system on which the job
System action
The request fails. Db2 (04E and 04F abends).

executing IFCEREP1.
• Contents of the BSDS (both copies if dual BSDS report the problem. For information about identifying
in use) obtained by using the Db2 print log map and reporting the problem, see Collecting diagnostic
(DSNJU004) utility. data (Collecting data).
00D10A12 Collect the following diagnostic items:
A compression dictionary data set (CDDS) in proxy period of time that spans the failure.
mode was not initialized. • Dynamic dump, taken to SYS1.DUMPxx data set, by
executing IFCEREP1.
The request fails.
System programmer response (DSNJU004) utility.
Review the Db2 console for related errors. • The unformatted contents of the compression
Problem determination of the CDDS.
If you suspect an error in Db2, you might need to 00D10A15

The compression dictionary data set (CDDS) could not
Collect the following diagnostic items: be opened.
The request fails.
executing IFCEREP1. Review the Db2 console for related errors.
in use) obtained by using the Db2 print log map Problem determination
(DSNJU004) utility.
00D10A13 report the problem. For information about identifying
The log record read request to a proxy data sharing Collect the following diagnostic items:
group specified a member name that is not in the • Console output from the system on which the job
system control record of the compression dictionary was run, and a listing of the SYSLOG data set for the
data set (CDDS). period of time that spans the failure.
The request fails. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Review the Db2 console for related errors. (DSNJU004) utility.
00D10A16

A request was made to write to the compression
dictionary data set (CDDS), but an invalid record key Collect the following diagnostic items:
was specified. • Console output from the system on which the job
The write request fails. • Dynamic dump, taken to SYS1.DUMPxx data set, by

executing IFCEREP1.
Review the Db2 console for related errors. • Contents of the BSDS (both copies if dual BSDS
If you suspect an error in Db2, you might need to • The unformatted contents of the compression
report the problem. For information about identifying dictionary data set (CDDS), or IDCAMS PRINT output
and reporting the problem, see Collecting diagnostic of the CDDS.
data (Collecting data). 00D10A18
was run, and a listing of the SYSLOG data set for the An error occurred when data was copied from the
period of time that spans the failure. address space of the caller to the compression
• Dynamic dump, taken to SYS1.DUMPxx data set, by dictionary data set (CDDS).
executing IFCEREP1.
The operation fails.
• The unformatted contents of the compression Review the Db2 console for related errors.
of the CDDS. Problem determination
00D10A17 If you suspect an error in Db2, you might need to
A request was made to insert or update a record in
the compression dictionary data set (CDDS), but the Collect the following diagnostic items:
specified record length was invalid. • Console output from the system on which the job
The insert or update request fails. • Dynamic dump, taken to SYS1.DUMPxx data set, by

executing IFCEREP1.
Review the Db2 console for related errors. • Contents of the BSDS (both copies if dual BSDS
If you suspect an error in Db2, you might need to 00D10A19

An error occurred while data was copied from the Review the Db2 console for related errors.
compression dictionary data set (CDDS) to the address
space of the caller. Problem determination
System action
The operation fails. and reporting the problem, see Collecting diagnostic
Review the Db2 console for related errors. • Console output from the system on which the job
Problem determination period of time that spans the failure.
Collect the following diagnostic items: • Contents of the BSDS (both copies if dual BSDS
• Console output from the system on which the job (DSNJU004) utility.
• Dynamic dump, taken to SYS1.DUMPxx data set, by of the CDDS.
00D1F001
executing IFCEREP1.
Explanation
in use) obtained by using the Db2 print log map An internal error was detected during log manager
(DSNJU004) utility. processing.
00D10A20
System action
Explanation The request is terminated and a SVC dump is
scheduled.
The high member ID for a proxy data sharing group
in the subsystem communication block (SCOM) did
not match the high member ID in the compression System programmer response
dictionary data set (CDDS) control record. Collect the following documentation and contact the
This situation typically occurs when a new member is IBM Support Center:
added to the source data sharing group, which causes • SVC dump
the high member ID in the CDDS to be incremented.
• Syslog
System action • SYS1.LOGREC entries from the time of the error

• Additional documentation may be required
Allocation of the BSDS for the proxy member fails. depending on the exact nature of the error.

Reason code identifiers that begin with 00D3 communicate normal and error situations with the
distributed data facility.
00D30000 recovery routine (FRR) anchor. The DPSB is created
after the DPS RALE is initialized.
Explanation
System action
The operator canceled the allied agent at the
requesting location and a dump was requested, or the A record is written to SYS1.LOGREC and an SVC dump
agent abended with a reason code that indicated a is requested at the site of the Db2 abend.
possible communication problem. In either case, the
database access agent at this location abended to take Operator response
a dump to assist in problem determination.
System action
The agent terminates.
Determine which sites the abending agent was
connected to by examining the DSNL027 and
Operator response DSNL028 SYSLOG console messages at the site of the
Notify the system programmer. Db2 abend. Obtain copies of the SYS1.LOGREC and
SYSLOG data sets from each connected site, the SVC
dump at the site of the Db2 failure, and any related
dumps from each connected site.
The information collected as a result of this abend
is related to information collected at the requesting
location. Obtain a copy of the SYS1.LOGREC listing
and the SVC dump. Contact the system programmer
at the requesting location (the location name can
be determined from the dump header) to coordinate
further action. Problem determination
• Console output and the listing of the SYSLOG data
This abend was initiated in order to save diagnostic set from each connected site for the period of time
information that might be useful in problem spanning the failure.
determination. • Listings of the SYS1.LOGREC data set, obtained by
Collect the following diagnostic items: executing IFCEREP1 at each connected site.
• Console output from the system on which the job 00D30002

The distributed data facility (DDF) standard ESTAE
and FRR recovery routines detected a bad recovery
• Listing of SYS1.LOGREC data set, obtained by element. This is a Db2 internal error.
executing IFCEREP1.
Explanation is requested at the site of the Db2 abend.
The DPS RALE was not initialized. The DSNLSPRR
was invoked with the DPSB defined as the functional Operator response

System programmer response • Console output and the listing of the SYSLOG data
set from each connected site for the period of time
Determine which sites the abending agent was spanning the failure.
DSNL028 SYSLOG console messages at the site of the • Listings of the SYS1.LOGREC data set, obtained by
Db2 abend. Obtain copies of the SYS1.LOGREC and executing IFCEREP1 at each connected site.
SYSLOG data sets from each connected site, the SVC 00D30004
Explanation
report the problem. For information about identifying A database access agent received an invalid message.
and reporting the problem, see Collecting diagnostic This is a Db2 internal error.
System action
Problem determination A record is written to SYS1.LOGREC and an SVC dump
Collect the following diagnostic items: is requested at the site of the Db2 abend.

Operator response
spanning the failure. Notify the system programmer.
• Listings of the SYS1.LOGREC data set, obtained by
executing IFCEREP1 at each connected site. System programmer response
00D30003 Determine which sites the abending agent was
Explanation DSNL028 SYSLOG console messages at the site of the
Db2 abend. Obtain copies of the SYS1.LOGREC and
While establishing an ESTAE functional recovery, Db2 SYSLOG data sets from each connected site, the SVC
detected a failure. dump at the site of the Db2 failure, and any related
dumps from each connected site. If you suspect an
A record is written to SYS1.LOGREC and an SVC dump problem, see Collecting diagnostic data (Collecting
is requested at the site of the Db2 abend. data).

System programmer response set from each connected site for the period of time
connected to by examining the DSNL027 and • Listings of the SYS1.LOGREC data set, obtained by
DSNL028 SYSLOG console messages at the site of the executing IFCEREP1 at each connected site.
SYSLOG data sets from each connected site, the SVC 00D30005
dumps from each connected site. If you suspect an Explanation
For information about identifying and reporting the Db2 detected a failure while retrying Db2 recovery.
data). System action
Db2 abends after it writes a SYS1.LOGREC record and
Problem determination requests a SVC dump.

Operator response problem, see Collecting diagnostic data (Collecting
data).
This is a Db2 internal error. Obtain a copy of the
SYS1.LOGREC listing and the SVC dump. Determine • Console output and the listing of the SYSLOG data
the failing environment (Db2, IMS, CICS, or TSO). If set from each connected site for the period of time
you suspect an error in Db2, you might need to report spanning the failure.
the problem. For information about identifying and • Listings of the SYS1.LOGREC data set, obtained by
reporting the problem, see Collecting diagnostic data executing IFCEREP1 at each connected site.
(Collecting data).
00D30009
Explanation
A distributed data facility (DDF) module retried
recovery after an abend, but invalidly returned control During allocation of a database access agent,
to the DDF functional recovery routine (DSNLFRCV) simultaneous use of an APLE was attempted. An APLE
that issued the abend. can be used once during allocation of a database
access agent. This is a Db2 internal error.
period of time that spans the failure. A record is written to SYS1.LOGREC and an SVC dump
is requested at the site of the Db2 abend.
Operator response
executing IFCEREP1. Notify the system programmer.
00D30008
Explanation Determine which sites the abending agent was
The distributed transaction manager (DTM) could not DSNL028 SYSLOG console messages at the site of the
allocate a RALE for the distributed data facility (DDF). Db2 abend. Obtain copies of the SYS1.LOGREC and
This is a Db2 internal error. SYSLOG data sets from each connected site, the SVC
System action dumps from each connected site. If you suspect an
A record is written to SYS1.LOGREC and an SVC dump For information about identifying and reporting the
is requested at the site of the Db2 abend. problem, see Collecting diagnostic data (Collecting
data).
Operator response
Notify the system programmer. Problem determination
Determine which sites the abending agent was set from each connected site for the period of time
connected to by examining the DSNL027 and spanning the failure.
dump at the site of the Db2 failure, and any related 00D3000A

Db2 invoked the DSNLTDSC macro or a function of the Notify the system programmer.
distributed transaction manager (DTM). The required
function could not be performed because the DPSB System programmer response
control block does not exist. This is a Db2 internal
error. Determine which sites the abending agent was
DSNL028 SYSLOG console messages at the site of the
System action
Db2 writes a SYS1.LOGREC record and requests a SVC SYSLOG data sets from each connected site, the SVC
dump. The execution unit abnormally terminates. dump at the site of the Db2 failure, and any related
Operator response error in Db2, you might need to report the problem.
Notify the system programmer. problem, see Collecting diagnostic data (Collecting
data).
Obtain a copy of the SYS1.LOGREC listing and the SVC
dump. Determine the failing environment (Db2, IMS, Collect the following diagnostic items:
CICS, or TSO). If you suspect an error in Db2, you
might need to report the problem. For information
about identifying and reporting the problem, see
spanning the failure.
executing IFCEREP1 at each connected site.
00D3000C
Db2 detects this error when the module that
abnormally terminated is invoked and determines that
the existence of the DDF agent local anchor block Explanation
(DPSB) is not indicated by the DDF RALE or is not
The location name received in a response message
indicated by the ACE.
from a responding site disagrees with the location
Collect the following diagnostic items: name to which the request message was sent. This is a
Db2 internal error.
period of time that spans the failure. System action
• Dynamic dump, taken to SYS1.DUMPxx data set, by A record is written to SYS1.LOGREC and an SVC dump
Db2 (04E and 04F abends). is requested at the site of the Db2 abend.
00D3000B Notify the system programmer.

A function of the distributed transaction manager Determine which sites the abending agent was
(DTM) was invoked and attempted to establish connected to by examining the DSNL027 and
a functional recovery environment. The functional DSNL028 SYSLOG console messages at the site of the
recovery element (FRE) that was created was not the Db2 abend. Obtain copies of the SYS1.LOGREC and
first one on the chain of FREs anchored in the DPSB. SYSLOG data sets from each connected site, the SVC
This is a Db2 internal error. dump at the site of the Db2 failure, and any related
A record is written to SYS1.LOGREC and an SVC dump problem, see Collecting diagnostic data (Collecting
is requested at the site of the Db2 abend. data).

Problem determination DSNL028 SYSLOG console messages at the site of the
Collect the following diagnostic items: SYSLOG data sets from each connected site, the SVC
• Console output and the listing of the SYSLOG data dump at the site of the Db2 failure, and any related
set from each connected site for the period of time dumps from each connected site. If you suspect an
spanning the failure. error in Db2, you might need to report the problem.
data).
00D3000D
A request using application-directed access starting at • Console output and the listing of the SYSLOG data
site 'A' referenced an object at site 'B' that is stored at set from each connected site for the period of time
site 'A'. spanning the failure.
System action executing IFCEREP1 at each connected site.
The application statement was not processed. 00D3000F

Recode the application to remove the alias reference A Db2 resource manager attempted to add a duplicate
at the remote server that resolves to an object stored entry to the list of resource managers. This list
at the local Db2. Objects stored at the local site must contains the names of resource managers that can
be referenced using a local name. participate in the allocation of a database access agent
at a remote site. This is a Db2 error.
If necessary, consult with the data base administrators System action
at the local site and the remote server location. Db2 writes a SYS1.LOGREC record and requests a SVC
Inspect the remote SYSIBM.SYSTABLES catalog table dump. The execution unit abends.
to determine the object at this location being
referenced in a circular manner.
Operator response
00D3000E
Explanation
The DSNLFTMB macro was invoked to determine
whether an update request was sent to a specified Obtain a copy of the SYS1.LOGREC listing and the SVC
location, but the transaction has not yet been migrated dump. Determine the failing environment (Db2, IMS,
to that location. This is a Db2 internal error. CICS, or TSO). If you suspect an error in Db2, you
System action Collecting diagnostic data (Collecting data).
is requested at the site of the Db2 abend. Problem determination
The module that incorrectly invoked this function also
Operator response invoked DSNLADRA.
System programmer response was run, and a listing of the SYSLOG data set for the
Determine which sites the abending agent was period of time that spans the failure.

Db2 writes a SYS1.LOGREC record and requests a SVC
• Listing of SYS1.LOGREC data set, obtained by dump. The execution unit abends.
executing IFCEREP1.
Explanation
A Db2 resource manager attempted to delete a System programmer response
resource manager that is not given in the list of
resource managers that participate in the allocation of Obtain a copy of the SYS1.LOGREC listing and the SVC
a database access agent at a remote site. This is a Db2 dump. Determine the failing environment (Db2, IMS,
internal error. CICS, or TSO). If you suspect an error in Db2, you
dump. The execution unit abends. Problem determination
Operator response
Notify the system programmer. was run, and a listing of the SYSLOG data set for the
Obtain a copy of the SYS1.LOGREC listing and the SVC Db2 (04E and 04F abends).
dump. Determine the failing environment (Db2, IMS, • Listing of SYS1.LOGREC data set, obtained by
CICS, or TSO). If you suspect an error in Db2, you executing IFCEREP1.
about identifying and reporting the problem, see 00D30012
Explanation
Problem determination More than one resource manager attempted to reserve
the same RALE for use in the allocation of a database
This module which incorrectly invoked this function
also invoked DSNLADRA. access agent at a remote site. This is a Db2 internal
error.
dump. The execution unit abends.
Operator response
00D30011
Explanation Obtain a copy of the SYS1.LOGREC listing and the SVC
dump. Determine the failing environment (Db2, IMS,
Only a certain number of resource managers can CICS, or TSO). If you suspect an error in Db2, you
participate in the allocation of a database access agent might need to report the problem. For information
at a remote site. The maximum has been attained and about identifying and reporting the problem, see
cannot be extended. This is a Db2 internal error. Collecting diagnostic data (Collecting data).

The RALE was previously reserved by another resource Determine which sites the abending agent was
manager and is not available. connected to by examining the DSNL027 and
• Console output from the system on which the job SYSLOG data sets from each connected site, the SVC
was run, and a listing of the SYSLOG data set for the dump at the site of the Db2 failure, and any related
period of time that spans the failure. dumps from each connected site. If you suspect an
• Dynamic dump, taken to SYS1.DUMPxx data set, by error in Db2, you might need to report the problem.
Db2 (04E and 04F abends). For information about identifying and reporting the
• Listing of SYS1.LOGREC data set, obtained by data).
executing IFCEREP1.
Explanation
The facility section (DSN6FAC) in the Db2 initialization set from each connected site for the period of time
parameter module does not exist. spanning the failure.
System action executing IFCEREP1 at each connected site.
Db2 writes a SYS1.LOGREC record and requests a SVC 00D30015
dump. The distributed data facility is terminated.
Explanation
Operator response
The facility section (DSN6FAC) in the Db2 initialization
Notify the system programmer. parameter module is invalid.

This is probably an installation error. Obtain a listing of Db2 writes a SYS1.LOGREC record and requests a
the DSNZPARM module used. SVC dump. The distributed data facility (DDF) is
terminated.
Ensure that DSN6FAC was installed correctly. Operator response
00D30014 Notify the system programmer.

The distributed transaction manager (DTM) detected This is probably an installation error. Obtain a listing of
an internal error. This is a Db2 internal error. the DSNZPARM module used.

A record is written to SYS1.LOGREC and an SVC dump Ensure that DSN6FAC was installed correctly.
is requested at the site of the Db2 abend. 00D30016

Notify the system programmer. An allied agent received an invalid response. This is a
Db2 internal error.

System action about identifying and reporting the problem, see
Operator response The distributed data facility (DDF) error monitor, which
terminates the agent that is waiting for some action to
Notify the system programmer. be taken by the nonexistent agent, detects this error.
The module that was waiting for the action of the
System programmer response nonexistent agent is the module that issued the abend.
Determine which sites the abending agent was Collect the following diagnostic items:
connected to by examining the DSNL027 and • Console output from the system on which the job
DSNL028 SYSLOG console messages at the site of the was run, and a listing of the SYSLOG data set for the
Db2 abend. Obtain copies of the SYS1.LOGREC and period of time that spans the failure.
dump at the site of the Db2 failure, and any related • Dynamic dump, taken to SYS1.DUMPxx data set, by
dumps from each connected site. If you suspect an Db2 (04E and 04F abends).
error in Db2, you might need to report the problem. • Listing of SYS1.LOGREC data set, obtained by
For information about identifying and reporting the executing IFCEREP1.
data). 00D30019

Collect the following diagnostic items: The distributed data facility (DDF) error monitor
detected an error at another site which caused the
• Console output and the listing of the SYSLOG data agent at this site to be canceled. This is probably a
set from each connected site for the period of time Db2 internal error.
• Listings of the SYS1.LOGREC data set, obtained by System action
. dump. The execution unit abends.
00D30018
Operator response
An agent exists at the site at which the abend
occurred, but an agent that should exist at another System programmer response
site does not exist at that site. This is probably a Db2
internal error. Obtain a copy of the SYS1.LOGREC listing and the SVC
dump. Determine the failing environment (Db2, IMS,
CICS, or TSO). If you suspect an error in Db2, you
System action might need to report the problem. For information
Db2 writes a SYS1.LOGREC record and requests a SVC about identifying and reporting the problem, see
dump. The execution unit abends. Collecting diagnostic data (Collecting data).

Notify the system programmer. The DDF error monitor, which terminates the agent
because of an error detected at another site to which
the agent is connected and for which the agent is
System programmer response waiting, detected this error. The module that was
Obtain a copy of the SYS1.LOGREC listing and the SVC suspended to wait for the action to be taken at the
dump. Determine the failing environment (Db2, IMS, other site is the module that issued the abend.
CICS, or TSO). If you suspect an error in Db2, you Collect the following diagnostic items:

• Console output from the system on which the job The module that was suspended while waiting for
was run, and a listing of the SYSLOG data set for the some action to be taken is the module that issued the
period of time that spans the failure. abend.
• Dynamic dump, taken to SYS1.DUMPxx data set, by 00D3001B
executing IFCEREP1.
The database access request from a remote
00D3001A site failed because the SYSIBM.USERNAMES table
did not contain an inbound row describing
Explanation what Db2 authorization ID should be used for
the remote primary authorization ID. When the
A CANCEL THREAD or CANCEL DDF THREAD command USERNAMES column in SYSIBM.LUNAMES specifies
naming a distributed thread caused the thread to 'I' or 'B', requiring inbound name translation, the
be terminated. A dump is provided for diagnostic SYSIBM.USERNAMES table must contain entries
purposes as a result of the CANCEL command DUMP describing which Db2 authorization IDs are to be used
keyword. for each authorization ID received from the remote LU.

Db2 writes a SYS1.LOGREC record and requests an The DSNL030I message is issued at the server. The
SVC dump. The execution unit abends. If the canceled database access agent is not allocated.
distributed thread is an allied thread, Db2 requests
the cancellation of each associated database access
thread at each of the server sites (refer to the Operator response
explanation for 00D30000). Notify the communications database administrator

Notify the system programmer. Make sure the USERNAMES column in
SYSIBM.LUNAMES has been specified correctly for
System programmer response the indicated LUNAME. If you intend to use remote
authorization IDs that differ from Db2 authorization
The command might have been used to terminate a IDs, verify that the SYSIBM.USERNAMES table has
thread that was in a state where no processing was rows that correctly specify the Db2 authorization IDs
occurring and the thread could not continue. to be used for each possible remote authorization ID.
If you suspect an internal Db2 error, obtain a copy
of the SYS1.LOGREC listing and the SVC dump. Problem determination
Determine the failing environment (Db2, IMS, CICS, or
TSO). If you suspect an error in Db2, you might need to Analyze the SYSIBM.USERNAMES table for an
report the problem. For information about identifying incorrect or missing entry.
and reporting the problem, see Collecting diagnostic 00D3001C
Explanation
The database access request from a remote site
Collect the following diagnostic items: failed because the SYSIBM.USERNAMES table did not
• Console output from the system on which the job contain an inbound row, the TYPE column specified
was run, and a listing of the SYSLOG data set for the as an 'I' describing what Db2 authorization ID to be
period of time that spans the failure. used for the remote new user primary authorization ID.
When the USERNAMES column in SYSIBM.LUNAMES
specifies 'I' or 'B' requiring inbound name translation,
the SYSIBM.USERNAMES table must contain entries
• Listing of SYS1.LOGREC data set, obtained by describing which Db2 authorization IDs are to be used
executing IFCEREP1. for each remote authorization ID from the LU.

The DSNL030I message is issued at the server. The Analyze the SYSIBM.USERNAMES table for an
database access agent is not allocated. incorrect or missing entry.
00D3001E
Operator response
Notify the communications database administrator. Explanation
The SYSTEM PARAMETER section (DSN6SYSP) in the
System programmer response Db2 installation parameter module does not exist.
Make sure the USERNAMES column in
SYSIBM.LUNAMES has been specified correctly for System action
the indicated LUNAME. If you intend to use
remote authorization IDs that differ from the Db2 A record is written to SYS1.LOGREC, and an SVC dump
authorization IDs, verify that the SYSIBM.USERNAMES is requested. DDF is terminated.
table has rows that correctly specify the Db2
authorization IDs to be used for each possible remote Operator response
authorization ID.
Analyze the SYSIBM.USERNAMES table for an
This is probably an installation error. Obtain a listing of
incorrect or missing entry.
the DSNZPARM module used.
00D3001D
Explanation
Ensure that DSN6SYSP was installed correctly.
00D3001F
failed because the SYSIBM.USERNAMES table did not
contain an inbound row, the TYPE column specified
as an 'I' describing what Db2 authorization ID to Explanation
be used for the remote plan owner authorization ID.
ACCRDBRM received from the remote server indicates
incompatible server.
specifies 'I' or 'B', requiring inbound name translation,
describing which Db2 authorization IDs are to be used System action
for each remote authorization ID from the LU.
The TYPDEFNAM or TYPDEFOVR values returned from
the remote server in the DDM ACCRDBRM reply require
System action data type and/or code page translations that cannot
be supported by the local Db2. The local Db2 has
The DSNL030I message is issued at the server. The
disconnected the conversation with the remote server.
database access agent is not allocated.
Db2 requests neither a SVC dump nor a SYS1.LOGREC
record.
Operator response
Notify the communications database administrator. System programmer response
System programmer response report the problem. For information about identifying
data (Collecting data). Notify the system programmer
at the remote location that the remote server may not
the indicated LUNAME. If you intend to use
be usable.
remote authorization IDs that differ from the Db2
authorization IDs, verify that the SYSIBM.USERNAMES
authorization IDs to be used for each possible remote
authorization ID.

User response the SQLCODE and the SQLCA tokens returned for the
CONNECT statement.
Notify the system programmer. Invoke the application
after the problem has been corrected. The remote server and local Db2 system
administrators should consult together to determine
if this is a system configuration error, or if an internal
Problem determination error exists at either the local Db2 or remote server.
Determine the server being accessed by examining Collect the following diagnostic items:
the SQLCODE -30041 message text. Refer also to the
DDM documentation of the ACCRDB command and the • Console output from the system on which the job
ACCRDBRM reply message. was run, and a listing of the SYSLOG data set for the
00D30020
executing IFCEREP1.
Explanation
Collect the following local Db2 diagnostic items:
The processing of the CONNECT statement at a
remote server has failed. This is because acceptable • Application source code and run time listing.
CONNECT information was not conveyed in the • Relevant error and system logs spanning the time of
distributed relational database architecture (DRDA) the failure.
EXCSAT command sent by the local Db2 to the remote
00D30021
server.

The processing of the CONNECT statement at a Db2
The remote server database access agent (DBAA)
remote server has failed. This is because acceptable
sends a DRDA reply message (for example,
CONNECT information was not conveyed in the
MGRLVLRM) to the local Db2 which indicates the
distributed relational database architecture (DRDA)
specific nature of the problem. The above reason
ACCRDB command sent by the local Db2 to the remote
code is sent in the server diagnosis area of the reply
server.
message. The DBAA awaits further DRDA commands
from the local Db2.
System action
Operator response The remote server database access agent (DBAA)
sends a DRDA reply message (for example,
Operator will not detect this problem.
VALNSPRM) to the local Db2 which indicates the
specific nature of the problem. The above reason
System programmer response code is sent in the server diagnosis area of the reply
If you suspect an error in Db2, you might need to message. The DBAA awaits further DRDA commands
report the problem. For information about identifying from the local Db2.
Operator will not detect this problem.
User response
The SQLCA returned in response to the CONNECT System programmer response
statement indicates what DRDA reply message was
sent by the remote server. The user should contact the
local Db2 system administrator with this information.
This represents a DRDA configuration mismatch User response
between the local Db2 and the remote server.
The SQLCA returned in response to the CONNECT
The precise mismatch is determined from the reply
statement indicates what DRDA reply message was
message sent from the remote server to the local Db2.
sent by the remote server. The user should contact the
The reply message may be determined by examining
local Db2 system administrator with this information.

Problem determination the MVS console at the remote server, and an alert is
generated.
This represents a DRDA configuration mismatch
between the local Db2 and the remote server.
The precise mismatch is determined from the reply Operator response
message sent from the Db2 remote server to the Notify the system programmer.
local Db2. The reply message may be determined
by examining the SQLCODE and the SQLCA tokens
returned for the CONNECT statement. It could indicate System programmer response
any one of the following problems (but is not limited to If you suspect an error in Db2, you might need to
these): report the problem. For information about identifying
• The EXCSAT command was not successfully and reporting the problem, see Collecting diagnostic
processed prior to receipt of the ACCRDB command. data (Collecting data).
• The TYPDEFNAM parameter (specifies local Db2
data types) in the ACCRDB command is not Problem determination
supported. Either the user does not have the proper authority
• The TYPDEFOVR parameter (specifies local Db2 to execute at the remote server, or there is a
CCSIDs) in the ACCRDB command is not supported. security configuration mismatch in the communication
• The local Db2 product is not recognized/supported database between the local Db2 and the remote
by the remote server. server. (For example, a row might be missing in the
SYSIBM.USERNAMES table at the remote server.)
The system administrators for the two locations
should consult together to determine if this is a system Examine the DSNL030I message or the alert for
configuration error or if an internal error exists at a more specific reason code describing the failure.
either location. Consult with the two system administrators if
necessary to fix the problem. No dump is generated
Collect the following diagnostic items at the remote for this abend.
server:
was run and a listing of SYSLOG data set for the • Console output from the system on which the job
period of time spanning the failure. was run, and a listing of the SYSLOG data set for the
• Listing of SYS1.LOGREC data set obtained by
executing IFCEREP1. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
• The system CCSIDs.
Related information
Collect the following diagnostic items at the local Db2:
• Application source code and run time listing.
00D3002D
• Relevant error and system logs spanning the time of
the failure.
• The system CCSIDs. Explanation
00D30022 The connection to the remote server failed.
The SYSIBM.USERNAMES table did not contain
an outbound row and did not specify the
Explanation remote authorization ID for the plan owner Db2
The processing of the CONNECT statement at the authorization ID. When the USERNAMES column in
remote server has failed and the local Db2 Data SYSIBM.LUNAMES or SYSIBM.IPNAMES is specified as
Base Access Agent (DBAA) has been abended. This 'O' or 'B', outbound name translation is in use. The
is because authorization checking has failed at the SYSIBM.USERNAMES table must contain entries that
remote server. describe the remote authorization IDs that are used
for each Db2 authorization ID that communicates with
the LU or the TCP/IP address.
System action
The conversation with the local Db2 is terminated by
the remote server with an LU6.2 SNA sense code. The
DBAA is abended. A DSNL030I message is written to

A response is sent to the application to indicate that Collect the following diagnostic items:
the resource is unavailable. The request is not sent to
the remote site.
Operator response • Listings of the SYS1.LOGREC data set, obtained by
Notify the communications database administrator. executing IFCEREP1 at each connected site.
.
00D3002F
SYSIBM.LUNAMES or SYSIBM.IPNAMES is specified Explanation
correctly for the indicated LUNAME or IPADDR. If
you intend to use remote authorization IDs that An unrecognized function request was detected during
differ from the Db2 authorization IDs, verify that the resynchronization. This is an internal error.
SYSIBM.USERNAMES table has rows that specify the
remote authorization ID to be used for each possible System action
Db2 authorization ID. These rows must specify 'O' in
the TYPE column of the SYSIBM.USERNAMES table. A record is written to SYS1.LOGREC and an SVC dump
Operator response
incorrect or missing entry. Notify the system programmer.
00D3002E
Explanation Determine the sites to which the abending agent was
connected by examining the DSNL027 and DSNL028
No resync list entry exists during resynchronization SYSLOG console messages at the site of the Db2
when one is expected to exist. This is an internal error. abend. Obtain copies of the SYS1.LOGREC and SYSLOG
data sets from each connected site, the SVC dump at
System action the site of the Db2 failure, and any related dumps from
each connected site.
is requested at the site of the Db2 abend. If you suspect an error in Db2, you might need to
Operator response data (Collecting data).
Determine the sites to which the abending agent was
SYSLOG console messages at the site of the Db2
abend. Obtain copies of the SYS1.LOGREC and SYSLOG
data sets from each connected site, the SVC dump at • Listings of the SYS1.LOGREC data set, obtained by
the site of the Db2 failure, and any related dumps from executing IFCEREP1 at each connected site.
each connected site. .
This site is not considered a coordinator or participant
during resynchronization. This is an internal error.

Determine the sites to which the abending agent was • Console output and the listing of the SYSLOG data
connected by examining the DSNL027 and DSNL028 set from each connected site for the period of time
SYSLOG console messages at the site of the Db2 spanning the failure.
the site of the Db2 failure, and any related dumps from executing IFCEREP1 at each connected site.
each connected site. .
This site is not considered either an initiator or
Problem determination recipient of resynchronization. This is an internal error.

System action
set from each connected site for the period of time A record is written to SYS1.LOGREC and an SVC dump
spanning the failure. is requested at the site of the Db2 abend.
executing IFCEREP1 at each connected site. Operator response
. Notify the system programmer.
00D30031
Explanation Determine the sites to which the abending agent was
An unknown 2-phase COMMIT protocol is being used SYSLOG console messages at the site of the Db2
during resynchronization. This is an internal error. abend. Obtain copies of the SYS1.LOGREC and SYSLOG
Determine the sites to which the abending agent was • Console output and the listing of the SYSLOG data
connected by examining the DSNL027 and DSNL028 set from each connected site for the period of time
SYSLOG console messages at the site of the Db2 spanning the failure.

. Operator response

This site is invalidly an initiator of resynchronization. Determine the sites to which the abending agent was
This is an internal error. connected by examining the DSNL027 and DSNL028
System action abend. Obtain copies of the SYS1.LOGREC and SYSLOG
A record is written to SYS1.LOGREC and an SVC dump the site of the Db2 failure, and any related dumps from
is requested at the site of the Db2 abend. each connected site.
Notify the system programmer. and reporting the problem, see Collecting diagnostic

connected by examining the DSNL027 and DSNL028 Collect the following diagnostic items:
SYSLOG console messages at the site of the Db2 • Console output and the listing of the SYSLOG data
abend. Obtain copies of the SYS1.LOGREC and SYSLOG set from each connected site for the period of time
data sets from each connected site, the SVC dump at spanning the failure.
the site of the Db2 failure, and any related dumps from
.
and reporting the problem, see Collecting diagnostic 00D30035
Explanation
A resolved unit of work still has internal structures
Collect the following diagnostic items: associated with it during resynchronization. This is an
• Console output and the listing of the SYSLOG data internal error.
spanning the failure. System action
• Listings of the SYS1.LOGREC data set, obtained by A record is written to SYS1.LOGREC and an SVC dump
executing IFCEREP1 at each connected site. is requested at the site of the Db2 abend.
.
00D30034
Operator response
Explanation
An INDOUBT resync list entry does not
have the correct associated structures during Determine the sites to which the abending agent was
resynchronization. This is an internal error. connected by examining the DSNL027 and DSNL028
System action abend. Obtain copies of the SYS1.LOGREC and SYSLOG
A record is written to SYS1.LOGREC and an SVC dump the site of the Db2 failure, and any related dumps from
is requested at the site of the Db2 abend. each connected site.

The resync list latch is erroneously still being held
during resynchronization. This is an internal error.
• Console output and the listing of the SYSLOG data A record is written to SYS1.LOGREC and an SVC dump
set from each connected site for the period of time is requested at the site of the Db2 abend.
• Listings of the SYS1.LOGREC data set, obtained by Operator response
.
Explanation connected by examining the DSNL027 and DSNL028
Either the coordinator or participant has an invalid SYSLOG console messages at the site of the Db2
status during resynchronization. This is an internal abend. Obtain copies of the SYS1.LOGREC and SYSLOG
error. data sets from each connected site, the SVC dump at
System action
A record is written to SYS1.LOGREC and an SVC dump report the problem. For information about identifying
is requested at the site of the Db2 abend. and reporting the problem, see Collecting diagnostic
Operator response
Determine the sites to which the abending agent was set from each connected site for the period of time
connected by examining the DSNL027 and DSNL028 spanning the failure.
SYSLOG console messages at the site of the Db2 • Listings of the SYS1.LOGREC data set, obtained by
abend. Obtain copies of the SYS1.LOGREC and SYSLOG executing IFCEREP1 at each connected site.
the site of the Db2 failure, and any related dumps from .
each connected site. 00D30038
data (Collecting data). The storage calculation for the amount of storage
needed for -DISPLAY THREAD is invalid. This is an
internal error.
.
00D30037

Determine the sites to which the abending agent was spanning the failure.
data sets from each connected site, the SVC dump at 00D3003A
Explanation
report the problem. For information about identifying An error occurred during resynchronization. This is an
and reporting the problem, see Collecting diagnostic internal error.
System action

Operator response
00D30039 Determine the sites to which the abending agent was
Explanation SYSLOG console messages at the site of the Db2
A resync conversation is invalid. This is an internal data sets from each connected site, the SVC dump at
error. the site of the Db2 failure, and any related dumps from
Operator response
Determine the sites to which the abending agent was spanning the failure.
data sets from each connected site, the SVC dump at 00D3003B
Explanation
report the problem. For information about identifying A distributed thread was canceled because one of the
and reporting the problem, see Collecting diagnostic following values was exceeded:
data (Collecting data). • The idle thread timeout value that is specified
by Db2 subsystem parameter IDTHTOIN in macro
Problem determination DSN6FAC
• The ATTRIBUTE2 value in a row with
KEYWORD value MONITOR IDLE THREADS in the

SYSIBM.DSN_PROFILE_ATTRIBUTES table, for a IDLE THREADS for a profile that monitors the server
profile that monitors the thread thread, increase the ATTRIBUTE2 value in the row,
or set ATTRIBUTE2 to zero to deactivate monitoring.
The execution unit abends. IDLE THREAD TIMEOUT field (IDTHTOIN
Migration)
Operator response DDF THREADS field (CMTSTAT subsystem
Notify the system programmer. parameter) (Db2 Installation and Migration)
DSN_PROFILE_ATTRIBUTES profile table (Db2
System programmer response Performance)
The server thread was holding Db2 resources and the 00D3003C
requester application did not make a request to the
Explanation:
Db2 server thread for an extended period of time. The
A client program issued a cancel request that
server thread is terminated to release resources that
terminated processing of the SQL statement.
might affect other threads.
System action:
This usually occurs for one of these reasons:
The SQL statement was terminated and any changes
• The ACTIVE thread option was specified in the made by that statement have been undone. If an
CMTSTAT subsystem parameter, which corresponds SQL cursor is associated with the interrupted SQL
to the DDF THREADS field of the DSNTIPR statement, that cursor is closed. An sqlcode of -952
installation panel. A requester application or its user is issued.
did not make a request to the Db2 server for an
00D3003D
extended period. This can happen due to a lengthy
user absence. As a result, the server thread was Explanation:
canceled when the timeout value was exceeded. Distributed data access to an accelerator is not
supported.
Determine why the requester application has not
made a request to the Db2 server in the specified System action:
time. The connection to the accelerator server is terminated.
• The INACTIVE option was specified for subsystem Programmer response:
parameter CMTSTAT. One of the following situations Remove references to accelerator server location
occurred: names from the application.
– A requester application or its user failed to issue 00D3003E
a commit operation before an extended dormant
period, such as a user absence.
Explanation
– A requester application or its user issued a
commit operation before an extended dormant A connection or thread that is running under
period, but database resources were still being KEEPDYNAMIC refresh rules was actively in use
held because of other conditions. for more than one hour. A unit-of-work was
completed and only packages bound with the
As a result, the server thread could not be moved KEEPDYNAMIC(YES) option are causing the thread to
to the inactive state, and was canceled when the remain active with its connection.
timeout value was exceeded.
This condition might normal if the client connected
Determine why the server thread was not moved to to Db2 indicating that it uses KEEPDYNAMIC(YES)
the inactive state. packages and it is enabled for either:
If the design or use of the application requires • Sysplex workload balancing.
additional time, take one of the following actions:
• Seamless failover.
• Increase the value of the IDTHTOIN subsystem
parameter, or set it to zero to deactivate idle thread Under the support for KEEPDYNAMIC refresh rules
timeout. from the following drivers, when a client socket
is closed from the server, the client attempts to
• If the server thread is monitored by profile tables, reconnect back to the same server and marks that all
and the SYSIBM.DSN_PROFILE_ATTRIBUTES profile
table contains a row with KEYWORD value MONITOR

statements managed under the connection need to be User response
prepared.
• IBM Data Server Driver for Java
Related concepts
• IBM Data Server Driver for ODBC/CLI/.NET
Methods for keeping prepared statements
after the point of commit or rollback (Db2
System action Performance)
The connection or thread is terminated. Related tasks
Enabling KEEPDYNAMIC refresh for DBATs (Db2
Performance)
User response
Related reference
No action is required. BIND and REBIND options for packages, plans,
Related concepts and services (Db2 Commands)
Methods for keeping prepared statements
00D30040
after the point of commit or rollback (Db2
Performance)
Enabling KEEPDYNAMIC refresh for DBATs (Db2 An invalid or incomplete DDF communication record
Performance) was found in the BSDS.
Related reference
BIND and REBIND options for packages, plans, System programmer response
and services (Db2 Commands)
Use the DSNJU003 change log inventory utility to add
00D3003F a valid DDF communication record to the BSDS.
00D30041
Explanation
A connection or thread that is running under Explanation
KEEPDYNAMIC refresh rules was idle for more than
An invalid subsystem IPv4 address was found the
20 minutes. A unit-of-work was completed and only
BSDS. The specified address does not conform to
packages bound with the KEEPDYNAMIC(YES) option
dotted decimal form.
are causing the thread to remain active with its
connection.
This condition might be normal if the client connected
to Db2 indicating that it uses KEEPDYNAMIC(YES) Use the DSNJU003 change log inventory utility to
packages and it is enabled for either: correct or remove the BSDS DDF communication
record subsystem IPv4 address. See the IPV4 and
• Sysplex workload balancing. NOIPV4 keywords of the DDF statement for more
• Seamless failover. information.
Under the support for KEEPDYNAMIC refresh rules 00D30042
from the following drivers, when a client socket
is closed from the server, the client attempts to
reconnect back to the same server and marks that all
Explanation
statements managed under the connection need to be An invalid subsystem IPv6 address was found the
prepared. BSDS. The specified address does not conform to
• IBM Data Server Driver for JDBC and SQLJ colon hexadecimal form.
• IBM Data Server Driver for ODBC/CLI/.NET

System action Use the DSNJU003 change log inventory utility to
correct or remove the BSDS DDF communication
The connection or thread is terminated. record subsystem IPv6 address. See the IPV6 and
NOIPV6 keywords of the DDF statement for more
information.

00D30043 an IPNAME value is specified, DDF will only attempt
to activate its TCP/IP communications support which
needs values for PORT and RESPORT in the BSDS DDF
Explanation
record.
An invalid group IPv4 address was found the BSDS.
The specified address does not conform to dotted System programmer response
decimal form.
Use the DSNJU003 change log inventory utility to add
non-zero values for the PORT and RESPORT fields of
the BSDS DDF record or to remove the IPNAME value if
Use the DSNJU003 change log inventory utility to SNA/APPC communication is needed.
correct or remove the BSDS DDF communication
00D30050
record group IPv4 address. See the GRPIPV4 and
NGRPIP4 keywords of the DDF statement for more
information. Explanation
00D30044 A distributed thread was aborted because a server
thread held Db2 resources, and the requesting
application did not make a request to the Db2 server
Explanation
thread for an extended period of time. The amount of
An invalid group IPv6 address was found the BSDS. time that the distributed thread was idle exceeded the
The specified address does not conform to colon setting for the MONITOR IDLE THREADS keyword in a
hexadecimal form. monitor profile. That monitor profile also specified an
EXCEPTION_ROLLBACK action for one of the following
filtering scopes:
• LOCATION
Use the DSNJU003 change log inventory utility to
correct or remove the BSDS DDF communication • PRDID
record group IPv6 address. See the GRPIPV6 and • ROLE_AUTHID
NGRPIPV6 keywords of the DDF statement for more
• ROLE
information.
• AUTHID
00D30045
• COLLID_PKGNAME
• COLLID
Explanation
• PKGNAME
An subsystem IPv4 or IPv6 address is invalid with
respect to the specified group IPv4 or IPv6 address. • CLIENT_APPLNAME
Data sharing members require subsystem or member • CLIENT_USERID
and group pairs. That is, if a subsystem or member IP • CLIENT_WRKSTNNAME
address is specified, a corresponding group address is
also required since the Db2 subsystem is a member of
a data sharing group. System action
The server thread is aborted. The connection with the
System programmer response remote application is maintained.
Use the DSNJU003 change log inventory utility to If the aborted transaction performed database
add a corresponding group address or to remove the updates, the application environment is placed in a
subsystem or member address. See the GRPIPV4, must-abort state so that the application environment
GRPIPV6, NOIPV4, and NOIPV6 keywords of the DDF is made aware of the resources that have been
statement for more information. destroyed as a result of the aborted threads.
00D30046 Important: If either of the following situations are

true, Db2 hides the EXCEPTION_ROLLBACK event
from the remote application environment:
Explanation
• The aborted transaction performed only read-only
A value was found for the IPNAME field of the BSDS operations.
DDF record but only zero values were found for the
PORT and RESPORT fields in the BSDS DDF record. If

• The transaction committed or aborted, but the 2. Issue the START PROFILE command to refresh the
associated database access thread remained active exception threshold value.
before it became idle.
Related tasks
Because the EXCEPTION_ROLLBACK event is not Monitoring idle threads by using profile tables
visible to the remote application environment in (Db2 Administration Guide)
those cases, it might appear to the remote Related reference
application environment that the database resources
IDLE THREAD TIMEOUT field (IDTHTOIN
are unexpectedly disappearing. For example, held
cursors, kept dynamic statements, and declared
Migration)
temporary tables that were created in the transaction
are destroyed. DDF THREADS field (CMTSTAT subsystem
Operator response Performance)
Notify the system programmer. -START PROFILE (Db2) (Db2 Commands)
00D30051
Review the information that is provided in the Explanation
DSNL030I message. The condition usually occurs for
one of the following reasons: Authentication failed for a distributed thread. A remote
client environment used a digital client certificate for
• The ACTIVE option was specified for subsystem
authentication, but a required trusted context was not
parameter CMTSTAT, which corresponds to the DDF
defined at the Db2 for z/OS server.
THREADS field of the DSNTIPR installation panel.
A requester application or its user did not make a The information that is provided in the associated
request to the Db2 server for an extended period. DSNL030I message includes the user ID and the
This might happen because of a lengthy user IP address of the remote client environment. A
absence. As a result, the server thread was aborted Db2 trusted context is required for the specified
when the timeout value was exceeded. user ID. The remote client environment accesses
the Db2 server using digital certificates, through SSL
Determine why the requesting application did not
client authentication. The user ID that is provided
make a request to the Db2 server in the specified
by the remote client is different from the user ID
time.
that is associated with the client digital certificate
• The INACTIVE option was specified for subsystem at the server. Therefore, additional authentication is
parameter CMTSTAT. One of the following situations required. Db2 uses the user ID that is obtained from
occurred: the certificate to search for a trusted context. When
– A requester application or its user failed to issue the trusted context exists, Db2 processes the remote
a commit operation before an extended dormant client user ID that is specified in the message as
period, such as a user absence. a trusted context switch-user request. However, the
trusted context did not exist, so a switch-user request
– A requester application or its user issued a could not be performed.
commit operation before an extended dormant
period, but database resources were still being
held because of other conditions. System action
As a result, the thread could no be moved to the Authentication fails, and the connection with the
inactive state, and was aborted when the timeout remote client environment is terminated.
value was exceeded.
Determine why the server thread was not moved to Operator response
the inactive state. Notify the system programmer.
If the design or use of the application requires
additional time, follow these steps: System programmer response
1. Modify the exception threshold for the Review the information that is provided in the
MONITOR IDLE THREADS profile in the associated DSNL030I message. Create a trusted
SYSIBM.DSN_PROFILE_ATTRIBUTES table. context for the user ID that is specified in the
information for the remote client environment.

If you suspect an error in Db2, you might need to This name of the module that invoked the function
report the problem. For information about identifying given as the abending module name. This is not the
and reporting the problem, see Collecting diagnostic module in error. An earlier failing module neglected to
data (Collecting data). report error information in the DTMF block.
Collect the following diagnostic items: Collect the following diagnostic items:
• Console output from the system on which the error • Console output from the system on which the job
occurred was run, and a listing of the SYSLOG data set for the
• Trusted context definition period of time that spans the failure.
• AT-TLS policy configuration, in which • Dynamic dump, taken to SYS1.DUMPxx data set, by
HandShakeRole is set to ServerWithClientAuth Db2 (04E and 04F abends).
• RACF RACDCERT commands that were used to add • Listing of SYS1.LOGREC data set, obtained by
the client certificate to the keyring at the z/OS server, executing IFCEREP1.
including any RACDCERT MAP commands if RACF 00D300F2
certificate name filtering is used
Encrypting your data with Secure Socket Layer
EXCSATRD reply received from a remote server
(SSL) support (Managing Security)
indicates an incompatible server.
Related reference
CREATE TRUSTED CONTEXT (Db2 SQL)
System action
Related information
DSNL030I (Db2 Messages) The manager levels returned from the local Db2 in
Managing access through trusted contexts the DDM EXCSATRD reply were too low for the local
(Managing Security) Db2 to support. The local Db2 has disconnected the
conversation with the remote server. Db2 requests
00D300F1 neither an SVC dump nor a SYS1.LOGREC record
written.
Explanation
The DSNLTOKS macro was invoked to extract
error information from the DTMF block using the If you suspect an error in Db2, you might need to
CHECK_SQLCODE keyword and the DTMF block was report the problem. For information about identifying
either uninitialized or contained an SQL return code and reporting the problem, see Collecting diagnostic
that was not negative. This is a Db2 internal error. data (Collecting data). Notify the system programmer
at the remote location that the remote server is not
usable.
System action
A record is written to SYS1.LOGREC and an SVC User response
dump is requested. The execution unit is abnormally
terminated. Notify the system programmer. Invoke the application
after the problem has been corrected.
Operator response
Determine the server being accessed by inspecting
the SQLCODE -30041 message text. Refer to the DDM
System programmer response documentation of the EXCSAT command.
This is a Db2 internal error. Obtain a copy of 00D300F3
SYS1.LOGREC and the SVC dump. Determine the
failing environment (Db2, IMS, CICS, or TSO). If you
the problem. For information about identifying and The connection to the remote server failed. The
reporting the problem, see Collecting diagnostic data SYSIBM.USERNAMES table did not contain an
(Collecting data).

outbound row and did not specify the remote 'COMMIT' statement, determine if manual recovery of
authorization ID for the new user primary Db2 the unit of work is necessary.
authorization ID. When the USERNAMES column in
SYSIBM.LUNAMES or SYSIBM.IPNAMES is specified as Operator response
'O' or 'B', outbound name translation is in use. The
SYSIBM.USERNAMES table must contain entries that Notify the operator or systems programmer for the
describe the remote authorization IDs that are used remote server.
for each Db2 authorization ID that communicates with
the LU or the TCP/IP address. System programmer response
Determine the product type of the server. The DISPLAY
System action
THREAD command may be used. Refer to the server
A response is sent to the application to indicate that products' diagnostic recommendations. If the server
the resource is unavailable. The request is not sent to DBMS is Db2, contact your IBM representative to
the remote site. report the problem and open an APAR.

Notify the communications database administrator. The problem originated with the remote server. Follow
the diagnostic recommendations published for the
server DBMS product, which might not be Db2.
Make sure the USERNAMES column in 00D300F5
SYSIBM.LUNAMES or SYSIBM.IPNAMES is specified
correctly for the indicated LUNAME or IPADDR. If Explanation
you intend to use remote authorization IDs that
DDM command chaining is in use.
differ from the Db2 authorization IDs, verify that the
remote authorization ID to be used for each possible System action
The DTM module returns to its invoker with a return
the TYPE column of the SYSIBM.USERNAMES table.
code = 4.
Problem determination 00D300F6

Explanation
A valid but unexpected DDM reply was received from
00D300F4
a remote server during a connect, commit, or abort
operation. For a connect, the expected DDM reply
Explanation is EXCSATRD (for EXCSAT command) or ACCRDBRM
(for ACCRDB command). For a commit or abort,
A DRDA protocol error occurred. Either a reply chain
the expected DDM reply is ENDUOWRM. (The DDM
is broken but there is no DDM reply with a high
command for a commit is RDBCMM. For a rollback, it is
enough severity to break the chain, or a message
RDBRLLBCK).
chain is unbroken in spite of a high severity code,
or a conversation expected to be available has been
terminated. The problem, though detected by Db2, is System action
believed to have originated at the remote server. The
The local Db2 tried to access a remote server and
server might not be a Db2 subsystem.
the server replied with an unexpected DDM answer.
The remote server may have suffered permanent
System action damage. The local Db2 may or may not subsequently
disconnect the conversation to the server. This is an
This reason code is returned to the application. A
internal-only DDF reason code. The local Db2 requests
request message has likely been sent to the remote
neither a SVC dump nor a SYS1.LOGREC record.
site but the outcome is uncertain. A DSNL031I
message may have been written to the console.
Refer to the description of this message for more
information. If this reason code is returned for an SQL

System programmer response 00D300F8
If the SQLCA is available, examine all fields in
the SQLCA. Using this information, try to determine Explanation
what DDM reply was received. Contact the system An attempt was made to access data at a remote
programmer at the server site with this information. location that has been started in restricted access
This is probably a programming error at the server mode. When a Db2 system is started in restricted
database system, although it may be a Db2 error. The access mode, no remote inbound or outbound access
server database system may have recorded diagnostic is allowed.
information for the problem. If this is a Db2 error, write
an APAR.
System action
User response Remote access is not allowed.
Contact the system programmer
Operator response
Examine the SQL return code in the SQLCA. It should
give further indication of the real cause. System programmer response
00D300F7 Determine the remote location where the remote
data access was attempted. Retry the request when
the remote location and/or the local Db2 has been
Explanation restarted in full access mode.
A DDM reply message was too big to fit in the DTM 00D300F9
reply buffer.
Explanation
System action
The Db2 server was unable to allocate a database
The requesting allied agent is terminated. A access agent since the maximum number allowed was
SYS1.LOGREC record is written and an SVC dump is zero (ZPARM MAXDBAT value was zero).
requested at the local Db2.
System action
Operator response
The Db2 server terminates the conversation with a
Notify the system programmer. 084B6031 SNA sense code for application-directed
access and a 00D300F9 Db2 code for system-directed
System programmer response access. A DSNL030I message containing this reason
code is written to the MVS operator console at the Db2
If you suspect an error in Db2, you might need to server site.
At the server, currently no data base access agents
Problem determination are allowed because the MAXDBAT value in the ZPARM
is zero. If access to this site from a remote site is
This error should never occur. Write an APAR. desirable, change the MAXDBAT parameter in ZPARM
Collect the following diagnostic items: to the maximum number of database access agents
needed. Restart Db2 at the server. Notify the user to
• Console output from the system on which the job rerun the application.
period of time that spans the failure. 00D300FA
data set, as result of an operator-initiated dump Explanation
You attempted a COMMIT statement for a plan that
• Listing of SYS1.LOGREC data set, obtained by specified ISOLATION (RR) and update operations were
executing IFCEREP1. performed either at the local site or at a remote

site. The COMMIT operation could not be performed System programmer response
because the COMMIT request could not be transmitted
to a remote site where Repeatable Read operations If you suspect an error in Db2, you might need to
had been performed. report the problem. For information about identifying
System action
All update operations were backed out. User response
Notify the system programmer. Invoke the application
System programmer response after the problem has been corrected.
Determine why the COMMIT failed and retry the
application. Problem determination
00D300FB Determine the resource being allocated and correct
the problem.
Explanation 00D300FD
A resource was not available during database access
agent allocation at a remote site. Explanation
An attempt was made to disconnect a connection with
System action a specified location, but the transaction has not yet
The allocation of the database access agent was been connected to that location. This is a Db2 internal
unsuccessful. A 'resource not available' code is error.
returned to the user. Db2 requests neither a SVC dump
nor a SYS1.LOGREC record. System action
A record is written to SYS1.LOGREC and an SVC
System programmer response dump is requested. The execution unit is abnormally
If you suspect an error in Db2, you might need to terminated.
Obtain a copy of SYS1.LOGREC and the SVC dump.
Determine the failing environment (Db2, IMS, CICS, or
User response TSO). If you suspect an error in Db2, you might need to
Notify the system programmer. Invoke the application report the problem. For information about identifying
after the problem has been corrected. and reporting the problem, see Collecting diagnostic
Problem determination The name of the module that invoked the function
incorrectly is given as the abending module name.
Determine the name of the resource being allocated
and correct the problem. Collect the following diagnostic items:
00D300FC • Console output from the system on which the job

Explanation
You attempted to allocate a resource at a remote site Db2 (04E and 04F abends).
using an invalid name.
executing IFCEREP1.
System action
00D300FE
The allocation of the database access agent was
unsuccessful. A 'resource not available' code is
Explanation
returned to the user. Db2 requests neither a SVC
dump nor a SYS1.LOGREC record. This reason code is You executed a COMMIT statement and update
returned only for system-directed access (DSNLTMRA). operations were performed at a remote site. The

success of the COMMIT operation could not be System programmer response
determined because a failure occurred at the remote
site or in the communication link with the remote site See Problem Determination.
after the request to commit the operation had been
transmitted. User response
Notify the system programmer of the failure.
System action
After the problem causing the chain to be broken at
The remote updates have been committed or backed the remote server is fixed, rerun the application and
out, depending on when the error occurred. perform the updates again.

After communication has been reestablished with the Collect the following diagnostic items from the local
remote site, use SQL to query the updated data to Db2 system.
determine whether the updates were committed. If
the updates were not committed, rerun the application • Listing of application program and output from
and perform the updates again. application program.
• Console output and a listing of SYSLOG data set for
00D300FF
the period of time spanning the failure.
Explanation executing IFCEREP1.
You attempted a COMMIT statement and update Consult with the remote server system programmer to
operations were performed at a remote site. The determine the cause of the error.
attempt failed.
The remote server system programmer may need to
collect the following remote server diagnostic items:
System action
The updates at the remote site have been backed out. the failure.
• Any relevant remote server dumps.
User response
00D30101
Explanation
A COMMIT was attempted but failed due to a prior
Determine why the COMMIT failed and retry the error. Communications to a remote site have been lost.
application. The COMMIT operation cannot be performed because
00D30100 the COMMIT request could not be transmitted to a
remote site. If the program has performed updates,
the updates have been backed out to the prior
Explanation COMMIT point.
A COMMIT statement was chained to a set of
commands sent to an remote server. The remote System action
server stopped processing the chained commands
before it reached the COMMIT. COMMIT was NOT All update operations were backed out.
performed.
Operator response
Any updates performed within the current unit of Work
have been backed out. System programmer response
Restart DDF at the affected sites and rerun the
Operator response application.
Operator will not detect this problem. 00D30103

This reason code may be returned for a failed
distributed commit using DRDA protocols. It indicates Explanation
that commit has failed because an ABNUOWRM reply The unit-of-work disposition (commit or rollback)
message was received from the server for a prior received from a DRDA server is inconsistent with the
SQL statement, but an abort had not been driven at command sent (commit or rollback), and the SQLCODE
the Db2 requester prior to this commit and after the returned from the server. For example, if a commit is
receipt of the ABNUOWRM. sent to the server, and the reply message indicates the
An ABNUOWRM reply message is sent by the unit of work (UOW) was committed, but the SQLCODE
server when it has rolled back its unit-of-work in returned is negative, then this reason code will be
response to an unusual situation at the server (for contained in the alert sent to NetView®.
example, deadlock or operator intervention). When
an ABNUOWRM reply message is received by the System action
requester, an abort must be driven at the requester
to synchronize the distributed systems. Until an abort An alert is generated and sent to NetView. Two trace
is driven, all subsequent SQL statements will receive records, IFCID 0191 and IFCID 0193, may be written
an SQLCODE -906. After an abort is driven, further SQL to the Statistics Class 4 trace, and two DSNL031I
statements will be accepted. messages may be written to the console. The trace
records and messages will not be written if this error
was previously detected within the last 5 minutes. The
System action Statistics Class 4 trace must be active for the trace
The commit at the Db2 requester fails. records to be written.
An SQLCODE +30100, -30020, or -30030 is returned
Operator response to the application. An SQLCODE -30020 indicates
a rollback was sent to the DRDA server, but a
The operator will not detect this problem. commit unit-of-work disposition was received. An
SQLCODE +30100 or -30030 conveys the unit-of-work
System programmer response disposition reported by the server, and replaces the
original SQL return code sent by the server, which was
Determine the cause of the problem represented by
not consistent with the UOW disposition. The original
the SQLCODE returned with the ABNUOWRM and if
SQL return code and SQLSTATE returned by the server
necessary, work with the system programmer at the
are saved as tokens in the SQLCA.
server to resolve it. If you suspect an error in Db2,
about identifying and reporting the problem, see Operator response
Collecting diagnostic data (Collecting data). Notify the system programmer.

Scan backwards in your application for the first non This is a DRDA distributed protocol problem. Once
-906 SQLCODE prior to the commit. This SQLCODE the nature of the inconsistency is known, the server
was returned with the ABNUOWRM from the server system programmer may have to be contacted to help
system. Use the server product reference manuals resolve the problem. If you suspect an error in Db2,
to determine and correct whatever problem this you might need to report the problem. For information
SQLCODE represents on the server and rerun your about identifying and reporting the problem, see
application. This may involve contacting your system Collecting diagnostic data (Collecting data).
programmer if the situation at the Server cannot be
corrected or improved by changes to the application
program. Problem determination
Problem determination • Listing of the user's application program output,
Collect the following diagnostic items: including printouts of the SQLCAs received for all
SQL statements.
• User's application output, including SQLCAs returned
for each SQL statement.

was run, and a listing of SYSLOG data set for the
period of time spanning the failure. A distributed commit has failed because the allied
agent was canceled as a result of a STOP DDF
• Listing of the Statistics Class 4 trace records for the MODE(FORCE) command during a previous execution
LUWID associated with the failing request. of DDF which has terminated. When an allied agent
If no DSNL031I messages were written at the same does not issue database requests for more than 2
time as the alert, then scan the log backwards for minutes after a STOP DDF MODE(FORCE) command is
previous DSNL031I messages. A Db2 filter function issued, DDF will come down without terminating the
prohibits multiple occurrences of the same problem allied agent. The agent is canceled when it makes its
detected within a 5 minute period from flooding the next request to Db2.
console and trace data set with diagnostic information.
You will have to find an earlier occurrence of the same System action
problem to start diagnosing it.
The commit operation is failed and the agent is
Once you have found the two DSNL031I messages, canceled. The last unit of work was rolled back at
locate the IFCID 0191 and 0193 trace records written all server systems when the STOP DDF MODE(FORCE)
for the problem by using the IFCID sequence numbers command was processed.
from the DSNL031I messages.
The IFCID 0193 trace record will document the nature Operator response
of the inconsistency (command sent, UOW disposition
received, SQL return code received). Re-start DDF.
The IFCID 0191 trace record will document the

exact data stream returned from the Server. Use this User response
information to determine if the reply message from Contact the operator to re-start DDF. After DDF is re-
the server was correctly converted into the UOW started, continue your application's work starting with
disposition and the SQL return code reported in the the last unit of work that was rolled back.
IFCID 0193 record. If the data stream was correctly
converted, then the problem lies at the server and you 00D30106
should contact the system programmer at the server
and have him or her analyze the data stream produced Explanation
by the server.
The result of a DRDA distributed commit could not
Related information be determined because the reply message from the
DSNL031I (Db2 Messages) server either was invalid or could not be deciphered.
+30100
OPERATION COMPLETED SUCCESSFULLY System action
BUT A DISTRIBUTION PROTOCOL
VIOLATION HAS BEEN DETECTED. ORIGINAL An alert is generated and sent to NetView. An IFCID
SQLCODE=original-sqlcode AND ORIGINAL 0191 trace record may be written to the statistics
SQLSTATE=original-sqlstate class 4 trace, and a DSNL031I message may be
written to the console. The trace record and message
-30020
will not be written if this error was previously detected
EXECUTION FAILED DUE TO A DISTRIBUTION
within the last 5 minutes. The statistics class 4 trace
PROTOCOL ERROR THAT CAUSED
must be active for the trace records to be written.
DEALLOCATION OF THE CONVERSATION:
REASON reason-code (sub-code) The requester disconnects from the server system.
The state of the unit of work at the server is
-30030
unknown. It may have been committed, or it may have
COMMIT REQUEST WAS UNSUCCESSFUL,
been rolled back. An SQLCA indicating the nature of
A DISTRIBUTION PROTOCOL VIOLATION
the DRDA reply message distortion is given to the
HAS BEEN DETECTED, THE CONVERSATION
application.
HAS BEEN DEALLOCATED. ORIGINAL
SQLCODE=original-sqlcode AND ORIGINAL
SQLSTATE=original-sqlstate Operator response
Notify the system programmer whenever a DSNL031I
00D30105
message is written to the MVS console.

This is a DRDA distributed protocol problem. Once the Phase 1 of a distributed commit failed. One or more
nature of the problem is known, the server system remote servers did one of the following actions:
programmer may have to be contacted to help resolve
• Voted NO
the problem.
• Voted heuristic mixed
report the problem. For information about identifying • Experienced a communications error
and reporting the problem, see Collecting diagnostic • Made an error in their use of commit protocol
System action
User response
The commit fails. The unit of work is backed out.
Notify the system programmer. After the problem
For communication errors, message DSNL406I is
has been resolved, re-connect to the server site
written to the system console, alert A006 is generated,
to determine whether the last unit of work was
and trace record IFCID 0209 is produced to record the
committed or rolled back. Continue your application
server affected (LUWID of the unit of work, and other
after correcting the server database (if necessary).
information).
Problem determination For protocol errors, message DSNL413I is written to

the system console, alert A005 is generated, and trace
Collect the following diagnostic items: record IFCID 0208 is produced to describe the nature
of each server's protocol violation.
• Listing of the user's application program output,
including printouts of the SQLCAs received for all
SQL statements. System programmer response
• Console output from the system on which the job For protocol errors, contact the system programmer
was run, and a listing of SYSLOG data set for the for the remote site. The invalid sync point message is
period of time spanning the failure. recorded in the IFCID 0208 trace record. The system
• Listing of the statistics class 4 trace records. logic error that causes the invalid sync point message
must be corrected at the remote site.
If no DSNL031I message was written at the same
time as the alert, then scan the log backwards for
a previous DSNL031I message. A Db2 filter function User response
prohibits multiple occurrences of the same problem Contact the Db2 systems programmer. If the commit
detected within a 5 minute period from flooding the failed for other than a commit protocol violation by a
console and trace data set with diagnostic information. remote server, resubmit your application. Otherwise,
You will have to find an earlier occurrence of the same wait for resolution of the protocol error.
problem to start diagnosing it.
Once you have found the DSNL031I message, locate Problem determination
the IFCID 0191 trace record written for the problem by
using the IFCID sequence number from the DSNL031I Collect the following diagnostic items:
message. • Console output from the system on which the job
The IFCID 0191 trace record will document the was run, and a listing of the SYSLOG data set for the
exact data stream returned from the server. Use this period of time that spans the failure.
information to determine if the reply message from the 00D3010A
Server was correct, and if so, the error resides with the
Db2 AR.
Explanation
If the data stream is incorrect, then the problem
lies at the server and you should contact the system This might occur when a version of IMS that does
programmer at the server and have he or she analyze not support the COMMIT VERIFY exit is running an
the data stream produced by the server. IMS MODE=MULTI application with one or more non-
Db2 servers. This is probably a user error, since this
00D30109 scenario is not supported by Db2 and IMS unless the
IMS version is 4 or later.

IMS requested a new user SIGNON without an System action
immediately preceding commit or abort, and your
application was connected to one or more remote non- The connection to the server is deallocated. The
Db2 servers. In order to preserve the consistency of server's portion of the current unit of work is rolled
database updates made at several different servers, back at the server. The application is placed in a must-
when at least one server is a non-Db2 server, a commit abort state. All subsequent operations except rollback
or abort must precede any new user SIGNON. or abort fail with an SQLCODE -918. The remainder of
the current unit of work is backed out when rollback or
abort is performed or when the application terminates.
System action
The execution unit writes a record to SYS1.LOGREC. User response
No dump is requested. The IMS application terminates
as a result of the abend. If your application does not do any work at a server
for a long time after issuing a CONNECT, consider
rewriting it to perform the CONNECT immediately
Operator response before performing any work at the server. This
Collect the SYS1.LOGREC. Notify the system minimizes the possibility of the server system going
programmer. down and coming back up at a different SYNC_LEVEL.
Rerun your application starting with the unit of
System programmer response work containing the SQL statement that received an
SQLCODE -904.
Determine if the IMS version and release being
used invokes the Db2 COMMIT VERIFY exit, which 00D3010C
is available in Version 3 and later. Obtain the
SYS1.LOGREC. Explanation
If you suspect an error in Db2, you might need to Cached information was used to determine whether
report the problem. For information about identifying updates are allowed at the server. From the time of
and reporting the problem, see Collecting diagnostic the execution of the CONNECT statement to the time
data (Collecting data). that the first SQL statement was sent to the server,
the partner was started with a program that does not
Problem determination support two-phase commit.
Collect the following diagnostic items: Such servers are not allowed to update in the current
unit of work. Since an update might have been
• Console output from the system on which the job performed by the partner during execution of the first
was run, and a listing of the SYSLOG data set for the statement at the server, the application must roll back.
This reason code is returned as a token in the
00D3010B SQLCODE -904.

Cached information was used to determine whether The connection to the server is deallocated. The
updates are allowed at the server. From the time of server's portion of the current unit of work is rolled
the execution of the CONNECT statement to the time back at the server. The application is placed in a must-
that the first SQL statement was sent to the server, the abort state. All subsequent operations except rollback
conversation SYNC_LEVEL supported by the partner or abort fail with an SQLCODE -918. The remainder of
changed from a cached value of SYNC to the current of the current unit of work is backed out when rollback or
value NONE. abort is performed or when the application terminates.
SYNC_LEVEL NONE servers are not allowed to update
in the current unit of work. Since an update might have User response
been performed by the partner during execution of the
first statement at the server, the application must roll If your application does not do any work at a server
back (abort). for a long time after issuing a CONNECT, consider
rewriting it to perform the CONNECT immediately
This reason code is returned as a token in the before performing any work at the server. This
SQLCODE -904. minimizes the possibility of the server system going
down and coming back up at a different level.

Rerun your application starting with the unit of User response
work containing the SQL statement that received the
SQLCODE -904. Notify the system programmer.
00D3010D 00D3010F
Db2 requested updates at multiple servers, but at Db2 was unable to authenticate the DRDA user, due to
least one server does not support distributed two- an error detected by RACF or DCE.
phase commit.
System action
System action The user's attempt to connect is rejected. An
If the application is using TSO or BATCH attach, then SQLCODE -30082 is returned to the application.
Db2 rolls back the UOW. If the application is using
CICS or IMS attach, then CICS or IMS rolls back the System programmer response
UOW after receiving the NO commit vote from Db2.
Correct the error detected by DCE or RACF. Both
products write messages to the MVS console
User response describing the error.
Change the application so that updates to multiple
servers (including the local server) are not performed User response
within a single UOW unless all the update servers in
the UOW support distributed two-phase commit. Notify the system programmer.
00D30110
In the UOW that was not committed, the first SQL Explanation
statement that performed an update that was not A DRDA error occurred. The Db2 crypto security
allowed received an SQLCODE -919. All subsequent component detected an error and could not process
SQL statements also received an SQLCODE -919 until the encryption security tokens used to authenticate
a ROLLBACK or a static ROLLBACK SQL statement was the user.
executed (if either occurred).
00D3010E System action
The attempt to connect to Db2 fails, the failure is
Explanation reported to the SQL application with an SQLCODE of
The DRDA server system does not support -30082, and the connection is terminated.
the authentication mechanism specified in the
communications database. For example, the System programmer response
communications database specified that RACF
passtickets were supposed to be used, but the server Determine the reason for the failure by verifying
does not support it. the DRDA data stream and by reviewing the server
diagnostic work area returned in the DRDA security
check reply message.
System action
The attempt to access the remote server fails. An Problem determination
SQLCODE -30073 is returned to the application.
Modify the row in SYSIBM.LUNAMES or data (Collecting data).
SYSIBM.IPNAMES to specify a security mechanism in 00D30111
the SECURITY_OUT column that the remote server
supports.

Db2 SAF Identity Mapping service encountered an Check the console message and the reason code in the
error when a request was made to process a user message for further analysis. Determine the reason for
registry name. failure by verifying the DRDA data stream. If the server
diagnostic work area is returned in the DRDA reply
System action message, check the contents of the server diagnostic
work area.
The Db2 SAF Identity Mapping service request is
not processed. Normal connection authentication
continues.
00D30112
Integrated Cryptographic Service Facility (ICSF) 00D30113
detected an error and could not process the DRDA
request.
Explanation
System action Authentication of a remote user was rejected by Db2
because the user ID that was provided by the remote
A DSNL045I or DSNL046I message might have been system or user exceeds eight characters.
written to the console. Refer to the description of the
The Db2 operating environment is restricted to no
message for more information.
more than eight characters for user IDs. Remote client
If ICSF fails during connection processing at the Db2 environments must be changed to comply with this
requester, the connection attempt fails, and the failure restriction.
is reported to the application with SQLCODE -904. The
connection is terminated.
System action
If ICSF fails fails during connection processing at a
The attempt to access Db2 is rejected, and the
remote Db2 server, the connection attempt fails, and
the failure is reported to the application with SQLCODE
-30082. The connection is terminated.
If ICSF fails at a remote Db2 server during one of the
following actions: Modify the user ID that was provided by the remote
system or user to contain no more than eight
• Processing of an encrypted DRDA request
characters, and try the remote request again.
• Generation of an encrypted DRDA reply
the attempt to access the Db2 server fails, and the Problem determination
failure is reported to the local Db2 server. A DSNL032I
message might have been written to the console.
Refer to the description of the message for more
information.
If ICSF fails at the Db2 requester during one of the
following actions:
• Processing of an encrypted DRDA reply
• Generation of an encrypted DRDA request period of time that spans the failure.
the attempt to access the distributed resource fails, • Dynamic dump, taken to SYS1.DUMPxx data set, by
and the failure is reported to the local Db2 server. A Db2 (04E and 04F abends).
DSNL031I message might have been written to the • Listing of SYS1.LOGREC data set, obtained by
console. Refer to the description of the message for executing IFCEREP1.
more information.
Related information

00D30114 Possible causes for this error include:
• A user ID only (no password required) security
Explanation mechanism is not allowed because the TCPALVER
value has been changed to a value that requires a
Authentication of a remote user was rejected by Db2
password.
because change of password security mechanism is
not allowed when Db2 extended security support has • A user ID and password security mechanism is
been disabled. not allowed because the TCPALVER value has been
changed to a value that requires security credentials
Db2 extended security support is determined by the to be properly encrypted.
EXTSEC subsystem parameter, and the value of the
parameter has been changed online to disable the • A change of password security mechanism is not
support. allowed because the TCPALVER value has been
changed to a value that requires security credentials
The change of password security mechanism will to be properly encrypted.
remain restricted until Db2 extended security support
• DES-based encrypted security mechanisms are not
is enabled.
allowed because the TCPALVER value has been
changed to a value that requires a more secure form
System action of encryption.
The attempt to access Db2 is rejected, and the The security mechanism will remain restricted unless
connection is terminated. the Db2 TCP/IP already verified rules are modified to
accommodate the security mechanism.
System action
Enable Db2 extended security support, and try the
remote request again. The remote attempt to access Db2 is rejected, and the
report the problem. For information about identifying Change the TCPALVER subsystem parameter to a
and reporting the problem, see Collecting diagnostic value that supports the security mechanism, and try
data (Collecting data). the remote request again. Or, modify the security
mechanism to meet the security requirement that
is defined by the TCPALVER subsystem parameter
• Console output from the system on which the job setting, and try the remote request again.
Db2 (04E and 04F abends). If you suspect an error in Db2, you might need to
Related reference Collect the following diagnostic items:
EXTENDED SECURITY field (EXTSEC subsystem
parameter) (Db2 Installation and Migration) • Console output from the system on which the job
Related information
00D30115 Db2 (04E and 04F abends).
Authentication of a remote user was rejected by Db2. Related reference

The TCPALVER (TCP/IP Already Verified) subsystem TCP/IP ALREADY VERIFIED field (TCPALVER
parameter has been changed, and the security subsystem parameter) (Db2 Installation and
mechanism that was provided is no longer allowed. Migration)

Related information 00D31010
Explanation
00D30116
An internal logic error occurred while a DCRM
functional service was being invoked.
Explanation
DSNLCnnn identifies that a DCRM Conversation
Authentication of a remote user was rejected by Db2.
manager CSECT detected a logic error. Refer to the
The TCPALVER (TCP/IP Already Verified) subsystem
dump title for the specific CSECT name.
parameter has been set to SERVER_ENCRYPT and
the user ID and password authentication that was
provided is not allowed because the password could System action
not be evaluated to be a RACF PassTicket.
This error is likely to result from the following causes: is requested at the site of the Db2 abend.
• The RACF PTKTDATA class is inactive, or the
resource (IRRPTAUTH.application.target-userid) is System programmer response
not defined to z/OS. Determine which sites the abending agent was
• The RACF PTKTDATA class is active and the resource connected to by examining the DSNL027 and
IRRPTAUTH.application.target-userid is defined to DSNL028 SYSLOG console messages at the site of the
z/OS but the user ID associated to ssnmDIST started Db2 abend. Obtain copies of the SYS1.LOGREC and
task is not permitted to use it. SYSLOG data sets from each connected site, the SVC
• The password provided is not a valid RACF dump at the site of the Db2 failure, and any related
PassTicket. dumps from each connected site. If you suspect an
System action problem, see Collecting diagnostic data (Collecting
The remote access attempt to Db2 is rejected, and the data).
Ensure that the RACF PTKTDATA class is active, or • Console output and the listing of the SYSLOG data
the resource IRRPTAUTH.application.target-userid is set from each connected site for the period of time
defined and the user ID associated to ssnmDIST spanning the failure.
started task is permitted to access this resource, and
try the remote request again. • Listings of the SYS1.LOGREC data set, obtained by
Problem determination 00D31011

data (Collecting data). An internal logic error occurred while invoking a VTAM
functional service.
DSNLVnnn identifies that a DCRM VTAM manager
• Console output from the system on which the job CSECT detected a logic error. Refer to the dump title
was run, and a listing of the SYSLOG data set for the for the specific CSECT name.
System action
Severity
0 (informational) is requested at the site of the Db2 abend.
Related reference
TCP/IP ALREADY VERIFIED field (TCPALVER Operator response
Collect the SYS1.LOGREC listing and the SVC dump.
Migration)

Determine which sites the abending agent was Notify the system programmer.
DSNL028 SYSLOG console messages at the site of the Problem determination
SYSLOG data sets from each connected site, the SVC Collect the following diagnostic items:
problem, see Collecting diagnostic data (Collecting • Listings of the SYS1.LOGREC data set, obtained by
data). executing IFCEREP1 at each connected site.
00D31013
User response
A Db2 message was received with an invalid message
Problem determination block header (MBH). The MBH is a header that
precedes all messages exchanged between two Db2
subsystems.
set from each connected site for the period of time System action
Collect the SYS1.LOGREC listing and the SVC dump.
Explanation
A VTAM functional service request failed because the System programmer response
state of the conversation was invalid for the request.
Determine which connected sites the abending agent
was connected to by examining the DSNL027 and
System action
A record is written to SYS1.LOGREC and an SVC dump Db2 abend. Obtain any related diagnostic information
is requested at the site of the Db2 abend. from each connected site and the SVC dump and
SYS1.LOGREC at the site of the Db2 failure. If you
Operator response
Collect the SYS1.LOGREC listing and the SVC dump. reporting the problem, see Collecting diagnostic data
(Collecting data).
User response
connected to by examining the DSNL027 and Notify the system programmer.
Db2 abend. Obtain any related diagnostic information Problem determination
from each connected site and the SVC dump and
SYS1.LOGREC at the site of the Db2 failure. Collect the following diagnostic items:
If you suspect an error in Db2, you might need to • Console output and the listing of the SYSLOG data
report the problem. For information about identifying set from each connected site for the period of time
and reporting the problem, see Collecting diagnostic spanning the failure.
data (Collecting data). • Listings of the SYS1.LOGREC data set, obtained by

Explanation
One or more invalid parameters were supplied while System programmer response
invoking a VTAM functional service.
A record is written to SYS1.LOGREC and an SVC dump data (Collecting data).
Collect the SYS1.LOGREC listing and the SVC dump. • Console output from the system on which the job
• Statistics Class 4 trace record for the LUWID
associated with the failing request.
DSNL028 SYSLOG console messages at the site of the 00D31019
Db2 abend. Obtain any related diagnostic information
SYS1.LOGREC at the site of the Db2 failure.
Explanation
If you suspect an error in Db2, you might need to A DDM protocol error was detected in a DDM reply
report the problem. For information about identifying received from a remote distributed database remote
and reporting the problem, see Collecting diagnostic server.
System action
User response The attempt to access the distributed resource fails,
Notify the system programmer. and the failure is reported to the local Db2.
A DSNL031I message might have been written to the
Problem determination console. Refer to the description of this message in
this book for further information.
• Console output and the listing of the SYSLOG data Operator response

00D31018 If you suspect an error in Db2, you might need to
A syntax error was detected in a DDM reply received
from a remote distributed database remote server. Problem determination
System action
The attempt to access the remote database resource was run, and a listing of the SYSLOG data set for the
fails, and the failure is reported to the application. period of time that spans the failure.
A DSNL031I message might have been written to the • Statistics Class 4 trace record for the LUWID
console. Refer to the description of this message for associated with the failing request.
further information.
00D3101A

A syntax error was detected in a DDM request received
from a remote distributed database local Db2.
The attempt to access the Db2 server fails, and the • Console output from the system on which the job
failure is reported to the local Db2. was run, and a listing of the SYSLOG data set for the
A DSNL032I message might have been written to the
console. Refer to the description of this message for • Statistics Class 4 trace record for the LUWID
further information. associated with the failing request.
.
Operator response 00D3101C
Explanation
System programmer response Db2 has detected an error while processing a
If you suspect an error in Db2, you might need to connection request from DDCS. A DB2RA connection
report the problem. For information about identifying request was received from DDCS.
data (Collecting data). System action
A DDM reply message (SYNTAXRM) is returned to the
Problem determination DRDA client.
• Console output from the system on which the job Operator response
was run, and a listing of the SYSLOG data set for the Notify the DDCS system administrator.
• Statistics Class 4 trace record for the LUWID System programmer response
This is probably not a Db2 problem. This error is
00D3101B most likely caused by an incorrect entry in the DCS
directory on DDCS. Refer to IBM Distributed Database
Explanation Connection Services Installation and Configuration
Guide for information on configuring your DDCS
A DDM protocol error was detected in a DDM request system.
received from a remote distributed database local
Db2. 00D31020

The attempt to access the Db2 server fails, and the An attempt was made to use SNA/APPC
failure is reported to the local Db2. communications to create an outbound DRDA protocol
connection. However, this DDF, as identified by the
A DSNL032I message may have been written to the corresponding resource-type of 00001000 and its Db2
console. Refer to the description of this message for subsystem ID as the corresponding resource-name,
further information. was started with an IPNAME value. This process
caused DDF to only start its TCP/IP communications
Operator response support.
System action
System programmer response Notification of the failure is returned to the application.
The conversation is not allocated.

An outbound DRDA protocol connection request was period of time that spans the failure.
determined to require SNA/ APPC communications.
This will occur when only a row in the • Listing of SYS1.LOGREC data set, obtained by
SYSIBM.LUNAMES table of the Db2 Communications executing IFCEREP1.
Database table has a LUNAME column value that 00D31023
matches to the LINKNAME column of the row in
the SYSIBM.LOCATIONS table that corresponds to
the location requested by the application. If DDF Explanation
was intended to be started with only its TCP/IP A request for a protected SNA conversation was
communications support, then a row must exist in rejected by a Db2 server because the SNA exchange
the SYSIBM.IPNAMES table with a LINKNAME column log names (XLN) process has not yet completed with
value for each row in the SYSIBM.LOCATIONS table the requesting system.
that has a distinct value for its LINKNAME column.
Otherwise, remove the IPNAME value from the BSDS
DDF record by performing an update to the BSDS DDF
System action
record using the NOIPNAME parameter of the DDF Message DSNL030I is displayed on the system
statement of DSNJU003, the Change Log Inventory console with reason code 00D31023. The SNA
utility. conversation is rejected with SNA sense code
08640001, indicating the SNA protocol for protected
00D31022
conversations was violated.
Explanation
The requested VTAM function for allocating a
The requesting system should have sent a valid SNA
conversation was not performed because the data
XLN request before starting a protected conversation.
manager returned an unavailable resource when
Contact the system programmer for the requesting
attempting to read the SYSIBM.LOCATIONS table in
system to determine why the SNA XLN process was
the communication database (CDB). The LOCATION
not completed successfully.
cannot be resolved to the remote Db2 subsystem
LUNAME.
User response
System action Notify the Db2 system programmer.
Notification of the failure is returned to the application.
The conversation is not allocated. Problem determination
Operator response
data (Collecting data). The requested VTAM function for allocating a
conversation was not performed because the location
name is not defined in the SYSIBM.LOCATIONS table
Problem determination in the communication database (CDB).
For more information, refer to the explanation of
message DSNL700I. Collect the following diagnostic System action
items:
• Definitions of the communication database (CDB) The conversation is not allocated to the specified
table space, tables, and indexes involved in the error. location.

Notify the system programmer. Notification of the failure is returned to the application.
The conversation is abnormally deallocated.
Operator response
Add the location to the SYSIBM.LOCATIONS table.
• Location used in the alias entry in
SYSIBM.SYSTABLES.
• Contents of the SYSIBM.LOCATIONS table. data (Collecting data).
00D31025
Explanation For more information, refer to the explanation of
message DSNL500I or message DSNL502I, depending
The requested VTAM function for allocating a
on the type of conversation that failed.
conversation was not performed because a mode
name could not be found in the SYSIBM.MODESELECT Collect the following diagnostic items:
table in the communication database (CDB) for the
requesting thread.
System action
Notification of the failure is returned to the application. executing IFCEREP1.
The conversation is not allocated.
00D31027
Operator response
Explanation
The requested VTAM function cannot be performed
because VTAM is abending or because the operator
System programmer response has issued a HALT NET command to terminate VTAM.
Add the mode name to be selected in the
SYSIBM.MODESELECT table for the authorization ID, System action
PLANNAME, and LUNAME of the service request that
Notification of DDF termination is reported to the
failed.
application. No remote communications are allowed.
The distributed data facility is terminated.
• AUTHORIZATION ID, PLANNAME, and LUNAME of Notify the system programmer.
the thread that is used to select the MODENAME in
the SYSIBM.MODESELECT table.
• Contents of SYSIBM.LOCATIONS and
SYSIBM.MODESELECT tables. Determine why VTAM was terminated.
00D31026 00D31029
The requested VTAM function was not performed The requested VTAM function to allocate a
because VTAM returned a nonzero return code while conversation failed. VTAM returned a nonzero return
attempting to communicate on a conversation. code while attempting to negotiate limits with a
remote location for a mode.

System action that indicates the partner's generic LU name instead
of its actual LU name. If the use of a generic LU name
Notification of the failure is returned to the application. is indicated, use the RESET GENERICLU command to
All communications to the remote location on the purge this generic LU affinity.
mode fail until the CNOS is successfully negotiated.
Operator response
• Print the contents of the SYSIBM.LUNAMES table.
System programmer response • Print the contents of the SYSIBM.LULIST table.
If you suspect an error in Db2, you might need to Related reference

report the problem. For information about identifying -RESET GENERICLU (Db2) (Db2 Commands)
and reporting the problem, see Collecting diagnostic LULIST catalog table (Db2 SQL)
data (Collecting data). LUNAMES catalog table (Db2 SQL)
Related information
Problem determination DSNL030I (Db2 Messages)
For more information, refer to the explanation of DSNL510I (Db2 Messages)
message DSNL501I.
00D3102B
period of time that spans the failure. A conversation was not allocated because the partner
LU attempted to allocate a conversation using a blank
• Listing of SYS1.LOGREC data set, obtained by mode name. Although Db2 tolerates CNOS requests
executing IFCEREP1. with a blank mode name, Db2 does not accept
00D3102A conversations with a blank mode name.

A conversation was not allocated because a VTAM Message DSNL030I is displayed on the system
LU name contained in the LUNAME column of the console with reason code 00D3102B. The
SYSIBM.LULIST table was also present in the LUNAME conversation is not allocated.
column of the SYSIBM.LUNAMES table. A given VTAM
LU name can appear in only one of these two tables. Operator response
System action
The conversation is not allocated. System programmer response
Correct the definitions at the partner LU to prevent
Operator response conversations from being allocated with a blank mode
Notify the system programmer. name.
00D3102D
Make sure each remote VTAM LU is defined in the Explanation
SYSIBM.LULIST table or the SYSIBM.LUNAMES table, The requested trusted connection was not established
but not in both tables. because the SECURITY_ OUT option in the
Verify that the condition did not occur because of the SYSIBM.IPNAMES table in the communications
unintended use of a generic LU name, which would database (CDB) is not defined correctly. If the
make Db2 aware of a partner LU name (its generic LU TRUSTED column in SYSIBM. LOCATIONS table is set
name) that is not specified in the LUNAME column of to 'Y', then the SECURITY_OUT column in the SYSIBM.
the SYSIBM.LULIST or SYSIBM.LUNAMES tables. Look IPNAMES table must be set to 'P', 'R', or 'E'.
for evidence of a DSNL510I or DSNL030I message

System action • The LUNAME column in the SYSIBM.LULIST table
in the communications database is greater than 8
Notification of the failure is returned to the application. bytes.
The requested trusted connection is not established.
• The MODENAME column in the
SYSIBM.MODESELECT or SYSIBM.LUMODES table
Operator response in the communications database is greater than 8
Notify the system programmer. bytes.
• The TPN column in the SYSIBM.LOCATIONS table
System programmer response in the communications database is greater than 64
bytes.
Set up the SYSIBM.IPNAMES table correctly. • The PORT column in the SYSIBM.LOCATIONS table
00D3102E in the communications database is greater than 32
bytes or contains leading blanks.
Explanation • The Db2 authorization ID used for outbound
authorization ID translation is greater than 8 bytes.
The remote server was not successfully connected.
• The SYSMODENAME column in the
The SYSIBM.USERNAMES table did not contain
SYSIBM.LUNAMES table in the communications
a row for trusted context system authorization
database is greater than 8 bytes.
ID translation, the TYPE column specified as 'S'
describing the system authorization ID. When the
USERNAMES column in SYSIBM.IPNAMES specifies System action
'S' requiring system authorization ID translation, the
SYSIBM.USERNAMES must contain an entry describing
The remote connection is unsuccessful.
the system authorization ID used for establishing
trusted connection.
System action Correct the column in error as indicated by the
unavailable resource message.
A resource unavailable is returned to the application.
The request is not sent to the remote site. For Db2 authorization ID translation failure, make
sure that the remote BIND OWNER option contains
Operator response an authorization ID less than or equal to 8 bytes for
normal connection.
Collect a listing of the SQL that was used to configure
Make sure the USERNAMES column in the CDB table in the error.
SYSIBM.USERNAMES has been specified correctly for
Related reference
the indicated LINKNAME for trusted connection.
LOCATIONS catalog table (Db2 SQL)
LULIST catalog table (Db2 SQL)
LUMODES catalog table (Db2 SQL)
Analyze the SYSIBM.USERNAMES table for an MODESELECT catalog table (Db2 SQL)
00D31031
00D31030
The local distributed data facility (DDF) is terminating.
A remote connection cannot be established. This
problem might be caused by one of the following
symptoms: System action
• The LINKNAME column in the SYSIBM.LOCATIONS Notification of the failure is returned to the application.
table in the communications database (CDB) is Db2 does not allow any new distributed threads while
greater than 8 bytes, or is blank. DDF is in termination or is terminated.

Operator response Related information
Contact the system to determine the cause of DDF
termination. DSNL030I (Db2 Messages)
To determine why DDF was terminated and then start
DDF. Explanation
The VTAM function request to allocate a conversation
User response failed because the thread timed-out while waiting for a
Contact your system programmer to determine why session.
DDF was terminated.
00D31032
System action
Explanation
Operator response
• The requested VTAM function failed because the Notify the system programmer.
distributed data facility (DDF) at the remote location
was terminating. System programmer response
• A remote TCP/IP client attempted to connect to The defined session limit for the mode used by
a local Db2 for z/OS data server after the TCP/IP the thread might be too small. The CONVLIMIT
listener was up, but before DDF was up on that data specified for the mode might have to be negotiated
server. with the communication administrator at the remote
subsystem.
System action
Db2 writes a SYS1.LOGREC record. If DDF terminated, Problem determination
no communication on the conversation is allowed. Refer to message DSNL510I for the limit negotiated by
VTAMCollect the following diagnostic items:
executing IFCEREP1.
Take one of the following actions, depending on the
• Listing of the contents of SYSIBM.LUMODES in the
situation that occurred:
communications database.
• If DDF at the remote location terminated, contact
the communication administrator at that location. 00D31034
• If a remote TCP/IP client attempted to connect to

a local Db2 for z/OS data server after the TCP/IP Explanation
listener was up, but before DDF was up on that The maximum number of remote connections, which
data server, no action is needed. This situation is is set by subsystem parameter CONDBAT, was
indicated by the following events: reached, and the connection was rejected. The remote
1. Message DSNL519I is issued to indicate that the requester was not allowed to connect to Db2.
TCP/IP listener is up.
2. Message DSNL030I with reason code 00D31032 System action
is issued to indicate that the TCP/IP client is The requester is not connected to Db2.
attempting to connect to the Db2 for z/OS server.
3. Message DSNL004I is issued to indicate that DDF Operator response
is up and ready to accept connections.

System programmer response system, or evidence of an abend should be visible
in SYS1.LOGREC information around the time that
The maximum number of connections that can this reason code was returned back to the requester
concurrently exist is defined by the CONDBAT system application. The internal error that caused the
subsystem parameter. When the current number of server system abend must be corrected.
connections reaches the CONDBAT limit, additional
connections to Db2 are not allowed. Use a trace of
IFCID 0001 for DDF global statistics to determine if Problem determination
the limit should be increased. Collect the following diagnostic items:
Problem determination set from each connected site for the period of time
Collect the following diagnostic items: spanning the failure.
• DDF global statistics: Use field QDSTQCRT to • Listings of the SYS1.LOGREC data set, obtained by
determine the number of requests that failed executing IFCEREP1 at each connected site.
because of the CONDBAT limit. 00D31036
Related reference
MAX REMOTE CONNECTED field (CONDBAT Explanation
The LINKNAME column of the SYSIBM.LOCATIONS
Migration)
table was invalid. Since LINKNAME is a foreign key of
the SYSIBM.LUNAMES table, the LINKNAME column
00D31035
must specify one of the values provided in the
LUNAME column of the SYSIBM.LUNAMES table. This
Explanation error should not occur.
The requested distributed function failed. The
database access agent was aborted at the remote System action
location. Notification of the failure is returned to the
requester system application however the failure is
really due to an unexpected failure at the remote
server system. This error is an internal error at the
remote server system. Evidence of the failure should Operator response
be visible as an abend in the remote server system's
Collect the SYS1.LOGREC, and the SVC dump.
SYS1.LOGREC information, or, you might find the
failure recorded in a dump.
System action Obtain copies of the SYS1.LOGREC and SYSLOG data
sets from the Db2 site with the inconsistently defined
Db2 writes a SYS1.LOGREC record and requests
communications database (CDB).
an SVC dump at the remote Db2 site. Db2 server
system recovery returns this reason code back to the If you suspect an error in Db2, you might need to
requester system. report the problem. For information about identifying

User response
System programmer response Notify the system programmer.
Obtain copies of the SYS1.LOGREC and SYSLOG data

sets or similar data from each connected site, the SVC
dump at the site of the Db2 failure, and any related Collect the following diagnostic items:
data). A dump should be present at the server

• Listings of the SYS1.LOGREC data set, obtained by – You might have intended to list all the sysplex's
executing IFCEREP1 at each connected site. LU names in the SYSIBM.LULIST table, but you did
not include one or more LU names.
00D31037
– You listed a subset of the LU names in
SYSIBM.LULIST but none of the LU names you
Explanation listed are currently available. Please note that
The connection to the remote server failed. The it can take up to 3 minutes for LU availability
SYSIBM.USERNAMES table did not contain an information to be updated following START DDF
outbound row and did not specify the remote at the remote site.
authorization ID for the primary Db2 authorization ID. – The location name sent to a remote site does not
When the USERNAMES column in SYSIBM.LUNAMES match the location name recorded in the BSDS at
or SYSIBM.IPNAMES is specified as 'O' or 'B', outbound that remote site.
name translation is in use. The SYSIBM.USERNAMES
– The local SYSIBM.LULIST table is incorrectly
table must contain entries that describe the remote
defined for the remote location.
authorization IDs that are used for each Db2
authorization ID that communicates with the LU or the A DSNL030I message might have been written to the
TCP/IP address. console.

A response is sent to the application to indicate that A record is written to SYS1.LOGREC and the
the resource is unavailable. The request is not sent to conversation is not allocated.
the remote site.
Operator response
Operator response
Notify the communications database administrator.
The CDB tables and Db2 BSDS parameters must
Make sure the USERNAMES column in correctly associate the LOCATION names with their
SYSIBM.LUNAMES or SYSIBM.IPNAMES is specified corresponding LUNAME names.
correctly for the indicated LUNAME or IPADDR. If
The cause of this error is usually one of the following
you intend to use remote authorization IDs that
problems:
SYSIBM.USERNAMES table has rows that specify the • The BSDS at the remote site does not have
remote authorization ID to be used for each possible the correct LOCATION or LUNAME value, which
Db2 authorization ID. These rows must specify 'O' in causes the remote DBMS to respond to the
the TYPE column of the SYSIBM.USERNAMES table. wrong LOCATION name when receiving distributed
database requests.
Problem determination • The SYSIBM.LOCATIONS table at the local Db2
system has an incorrect value in the LINKNAME or
Analyze the SYSIBM.USERNAMES table for an LOCATION column for the failing LOCATION, which
incorrect or missing entry. causes the request to be sent to the wrong remote
00D31038 DBMS.
• The SYSIBM.LULIST table at the local Db2 system
Explanation has an incorrect value in the LUNAME column for the
failing LOCATION, which causes the request to be
A conversation was not allocated for one of these sent to the wrong remote DBMS.
reasons:
• Not all LU names in the requesting Db2 sysplex are
• The requesting LU is part of a Db2 sysplex. When one defined in the SYSIBM.LULIST table at the remote
or more LU names within a Db2 sysplex appear in site.
the SYSIBM.LULIST table at the remote site, all LU • Not all LU names in the requesting Db2 sysplex are
names within the sysplex must be identified in the defined in the SYSIBM.LULIST table at the server
SYSIBM.LULIST table at the remote site. Db2 subsystem. The remote LU is not allowed access
to the server subsystem.

In general, when the requester is a member of a remote authorization ID, password, or both
sysplex, each member of the requesting sysplex contained more than eight characters.
should be defined in SYSIBM.LULIST of the server
subsystem. However, there may be causes where
or SYSIBM.IPNAMES is specified as 'O' or 'B', outbound
an LU of a remote sysplex is not defined in
name translation is in use. The SYSIBM.USERNAMES
SYSIBM.LULIST of the local subsystem to prevent
table must contain entries that describe the remote
the remote LU from being a candidate member when
authorization IDs and passwords that are used for
accessing the remote sysplex. This is known as
each Db2 authorization ID that communicates with the
"member specific routing". If the remote sysplex LU
LU or the TCP/IP address.
attempts to access the local subsystem, this reason
code will be returned if the remote LU is not defined
in the local SYSIBM.LULIST table and is also not System action
defined in SYSIBM.LUNAMES. Remote requesting
The connection to the remote system is not allocated.
sysplex members can be defined in SYSIBM.LULIST,
or, when member specific routing requirements to
the remote sysplex member are needed, the remote Operator response
sysplex LU can be defined in SYSIBM.LUNAMES Notify the system programmer.
for inbound purposes from the remote sysplex
LU that contain the appropriate inbound security
characteristics. System programmer response
• The local Db2 system contains a SYSIBM.LULIST row On the requesting system, make sure the USERNAMES
for a remote system that is not a member of a Data column in SYSIBM.LUNAMES or SYSIBM.IPNAMES
Sharing group. SYSIBM.LULIST rows CANNOT be is specified correctly for the indicated LUNAME or
defined for remote non Data Sharing server systems. IPADDR. If you intend to use remote authorization IDs
Remove the SYSIBM.LULIST row for the remote that differ from the Db2 authorization IDs, verify that
systems. the SYSIBM.USERNAMES table has rows that specify
the remote authorization ID that is to be used for
Problem determination each possible Db2 authorization ID. Each authorization
ID must contain eight or fewer characters. If the
• Determine the LUNAME and LOCATION name of remote connection communicates with the LU and
the Db2 system that attempted to start a VTAM you intend to use remote passwords, verify that the
conversation. SYSIBM.USERNAMES table has rows that specify the
• Print the contents of the SYSIBM.LOCATIONS table remote password that is to be used for each possible
at that site. Db2 authorization ID. Each password must contain
eight or fewer characters. These rows must specify 'O'
• Print the contents of the SYSIBM.LULIST table at in the TYPE column of the SYSIBM.USERNAMES table.
both the local site and the remote site.
• Determine the LUNAME and LOCATION name of the
remote DBMS involved in the failure from the BSDS
at the remote site. Determine the LUNAME or IPADDR and find the
• Issue the -DISPLAY LOCATION command to authorization ID, password, or both for the failing
determine which LUNAMEs and LOCATIONs were remote system. Collect the following diagnostic items:
active at the time of failure. • Listing of the contents of the SYSIBM.IPNAMES and
00D31039 SYSIBM.LUNAMES tables at the local Db2 subsystem
and the remote Db2 subsystem.
• Listing of the contents of the SYSIBM.USERNAMES
Explanation
table at the local Db2 subsystem and the remote
The allocation of a connection to the remote system Db2 subsystem.
failed for one of the following reasons:
00D3103A
• The SYSIBM.USERNAMES table at the requesting
site did not contain an outbound row and did not
Explanation
specify the remote authorization ID to be used for
this Db2 authorization ID. Database access agent allocation failed because the
• The SYSIBM.USERNAMES table at the requesting RACROUTE REQUEST=EXTRACT macro failed to locate
site contained an outbound row, but the specified a user profile for the Db2 primary authorization ID
obtained from the SYSIBM.USERNAMES table. When

the ENCRYPTPSWDS column in SYSIBM.LUNAMES reclaiming process will reduce system throughput,
specifies 'Y', the requesting Db2 system must since the reclaimed conversation will have to service
be able to extract the encrypted password (via multiple SQL statements.
RACROUTE REQUEST=EXTRACT) and send this
00D3103C
encrypted password to the responding Db2 system for
validation.
Explanation
System action An attempt was made to allocate an SNA (LU 6.2)
The reason code is returned to the application. conversation, but the authentication request failed
because the specified remote partner LUNAME will
not allow authentication based on a user ID alone.
Operator response The remote partner LUNAME is configured to require
Notify the communications database administrator. authentication using a user ID and corresponding
password.
System programmer response A password must be provided throughDb2 application

logic or throughDb2 Communications Database (CDB)
Make sure the new authorization ID column in definitions. Alternately, the partner LUNAME can be
SYSIBM.USERNAMES has been specified correctly for configured to allow authentication based on user ID
the indicated LUNAME. If you intend to use encrypted alone. For example, specify LU 6.2 SECURITY=SAME or
passwords, the new authorization ID must be defined Already-Verified.
to your MVS security subsystem.
System action
The attempt to allocate an LU6.2 conversation fails,
• Analyze the SYSIBM.USERNAMES table for an and the error is reported to theDb2 application that
incorrect or missing entry. requested access to the distributed resource.
• Verify that the names given in the NEWAUTHID
column are defined to your MVS security subsystem System programmer response
properly.
If the remote LUNAME configuration can be changed,
00D3103B change it to allow Already Verified (Security=Same)
authentication, which does not require a password. If
Explanation the target LUNAME is a Db2 for z/OS system, support
is declared by specifying SECACPT=ALREADYV on
An attempt to allocate an LU6.2 conversation failed theDb2 VTAM APPL statement.
because the conversation limits for the requested
partner LU and VTAM MODE have been reached. If remote LUNAME configuration changes are not
appropriate, or if a higher level of security is required,
then the local Db2 for z/OS system must honor the
System action requirements of the remote LUNAME and provide a
This reason code is generated internally when an password. It might be possible to make application
attempt is made to allocate an LU6.2 conversation changes to provide a password. If application changes
and conversation limits have been reached for the are not possible, CDB changes will be required.
requested partner LU and VTAM MODE. In this If the local application is DRDA related, and if it
situation, the requesting Db2 system will attempt to is executing an explicit SQL CONNECT statement to
reuse one of the existing LU6.2 conversations that connect to the remote system, consider changing
have already been allocated to the agent in question. the application to provide a password on the SQL
The allocate process will be retried using the existing CONNECT statement as follows:
conversation.
CONNECT TO server USING userid USING password
System programmer response In the following circumstances, Db2 Communications

Database tables must be changed to provide a
If you increase the LU6.2 conversation limits for the
password:
indicated partner LU and VTAM MODE, it will not
be necessary for Db2 to reclaim conversations in • The local application cannot be modified to provide a
order to allocate additional LU6.2 conversations. The password on its SQL CONNECT statement.

• The application is performing an implicit SQL be recorded in NetView (if the NetView product is
connection. (The application refers to a three-part available) to describe the security failure.
name, or alias, that resolves to the remote system.)
If the remote site is not a Db2 subsystem, obtain any
In these cases, change the SYSIBM.LUNAMES rows, diagnostic information about the security failure at
which are associated to the partner LUNAME, to the remote site.
specify 'P' (password) or 'R' (RACF PassTicket) for
If you suspect the authorization ID or password is not
SECURITY_OUT. If you specify 'P', you must also:
correct, the Db2 CDB on the local Db2 system should
• Add a SYSIBM.USERNAMES "outbound" row that be examined to validate the following items:
specifies the user ID and its associated password.
• If the remote site requires both an authorization
• Specify a SYSIBM.LUNAMES USERNAMES column ID and a password on LU6.ALLOCATE requests (i.e.,
value of 'O' or 'B' to satisfy referential constraints the remote site does not accept already-verified
on the SYSIBM.USERNAMES table. ALLOCATE requests), the USERNAMES column of
the SYSIBM.LUNAMES table at the local Db2 system
User response must specify either 'O' or 'B'.
• If the USERNAMES column of the SYSIBM.LUNAMES
table at the local Db2 system specifies 'O' or
'B', the SYSIBM.USERNAMES table will be used to
Problem determination determine the authorization ID and password sent
Collect the following diagnostic items: on the LU6.ALLOCATE request.
• The VTAM APPL definition for the remote Db2 If you intend to translate the authorization IDs,
system. ensure that the NEWAUTHID column of the
SYSIBM.USERNAMES table contains the correct
• The contents of the SYSIBM.LUNAMES table. authorization ID to be used at the remote site.
Related concepts • If the remote site is a Db2 system, the
Ways to control access to Db2 subsystems ENCRYPTPSWDS value in the SYSIBM.LUNAMES
(Introduction to Db2 for z/OS) table must exactly match the ENCRYPTPSWDS
Related reference column of the SYSIBM.LUNAMES table at the remote
CONNECT (Db2 SQL) site.
LUNAMES catalog table (Db2 SQL) • If the remote site is not a Db2 system, the
ENCRYPTPSWDS value in the SYSIBM.LUNAMES
00D3103D table must be set to 'N'.
• If you are transmitting passwords to the remote
Explanation site, the password transmitted by the local Db2
system must exactly match the value expected by
An attempt to allocate a VTAM LU6.2 conversation the remote site.
with a remote site failed because the request did not
contain the proper security information. 1. For encrypted passwords, the password sent
to the remote Db2 subsystem is obtained by
extracting the RACF password of the user
System action identified by the NEWAUTHID column in the
The attempt to access the remote database resource SYSIBM.USERNAMES table. This user's RACF
failed and the failure is reported to the application. password must exactly match the password at
the remote site.
System programmer response 2. If password encryption is not used, the password
will be taken from the PASSWORD column of
This error is usually caused by transmitting an invalid the SYSIBM.USERNAMES table. This value must
authorization ID or password in a request to the exactly match the password at the remote site.
remote site. However, this is not always the case, so
it is important to review the diagnostic information at
the remote site to determine the cause of the failure.
User response
• If the remote site is a Db2 subsystem, refer to the Notify the communications database administrator.
DSNL030I message at the remote site for the cause
of the security failure. Additionally, an ALERT will

Collect the following diagnostic items: Db2 starts a new conversation to the remote site
that does not use two-phase commit. Db2 does not
• Listing of the contents of the SYSIBM.IPNAMES and
attempt to use two-phase commit with this remote
SYSIBM.LUNAMES tables at the local Db2 subsystem
site until DDF is restarted.
• Listing of the contents of the SYSIBM.USERNAMES
table at the local Db2 subsystem and the remote
Db2 subsystem. This reason code is produced when the LU at the
• Console output from the system on which the job remote site supports two-phase commit, but the TPN
was run, and a listing of the SYSLOG data set for the at the remote LU does not support two-phase commit.
period of time that spans the failure. This is a normal situation, so no system programmer
action is required.
00D3103E
00D31040
Explanation
Explanation
The requested VTAM function to allocate a
conversation was not performed because the VTAM The requested VTAM function failed before the
MODE specified a conversation limit of zero. The database access agent has failed. This is an internal
conversation limits must be set to a value greater than error.
zero before a conversation can be allocated.
System action
System action Db2 writes a SYS1.LOGREC record and requests an
The conversation is not allocated. SVC dump at the failed Db2 site.


If you have placed entries in the SYSIBM.LUMODES Determine which sites the abending agent was
table, make sure CONVLIMIT column has a nonzero connected to by examining the DSNL027 and
value. If you are allowing the session limits to be DSNL028 SYSLOG console messages at the site of the
chosen by VTAM, make sure the DSESLIM values on Db2 failure. Obtain any related diagnostic information
the VTAM APPL and mode entries are nonzero. from each connected site and the SVC dump and
• Determine the LUNAME and MODE name of the Db2 report the problem. For information about identifying
system that attempted to start a VTAM conversation. and reporting the problem, see Collecting diagnostic
• Print the contents of the SYSIBM.LUMODES table. data (Collecting data).
• Determine the session limits defined on the VTAM Collect the following diagnostic items:
APPL statement and the VTAM MODE entry.
00D3103F set from each connected site for the period of time
Explanation • Listings of the SYS1.LOGREC data set, obtained by
An attempt to allocate a VTAM LU6.2 conversation with
a remote site failed because the server at the remote 00D31041
LU does not support the SNA two-phase commit
process.

The requested VTAM function to allocate a Notify the system programmer.
conversation was not performed because the
SYSIBM.USERNAMES table at the responding site System programmer response
did not contain a row whose authorization ID
column matches the Db2 authorization ID received Obtain copies of the SYS1.LOGREC and SYSLOG data
from the requesting Db2 system. When the sets from each connected site, the SVC dump at the
USERNAMES column in SYSIBM.LUNAMES specifies site of the Db2 failure, and any related dumps from
'I' or 'B', inbound name translation is in effect. each connected site.
The SYSIBM.USERNAMES table must contain entries
describing the local Db2 authorization ID to be used
for each Db2 authorization ID sent by the requesting
Db2 system.

A record is written to SYS1.LOGREC and the
conversation is not allocated.
Operator response
Notify the system programmer. • Listings of the SYS1.LOGREC data set, obtained by
00D31043
SYSIBM.LUNAMES has been specified correctly for Explanation
the indicated LUNAME. If you intend to use local
authorization IDs that differ from the remote Db2 The requested VTAM function failed. The connection
authorization ID, verify that the SYSIBM.USERNAMES from the remote location was interrupted. This is an
table has rows that correctly specify the local internal error.
authorization ID to be used for each possible remote
authorization ID. These rows must specify 'I' in the System action
TYPE column of the SYSIBM.USERNAMES table.
is requested at the failed Db2 site.
Determine the LUNAME and authorization ID for the Operator response
failing VTAMCollect the following diagnostic items:
and the remote Db2 subsystem. System programmer response
00D31042 Obtain copies of the SYS1.LOGREC and SYSLOG data
sets from each connected site, the SVC dump at the
site of the Db2 failure, and any related dumps from
Explanation each connected site.
The requested VTAM function failed. The connection to If you suspect an error in Db2, you might need to
the remote location was interrupted. This is an internal report the problem. For information about identifying
error. and reporting the problem, see Collecting diagnostic
System action
A record is written to SYS1.LOGREC and an SVC dump Problem determination
is requested at the failed Db2 site. Collect the following diagnostic items:

• Console output and the listing of the SYSLOG data • Listing of the contents of the SYSIBM.USERNAMES
set from each connected site for the period of time table at the local Db2 subsystem and the remote
spanning the failure. Db2 subsystem.
• Listings of the SYS1.LOGREC data set, obtained by 00D31045
A remote subsystem has attempted to allocate a VTAM
Explanation LU6.2 conversation, but the request was rejected
A remote subsystem has attempted to allocate because the request did not contain the proper
a VTAM LU6.2 conversation, but the request was security information. The FMH5 received from the
rejected because the request did not contain the remote subsystem did not contain the security subfield
proper security information. The FMH5 received from that supplies the USERID, or the USERID was not 1 to
the remote subsystem did not contain any security 8 bytes in length.
subfields. This represents SECURITY=NONE in the
LU6.2 architecture, which is not supported by Db2. System action
The attempt to access the remote database resource
System action fails and the failure is reported to the application.
The attempt to access the remote database resource A DSNL032I message may have been written to the
fails and the failure is reported to the application. console. Refer to the description of this message for
A DSNL030I message may have been written to the further information.
console.
Operator response
Operator response Notify the system programmer.
System programmer response Verify that the remote subsystem is configured to send
Verify that the remote subsystem is configured to send valid security subfields.
valid security subfields. If you suspect an error in Db2, you might need to
If the remote subsystem is Db2, make sure the VTAM report the problem. For information about identifying
APPL definition does not specify SECACPT=NONE, and reporting the problem, see Collecting diagnostic
which is the default for the VTAM APPL definition. data (Collecting data).
SECACPT=NONE will cause VTAM to remove the
security subfields from the FMH5. User response
If you suspect an error in Db2, you might need to Notify the communications database administrator.
User response • Console output from the system on which the job
Notify the communications database administrator. was run, and a listing of the SYSLOG data set for the
Collect the following diagnostic items: and the remote Db2 subsystem.
• Console output from the system on which the job • Statistics Class 4 trace record for the LUWID
was run, and a listing of the SYSLOG data set for the associated with the failing request.
period of time that spans the failure. • Listing of the contents of the SYSIBM.USERNAMES
• Listing of the contents of the SYSIBM.IPNAMES and table at the local Db2 subsystem and the remote
SYSIBM.LUNAMES tables at the local Db2 subsystem Db2 subsystem.

00D31046 table to 'A' for the remote LU in question. Also
the Db2 VTAM APPL definition should specify
SECACPT=ALREADYV.
Explanation
2. If you would like Db2 to continue to reject requests
A remote subsystem has attempted to allocate a VTAM of this kind, the remote LU must be configured
LU6.2 conversation, but the request was rejected to send requests that contain both a USERID and
because the request did not contain the proper PASSWORD (SECURITY=PGM in SNA LU6.2 terms).
security information. The FMH5 received from the
remote subsystem indicated SECURITY=SAME (also If the remote LU is Db2, the SECURITY_OUT
known as Already-Verified) and the subsystem in column in the SYSIBM.LUNAMES table must specify
question was not authorized to send requests with either 'R' or 'P' in the row associated with the local
SECURITY=SAME. Db2 subsystem.
The attempt to access the remote database resource data (Collecting data).
fails and the failure is reported to the application.
A DSNL030I message may have been written to the User response
console.
Operator response
The request was rejected because the SECURITY_IN period of time that spans the failure.
column of the SYSIBM.LUNAMES table contained a 'V'
in the row associated with the remote system. The • Listing of the contents of the SYSIBM.IPNAMES and
value 'V' indicates that the remote system must send SYSIBM.LUNAMES tables at the local Db2 subsystem
both a USERID and a PASSWORD, which corresponds and the remote Db2 subsystem.
to SECURITY_PGM in the SNA LU6.2 architecture. • Listing of the contents of the SYSIBM.USERNAMES
Users should also be aware that in the absence of a table at the local Db2 subsystem and the remote
SYSIBM.LUNAMES row that specifically identifies the Db2 subsystem.
remote LU, a "default" SYSIBM.LUNAMES row (blank
LUNAME) may be used, if defined, if the inbound 00D31047
connection is via DRDA protocols. This "default"
row may not reflect the needed inbound security Explanation
characteristics in which case a SYSIBM.LUNAMES row
A remote subsystem has attempted to allocate a VTAM
can be defined that explicitly identifies the remote LU.
LU6.2 conversation, but the request was rejected
If the remote LU is a member of a remote sysplex because the request did not contain the proper
and the local system requires access to the remote security information. The FMH5 received from the
sysplex, then members of the remote sysplex to be remote subsystem did not contain the security subfield
accessed must be defined in the local SYSIBM.LULIST that supplies the PASSWORD, or the PASSWORD was
table. In this case, the remote sysplex LU can be not 1 to 8 bytes in length.
defined in the local SYSIBM.LULIST table although a
SYSIBM.LUNAMES definition, default row or explicit
System action
definition, is appropriate in cases where it is
undesirable to define the remote LU in SYSIBM.LULIST The attempt to access the remote database resource
(for example when you don't want the remote LU to fails and the failure is reported to the application.
be a candidate member when outbound accessing the
A DSNL032I message may have been written to the
remote SYSPLEX location).
console. Refer to the description of this message for
This problem can be corrected in two ways: further information.
1. If you would like Db2 to accept requests that
are marked with SECURITY=SAME, change the
SECURITY_IN value in the SYSIBM.LUNAMES

Operator response opposed to the ACBNAME keyword, on the Db2 VTAM
APPL statement for the requester site. A server's
Notify the system programmer. SYSIBM.LUNAMES table should contain an entry for
the requester's LUNAME.
System programmer response In the absence of a SYSIBM.LUNAMES row that
Verify that the remote subsystem is configured to send specifically identifies the remote LU, a default
valid security subfields. SYSIBM.LUNAMES row (blank LUNAME) might be
used, if defined, in the case where the inbound
If you suspect an error in Db2, you might need to connection is through DRDA protocols. This default
report the problem. For information about identifying row might not reflect the needed inbound security
and reporting the problem, see Collecting diagnostic characteristics, in which case a SYSIBM.LUNAMES row
data (Collecting data). can be defined that explicitly identifies the remote LU.
If the remote LU is a member of a remote
User response sysplex and the local system requires access to
Notify the communications database administrator. the remote sysplex, then members of the remote
sysplex to be accessed must be defined in the
local SYSIBM.LULIST table. In this case, the remote
sysplex LU can be defined in the local SYSIBM.LULIST
Collect the following diagnostic items: table. A SYSIBM.LUNAMES definition, default row or
explicit definition, is appropriate in cases where it is
undesirable to define the remote LU in SYSIBM.LULIST,
such as when you do not want the remote LU to be
a candidate member when outbound accessing the
• Listing of the contents of the SYSIBM.IPNAMES and remote SYSPLEX location.
and the remote Db2 subsystem. Verify that the condition did not occur because of the
unintended use of a generic LU name, which would
• Listing of the contents of the SYSIBM.USERNAMES make Db2 aware of a partner LU name (its generic LU
table at the local Db2 subsystem and the remote name) that is not specified in the LUNAME column of
Db2 subsystem. the SYSIBM.LULIST or SYSIBM.LUNAMES tables. Look
• Statistics Class 4 trace record for the LUWID for evidence of a DSNL510I or DSNL030I message
associated with the failing request. that indicates the partner's generic LU name instead
of its actual LU name. If the use of a generic LU name
00D31048 is indicated, use the RESET GENERICLU command to
purge this generic LU affinity.
Explanation
The requested VTAM function for allocating a Problem determination
conversation at the Db2 server was not performed Collect the following diagnostic items:
because the requester's LUNAME is not defined in
the SYSIBM.LUNAMES table of the communication • Listing of the contents of the SYSIBM.IPNAMES and
database (CDB) at the server. SYSIBM.LUNAMES tables at the local Db2 subsystem
-RESET GENERICLU (Db2) (Db2 Commands)
The conversation is not allocated to the specified LULIST catalog table (Db2 SQL)
location. LUNAMES catalog table (Db2 SQL)
Related information
Operator response DSNL030I (Db2 Messages)
00D31049
Add the requester's LUNAME to the SYSIBM.LUNAMES
table at the server. If the remote LU is Db2,
the requester's LUNAME is the label name, as

A request using application-directed access starting at period of time that spans the failure.
site 'A' referenced an object at site 'B' that is stored at
site 'A' 00D3104B

The application statement was not processed. An SNA conversation was rejected by a Db2 server
because the SNA FMH5 specified SNA persistent
verification. Db2 does not support the SNA persistent
User response verification option.
Recode the application to remove the alias reference
at the remote server that resolves to an object stored System action
at the local Db2. Objects stored at the local site must
be referenced using a local name. Message DSNL030I is displayed on the system
console with reason code 00D3104B. The SNA
conversation is rejected with SNA sense code
Problem determination X'080F6051 ', indicating the SNA security parameters
If necessary, consult with the database administrators in the FMH5 were not acceptable.
at the local site and the remote server location.
Inspect the remote SYSIBM.SYSTABLES catalog table System programmer response
to determine the object at this location being
referenced in a circular manner. The SECACPT keyword on the VTAM APPL
statement tells VTAM whether Db2 supports
00D3104A persistent verification. Because Db2 does not support
persistent verification, the SECACPT=PERSISTV and
Explanation SECACPT=AVPV options cannot be used on the Db2
VTAM APPL statement.
A remote server issued an SNA BACKOUT, which
was not sent as a reply to an SNA PREPARE or
REQUEST_COMMIT. This indicates the server backed User response
out the current unit of work without waiting for the SQL Notify the Db2 system programmer.
application to either commit or roll back.
System action
fails and the failure is reported to the application. Db2 • Console output from the system on which the job
terminates the SNA conversation to the remote server was run, and a listing of the SYSLOG data set for the
and forces the application to roll back. period of time that spans the failure.
00D3104C
Db2 never issues an unsolicited SNA BACKOUT. Non- Explanation
Db2 servers can send an SNA BACKOUT indication The SNA Exchange Log Names (XLN) process failed
when resources required to complete the unit of work because of a log name mismatch between Db2 and a
are not available. For example, a deadlock might cause remote LU in the network.
the non-Db2 server to send an SNA BACKOUT. Contact
the system programmer for the remote system to
determine why the unit of work had to be aborted. System action
The attempt to allocate an SNA two-phase commit
User response conversation fails with reason code 00D3104C.
Message DSNL410 is displayed on the system console
Notify the Db2 systems programmer. to describe the error.

The log name recorded in the Db2 log does not match Collect the following diagnostic items:
the log name currently in use at the remote LU. There
are indoubt units of work that need to be resolved
at this Db2 system. The log name required to resolve
the indoubt units of work is displayed in the DSNL410
message. 00D3104E
If a non-Db2 partner was started with the wrong log, it
might be possible to restart the non-Db2 partner with Explanation
the desired log name. This should cause the indoubt
An SNA Exchange Log Names (XLN) protocol violation
units of work to be resolved automatically.
was detected when attempting to establish a
If the partner cannot be restarted with the desired log connection to a remote site.
name, the -RECOVER INDOUBT command can be used
to resolve the indoubt units of work. Once the indoubt
System action
units of work are resolved, Db2 will accept an SNA XLN
with a new partner log name. The attempt to allocate an SNA conversation is
rejected with reason code 00D3104E. Message
User response DSNL421E is written to the system console and IFCID
0213 is produced to describe the protocol violation.
Contact the Db2 systems programmer.
Contact the system programmer for the remote site.
Collect the following diagnostic items: The invalid XLN message is recorded in the IFCID
0213 trace record. The system logic error that causes
the invalid XLN message must be corrected at the
remote site.
00D3104D User response
Explanation
The local Db2 system does not support connectivity to Problem determination
the Db2 release currently running at the remote Db2
site. Collect the following diagnostic items:
System action was run, and a listing of the SYSLOG data set for the
The attempt to allocate an SNA conversation is
rejected with reason code 00D3104D. 00D3104F

Db2 distributed database connections can only be A connection to a remote location was lost during a
established between compatible Db2 releases. For previous communication operation.
example, Version 3 can connect to Db2 2.3, but not
to Db2 2.2.
System action
In order to establish connectivity, the down-level Db2
If the communication failure occurred during a commit
system must be migrated to a supported release of
or abort operation, the SQL application might not be
Db2.
aware that a failure occurred. Messages associated
with the failure were written to the system console at
User response the time of failure. Additionally, alerts were reported to
NetView at the time of failure.

User response of a SECCHK command, this is a DRDA protocol error
committed by the DRDA AR implementation at the
Reestablish the connection to the remote site and remote client.
reissue the SQL statement.
For TCP/IP connections, this is a DRDA protocol error
committed by the DRDA AR implementation at the
Problem determination remote client.
was run, and a listing of the SYSLOG data set for the If you suspect an error in Db2, you might need to
period of time that spans the failure. report the problem. For information about identifying
. and reporting the problem, see Collecting diagnostic
data (Collecting data). Collect the following diagnostic
00D31050 items:
Db2 expected to receive security information for the period of time that spans the failure.
remote client but a valid DRDA SECCHK command • Dynamic dump, taken to SYS1.DUMPxx data set, by
was not received for a connection request from a Db2 (04E and 04F abends).
DRDA application requester (AR). The DRDA SECCHK
command is only valid with a DRDA security manager
executing IFCEREP1.
level greater than or equal to 5.
00D31052
This can be the case if one of the following occurs:
• The DRDA AR requested a DRDA security manager Explanation
less than level 5 for an SNA connection where
the APPL command for Db2 was specified with the An application caused recursive access to a remote
SECACPT=NONE option. location, followed by access to another remote
• The DRDA SECCHK command did not contain the location, which is not permitted.
required security information. For example, an application at location LOC1 might
• The DRDA AR requested a DRDA security manager have connected to location LOC2 and accessed a table
less than level 5 for a TCP/IP connection. using an alias that resolves back to LOC1. There was a
subsequent remote access from LOC1 to LOCn, which
caused the error.
System action
The attempt to access the local database resource System action
fails, the failure is reported to the SQL application, and
the conversation is terminated. The attempt to access the remote location fails. The
SQL application receives a -904 SQLCODE.
For SNA connections, if SECACPT=NONE and the
DRDA AR does not support DRDA security manager Correct the application program so that it does not
level 5, contact the Db2 security administrator to cause recursive access to a location followed by
change the SECACPT option to ALREADYV or CONV remote access from that location. The application
to allow for security information in the VTAM FMH-5 might have used table aliases, three-part table names,
in the form of userid or userid/password fields. If stored procedures, user-defined functions, or triggers
SECACPT=NONE is not changed, then Db2 cannot to cause the condition.
accept connection requests from this remote client.
For SNA connections, If SECACPT=ALREADYV or Problem determination
CONV, then even though userid or userid/password Collect the following diagnostic items:
fields in the FMH-5 are received and validated, Db2
must evaluate a DRDA SECCHK command if it is sent. • Console output from the system on which the job
If the DRDA AR requests this level of security but was run, and a listing of the SYSLOG data set for the
does not provide the correct information in the form period of time that spans the failure.

• Definitions of views and tables involved in the error. User response
• Location used in the alias entry in You might need to increase the value of the MAXDBAT
SYSIBM.SYSTABLES. subsystem parameter or investigate the cause of the
• Contents of the SYSIBM.LOCATIONS table. slowdown of request processing.
MAX REMOTE ACTIVE field (MAXDBAT
Explanation subsystem parameter) (Db2 Installation and
Migration)
The number of queued connection requests has CONN QUEUE MAX DEPTH field (MAXCONQN
reached the value of the MAXCONQN subsystem subsystem parameter) (Db2 Installation and
parameter. The TCP/IP socket was closed for the Migration)
longest-waiting connection in the connection request
queue. 00D31055

The client is no longer connected to Db2. The remote location defined in the
SYSIBM.LOCATIONS table could not be accessed
User response because the TCP/IP interface to DDF is not available.
This reason code might indicate that a slowdown in

the processing of requests occurred or is occurring. System action
Because the value of the MAXDBAT subsystem The request to connect to a remote site fails. The SQL
parameter has also been reached, you might need application receives a -904 SQLCODE.
to increase the value of the MAXDBAT subsystem
parameter or determine the cause of the slowdown of
the request processing. Operator response
Related tasks Notify the system programmer.
Setting limits for the queuing of client
connections waiting for database access System programmer response
threads (Db2 Performance)
One of the following actions should be taken:
Related reference
CONN QUEUE MAX DEPTH field (MAXCONQN • If the remote site is not supposed to be using
subsystem parameter) (Db2 Installation and TCP/IP, add a row to SYSIBM.LUNAMES defining the
Migration) LUNAME used by the remote location.
MAX REMOTE ACTIVE field (MAXDBAT • If the remote site is correctly defined in the CDB,
subsystem parameter) (Db2 Installation and examine the messages written to the console during
Migration) -START DDF processing. Those messages describe
any errors that would prevent DDF from using
00D31054 TCP/IP.
• Determine if Db2 is started in restricted access
Explanation mode. If so, retry the request when Db2 has been
started in full access mode.
Db2 detected a connection request that waited
longer than the value of the MAXCONQW subsystem
parameter. The TCP/IP socket of a long-waiting User response
connection request was closed. Notify the system programmer.

The client is no longer connected to Db2. Collect the following diagnostic items:

. System programmer response
00D31056 Insert a row in SYSIBM.LUNAMES or
SYSIBM.IPNAMES that matches the LINKNAME
Explanation specified in SYSIBM.LOCATIONS.
The PORT column of the SYSIBM.LOCATIONS table

could not be converted to a TCP/IP port number by
User response
the getservbyname TCP/IP socket call. Notify the system programmer.
00D31058
System action
The request to connect to a remote site fails. The SQL Explanation
application receives a -904 SQLCODE, and message
DSNL514, DSNL517, or DSNL518 is written to the The IPADDR column of the SYSIBM.IPNAMES table
console describing the error. could not be converted to an IP address by the
gethostbyname TCP/IP socket call.
Operator response
System action
The request to connect to a remote site fails. The SQL
application receives a -904 SQLCODE, and message
System programmer response DSNL513, DSNL517, or DSNL518 is written to the
Use the information in the DSNL514, DSNL517, or console describing the error.
DSNL518 message to resolve the error.
Operator response
User response Notify the system programmer.
Problem determination Use the information in the DSNL513, DSNL517, or
Collect the following diagnostic items: DSNL518 message to resolve the error.

period of time that spans the failure. Notify the system programmer.
.
00D31057
Db2 was able to find the row in SYSIBM.LOCATIONS was run, and a listing of the SYSLOG data set for the
for the LOCATION specified in the SQL request. period of time that spans the failure.
However, the LINKNAME column value specified .
in LOCATIONS did not match any row in
SYSIBM.LUNAMES or SYSIBM.IPNAMES. 00D31059

The request to connect to a remote site fails. The SQL An attempt to allocate a conversation to the remote
application receives a -904 SQLCODE. site failed because Db2 was unable to obtain a
RACF PassTicket. The user specified an 'R' in the
SECURITY_OUT column of the SYSIBM.IPNAMES or
Operator response SYSIBM.LUNAMES communications database (CDB)
Notify the system programmer. tables for the partner site. As a result, Db2 invokes
RACF to extract a PassTicket for the partner site.

However, RACF could not provide a PassTicket, and the System action
attempt failed.
The connection request is not processed. The
application is placed in the unconnected and
System action connectable state.
failed, and the failure is reported to the application. User response
Change the application to eliminate its use of SQL
System programmer response CONNECT with a user ID and password, or remove the
The error usually occurs due to incorrect or missing RACF PassTicket requirement in SYSIBM.LUNAMES or
RACF definitions. To avoid this error, specify the SYSIBM.IPNAMES.
proper RACF definitions to provide for the PassTicket. 00D3105B
Alternatively, you may avoid the use of PassTickets
by changing the SECURITY_OUT column of the
SYSIBM.IPNAMES and/or SYSIBM.LUNAMES CDB Explanation
table for the partner site. An SQL CONNECT statement was issued with a
user ID and password to connect to a location that
User response requires RACF encrypted password authorization. The
connection cannot be made.
The entry in SYSIBM.LUNAMES for the location that
is specified on the SQL CONNECT statement indicates
Problem determination that a connection request must contain a user ID and
Collect the following diagnostic items: RACF encrypted password .
• Listing of the results produced by the SQL
statements. System action
• Listing of the contents of the SYSIBM.IPNAMES and The connection request is not processed. The
SYSIBM.LUNAMES tables at the local Db2 subsystem application is placed in the unconnected and
and the remote Db2 subsystem. connectable state.
• Contents of the SYSIBM.LOCATIONS table.
Related tasks
User response
Enabling Db2 to send RACF PassTickets Change the application to eliminate its use of
(Managing Security) SQL CONNECT with a user ID and password, or
Managing outbound connection requests remove the RACF encrypted password requirement in
(Managing Security) SYSIBM.LUNAMES.
Related reference 00D3105C
IPNAMES catalog table (Db2 SQL)
LUNAMES catalog table (Db2 SQL) Explanation
00D3105A During a TCP/IP synchronous read operation from
a Db2 for z/OS server to a distributed client, a
DRDA exception occurred because the timer for the
Explanation
synchronous read operation expired, and the Db2
An SQL CONNECT statement was issued with a user server did not receive the remaining data from the
ID and password to connect to a location that requires client.
RACF PassTicket authorization. The connection cannot
be made. System action
The entry in SYSIBM.LUNAMES or SYSIBM.IPNAMES The connection between the distributed client and the
for the location that is specified on the SQL CONNECT Db2 server fails. Db2 generates message DSNL032I
statement indicates that a connection request must with reason code 00D3105C.
contain a user ID and RACF PassTicket.

System programmer response • The name of the user's workstation.
The timer for the TCP/IP synchronous receive • The ID of the user.
operation might have expired for any of the following • The name of the application.
reasons: • The statement type for the previously executed
• Slowdowns occurred at the distributed client. statement: dynamic or static.
• Network resource problems occurred between the • The statement identifier for the previously
client and the Db2 server. executed statement, if available. The statement
identifier can be used to identify the
• Problems occurred in the system on which the Db2
particular SQL statement. For static statements,
server was running, or in the Db2 server.
the statement identifier correlates to the
• The timeout value for TCP/IP synchronous read STMT_ID column in the SYSIBM.SYSPACKSTMT
operations is too low. To remedy this situation, set table. For dynamic statements, the statement
subsystem parameter IDTHTOIN to a higher value. identifier correlates to the STMT_ID column in
the DSN_STATEMENT_CACHE_TABLE table. That
Problem determination statement might not have contributed to the current
failure.
• The name of the role that is associated with the
thread.
data (Collecting data). Collect the following diagnostic • The correlation token that can be used to correlate
items: work at the remote system with work performed
at the Db2 subsystem. The correlation token, if
• Console output from the system on which the job available, is enclosed in '<' and '>' characters, and
was run, and a listing of the SYSLOG data set for the contains three components, separated by periods:
– A 3 to 39 character IP address.
• Output from a statistics class 4 trace for IFCID 0192.
– A 1 to 8 character port address.
Related reference
– A 12 character unique identifier.
IDLE THREAD TIMEOUT field (IDTHTOIN
Migration) Programmer response
Related information Consider using CLIENT_CORR_TOKEN for tracking
DSNL032I (Db2 Messages) individual connections. CLIENT_CORR_TOKEN is a
unique value that allows you to correlate your business
00D3105D processes across the enterprise. CLIENT_APPLNAME
should not be used to identify individual connections.
Explanation
The number of unique application names has Problem determination
exceeded 6000 unique values. For more information, refer to thread-information in
the DSNL030I message.
Db2 does not collect remote application statistics for CURRENT CLIENT_APPLNAME (Db2 SQL)
any new application name until DDF is restarted. CURRENT CLIENT_CORR_TOKEN (Db2 SQL)
Client info properties support by the IBM
Administrator response Data Server Driver for JDBC and SQLJ (Db2
Application Programming for Java)
Notify the application programmer. The application
Related information
can be identified from the thread-information in the
DSNL030I message. DSNL030I (Db2 Messages)
thread-information is a colon-delimited list that 00D3105E

contains the following segments. An asterisk (*) in any
segment indicates that the information is not available.
• The primary authorization ID that is associated with
the thread.

Explanation processes across the enterprise. CLIENT_USERID
should not be used to identify individual connections.
The number of unique user IDs has exceeded 6000
unique values.
System action For more information, refer to thread-information in
the DSNL030I message.
Db2 does not collect remote application statistics for
any new user IDs until DDF is restarted. Related reference
CURRENT CLIENT_USERID (Db2 SQL)
Administrator response CURRENT CLIENT_CORR_TOKEN (Db2 SQL)
Client info properties support by the IBM
Notify the application programmer. The application Data Server Driver for JDBC and SQLJ (Db2
can be identified from the thread-information in the Application Programming for Java)
DSNL030I message.
Related information
thread-information is a colon-delimited list that DSNL030I (Db2 Messages)
contains the following segments. An asterisk (*) in any
segment indicates that the information is not available. 00D31100
• The primary authorization ID that is associated with
the thread. Explanation
• The name of the user's workstation. The data communications function service was
• The ID of the user. invoked with a parameter list that contained one or
more invalid parameters. This is an internal error.
• The name of the application.
• The statement type for the previously executed
statement: dynamic or static. System action
• The statement identifier for the previously A record is written to SYS1.LOGREC and an SVC dump
executed statement, if available. The statement is requested at the site of the Db2 abend.
identifier can be used to identify the
particular SQL statement. For static statements, Operator response
the statement identifier correlates to the
STMT_ID column in the SYSIBM.SYSPACKSTMT Notify the system programmer.
table. For dynamic statements, the statement
identifier correlates to the STMT_ID column in System programmer response
the DSN_STATEMENT_CACHE_TABLE table. That
statement might not have contributed to the current Determine which sites the abending agent was
failure. connected to by examining the DSNL027 and
• The name of the role that is associated with the Db2 abend. Obtain any related diagnostic information
thread. from each connected site and the SVC dump and
• The correlation token that can be used to correlate STS1.LOGREC at the site of a Db2 abend.
work at the remote system with work performed
at the Db2 subsystem. The correlation token, if
available, is enclosed in '<' and '>' characters, and
contains three components, separated by periods:
– A 3 to 39 character IP address.
– A 1 to 8 character port address. Problem determination
– A 12 character unique identifier. Collect the following diagnostic items:
Programmer response set from each connected site for the period of time
Consider using CLIENT_CORR_TOKEN for tracking spanning the failure.
individual connections. CLIENT_CORR_TOKEN is a • Listings of the SYS1.LOGREC data set, obtained by
unique value that allows you to correlate your business executing IFCEREP1 at each connected site.
00D31101

A data communications functional service was invoked Determine which sites the abending agent was
with the cursor table marked invalid. This is an internal connected to by examining the DSNL027 and
error. DSNL028 SYSLOG console messages at the site of the
System action SYSLOG data sets or similar data from each connected
site, the SVC dump at the site of the Db2 failure, and
A record is written to SYS1.LOGREC and an SVC dump any related dumps from each connected site.
Notify the system programmer. data (Collecting data).

connected to by examining the DSNL027 and • Console output and the listing of the SYSLOG data
DSNL028 SYSLOG console messages at the site of the set from each connected site for the period of time
Db2 abend. Obtain any related diagnostic information spanning the failure.
00D31103
A data communications functional service received an
Problem determination invalid logical-unit-of-work ID (LUWID) or no LUWID.
This is an internal error.
• Console output and the listing of the SYSLOG data System action
spanning the failure. A record is written to SYS1.LOGREC and an SVC dump
• Listings of the SYS1.LOGREC data set, obtained by is requested at the site of the Db2 abend.
Operator response
00D31102
Explanation
A data communications functional service
encountered an inconsistency in the requesting thread Determine which sites the abending agent was
control block structure. This is an internal error. connected to by examining the DSNL027 and
System action Db2 abend. Obtain any related diagnostic information
A record is written to SYS1.LOGREC and an SVC dump SYS1.LOGREC as the site of the Db2 failure.

Explanation Db2 abend. Obtain copies of the SYS1.LOGREC and
A data communications functional service cannot find SYSLOG data sets from each connected site, the SVC
a distributed processing block for the primary thread. dump at the site of the Db2 failure, and any related
This is an internal error. dumps from each connected site.
A record is written to SYS1.LOGREC and an SVC dump data (Collecting data).
Operator response
System programmer response spanning the failure.
Determine which sites the abending agent was • Listings of the SYS1.LOGREC data set, obtained by
connected to by examining the DSNL027 and executing IFCEREP1 at each connected site.
Db2 abend. Obtain any related diagnostic information 00D31106
SYS1.LOGREC at the site of the Db2 failure. Explanation
If you suspect an error in Db2, you might need to A data communications functional service detected an
report the problem. For information about identifying invalid message sequence. One or more rows of data
and reporting the problem, see Collecting diagnostic might have been lost. This is an internal error.
System action
set from each connected site for the period of time Operator response
00D31105
Explanation DSNL028 SYSLOG console messages at the site of the
A data communications functional service detected Db2 abend. Obtain copies of the SYS1.LOGREC and
an invalid or incorrect buffer size on a send message SYSLOG data sets from each connected site, the SVC
operation. This is an internal error. dump at the site of the Db2 failure, and any related
A record is written to SYS1.LOGREC and an SVC dump and reporting the problem, see Collecting diagnostic
is requested at the site of the Db2 abend. data (Collecting data).

Collect the following diagnostic items: A record is written to SYS1.LOGREC and an SVC dump
spanning the failure. Operator response
• Listings of the SYS1.LOGREC data set, obtained by Notify the system programmer.
Explanation connected to by examining the DSNL027 and
A data communications functional service was invoked
incorrectly (protocol violation) to wait for a message.


00D31109
Explanation
report the problem. For information about identifying A data communications functional service was invoked
and reporting the problem, see Collecting diagnostic incorrectly (protocol violation) to send a message. This
data (Collecting data). is an internal error.

A data communications functional service was invoked
incorrectly (protocol violation) to receive a message.

and reporting the problem, see Collecting diagnostic While a message was being sent or received by the
data (Collecting data). data communications resource manager, an internal
error was detected in Db2. Register 4 contains a
reason code that provides additional information about
Problem determination this error. This is an internal error.
00D3110A Notify the system programmer.

A data communications functional service detected an Determine which sites the abending agent was
invalid message sequence. One or more rows of data connected to by examining the DSNL027 and
might have been lost. This is an internal error. DSNL028 SYSLOG console messages at the site of the
System action from each connected site and the SVC dump and
Determine which sites the abending agent was • Console output and the listing of the SYSLOG data
connected to by examining the DSNL027 and set from each connected site for the period of time
DSNL028 SYSLOG console messages at the site of the spanning the failure.
SYSLOG data sets from each connected site, the SVC • Listings of the SYS1.LOGREC data set, obtained by
dump at the site of the Db2 failure, and any related executing IFCEREP1 at each connected site.
dumps from each connected site. 00D31110
data (Collecting data). Instrumentation facility component (IFC) has passed
a nonzero return code to the data communications
resource manager. This is an internal error.
00D3110B

Db2 abend. Obtain any related diagnostic information executing IFCEREP1 at each connected site.
from each connected site and the SVC dump and 00D31112
and reporting the problem, see Collecting diagnostic The data communications resource manager cannot
data (Collecting data). find the LUWID for the remote thread in the database
thread control blocks. This is an internal error.
System action
• Console output and the listing of the SYSLOG data is requested at the site of the Db2 abend.
Operator response
executing IFCEREP1 at each connected site. Notify the system programmer.
00D31111
The instrumentation facility component (IFC) passed DSNL028 SYSLOG console messages at the site of the
a nonzero return code to the data communications Db2 abend. Obtain any related diagnostic information
resource manager. This is an internal error. from each connected site and the SVC dump and
Operator response
Db2 abend. Obtain any related diagnostic information executing IFCEREP1 at each connected site.
from each connected site and the SVC dump and 00D31113
and reporting the problem, see Collecting diagnostic The data communications resource manager received
data (Collecting data). an invalid set of control block pointers. This is an
internal error.
System action

Db2 abend. Obtain copies of the SYS1.LOGREC and spanning the failure.
SYSLOG data sets or similar data from each connected • Listings of the SYS1.LOGREC data set, obtained by
site, the SVC dump at the site of the Db2 failure, and executing IFCEREP1 at each connected site.
any related dumps from each connected site.
00D31115
data (Collecting data). The data communications resource manager attempt
to enqueue a request for a database access thread
Problem determination failed. This is an internal error.

System action


A data communications resource manager(DCCM) Determine which sites the abending agent was
block for a deallocated conversation which belongs to connected to by examining the DSNL027 and
a database access thread cannot be found. This is an DSNL028 SYSLOG console messages at the site of the
internal error. Db2 abend. Obtain copies of the SYS1.LOGREC and
SYSLOG data sets or similar data from each connected
System action any related dumps from each connected site.
A record is written to SYS1.LOGREC and an SVC dump If you suspect an error in Db2, you might need to
is requested at the site of the Db2 abend. report the problem. For information about identifying

Db2 abend. Obtain copies of the SYS1.LOGREC and • Listings of the SYS1.LOGREC data set, obtained by
SYSLOG data sets or similar data from each connected executing IFCEREP1 at each connected site.
any related dumps from each connected site. 00D31116


The data communications resource manager received Determine which sites the abending agent was
an invalid DC message number. This is an internal connected to by examining the DSNL027 and
error. DSNL028 SYSLOG console messages at the site of the

Db2 abend. Obtain copies of the SYS1.LOGREC and spanning the failure.
00D31118
A message-processing routine returned to the
data communications resource manager without the
Problem determination requested response. This is an internal error.
System action

The data communications resource manager received Determine which sites the abending agent was
a request with an invalid response type. This is an connected to by examining the DSNL027 and
internal error. DSNL028 SYSLOG console messages at the site of the

• Console output and the listing of the SYSLOG data • A VTAM VARY NET, INACTIVE or HALT NET command
set from each connected site for the period of time was issued which interrupted a Db2 conversation.
spanning the failure. • A Db2 internal logic error occurred.
executing IFCEREP1 at each connected site. System action
00D31119 A record is written to SYS1.LOGREC and an SVC dump
may be requested at the site of the Db2 abend.
Explanation
The data communications resource manager Operator response
processed a request with an unassigned or Notify the system programmer.
disconnected message class. This is an internal error.

System action
If the abend appears to have been caused by a Db2
A record is written to SYS1.LOGREC and an SVC dump logic error, determine which sites the abending agent
is requested at the site of the Db2 abend. was connected to by examining the DSNL027 and
Operator response Db2 abend. Obtain copies of the SYS1.LOGREC and
Notify the system programmer. site as well as any related dumps from each connected
site.
Determine which sites the abending agent was report the problem. For information about identifying
connected to by examining the DSNL027 and and reporting the problem, see Collecting diagnostic
DSNL028 SYSLOG console messages at the site of the data (Collecting data).
SYSLOG data sets from each connected site, the SVC Problem determination
dumps from each connected site. Collect the following diagnostic items:
If you suspect an error in Db2, you might need to • Console output and the listing of the SYSLOG data
report the problem. For information about identifying set from each connected site for the period of time
and reporting the problem, see Collecting diagnostic spanning the failure.
data (Collecting data). • Listings of the SYS1.LOGREC data set, obtained by
Problem determination 00D3111B
• Console output and the listing of the SYSLOG data Explanation
set from each connected site for the period of time The data communications resource manager cannot
spanning the failure. find the remote location for the requesting thread in
• Listings of the SYS1.LOGREC data set, obtained by the control blocks. This is an internal error.
00D3111A System action
Explanation is requested at the site of the Db2 abend.
The data communications resource manager received
an unexpected communications error when processing Operator response
a request. This can occur for any of the following Notify the system programmer.
reasons:
• A VTAM session failure caused the premature
termination of a Db2 conversation.

Determine which sites the abending agent was Notify the system programmer.
DSNL028 SYSLOG console messages at the site of the Problem determination
SYSLOG data sets or similar data from each connected Collect the following diagnostic items:
If you suspect an error in Db2, you might need to spanning the failure.
report the problem. For information about identifying • Listings of the SYS1.LOGREC data set, obtained by
and reporting the problem, see Collecting diagnostic executing IFCEREP1 at each connected site.
00D3111E
Explanation
A database access thread (DBAT) meets the
• Console output and the listing of the SYSLOG data requirement for becoming inactive but the limit
set from each connected site for the period of time specified by the value of the MAXTYPE1 subsystem
spanning the failure. parameter has already been reached.
System action
00D3111C A record is written to SYS1.LOGREC, DSNL027I and
DSNL028I messages have are written to SYSLOG, and
Explanation the thread is terminated.
An internal logic error occurred while invoking a
TCP/IP functional service. Operator response
DSNLInnn identifies that a DCRM TCP/IP manager Collect the SYS1.LOGREC listing and the SVC dump.
CSECT detected a logic error. Refer to the dump title
for the specific CSECT name. System programmer response
The DBAT meets the requirements for becoming
System action inactive because a nonzero value has been specified
A record is written to SYS1.LOGREC and an SVC dump for the MAXTYPE1 subsystem parameter. However,
is requested at the site of the Db2 abend. because the number of inactive DBATs has already
reached the MAXTYPE1 limit, the DBAT is terminated
with this reason code. To correct the condition,
Operator response
increase the value of the MAXTYPE1 subsystem
Collect the SYS1.LOGREC listing and the SVC dump. parameter to allow additional inactive DBATs, or set
the value to zero.
User response
connected to by examining the DSNL027 and Notify the system programmer.
Db2 abend. Obtain copies of the SYS1.LOGREC and Problem determination
dump at the site of the Db2 failure, and any related Collect the following diagnostic items:
dumps from each connected site. If you suspect an • Console output and the listing of the SYSLOG data
error in Db2, you might need to report the problem. set from each connected site for the period of time
For information about identifying and reporting the spanning the failure.
data). • Listings of the SYS1.LOGREC data set, obtained by

Related tasks intent to fetch all n rows before attempting to
Managing Db2 threads (Db2 Performance) execute other SQL statements. The application is not
Related reference abiding by its intent and is executing other SQL, or
committing, prior to fetching all n rows. In this case,
DDF THREADS field (CMTSTAT subsystem
the cursor definition can be changed to reduce the
value of n, or the application logic can be modified
MAX INACTIVE DBATS field (MAXTYPE1 to fetch all n rows or to close the cursor before
subsystem parameter) (Db2 Installation and executing the statement that caused the in-transit
Migration) data to be buffered.
Related information
• The number of extra blocks returned can be
DSNL027I (Db2 Messages) controlled by Db2 installation parameters. The
DSNL028I (Db2 Messages) maximum number of extra blocks requested by a
Db2 requester system is determined by the "Extra
00D3111F Blocks Req" option of the DSNTIP5 Db2 installation
panel. This value can be reduced which prevents the
Explanation server system from returning more blocks than the
Db2 requester system can buffer.
The maximum amount of buffered query data has
been exceeded. Rather than return one block of Similarly, the server system may also provide a
query data, the DRDA server system elected to return method to regulate the maximum number of extra
multiple extra blocks. Instead of fetching all rows in blocks that it will return to a requester. In this case,
all the extra blocks, the requesting application either this number can also be reduced. For Db2 for z/OS
executed an SQL statement that is not related to systems, this is determined by the EXTRA BLOCKS
the query or executed a commit while a held cursor SRV field on the DSNTIP5 Db2 installation panel.
was still open. Db2 buffers the extra in-transit blocks, Examine the columns in the cursor select list. The
however Db2 was not able to buffer the entire set of columns in the select list can impact the amount of
extra blocks and thus truncated the result set. The storage required by the DRDA server for processing
application then resumed fetching and attempted to query data. The cursor definition can be changed
fetch data beyond the point of truncation. to reduce the number of columns in the select list,
This SQLCODE can also be returned when the DRDA or the columns in the select list can be changed to
server system calculates the maximum amount of have a smaller declared length in the table. Both can
storage required for processing query data, and finds reduce the required storage at the DRDA server to
the requested storage exceeds the system limit. handle the query data.
For information about block fetching result sets, see
System action Enabling block fetch for distributed applications (Db2
Performance).
The SQL statement fails.
User response
Operator response
Determine the failing application program and
consider the following resolutions: • Listing of the results produced by the SQL
statements.
• The cursor definition may cause the server to return
extra blocks. In this case, the cursor definition can • Source listing of the failing application program.
be changed to reduce the number of rows, thus extra 00D31200
blocks, being returned by the server.
Db2 for z/OS systems return extra blocks for cursors Explanation
defined with the OPTIMIZER FOR n rows clause
and will return only enough extra blocks in order Db2 thread inactivation processing failed to inactivate
to return n rows. When a cursor is defined with a database access thread (DBAT) because the DBAT's
OPTIMIZER FOR n rows, either in the application or unit of recovery state was marked as "inflight".
in a stored procedure, this indicates an application This processing occurs only when Db2 is configured

with DDF Inactive Threads support (when the "DDF PORTs for Db2. If not using dynamic VIPA to bind
THREADS" field is set to "INACTIVE" in the DSNTIPR to Db2 PORT, remove the BIND ipaddr option on the
installation panel). This error is an internal error. PORT statement in the PROFILE.TCPIP data set used
to reserve the PORT numbers for Db2. After fixing the
System action TCP/IP PORT configuration statements, start DDF.
A record is written to SYS1.LOGREC and an SVC dump 00D31202

Explanation
System programmer response Db2 has detected an inconsistent change in the TCP/IP
Determine which sites the abending agent was PORT configuration parameter for the RSYNC PORT. A
connected to by examining the DSNL027 and BIND ipaddr specified on the RSYNC PORT statement
DSNL028 SYSLOG console messages at the site of the was changed in the PROFILE.TCPIP data set since DDF
Db2 abend. Obtain copies of the SYS1.LOGREC and was started.
dump at the site of the Db2 failure, and any related System action
DDF is abnormally terminated. This change can cause
error in Db2, see the information about identifying and
outages because of invalid sysplex routing information
reporting problems in Searching the IBM Support site
or commit resynchronization failures due to invalid IP
for known problems and solutions (Diagnosing Db2
problems). addresses being returned to requesters.

Verify the BIND ipaddr specified on the RSYNC PORT
number in the TCP/IP PORT statement and start DDF.
set from each connected site for the period of time 00D31203
• Listings of the SYS1.LOGREC data set, obtained by Explanation
executing IFCEREP1 at each connected site. A conversation was not allocated for one of these
00D31201 reasons:
• The LINKNAME was present in the SYSIBM.IPLIST
Explanation table, but not in the SYSIBM.IPNAMES table.
• The IP Address contained in the IPADDR column
Db2 has detected an inconsistency in the TCP/IP
of SYSIBM.IPLIST table was also present in the
PORT configuration parameter between the DRDA and
IPADDR column of SYSIBM.IPNAMES table. A given
RSYNC ports. A BIND ipaddr was specified on the
IP Address can appear in only one of these two
DRDA PORT statement in the PROFILE.TCPIP data
tables.
set but the BIND ipaddr was not specified on the
RSYNC PORT statement in the PROFILE.TCPIP data
set. When using dynamic virtual IP addresses (VIPA), System action
Db2 requires both the DRDA PORT and RSYNC PORT to
A record is written to SYS1.LOGREC and the
be configured to use a VIPA.
conversation is not allocated.
System action
Operator response
DDF is abnormally terminated.

If using dynamic VIPA to bind to a Db2 PORT
Make sure the LINKNAME in SYSIBM.IPLIST table is
number, verify that a VIPA is defined for both the
also defined in SYSIBM.IPNAMES table. Make sure
DRDA PORT number and RSYNC PORT number by
the IP Address is specified in the IPADDR column of
specifying the BIND ipaddr on the PORT statement
SYSIBM.IPLIST table and a blank value is specified in
in the PROFILE.TCPIP data set used to reserve the
the IPADDR column of SYSIBM.IPNAMES table.

Explanation
• Print the contents of the SYSIBM.IPNAMES table.
A secure connection could not be established using
• Print the contents of the SYSIBM.IPLIST table.
z/OS Application Transparent-Transport Layer Security
00D31204 (AT-TLS). The reason that this code was issued
depends on whether the connection attempt was
inbound or outbound:
Explanation
Inbound connections
An outbound TCP/IP connection requires the use
Db2 has detected an invalid use of a secure port.
of IPv6 addressing but TCP/IP is not configured to
A non-secure TCP/IP connection is attempting to
support IPv6 addressing.
access Db2 using a secure port without an AT-TLS
policy established for the connection.
System action Outbound connections
Notification of the failure is returned to the application. Db2 cannot establish a secure connection with the
remote location.
System action
The Communications Database (CDB) registration of
the remote partner indicates that an IPv6 address is The system action depends on whether the connection
to be used. That is, the location name being accessed was inbound or outbound:
by the application SQL refers to a SYSIBM.LOCATIONS Inbound connections
row. The SYSIBM.LOCATIONS row contains a The attempted connection request is terminated.
LINKNAME that refers to a SYSIBM.IPNAMES row. If no instance of message DSNL030I has been
The SYSIBM.IPNAMES row contains an IPADDR value written to the system console in the preceding
that indicates the use of IPv6 addressing, either by five minutes, message DSNL030I is written to the
explicitly specifying an IPv6 address or by referring to system console.
a domain name that resolves to an IPv6 address.
Outbound connections
You must choose of the following actions: The request to connect to the remote site fails. The
• Configure TCP/IP to support IPv6 addressing. SQL application receives SQLCODE -904.
• Make configuration changes to refer to only IPv4
addresses. System programmer response
To configure TCP/IP to support IPv6 addressing, you z/OS AT-TLS transparently performs transport layer
must first ensure that TCP/IP is configured to use security (TLS) on behalf of Db2 by invoking the z/OS
a dual-mode IPv4 and IPv6 stack - the BPXPRMxx System Secure Socket Layer (SSL) in the TCP transport
PARMLIB member must be modified to allow TCP/IP layer. AT-TLS uses a policy-based configuration, and
to behave as a dual-mode stack. Other TCP/IP the Policy Agent application is required to define AT-
configuration changes are also required to define the TLS rules and actions to the TCP/IP stack for TCP
IPv6 address. You can verify that IPv6 addressing is connections.
correctly defined for Db2 purposes if the Db2 Display 1. Use the reports generated by the z/OS UNIX
DDF command report, issued after DDF is started, pasearch and TCP/IP NETSTAT TTLS commands to
provides an IPv6 address. verify that an AT-TLS policy exists and has been
If TCP/IP cannot be configured to support IPv6 defined for the appropriate port.
addressing, you can only refer to IPv4 addresses. If Inbound connections
the IPADDR column, of the SYSIBM.IPNAMES CDB The secure port that Db2 uses for accepting
table, specifies an IPv6 address, you must change the secure TCP/IP connections.
IPADDR column to refer to an IPv4 address. If the
Outbound connections
IPADDR column specifies a domain name that resolves
The remote port that Db2 uses to establish
to an IPv6 address by the Domain Name Server (DNS),
a secure TCP/IP connection with the remote
you must modify the DNS to resolve the domain name
location.
to an IPv4 address.
2. Ensure that AT-TLS is enabled for this connection.
Make the appropriate changes and rerun the
application.

Verify that the correct port number has been specified Analyze the statistics class 4 trace record identified
for the connection to the target server. For a secure by the IFCID sequence number enumerated in the
connection, the port number should be the target DSNL032I message. For the Db2 system generating
Db2 SECURE PORT, in which case an AT-TLS policy is the DSNL032I message, collect the following
required. diagnostic items:
If you want to access Db2 without a secure • Statistics Class 4 trace record for the LUWID
connection, specify the Db2 DRDA PORT. associated with the failing request.
Related reference In addition, identify all connected systems
AT-TLS policy statements (z/OS participating in the processing of the remote request.
Communications Server: IP Configuration This includes the requester system to which the
Reference) application is connected and the data server which is
The z/OS UNIX pasearch command: Display the target of the remote request. This may also include
policies (z/OS Communications Server: IP intermediate server systems. For each system that is a
System Administrator's Commands) Db2 system, collect the following diagnostic items:
Netstat TTLS/-x report (z/OS Communications • Console output and the listing of the SYSLOG data
Server: IP System Administrator's Commands) set from each connected site for the period of time
Related information spanning the failure.
DSNL030I (Db2 Messages) For non-Db2 systems, refer to the documentation
-904 specific to those products for diagnostic procedures.
If any dumps were generated on any Db2 system
participating in processing the remote request, collect
the following diagnostic items:
00D31206 executing IFCEREP1 at each connected site.
• All dumps created by this failure.
Explanation
00D31207
The MAXFILEPROC limit was exceeded and the thread
was not allowed to connect to Db2.
Explanation
System action A remote connection was not established because the
USERNAMES option in the SYSIBM.IPNAMES table in
The requester is not connected to Db2. the communications database (CDB) is not defined
correctly.
Operator response If the TRUSTED column in SYSIBM.LOCATIONS table
Notify the system programmer. is set to 'N', and the SECURITY_OUT column in
the SYSIBM.IPNAMES table is set to 'P' or 'E', the
USERNAMES column in the SYSIBM.IPNAMES table
System programmer response must be set to 'O'.
The maximum number of sockets that can be opened
concurrently is defined by the installation option System action
MAXFILEPROC. When the MAXFILEPROC limit is
exceeded, threads are not allowed to connect to Notification of the failure is returned to the application.
Db2. This message will be issued by DSNLILNR if The remote connection is not established.
Db2 is acting as the server listening on a socket
and the conversation was abnormally deallocated or Operator response
by DSNLIAAC when Db2 is acting as the requester
initiating a connection and the connection was not
allocated.
Make the appropriate changes and rerun the
application. Set up the SYSIBM.IPNAMES table correctly.

IPNAMES catalog table (Db2 SQL)
00D34401
The relational data system (RDS) passed an invalid connected to by examining the DSNL027 and
function code to the distributed RDS (DRDS). This is an DSNL028 SYSLOG console messages at the site of the
internal error. Db2 abend. Obtain copies of the SYS1.LOGREC and
System action any related dumps from each connected site. If you
A record is written to SYS1.LOGREC and an SVC dump suspect an error in Db2, you might need to report
is requested at the site of the Db2 abend. the problem. For information about identifying and
(Collecting data).
Operator response
Determine which sites the abending agent was set from each connected site for the period of time
site, the SVC dump at the site of the Db2 failure, and .
00D34405
Explanation
data (Collecting data). The data communications resource manager (DCRM)
passed an invalid LMPP message number to the
Problem determination distributed relational data system (DRDS). This is
either an internal DCRM error or an internal DRDS
Collect the following diagnostic items: error.
Explanation
The relational data system (RDS) passed the System programmer response
distributed RDS (DRDS) an invalid distributed interface
block (DIB). This is an internal RDS error. Determine which sites the abending agent was
System action Db2 abend. Obtain copies of the SYS1.LOGREC and
A record is written to SYS1.LOGREC and an SVC dump SYSLOG data sets or similar data from each connected
is requested at the site of the Db2 abend. site, the SVC dump at the site of the Db2 failure, and

Explanation
The distributed relational data system (DRDS) received
Problem determination an invalid return code from the data communications
resource manager (DCRM) on a SEND request. This is a
Collect the following diagnostic items: DCRM internal error.
Explanation
The distributed relational data system (DRDS) System programmer response
detected a message of invalid length from the
data communications resource manager (DCRM). The
message is longer than the buffer size. This is either an
internal DRDS error or an internal DCRM error.
System action site, the SVC dump at the site of the Db2 failure, and
A record is written to SYS1.LOGREC and an SVC dump any related dumps from each connected site. If you
is requested at the site of the Db2 abend. suspect an error in Db2, you might need to report
Operator response (Collecting data).
any related dumps from each connected site. 00D34408
The distributed relational data system (DRDS) received
an invalid LMPP from the data communications
resource manager (DCRM). This is either a DCRM
Problem determination internal error or a DRDS internal error.
System action

00D3440B
any related dumps from each connected site. If you Explanation
suspect an error in Db2, you might need to report The distributed relational data system (DRDS)
the problem. For information about identifying and detected an inconsistency. This is an internal error.
(Collecting data).
System action
Problem determination Db2 writes a SYS1.LOGREC record and requests an
SVC dump at the failed Db2 site.
00D34409 Obtain copies of the SYS1.LOGREC and SYSLOG data
sets or similar data from each connected site, the SVC
Explanation
The distributed relational data system (DRDS) error in Db2, you might need to report the problem.
detected an internal inconsistency. An invalid state For information about identifying and reporting the
transition occurred. This is a DRDS internal error. problem, see Collecting diagnostic data (Collecting
data).
System action
is requested at the site of the Db2 abend. Collect the following diagnostic items:
Operator response set from each connected site for the period of time
00D3440C
DSNL028 SYSLOG console messages at the site of the Explanation
Db2 abend. Obtain copies of the SYS1.LOGREC and The distributed relational data system (DRDS)
SYSLOG data sets or similar data from each connected requesting site control block must exist at this time
site, the SVC dump at the site of the Db2 failure, and but does not. This is an internal DRDS error.
any related dumps from each connected site. If you
the problem. For information about identifying and System action
reporting the problem, see Collecting diagnostic data A record is written to SYS1.LOGREC and an SVC dump
(Collecting data). is requested at the site of the Db2 abend.

00D3440E
suspect an error in Db2, you might need to report A distributed request was received, but the distributed
the problem. For information about identifying and data facility (DDF) is inactive.
(Collecting data).
System action
Problem determination The request is not processed.
Operator response
set from each connected site for the period of time Ensure that the DDF has been started.
• Listings of the SYS1.LOGREC data set, obtained by User response
Notify the system operator.
00D3440D
00D3440F
The distributed statistics and accounting control block
The distributed relational data system (DRDS)
does not exist. This is an internal distributed data
detected a message of invalid length from the
facility (DDF) error.
data communications resource manager (DCRM). The
message is smaller than the buffer size, but the return
System action code from the DCRM indicates that the message is
greater than one buffer. This is either an internal DRDS
error or an internal DCRM error.


Operator response
Db2 abend. Obtain copies of the SYS1.LOGREC and System programmer response
(Collecting data).

reporting the problem, see Collecting diagnostic data The distributed relational data system (DRDS)
(Collecting data). detected an internal inconsistency. An invalid state is
specified. This is an internal DRDS error.
System action
Operator response
00D34410
The distributed relational data system (DRDS) received DSNL028 SYSLOG console messages at the site of the
an invalid return code from the data communications Db2 abend. Obtain copies of the SYS1.LOGREC and
resource manager (DCRM) on a RECEIVE request. This SYSLOG data sets or similar data from each connected
is an internal DCRM error. site, the SVC dump at the site of the Db2 failure, and
System action suspect an error in Db2, you might need to report
A record is written to SYS1.LOGREC and an SVC dump reporting the problem, see Collecting diagnostic data
is requested at the site of the Db2 abend. (Collecting data).

SYSLOG data sets or similar data from each connected 00D34412
the problem. For information about identifying and The distributed relational data system (DRDS)
reporting the problem, see Collecting diagnostic data detected an internal inconsistency. An internal buffer
(Collecting data). offset variable contains an invalid value. This is an
internal DRDS error.
System action
Operator response
00D34411

the problem. For information about identifying and The relational data system (RDS) did not specify an
reporting the problem, see Collecting diagnostic data area for the null indicator of the data. This is an
(Collecting data). internal error.

The data header on the message received from the DSNL028 SYSLOG console messages at the site of the
responding site contains invalid information. This is an Db2 abend. Obtain copies of the SYS1.LOGREC and
internal error. SYSLOG data sets or similar data from each connected
A record is written to SYS1.LOGREC and an SVC dump the problem. For information about identifying and
is requested at the site of the Db2 abend. reporting the problem, see Collecting diagnostic data
(Collecting data).
Operator response
the problem. For information about identifying and The input host variable SQLDA format specified in the
reporting the problem, see Collecting diagnostic data RDI is not valid. This is an internal error.
(Collecting data).
System action

00D34417
suspect an error in Db2, you might need to report DRDS detected an illegal attempt to enter Continuous
the problem. For information about identifying and Block Fetch mode.
(Collecting data).
System action
Explanation
An incomplete response was received on a SYSLOG data sets or similar data from each connected
conversation when a complete response was site, the SVC dump at the site of the Db2 failure, and
expected. any related dumps from each connected site.

Determine which sites the abending agent was • Listings of the SYS1.LOGREC data set, obtained by
connected to by examining the DSNL027 and executing IFCEREP1 at each connected site.
Db2 abend. Obtain copies of the SYS1.LOGREC and 00D34418
site, the SVC dump at the site of the Db2 failure, and Explanation
The connection to the remote server failed.
If you suspect an error in Db2, you might need to The SYSIBM.USERNAMES table did not contain
report the problem. For information about identifying an outbound row and did not specify the
and reporting the problem, see Collecting diagnostic remote authorization ID for the plan owner Db2
data (Collecting data). authorization ID. When the USERNAMES column in

SYSIBM.LUNAMES is specified as 'O' or 'B', outbound suspect an error in Db2, you might need to report
name translation is in use. The SYSIBM.USERNAMES the problem. For information about identifying and
table must contain entries that describe the remote reporting the problem, see Collecting diagnostic data
authorization IDs that are used for each Db2 (Collecting data).
authorization ID that communicates with the LU.
System action
A response is sent to the application to indicate that
the resource is unavailable. The request is not sent to
the remote site.
Operator response executing IFCEREP1 at each connected site.
00D3441C

Allocation of the distributed processing services block
SYSIBM.LUNAMES is specified correctly for the
(DPSB) failed.
indicated LUNAME. If you intend to use remote
authorization IDs that differ from the Db2
authorization IDs, verify that the SYSIBM.USERNAMES System action
table has rows that specify the remote authorization
ID to be used for each possible Db2 authorization ID.
These rows must specify 'O' in the TYPE column of the
SYSIBM.USERNAMES table.
Operator response
incorrect or missing entry. System programmer response
Explanation Db2 abend. Obtain copies of the SYS1.LOGREC and
RDS has passed an invalid DESCRIBE request to DRDS. SYSLOG data sets or similar data from each connected
This is an internal error. site, the SVC dump at the site of the Db2 failure, and

SYSLOG data sets or similar data from each connected 00D3441D

The distributed relational data system (DRDS) Determine which sites the ABENDing agent was
subcomponent has determined that control structures connected to by examining the DSNL027 and
necessary for processing do not exist. This is a Db2 DSNL028 SYSLOG console messages at the site of the
internal error. Db2 ABEND. Obtain copies of the SYS1.LOGREC and
System action site, the SVC dump at the site of the Db2 failure, and
is requested at the site of the Db2 ABEND. the problem. For information about identifying and

Determine which sites the ABENDing agent was • Console output and the listing of the SYSLOG data
Db2 ABEND. Obtain copies of the SYS1.LOGREC and • Listings of the SYS1.LOGREC data set, obtained by
00D3441F
and reporting the problem, see Collecting diagnostic The distributed relational data system (DRDS)
data (Collecting data). subcomponent is in an invalid state and cannot
process the function requested. This is a Db2 internal
error.
is requested at the site of the Db2 ABEND.
Operator response
00D3441E

Determine which sites the ABENDing agent was
subcomponent has determined that the function to be
executed is not a valid function. This is a Db2 internal
Db2 ABEND. Obtain copies of the SYS1.LOGREC and
error.
(Collecting data).
Operator response

Operator response
00D34422
Explanation
subcomponent has received an unexpected return Determine which sites the ABENDing agent was
code from the Distributed Transaction Manager (DTM) connected to by examining the DSNL027 and
subcomponent during CONNECT processing. This is a DSNL028 SYSLOG console messages at the site of the
Db2 internal error. Db2 ABEND. Obtain copies of the SYS1.LOGREC and
is requested at the site of the Db2 ABEND. the problem. For information about identifying and
(Collecting data).
Operator response
Determine which sites the ABENDing agent was set from each connected site for the period of time
Db2 ABEND. Obtain copies of the SYS1.LOGREC and • Listings of the SYS1.LOGREC data set, obtained by
site, the SVC dump at the site of the Db2 failure, and 00D34424
the problem. For information about identifying and Explanation
(Collecting data). subcomponent has received an unexpected return
code from the Distributed Data Interchange Service
Problem determination (DDIS) subcomponent on an invocation to parse a
reply. This is a Db2 internal error.
Operator response
00D34423
Explanation
subcomponent has received an unexpected return Determine which sites the ABENDing agent was
code from the Distributed Data Interchange Service connected to by examining the DSNL027 and
(DDIS) subcomponent on an invocation to generate a DSNL028 SYSLOG console messages at the site of the
request. This is a Db2 internal error. Db2 ABEND. Obtain copies of the SYS1.LOGREC and

site, the SVC dump at the site of the Db2 failure, and 00D34426
Explanation
(Collecting data). subcomponent has detected an invalid date format in
the DSNHDECP module or a user-supplied application
Problem determination defaults module. This is a Db2 internal error.

System action
00D34425

subcomponent has received an unexpected return
code from the Data Communications Resource
Manager (DC) subcomponent. This is a Db2 internal
error.
A record is written to SYS1.LOGREC and an SVC dump the problem. For information about identifying and
is requested at the site of the Db2 ABEND. reporting the problem, see Collecting diagnostic data
(Collecting data).
Operator response
Determine which sites the ABENDing agent was spanning the failure.
Explanation
the problem. For information about identifying and The distributed relational data system (DRDS)
reporting the problem, see Collecting diagnostic data subcomponent has detected an invalid time format
(Collecting data). in the DSNHDECP module or the user-supplied
application defaults manual. This is a Db2 internal
Problem determination error.

System action

Notify the system programmer. Analyze the statistics class 4 trace record identified
by the IFCID sequence number enumerated in the
System programmer response DSNL032I message.
At the Db2 DRDA server system that is generating the
message, collect the following diagnostic items:
DSNL028 SYSLOG console messages at the site of the • Statistics Class 4 trace record for the LUWID
Db2 ABEND. Obtain copies of the SYS1.LOGREC and associated with the failing request.
If the requester system is a Db2 for z/OS system,
collect the following diagnostic items:
suspect an error in Db2, you might need to report • Console output from the system on which the job
the problem. For information about identifying and was run, and a listing of the SYSLOG data set for the
reporting the problem, see Collecting diagnostic data period of time that spans the failure.
(Collecting data). • All dumps taken by the attachment facility or
Problem determination Related information
Collect the following diagnostic items: DSNL032I (Db2 Messages)
00D34429
Explanation
executing IFCEREP1 at each connected site. The distributed relational data system (DRDS)
. subcomponent has detected that the call type in the
RDI is invalid. This is a Db2 internal error.
00D34428
System action
Explanation
Db2, acting as a DRDA server, has detected an error is requested at the site of the Db2 ABEND.
while parsing a DRDA command and its command data
objects and has generated a DRDA exception.
Operator response
An EXCSQLSTT command was received with the
parameter OUTEXP set to TRUE, but the requester
has not sent any parameter data. Db2 returns a
SYNTAXRM to the requester, writes an IFCID 195 trace System programmer response
record, and generates a DSNL032I console message.
System action: connected to by examining the DSNL027 and
Message DSNL032I is written to the console. A DDM DSNL028 SYSLOG console messages at the site of the
reply message is returned to the requester system. Db2 ABEND. Obtain copies of the SYS1.LOGREC and
Operator response:
System programmer response the problem. For information about identifying and
(Collecting data).

• Console output and the listing of the SYSLOG data The local Db2 has received an ENDUOWRM that
set from each connected site for the period of time indicates that the remote server processed a dynamic
spanning the failure. COMMIT request successfully; however, the SQLCARD
• Listings of the SYS1.LOGREC data set, obtained by that accompanies the ENDUOWRM contains a negative
executing IFCEREP1 at each connected site. SQL return code.
00D3442B
System action
Explanation An alert is generated. If this error has not been
previously detected, then message DSNL031I is
The distributed relational data system (DRDS) written to the MVS console and trace record containing
subcomponent has received a nonzero SQL return the reply from the remote server are written in
code from an invocation of the parser. This is a Db2 statistics class 4. If the error was already detected,
internal error. information from the previous occurrence can be used
to diagnose the problem.
System action During execution the application will receive an
A record is written to SYS1.LOGREC and an SVC dump SQLCODE +30100 for this operation.
Operator response
Determine which sites the ABENDing agent was report the problem. For information about identifying
connected to by examining the DSNL027 and and reporting the problem, see Collecting diagnostic
DSNL028 SYSLOG console messages at the site of the data (Collecting data).
SYSLOG data sets or similar data from each connected Problem determination
any related dumps from each connected site. If you Examine the trace record associated with the failing
suspect an error in Db2, you might need to report request's LUWID to determine the reply message and
the problem. For information about identifying and data that was received by the local Db2. Consult with
reporting the problem, see Collecting diagnostic data the remote server system programmer to diagnose the
(Collecting data). problem.
At this local Db2, collect the following diagnostic
Problem determination items:
• Console output and the listing of the SYSLOG data period of time that spans the failure.
executing IFCEREP1.
.
At this remote server, collect the following diagnostic
00D3442E items:
subcomponent has detected an inconsistency • All dumps taken by the attachment facility or
processing a request using Distributed Relational requesting application.
Database Architecture™ (DRDA) at the local Db2. 00D3442F

The distributed relational data system (DRDS) period of time that spans the failure.
subcomponent has detected an inconsistency
processing a request using Distributed Relational • Listing of SYS1.LOGREC data set, obtained by
Database Architecture (DRDA) at the local Db2. executing IFCEREP1.
The inconsistency may manifest itself as follows:
• In the processing of an embedded SELECT SQL
At the remote server, collect the following items:
statement, a prior execution of this embedded
SELECT SQL statement resulted in a SQLDTARD that • Console output from the system on which the job
is NOT the same as the SQLDTARD received on the was run, and a listing of the SYSLOG data set for the
current execution of this SQL statement. period of time that spans the failure.
• In the processing of an OPEN cursor SQL statement, • All dumps taken by the attachment facility or
a prior description of the resultant data, obtained requesting application.
either as a result of a PREPARE or a prior execution
00D34432
of this SQL statement is NOT the same as the
description of the resultant data that was received
on the current execution of this SQL statement. Explanation
The data length, the data type and CCSID of each The Distributed Relational Data System (DRDS)
column of resultant data is checked for consistency. subcomponent encountered a positive SQL return
code during remote program BIND processing. This is
System action a Db2 internal error.
An alert is generated. If this error has not been

System action
previously detected, then message DSNL031I is
written to the MVS console and trace record containing The request was successfully processed.
the reply from the remote server written in statistics
class 4. If the error was already detected, information 00D34433
from the previous occurrence can be used to diagnose
the problem. Explanation
During execution the application will receive an The distributed relational data system (DRDS)
SQLCODE -30020 for this operation. Subsequent subcomponent encountered a negative SQL return
requests within this unit of work will receive an code. during remote program BIND processing. This
SQLCODE -900 or -906. is a Db2 internal error.

Notify the system programmer. The request was not successfully processed.
00D34434
and reporting the problem, see Collecting diagnostic The distributed relational data system (DRDS)
data (Collecting data). subcomponent was forced to deallocate the
conversation. This is a Db2 internal error.
System action
Examine the trace record associated with the failing
request's LUWID to determine the reply message and The request was not processed successfully.
data that was received by the local Db2. Consult with 00D34436
the remote server system programmer to diagnose the
problem.
Explanation
At the local Db2, collect the following diagnostic items:
subcomponent detected that a remote program BIND

request specified the local site. This is a Db2 internal System programmer response
error.
System action DSNL028 SYSLOG console messages at the site of the
A record is written to SYS1.LOGREC and an SVC dump Db2 ABEND. Obtain copies of the SYS1.LOGREC and
is requested at the site of the BB2 ABEND. SYSLOG data sets from each connected site, the SVC
Notify the system programmer. For information about identifying and reporting the
data).
Determine which sites the ABENDing agent was Problem determination
DSNL028 SYSLOG console messages at the site of the Collect the following diagnostic items:
Db2 ABEND. Obtain copies of the SYS1.LOGREC and • Console output and the listing of the SYSLOG data
SYSLOG data sets from each connected site, the SVC set from each connected site for the period of time
dump at the site of the Db2 failure, and any related spanning the failure.
error in Db2, you might need to report the problem. • Listings of the SYS1.LOGREC data set, obtained by
For information about identifying and reporting the executing IFCEREP1 at each connected site.
problem, see Collecting diagnostic data (Collecting .
data).
00D3443A
Explanation
• Console output and the listing of the SYSLOG data failed because the SYSIBM.USERNAMES table did not
set from each connected site for the period of time contain an inbound row, the TYPE column specified
spanning the failure. as an 'I' describing the Db2 authorization ID to be
• Listings of the SYS1.LOGREC data set, obtained by used for the remote plan owner authorization ID.
executing IFCEREP1 at each connected site. When the USERNAMES column in SYSIBM.LUNAMES
specifies 'I' or 'B', requiring inbound name translation,
. the SYSIBM.USERNAMES table must contain entries
00D34438 describing which Db2 authorization IDs are to be used
Explanation
System action
subcomponent received an invalid SQLD value from The DSNL030I message is issued at the server. The
the Relational Data System (RDS) component as a database access agent is not allocated.
result of a DESCRIBE request. This is a Db2 internal
error. Operator response
System action
A record is written to SYS1.LOGREC and an SVC dump System programmer response
Operator response the indicated LUNAME. If you intend to use
Notify the system programmer. remote authorization IDs that differ from the Db2
authorization IDs, verify that the SYSIBM.USERNAMES

authorization IDs to be used for every possible remote Problem determination
authorization ID.
Examine the trace record associated with the failing
request's LUWID to determine the reply message and
Problem determination data that was received by the local Db2. Consult with
Analyze the SYSIBM.USERNAMES table for an the remote server system programmer to diagnose the
incorrect or missing entry. problem.
00D3443B At the local Db2, collect the following diagnostic items:

executing IFCEREP1.
processing a chained request using Distributed
Relational Database Architecture (DRDA) at the local • Statistics Class 4 trace record for the LUWID
Db2. associated with the failing request.
Examples of inconsistencies follow: At the remote server, collect the following diagnostic
items:
• The local Db2 believes that the chain is intact but
the remote server believes that the chain has been • Console output from the system on which the job
severed. was run, and a listing of the SYSLOG data set for the
• The local Db2 believes that the chain has been
severed but the remote server believes that the • All dumps taken by the attachment facility or
chain is intact. requesting application.
• The local Db2 has received a negative SQL return 00D3443C
code while processing a response to BEGIN BIND
yet the remote server has not severed the chain.
Explanation
System action The distributed relational data system (DRDS) received
an invalid return code from the relational data system
An alert is generated. If this error has not been (RDS) on a string translation request. This is a DRDS
previously detected, then message DSNL031I is internal error.
written to the MVS console and trace record containing
the reply from the remote server are written in
statistics class 4. If the error was already detected,
System action
information from the previous occurrence can be used A record is written to SYS1.LOGREC and an SVC dump
to diagnose the problem. is requested at the site of the Db2 abend.
During BIND, the application will receive a DSNT500I
message. During execution the application will receive Operator response
an SQLCODE -904 for this operation. Subsequent
requests within this unit of work will receive an
SQLCODE -900 or -906.
Operator response Determine which sites the abending agent was
System programmer response SYSLOG data sets from each connected site, the SVC
If you suspect an error in Db2, you might need to dump at the site of the Db2 failure, and any related
report the problem. For information about identifying dumps from each connected site. If you suspect an
and reporting the problem, see Collecting diagnostic error in Db2, you might need to report the problem.
data (Collecting data). For information about identifying and reporting the
data).

Problem determination specifies 'I' or 'B' requiring inbound name translation,
Collect the following diagnostic items: describing which Db2 authorization IDs are to be used
• Console output and the listing of the SYSLOG data for each remote authorization ID from the LU.
spanning the failure. System action
• Listings of the SYS1.LOGREC data set, obtained by The database access agent is not allocated.
00D3443D Operator response
Explanation
The database access request from a remote site System programmer response
contain an inbound row, the TYPE column specified Make sure the USERNAMES column in
as an 'I' describing the Db2 authorization ID to SYSIBM.LUNAMES has been specified correctly for
be used for the remote primary authorization ID. the indicated LUNAME. If you intend to use remote
When the USERNAMES column in SYSIBM.LUNAMES authorization IDs that differ from Db2 authorization
specifies 'I' or 'B' requiring inbound name translation, IDs, verify that the SYSIBM.USERNAMES table has
the SYSIBM.USERNAMES table must contain entries rows that correctly specify the Db2 authorization IDs
describing which Db2 authorization IDs are to be used to be used for every possible remote authorization ID.
System action Analyze the SYSIBM.USERNAMES table for an
The DSNL030I message is issued at the server. The incorrect or missing entry.
database access agent is not allocated. 00D3443F

Notify the communications database administrator. The connection to the remote server failed. The
SYSIBM.USERNAMES table did not contain an
System programmer response outbound row and did not specify the remote
authorization ID for the package owner Db2
Make sure the USERNAMES column in authorization ID. When the USERNAMES column in
SYSIBM.LUNAMES has been specified correctly for SYSIBM.LUNAMES or SYSIBM.IPNAMES is specified as
the indicated LUNAME. If you intend to use remote 'O' or 'B', outbound name translation is in use. The
authorization IDs that differ from Db2 authorization SYSIBM.USERNAMES table must contain entries that
IDs, verify that the SYSIBM.USERNAMES table has describe the remote authorization IDs that are used
rows that correctly specify the Db2 authorization IDs for each Db2 authorization ID that communicates with
to be used for every possible remote authorization ID. the LU or the TCP/IP address.

Analyze the SYSIBM.USERNAMES table for an A response is sent to the application to indicate that
incorrect or missing entry. the resource is unavailable. The request is not sent to
00D3443E the remote site.

The database access request from a remote site Notify the communications database administrator.
contain an inbound row, the TYPE column specified System programmer response
as an 'I' describing the Db2 authorization ID to be
used for the remote package owner authorization ID. Make sure the USERNAMES column in
When the USERNAMES column in SYSIBM.LUNAMES SYSIBM.LUNAMES or SYSIBM.IPNAMES is specified

correctly for the indicated LUNAME or IPADDR. If trace record, and generates a DSNL032I console
you intend to use remote authorization IDs that message.
System action:
Message DSNL032I is written to the console. A DDM
remote authorization ID to be used for each possible
reply message is returned to the requester system.
the TYPE column of the SYSIBM.USERNAMES table. Operator response:
incorrect or missing entry. If you suspect an error in Db2, you might need to
00D34440 and reporting the problem, see Collecting diagnostic
Explanation
A timeout or deadlock was detected during remote Problem determination
bind processing. This can occur during BIND, REBIND, Analyze the statistics class 4 trace record identified
or FREE. by the IFCID sequence number enumerated in the
DSNL032I message.
System action
At the Db2 DRDA server system that is generating the
The BIND is not successful. message, collect the following diagnostic items:
System programmer response associated with the failing request.
None is required. If the requester system is a Db2 for z/OS system,
Reissue the BIND subcommand.
Related information
• Console output from the system on which the job DSNL032I (Db2 Messages)
00D34441
Explanation
Explanation The distributed relational data system (DRDS)
Db2, acting as a DRDA server, has detected an error
processing a request using Distributed Relational
while parsing a DRDA command and its command data
Database Architecture (DRDA) at the local Db2.
objects and has generated a DRDA exception. One of
the following error conditions might have occurred: The local Db2 has received an ENDUOWRM that
indicates that the remote server processed a dynamic
• An EXCSQLSTT command was received specifying
ROLLBACK request successfully; however, the server
a stored procedure name (PRCNAM), but the
should not have processed the ROLLBACK for one of
statement is not a stored procedure call. Db2 returns
a CMDCHKRM to the requester.
• An EXCSQLIMM or EXCSQLSTT command was • The server was not available to update
received from the requester specifying an invalid • The server was participating in two phase commit
QRYINSID instance variable. Db2 returns a protocols with the current request
VALNSPRM to the requester, writes an IFCID 192

System action a DDM CNTQRY command received from a remote
requester.
An alert is generated. If this error has not been
previously detected, then message DSNL031I is A previous CNTQRY command specified a
written to the MVS console and trace record containing QRYROWSET parameter, which indicated the number
the reply from the remote server are written in of rows to be returned as a rowset. Because of the
statistics class 4. If the error was already detected, blocking limits in effect with the requester, only a
information from the previous occurrence can be used partial rowset was returned to the requester. Some
to diagnose the problem. rows in the requested rowset are still unfetched
and are pending. The DRDA rules require that this
During execution, the application will receive an subsequent CNTQRY command must either:
SQLCODE -904 for this operation. The connection to
the server will be terminated. • Specify a QRYROWSET value that is equal to the
number of pending rows in the rowset.
Operator response • Reset the query blocks from the pending rowset
Notify the system programmer. The CNTQRY command did not specify the
QRYRSTBLK parameter to reset the query blocks, so
this command is assumed to completes the pending
System programmer response rowset. Because the requested QRYROWSET value
If you suspect an error in Db2, you might need to does not equal the number of pending rows in the
report the problem. For information about identifying rowset that was requested by the previous CNTQRY, a
and reporting the problem, see Collecting diagnostic DRDA exception occurred.
System action
Problem determination Message DSNL032I is written to the console, and a
Examine the trace record associated with the LUWID DDM reply message (PRCCNVRM) is returned to the
of the failing request to determine the reply message requester system.
and data that was received by the local Db2.
Consult with the remote server system programmer to Operator response
diagnose the problem.
For the local Db2 that made the request, collect the
• Listing of SYS1.LOGREC data set, obtained by data (Collecting data).
executing IFCEREP1.
• Statistics Class 4 trace record for the LUWID Problem determination
Analyze the statistics class 4 trace record that is
For the remote server that received the request,
identified by the IFCID sequence number that is
enumerated in the DSNL032I message.
• All dumps taken by the attachment facility or • Console output from the system on which the job
requesting application. was run, and a listing of the SYSLOG data set for the
00D34445 • Statistics Class 4 trace record for the LUWID
Explanation • All dumps taken by the attachment facility or
The distributed relational data system (DRDS) requesting application.
subcomponent detected an error while processing

At the Db2 server system that generated the • Statistics Class 4 trace record for the LUWID
DSNL032I message, collect the following diagnostic associated with the failing request.
items: • All dumps taken by the attachment facility or
• Console output from the system on which the job requesting application.
was run, and a listing of the SYSLOG data set for the At the Db2 server system that generated the
period of time that spans the failure. DSNL032I message, collect the following diagnostic
• Statistics Class 4 trace record for the LUWID items:
• All dumps taken by the attachment facility or was run, and a listing of the SYSLOG data set for the
requesting application. period of time that spans the failure.
Related information • Statistics Class 4 trace record for the LUWID
DSNL032I (Db2 Messages) associated with the failing request.
00D34447 requesting application.
Related information
Explanation
subcomponent detected an error while processing 00D34448
a DDM CNTQRY command received from a remote
requester. If either or both the OPNQRY command Explanation
and the first CNTQRY command specified QRYROWSET
parameter, then all subsequent CNTQRY commands The distributed relational data system (DRDS)
must specify the QRYROWSET parameter explicitly. subcomponent detected an error while processing
The CNTQRY command did not specify a QRYROWSET a DDM CNTQRY command received from a remote
parameter as required by the DRDA rules and a DRDA requester. If both the OPNQRY command and the first
exception occurred. CNTQRY command did not specify the QRYROWSET
parameter, then subsequent CNTQRY commands must
not specify the QRYROWSET parameter. The CNTQRY
System action command specified a QRYROWSET parameter which is
Message DSNL032I is written to the console, and a prohibited by the DRDA rules and a DRDA exception
DDM reply message (PRCCNVRM) is returned to the occurred.
requester system.
System action
Operator response Message DSNL032I is written to the console, and a
Notify the system programmer. DDM reply message (PRCCNVRM) is returned to the
requester system.
Operator response
report the problem. For information about identifying Notify the system programmer.
Analyze the statistics class 4 trace record that is and reporting the problem, see Collecting diagnostic
identified by the IFCID sequence number that is data (Collecting data).
If the requester system is a Db2 for z/OS system, Problem determination
collect the following diagnostic items: Analyze the statistics class 4 trace record that is
• Console output from the system on which the job identified by the IFCID sequence number that is
was run, and a listing of the SYSLOG data set for the enumerated in the DSNL032I message.

If the requester system is a Db2 for z/OS system, System programmer response
• Console output from the system on which the job report the problem. For information about identifying
was run, and a listing of the SYSLOG data set for the and reporting the problem, see Collecting diagnostic
period of time that spans the failure. data (Collecting data).
associated with the failing request. Problem determination
Analyze the statistics class 4 trace record that is
identified by the IFCID sequence number that is
At the Db2 server system that generated the enumerated in the DSNL032I message.
DSNL032I message, collect the following diagnostic
items:
Related information
At the Db2 server system that generated the
DSNL032I (Db2 Messages) DSNL032I message, collect the following diagnostic
items:
00D34449
Explanation
The distributed relational data system (DRDS) • Statistics Class 4 trace record for the LUWID
subcomponent detected an error while processing associated with the failing request.
a DDM CNTQRY command received from a
remote requester. Scrolling parameters (such • All dumps taken by the attachment facility or
as QRYSCRORN, QRYROWNBR, QRYROWSNS, requesting application.
QRYBLKRST, QRYRTNDTA) were specified on the Related information
CNTQRY command, but one of the following conditions DSNL032I (Db2 Messages)
exists:
• The cursor is not scrollable. 00D3444A
• The cursor is scrollable, but it is being accessed by
the requester in a non-scrollable manner. (Neither Explanation
the OPNQRY command nor the first CNTQRY The distributed relational data system (DRDS)
command specified the QRYROWSET parameter.) subcomponent detected an error while processing
A DRDA exception occurred. a DDM CNTQRY command received from a remote
requester. The CNTQRY is fetching data from a
scrollable cursor which is being accessed in a
System action scrollable manner by the requester. The CNTQRY
Message DSNL032I is written to the console, and a command will return one or more LOB columns as
DDM reply message (PRCCNVRM) is returned to the LOB data, but the RTNEXTDTA parameter on the
requester system. CNTQRY command (indicating how LOB values are to
be returned) did not specify RTNEXTALL as required by
the DRDA rules. A DRDA exception is generated.
Operator response

System action blocking limits in effect with the requester, only a
partial rowset was returned to the requester and a
Message DSNL032I is written to the console, and a number of rows in the requested rowset are still
DDM reply message (PRCCNVRM) is returned to the unfetched, and remain in pending state. The DRDA
requester system. rules require that this subsequent CNTQRY command
either reset the pending query blocks by means of the
Operator response QRYRSTBLK parameter or must explicitly or implicitly
specify a FETCH NEXT orientation (RELATIVE+1) to
Notify the system programmer. complete the pending rowset.The CNTQRY command
did not reset the pending rowset and did not specify
System programmer response the FETCH NEXT orientation, resulting in a DRDA
exception.
data (Collecting data). The message DSNL032I is written to the console.
Refer to the description of this message for further
Problem determination information.
Analyze the statistics class 4 trace record that is A DDM reply message (PRCCNVRM) is returned to the
identified by the IFCID sequence number that is requester system.
If the requester system is a Db2 for z/OS system, Operator response
collect the following diagnostic items: Notify the system programmer.
was run, and a listing of the SYSLOG data set for the System programmer response
• All dumps taken by the attachment facility or data (Collecting data).
At the Db2 server system that generated the Problem determination
items: Analyze the statistics class 4 trace record identified
• Console output from the system on which the job DSNL032I message.
period of time that spans the failure. If the requester system is a Db2 for z/OS system,
associated with the failing request. • Console output from the system on which the job
Related information associated with the failing request.
00D3444C
At the Db2 server system that is generating the
Explanation message, collect the following diagnostic items:
subcomponent detected an error while processing
a DDM CNTQRY command received from a remote
requester. A previous CNTQRY command specified • Statistics Class 4 trace record for the LUWID
a QRYROWSET parameter, indicating the number of associated with the failing request.
rows to be returned as a rowset. Because of the

00D3444F
executing IFCEREP1.
Explanation
Acting as a DRDA server, Db2 has detected an error program or batch job, and system messages that
while parsing an SQLDTA object received from a DRDA were issued. Make sure that MSGLEVEL=(1,1) on the
requester system. The total FDODTA object length, as JOB statement so that all diagnostic information is
determined by parsing the individual data items in the sent to SYSPRINT.
FDODTA object, is smaller than the stated length of the
• UTPRINT output, produced by utility invocation of
FDODTA object itself.
SORT.
System action Db2 (for 04E and 04F abends). Availability of this
The system generates an alert and returns message dump is dependent on the failing environment.
DSNL032I. Refer to the description of this message • SYSABEND, SYSUDUMP, or SYSMDUMP output.
for further information. A DDM reply message Availability of these dumps is dependent on the
(SYNTAXRM) is returned to the requester system. failing environment.
00D34450
and reporting the problem, see Collecting diagnostic Acting as a DRDA server, Db2 has detected an error
data (Collecting data). while parsing an SQLDTA object received from a
DRDA requester system. While parsing the FDODTA
constituent of the SQLDTA object, a data item has a
Problem determination stated or implied length that is larger than the stated
You should analyze the statistics class 4 trace record length of the FDODTA object itself.
identified by the IFCID sequence number enumerated
in the DSNL032I message. System action
At the Db2 for z/OS DRDA server, collect the following The system generates an alert and returns message
diagnostic items: DSNL032I. Refer to the description of this message
• Console output from the system on which the job for further information. A DDM reply message
was run, and a listing of the SYSLOG data set for the (SYNTAXRM) is returns to the requester system.
• Listing of SYS1.LOGREC data set, obtained by Programmer response
executing IFCEREP1. Modify the stored procedure to return result sets that
• SYSPRINT output, including JCL, for the application include only data types that are supported by the
program or batch job, and system messages that requester. You may also upgrade the level of the code
were issued. Make sure that MSGLEVEL=(1,1) on the at the requester to one that supports the data types
JOB statement so that all diagnostic information is that were returned by the server.
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of Programmer response
SORT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by report the problem. For information about identifying
Db2 (for 04E and 04F abends). Availability of this and reporting the problem, see Collecting diagnostic
dump is dependent on the failing environment. data (Collecting data).
Availability of these dumps is dependent on the Problem determination
failing environment.
You should analyze the statistics class 4 trace record
If the requester is a Db2 for z/OS system, collect the
in the DSNL032I message.

At the Db2 for z/OS DRDA server, collect the following System action
diagnostic items:
The SQL statement is rejected.
• Listing of SYS1.LOGREC data set, obtained by Bind the application package at the server after
executing IFCEREP1. the location alias is defined. For a data sharing
group, ensure that the location alias is defined on all
members.
JOB statement so that all diagnostic information is Problem determination
sent to SYSPRINT.
Use the DISPLAY DDF command to determine the
• UTPRINT output, produced by utility invocation of location aliases for the server. Ensure that any location
SORT. alias references in the application exist at the server
• Dynamic dump, taken to SYS1.DUMPxx data set, by when the package is bound.
Db2 (for 04E and 04F abends). Availability of this Related concepts
dump is dependent on the failing environment.
Member-specific TCP/IP access (Db2 Data
• SYSABEND, SYSUDUMP, or SYSMDUMP output. Sharing Planning and Administration)
Availability of these dumps is dependent on the Considerations for binding packages at a
failing environment. remote location (Db2 Application programming
If the requester is a Db2 for z/OS system, collect the and SQL)
following diagnostic items: Related reference
• Console output from the system on which the job Bind options for remote access (Db2
was run, and a listing of the SYSLOG data set for the Application programming and SQL)
period of time that spans the failure. -DISPLAY DDF (Db2) (Db2 Commands)
• Listing of SYS1.LOGREC data set, obtained by 00D34452
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application Explanation
were issued. Make sure that MSGLEVEL=(1,1) on the The request failed because table
JOB statement so that all diagnostic information is SYSIBM.DSNSERVICE is unavailable.
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of System action
SORT.
The native REST request, DSN subcommand BIND
• Dynamic dump, taken to SYS1.DUMPxx data set, by SERVICE, or DSN subcommand FREE SERVICE is
Db2 (for 04E and 04F abends). Availability of this terminated.
User response:
Refer to Enabling Db2 REST services (Db2 REST
Availability of these dumps is dependent on the
services) for information on creating the required
database objects for Db2 REST services.
00D34451 Related tasks
Enabling Db2 REST services (Db2 REST
Explanation services)
Related reference
A remote application connected to a Db2 server and Db2 REST services table
issued an SQL statement that contain a three-part (SYSIBM.DSNSERVICE) (Db2-supplied user
name or alias that refers to an table or view at tables)
a remote location. However, the remote reference
actually resolves to the local Db2 server location. This 00D35000
situation can occur when the SQL statement refers to
a location alias but the package for the application was
bound before the location alias was defined.

Db2 has detected a DRDA exception condition. This is Execution of the SQL statement fails during DRDA
a generic reason code that describes a situation not processing, which is before or after Db2 executes the
covered by any other reason codes. SQL statement.
For a stored procedure call, the stored procedure has
System action already executed when this reason code is issued. If
the stored procedure returns any result sets, they are
An alert is generated and message DSNL031I is
still open.
written to the console. Refer to the description of this
message for further information. In some cases, if the storage limit was already
reached during previous Db2 processing, Db2 takes
Operator response the following actions:
Notify the system programmer. • Requests an abend and an SVC dump.

• Writes a record to SYS1.LOGREC.
System programmer response • Writes messages DSNL027I and DSNL028I to the
console.
report the problem. For information about identifying • Writes message DSNL500I to the console if the
and reporting the problem, see Collecting diagnostic conversation is terminated as a result of the abend.
Programmer response
Problem determination To avoid this error, take one or more of the following
The statistics class 4 trace record identified by the actions:
IFCID sequence number enumerated in the DSNL031I • Reduce the number of parameters or the sizes of
message should be analyzed. the parameters that are returned by the stored
Collect the following diagnostic items at the local Db2. procedure. Doing so might reduce the required
storage.
• Statistics class 4 trace record identified by the IFCID
• Reduce the amount of storage that is used by array
sequence number specified in message DSNL031I.
parameters by reducing the number of elements in
Collect the following diagnostic items at the remote the array, or by reducing the declared size of the
server. elements in the array.
• Relevant error and system logs spanning the time of • If the SQL CALL statement failed, and the called
the failure. stored procedure returns result sets, modify the
calling application in the following ways:
• Any relevant remote server trace information or
dumps. – Include COMMIT statements to close WITHOUT
HOLD result sets.
00D35001
– Include ROLLBACK statements to close WITH
HOLD result sets.
Explanation
• If an abend and SVC dump were generated, the
Db2 calculated the maximum amount of storage that is problem might be a Db2 error. If you suspect an
required for sending application input or output data error in Db2, you might need to report the problem.
through DRDA, and determined that the calculated For information about identifying and reporting the
value exceeds the system limit. problem, see Collecting diagnostic data (Collecting
For a stored procedure call in which at least one data).
of the parameters is an array type, the maximum
amount of storage that is needed to send the array, Problem determination
in combination with the amount of storage that is used
If the SQL CALL statement failed, collect the following
by other parameters, is too large. The actual declared
diagnostic items:
cardinality of the array parameter and the maximum
declared length of the array elements are used in the • Listings of the results that were produced by all SQL
calculation. statements in the calling application program and
the called stored procedure.

• Source listings of the calling application program and and reporting the problem, see Collecting diagnostic
the called stored procedure. data (Collecting data).
If an abend and SVC dump were generated, take the
following actions: Problem determination
1. Identify all connected systems that participated Identify all connected systems participating in the
in the processing of the remote request. Those processing of the remote request. This includes
systems include: the requester system to which the application is
connected and the data server which is the target of
• The requester system to which the application is
the remote request. This may include intermediate
connected
server systems. Determine which sites the abending
• The data server that is the target of the remote agent was connected to by examining the DSNL027
request and DSNL028 SYSLOG console messages at the site of
• Any intermediate server systems the Db2 abend.
2. At the site of the Db2 abend, examine messages For each connected system that is a Db2 system
DSNL027I and DSNL028I in the console log to collect the diagnostic items:
determine the sites to which the agent that
received the abend was connected.
3. For each connected Db2 system, collect the spanning the failure.
• Console output from the system on which the job executing IFCEREP1 at each connected site.
was run, and a listing of the SYSLOG data set for • All dumps created by this failure.
the period of time that spans the failure.
For non-Db2 systems, refer to the documentation
specific to those products for diagnostic procedures.
executing IFCEREP1.
• All dumps created by this failure. 00D35030
Related information
Explanation
DSNL028I (Db2 Messages) Db2, acting as a DRDA server, detected an error while
DSNL500I (Db2 Messages) processing an SQL request from a remote DRDA client.
Db2 was building a DDM query descriptor (QRYDSC
00D35011 or FDODSC) to return to the DRDA client, but could
not do so because the descriptor required more late
environment descriptors (LEDs) than Db2 can support.
Explanation
The distributed data interchange system (DDIS) System action
component detected an internal error. This is a Db2
internal error. The DBAA is abended. The conversation with the
remote site is terminated. At the server console, the
DSNL027I message is issued, accompanied by one or
System action more DSNL028I messages identifying all remote sites
A record is written to SYS1.LOGREC and an SVC where the distributed agent also exists and where
dump is requested at the site of the abend. Messages diagnostic information might also be collected.
DSNL027 and DSNL028 are written to the console.
If the conversation is terminated as a result of the Operator response
abend, DSNL500I is also written.
Notify the application programmer or user creating the
SQL statement.
Operator response
If the remote DRDA client is a Db2 for z/OS system,
Notify the system programmer. collect the following diagnostic items:

For other remote DRDA clients, refer to the DSNL031I message should be analyzed. For the Db2
client product documentation for diagnostic system generating the DSNL031I message, collect the
recommendations. following diagnostic items:
At Db2 DRDA server, collect the following diagnostic • Statistics Class 4 trace record for the LUWID
items: associated with the failing request.
• Console output from the system on which the job In addition, identify all connected systems
was run, and a listing of the SYSLOG data set for the participating in the processing of the remote request.
period of time that spans the failure. This includes the requester system to which the
• All dumps taken by the attachment facility or application is connected and the data server which is
requesting application. the target of the remote request. This may also include
intermediate server systems. For each system that is a
Db2 system, collect the following diagnostic items:
User response
The SQL request issued by the client cannot be set from each connected site for the period of time
processed by Db2. As a circumvention, the SQL spanning the failure.
request can be simplified to reduce the number
of LEDs required to describe the data using DRDA. For non-Db2 systems, refer to the references specific
LEDs may be required, for example, if columns being to those products.
fetched are in a different code page (CCSID) than the If any dumps were generated on any Db2 system
default CCSID for the Db2 for z/OS system. participating in processing the remote request, collect
00D35101 the following diagnostic items:
Explanation executing IFCEREP1 at each connected site.
Db2 has detected an error in the DDM reply message
or DDM reply data object received from the remote 00D35102
server in response to a DDM command. The DDM level
6b object, other than a Reply DSS or an Object DSS, is
Explanation
invalid.
Db2 has detected an error in the DDM reply data object
Db2 may be acting as a requester system for a local
received from the remote server in response to a DDM
application or may be acting as an intermediate DRDA
command. The object, carried in a level 6b OBJDSS, is
system for a remote application on another DRDA
not defined as valid for DDM level 3.
requester system.

message for further information.
The application will receive SQLCODE -30072 and
Operator response SQLSTATE 58016.

Operator response

Problem determination data (Collecting data).
The statistics class 4 trace record identified by

the IFCID sequence number enumerated in the

Problem determination At this remote server, collect the following diagnostic
items:
The statistics class 4 trace record identified by the
IFCID sequence number enumerated in the DSNL031I • Console output from the system on which the job
message should be analyzed. was run, and a listing of the SYSLOG data set for the
associated with the failing request. 00D35104

items: Explanation
• Console output from the system on which the job Db2 has detected an error in the DDM reply message
was run, and a listing of the SYSLOG data set for the or DDM reply data object received from the remote
period of time that spans the failure. server in response to a DDM command. The reply data
object is not defined by DRDA.
System action
00D35103
Explanation message for further information.
Db2 has detected an error in the DDM reply message The application will receive SQLCODE -30071 and
or DDM reply data object received from the remote SQLSTATE 58015.
server in response to a DDM command. Multiple
instances of a DDM reply data object, defined within
DDM level 3 as nonrepeatable, have been returned. Operator response
System action
An alert is generated and message DSNL031I is System programmer response
written to the console. Refer to the description of this If you suspect an error in Db2, you might need to
message for further information. report the problem. For information about identifying
The application will receive SQLCODE -30000 and and reporting the problem, see Collecting diagnostic
SQLSTATE 58008. data (Collecting data).

Notify the system programmer. The statistics class 4 trace record identified by the
IFCID sequence number enumerated in the DSNL031I
message should be analyzed.
Collect the following diagnostic items at this local Db2.
report the problem. For information about identifying • Statistics Class 4 trace record identified by the IFCID
and reporting the problem, see Collecting diagnostic sequence number specified in message DSNL031I.
data (Collecting data). Collect the following diagnostic items at the remote
server.
Problem determination • Relevant error and system logs spanning the time of
The statistics class 4 trace record identified by the the failure.
IFCID sequence number enumerated in the DSNL031I • Any relevant remote server trace information or
message should be analyzed. dumps.
At this local Db2, collect the following diagnostic 00D35105
items:

Db2 has detected an error in the DDM reply message An alert is generated and message DSNL031I is
or DDM reply data object received from the remote written to the console. Refer to the description of this
server in response to a DDM command. While defined message for further information.
by DDM Level 3 as a valid reply object for this
command, Db2 does not support the object.
SQLSTATE 58008.
System action
Operator response
SQLSTATE 58008. If you suspect an error in Db2, you might need to
Operator response
If you suspect an error in Db2, you might need to the IFCID sequence number enumerated in the
report the problem. For information about identifying DSNL031I message should be analyzed. For the Db2
and reporting the problem, see Collecting diagnostic system generating the DSNL031I message, collect the
data (Collecting data). following diagnostic items:
Problem determination associated with the failing request.
The statistics class 4 trace record identified by the In addition, identify all connected systems
IFCID sequence number enumerated in the DSNL031I participating in the processing of the remote request.
message should be analyzed. This includes the requester system to which the
application is connected and the data server which is
the target of the remote request. This may also include
items:
• Statistics Class 4 trace record for the LUWID Db2 system, collect the following diagnostic items:
At this remote server, collect the following diagnostic set from each connected site for the period of time
items: spanning the failure.
• Console output from the system on which the job For non-Db2 systems, refer to the references specific
was run, and a listing of the SYSLOG data set for the to those products.
• All dumps taken by the attachment facility or participating in processing the remote request, collect
requesting application. the following diagnostic items:
00D35106 • Listings of the SYS1.LOGREC data set, obtained by
Explanation • All dumps created by this failure.
Db2 has detected an error in the DDM reply message 00D35107
or DDM reply data object received from the remote
server in response to a DDM command. The object
Explanation
must be contained within a single OBJDSS, but was
received in an OBJDSS which contained other objects. Db2 has detected an error in the DDM reply message
server in response to a DDM command. One or more

DDM reply data objects, defined by DDM Level-3 as System action
required for the DDM command, were not received.
System action message for further information.
An alert is generated and message DSNL031I is The application will receive SQLCODE -30000 and
written to the console. Refer to the description of this SQLSTATE 58008.
The application will receive SQLCODE -30000 and Operator response
SQLSTATE 58008.
Operator response
Problem determination message should be analyzed.
The statistics class 4 trace record identified by the At this local Db2, collect the following diagnostic
IFCID sequence number enumerated in the DSNL031I items:
At this local Db2, collect the following diagnostic associated with the failing request.
items:
At this remote server, collect the following diagnostic was run, and a listing of the SYSLOG data set for the
items: period of time that spans the failure.
• Console output from the system on which the job • All dumps taken by the attachment facility or
was run, and a listing of the SYSLOG data set for the requesting application.
00D35109
Explanation
00D35108
Db2 has detected an error in the DDM SQLDTARD reply
data object received in response to a DDM EXCSQLSTT
Explanation command. The DDM SQLDTARD object is a collection
Db2 has detected an error in the DDM SQLDTARD consisting of the FDODSC and FDODTA scalars. The
reply data object received in response to a DDM FDODSC scalar, describing a single row returned on
EXCSQLSTT command. The SQL operation is a SELECT SELECT, is not contained with the SQLDTARD reply
and the size of the FDODSC scalar, contained within data object. The DDM SQLDTARD object is a collection
the SQLDTARD, exceeds 32KB. The DDM extended which contains the FDODSC and FDODTA DDM objects.
length field required to support this is invalid. The The FDODSC element, describing the single row, is not
SQL operation is a SELECT and the size of the contained within the SQLDTARD reply data object.
FDODSC object, contained within the SQLDTARD
collection, exceeds 32KB. The DDM extended length System action
field required to support this is invalid.

The application will receive SQLCODE -30000 and Operator response
SQLSTATE 58008.
Operator response
items:
At this remote server, collect the following diagnostic was run, and a listing of the SYSLOG data set for the
00D3510B
Explanation
00D3510A
Db2 has detected an error in the DDM SQLDTARD reply
data object received in response to a DDM EXCSQLSTT
Explanation command. The SQL operation is a SELECT and the
Db2 has detected an error in the DDM SQLDTARD reply size of the resultant row, contained with the FDODTA
data object received in response to a DDM EXCSQLSTT scalar, exceeds 32KB. The FDODTA DDM extended
command. The DDM SQLDTARD object is a collection length field required to support this is invalid. The SQL
consisting of the FDODSC and FDODTA scalars. The operation is a SELECT and the size of the resultant
FDODTA scalar, containing the single row described by row exceeds 32KB. The DDM extended length field
the FDODSC, is not contained within the SQLDTARD required to support this is invalid.
reply data object. The DDM SQLDTARD object is a
collection which contains the FDODSC and FDODTA System action
DDM objects. The FDODTA element, containing the
single row, is not contained within the SQLDTARD reply An alert is generated and message DSNL031I is
data object. written to the console. Refer to the description of this
System action The application will receive SQLCODE -30000 and

SQLSTATE 58008.
message for further information. Operator response
The application will receive SQLCODE -30000 and Notify the system programmer.
SQLSTATE 58008.

If you suspect an error in Db2, you might need to The statistics class 4 trace record identified by the
report the problem. For information about identifying IFCID sequence number enumerated in the DSNL031I
and reporting the problem, see Collecting diagnostic message should be analyzed.
items:
The statistics class 4 trace record identified by the associated with the failing request.
items:
items:
• Statistics Class 4 trace record for the LUWID period of time that spans the failure.
associated with the failing request. • All dumps taken by the attachment facility or
At this remote server, collect the following diagnostic requesting application.
items:
00D3510D
was run, and a listing of the SYSLOG data set for the Explanation
• All dumps taken by the attachment facility or Db2 has detected an error in the DDM reply message
requesting application. or DDM reply data object received from the remote
server in response to a DDM command. The DDM
00D3510C object is a TYPDEFNAM signaling a change in machine
representation. The length of the DDM object is
Explanation incorrect.

System action
server in response to a DDM command. The SQL An alert is generated and message DSNL031I is
operation is a SELECT and the size of the SQLDTARD, written to the console. Refer to the description of this
a DDM collection consisting of the FDODSC and message for further information.
FDODTA scalars, SQLDTARD is greater than the sum
of the lengths of the constituent FDODSC and FDODTA
SQLSTATE 58008.
scalars. The object is invalid.

message for further information. System programmer response
The application will receive SQLCODE -30000 and If you suspect an error in Db2, you might need to
SQLSTATE 58008. report the problem. For information about identifying
Operator response
If you suspect an error in Db2, you might need to message should be analyzed.
items:

• Statistics Class 4 trace record for the LUWID • Console output from the system on which the job
associated with the failing request. was run, and a listing of the SYSLOG data set for the
was run, and a listing of the SYSLOG data set for the 00D3510F
• All dumps taken by the attachment facility or Explanation
00D3510E or DDM reply data object received from the remote
object is a TYPDEFOVR collection signaling a remote
Explanation
server change in CCSIDs. The length of one of
Db2 has detected an error in the DDM reply message the constituent scalars, CCSIDSBC, CCSIDMBC or
or DDM reply data object received from the remote CCSIDDBC is incorrect.
object is a TYPDEFNAM signaling a change in machine System action
representation. The value of the DDM object specifies
a machine environment which is not supported by An alert is generated and message DSNL031I is
DRDA. written to the console. Refer to the description of this
SQLSTATE 58008.
SQLSTATE 58008.
Operator response
Notify the system programmer. report the problem. For information about identifying
and reporting the problem, see Collecting diagnostic The statistics class 4 trace record identified by the
data (Collecting data). IFCID sequence number enumerated in the DSNL031I
Problem determination At this local Db2, collect the following diagnostic
items:
IFCID sequence number enumerated in the DSNL031I • Statistics Class 4 trace record for the LUWID
message should be analyzed. associated with the failing request.
At this local Db2, collect the following diagnostic At this remote server, collect the following diagnostic
items: items:
00D35110

Explanation contains multiple occurrences of the CCSIDSBC scalar
(MIXED CCSID). This is an error. The DDM object is
Db2 has detected an error in the DDM TYPEDEFOVR a TYPDEFOVR collection signaling a remote server
reply data object received from the remote server change in CCSIDs. The CCSIDMBC (MIXED CCSID)
in response to a DDM command, signaling a change code point is invalid.
in the remote server CCSIDs. The TYPEDEFOVR
contains multiple occurrences of the CCSIDSBC scalar
(SBCS CCSID). This is an error. The DDM object is System action
a TYPDEFOVR collection signaling a remote server An alert is generated and message DSNL031I is
change in CCSIDs. The CCSIDSBC (SBCS CCSID) code written to the console. Refer to the description of this
point is invalid. message for further information.
System action SQLSTATE 58008.
written to the console. Refer to the description of this Operator response
SQLSTATE 58008.
Operator response If you suspect an error in Db2, you might need to
report the problem. For information about identifying The statistics class 4 trace record identified by the
and reporting the problem, see Collecting diagnostic IFCID sequence number enumerated in the DSNL031I
data (Collecting data). message should be analyzed.
The statistics class 4 trace record identified by the • Statistics Class 4 trace record for the LUWID
IFCID sequence number enumerated in the DSNL031I associated with the failing request.
At this local Db2, collect the following diagnostic items:
items:
• Statistics Class 4 trace record for the LUWID was run, and a listing of the SYSLOG data set for the
associated with the failing request. period of time that spans the failure.
At this remote server, collect the following diagnostic • All dumps taken by the attachment facility or
items: requesting application.
Explanation
requesting application. Db2 has detected an error in the DDM TYPEDEFOVR
reply data object received from the remote server
00D35111 in response to a DDM command, signaling a change
Explanation contains multiple occurrences of the CCSIDSBC scalar
(GRAPHIC CCSID). This is an error. The DDM object
Db2 has detected an error in the DDM TYPEDEFOVR is a TYPDEFOVR collection signaling a remote server
reply data object received from the remote server change in CCSIDs. The CCSIDDBC (GRAPHIC CCSID)
response to a DDM command, signaling a change code point is invalid.

An alert is generated and message DSNL031I is Notify the system programmer.
SQLSTATE 58008.
System programmer response The statistics class 4 trace record identified by the
and reporting the problem, see Collecting diagnostic At this local Db2, collect the following diagnostic
data (Collecting data). items:
The statistics class 4 trace record identified by the At this remote server, collect the following diagnostic
At this local Db2, collect the following diagnostic was run, and a listing of the SYSLOG data set for the
• Statistics Class 4 trace record for the LUWID • All dumps taken by the attachment facility or
associated with the failing request. requesting application.
At this remote server, collect the following diagnostic 00D35114
items:
• All dumps taken by the attachment facility or server in response to a DDM command. The length of
requesting application. the DDM reply message is inconsistent with the length
of its DSS carrier.
00D35113
System action
Explanation
object is a TYPDEFOVR collection signaling a remote The application will receive SQLCODE -30000 and
server change in CCSIDs. The DDM object length is SQLSTATE 58008.
invalid.
Operator response
System action
written to the console. Refer to the description of this System programmer response
SQLSTATE 58008.

Problem determination Collect the following diagnostic items at the remote
server.
IFCID sequence number enumerated in the DSNL031I • Relevant error and system logs spanning the time of
message should be analyzed. the failure.
Collect the following diagnostic items at this local Db2. • Any relevant remote server trace information or
dumps.
sequence number specified in message DSNL031I. 00D35116
Collect the following diagnostic items at the remote

server. Explanation
• Relevant error and system logs spanning the time of Db2 has detected an error in the DDM reply message
the failure. or DDM reply data object received from the remote
server in response to a DDM command. The DDM reply
• Any relevant remote server trace information or message is not valid for the current command.
dumps.
Explanation written to the console. Refer to the description of this
Db2 has detected an error in the DDM reply message message for further information.
or DDM reply data object received from the remote The application will receive SQLCODE -30000 and
server in response to a DDM command. The sum of SQLSTATE 58008.
the lengths of the constituent DDM objects within an
OBJDSS is inconsistent with the length of the DSS
carrier. Operator response
System action

report the problem. For information about identifying • Statistics class 4 trace record identified by the IFCID
and reporting the problem, see Collecting diagnostic sequence number specified in message DSNL031I.
data (Collecting data). Collect the following diagnostic items at the remote
server.
Problem determination • Relevant error and system logs spanning the time of
The statistics class 4 trace record identified by the the failure.
IFCID sequence number enumerated in the DSNL031I • Any relevant remote server trace information or
message should be analyzed. dumps.
Collect the following diagnostic items at this local Db2. 00D35117

Db2 has detected an error in the SQLDTARD reply data An alert is generated and message DSNL031I is
object received in response to an EXCSQLSTT DDM written to the console. Refer to the description of this
command. The FDODTA element of the SQLDTARD message for further information.
collection contains a null SQLDTAGRP containing
The application receives SQLCODE -30020 and
no data and a null SQLCAGRP, indicating that the
SQLSTATE 58009.
SQL SELECT operation was successful. This is an
inconsistency.
Operator response
The application will receive SQLCODE -30000 and report the problem. For information about identifying
SQLSTATE 58008. and reporting the problem, see Collecting diagnostic
Operator response
Analyze the statistics class 4 trace record identified by
the IFCID sequence number included in the DSNL031I
message.
items:
data (Collecting data). • Statistics Class 4 trace record for the LUWID
IFCID sequence number enumerated in the DSNL031I Explanation
Db2 detected an error in the DDM reply message
Collect the following diagnostic items at this local Db2. received from the application server (AS) in response
to a DDM command. The DDM minimum level attribute
of the reply message (that is, the level of DDM required
to support the reply message) exceeds the DDM level
Collect the following diagnostic items at the remote of the AS specified during CONNECT processing.
server.
• Relevant error and system logs spanning the time of System action
the failure.
• Any relevant remote server trace information or written to the console. Refer to the description of this
dumps. message for further information.
00D35118 The application received SQLCODE -30020 and
SQLSTATE 58009.
Explanation
Db2 detected an error in the DDM reply data object
Operator response
received from the application server (AS) in response Notify the system programmer.
to a DDM command. The DDM minimum level attribute
of the reply data object (that is, the level of DDM
required to support the object) exceeds the DDM level
of the AS specified during CONNECT processing. If you suspect an error in Db2, you might need to

Analyze the statistics class 4 trace record identified
by the IFCID sequence number given in message
Problem determination DSNL031I.
Analyze the statistics class 4 trace record identified by At the Db2 requester, collect the following diagnostic
the IFCID sequence number included in the DSNL031I items:
message.
• Statistics Class 4 trace record for the LUWID • Statistics Class 4 trace record for the LUWID
associated with the failing request. associated with the failing request.
At this remote server, collect the following diagnostic If the DRDA server is Db2 for z/OS, then Db2
items: diagnostic information is available. In this case, at the
• Console output from the system on which the job Db2 server, collect the following diagnostic items:
was run, and a listing of the SYSLOG data set for the • Console output from the system on which the job
period of time that spans the failure. was run, and a listing of the SYSLOG data set for the
• All dumps taken by the attachment facility or period of time that spans the failure.
requesting application. 00D3511B
00D3511A
Explanation
Explanation Db2 has detected an error in the DRDA summary
Db2 has detected an error in the DRDA summary component received from the remote server in
component received from the remote server in response to a DDM EXCSQLSTT command that
response to a DDM EXCSQLSTT command that generated query result sets. The DRDA summary
generated query result sets. The DRDA summary component should consist of the DDM RSLSETRM
component should consist of the DDM RSLSETRM reply message, a DDM SQLCARD or SQLDTARD reply
reply message, a DDM SQLCARD or SQLDTARD reply data object, and a DDM SQLRSLRD reply data object.
data object, and a DDM SQLRSLRD reply data object. The SQLRSLRD object is not contained in the summary
Neither the SQLCARD nor the SQLDTARD is contained component.
in the summary component.
System action
System action An alert is generated and message DSNL031I is
An alert is generated and message DSNL031I is written to the console. Refer to the description of this
written to the console. Refer to the description of this message for further information.
message for further information. The application will receive SQLCODE -30020 and
The application will receive SQLCODE -30020 and SQLSTATE 58009.
SQLSTATE 58009.
Operator response

Analyze the statistics class 4 trace record identified Analyze the statistics class 4 trace record identified
by the IFCID sequence number given in message by the IFCID sequence number given in message
DSNL031I. DSNL031I.
At the Db2 requester, collect the following diagnostic At the Db2 requester, collect the following diagnostic
items: items:
• Console output from the system on which the job • Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the was run, and a listing of the SYSLOG data set for the
period of time that spans the failure. period of time that spans the failure.
If the DRDA server is Db2 for z/OS, then Db2 If the DRDA server is Db2 for z/OS, then Db2
diagnostic information is available. In this case, at the diagnostic information is available. In this case, at the
Db2 server, collect the following diagnostic items: Db2 server, collect the following diagnostic items:
00D3511C 00D3511D
Db2 has detected an error in the DRDA summary Db2 has detected an error in the DRDA summary
component received from the remote server in component or the DRDA result set component
response to a DDM EXCSQLSTT command that received from the remote server in response to a DDM
generated query result sets. The DRDA summary EXCSQLSTT command that generated query result
component should consist of the DDM RSLSETRM sets. The DRDA summary component should consist of
reply message, a DDM SQLCARD or SQLDTARD reply the DDM RSLSETRM reply message, a DDM SQLCARD
data object, and a DDM SQLRSLRD reply data object. or SQLDTARD reply data object, and a DDM SQLRSLRD
The SQLRSLRD reply data object was not preceded by reply data object. The DRDA result set component
the RSLSETRM reply message. should consist of at least the DDM OPNQRYRM reply
message and the DDM QRYDSC reply data object.
System action The OPNQRYRM message is not present following the
SQLRSLRD object.
System action
SQLSTATE 58009.
Operator response The application will receive SQLCODE -30020 and

SQLSTATE 58009.
Operator response

Analyze the statistics class 4 trace record identified The statistics class 4 trace record identified by
by the IFCID sequence number given in message the IFCID sequence number enumerated in the
DSNL031I. DSNL031I message should be analyzed. For the Db2
system generating the DSNL031I message, collect the
At the Db2 requester, collect the following diagnostic
items:
period of time that spans the failure. In addition, identify all connected systems
• Statistics Class 4 trace record for the LUWID participating in the processing of the remote request.
associated with the failing request. This includes the requester system to which the
If the DRDA server is Db2 for z/OS, then Db2 the target of the remote request. This may also include
diagnostic information is available. In this case, at the intermediate server systems. For each system that is a
Db2 server, collect the following diagnostic items: Db2 system, collect the following diagnostic items:
• Console output from the system on which the job • Console output and the listing of the SYSLOG data
was run, and a listing of the SYSLOG data set for the set from each connected site for the period of time
period of time that spans the failure. spanning the failure.
00D3511E For non-Db2 systems, refer to the references specific
to those products.
Explanation If any dumps were generated on any Db2 system
Db2 has detected an error in the DDM QRYDTA reply participating in processing the remote request, collect
data object received in response to a DDM OPNQRY the following diagnostic items:
or CNTQRY command. The SQL operation is a FETCH • Listings of the SYS1.LOGREC data set, obtained by
and the size of the QRYDTA object, exceeds 32KB. The executing IFCEREP1 at each connected site.
DDM length field required to support this is invalid.
00D3511F
requester system. Explanation
System action or DDM reply data object received from the remote
object is a MGRLVLOVR collection signaling a remote
server change in DRDA manager levels. The DDM
object length is invalid.
SQLSTATE 58008.
Operator response requester system.
System action
System programmer response An alert is generated and message DSNL031I is
If you suspect an error in Db2, you might need to written to the console. Refer to the description of this
report the problem. For information about identifying message for further information.
and reporting the problem, see Collecting diagnostic The application will receive SQLCODE -30000 and
data (Collecting data). SQLSTATE 58008.
Operator response

If you suspect an error in Db2, you might need to An alert is generated and message DSNL031I is
report the problem. For information about identifying written to the console. Refer to the description of this
and reporting the problem, see Collecting diagnostic message for further information.
SQLSTATE 58008.
The statistics class 4 trace record identified by Operator response
DSNL031I message should be analyzed. For the Db2
following diagnostic items: System programmer response
• Statistics Class 4 trace record for the LUWID If you suspect an error in Db2, you might need to
associated with the failing request. report the problem. For information about identifying
In addition, identify all connected systems
participating in the processing of the remote request.
This includes the requester system to which the
application is connected and the data server which is Problem determination
the target of the remote request. This may also include The statistics class 4 trace record identified by
intermediate server systems. For each system that is a the IFCID sequence number enumerated in the
Db2 system, collect the following diagnostic items: DSNL031I message should be analyzed. For the Db2
• Console output and the listing of the SYSLOG data system generating the DSNL031I message, collect the
set from each connected site for the period of time following diagnostic items:
spanning the failure. • Statistics Class 4 trace record for the LUWID
For non-Db2 systems, refer to the references specific associated with the failing request.
to those products. In addition, identify all connected systems
If any dumps were generated on any Db2 system participating in the processing of the remote request.
participating in processing the remote request, collect This includes the requester system to which the
the following diagnostic items: application is connected and the data server which is
• Listings of the SYS1.LOGREC data set, obtained by intermediate server systems. For each system that is a
executing IFCEREP1 at each connected site. Db2 system, collect the following diagnostic items:
00D35120 set from each connected site for the period of time
Explanation For non-Db2 systems, refer to the references specific
to those products.
Db2 has detected an error in the DDM TYPDEFOVR
reply data object received from the remote server in If any dumps were generated on any Db2 system
response to a DDM command, signaling a change in participating in processing the remote request, collect
the remote server CCSIDs. The TYPDEFOVR contains the following diagnostic items:
multiple occurrences of the CCSIDXML scalar (XML
CCSID). This is an error. The CCSIDXML (XML CCSID)
code point is invalid.
application or may be acting as an intermediate DRDA 00D35121
requester system. Explanation
that was received in response to a DDM EXSQLSTT,
OPNQRY, or CNTQRY command. The SQL operation is
a FETCH and the DDM object is a streamed object,

but is not a QRYDTA object. Db2 might be acting as Related information
a requester system for a local application or as an DSNL031I (Db2 Messages)
intermediate DRDA system for a remote application on -30020
another DRDA requester system. EXECUTION FAILED DUE TO A DISTRIBUTION
PROTOCOL ERROR THAT CAUSED
System action DEALLOCATION OF THE CONVERSATION:
REASON reason-code (sub-code)
written to the console. 00D35122
SQLSTATE 58009. Explanation
Operator response that was received in response to a DDM EXSQLSTT,
Notify the system programmer. OPNQRY, or CNTQRY command. The SQL operation is a
FETCH and the DDM object is a streamed object, but is
not the only object in the OBJDSS. Db2 might be acting
System programmer response as a requester system for a local application or as an
If you suspect an error in Db2, you might need to intermediate DRDA system for a remote application on
report the problem. For information about identifying another DRDA requester system.
Problem determination written to the console.
• Analyze the statistics class 4 trace record that is The application receives SQLCODE -30020 and
identified by the IFCID sequence number that is SQLSTATE 58009.
enumerated in the DSNL031I message. For the Db2
system generating the DSNL031I message, collect
the following diagnostic items: Operator response
– Statistics Class 4 trace record for the LUWID that Notify the system programmer.
is associated with the failing request.
• Identify all connected systems that are participating System programmer response
in the processing of the remote request, including:
– The requester system to which the application is report the problem. For information about identifying
connected and reporting the problem, see Collecting diagnostic
– The data server that is the target of the remote data (Collecting data).
request
– Any intermediate server systems Problem determination
For each system that is a Db2 system, collect the • Analyze the statistics class 4 trace record that is
following diagnostic items: identified by the IFCID sequence number that is
enumerated in the DSNL031I message. For the Db2
– The console output and the listing of the SYSLOG system generating the DSNL031I message, collect
data set from each connected site for the period of the following diagnostic items:
time spanning the failure.
– Statistics Class 4 trace record for the LUWID that
• For non-Db2 systems, refer to the references is associated with the failing request.
specific to those products.
• Identify all connected systems that are participating
• If any dumps were generated on any Db2 system in the processing of the remote request, including:
that is participating in processing the remote
request, collect the following diagnostic items: – The requester system to which the application is
connected
– The listings of the SYS1.LOGREC data set,
obtained by executing IFCEREP1 at each – The data server that is the target of the remote
connected site. request
– All dumps generated by this failure. – Any intermediate server systems

For each system that is a Db2 system, collect the Problem determination
– The console output and the listing of the SYSLOG IFCID sequence number included in the DSNL031I
data set from each connected site for the period of message should be analyzed.
time spanning the failure.
• For non-Db2 systems, refer to the references
specific to those products. • Statistics class 4 trace record identified by the IFCID
• If any dumps were generated on any Db2 system
that is participating in processing the remote Collect the following diagnostic items at the remote
request, collect the following diagnostic items: server.
– The listings of the SYS1.LOGREC data set, • Relevant error and system logs spanning the time of
obtained by executing IFCEREP1 at each the failure.
connected site. • Any relevant remote server trace information or
– All dumps generated by this failure. dumps.
Related information 00D35201
-30020 Explanation
EXECUTION FAILED DUE TO A DISTRIBUTION
PROTOCOL ERROR THAT CAUSED Db2 has detected an error in the DDM reply message
DEALLOCATION OF THE CONVERSATION: or DDM reply data object received from the remote
REASON reason-code (sub-code) server in response to a DDM command. The DDM
object is the FDODSC element of an SQLDTARD. The
00D351FF size of the FDODSC is greater than 32KB and the DDM
level 6b extended length field is invalid.
Explanation
System action
Db2 received a DDM reply message from the remote
server in response to a DDM command. The reply An alert is generated and message DSNL031I is
message, while valid for the DDM command, indicates written to the console. Refer to the description of this
that the DDM command and hence the SQL statement message for further information.
was not successfully processed. The application The application will receive SQLCODE -30000 and
is notified of the failure through the architected SQLSTATE 58008.
SQLCODE (-300xx) and associated SQLSTATE.
Operator response
System action

items:

At this remote server, collect the following diagnostic • All dumps taken by the attachment facility or
items: requesting application.
Explanation
requesting application. Db2 has detected an error in the QRYDSC or
SQLDTARD reply data object received in response to
00D35202 an OPNQRY or EXCSQLSTT DDM command. The DDM
object is either a QRYDSC or the FDODSC scalar of
Explanation the SQLDTARD collection. The FDOCA geometry is
incorrect. The SQLCADTA row triplet (RLO) is either
Db2 has detected an error in the QRYDSC or invalid or has not been included with the SQLDTARD
SQLDTARD reply data object received in response to descriptor.
an OPNQRY or EXCSQLSTT DDM command. The DDM
object is either a QRYDSC or the FDODSC scalar of
the SQLDTARD collection. The FDOCA geometry is
System action
incorrect. The SQLCADTA row (RLO) MDD is either An alert is generated and message DSNL031I is
invalid or has not been included within the SQLDTARD written to the console. Refer to the description of this
descriptor. The descriptor is invalid. message for further information.
SQLSTATE 58008.
Operator response The statistics class 4 trace record identified by the
Notify the system programmer. message should be analyzed.
System programmer response items:
If you suspect an error in Db2, you might need to • Statistics Class 4 trace record for the LUWID
report the problem. For information about identifying associated with the failing request.
data (Collecting data). At this remote server, collect the following diagnostic
items:
The statistics class 4 trace record identified by the period of time that spans the failure.
items: 00D35204

Explanation
Db2 has detected an error in the QRYDSC or
SQLDTARD reply data object received in response to
items:
• Console output from the system on which the job object is either a QRYDSC or the FDODSC scalar of
was run, and a listing of the SYSLOG data set for the the SQLDTARD collection. The FDOCA geometry is
period of time that spans the failure. incorrect. Either the first component of the SQLCADTA
row is other than an SQLCAGRP (early) group or the

number of elements taken from the SQLCAGRP or of the SQLCAGRP; however, the second component,
SQLCAGRP replication factor (or both) are incorrect. identifying the SQLDTAGRP (late) group is incorrect.
The descriptor is invalid. The DDM object is either a Either the SQLDTAGRP local identifier (LID) is
QRYDSC or the FDODSC element of the SQLDTARD different than the LID of the SQLDTAGRP previously
collection. The FDOCA geometry is incorrect. The first specified or the number of elements taken from the
elements of the row are other than the elements of the SQLDTAGRP replication factor (or both) are incorrect.
early SQLCAGRP. The descriptor is invalid. The descriptor is invalid. The DDM object is either a
QRYDSC or the FDODSC element of the SQLDTARD
System action collection. The FDOCA geometry is incorrect. The first
elements of the row correctly enumerate the elements
An alert is generated and message DSNL031I is of the early SQLCAGRP, however, the local identifier
written to the console. Refer to the description of this (LID) following the SQLCAGRP LID is different than the
message for further information. LID of the SQLDTAGRP group previously specified. The
descriptor is invalid.
SQLSTATE 58008.
System action
Operator response An alert is generated and message DSNL031I is
System programmer response The application will receive SQLCODE -30000 and
SQLSTATE 58008.
Operator response

The statistics class 4 trace record identified by the If you suspect an error in Db2, you might need to
IFCID sequence number enumerated in the DSNL031I report the problem. For information about identifying
message should be analyzed. and reporting the problem, see Collecting diagnostic
items:
associated with the failing request. The statistics class 4 trace record identified by the
items:
items:
period of time that spans the failure. • Statistics Class 4 trace record for the LUWID
• All dumps taken by the attachment facility or associated with the failing request.
requesting application. At this remote server, collect the following diagnostic
00D35205 items:
SQLDTARD reply data object received in response
to an OPNQRY or EXCSQLSTT DDM command. The
DDM object is either a QRYDSC or the FDODSC 00D35206
scalar of the SQLDTARD collection. The FDOCA
geometry is incorrect. The first component of the
SQLCADTA row correctly enumerates the elements

Explanation • All dumps taken by the attachment facility or
SQLDTARD reply data object received in response to 00D35207
object is either a QRYDSC or the FDODSC scalar of Explanation
the SQLDTARD collection. The FDOCA geometry is
incorrect. One or more late environmental descriptors Db2 has detected an error in the QRYDSC or
is included within the previously specified SQLDTAGRP SQLDTARD reply data object received in response to
late group descriptor. However, SQLDTARD row (RLO) an OPNQRY or EXCSQLSTT DDM command. The DDM
Meta Data Definition (MDD) is either incorrect or has object is either a QRYDSC or the FDODSC scalar of
not been included within the SQLDTARD descriptor. the SQLDTARD collection. The FDOCA geometry is
The descriptor is invalid. The DDM object is either incorrect. Either the SQLDTARD is specified as other
a QRYDSC or the FDODSC scalar of the SQLDTARD than a row triplet (RLO) or the SQLDTARD RLO triplet
collection. The FDOCA geometry is incorrect. One length is invalid. The descriptor is invalid.
or more late environmental descriptors have been
included within the previously processed SQLDTAGRP System action
group. However, the Meta Data Definition (MDD) of the
SQLDTARD row (RLO) has not been included within the An alert is generated and message DSNL031I is
descriptor. The descriptor is invalid. written to the console. Refer to the description of this
SQLSTATE 58008.
SQLSTATE 58008.
items:
items: items:
was run, and a listing of the SYSLOG data set for the 00D35208

Db2 has detected an error in the QRYDSC or Db2 has detected an error in the QRYDSC or
SQLDTARD reply data object received in response to SQLDTARD reply data object received in response
an OPNQRY or EXCSQLSTT DDM command. The DDM to an OPNQRY or EXCSQLSTT DDM command. The
object is either a QRYDSC or the FDODSC scalar of DDM object is either a QRYDSC or the FDODSC scalar
the SQLDTARD collection. The FDOCA geometry is of the SQLDTARD collection. The FDOCA geometry
incorrect. Either the SQLCADTA LID referenced within is incorrect. Either the length is specified in the LL
the SQLDTARD RLO did not match the LID defined preceding the QRYDSC or FDODSC is greater than the
within the SQLCADTA RLO or the number of elements length of the OBJDSS carrier or the length of one of the
or replication factor (or both) within the SQLDTARD constituent geometries (triplet lengths) is inconsistent
RLO was non zero. The descriptor is invalid. with the length of the QRYDSC or FDODSC. The
descriptor is invalid.
System action
System action
written to the console. Refer to the description of this An alert is generated and message DSNL031I is
message for further information. written to the console. Refer to the description of this
If this Db2 is the AR for the thread, the DDM object
received is an SQLDTA or QRYDSC. The application will The application will receive SQLCODE -30000 and
receive SQLCODE -30000 and SQLSTATE 58008. If this SQLSTATE 58008.
Db2 is an remote server for the thread, the DDM object
received is SQLDTA. DSCINVRM will be returned to the Operator response
AR.
Operator response
items:
Collect the following diagnostic items at the local Db2.
items:
server.
• Relevant error and system logs spanning the time of period of time that spans the failure.
the failure. • All dumps taken by the attachment facility or
• Any relevant remote server trace information or requesting application.
dumps.
00D3520A
00D35209
Explanation
Db2 has detected an error in the SQLDTARD reply data
object received in response to an EXCSQLSTT DDM

command. The DDM object is the FDODSC scalar of the System action
SQLDTARD collection and is contained within multiple
DDM Level 6b OBJDSS carriers. The descriptor is An alert is generated and message DSNL031I is
invalid. The DDM object is the FDODSC scalar of the written to the console. Refer to the description of this
SQLDTARD collection. The SQLDTARD is contained in message for further information.
multiple level 6b object DSSs. The descriptor is invalid. The application will receive SQLCODE -30000 and
SQLSTATE 58008.
System action
An alert is generated and message DSNL031I is Operator response
written to the console. Refer to the description of this Notify the system programmer.
The application will receive SQLCODE -30000 and System programmer response
SQLSTATE 58008.

data (Collecting data). At this local Db2, collect the following diagnostic
items:
Problem determination • Statistics Class 4 trace record for the LUWID
IFCID sequence number enumerated in the DSNL031I At this remote server, collect the following diagnostic
message should be analyzed. items:
At this local Db2, collect the following diagnostic • Console output from the system on which the job
items: was run, and a listing of the SYSLOG data set for the
items: 00D3520C
• All dumps taken by the attachment facility or or DDM reply data object received from the remote
requesting application. server in response to a DDM command. The DDM
00D3520B object is a QRYDSC returned from an OPNQRY
command which spans multiple DDM level 6b object
DSSs. One or more of the DDM code points within
Explanation the containing object DSSs is (are) other than QRYDSC
Db2 has detected an error in the DDM reply message (X'241A'). The descriptor is invalid.
server in response to a DDM command. The DDM System action
object is a QRYDSC returned from an OPNQRY
command which spans multiple DDM level 6b DSSs. An alert is generated and message DSNL031I is
One or more of the containing level 6b DSSs is (are) written to the console. Refer to the description of this
other than an object (OBJ) DSS. The descriptor is message for further information.
invalid.

SQLSTATE 58008.

items:
items: 00D3520E
Db2 has detected an error in the DDM QRYDSC or
• All dumps taken by the attachment facility or the DDM SQLCINRD reply data object received from
requesting application. the remote server in response to a DDM EXCSQLSTT
00D3520D command that generated query result sets. The
number of columns described by the QRYDSC object
is inconsistent with the number of columns described
Explanation by the DDM SQLCINRD object.
Db2 has detected an error in the QRYDSC reply
data object received in response to an OPNQRY DDM System action
command. The QRYDSC contained in one or more
query blocks is incomplete, i.e., the entire QRYDSC An alert is generated and message DSNL031I is
has not been returned in response to the OPNQRY written to the console. Refer to the description of this
command. message for further information.

message for further information. Notify the system programmer.
SQLSTATE 58008. System programmer response

by the IFCID sequence number given in message At this remote server, collect the following diagnostic
DSNL031I. items:
At the Db2 requester, collect the following diagnostic • Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the • All dumps taken by the attachment facility or
period of time that spans the failure. requesting application.
• Statistics Class 4 trace record for the LUWID 00D35302

If the DRDA server is Db2 for z/OS, then Db2 Explanation
diagnostic information is available. In this case, at the Db2 has detected an error in the DDM reply message
Db2 server, collect the following diagnostic item: received from the remote server in response to a DDM
• Console output from the system on which the job command. The reply message contains one or more
was run, and a listing of the SYSLOG data set for the constituent instance variables whose code point is not
period of time that spans the failure. supported by DDM Level 3.
00D35301
System action
Explanation An alert is generated and message DSNL031I is
received from the remote server in response to a
DDM command. The reply message code point is not The application will receive SQLCODE -30000 and
supported by DDM Level 3. SQLSTATE 58008.

The application will receive SQLCODE -30000 and If you suspect an error in Db2, you might need to

message should be analyzed. • Console output from the system on which the job

• All dumps taken by the attachment facility or by DDM Level 3 as required for this reply message, is
requesting application. (are) not contained within the reply message.
00D35303
System action
command. The length of the reply message is greater The application will receive SQLCODE -30000 and
than the sum of the lengths of the constituent instance SQLSTATE 58008.
variables.
Operator response
Operator response
System programmer response IFCID sequence number enumerated in the DSNL031I
report the problem. For information about identifying At this local Db2, collect the following diagnostic
and reporting the problem, see Collecting diagnostic items:
The statistics class 4 trace record identified by the items:
At this local Db2, collect the following diagnostic period of time that spans the failure.
• Statistics Class 4 trace record for the LUWID requesting application.
associated with the failing request. 00D35305
items: Explanation
• Console output from the system on which the job Db2 has detected an error in the DDM reply message
was run, and a listing of the SYSLOG data set for the received from the remote server in response to a DDM
period of time that spans the failure. command. The length of the reply message exceeds
• All dumps taken by the attachment facility or the sum of the lengths of all the constituent instance
requesting application. variables.
00D35304
System action
command. One or more instance variables, specified

SQLSTATE 58008.

items:
items: 00D35307
• All dumps taken by the attachment facility or received from the remote server in response to a DDM
requesting application. command. The value of the DDM enumerated value
00D35306 instance variable, DTALCKST is other than TRUE (X'F1')
or FALSE (X'F0').
Explanation
System action
received from the remote server in response to a An alert is generated and message DSNL031I is
DDM command. The length of the RDBNAM instance written to the console. Refer to the description of this
variable is 18 bytes as specified by DDM Level 3, message for further information.
however, bytes 17 and 18 are non blank. Db2 supports The application will receive SQLCODE -30000 and
only a 16 byte RDBNAM. SQLSTATE 58008.


items: 00D35309

period of time that spans the failure. Db2 has detected an error in the ACCRDBRM reply
• All dumps taken by the attachment facility or message received from the remote server as in
requesting application. response to the ACCRDB command. The length of the
PRDID instance variable is invalid.
00D35308
System action
Explanation
Db2 has detected an error in the MGRLVLRM reply written to the console. Refer to the description of this
message received from the remote server in response message for further information.
to the EXCSAT DDM command. The MGRLVL specified
is not supported by Db2. Db2 supports the following The application will receive SQLCODE -30000 and
DDM Level 3 managers: CMNAPPC, SUPERVISOR, SQLSTATE 58008.
SECMGR, AGENT, DIRECTORY, SQLADM, and RDB.
Operator response
Operator response

00D3530A System action
Db2 has detected an error in the ACCRDBRM reply message for further information.
message received from the remote server in response The application will receive SQLCODE -30000 and
to ACCRDB DDM command. Db2 is currently disabled SQLSTATE 58017.
to connect to the server specified by the value of the
PRDID instance variable.
Operator response

message for further information. If you suspect an error in Db2, you might need to
Operator response
System programmer response message should be analyzed.
If you suspect an error in Db2, you might need to At this local Db2, collect the following diagnostic
report the problem. For information about identifying items:

items:
items:
associated with the failing request. 00D3530C

items:
Explanation
command. The value of the severity code (SVRCOD)
instance variable, as specified by DRDA, is not valid for
• All dumps taken by the attachment facility or this reply message.
00D3530B System action
Db2 has detected an error in the DDM reply message for further information.
message received from the remote server in response The application will receive SQLCODE -30000 and
to a DDM OPNQRY command. The value of the SQLSTATE 58008.
enumerated instance variable, QRYPRCTYP, is other
than SNGROWPRC or LMTBLKPRC.

If you suspect an error in Db2, you might need to IFCID sequence number enumerated in the DSNL031I
report the problem. For information about identifying message should be analyzed.
items:
items: 00D3530E

period of time that spans the failure. Db2 has detected an error in the ACCRDBRM reply
• All dumps taken by the attachment facility or message received from the remote server in response
requesting application. to the ACCRDB DDM command. The length of the
TYPDEFOVR instance variable, a collection, is different
00D3530D than the sum of the lengths of the constituent scalar
instance variables.
Explanation
Db2 has detected an error in the ACCRDBRM reply System action
message received from the remote server in response An alert is generated and message DSNL031I is
to ACCRDB DDM command. The DDM TYPDEFOVR written to the console. Refer to the description of this
instance variable, a collection, contains a scalar message for further information.
instance variable other than CCSIDSBC, CCSIDMBC or
CCSIDDBC. The application will receive SQLCODE -30000 and
SQLSTATE 58008.
System action
Operator response

items: 00D35310
period of time that spans the failure. Db2 has detected an error in the DDM reply message
• All dumps taken by the attachment facility or received from the remote server in response to a
requesting application. DDM command. The length of a DDM variable length
collection or scalar is different than that specified by
00D3530F
DDM Level 3.

command. The length of a DDM fixed length collection
or scalar is different than that specified by DDM Level
3. The application will receive SQLCODE -30000 and
SQLSTATE 58008.
System action
Operator response
items:
items: 00D35311

Db2 detected an error in the DDM reply message
received from the application server (AS) in response • All dumps created by this failure.
to a DDM EXCSQLIMM or EXCSQLSTT command. The 00D35312
AS DDM level specified during CONNECT is 4 and an
ENDUOWRM was returned signaling that a dynamic
COMMIT or ROLLBACK was performed. The correct Explanation
response from an AS supporting DDM Level 4 is the Db2 has detected an error in the DDM reply message
CMMRQSRM reply message. received from the remote server in response to a
DDM command. Either Db2 was expecting to receive
System action a SRVPRTY object and received an object other than
SRVPRTY, or Db2 was expecting to receive an IPADDR
An alert is generated and message DSNL031I is object and received an object other an IPADDR.
System action
SQLSTATE 58009. An alert is generated and message DSNL031I is
Operator response
Notify the system programmer. SQLSTATE 58008.

If you suspect an error in Db2, you might need to Notify the system programmer.
The statistics class 4 trace record identified by data (Collecting data).
system generating the DSNL031I message, collect the Problem determination
following diagnostic items: The statistics class 4 trace record identified by
• Statistics Class 4 trace record for the LUWID the IFCID sequence number enumerated in the
associated with the failing request. DSNL031I message should be analyzed. For the Db2
In addition, identify all connected systems following diagnostic items:
This includes the requester system to which the • Statistics Class 4 trace record for the LUWID
application is connected and the data server which is associated with the failing request.
the target of the remote request. This may also include In addition, identify all connected systems
intermediate server systems. For each system that is a participating in the processing of the remote request.
Db2 system, collect the following diagnostic items: This includes the requester system to which the
• Console output and the listing of the SYSLOG data application is connected and the data server which is
set from each connected site for the period of time the target of the remote request. This may also include
spanning the failure. intermediate server systems. For each system that is a
For non-Db2 systems, refer to the references specific
to those products. • Console output and the listing of the SYSLOG data
If any dumps were generated on any Db2 system spanning the failure.
the following diagnostic items: For non-Db2 systems, refer to the references specific
to those products.

If any dumps were generated on any Db2 system Explanation
the following diagnostic items: Db2 detected an error in the DDM reply message
• Listings of the SYS1.LOGREC data set, obtained by DDM command. The value of the QRYATTSNS instance
executing IFCEREP1 at each connected site. variable is not recognized for this command in DDM
• All dumps created by this failure. Level 6.
00D35313
System action
Explanation Db2 generates an alert, and writes message DSNL031I
to the console. Refer to the description of this message
Db2 has detected an error in the DDM reply message for further information.
DDM command. The value of the QRYATTUPD instance The application will receive SQLCODE -30000 and
variable is not recognized for this command in DDM SQLSTATE 58008.
Level 6.
Operator response
System action Notify the System Programmer.
Db2 generates an alert, and writes message DSNL031I
to the console. Refer to the description of this message System programmer response
for further information.
Operator response
Notify the System Programmer. Problem determination
System programmer response by the IFCID sequence number enumerated in the
DSNL031I message.
report the problem. For information about identifying If the DRDA requester is also a Db2 for z/OS system,
and reporting the problem, see Collecting diagnostic then at the requester Db2 system, collect the following
data (Collecting data). diagnostic items:
Analyze the statistics class 4 trace record identified At this remote server, collect the following diagnostic
by the IFCID sequence number enumerated in the items:
DSNL031I message. • All dumps taken by the attachment facility or
If the DRDA requester is also a Db2 for z/OS system, requesting application.
then at the requester Db2 system, collect the following 00D35315
diagnostic items:
• Statistics Class 4 trace record for the LUWID Explanation
At this remote server, collect the following diagnostic received from the remote server in response to a DDM
items: command. The received value for the DDM instance
• All dumps taken by the attachment facility or variable QRYATTSCR is other than TRUE (X'F1') or
requesting application. FALSE (X'F0'). The value is not supported.
00D35314

System action variable QRYATTSET is other than TRUE (X'F1') or
FALSE (X'F0'). The value is not supported.
message for further information. System action
The application will receive SQLCODE -30000 and An alert is generated and message DSNL031I is
SQLSTATE 58008. written to the console. Refer to the description of this
Operator response The application will receive SQLCODE -30000 and
SQLSTATE 58008.
Operator response
and reporting the problem, see Collecting diagnostic System programmer response
DSNL031I message should be analyzed. For the Db2 Problem determination
system generating the DSNL031I message, collect the The statistics class 4 trace record identified by
following diagnostic items: the IFCID sequence number enumerated in the
• Statistics Class 4 trace record for the LUWID DSNL031I message should be analyzed. For the Db2
associated with the failing request. system generating the DSNL031I message, collect the
participating in the processing of the remote request. • Statistics Class 4 trace record for the LUWID
This includes the requester system to which the associated with the failing request.
application is connected and the data server which is In addition, identify all connected systems
the target of the remote request. This may also include participating in the processing of the remote request.
intermediate server systems. For each system that is a This includes the requester system to which the
Db2 system, collect the following diagnostic items: application is connected and the data server which is
• Console output and the listing of the SYSLOG data the target of the remote request. This may also include
set from each connected site for the period of time intermediate server systems. For each system that is a
spanning the failure. Db2 system, collect the following diagnostic items:
For non-Db2 systems, refer to the references specific • Console output and the listing of the SYSLOG data
to those products. set from each connected site for the period of time
participating in processing the remote request, collect For non-Db2 systems, refer to the references specific
the following diagnostic items: to those products.
• Listings of the SYS1.LOGREC data set, obtained by If any dumps were generated on any Db2 system
executing IFCEREP1 at each connected site. participating in processing the remote request, collect
Explanation
00D35401
command. The received value for the DDM instance

Db2 detected an error in the DDM SQLCARD reply data If you suspect an error in Db2, you might need to
object received from the remote server in response to report the problem. For information about identifying
a DDM command. The object contains nonzero lengths and reporting the problem, see Collecting diagnostic
for both the SQLERRMSG_m and SQLERRMSG_s data (Collecting data).
elements as described by the SQLCAXGRP early group
descriptor. This is invalid as specified by DRDA. Problem determination
System action
An alert is generated and message DSNL031I is message should be analyzed.
items:
SQLSTATE 58008.
Operator response At this remote server, collect the following diagnostic

items:
If you suspect an error in Db2, you might need to • All dumps taken by the attachment facility or
report the problem. For information about identifying requesting application.
00D35502

Db2 has detected an error in the DDM SQLDARD
by the IFCID sequence number identified in the
in response to a DDM PRPSQLSTT command. Within
DSNL031I message.
one or more SQLDAROW occurrences, either (a)
00D35501 the lengths of SQLNAME_m and SQLNAME_s are
both non-0, or (b) the lengths of SQLLABEL_m and
SQLLABEL_s are both non-0, or (c) the lengths of
Explanation
SQLCOMMENTS_m and SQLCOMMENTS_s are both
Db2 has detected an error in the DDM SQLDARD non-0. The data is invalid with regard to the Early
reply data object received from the remote server in SQLDAGRP group descriptor as defined by DRDA.
response to a DDM PRPSQLSTT command. The value
of the single element of the SQLNUMGRP, SQLNUM, System action
defining the total number of SQLDAROW occurrences
within the SQLDARD array, is either negative or is An alert is generated and message DSNL031I is
inconsistent with the size of the SQLDARD array. written to the console. Refer to the description of this
SQLSTATE 58008.
SQLSTATE 58008.

The statistics class 4 trace record identified by the data (Collecting data).
message should be analyzed. Problem determination
At this local Db2, collect the following diagnostic The statistics class 4 trace record identified by the
items: IFCID sequence number enumerated in the DSNL031I
• Statistics Class 4 trace record for the LUWID message should be analyzed.
associated with the failing request. At this local Db2, collect the following diagnostic
At this remote server, collect the following diagnostic items:
items: • Statistics Class 4 trace record for the LUWID
• Console output from the system on which the job associated with the failing request.
was run, and a listing of the SYSLOG data set for the At this remote server, collect the following diagnostic
period of time that spans the failure. items:
Explanation requesting application.
Db2 has detected an error in command data received 00D35602

from a local Db2, or reply data received from the
remote server in response to a DDM command. The Explanation
command or reply data is described by either an
FDOCA early or late descriptor. Any Late descriptors Db2 has detected an error in a SQLSTT, SQLSTTVRB,
have been previously validated. The data currently SQLOBJNAM or SQLDTA data object received from
being retrieved from the data stream is described by a local Db2. The length of the data to be retrieved
a simple data Array (SDA) defining variable length data from the data stream is defined by an SDA which is
whose length is given by a 2 byte length field. The part of an early or late descriptor. The length exceeds
value of the length field is either negative or greater the length of remainder of the OBJDSS carrier of the
than the maximum length specified by the SDA. The command data object. The data is inconsistent with
data is inconsistent with the descriptor. the descriptor.

An alert is generated and message DSNL031I is An alert is generated and message DSNL032I is
written to the console. Refer to the description of this written to the console. Refer to the description of this
message for further information. message for further information.
If the error occurs within reply data, then the A DDM DTAMCHRM reply message will be returned to
application will receive SQLCODE -30000 and the AR.
SQLSTATE 58008. If the error occurs within command
data, a DDM DTAMCHRM reply message will be Operator response
returned to the AR.
Operator response

The statistics class 4 trace record identified by the The statistics class 4 trace record identified by the
IFCID sequence number enumerated in the DSNL032I IFCID sequence number enumerated in the DSNL031I
message should be analyzed. message should be analyzed.
At this local Db2, collect the following diagnostic At this local Db2, collect the following diagnostic
items: items:
At this remote server, collect the following diagnostic At this remote server, collect the following diagnostic
items: items:
• All dumps taken by the attachment facility or • All dumps taken by the attachment facility or
requesting application. requesting application.
00D35603 00D35604
Db2 has detected an error in SQLCARD, SQLDARD, Db2 has detected an error in SQLCARD, SQLDARD, or
or SQLDTARD reply data object received from an SQLDTARD reply data object received from an remote
remote server in response to a DDM command. The server in response to a DDM command. The reply data
reply data is described by either the SQLCAGRP is described by either the SQLCAGRP or SQLDAGRP
or SQLDAGRP early descriptors or the SQLDTAGRP early descriptors or the SQLDTAGRP (contained within
(contained within a SQLDTARD) late descriptor. The a SQLDTARD) late descriptor. The length of the data
length of the data to be retrieved is specified to be retrieved is specified by the default length of a
by the default length of a constituent SDA within constituent SDA within the SQLCAGRP or SQLDAGRP
the SQLCAGRP or SQLDAGRP early groups or the early groups or the SDA length specification within
SDA length specification within the SQLDTAGRP late the SQLDTAGRP late group. The carrier OBJDSS has
group. All OBJDSSs received in response to the DDM been exhausted but the complete object has not been
command have been processed but the SQLCARD, assembled. The object must be contained in exactly
SQLDARD, or SQLDTARD is incomplete. These must be one OBJDSS carrier. This is not the case and the data
returned in their entirety. The data is inconsistent with is inconsistent with the descriptor.
the descriptor.
System action
System action
The application will receive SQLCODE -30000 and SQLSTATE 58008.
SQLSTATE 58008.
Operator response
Operator response

items:
items: items:
requesting application. Db2 has detected an error in a QRYDTA reply data
00D35605 object received from the remote server in response to
a DDM OPNQRY or CNTQRY command. The reply data,
described by an SQLDTARD late descriptor carried in
Explanation a DDM QRYDSC reply data object, has been previously
Db2 has detected an error in a QRYDTA reply data validated. The reply data spans multiple query blocks,
object received from the remote server in response to each of which are contained in a level 6b Object DSS
a DDM OPNQRY or CNTQRY command. The reply data, (OBJDSS). The code points of one or more of the DDM
described by an SQLDTARD late descriptor carried in reply data objects is other than QRYDTA (X'241B').
a DDM QRYDSC reply data object, has been previously This is invalid.
validated. The reply data spans multiple query blocks,
each of which are contained in a level 6b DSS. One or System action
more of the containing level 6b DSSs is other than a
DDM level 6b object DSS. This is invalid. An alert is generated and message DSNL031I is
System action
An alert is generated and message DSNL031I is SQLSTATE 58008.
Operator response
SQLSTATE 58008. Notify the system programmer.

Notify the system programmer. If you suspect an error in Db2, you might need to
data (Collecting data). The statistics class 4 trace record identified by the
message should be analyzed. • Statistics Class 4 trace record for the LUWID

At this remote server, collect the following diagnostic Explanation
items:
Db2 has detected an error in a QRYDTA reply data
• Console output from the system on which the job object received from the remote server in response to
was run, and a listing of the SYSLOG data set for the a DDM OPNQRY or CNTQRY command. The reply data,
period of time that spans the failure. described by an SQLDTARD late descriptor carried in a
• All dumps taken by the attachment facility or DDM QRYDSC reply data object, has been previously
requesting application. validated. The current data to be retrieved from
the QRYDTA is described by an SDA defining Null-
00D35607 Terminated data (DRDA types X'2C', X'2D', X'2E', X'2F',
X'42' or X'43'). The null terminator cannot be located
Explanation within the reply data. The data is inconsistent with the
descriptor defined by the QRYDSC.
Db2 has detected an error in a QRYDTA reply data
object received from a remote server in response
to a DDM OPNQRY or CNTQRY. The cursor is being System action
processed with single row protocols (SNGROWPRC). An alert is generated and message DSNL031I is
The QRYDTA may span multiple query blocks but must written to the console. Refer to the description of this
be returned in its entirety. This is not the case. message for further information.
SQLSTATE 58008.
Collect the following diagnostic items at this local Db2. items:
• Statistics class 4 trace record identified by the IFCID • Console output from the system on which the job
sequence number specified in message DSNL031I. was run, and a listing of the SYSLOG data set for the
Collect the following diagnostic items at the remote period of time that spans the failure.
server. • All dumps taken by the attachment facility or
• Relevant error and system logs spanning the time of requesting application.
the failure. 00D35609
• Any relevant remote server trace information or
dumps.
00D35608

Db2 detected an error in conversion of numeric Db2 has detected an error in command data received
data. Possible scenarios are: floating point conversion from a remote requester, or reply data received from
overflow, or digits of numeric character out of range. the remote server in response to a DDM command.
The command or reply data is described by either an
System action FDOCA early or late descriptor. Any late descriptors
have been previously validated. The data currently
An alert is generated and message DSNL031I is being retrieved from the data stream is described by
written to the console. Refer to the description of this a simple data array (SDA) defining variable length data
message for further information. whose length is given by a 4 bytes length field. The 4
bytes length field is incomplete and split across more
than one object. The length field is invalid.
SQLSTATE 58017.

An alert is generated and message DSNL031I (if the
error is detected by Db2 acting as a requester) or
message DSNL032I (if the error is detected by Db2
acting as a server) is written to the console. Refer to
the description of this message for further information.
User response
Operator response
Check your numeric data. If you are connecting to
Db2 via a non-S/370 type machine, overflow can occur
when the floating point value is out of the System/370
floating point range. System programmer response
DSNL031I.
items: Analyze the statistics class 4 trace record identified
DSNL031I or DSNL032I message.
period of time that spans the failure. For the Db2 system generating the DSNL031I or
• All dumps taken by the attachment facility or DSNL032I message, collect the following diagnostic
requesting application. items:
Related concepts • Statistics Class 4 trace record for the LUWID

Decimal floating-point (DECFLOAT) (Db2 SQL)
Double precision floating-point (DOUBLE or In addition, identify all connected systems
FLOAT) (Db2 SQL) participating in the processing of the remote request.
Single precision floating-point (REAL) (Db2 SQL) This includes the requester system to which the
Related information
DSNL031I (Db2 Messages) intermediate server systems. For each system that is a
-30073 Db2 system, collect the following diagnostic items:
parameter subcode PARAMETER VALUE NOT
SUPPORTED ERROR • Console output and the listing of the SYSLOG data
00D35610 spanning the failure.

If any dumps were generated on any Db2 system application is connected and the data server which is
participating in processing the remote request, collect the target of the remote request. This may also include
the following diagnostic items: intermediate server systems. For each system that is a
executing IFCEREP1 at each connected site. • Console output and the listing of the SYSLOG data
• All dumps created by this failure. set from each connected site for the period of time
00D35611
Explanation
Db2 has detected an error in command data received participating in processing the remote request, collect
from a remote requester, or reply data received from the following diagnostic items:
the remote server in response to a DDM command.
The command or reply data is described by either an • Listings of the SYS1.LOGREC data set, obtained by
FDOCA early or late descriptor. Any Late descriptors executing IFCEREP1 at each connected site.
have been previously validated. The data currently • All dumps created by this failure.
being retrieved from the data stream is described by
00D35701
a simple data Array (SDA) defining variable length data
whose length is given by a 4 bytes length field. The
value of the length field is either negative or greater Explanation
than the maximum length specified by the SDA. The
Db2 has detected an error while processing
data is inconsistent with the descriptor.
the SQLDTAGRP late group descriptor, contained
within either the DRDA SQLDTARD or SQLDTA
System action late descriptors. The DDM object is either a
QRYDSC, SQLDTARD or SQLDTA. The FDOCA geometry
is incorrect. The late descriptor includes late
environmental descriptors and the SQLDTAGRP meta
message DSNL032I (if the error is detected by Db2
data definition (MDD) is either invalid or has not
been included within the descriptor. The descriptor is
invalid.
Operator response
System action
System programmer response message for further information.
If you suspect an error in Db2, you might need to If the error occurs within the QRYDSC or SQLDTARD
report the problem. For information about identifying DDM objects, the application will receive SQLCODE
and reporting the problem, see Collecting diagnostic -30000 and SQLSTATE 58008. If the error occurs
data (Collecting data). within the DDM SQLDTA object, a DSCINVRM reply
message will be returned to the AR.
Operator response
by the IFCID sequence number enumerated in the Notify the system programmer.
DSNL031I or DSNL032I message.
For the Db2 system generating the DSNL031I or System programmer response
items:
• Statistics Class 4 trace record for the LUWID and reporting the problem, see Collecting diagnostic
associated with the failing request. data (Collecting data).

items:
items: items:
requesting application. Db2 has detected an error while processing
00D35702 the SQLDTAGRP late group descriptor, contained
within either the DRDA SQLDTARD or SQLDTA late
descriptors. The DDM object is either a QRYDSC,
Explanation SQLDTARD or SQLDTA. The FDOCA geometry is
Db2 has detected an error while processing incorrect. The local identifier (LID) of one of
the SQLDTAGRP late group descriptor, contained the SQLDTAGRP constituent triplets has not been
within either the DRDA SQLDTARD or SQLDTA late previously defined by a late environmental descriptor
descriptors. The DDM object is either a QRYDSC, and the LID is outside of the bounds of the default
SQLDTARD or SQLDTA. The FDOCA geometry is environmental descriptor LIDs (LID > X'49'). Note that
incorrect. The SQLDTAGRP triplet is not defined as an the default LIDs are identical to the DRDA types. The
FDOCA nullable group. The descriptor is invalid. descriptor is invalid.

If the error occurs within the QRYDSC or SQLDTARD If the error occurs within the QRYDSC or SQLDTARD
DDM objects, the application will receive SQLCODE DDM objects, the application will receive SQLCODE
-30000 and SQLSTATE 58008. If the error occurs -30000 and SQLSTATE 58008. If the error occurs
within the DDM SQLDTA object, a DSCINVRM reply within the DDM SQLDTA object, a DSCINVRM reply
message will be returned to the AR. message will be returned to the AR.




items: items:
items: items:
00D35704 00D35705
Db2 has detected an error while processing Db2 has detected an error while processing
the SQLDTAGRP late group descriptor, contained the SQLDTAGRP late group descriptor contained
within either the DRDA SQLDTARD or SQLDTA late within either the DRDA SQLDTARD or SQLDTA late
descriptors. The DDM object is either a QRYDSC, descriptors. The DDM object is either a QRYDSC,
SQLDTARD or SQLDTA. The FDOCA geometry is SQLDTARD reply data object, or the SQLDTA command
incorrect. The local identifier (LID) of one of the data object. The FDOCA geometry is incorrect. All
constituent SQLDTAGRP SDAs has either not been the OBJDSS carriers have been processed and
previously defined by a late environmental descriptor, the SQLDTAGRP has not been assembled. The
or is not a valid default LID. Note that the default SQLDTAGRP is incomplete and the descriptor is
LIDs are identical to the DRDA types. The descriptor invalid.
is invalid.
System action
System action
If the error occurs within the QRYDSC or SQLDTARD
An alert is generated and message DSNL031I is reply data object, the application will receive SQLCODE
written to the console. Refer to the description of this -30000 and SQLSTATE 58008. If the error occurs
message for further information. within the DDM SQLDTA object, a DSCINVRM reply
message will be returned to the local Db2.
DDM objects, the application will receive SQLCODE
-30000 and SQLSTATE 58008. If the error occurs Operator response
within the DDM SQLDTA object, a DSCINVRM reply

Operator response
Collect the following diagnostic item at this local Db2:

Collect the following diagnostic items at the remote System programmer response
server:
• Relevant error and system logs spanning the time of report the problem. For information about identifying
the failure. and reporting the problem, see Collecting diagnostic
• Any relevant remote server trace information or data (Collecting data).
dumps.
Related concepts Problem determination
Diagnostic aids for distributed data (Diagnosing The statistics class 4 trace record identified by the
Db2 problems) IFCID sequence number enumerated in the DSNL031I
Related tasks message should be analyzed.
Collecting data for distributed data facility At this local Db2, collect the following diagnostic
problems (Collecting data) items:
Related reference
SQLSTATE values and common error codes
Db2 produces SQLSTATE values when it works
as an application server or requester. At this remote server, collect the following diagnostic
items:
Related information
DSNL031I (Db2 Messages) • Console output from the system on which the job
-30000 was run, and a listing of the SYSLOG data set for the
EXECUTION FAILED DUE TO A DISTRIBUTION period of time that spans the failure.
PROTOCOL ERROR THAT WILL NOT • All dumps taken by the attachment facility or
AFFECT THE SUCCESSFUL EXECUTION requesting application.
OF SUBSEQUENT COMMANDS OR SQL
STATEMENTS: REASON reason-code (sub-code) 00D35707
Db2 has detected an error while processing the
Explanation SQLDTAGRP late group descriptor, contained within
Db2 has detected an error while processing the the DRDA SQLDTARD late descriptor. The DDM object
SQLDTAGRP late group descriptor, contained within is a QRYDSC spanning multiple query blocks and DDM
the DRDA SQLDTARD or SQLDTA late descriptors. Level 6b DSSs. One or more of the containing level 6b
The DDM object is either an SQLDTARD or SQLDTA DSSs is other than an object (OBJ) DSS. The descriptor
and must be contained within a single OBJDSS. The is invalid.
descriptor, as defined by the length of the SQLDTARD
or SQLDTA DDM objects, is incomplete and is therefore System action
invalid.
An alert is generated and message DSNL031I is the application will receive SQLCODE -30000 and
written to the console. Refer to the description of this SQLSTATE 58008.
If the error occurs within the SQLDTARD DDM object, Operator response
the application will receive SQLCODE -30000 and
SQLSTATE 58008. If the error occurs within the DDM Notify the system programmer.
SQLDTA object, a DSCINVRM reply message will be
returned to the local Db2. System programmer response

items: 00D35709

period of time that spans the failure. Db2 has detected an error while processing the
• All dumps taken by the attachment facility or SQLDTAGRP late group descriptor contained within
requesting application. a QRYDSC DDM object. The FDOCA geometry
is incorrect. The SQLDTAGRP length specification
00D35708 exceeds the size of the QRYDSC level 6b DSS carrier.
The descriptor is invalid.
Explanation
Db2 has detected an error while processing the System action
SQLDTAGRP late group descriptor, contained within An alert is generated and message DSNL031I is
the DRDA SQLDTARD late descriptor. The DDM object written to the console. Refer to the description of this
is a QRYDSC spanning multiple query blocks and DDM message for further information.
level object 6b DSSs. The code point of one or more
of the containing DDM objects is other than QRYDSC The application will receive SQLCODE -30000 and
(X'241B'). The descriptor is invalid. SQLSTATE 58008.

the application will receive SQLCODE -30000 and If you suspect an error in Db2, you might need to

and reporting the problem, see Collecting diagnostic Collect the following diagnostic items at this local Db2.
data (Collecting data). • Statistics class 4 trace record identified by the IFCID
Problem determination Collect the following diagnostic items at the remote
The statistics class 4 trace record identified by the server.
IFCID sequence number enumerated in the DSNL031I • Relevant error and system logs spanning the time of
message should be analyzed. the failure.
At this local Db2, collect the following diagnostic • Any relevant remote server trace information or
items: dumps.

00D3570A For other remote DRDA clients, refer to the
client product documentation for diagnostic
recommendations.
Explanation
At the Db2 DRDA server, collect the following
diagnostic items:
the SQLDTAGRP late group descriptor, contained
within either the DRDA SQLDTARD or SQLDTA late • Console output from the system on which the job
descriptors. The DDM object is one of the following was run, and a listing of the SYSLOG data set for the
possibilities: QRYDSC, SQLDTARD or SQLDTA. The period of time that spans the failure.
length override value in one of the constituent • All dumps taken by the attachment facility or
SQLDTAGRP SDAs is a placeholder length value, but requesting application.
an allowable placeholder length was not received. This
is invalid. 00D3570B

An alert is generated and message DSNL032I is Db2 has detected an error while processing the
written to the console if the error is detected while SQLDTAGRP late group descriptor, contained within
parsing a command or message DSNL031I is written the DRDA SQLDTA late descriptor. The DDM object is
to the console if the error is detected while parsing the OUTOVR object. A non-zero local identifier (LID)
a command reply. Refer to the description of this was received as an output override descriptor, but the
message for further information. LID value was not one of the values allowed for the
current DRDA level (DRDA Level 4). This is invalid.
If the error occurs within a QRYDSC or SQLDTARD DDM
object, the application will receive SQLCODE -30000
and SQLSTATE 58008. If the error occurs within the System action
DDM SQLDTA object, a DSCINVRM reply message will An alert is generated and message DSNL032I is
be returned to the remote DRDA client. written to the console if the error is detected while
parsing a command. Refer to the description of this
Operator response message for further information.
Notify the system programmer. A DSCINVRM reply message will be returned to the
remote DRDA client.
Operator response
report the problem. For information about identifying Notify the system programmer.

If the remote DRDA client is a Db2 for z/OS system, at If the remote DRDA client is a Db2 for z/OS system, at
the Db2 DRDA client, collect the following diagnostic the Db2 DRDA client, collect the following diagnostic
items: items:

For other remote DRDA clients, refer to the the target of the remote request. This may also include
client product documentation for diagnostic intermediate server systems. For each system that is a
recommendations. Db2 system, collect the following diagnostic items:
At the Db2 DRDA server, collect the following • Console output and the listing of the SYSLOG data
diagnostic items: set from each connected site for the period of time
was run, and a listing of the SYSLOG data set for the For non-Db2 systems, refer to the references specific
period of time that spans the failure. to those products.
• All dumps taken by the attachment facility or If any dumps were generated on any Db2 system
requesting application. participating in processing the remote request, collect
00D3570C
the SQLDTAGRP late group descriptor contained 00D3570D
within either the DRDA SQLDTARD or SQLDTA late
descriptors. The DDM object is either a QRYDSC or
Explanation
SQLDTARD reply data object. The Db2 requester has
received an XMLSEE LID but the CCSIDXML in the Db2 has detected an error while processing
TYPDEFOVR in effect for the object is not UTF-8. Db2 the SQLDTAGRP late group descriptor contained
only supports UTF-8 for XMLSEE LIDs in a reply data within either the DRDA SQLDTARD or SQLDTA late
object. The CCSIDXML value is not supported and is descriptors. The DDM object is either a QRYDSC or
rejected. SQLDTARD reply data object. The Db2 requester has
received an XMLSIE LID in an reply data object. Db2
System action only supports XMLSEE LIDs in a reply data object. The
XMLSIE LID is not supported and is rejected.
System action
Operator response written to the console. Refer to the description of this
Operator response
system generating the DSNL031I message, collect the The statistics class 4 trace record identified by
following diagnostic items: the IFCID sequence number enumerated in the

In addition, identify all connected systems Problem determination
This includes the requester system to which the The statistics class 4 trace record identified by the
application is connected and the data server which is IFCID sequence number enumerated in the DSNL031I
the target of the remote request. This may also include message should be analyzed.
intermediate server systems. For each system that is a At this local Db2, collect the following diagnostic
Db2 system, collect the following diagnostic items: items:
• Console output and the listing of the SYSLOG data • Statistics Class 4 trace record for the LUWID
set from each connected site for the period of time associated with the failing request.
For non-Db2 systems, refer to the references specific items:
to those products.
If any dumps were generated on any Db2 system was run, and a listing of the SYSLOG data set for the
participating in processing the remote request, collect period of time that spans the failure.
• Listings of the SYS1.LOGREC data set, obtained by requesting application.
00D35802
Explanation late environmental descriptors which precede the
Db2 has detected an error while processing SQLDTAGRP late group descriptor contained within
late environmental descriptors which precede the either the SQLDTARD or SQLDTA late descriptors. The
SQLDTAGRP late group descriptor, contained within DDM object is either a QRYDSC, SQLDTARD reply
either the SQLDTARD or SQLDTA late descriptors. The data object, or an SQLDTA command data object. The
DDM object is a QRYDSC, SQLDTARD or SQLDTA. The FDOCA geometry is incorrect. The late environmental
FDOCA geometry is incorrect. The late environmental descriptor meta data definition (MDD) either specifies
descriptor meta data definition does not specify a valid a local identifier (LID) of 0 or defines a nonrelational
DRDA type. The SDA and the entire descriptor are database application class (other than X'05') or the
invalid. meta data reference type is other than X'01'. The MDD
and the entire descriptor are invalid.
System action
System action
written to the console. Refer to the description of this An alert is generated and message DSNL031I is
message for further information. written to the console. Refer to the description of this
DDM objects, the application will receive SQLCODE If the error occurs within the QRYDSC or SQLDTARD
-30000 and SQLSTATE 58008. If the error occurs DDM objects, the application will receive SQLCODE
within the DDM SQLDTA object, a DSCINVRM reply -30000 and SQLSTATE 58008. If the error occurs
message will be returned to the local Db2. within the DDM SQLDTA object, a DSCINVRM reply
Operator response
Operator response

report the problem. For information about identifying If you suspect an error in Db2, you might need to
and reporting the problem, see Collecting diagnostic report the problem. For information about identifying
data (Collecting data). and reporting the problem, see Collecting diagnostic

items: items:
items: items:
00D35803 00D35804
Db2 has detected an error while processing Db2 has detected an error while processing
late environmental descriptors which precede the late environmental descriptors which precede the
SQLDTAGRP late group descriptor, contained within SQLDTAGRP late group descriptor, contained within
either the SQLDTARD or SQLDTA late descriptors. either the SQLDTARD or SQLDTA late descriptors.
The DDM object is either a QRYDSC, SQLDTARD or The DDM object is either a QRYDSC, SQLDTARD or
SQLDTA. The FDOCA geometry is incorrect. The late SQLDTA. The FDOCA geometry is incorrect. The late
environmental descriptor meta data definition (MDD) environmental descriptor meta data definition (MDD)
is valid, however, the descriptor following the MDD is is valid, however, the SDA immediately following the
either not an SDA or is an SDA with a length other MDD is overriding a DRDA type not supported by
than 12 (X'0C'). The SDA and the entire descriptor are DRDA. The SDA and the entire descriptor are invalid.
invalid.
System action
System action
If the error occurs within the QRYDSC or SQLDTARD DDM objects, the application will receive SQLCODE
DDM objects, the application will receive SQLCODE -30000 and SQLSTATE 58008. If the error occurs
-30000 and SQLSTATE 58008. If the error occurs within the DDM SQLDTA object, a DSCINVRM reply
within the DDM SQLDTA object, a DSCINVRM reply message will be returned to the local Db2.
Operator response
Operator response

At this local Db2, collect the following diagnostic Collect the following diagnostic items at this local Db2.
items:
• Statistics Class 4 trace record for the LUWID sequence number specified in message DSNL031I.
At this remote server, collect the following diagnostic server.
items:
• Console output from the system on which the job the failure.
was run, and a listing of the SYSLOG data set for the • Any relevant remote server trace information or
period of time that spans the failure. dumps.
00D35806
Explanation
late environmental descriptors which precede the
Db2 has detected an error while processing SQLDTAGRP late group descriptor, contained within
late environmental descriptors which precede the either the SQLDTARD or SQLDTA late descriptors. The
SQLDTAGRP late group descriptor contained within DDM object is either an SQLDTARD or SQLDTA, each
either the SQLDTARD or SQLDTA late descriptors. The of which may not span DDM level 6b object (OBJ)
DDM object is a QRYDSC, SQLDTARD, or an SQLDTA DSSs. The containing level 6b OBJDSS contains only
data object. The FDOCA geometry is incorrect. The late environmental descriptors and neither groups or
size of the late environmental descriptors exceeds the rows are defined. The descriptor is invalid.
size of the DDM level 6b DSS carrier. The descriptor is
invalid. System action
System action
An alert is generated and message DSNL031I is message for further information.
The application will receive SQLCODE -30000 and -30000 and SQLSTATE 58008. If the error occurs
SQLSTATE 58008. within the DDM SQLDTA object, a DSCINVRM reply
Operator response
Operator response
If the error occurs within a QRYDSC or SQLDTARD
replay data object (SQLDTARD late descriptor), If you suspect an error in Db2, you might need to
the application will receive SQLCODE -30000 and report the problem. For information about identifying
SQLSTATE 58008. If the error occurs within an SQLDTA and reporting the problem, see Collecting diagnostic
command data object (SQLDTA late descriptor), a data (Collecting data).
DSCINVRM reply message will be returned to the local
Db2. Problem determination

items: items:
00D35807 late environmental descriptors which precede the
SQLDTAGRP late group descriptor, contained within
the SQLDTARD late descriptor. The DDM object is a
Explanation
QRYDSC which spans multiple query blocks. One or
Db2 has detected an error while processing more of the code points of the DDM objects carrying
late environmental descriptors which precede the the descriptor is (are) other than QRYDSC (X'241B').
SQLDTAGRP late group descriptor, contained within The descriptor is invalid.
the SQLDTARD late descriptor. The DDM object is a
QRYDSC which spans multiple query blocks. One or System action
more of the containing level 6b DSSs is (are) other than
an object (OBJ) DSS. The descriptor is invalid. An alert is generated and message DSNL031I is
System action
-30000 and SQLSTATE 58008. If the error occurs
If the error occurs within the QRYDSC or SQLDTARD message will be returned to the local Db2.
-30000 and SQLSTATE 58008. If the error occurs Operator response
message will be returned to the local Db2. Notify the system programmer.

items:
items: At this remote server, collect the following diagnostic
items:

period of time that spans the failure. Db2 has detected an error while parsing a DDM
command or DDM command data received from a local
• All dumps taken by the attachment facility or Db2. A reply DSS (RPYDSS) has been received from the
requesting application. local Db2. This is invalid.
00D35809
System action
Db2 has detected an error while processing written to the console. Refer to the description of this
late environmental descriptors which precede the message for further information.
SQLDTAGRP late group descriptor contained within A DDM reply message (PRCCNVRM) will be returned to
the SQLDTARD late descriptor. This late descriptor the local Db2.
is within a QRYDSC which spans one or more query
blocks. The QRYDSC contains only late environmental
descriptors and is, therefore, incomplete. Operator response
System action

If you suspect an error in Db2, you might need to items:
and reporting the problem, see Collecting diagnostic • Statistics Class 4 trace record for the LUWID
data (Collecting data). associated with the failing request.
The statistics class 4 trace record identified by the • Console output from the system on which the job
IFCID sequence number enumerated in the DSNL031I was run, and a listing of the SYSLOG data set for the
message should be analyzed. period of time that spans the failure.
Collect the following diagnostic items at this local Db2. • All dumps taken by the attachment facility or
sequence number specified in message DSNL031I. 00D35902

server. Explanation
• Relevant error and system logs spanning the time of Db2 has detected an error while parsing a DDM
the failure. command or DDM command data received from a local
Db2. The first level 6b DSS received is an object DSS.
• Any relevant remote server trace information or The DDM command carried in a level 6b request DSS
dumps. (RQSDSS) must be the first level 6b DSS received.
00D35901

A DDM reply message (PRCCNVRM) will be returned to
the local Db2.
items:
Db2 has detected an error while parsing a DDM
• All dumps taken by the attachment facility or Db2. The DDM command, specified by the code point
requesting application. contained within the level 6b RQSDSS, is invalid or not
supported by DDM Level 3.
00D35903
System action
Explanation
command or DDM command data received from a
local Db2. The first level 6b DSS received is neither a
request (RQS) DSS, Object (OBJ) DSS nor Reply (RPY) A DDM reply message (CMDNSPRM) will be returned to
DSS and is invalid. the local Db2.

A DDM reply message (SYNTAXRM) will be returned to
the local Db2.

items: 00D35906

• All dumps taken by the attachment facility or command or DDM command data received from a local
requesting application. Db2. The EXCSAT command has been successfully
processed but the current DDM command, while
00D35905 supported by DDM Level 3 and Db2, has been sent
prior to ACCRDB. The only valid command prior to
Explanation ACCRDB is another EXCSAT command.

command or DDM command data received from a System action
local Db2. The first DDM command received on this An alert is generated and message DSNL032I is
conversation, while a valid DDM Level 3 command, written to the console. Refer to the description of this
is other than EXCSAT. The first command must be message for further information.
EXCSAT.
A DDM reply message (RDBNACRM) will be returned to
the local Db2.
System action

the local Db2. System programmer response

items:
message should be analyzed. At this remote server, collect the following diagnostic
items:
items:

command or DDM command data received from an
• All dumps taken by the attachment facility or local Db2. The state of the Db2 remote server is
requesting application. in 'BIND processing' and the current DDM command
00D35907 is other than BNDSQLSTT, ENDBND, RDBCMM or
RDBRLLBCK.
Explanation
System action
command or DDM command data received from An alert is generated and message DSNL032I is
an local Db2. the ACCRDB command has been written to the console. Refer to the description of this
successfully processed and the current command is message for further information.
another ACCRDB instance. This is invalid. A DDM reply message (PKGBPARM) will be returned to
the local Db2.
System action
A DDM reply message (RDBACCRM) will be returned to System programmer response
the local Db2.

data (Collecting data). At this local Db2, collect the following diagnostic item:
items:
command or DDM command data received from an
• All dumps taken by the attachment facility or local Db2. The DDM command has been successfully
requesting application. processed, however, one or more of the level 6b DSSs
00D35908 are other than object (OBJ) DSSs. The only valid level
6b DSS chain is a single RQS DSS, followed by one or
more OBJ DSSs.

the local Db2.
and reporting the problem, see Collecting diagnostic At this Db2 local Db2, collect the following diagnostic
The statistics class 4 trace record identified by the At this Db2 remote server, collect the following
IFCID sequence number enumerated in the DSNL032I diagnostic items:
At this remote server, collect the following diagnostic 00D3590B
items:
• All dumps taken by the attachment facility or local Db2. One or more DDM command data objects,
requesting application. defined as required by DDM Level 3, were not received
with the DDM command.
00D3590A
System action
Explanation
Db2 has detected an error while parsing DDM
command data received from a local Db2. The DDM
command data object, as defined by the DDM code
point, is either invalid or not valid for this command, as A DDM reply message (SYNTAXRM) will be returned to
specified by DDM level 3. the local Db2.

A DDM reply message (OBJNSPRM) will be returned to
the local Db2.

Problem determination At this Db2 remote server, collect the following
diagnostic items:
associated with the failing request. 00D3590D
At this Db2 remote server, collect the following

diagnostic items: Explanation
• Console output from the system on which the job Db2 has detected an error while parsing a DDM
was run, and a listing of the SYSLOG data set for the command data object received from a local Db2. The
period of time that spans the failure. DDM object is a TYPDEFNAM, signaling a change in
machine representation from the local Db2, however,
• All dumps taken by the attachment facility or the value of this DDM scalar is other than QTDSQL370,
requesting application. QTDSQLX86 or QTDSQL400. These are the only valid
00D3590C machine representations supported by DRDA.

Db2 has detected an error while parsing DDM An alert is generated and message DSNL032I is
command data received from a local Db2. The DDM written to the console. Refer to the description of this
object is a TYPDEFNAM, signaling a change in machine message for further information.
representation from the local Db2, however, the A DDM reply message (VALNSPRM) will be returned to
length, as specified by DDM level 3, is incorrect. the local Db2.

the local Db2. If you suspect an error in Db2, you might need to
The statistics class 4 trace record identified by the At this Db2 remote server, collect the following
IFCID sequence number enumerated in the DSNL032I diagnostic items:

00D3590E change in CCSIDs from the local Db2. This is a DDM
collection consisting of three DDM scalars: CCSIDSBC,
CCSIDMBC, and CCSIDDBC. The TYPDEFOVR contains
Explanation
multiple instances of the CCSIDSBC scalar. This is
Db2 has detected an error while parsing a DDM invalid.
command data object received from a local Db2.
The DDM object is a TYPDEFOVR, signaling a change System action
in CCSIDs from the local Db2. This is a DDM
collection consisting of three DDM scalars: CCSIDSBC, An alert is generated and message DSNL032I is
CCSIDMBC, and CCSIDDBC. The length of one of the written to the console. Refer to the description of this
constituent scalars is incorrect. message for further information.
System action the local Db2.
At this local Db2, collect the following diagnostic diagnostic items:
items:
At this Db2 remote server, collect the following • All dumps taken by the attachment facility or
diagnostic items: requesting application.

00D3590F Db2. The DDM object is a TYPDEFOVR, signaling a
change in CCSIDs from the local Db2. This is a DDM
Explanation
Db2 has detected an error while parsing a DDM multiple instances of the CCSIDMBC scalar. This is
command or DDM command data received from a local invalid.
Db2. The DDM object is a TYPDEFOVR, signaling a

System action A DDM reply message (SYNTAXRM) will be returned to
the local Db2.
A DDM reply message (SYNTAXRM) will be returned to Notify the system programmer.
the local Db2.
items:
At this local Db2, collect the following diagnostic At this Db2 remote server, collect the following
items: diagnostic items:
diagnostic items: • All dumps taken by the attachment facility or
was run, and a listing of the SYSLOG data set for the .
requesting application. Explanation
00D35911 Db2 has detected an error while parsing a DDM
Explanation Db2. The DDM object is a TYPDEFOVR, signaling a
change in CCSIDs from the local Db2. This is a DDM
Db2 has detected an error while parsing a DDM collection consisting of three DDM scalars: CCSIDSBC,
command or DDM command data received from a local CCSIDMBC, and CCSIDDBC. The TYPDEFOVR length
Db2. The DDM object is a TYPDEFOVR, signaling a exceeds the sums of the lengths of the constituent
change in CCSIDs from the local Db2. This is a DDM scalars. This is invalid.
multiple instances of the CCSIDDBC scalar. This is System action
invalid. An alert is generated and message DSNL032I is
An alert is generated and message DSNL032I is A DDM reply message (SYNTAXRM) will be returned to
written to the console. Refer to the description of this the local Db2.

data (Collecting data). Collect the following diagnostic items at this local Db2.
Problem determination sequence number specified in message DSNL031I.
Analyze the statistics class 4 trace record identified Collect the following diagnostic items at the remote
by the IFCID sequence number enumerated in the server.
DSNL032I message. • Relevant error and system logs spanning the time of
At this local Db2, collect the following diagnostic the failure.
items: • Any relevant AS trace information or dumps.
• Statistics Class 4 trace record for the LUWID 00D35914
At this Db2 remote server, collect the following Explanation
diagnostic items:
Db2 detected an error while parsing a DDM command
• Console output from the system on which the job received from the application requester (AR). The
was run, and a listing of the SYSLOG data set for the minimum level attribute of the DDM command
period of time that spans the failure. received from the AR, (that is, the level of DDM
• All dumps taken by the attachment facility or required to support the command) exceeds the DDM
requesting application. level specified by the AR during CONNECT processing.
00D35913
System action
Db2 has detected an error while parsing a DDM message for further information.
The DDM object is TYPDEFOVR, signaling a CCSID A DDM reply message (PRCCNVRM) is returned to the
change from the local Db2. This is a collection local Db2.
consisting of CCSIDSBC, CCSIDMBC, and CCSIDDBC.
The TYPDEFOVR contains an object other than Operator response
CCSIDSBC, CCSIDDBC, or CCSIDDBC. This is invalid.
System action
A DDM reply message (VALNSPRM) will be returned to data (Collecting data).
the local Db2.
Operator response
Notify the system programmer. the IFCID sequence number included in the DSNL032I
message.
System programmer response At this local Db2, collect the following diagnostic

00D35915 data object received from a remote requester. The
command data object is not supported at the DDM
level negotiated during CONNECT processing. The
Explanation
command data object is rejected.
data object received from the application requester System action
(AR). The minimum level attribute of the DDM
command data object received from the AR (that An alert is generated and message DSNL032I is
is, the level of DDM required to support the object) written to the console. Refer to the description of this
exceeds the DDM level specified by the AR during message for further information.
CONNECT processing.
A DDM reply message (PRCCNVRM) is returned to the
remote requester.
System action
A DDM reply message (PRCCNVRM) is returned to the System programmer response
local Db2.
Operator response

If you suspect an error in Db2, you might need to Analyze the statistics class 4 trace record identified
report the problem. For information about identifying by the IFCID sequence number enumerated in the
and reporting the problem, see Collecting diagnostic DSNL032I message. For the Db2 system generating
data (Collecting data). the DSNL032I message, collect the following
diagnostic items:
the IFCID sequence number included in the DSNL032I In addition, identify all connected systems
message. participating in the processing of the remote request.
items:
• Statistics Class 4 trace record for the LUWID intermediate server systems. For each system that is a
associated with the failing request. Db2 system, collect the following diagnostic items:
At this Db2 remote server, collect the following • Console output and the listing of the SYSLOG data
diagnostic items: set from each connected site for the period of time

For non-Db2 systems, refer to the documentation Explanation
If any dumps were generated on any Db2 system command or DDM command data. The negotiated
participating in processing the remote request, collect security manager level is greater than or equal to
the following diagnostic items: 5, and the required ACCSEC and SECCHK commands
• Listings of the SYS1.LOGREC data set, obtained by were not received before the ACCRDB command.
• All dumps created by this failure. System action
00D35918 The conversation is terminated, and message
DSNL030I is issued. Refer to the description of this
Explanation
A DDM reply message (MGRDEPRM) is returned to the
Db2 has detected an error while parsing a DDM local Db2.
command or DDM command data. The DDM command,
specified by the code point contained within the level
6b RQSDSS, is invalid or not supported by DDM Level Operator response
3. Notify the system programmer.

A DDM reply message (CMDNSPRM) is returned to the If you suspect an error in Db2, you might need to
local Db2. report the problem. For information about identifying

System programmer response Analyze the statistics class 4 trace record identified
If you suspect an error in Db2, you might need to DSNL032I message.
and reporting the problem, see Collecting diagnostic At this local Db2, collect the following diagnostic item:
Analyze the statistics class 4 trace record identified items:
by the IFCID sequence number enumerated in the • Console output from the system on which the job
DSNL032I message. was run, and a listing of the SYSLOG data set for the
associated with the failing request. 00D3591A
items: Explanation
was run, and a listing of the SYSLOG data set for the command or DDM command data. The negotiated
period of time that spans the failure. security manager level is less than 5, and an ACCSEC
• All dumps taken by the attachment facility or command was received.
A DDM reply message (CMDNSPRM) is returned to the
local Db2.

At this local Db2, collect the following diagnostic item:
report the problem. For information about identifying • Statistics Class 4 trace record for the LUWID
and reporting the problem, see Collecting diagnostic associated with the failing request.
items:
The statistics class 4 trace record identified by the was run, and a listing of the SYSLOG data set for the
IFCID sequence number enumerated in the DSNL032I period of time that spans the failure.
At this local Db2, collect the following diagnostic item: requesting application.
• Statistics Class 4 trace record for the LUWID 00D3591C
items:
• Console output from the system on which the job command or DDM command data. The negotiated
was run, and a listing of the SYSLOG data set for the security manager level is less than 5, and a SECCHK
period of time that spans the failure. command was received.
requesting application. System action
00D3591B A DDM reply message (CMDNSPRM) is returned to the
local Db2.
Explanation
Operator response
command or DDM command data. An ACCSEC Notify the system programmer.
command was received when an ACCSEC command
had already been executed successfully. System programmer response
System action
The conversation is terminated, and message and reporting the problem, see Collecting diagnostic
DSNL030I is issued. Refer to the description of this data (Collecting data).
A DDM reply message (PRCCNVRM) is returned to the Problem determination
local Db2.
Operator response message should be analyzed.
Notify the system programmer. At this local Db2, collect the following diagnostic item:
If you suspect an error in Db2, you might need to At this remote server, collect the following diagnostic

• All dumps taken by the attachment facility or SECCHK command was sent after an ACCRDB was
requesting application. successfully processed.
00D3591D
System action
Explanation The conversation is terminated, and message
command or DDM command data. A SECCHK
command was received out of order, which means A DDM reply message (PRCCNVRM) is returned to the
either an ACCSEC command has not executed local Db2.
successfully, or a SECCHK command has already been
processed. Operator response
System action
The conversation is terminated, and message System programmer response
A DDM reply message (PRCCNVRM) is returned to the and reporting the problem, see Collecting diagnostic
local Db2. data (Collecting data).

If you suspect an error in Db2, you might need to At this local Db2, collect the following diagnostic item:
items:
• Statistics Class 4 trace record for the LUWID 00D3591f
items:
• Console output from the system on which the job command or DDM command data. The negotiated
was run, and a listing of the SYSLOG data set for the resync manager level is less than 5, but an SYNCRSY
period of time that spans the failure. command was received. The request is invalid.
00D3591E An alert is generated and message DSNL032I is
Explanation message for further information.
Db2 has detected an error while parsing a DDM A DDM reply message (CMDNSPRM) is returned to the
command or DDM command data. An ACCSEC or remote requester.

Operator response A DDM reply message (CMDNSPRM) is returned to the
remote requester.
Operator response
DSNL032I message. For the Db2 system generating Problem determination
the DSNL032I message, collect the following Analyze the statistics class 4 trace record identified
diagnostic items: by the IFCID sequence number enumerated in the
• Statistics Class 4 trace record for the LUWID DSNL032I message. For the Db2 system generating
associated with the failing request. the DSNL032I message, collect the following
diagnostic items:
For non-Db2 systems, refer to the documentation • Console output and the listing of the SYSLOG data
specific to those products for diagnostic procedures. set from each connected site for the period of time
participating in processing the remote request, collect For non-Db2 systems, refer to the documentation
the following diagnostic items: specific to those products for diagnostic procedures.
Explanation
00D35921
Db2 has detected an error while parsing a
DDM command or DDM command data. A
SYNCCTL command was received but the negotiated Explanation
SYNCPTMGR (Sync Point Manager) level is less than Db2 has detected an error while parsing a DDM
5 and XAMGR (XA Manager) level is less than 7. The command or DDM command data. Db2 received an
request is invalid. ACCRDB command from the resynch port. The request
is invalid.
System action
An alert is generated and message DSNL032I is System action
written to the console. Refer to the description of this The conversation is terminated.

message for further information. The conversation is terminated.
A DDM reply message (PRCCNVRM) is returned to the An alert is generated and message DSNL032I is
remote requester. written to the console. Refer to the description of this
Operator response A DDM reply message (PRCCNPRM) is returned to the

remote requester.
Operator response
diagnostic items:
Explanation
00D35923
command or DDM command data. Db2 received an
ACCSEC command from the resynch port. This request Explanation
is invalid. Db2 has detected an error while parsing a DDM
command or DDM command data. A SECCHK

command was received from the resynch port. The Explanation
request is invalid.
command or DDM command data. An INTRDBRQS
System action command was received on an SNA connection. The
The conversation is terminated. request is invalid.

written to the console. Refer to the description of this System action
message for further information. The conversation is terminated.
A DDM reply message (PRCCNPRM) is returned to the An alert is generated and message DSNL032I is
Operator response A DDM reply message (MGRDEPRM) is returned to the
Notify the system programmer. remote requester.

Analyze the statistics class 4 trace record identified data (Collecting data).
the DSNL032I message, collect the following
diagnostic items: Analyze the statistics class 4 trace record identified
In addition, identify all connected systems diagnostic items:
• All dumps created by this failure. the following diagnostic items:
00D35924 • Listings of the SYS1.LOGREC data set, obtained by


00D35925 • All dumps created by this failure.
00D35926
Explanation
Db2 has detected an error while parsing a DDM Explanation
command or DDM command data. A SYNCCTL
command was received but the negotiated XAMGR (XA
Manager) level is less than 7. The request is invalid.
remote requester. The DDM object is a TYPDEFOVR,
signaling a change in CCSIDs from the remote
System action requester. This is a DDM collection consisting of
four DDM scalars: CCSIDSBC, CCSIDMBC, CCSIDDBC
and CCSIDXML. The TYPDEFOVR contains multiple
instances of the CCSIDXML scalar. This is invalid.
A DDM reply message (CMDNSPRM) is returned to the
System action
remote requester.
remote requester.
DSNL032I message. For the Db2 system generating
diagnostic items: Problem determination
• Statistics Class 4 trace record for the LUWID Analyze the statistics class 4 trace record identified
associated with the failing request. by the IFCID sequence number enumerated in the
diagnostic items:
application is connected and the data server which is • Statistics Class 4 trace record for the LUWID
the target of the remote request. This may also include associated with the failing request.
• Console output and the listing of the SYSLOG data This includes the requester system to which the
set from each connected site for the period of time application is connected and the data server which is
spanning the failure. the target of the remote request. This may also include

If any dumps were generated on any Db2 system • Console output from the system on which the job
participating in processing the remote request, collect was run, and a listing of the SYSLOG data set for the
the following diagnostic items: period of time that spans the failure.
• Listings of the SYS1.LOGREC data set, obtained by • All dumps taken by the attachment facility or
executing IFCEREP1 at each connected site. requesting application.
• All dumps created by this failure. 00D35A02
00D35A01
Explanation
Explanation Db2 has detected an error while parsing a DDM
The DDM object is either an SQLSTT, SQLOBJNAM,
or SQLSTTVRB. These objects are described by early
The DDM object is either an SQLSTT, SQLOBJNAM
group descriptors, each of which contains both SBCS
or SQLSTTVRB. These objects are described by early
and mixed SDAs describing character data. In all
group descriptors, each of which contains both SBCS
cases, the instantiation of the SBCS and mixed
and mixed SDAs describing character data. In all
elements are mutually exclusive, i.e. if the SBCS
cases, the instantiation of the SBCS and mixed
element is sent, then the mixed must not be sent
elements are mutually exclusive, i.e. if the SBCS
and conversely. Further, either the SBCS or mixed (not
element is sent, then the mixed must not be sent
both) must be instantiated. The data retrieved from
and conversely. The instantiation of both the SBCS and
the object instantiates neither the SBCS nor the mixed
mixed data SDAs has been sent. This is invalid.
SDA. This is invalid.

A DDM reply message (DTAMCHRM) will be returned to
the local Db2.
the local Db2.



DSNL032I message.
DSNL032I message.
items:
items:
diagnostic items:
diagnostic items listed in

• Console output from the system on which the job For non-Db2 systems, refer to the documentation
was run, and a listing of the SYSLOG data set for the specific to those products for diagnostic procedures.
• All dumps taken by the attachment facility or participating in processing the remote request, collect
requesting application. the following diagnostic items:
00D35A03 • Listings of the SYS1.LOGREC data set, obtained by
Db2 has detected an error while parsing a DDM 00D35A04
command data object received from a remote
requester. The DDM object is either an SQLSTT,
Explanation
SQLOBJNAM, or SQLSTTVRB. The DDM extended
length field required to support these objects is Db2 has detected an error while parsing a DDM
invalid. command data object received from a remote
requester. The DDM object is SQLATTR. The SQLATTR
System action object has a length exceeding 32K. The length is
invalid.
System action
remote requester.
Operator response A DDM reply message (SYNTAXRM) is returned to the

remote requester.
Operator response
diagnostic items:

• Console output and the listing of the SYSLOG data • Console output from the system on which the job
set from each connected site for the period of time was run, and a listing of the SYSLOG data set for the
spanning the failure. period of time that spans the failure.
For non-Db2 systems, refer to the documentation • All dumps taken by the attachment facility or
specific to those products for diagnostic procedures. requesting application.
If any dumps were generated on any Db2 system .

participating in processing the remote request, collect 00D35B02
• Listings of the SYS1.LOGREC data set, obtained by Explanation
Db2 has detected an error while parsing an SQLDTA
00D35B01 The SQLDTA is a DDM collection consisting of the
FDODSC and FDODTA scalars. The first scalar within
the SQLDTA is other than the FDODSC scalar. This is
Explanation
invalid.
command data object received from a local Db2. The System action
length of the SQLDTA exceeds 32KB, however, the
DDM extended length field is invalid. An alert is generated and message DSNL032I is
System action
the local Db2.
Operator response
the local Db2. Notify the system programmer.

items:
items: .
• Statistics Class 4 trace record for the LUWID At this Db2 remote server, collect the following
associated with the failing request. diagnostic items listed in
. • Console output from the system on which the job

. Explanation
00D35B03 Db2 has detected an error while parsing an SQLDTA
command data object received from a local Db2. The
Explanation SQLDTA FDOCA descriptor, contained in the FDODSC
scalar, includes late environmental descriptors,
Db2 has detected an error while parsing an SQLDTA however, the SQLDTA meta data definition (MDD) is
command data object received from a local Db2. The either invalid or has not been included within the
SQLDTA is a DDM collection consisting of the FDODSC SQLDTA descriptor. The descriptor is invalid.
and FDODTA scalars. The length of the FDODSC
scalar exceeds 32KB, however, the format of the DDM
extended length is invalid.
System action
System action written to the console. Refer to the description of this
written to the console. Refer to the description of this A DDM reply message (DSCINVRM) will be returned to
message for further information. the local Db2.

the local Db2.
Operator response
Operator response
Problem determination IFCID sequence number enumerated in the DSNL032I
IFCID sequence number enumerated in the DSNL032I At this local Db2, collect the following diagnostic
At this local Db2, collect the following diagnostic • Statistics Class 4 trace record for the LUWID
• Statistics Class 4 trace record for the LUWID .

associated with the failing request. At this Db2 remote server, collect the following
. diagnostic items listed in
At this Db2 remote server, collect the following • Console output from the system on which the job
diagnostic items listed in was run, and a listing of the SYSLOG data set for the
• All dumps taken by the attachment facility or .
requesting application. 00D35B05
.
00D35B04
Explanation
The SQLDTA FDOCA descriptor geometry is incorrect.

Either the SQLDTA triplet length is incorrect or the or a replication factor other than 1. The descriptor is
SQLDTA triplet type is other than an row layout (RLO). invalid.
The descriptor is invalid.
System action
System action
A DDM reply message (DSCINVRM) will be returned to
A DDM reply message (DSCINVRM) will be returned to the local Db2.
the local Db2.
Operator response
Operator response
The statistics class 4 trace record identified by the IFCID sequence number enumerated in the DSNL032I
IFCID sequence number enumerated in the DSNL032I message should be analyzed.
items:
• Statistics Class 4 trace record for the LUWID associated with the failing request.
.
.
At this Db2 remote server, collect the following diagnostic items listed in
• Console output from the system on which the job was run, and a listing of the SYSLOG data set for the
was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
period of time that spans the failure. • All dumps taken by the attachment facility or
• All dumps taken by the attachment facility or requesting application.
.
.
00D35B07
00D35B06
Explanation
Explanation
Db2 has detected an error while parsing an SQLDTA command data object received from a local Db2.
command data object received from a local Db2. The SQLDTA FDOCA descriptor, contained within the
The SQLDTA FDOCA descriptor geometry is incorrect. FDODSC scalar, has been validated, however, the
The SQLDTA RLO triplet either specifies a local FDODTA scalar, containing the host variable data, is
identifier (LID) which is different than that defined not included within the SQLDTA DDM object. This is
in the previously processed SQLDTAGRP late group invalid.
descriptor, or specifies a nonzero number of elements

the local Db2.
the local Db2.
items:
At this local Db2, collect the following diagnostic .

items: At this Db2 remote server, collect the following
• Statistics Class 4 trace record for the LUWID diagnostic items listed in
diagnostic items listed in • All dumps taken by the attachment facility or
period of time that spans the failure. 00D35B09
. Acting as a DRDA server, Db2 has detected an error
00D35B08 while parsing an SQLDTA object. The SQLDTA object,
or one of its constituent members, has an object
length less than 4. Its constituent members are:
Explanation
• FDODSC or FDODTA, in the case of an SQLDTA in
Db2 has detected an error while parsing an SQLDTA non-array format
The SQLDTA FDOCA descriptor, contained within the • FDODSC, FDOEXT, FDODTA, or FDOOFF, in the case
FDODSC scalar, has been validated. The length of of an SQLDTA in array format.
the FDODTA scalar, containing the host variable data,
exceeds 32KB, however, the format of the DDM System action
extended length field is invalid.
The system generates an alert and returns message
DSNL032I. Refer to the description of this message for
System action further information.

data (Collecting data). You should analyze the statistics class 4 trace record
Problem determination in the DSNL032I message.
Analyze the statistics class 4 trace record identified At the Db2 for z/OS DRDA server, collect the following
by the IFCID sequence number enumerated in the diagnostic items:
DSNL032I message. • SVC dump (or system dump), taken to SYS1.DUMPxx
At the Db2 for z/OS DRDA server, collect the following data set, as result of an operator-initiated dump
diagnostic items: command or SLIP trap exit.
• SVC dump (or system dump), taken to SYS1.DUMPxx • Statistics Class 4 trace record for the LUWID
data set, as result of an operator-initiated dump associated with the failing request.
command or SLIP trap exit. If the requester is a Db2 for z/OS system, collect the
• Statistics Class 4 trace record for the LUWID following diagnostic items:
If the requester is a Db2 for z/OS system, collect the was run, and a listing of the SYSLOG data set for the
following diagnostic items: period of time that spans the failure.
period of time that spans the failure. 00D35B0B
Related information Acting as a DRDA server, Db2 has detected an error
DSNU032E (Db2 Messages) while parsing an SQLDTA object in array format. In
this case, the SQLDTA is a DDM collection consisting
00D35B0A of FDODSC, FDOEXT, FDODTA, and FDOOFF scalars.
The last scalar within the SQLDTA is other than the
Explanation FDOOFF. This procedure is invalid.
Acting as a DRDA server, Db2 has detected an error

while parsing an SQLDTA object. The SQLDTA object, System action
or one of its constituent members, has an object The system generates an alert and returns message
length indicator less than 8. Its constituent members DSNL032I. Refer to the description of this message for
are listed below: further information.
non-array format System programmer response
• FDODSC, FDOEXT, FDODTA, or FDOOFF, in the case If you suspect an error in Db2, you might need to
of an SQLDTA in array format. report the problem. For information about identifying
DSNL032I. Refer to the description of this message for Problem determination
further information. You should analyze the statistics class 4 trace record
System programmer response in the DSNL032I message.
If you suspect an error in Db2, you might need to At the Db2 for z/OS DRDA server, collect the following
report the problem. For information about identifying diagnostic items:

• SVC dump (or system dump), taken to SYS1.DUMPxx • SVC dump (or system dump), taken to SYS1.DUMPxx
data set, as result of an operator-initiated dump data set, as result of an operator-initiated dump
command or SLIP trap exit. command or SLIP trap exit.
If the requester is a Db2 for z/OS system, collect the If the requester is a Db2 for z/OS system, collect the
following diagnostic items: following diagnostic items:
00D35B0C 00D35B0D
Acting as a DRDA server, Db2 has detected an error Acting as a DRDA server, Db2 has detected an error
while parsing an SQLDTA object. The SQLDTA object while parsing an SQLDTA object. The FDOCA geometry
itself, or one of its constituent members has an object for an SQLDTAGRP late group descriptor, contained
length that is greater than the actual length remaining within the DRDA SQLDTA late descriptor, is incorrect.
in the enclosing object. The constituent members are The SQLDTAGRP triplet is not defined as an FD:OCA
listed below: nullable group. The descriptor is invalid.
non-array format System action
• FDODSC, FDOEXT, FDODTA, or FDOOFF, in the case The system generates an alert and returns message
of an SQLDTA in array format DSNL032I. Refer to the description of this message for
For example, a FDODSC scalar as an object length further information.
that is greater than the SQLDTA object in which it is A DSCINVRM reply message is returned to the
contained, or an SQLDTA object has an object length requester.
greater than the DSS in which it is contained.
System action
The system generates an alert and returns message report the problem. For information about identifying
DSNL032I. Refer to the description of this message for and reporting the problem, see Collecting diagnostic
further information. data (Collecting data).

If you suspect an error in Db2, you might need to You should analyze the statistics class 4 trace record
report the problem. For information about identifying identified by the IFCID sequence number enumerated
and reporting the problem, see Collecting diagnostic in the DSNL032I message.
At the Db2 for z/OS DRDA server, collect the following
diagnostic items:
You should analyze the statistics class 4 trace record data set, as result of an operator-initiated dump
identified by the IFCID sequence number enumerated command or SLIP trap exit.
At the Db2 for z/OS DRDA server, collect the following associated with the failing request.
diagnostic items:

period of time that spans the failure. Acting as a DRDA server, Db2 has detected an error
while parsing in an SQLDTA object received from a
• All dumps taken by the attachment facility or DRDA requester system. The total FDODSC object
requesting application. length computed from the constituent SDAs in the
00D35B0E SQLDTAGRP is smaller than the stated length of the
FDODSC object.
Explanation
System action
while parsing an SQLDTA object. The FDOCA geometry The system generates an alert and returns message
for an SQLDTAGRP late group descriptor, contained DSNL032I. Refer to the description of this message for
within the DRDA SQLDTA late descriptor, is incorrect. further information.
The late descriptor includes late environmental
descriptors and the SQLDTAGRP meta data definition System programmer response
(MDD) is either invalid or has not been included within
the descriptor. The descriptor is invalid. If you suspect an error in Db2, you might need to
DSNL032I. Refer to the description of this message for Problem determination
A DSCINVRM reply message is returned to the identified by the IFCID sequence number enumerated
requester. in the DSNL032I message.
System programmer response diagnostic items:
If you suspect an error in Db2, you might need to • SVC dump (or system dump), taken to SYS1.DUMPxx
report the problem. For information about identifying data set, as result of an operator-initiated dump
and reporting the problem, see Collecting diagnostic command or SLIP trap exit.
You should analyze the statistics class 4 trace record following diagnostic items:
in the DSNL032I message. • Console output from the system on which the job
At the Db2 for z/OS DRDA server, collect the following period of time that spans the failure.
diagnostic items:
• SVC dump (or system dump), taken to SYS1.DUMPxx requesting application.
command or SLIP trap exit. 00D35B10

associated with the failing request. Explanation
If the requester is a Db2 for z/OS system, collect the Acting as a DRDA server, Db2 has detected an error
following diagnostic items: while parsing an SQLDTA object. While parsing a
constituent part of the SQLDTA object, the constituent
• Console output from the system on which the job part has a stated or implied length that is larger than
was run, and a listing of the SYSLOG data set for the the stated length of the SQLDTA object itself.
00D35B0F

The system generates an alert and returns message If you suspect an error in Db2, you might need to
DSNL032I. Refer to the description of this message for report the problem. For information about identifying
further information. and reporting the problem, see Collecting diagnostic
A DSCINVRM reply message is returned to the
requester.
System programmer response You should analyze the statistics class 4 trace record
and reporting the problem, see Collecting diagnostic At the Db2 for z/OS DRDA server, collect the following
data (Collecting data). diagnostic items:
Problem determination data set, as result of an operator-initiated dump
identified by the IFCID sequence number enumerated • Statistics Class 4 trace record for the LUWID
in the DSNL032I message. associated with the failing request.
At the Db2 for z/OS DRDA server, collect the following If the requester is a Db2 for z/OS system, collect the
diagnostic items: following diagnostic items:
• SVC dump (or system dump), taken to SYS1.DUMPxx • Console output from the system on which the job
data set, as result of an operator-initiated dump was run, and a listing of the SYSLOG data set for the
command or SLIP trap exit. period of time that spans the failure.
If the requester is a Db2 for z/OS system, collect the 00D35B12
while parsing an SQLDTA object in an array format. The
• All dumps taken by the attachment facility or number elements in the FDOEXT scalar object is not
requesting application. equal to the number elements in the FDOOFF scalar
object.
00D35B11
System action
Explanation
while parsing an SQLDTA object in an array format.
The number elements in the FDOEXT scalar object
is not equal to the number elements of SDAs in the
SQLDTAGRP in the FDODSC. System programmer response
requester. You should analyze the statistics class 4 trace record

At the Db2 for z/OS DRDA server, collect the following • Console output from the system on which the job
diagnostic items: was run, and a listing of the SYSLOG data set for the
data set, as result of an operator-initiated dump • All dumps taken by the attachment facility or
command or SLIP trap exit. requesting application.
• Statistics Class 4 trace record for the LUWID 00D35B14
If the requester is a Db2 for z/OS system, collect the Explanation
• Console output from the system on which the job while parsing an SQLDTA object. The FDODTA scalar
was run, and a listing of the SYSLOG data set for the object is a null FD:OCA group and contains no input
period of time that spans the failure. data values. The FDODTA scalar object must be non-
• All dumps taken by the attachment facility or null and must contain the input data values described
requesting application. by the FDODSC scalar object
00D35B13
System action
Explanation The system generates an alert and returns message
Acting as a DRDA server, Db2 has detected an error further information.
while parsing an SQLDTA object in an array format.
An offset value in FDOOFF scalar object results is
invalid and results in a data value location that is not
contained within the FDODTA scalar object. If you suspect an error in Db2, you might need to
System programmer response identified by the IFCID sequence number enumerated
report the problem. For information about identifying At the Db2 for z/OS DRDA server, collect the following
and reporting the problem, see Collecting diagnostic diagnostic items:
data (Collecting data). • SVC dump (or system dump), taken to SYS1.DUMPxx
in the DSNL032I message. If the requester is a Db2 for z/OS system, collect the
diagnostic items: • Console output from the system on which the job
command or SLIP trap exit. • All dumps taken by the attachment facility or
associated with the failing request. 00D35B15
following diagnostic items: Explanation
in an SQLDTA object received from a DRDA requester

system. The total SQLDTA object length computed A DSCINVRM reply message is returned to the
from the constituent scalar object is smaller than the requester.
stated length of the SQLDTA object itself.
System action

diagnostic items:
in the DSNL032I message. • Statistics Class 4 trace record for the LUWID
diagnostic items: If the requester is a Db2 for z/OS system, collect the
• SVC dump (or system dump), taken to SYS1.DUMPxx following diagnostic items:
If the requester is a Db2 for z/OS system, collect the requesting application.
00D35B17
• All dumps taken by the attachment facility or Acting as a DRDA server, Db2 has detected an error
requesting application. while parsing an SQLDTA object. While parsing the
SQLDTAGRP late group descriptor contained within the
00D35B16 SQLDTA object, the length override value in one of the
constituent SQLDTAGRP SDAs contains a placeholder
Explanation length value, but the placeholder length value is an
allowable value. The descriptor is invalid.
while parsing an SQLDTA object. While parsing the
System action
SQLDTAGRP late group descriptor contained within the
SQLDTA object, the local identifier (LID) of one of the The system generates an alert and returns message
SQLDTAGRP constituent triplets was not previously DSNL032I. Refer to the description of this message for
defined by a late environmental descriptor and the LID further information.
is outside of the bounds of the default environmental
descriptor LIDs. Note that the default LIDs are
requester.
identical to the DRDA types. The descriptor is invalid.


You should analyze the statistics class 4 trace record At this local Db2, collect the following diagnostic
identified by the IFCID sequence number enumerated items:
diagnostic items:
• SVC dump (or system dump), taken to SYS1.DUMPxx diagnostic items listed in
command or SLIP trap exit. • Console output from the system on which the job
.
was run, and a listing of the SYSLOG data set for the 00D35C02
00D35C01 BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
command received from a local Db2. An invalid
instance has been received as a parameter on a
Explanation BNDSQLSTT command.
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND System action
instance has been received as a parameter on a An alert is generated and message DSNL032I is
BGNBND command. written to the console. Refer to the description of this
System action A DDM reply message (PRMNSPRM) will be returned to
the local Db2.
A DDM reply message (PRMNSPRM) will be returned to Notify the system programmer.
the local Db2.
items:

.
At this Db2 remote server, collect the following requesting application.
.
. BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
00D35C03
instance has been received as a parameter on an
ENDBND command.
Explanation
Db2 has detected an error while parsing a DDM System action
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
instance has been received as a parameter on a
DRPPKG command.
A DDM reply message (PRMNSPRM) will be returned to
the local Db2.
System action

items:
message should be analyzed. .
items: diagnostic items listed in
.
.

00D35C05 command received from a local Db2. One or more
instance variables, defined by DDM Level 3 as required
parameters for this DDM command, were not received.
Explanation
command received from a local Db2. An invalid An alert is generated and message DSNL032I is
instance has been received as a parameter on a written to the console. Refer to the description of this
REBIND command. message for further information.
.
items:
. period of time that spans the failure.
diagnostic items listed in requesting application.
• Console output from the system on which the job .

Explanation
.
command or DDM BGNBND, BNDSQLSTT, ENDBND,
00D35C06 DRPPKG, or REBIND command data received from a
local Db2. The DDM command contains an instance
variable which is not defined within DDM level 3.0 The
Explanation
instance variable (parameter) is invalid.

the local Db2.
The statistics class 4 trace record identified by the .
Collect the following diagnostic items at this Db2
remote server.
• Statistics Class 4 trace record identified by the IFCID period of time that spans the failure.
sequence number specified in message DSNL031I. • All dumps taken by the attachment facility or
Collect the following diagnostic items at the remote requesting application.
server. .
00D35C09
the failure.
• Any relevant AS trace information or dumps.
Explanation
00D35C08
Explanation command received from a local Db2. The value of the
DDM enumerated scalar, BNDCHKEXS, is invalid.
command received from a local Db2. Multiple System action
occurrences of a DDM instance variable, defined by
DDM Level 3 as nonrepeatable, have been processed
as parameters on this DDM command.
System action A DDM reply message (VALNSPRM) will be returned to

the local Db2.
Operator response
the local Db2.

items:
.
associated with the failing request. At this Db2 remote server, collect the following
.
At this Db2 remote server, collect the following was run, and a listing of the SYSLOG data set for the
diagnostic items listed in period of time that spans the failure.
.
requesting application. 00D35C0B
.
Explanation
00D35C0A
Explanation command received from a local Db2. The value of the
Db2 has detected an error while parsing a DDM DDM enumerated scalar, BNDEXPOPT, is invalid.
command received from a local Db2. The value of the System action
DDM enumerated scalar, BNDCRTCTL, is invalid.
An alert is generated and message DSNL032I is A DDM reply message (VALNSPRM) will be returned to
written to the console. Refer to the description of this the local Db2.
A DDM reply message (VALNSPRM) will be returned to Operator response
the local Db2.
Operator response
items:

.
.
was run, and a listing of the SYSLOG data set for the 00D35C0D
. BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
command received from a local Db2. The value of the
00D35C0C
DDM enumerated scalar, DECPRC, is invalid.

DDM enumerated scalar, BNDSTTASM, is invalid.
A DDM reply message (VALNSPRM) will be returned to
the local Db2.
System action

items:
.
.

00D35C0E Explanation
Explanation BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
Db2 has detected an error while parsing a DDM command received from a local Db2. The value of the
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND DDM enumerated scalar, PKGATHOPT, is invalid.
command received from a local Db2. Bytes 9 through
18 of the DDM scalar, DFTRDBCOL are other than System action
blank. While DDM defines the length of DFTRDBCOL
to be 18 bytes, Db2 supports only 8-byte collection An alert is generated and message DSNL032I is
identifiers. written to the console. Refer to the description of this
System action A DDM reply message (VALNSPRM) will be returned to

the local Db2.
Operator response
A DDM reply message (VALNSPRM) will be returned to Notify the system programmer.
the local Db2.

items:

.
period of time that spans the failure. 00D35C10
. Db2 has detected an error while parsing a DDM
00D35C0F BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
command received from a local Db2. The length of the
DDM scalar PKGDFTCC is invalid.

the local Db2.
the local Db2.
items:

period of time that spans the failure. 00D35C12
. Db2 has detected an error while parsing a
00D35C11 DDM BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or
REBIND command received from a local Db2. The
DDM PKGDFTCC collection consists of three DDM
Explanation scalars: CCSIDSBC, CCSIDMBC, and CCSIDDBC. The
Db2 has detected an error while parsing a PKGDFTCC collection contains multiple instances of
DDM BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or the CCSIDDBC scalar. This is invalid.
DDM PKGDFTCC collection consists of three DDM System action
scalars: CCSIDSBC, CCSIDMBC, and CCSIDDBC. The
PKGDFTCC collection contains multiple instances of An alert is generated and message DSNL032I is
the CCSIDSBC scalar. This is invalid. written to the console. Refer to the description of this
the local Db2.

items:
items: .
. • Console output from the system on which the job
period of time that spans the failure. .
• All dumps taken by the attachment facility or 00D35C14
. Explanation
00D35C13 Db2 has detected an error while parsing a
DDM BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or
Explanation REBIND command received from a local Db2. The
Db2 has detected an error while parsing a scalars: CCSIDSBC, CCSIDMBC, and CCSIDDBC. The
DDM BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or PKGDFTCC collection contains an invalid DDM object.
System action
scalars: CCSIDSBC, CCSIDMBC, and CCSIDDBC. The
PKGDFTCC collection contains multiple instances of An alert is generated and message DSNL032I is
the CCSIDMBC scalar. This is invalid. written to the console. Refer to the description of this
the local Db2.
the local Db2.
Operator response

IFCID sequence number enumerated in the DSNL032I .
message should be analyzed. At this Db2 remote server, collect the following
At this local Db2, collect the following diagnostic diagnostic items listed in
items: • Console output from the system on which the job
. • All dumps taken by the attachment facility or

diagnostic items listed in .
• Console output from the system on which the job 00D35C16

• All dumps taken by the attachment facility or Db2 has detected an error while parsing a DDM
requesting application. BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
. command received from a local Db2. The value of the
DDM enumerated scalar, PKGISOLVL, is invalid.
00D35C15
System action
Explanation
Db2 has detected an error while parsing a DDM written to the console. Refer to the description of this
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND message for further information.
DDM enumerated scalar, PKGDFTCST, is invalid. A DDM reply message (VALNSPRM) will be returned to
the local Db2.
System action
Operator response
A DDM reply message (VALNSPRM) will be returned to System programmer response
items:
items:

.
requesting application. 00D35C18
.
Explanation
00D35C17
Db2 has detected an error while parsing a DRDA
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, BNDCPY,
Explanation BNDDPLY, or REBIND command received from a
Db2 has detected an error while parsing a DDM remote DRDA requester. The DDM object PKGNAM,
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND PKGNAMCSN, or PKGID is invalid.
command received from a local Db2. The DDM object PKGNAMCSN
PKGNAM is a mapped scalar containing RDBNAM, If the DDM object is PKGNAMCSN, then either the
RDBCOLID and PKGID. Bytes 17 and 18 of the DDM section number is nonpositive (zero or a negative
scalar, RDBNAM, are other than blank. While DDM number) or the DDM scalar PKGID contains a
defines the length of RDBNAM to be 18 bytes, Db2 package identifier that is greater than 128 bytes
supports only a 16 byte RDBNAM. in length. Db2 supports package identifiers with a
maximum length of 128 bytes.
System action PKGNAM or PKGID
If the DDM object is PKGNAM or PKGID, then
the DDM scalar object PKGID contains a package
identifier that is greater than 128 bytes in length.
Db2 supports package identifiers with a maximum
A DDM reply message (VALNSPRM) will be returned to length of 128 bytes.
the local Db2.
System action
Operator response
Notify the system programmer. written to the console.
The DDM reply message VALNSPRM (parameter value
System programmer response not supported) is returned to the local Db2.

items:
. message should be analyzed.
At this Db2 remote server, collect the following At this local Db2, collect the following diagnostic
diagnostic items listed in items:
.

At this Db2 remote server, collect the following At this Db2 remote server, collect the following
diagnostic items listed in diagnostic items listed in
. .
Related information 00D35C1A
Explanation
00D35C19
Explanation
BNDDPLY, or REBIND command received from a
Db2 has detected an error while parsing a DDM remote DRDA requester. The DDM object PKGNAMCT
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND is invalid. The DDM scalar PKGID contains a package
command received from a local Db2. The DDM object identifier that is greater than 128 bytes in length. Db2
PKGNAMCT is a mapped scalar containing RDBNAM, supports package identifiers with a maximum length of
RDBCOLID, PKGID and PKGCNSTKN. Bytes 17 and 18 128 bytes.
of the DDM scalar, RDBNAM, are other than blank.
While DDM defines the length of RDBNAM to be 18 System action
bytes, Db2 supports only a 16 byte RDBNAM.
written to the console.
System action
not supported) is returned to the local Db2.
Operator response
the local Db2. Notify the system programmer.

items:
items: .
.

.
requesting application. 00D35C1C
.
Explanation
Related information
00D35C1B command received from a local Db2. The value of the
DDM enumerated scalar, QRYBLKCTL, is invalid.
Explanation
System action
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND An alert is generated and message DSNL032I is
command received from a local Db2. The value of the written to the console. Refer to the description of this
DDM enumerated scalar, PKGRPLOPT, is invalid. message for further information.

Operator response

.
was run, and a listing of the SYSLOG data set for the 00D35C1D

Db2 has detected an error while parsing a DDM An alert is generated and message DSNL032I is
BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND written to the console. Refer to the description of this
command received from a local Db2. Bytes 17 and message for further information.
18 of the DDM scalar, RDBNAM, are other than blank.
A DDM reply message (RDBNACRM) will be returned to
While DDM defines the length of RDBNAM to be 18
the local Db2.
bytes, Db2 supports only a 16 byte RDBNAM.

A DDM reply message (VALNSPRM) will be returned to If you suspect an error in Db2, you might need to
the local Db2. report the problem. For information about identifying
Operator response
items:
.
IFCID sequence number enumerated in the DSNL032I At this Db2 remote server, collect the following
message should be analyzed. diagnostic items listed in
.
.
diagnostic items listed in 00D35C1F
• All dumps taken by the attachment facility or BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
requesting application. command received from a local Db2. The value of the
DDM enumerated scalar, RDBRLSOPT, is invalid.
.
00D35C1E System action
Explanation
the local Db2.
RDBNAM scalar is other than the local Db2 RDBNAM.

items:

. command received from a local Db2. The value of the
DDM enumerated scalar, STTDECDEL, is invalid.
00D35C20
System action
Explanation
DDM enumerated scalar, STTDATFMT, is invalid. A DDM reply message (VALNSPRM) will be returned to
the local Db2.
System action
Operator response




. command received from the local Db2. The value of
the DDM enumerated scalar, STTTIMFMT, is invalid.
00D35C22
System action
Explanation
DDM enumerated scalar, STTSTRDEL, is invalid. A DDM reply message (VALNSPRM) will be returned to
the local Db2.
System action
Operator response
items:
items:

00D35C25
00D35C24 command received from a local Db2. The length of a
DDM object is less than 4, the minimum length of any
Explanation DDM object. This is invalid.

System action
command received from a local Db2. The DDM An alert is generated and message DSNL032I is
TIMESTAMP scalar has been received as a command written to the console. Refer to the description of this
parameter from a database other than Db2. The message for further information.
TIMESTAMP scalar is private to Db2.
the local Db2.
System action

the local Db2.

items:
.
.
00D35C26

BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND written to the console. Refer to the description of this
command received from a local Db2. The length of the message for further information.
DDM command is less than the sum of the lengths
of the constituent instance variables appearing as
the local Db2.
parameters.

A DDM reply message (SYNTAXRM) will be returned to If you suspect an error in Db2, you might need to
Operator response
items:
.
message should be analyzed. diagnostic items listed in
.
.
diagnostic items listed in 00D35C28
• All dumps taken by the attachment facility or BGNBND, BNDSQLSTT, ENDBND, DRPPKG, or REBIND
requesting application. command received from a local Db2. The length of a
DDM object is less than the length defined by DDM
00D35C27
Level 3. This is invalid.

command received from a local Db2. The length of a
DDM object exceeds the length defined by DDM Level
3. This is invalid.

A DDM reply message (SYNTAXRM) will be returned to A DDM reply message (VALNSPRM) will be returned to
the local Db2. the local Db2.



At this local Db2, collect the following diagnostic Collect the following diagnostic items at this local Db2.
items:
• Statistics Class 4 trace record for the LUWID sequence number specified in message DSNL031I.
. server.
At this Db2 remote server, collect the following • Relevant error and system logs spanning the time of
diagnostic items listed in the failure.
• Console output from the system on which the job • Any relevant AS trace information or dumps.
00D35C2A
Explanation
.
00D35C29 command received from the local Db2. The value of
MAXSCTNBR received on the ENDBND command is
invalid. The value must be within the range 1 to 32767
Explanation
inclusive.
command or DDM BGNBND, BNDSQLSTT, ENDBND, System action
DRPPKG, or REBIND command received from a
local Db2. A package related identifier or collection An alert is generated and message DSNL031I is
identifier is in violation of the SAA syntax. This is written to the console. Refer to the description of this
either the collection identifier (DFTRDBCOL) received message for further information.
on a BGNBND or REBIND command or the package
identifier or collection identifier within the PKGNAM,
the local Db2.
PDGNAMCT, or PKGNAMCSN mapped scalars received
on a BGNBND, BNDSQLSTT, ENDBND, or DRPPKG
command. Operator response
System action

and reporting the problem, see Collecting diagnostic In addition, identify all connected systems
data (Collecting data). participating in the processing of the remote request.
Problem determination application is connected and the data server which is
The statistics class 4 trace record identified by the intermediate server systems. For each system that is a
IFCID sequence number enumerated in the DSNL031I Db2 system, collect the following diagnostic items:
Collect the following diagnostic items at this local Db2. set from each connected site for the period of time
sequence number specified in message DSNL031I. For non-Db2 systems, refer to the documentation
server. If any dumps were generated on any Db2 system
the failure.
• Any relevant AS trace information or dumps. • Listings of the SYS1.LOGREC data set, obtained by
00D35C2E
Explanation 00D35C2F
Db2 detected an error in a DDM BGNBND command

Explanation
received from a remote requester. The value of the
enumerated scalar, PRPSTTKP, is invalid. Db2 has detected an error while parsing a DDM
BGNBND, REBIND, BNDCPY, BNDDPLY command
System action received from a remote requester. The DDM object
PKGOWNID has the length more than 128 bytes.
System action
A DDM reply message (VALNSPRM) is returned to the
remote requester.
Operator response A DDM reply message (VALNSPRM) is returned to the

remote requester.
Operator response
diagnostic items:

In addition, identify all connected systems by the IFCID sequence number enumerated in the
participating in the processing of the remote request. DSNL032I message. For the Db2 system generating
This includes the requester system to which the the DSNL032I message, collect the following
application is connected and the data server which is diagnostic items:
intermediate server systems. For each system that is a • Statistics Class 4 trace record for the LUWID
Db2 system, collect the following diagnostic items: associated with the failing request.
• Console output and the listing of the SYSLOG data In addition, identify all connected systems
set from each connected site for the period of time participating in the processing of the remote request.
spanning the failure. This includes the requester system to which the
For non-Db2 systems, refer to the documentation the target of the remote request. This may also include
specific to those products for diagnostic procedures. intermediate server systems. For each system that is a
If any dumps were generated on any Db2 system Db2 system, collect the following diagnostic items:
participating in processing the remote request, collect • Console output and the listing of the SYSLOG data
the following diagnostic items: set from each connected site for the period of time
• Listings of the SYS1.LOGREC data set, obtained by spanning the failure.
executing IFCEREP1 at each connected site. For non-Db2 systems, refer to the documentation
• All dumps created by this failure. specific to those products for diagnostic procedures.
00D35C30 If any dumps were generated on any Db2 system

Explanation
Db2 has detected an error while parsing a executing IFCEREP1 at each connected site.
DDM DRPPKG command received from a remote
requester. Db2 has received a wild card instance • All dumps created by this failure.
variable RDBCOLIDANY, but neither instance variable 00D35C31
PKGIDANY nor instance variable PKGID is received.
When RDBCOLIDANY is present, PKGIDANY or PKGID
must be specified. The request is invalid. Explanation
System action DRPPKG command received from a remote requester.
Db2 has received a wild card PKGIDANY instance
An alert is generated and message DSNL032I is variable, but neither RDBCOLIDANY nor COLID is
written to the console. Refer to the description of this received. When PKGIDANY is present, RDBCOLIDANY
message for more information. or COLID must be specified. The request is invalid.
remote requester. System action
Notify the system programmer. message for more information.
System programmer response remote requester.

and reporting the problem, see Collecting diagnostic Notify the system programmer.

00D35C32 • Listings of the SYS1.LOGREC data set, obtained by

Db2 has detected an error while parsing a DDM 00D35C33

BNDCPY command received from a remote requester.
An invalid instance variable has been received as a Explanation
parameter on an BNDCPY command.
BNDDPLY command received from a remote requester.
System action An invalid instance variable has been received as a
An alert is generated and message DSNL032I is parameter on an BNDDPLY command.
message for more information. System action
A DDM reply message (PRMNSPRM)) is returned to the An alert is generated and message DSNL032I is
Operator response A DDM reply message (PRMNSPRM) is returned to the
Operator response

00D35C34 • Listings of the SYS1.LOGREC data set, obtained by
Db2 has detected an error while parsing a DDM 00D35C35
DRPPKG command received from a remote requester.
Db2 received both the VRSNAMANY instance variable Explanation
and the VRSNAM instance variable in the DDM
DRPPKG command. VRSNAMANY and VRSNAM are Db2 has detected an error while parsing a DRDA
mutually exclusive. This is invalid. BGNBND, BNDSQLSTT, ENDBND, DRPPKG, BNDCPY,
BNDDPLY, or REBIND command received from a
remote DRDA requester. The DDM object RDBCOLID,
System action
PKGNAM, PKGMANCT, or PKGNAMCSN is invalid. The
An alert is generated and message DSNL032I is DDM scalar RDBCOLID contains a collection ID that
written to the console. Refer to the description of this is greater than 128 bytes in length. Db2 supports
message for further information. collection IDs with a maximum length of 128 bytes.
remote requester.

the local Db2.
Operator response
not supported) is returned to the remote requester. Notify the system programmer.

Analyze the statistics class 4 trace record identified items:
DSNL032I message. • Statistics Class 4 trace record for the LUWID
items: .
At this Db2 remote server, collect the following • Console output from the system on which the job
• All dumps taken by the attachment facility or .

requesting application. 00D35D02
Related information
DSNL032I (Db2 Messages) Explanation
00D35D01 Db2 has detected an error while parsing a DDM
command received from a local Db2. An instance
variable, defined as valid by DDM Level 3, but not
Explanation supported by Db2, has been detected on a DDM
Db2 has detected an error while parsing a DDM CNTQRY command.
variable, defined as valid by DDM Level 3, but not System action
supported by Db2, has been detected on one of
the following DDM commands: CLSQRY, DSCRDBTBL, An alert is generated and message DSNL032I is
DSCSQLSTT, or EXCSQLIMM. written to the console. Refer to the description of this
the local Db2.

items:

period of time that spans the failure. 00D35D04
00D35D03 command received from a local Db2. An instance
variable, defined as valid by DDM Level 3, but not
supported by Db2, has been detected on a DDM
Explanation EXCSQLSTT command.
command received from a local Db2. The value of System action
the DDM OUTEXP enumerated value instance variable,
contained within a DDM EXCSQLSTT command, is An alert is generated and message DSNL032I is
other than FALSE (X'F0') or TRUE (X'F1'). written to the console. Refer to the description of this
the local Db2.
A DDM reply message (VALNSPRM) will be returned to Notify the system programmer.
the local Db2.
items:
.

At this Db2 remote server, collect the following Explanation
• Console output from the system on which the job command received from a remote requester. An
was run, and a listing of the SYSLOG data set for the OPNQRY command was received containing an
period of time that spans the failure. instance variable that is not supported at the DDM
• All dumps taken by the attachment facility or level negotiated during CONNECT processing.
. System action
00D35D05 An alert is generated and message DSNL032I is
Explanation
A DDM reply message (PRMNSPRM) is returned to the
Db2 has detected an error while parsing a DDM remote requester.
command received from a local Db2. The value of DDM
QRYBLKCTL instance variable, received as a parameter
on OPNQRY, is other than FRCSNGROW. The local Operator response
Db2 may not specify LMTBLKPRC or SNGROWPRC as Notify the system programmer.
values of QRYBLKCTL as an OPNQRY parameter.
System action
An alert is generated and message DSNL032I is report the problem. For information about identifying
written to the console. Refer to the description of this and reporting the problem, see Collecting diagnostic
message for further information. data (Collecting data).
the local Db2. Problem determination
Operator response by the IFCID sequence number enumerated in the
Notify the system programmer. DSNL032I message. For the Db2 system generating
diagnostic items:
If you suspect an error in Db2, you might need to associated with the failing request.
and reporting the problem, see Collecting diagnostic In addition, identify all connected systems
data (Collecting data). participating in the processing of the remote request.
At this local Db2, collect the following diagnostic application is connected and the data server which is
items: the target of the remote request. This may also include
• Statistics Class 4 trace record for the LUWID intermediate server systems. For each system that is a
associated with the failing request. Db2 system, collect the following diagnostic items:
. • Console output and the listing of the SYSLOG data

At this Db2 remote server, collect the following spanning the failure.
• Console output from the system on which the job specific to those products for diagnostic procedures.
period of time that spans the failure. If any dumps were generated on any Db2 system
.
00D35D06 • All dumps created by this failure.

00D35D07 variable, defined as valid by DDM Level 3, but not
PRPSQLSTT command.
Explanation
DDM RTNSQLDA enumerated value instance variable, An alert is generated and message DSNL032I is
contained within a DDM EXCSQLSTT command, is written to the console. Refer to the description of this
other than FALSE (X'F0') or TRUE (X'F1'). message for further information.
.
items:
diagnostic items listed in requesting application.

was run, and a listing of the SYSLOG data set for the 00D35D09
Explanation
.
00D35D08 variable, defined as valid by DDM Level 3, but not
RDBCMM or RDBRLLBCK command.
Explanation

the local Db2.
The statistics class 4 trace record identified by the .
items:
. requesting application.
At this Db2 remote server, collect the following .
00D35D0B
requesting application. command received from a local Db2. One or more
instance variables, defined by DDM Level 3 as required
. for this command, were not received as command
parameters.
00D35D0A

command received from a local Db2. The length of the
DDM command is not equal to the sum of the lengths
of the constituent instance variables. A DDM reply message (SYNTAXRM) will be returned to
the local Db2.
System action
Operator response
the local Db2.

items:
.
items:
00D35D0D
Explanation
requesting application. Db2 has detected an error while parsing a DDM
. command received from a local Db2. Multiple
occurrences of one or more instance variables, defined
00D35D0C by DDM level 3 as nonrepeatable, have been received
as parameters of this DDM command.
Explanation
System action
command received from a local Db2. An instance An alert is generated and message DSNL032I is
variable, defined by DDM Level 3 as not valid for written to the console. Refer to the description of this
this command, has been received as a command message for further information.
parameter.
the local Db2.
System action
A DDM reply message (PRMNSPRM) will be returned to System programmer response
the local Db2.
Operator response


.
.
was run, and a listing of the SYSLOG data set for the 00D35D0F
. command received from a local Db2. The value of
the RDBNAM instance variable is different than that
00D35D0E
received on the ACCRDB command.

command received from a local Db2. Bytes 17 and
18 of the DDM scalar, RDBNAM, are other than blank.
While DDM Level 3 defines the length of this scalar to
be 18 bytes, Db2 supports only a 16 byte RDBNAM. A DDM reply message (RDBNACRM) will be returned to
the local Db2.
System action
Operator response
items:
items:

. The DDM object PKGNAMCSN is invalid. Either the
section number is nonpositive (zero or a negative
00D35D10 number) or the DDM scalar PKGID contains a package
identifier that is greater than 128 bytes in length. Db2
Explanation supports package identifiers with a maximum length of
128 bytes.
command received from a local Db2. The mapped
scalar, PKGNAMCSN, is invalid. Bytes 17 and 18 of the System action
DDM scalar RDBNAM, contained within PKGNAMCSN, An alert is generated and message DSNL032I is
are other than blank. While DDM Level 3 defines the written to the console.
length of this scalar to be 18 bytes, Db2 supports only
a 16 byte RDBNAM. The DDM reply message VALNSPRM (parameter value
System action
Operator response
A DDM reply message (SYNTAXRM) will be returned to System programmer response
If you suspect an error in Db2, you might need to by the IFCID sequence number enumerated in the
report the problem. For information about identifying DSNL032I message.
items:
message should be analyzed. diagnostic items:
diagnostic items: Related information
was run, and a listing of the SYSLOG data set for the 00D35D12
Explanation
00D35D11 command received from a local Db2. The value of the
DDM scalar, QRYBLKSZ, contained as a parameter on
Explanation a DDM OPNQRY, CNTQRY, or EXCSQLSTT command, is
invalid.The value of QRYBLKSZ must be between 512
and 32767, inclusive.
command received from a remote DRDA requester.

the local Db2.
DSNL032I message.
Analyze the statistics class 4 trace record identified At this Db2 remote server, collect the following
by the IFCID sequence number enumerated in the diagnostic items:
DSNL032I message.
At this Db2 remote server, collect the following 00D35D14
diagnostic items:
command received from a local Db2. The length of
• All dumps taken by the attachment facility or one or more instance variables received as command
requesting application. parameters is less than 4. This is the minimum length
to support a DDM length and code point (llcp).
00D35D13
System action
Explanation
command received from a local Db2. a TIMESTAMP
instance variable has been included as a command
parameter received from a database other than Db2. A DDM reply message (SYNTAXRM) will be returned to
This DDM scalar is private to Db2. the local Db2.

the local Db2.

Problem determination At this Db2 remote server, collect the following
diagnostic items:
by the IFCID sequence number enumerated in the • Console output from the system on which the job
DSNL032I message. was run, and a listing of the SYSLOG data set for the
associated with the failing request. 00D35D16

was run, and a listing of the SYSLOG data set for the command received from a local Db2. The length
period of time that spans the failure. of an instance variable received as a command
parameter exceeds the length of the instance variable,
• All dumps taken by the attachment facility or as specified by DDM Level 3.
00D35D15 System action
command received from a local Db2. The length of the A DDM reply message (SYNTAXRM) will be returned to
DDM command is less than the sum of the lengths of the local Db2.
all constituent instance variables.
Operator response
System action
Operator response
System programmer response by the IFCID sequence number enumerated in the
The statistics class 4 trace record identified by the diagnostic items:
message should be analyzed. • Console output from the system on which the job
items:
00D35D17

command received from a local Db2. The length of an written to the console. Refer to the description of this
instance variable received as a command parameter message for further information.
is less than the length of the instance variable, as
specified by DDM Level 3.
the DRDA requester.
System action
Operator response
Operator response
If you suspect an error in Db2, you might need to by the IFCID sequence number given in message
report the problem. For information about identifying DSNL032I.
If the DRDA requester is Db2 for z/OS, then Db2
diagnostic information is available. In this case, at the
Db2 requester, collect the following diagnostic items:
Analyze the statistics class 4 trace record identified was run, and a listing of the SYSLOG data set for the
by the IFCID sequence number enumerated in the period of time that spans the failure.
DSNL032I message.
At the Db2 server, collect the following diagnostic
items:
At this Db2 remote server, collect the following • Statistics Class 4 trace record for the LUWID
diagnostic items: associated with the failing request.
• Console output from the system on which the job 00D35D19
requesting application. Db2, acting as a DRDA server, has detected an error
while parsing a DDM DSCSQLSTT command received
00D35D18 from a remote DRDA client. The value of the DDM
enumerated scalar TYPSQLDA is invalid.
Explanation
System action
command received from a DRDA requester. The value An alert is generated and message DSNL032I is
of the DDM scalar, MAXRSLCNT, contained as a written to the console. Refer to the description of this
parameter on a DDM EXCSQLSTT command, is invalid. message for further information.
The value of MAXRSLCNT must be greater than or
equal to -1.
the remote DRDA client.

If the remote DRDA client is a Db2 for z/OS system, at
the DRDA client, collect the following diagnostic items:
If the remote DRDA client is a Db2 for z/OS, at the
DRDA client, collect the following diagnostic items: For other remote DRDA clients, refer to the
recommendations.
For other remote DRDA clients, refer to the
diagnostic items:
recommendations. • Console output from the system on which the job
diagnostic items:
period of time that spans the failure. .
• All dumps taken by the attachment facility or 00D35D1B
00D35D1A Explanation
Db2, acting as a DRDA server, has detected an
Explanation error while parsing a DDM OPNQRY or EXCSQLSTT
command received from a remote DRDA client. The
value of the DDM enumerated scalar OUTOVROPT is
while parsing a DDM DSCSQLSTT command received
invalid.
from a remote DRDA client. An instance variable,
defined as valid by DDM Level 5, but not supported
by Db2, has been detected on a DDM DSCSQLSTT System action
command.
An alert is generated and message DSNL032I is A DDM reply message (VALNSPRM) will be returned to
written to the console. Refer to the description of this the remote DRDA client.
A DDM reply message (PRMNSPRM) will be returned to Operator response
Operator response

The statistics class 4 trace record identified by the If the remote DRDA client is a Db2 for z/OS system, at
IFCID sequence number enumerated in the DSNL032I the Db2 DRDA client, collect the following diagnostic
If the remote DRDA client is a Db2 for z/OS system, at • Statistics Class 4 trace record for the LUWID
the Db2 DRDA client, collect the following diagnostic associated with the failing request.
items:
. For other remote DRDA clients, refer to
• Statistics Class 4 trace record for the LUWID the client product documentation for diagnostic
associated with the failing request. recommendations.
. For other remote DRDA clients, refer to At the Db2 DRDA server, collect the following
the client product documentation for diagnostic diagnostic items:
recommendations.
At the Db2 DRDA server, collect the following was run, and a listing of the SYSLOG data set for the
diagnostic items: period of time that spans the failure.
.
requesting application. 00D35D1D
.
Explanation
00D35D1C
received from DRDA requester. The value of the DDM
Explanation QRYSCRORN enumerated value instance variable,
Db2, acting as a DRDA server, has detected an error contained within a DDM CNTQRY command, is
while parsing a DDM CNTQRY command received unrecognized.
from a remote DRDA client. The value of the DDM
enumerated scalar RTNEXTDTA is invalid. System action
System action to the console. Refer to the description of this message
An alert is generated and message DSNL032I is for further information.
written to the console. Refer to the description of this A DDM reply message (VALNSPRM) will be returned to
message for further information. the DRDA requester.
the remote DRDA client. Operator response
Notify the System Programmer.
Operator response
Notify the system programmer. System programmer response
If you suspect an error in Db2, you might need to and reporting the problem, see Collecting diagnostic
report the problem. For information about identifying data (Collecting data).

by the IFCID sequence number enumerated in the .
DSNL031I message. At this remote server, collect the following diagnostic
If the DRDA requester is also a Db2 for z/OS system, items:
then at the requester Db2 system, collect the following • All dumps taken by the attachment facility or
• Statistics Class 4 trace record for the LUWID .
00D35D1F
.
items:
• All dumps taken by the attachment facility or CNTQRY command received from a DRDA requester.
requesting application. The value of the QRYROWSET instance value is zero,
. but the minimum defined value for this instance
variable on a CNTQRY command is one.
00D35D1E
System action
Explanation
Db2 detected an error while parsing a DDM command to the console. Refer to the description of this message
received from a DRDA requester. The value of the for further information.
QRYROWSET instance variable on an OPNQRY or
CNTQRY command is less than zero. The minimum A DDM reply message (SYNTAXRM) will be returned to
defined value for this instance variable is zero. the DRDA requester.

Db2 generates an alert, and writes message DSNL032I Notify the System Programmer.
for further information. System programmer response
the DRDA requester. report the problem. For information about identifying

and reporting the problem, see Collecting diagnostic If the DRDA requester is also a Db2 for z/OS system,
data (Collecting data). then at the requester Db2 system, collect the following
diagnostic items:
by the IFCID sequence number enumerated in the .
DSNL031I message. At this remote server, collect the following diagnostic
If the DRDA requester is also a Db2 for z/OS system, items:
then at the requester Db2 system, collect the following • All dumps taken by the attachment facility or

. System action
00D35D20 Db2 generates an alert, and writes message DSNL032I
Explanation for further information.
Db2 has detected an error while parsing a DDM A DDM reply message (VALNSPRM)) will be returned to
command received from a DRDA requester. The the DRDA requester.
value of the QRYROWSET instance variable on an
EXCSQLSTT is less than zero. The minimum defined Operator response
value for this instance variable is zero.
System action
to the console. Refer to the description of this message If you suspect an error in Db2, you might need to
for further information. report the problem. For information about identifying
A DDM reply message (SYNTAXRM) will be returned to data (Collecting data).
the DRDA requester.
Operator response
Notify the System Programmer. by the IFCID sequence number enumerated in the
DSNL031I message.
System programmer response If the DRDA requester is also a Db2 for z/OS system,
If you suspect an error in Db2, you might need to then at the requester Db2 system, collect the following
report the problem. For information about identifying diagnostic items:
Analyze the statistics class 4 trace record identified • All dumps taken by the attachment facility or
by the IFCID sequence number enumerated in the requesting application.
DSNL031I message.
00D35D22
If the DRDA requester is also a Db2 for z/OS system,
then at the requester Db2 system, collect the following
• Statistics Class 4 trace record for the LUWID Db2 has detected an error while parsing a DDM
associated with the failing request. command received from a DRDA requester. The value
of the DDM QRYRTNDTA enumerated value instance
At this remote server, collect the following diagnostic variable, contained within a DDM CNTQRY command,
items: is other than FALSE (X'F0') or TRUE (X'F1').
00D35D21 Db2 generates an alert, and writes message DSNL032I
Explanation for further information.
Db2 detected an error while parsing a DDM command A DDM reply message (VALNSPRM)) will be returned to
received from a DRDA requester. The value of the the DRDA requester.
DDM QRYRSTBLK enumerated value instance variable,
contained within a DDM CNTQRY command, is other Operator response
than FALSE (X'F0') or TRUE (X'F1').

System programmer response the DSNL032I message, collect the following
diagnostic items:
data (Collecting data). In addition, identify all connected systems
Problem determination This includes the requester system to which the
Analyze the statistics class 4 trace record identified the target of the remote request. This may also include
by the IFCID sequence number enumerated in the intermediate server systems. For each system that is a
DSNL031I message. Db2 system, collect the following diagnostic items:
If the DRDA requester is also a Db2 for z/OS system, • Console output and the listing of the SYSLOG data
then at the requester Db2 system, collect the following set from each connected site for the period of time
diagnostic items: spanning the failure.
• Statistics Class 4 trace record for the LUWID For non-Db2 systems, refer to the documentation
associated with the failing request. specific to those products for diagnostic procedures.
At this remote server, collect the following diagnostic If any dumps were generated on any Db2 system
items: participating in processing the remote request, collect
• All dumps taken by the attachment facility or the following diagnostic items:
requesting application. • Listings of the SYS1.LOGREC data set, obtained by
00D35D23 executing IFCEREP1 at each connected site.
Explanation 00D35D24
RDBCMM or RDBRLLBCK command received from a Explanation
remote requester. The value of the DDM enumerated
scalar RLSCONV is invalid. Db2 has detected an error while parsing a DDM
EXCSQLSTT command received from a remote
requester. The value of the DDM enumerated scalar
System action NBRROW is invalid.
A DDM reply message (VALNSPRM) is returned to the written to the console. Refer to the description of this
remote requester. message for further information.
Operator response remote requester.
Operator response

by the IFCID sequence number enumerated in the by the IFCID sequence number enumerated in the
DSNL032I message. For the Db2 system generating DSNL032I message. For the Db2 system generating
the DSNL032I message, collect the following the DSNL032I message, collect the following
diagnostic items: diagnostic items:
In addition, identify all connected systems In addition, identify all connected systems
participating in the processing of the remote request. participating in the processing of the remote request.
This includes the requester system to which the This includes the requester system to which the
application is connected and the data server which is application is connected and the data server which is
the target of the remote request. This may also include the target of the remote request. This may also include
intermediate server systems. For each system that is a intermediate server systems. For each system that is a
Db2 system, collect the following diagnostic items: Db2 system, collect the following diagnostic items:
• Console output and the listing of the SYSLOG data • Console output and the listing of the SYSLOG data
set from each connected site for the period of time set from each connected site for the period of time
spanning the failure. spanning the failure.
For non-Db2 systems, refer to the documentation For non-Db2 systems, refer to the documentation
specific to those products for diagnostic procedures. specific to those products for diagnostic procedures.
If any dumps were generated on any Db2 system If any dumps were generated on any Db2 system
participating in processing the remote request, collect participating in processing the remote request, collect
the following diagnostic items: the following diagnostic items:
• Listings of the SYS1.LOGREC data set, obtained by • Listings of the SYS1.LOGREC data set, obtained by
executing IFCEREP1 at each connected site. executing IFCEREP1 at each connected site.
• All dumps created by this failure. • All dumps created by this failure.
00D35D25 00D35D27
Db2 has detected an error while parsing a DDM Db2 has detected an error while parsing a DDM
CNTQRY command received from a remote requester. GETNXTCHK command received from a remote
The value of the DDM enumerated scalar FREPRVREF requester. The value of the DDM enumerated scalar
is invalid. FREREFOPT is invalid.

A DDM reply message (VALNSPRM) is returned to the A DDM reply message (VALNSPRM) is returned to the
remote requester. remote requester.



DSNL032I message. For the Db2 system generating DSNL032I message. For the Db2 system generating
the DSNL032I message, collect the following the DSNL032I message, collect the following
In addition, identify all connected systems In addition, identify all connected systems
participating in the processing of the remote request. participating in the processing of the remote request.
This includes the requester system to which the This includes the requester system to which the
application is connected and the data server which is application is connected and the data server which is
the target of the remote request. This may also include the target of the remote request. This may also include
intermediate server systems. For each system that is a intermediate server systems. For each system that is a
Db2 system, collect the following diagnostic items: Db2 system, collect the following diagnostic items:
• Console output and the listing of the SYSLOG data • Console output and the listing of the SYSLOG data
set from each connected site for the period of time set from each connected site for the period of time
spanning the failure. spanning the failure.
For non-Db2 systems, refer to the documentation For non-Db2 systems, refer to the documentation
specific to those products for diagnostic procedures. specific to those products for diagnostic procedures.
If any dumps were generated on any Db2 system If any dumps were generated on any Db2 system
participating in processing the remote request, collect participating in processing the remote request, collect
the following diagnostic items: the following diagnostic items:
• Listings of the SYS1.LOGREC data set, obtained by • Listings of the SYS1.LOGREC data set, obtained by
executing IFCEREP1 at each connected site. executing IFCEREP1 at each connected site.
• All dumps created by this failure. • All dumps created by this failure.
00D35D28 00D35D29
Db2 has detected an error while parsing a DDM Db2 has detected an error while parsing a DDM
EXCSQLSTT or OPNQRY command received from a GETNXTCHK command received from a remote
remote requester. The value of the DDM enumerated requester. The value of the DDM enumerated scalar
scalar DYNDTAFMT is invalid. REFRST is invalid.

A DDM reply message (VALNSPRM) is returned to the A DDM reply message (VALNSPRM) is returned to the
remote requester. remote requester.



DSNL032I message. For the Db2 system generating DSNL032I message.
diagnostic items:
This includes the requester system to which the At the Db2 remote server, collect the following
application is connected and the data server which is diagnostic items:
• Console output and the listing of the SYSLOG data • All dumps created by this failure.
spanning the failure. Related information
00D35D2B
participating in processing the remote request, collect Explanation
• Listings of the SYS1.LOGREC data set, obtained by OPNQRY or CLSQRY command that was received from
executing IFCEREP1 at each connected site. a remote requester. The value of the DDM enumerated
• All dumps created by this failure. scalar QRYCLSRLS is invalid.
00D35D2A
System action
OPNQRY command that was received from a remote A DDM reply message (VALNSPRM) is returned to the
requester. The value of the DDM enumerated scalar remote requester.
QRYCLSIMP is invalid.
Operator response
System action
written to the console. System programmer response
A DDM reply message (VALNSPRM) is returned to the If you suspect an error in Db2, you might need to
remote requester. report the problem. For information about identifying
DSNL032I message.
and reporting the problem, see Collecting diagnostic At this local Db2, collect the following diagnostic item:

specific to those products for diagnostic procedures. • All dumps created by this failure.
At the Db2 remote server, collect the following Related information
diagnostic items: DSNL032I (Db2 Messages)
• Console output from the system on which the job 00D35D2D
Explanation
Related information
OPNQRY or EXCSQLSTT command that was received
DSNL032I (Db2 Messages) from a remote requester. The value of the DDM
enumerated scalar DFTFMTXML is invalid.
00D35D2C
System action
Explanation
OPNQRY or EXCSQLSTT command that was received
from a remote requester. The value of the DDM A DDM reply message (VALNSPRM) is returned to the
enumerated scalar OUTOVRXML is invalid. remote requester.

A DDM reply message (VALNSPRM) is returned to the System programmer response
remote requester. If you suspect an error in Db2, you might need to
DSNL032I message.
data (Collecting data). At this local Db2, collect the following diagnostic item:
Analyze the statistics class 4 trace record identified For non-Db2 systems, refer to the documentation
by the IFCID sequence number enumerated in the specific to those products for diagnostic procedures.
DSNL032I message.
At the Db2 remote server, collect the following
At this local Db2, collect the following diagnostic item: diagnostic items:
specific to those products for diagnostic procedures. • All dumps created by this failure.
At the Db2 remote server, collect the following Related information

diagnostic items: DSNL032I (Db2 Messages)

00D35D2E Explanation
Explanation command or DDM command data. An invalid RDBNAM
Db2 has detected an error while parsing a DRDA length was sent on an ACCSEC command.
BNDDPLY, or REBIND command received from a System action
remote DRDA requester. The DDM object RDBCOLID,
PKGNAM, PKGMANCT, or PKGNAMCSN is invalid. The If the length of the RDBNAM is greater than 18, then
DDM scalar RDBCOLID contains a collection ID that A DDM reply message (SYNTAXRM) is returned to the
is greater than 128 bytes in length. Db2 supports DRDA client. If the data in characters 17-18 of the
collection IDs with a maximum length of 128 bytes. RDBNAME is non-blank, then a DDM reply message
(VALNSPRM) is returned to the DRDA client.
System action
Operator response
written to the console. Notify the system programmer.


and reporting the problem, see Collecting diagnostic DSNL032I message.

by the IFCID sequence number enumerated in the At this remote server, collect the following diagnostic
DSNL032I message. items:
00D35E01
diagnostic items:
Explanation
• All dumps taken by the attachment facility or command or DDM command data. An ACCSEC or
requesting application. SECCHK command was sent without one or more of
its required DDM instance variables.
Related information
System action
00D35E00 A DDM reply message (SYNTAXRM) is returned to the
local Db2.

items:
• Statistics Class 4 trace record for the LUWID 00D35E03
items:
• Console output from the system on which the job command or DDM command data. An invalid instance
was run, and a listing of the SYSLOG data set for the variable was sent on an ACCSEC command.
00D35E02 local Db2.

Db2 has detected an error while parsing a DDM Notify the system programmer.
command or DDM command data. An ACCSEC or
SECCHK command was sent with the RQSDSS length System programmer response
fields set improperly.
System action
A DDM reply message (SYNTAXRM) is returned to the data (Collecting data).
local Db2.
Operator response
Notify the system programmer. by the IFCID sequence number enumerated in the
DSNL032I message.
System programmer response At this local Db2, collect the following diagnostic item:
items:

• All dumps taken by the attachment facility or Operator response
00D35E04
Explanation
Db2 has detected an error while parsing a DDM report the problem. For information about identifying
command or DDM command data. A duplicate instance and reporting the problem, see Collecting diagnostic
variable was sent on an ACCSEC command. data (Collecting data).

A DDM reply message (SYNTAXRM) is returned to the Analyze the statistics class 4 trace record identified
local Db2. by the IFCID sequence number enumerated in the
DSNL032I message.
Operator response At this local Db2, collect the following diagnostic item:
Notify the system programmer. • Statistics Class 4 trace record for the LUWID
System programmer response At this remote server, collect the following diagnostic
report the problem. For information about identifying • Console output from the system on which the job
and reporting the problem, see Collecting diagnostic was run, and a listing of the SYSLOG data set for the
data (Collecting data). period of time that spans the failure.
Problem determination requesting application.
Analyze the statistics class 4 trace record identified 00D35E06
DSNL032I message.
Explanation
• Statistics Class 4 trace record for the LUWID command or DDM command data. An invalid SECMEC
associated with the failing request. length was sent on an ACCSEC command. Only one
At this remote server, collect the following diagnostic SECMEC can be specified.
items:
System action
was run, and a listing of the SYSLOG data set for the A DDM reply message (SYNTAXRM) is returned to the
period of time that spans the failure. local Db2.
requesting application. Operator response
00D35E05 Notify the system programmer.

Db2 has detected an error while parsing a DDM If you suspect an error in Db2, you might need to
command or DDM command data. An invalid report the problem. For information about identifying
SECMGRNM length was sent on an ACCSEC command. and reporting the problem, see Collecting diagnostic
The SECMGRNM must be null. data (Collecting data).
System action
local Db2.

Problem determination • All dumps taken by the attachment facility or
IFCID sequence number enumerated in the DSNL032I 00D35E08
At this local Db2, collect the following diagnostic item: Explanation
associated with the failing request. command or DDM command data. A duplicate instance
variable was sent on a SECCHK command.
items:
System action
period of time that spans the failure. local Db2.

command or DDM command data. An invalid instance report the problem. For information about identifying
variable was sent on a SECCHK command. and reporting the problem, see Collecting diagnostic
System action
local Db2. The statistics class 4 trace record identified by the
Operator response
and reporting the problem, see Collecting diagnostic • Console output from the system on which the job
data (Collecting data). was run, and a listing of the SYSLOG data set for the
associated with the failing request. command or DDM command data. An invalid
SECMGRNM length was sent on a SECCHK command.
At this remote server, collect the following diagnostic The SECMGRNM must be null.
items:
period of time that spans the failure. A DDM reply message (SYNTAXRM) is returned to the
local Db2.

items:
• Statistics Class 4 trace record for the LUWID 00D35E0B
items:
• Console output from the system on which the job command or DDM command data. An invalid RDBNAM
was run, and a listing of the SYSLOG data set for the length was sent on a SECCHK command.
00D35E0A DRDA client.

command or DDM command data. An invalid SECMEC
length was sent on a SECCHK command. Only one System programmer response
SECMEC can be specified.
System action
local Db2.
Operator response
Notify the system programmer. IFCID sequence number enumerated in the DSNL032I
items:

00D35E0C local Db2.

command or DDM command data. An invalid USERID
length was sent on a SECCHK command. Db2 user IDs
cannot exceed 8 bytes.
local Db2.
Operator response
Notify the system programmer. by the IFCID sequence number enumerated in the
DSNL032I message should be analyzed.
data (Collecting data). At this remote server, collect the following diagnostic
items:
00D35E0E
Explanation
items: Db2 has detected an error in the DDM command data
object or DDM reply data object received from the
• Console output from the system on which the job remote server as part of a DDM command or reply.
was run, and a listing of the SYSLOG data set for the The sum of the lengths of the constituent DDM objects
period of time that spans the failure. within an OBJDSS is inconsistent with the length of the
• All dumps taken by the attachment facility or DSS carrier.
00D35E0D
System action
command or DDM command data. An invalid The application will receive SQLCODE -30000 and
PASSWORD length was sent on a SECCHK command. SQLSTATE 58008.
Db2 passwords cannot exceed 8 bytes.
Operator response

items:
Analyze the statistics class 4 trace record identified associated with the failing request.
DSNL031I message.
items:
items:
items:
00D35E10
• All dumps taken by the attachment facility or Db2, acting as a DRDA client, has detected a floating
requesting application. point conversion error when converting a 4-byte
or 8-byte floating point number in IEEE format to
00D35E0F System/370 format.

Db2 has detected an error in the DDM command data An alert is generated and message DSNL031I is
object or DDM reply data object received from the written to the console. Refer to the description of this
remote server as part of a DDM command or reply. The message for further information.
size of the object is greater than 32KB and the DDM
level 6b extended length field is invalid. Operator response
System action
SQLSTATE 58008.

Check the floating point value. Overflow can occur
when the floating value is out of the System/370
System programmer response floating point range.
At the Db2 for z/OS DRDA client, collect the following
diagnostic item:

Db2, acting as a DRDA client, has detected a floating
Related concepts point conversion error when converting a 4-byte
Double precision floating-point (DOUBLE or floating point number in VAX format to System/370
FLOAT) (Db2 SQL) format.
Single precision floating-point (REAL) (Db2 SQL)
System action
00D35E11
Explanation
point conversion error when converting a nullable 4- Operator response
byte or 8-byte floating point number in IEEE format to
System/370 format. Notify the system programmer.

An alert is generated and message DSNL031I is If you suspect an error in Db2, you might need to
written to the console. Refer to the description of this report the problem. For information about identifying
message for further information. and reporting the problem, see Collecting diagnostic
Operator response
User response
floating point range.
User response
diagnostic item:
floating point range. • Statistics Class 4 trace record for the LUWID
Problem determination Related concepts
The statistics class 4 trace record identified by the Double precision floating-point (DOUBLE or
IFCID sequence number enumerated in the DSNL031I FLOAT) (Db2 SQL)
message should be analyzed. Single precision floating-point (REAL) (Db2 SQL)
At the Db2 for z/OS DRDA client, collect the following 00D35E13
diagnostic item:
Related concepts point conversion error when converting a nullable
Double precision floating-point (DOUBLE or 4-byte floating point number in VAX format to
FLOAT) (Db2 SQL) System/370 format.
00D35E12

Operator response
User response
System programmer response when the floating value is out of the System/370
User response message should be analyzed.
diagnostic items:
floating point range. • Statistics Class 4 trace record for the LUWID
Problem determination Related concepts
The statistics class 4 trace record identified by the Double precision floating-point (DOUBLE or
IFCID sequence number enumerated in the DSNL031I FLOAT) (Db2 SQL)
message should be analyzed. Single precision floating-point (REAL) (Db2 SQL)
At the Db2 for z/OS DRDA client, collect the following 00D35E15
diagnostic item:
Related concepts point conversion error when converting a nullable
Double precision floating-point (DOUBLE or 8-byte floating point number in VAX format to
FLOAT) (Db2 SQL) System/370 format.
System action
00D35E14
point conversion error when converting a 8-byte
Operator response
floating point number in VAX format to System/370
format. Notify the system programmer.

Operator response

Check the floating point value. Overflow can occur The statistics class 4 trace record identified by the
when the floating value is out of the System/370 IFCID sequence number enumerated in the DSNL031I
floating point range. message should be analyzed.
Problem determination diagnostic item:
Related concepts
At the Db2 for z/OS DRDA client, collect the following Double precision floating-point (DOUBLE or
diagnostic item: FLOAT) (Db2 SQL)
• Statistics Class 4 trace record for the LUWID Single precision floating-point (REAL) (Db2 SQL)
00D35E17
Related concepts
Double precision floating-point (DOUBLE or
FLOAT) (Db2 SQL)
Explanation
Single precision floating-point (REAL) (Db2 SQL) Db2, acting as a DRDA client, has detected a floating
point conversion error when converting a nullable
00D35E16 4-byte floating point number in 80x86 format to
System/370 format.
Explanation
System action
point conversion error when converting a 4-byte An alert is generated and message DSNL031I is
floating point number in 80x86 format to System/370 written to the console. Refer to the description of this
format. message for further information.

Operator response
User response
report the problem. For information about identifying Check the floating point value. Overflow can occur
and reporting the problem, see Collecting diagnostic when the floating value is out of the System/370
data (Collecting data). floating point range.

Check the floating point value. Overflow can occur The statistics class 4 trace record identified by the
when the floating value is out of the System/370 IFCID sequence number enumerated in the DSNL031I
floating point range. message should be analyzed.
diagnostic item:

FLOAT) (Db2 SQL)
point conversion error when converting a nullable
Single precision floating-point (REAL) (Db2 SQL) 8-byte floating point number in 80x86 format to
System/370 format.
00D35E18
System action
Explanation
point conversion error when converting a 8-byte
floating point number in 80x86 format to System/370
format.
Operator response
User response
User response The statistics class 4 trace record identified by the
floating point range. At the Db2 for z/OS DRDA client, collect the following
diagnostic item:
IFCID sequence number enumerated in the DSNL031I Related concepts
message should be analyzed. Double precision floating-point (DOUBLE or
At the Db2 for z/OS DRDA client, collect the following FLOAT) (Db2 SQL)
diagnostic item: Single precision floating-point (REAL) (Db2 SQL)
• Statistics Class 4 trace record for the LUWID 00D35E1A

Db2, acting as a DRDA client, has detected an error in
FLOAT) (Db2 SQL)
a NUL-terminated string of length less than 257 bytes.
Single precision floating-point (REAL) (Db2 SQL) The NUL-terminator cannot be located within the data
field as defined by the DDM descriptor received.
00D35E19

An alert is generated and message DSNL031I is The statistics class 4 trace record identified by the
written to the console. Refer to the description of this IFCID sequence number enumerated in the DSNL031I
message for further information. message should be analyzed.
Operator response diagnostic items listed in
If you suspect an error in Db2, you might need to 00D35E1C
Explanation
Db2, acting as a DRDA client, has detected an error
Problem determination in a NUL-terminated string of length greater than
256 bytes. The NUL-terminator cannot be located
The statistics class 4 trace record identified by the within the data field as defined by the DDM descriptor
IFCID sequence number enumerated in the DSNL031I received.
At the Db2 for z/OS DRDA client, collect the following System action
• Statistics Class 4 trace record for the LUWID written to the console. Refer to the description of this
associated with the failing request. message for further information.
.
Operator response
00D35E1B
Explanation
in a nullable NUL-terminated string of length less If you suspect an error in Db2, you might need to
than 257 bytes. The NUL-terminator cannot be located report the problem. For information about identifying
within the data field as defined by the DDM descriptor and reporting the problem, see Collecting diagnostic
received. data (Collecting data).

If you suspect an error in Db2, you might need to 00D35E1D
Explanation
in a nullable NUL-terminated string of length greater
than 256 bytes. The NUL-terminator cannot be located

within the data field as defined by the DDM descriptor User response
received.
Check the numeric data.
System action
written to the console. Refer to the description of this The statistics class 4 trace record identified by the
message for further information. IFCID sequence number enumerated in the DSNL031I
Operator response At the Db2 for z/OS DRDA client, collect the following
.
report the problem. For information about identifying 00D35E1F
Problem determination in a variable length DBCS character data field whose
The statistics class 4 trace record identified by the length is given by a 2-byte length field and whose
IFCID sequence number enumerated in the DSNL031I maximum length is less than 257 bytes. The value of
message should be analyzed. the length field is either negative or greater than the
maximum length specified by the DDM descriptor for
At the Db2 for z/OS DRDA client, collect the following the field.
• Statistics Class 4 trace record for the LUWID System action
. written to the console. Refer to the description of this
00D35E1E message for further information.

Db2, acting as a DRDA client, has detected an error Notify the system programmer.
in a numeric character data field (nullable or non-
nullable). Db2 has detected a numeric conversion System programmer response
error, preventing the data from being converted to
packed decimal format. If you suspect an error in Db2, you might need to
written to the console. Refer to the description of this Problem determination
Notify the system programmer. At the Db2 for z/OS DRDA client, collect the following
System programmer response • Statistics Class 4 trace record for the LUWID
data (Collecting data). 00D35E20

in a nullable variable length DBCS character data
field whose length is given by a 2-byte length field System programmer response
and whose maximum length is less than 257 bytes.
The value of the length field is either negative or If you suspect an error in Db2, you might need to
greater than the maximum length specified by the report the problem. For information about identifying
DDM descriptor for the field. and reporting the problem, see Collecting diagnostic
System action
Operator response At the Db2 for z/OS DRDA client, collect the following
.
report the problem. For information about identifying 00D35E22
Explanation
Problem determination Db2, acting as a DRDA client, has detected an error in
a nullable variable length DBCS character data field
The statistics class 4 trace record identified by the whose length is given by a 2-byte length field and
IFCID sequence number enumerated in the DSNL031I whose maximum length is greater than 256 bytes.
message should be analyzed. The value of the length field is either negative or
At the Db2 for z/OS DRDA client, collect the following greater than the maximum length specified by the
diagnostic items listed in DDM descriptor for the field.

System action
. An alert is generated and message DSNL031I is
00D35E21 message for further information.

in a variable length DBCS character data field whose
length is given by a 2-byte length field and whose System programmer response
maximum length is greater than 256 bytes. The value
of the length field is either negative or greater than the If you suspect an error in Db2, you might need to
maximum length specified by the DDM descriptor for report the problem. For information about identifying
the field. and reporting the problem, see Collecting diagnostic
System action

At the Db2 for z/OS DRDA client, collect the following System action
• Statistics Class 4 trace record for the LUWID written to the console. Refer to the description of this
associated with the failing request. message for further information.
.
00D35E23
Operator response
Explanation
in a variable length DBCS character data field whose If you suspect an error in Db2, you might need to
length is given by a 1-byte length field. The value of report the problem. For information about identifying
the length field is greater than the maximum length and reporting the problem, see Collecting diagnostic
specified by the DDM descriptor for the field. data (Collecting data).

If you suspect an error in Db2, you might need to 00D35E25
Problem determination in a variable length SBCS character data field whose
length is given by a 2-byte length field and whose
The statistics class 4 trace record identified by the maximum length is less than 257 bytes. The value of
IFCID sequence number enumerated in the DSNL031I the length field is either negative or greater than the
message should be analyzed. maximum length specified by the DDM descriptor for
At the Db2 for z/OS DRDA client, collect the following the field.
• Statistics Class 4 trace record for the LUWID System action
associated with the failing request. An alert is generated and message DSNL031I is
. written to the console. Refer to the description of this
00D35E24
Operator response
Explanation
in a nullable variable length DBCS character data field
whose length is given by a 1-byte length field. The
value of the length field is greater than the maximum If you suspect an error in Db2, you might need to
length specified by the DDM descriptor for the field. report the problem. For information about identifying

The statistics class 4 trace record identified by the Db2, acting as a DRDA client, has detected an error
IFCID sequence number enumerated in the DSNL031I in a variable length SBCS character data field whose
message should be analyzed. length is given by a 2-byte length field and whose
maximum length is greater than 256 bytes. The value
of the length field is either negative or greater than the
maximum length specified by the DDM descriptor for
• Statistics Class 4 trace record for the LUWID the field.
. System action
00D35E26 An alert is generated and message DSNL031I is
Explanation
Db2, acting as a DRDA client, has detected an error Operator response
in a nullable variable length SBCS character data
field whose length is given by a 2-byte length field Notify the system programmer.
and whose maximum length is less than 257 bytes.
The value of the length field is either negative or System programmer response
greater than the maximum length specified by the
DDM descriptor for the field. If you suspect an error in Db2, you might need to
written to the console. Refer to the description of this Problem determination
Notify the system programmer. At the Db2 for z/OS DRDA client, collect the following
System programmer response • Statistics Class 4 trace record for the LUWID
data (Collecting data). 00D35E28

The statistics class 4 trace record identified by the Db2, acting as a DRDA client, has detected an error in
IFCID sequence number enumerated in the DSNL031I a nullable variable length SBCS character data field
message should be analyzed. whose length is given by a 2-byte length field and
whose maximum length is greater than 256 bytes.
The value of the length field is either negative or
greater than the maximum length specified by the
• Statistics Class 4 trace record for the LUWID DDM descriptor for the field.
. System action
00D35E27 An alert is generated and message DSNL031I is

.
00D35E2A
Explanation
At the Db2 for z/OS DRDA client, collect the following Db2, acting as a DRDA server, has detected an
diagnostic items listed in error while parsing a DDM BNDOPT command data
object received from a remote DRDA client. The
• Statistics Class 4 trace record for the LUWID BNDOPT collection contains multiple instances of the
associated with the failing request. BNDOPTNM scalar. This is invalid.
.
System action
00D35E29
Db2, acting as a DRDA client, has detected an
error in a zoned decimal data field (nullable or non-
nullable). Db2 has detected a numeric conversion
error, preventing the data from being converted to
packed decimal format. Operator response
System action
and reporting the problem, see Collecting diagnostic If the remote DRDA client is a Db2 for z/OS system, at
data (Collecting data). the Db2 DRDA client, collect the following diagnostic
items:
User response • Statistics Class 4 trace record for the LUWID
Check the numeric data. associated with the failing request.
recommendations.

At the Db2 DRDA server, collect the following • Console output from the system on which the job
• All dumps taken by the attachment facility or 00D35E2C
. Explanation
00D35E2B Db2, acting as a DRDA server, has detected an error
while parsing a DDM BNDOPT command data object
received from a remote DRDA client. The BNDOPT
Explanation
collection contains an invalid instance.
error while parsing a DDM BNDOPT command data System action
object received from a remote DRDA client. The
BNDOPT collection contains multiple instances of the An alert is generated and message DSNL032I is
BNDOPTVL scalar. This is invalid. written to the console. Refer to the description of this
Operator response
message should be analyzed
Problem determination If the remote DRDA client is a Db2 for z/OS system, at
the Db2 DRDA client, collect the following diagnostic
items:
DSNL032I message. • Statistics Class 4 trace record for the LUWID
the Db2 DRDA client, collect the following diagnostic For other remote DRDA clients, refer to the
items: client product documentation for diagnostic
recommendations.
associated with the failing request. At the Db2 DRDA server, collect the following
diagnostic items:
client product documentation for diagnostic • Console output from the system on which the job
recommendations. was run, and a listing of the SYSLOG data set for the

00D35E2D Explanation
Explanation while parsing a DDM BNDOPT command data object
Db2, acting as a DRDA server, has detected an error received from a remote DRDA client. A BNDOPTVL
while parsing a DDM BNDOPT command data object instance variable is required for this DDM collection
received from a remote DRDA client. A BNDOPTNM but was not received.
instance variable is required for this DDM collection
but was not received. System action
System action written to the console. Refer to the description of this
An alert is generated and message DSNL032I is message for further information.
written to the console. Refer to the description of this A DDM reply message (SYNTAXRM) will be returned to
message for further information. the remote DRDA client.
the remote DRDA client. Operator response
Operator response
Notify the system programmer. System programmer response
If you suspect an error in Db2, you might need to and reporting the problem, see Collecting diagnostic
report the problem. For information about identifying data (Collecting data).
Problem determination IFCID sequence number enumerated in the DSNL032I
The statistics class 4 trace record identified by the message should be analyzed.
IFCID sequence number enumerated in the DSNL032I If the remote DRDA client is a Db2 for z/OS system, at
message should be analyzed. the Db2 DRDA client, collect the following diagnostic
If the remote DRDA client is a Db2 for z/OS system, at items:
the Db2 DRDA client, collect the following diagnostic • Statistics Class 4 trace record for the LUWID
• Statistics Class 4 trace record for the LUWID For other remote DRDA clients, refer to the
associated with the failing request. client product documentation for diagnostic
For other remote DRDA clients, refer to the recommendations.
client product documentation for diagnostic At the Db2 DRDA server, collect the following
recommendations. diagnostic items:
At the Db2 DRDA server, collect the following • Console output from the system on which the job
• All dumps taken by the attachment facility or 00D35E2F
00D35E2E Explanation
received from a remote DRDA client. The length of the

DDM object is less than 4, the minimum length of any System action
DDM object. This is invalid.
An alert is generated and message DSNL032I is A DDM reply message (SYNTAXRM) will be returned to
written to the console. Refer to the description of this the remote DRDA client.
A DDM reply message (SYNTAXRM) will be returned to Operator response
Operator response
Problem determination message should be analyzed
items:
• Statistics Class 4 trace record for the LUWID client product documentation for diagnostic
For other remote DRDA clients, refer to the At the Db2 DRDA server, collect the following
client product documentation for diagnostic diagnostic items:
recommendations.
diagnostic items: Collect the following diagnostic period of time that spans the failure.
items:
period of time that spans the failure. 00D35E31

00D35E30 Db2, acting as a DRDA server, has detected an error
received from a remote DRDA client. The length of a
Explanation DDM instance variable is less than the minimum length
Db2, acting as a DRDA server, has detected an error defined by DDM Level 3. This is invalid.
received from a remote DRDA client. The length of the System action
DDM command is less than the sum of the lengths
of the constituent instance variables appearing as An alert is generated and message DSNL032I is
parameters. written to the console. Refer to the description of this

A DDM reply message (SYNTAXRM) will be returned to Operator response
Operator response
items:
• Statistics Class 4 trace record for the LUWID client product documentation for diagnostic
For other remote DRDA clients, refer to the At the Db2 DRDA server, collect the following
client product documentation for diagnostic diagnostic items:
recommendations.
diagnostic items: period of time that spans the failure.
00D35E33
Explanation
00D35E32
Db2 has detected an error in the DDM SQLRSLRD
Explanation in response to a DDM EXCSQLSTT command that
Db2, acting as a DRDA server, has detected an error generated query result sets. The value of the single
while parsing a DDM BNDOPT command data object element of the SQLNUMGRP, SQLNUM, defining the
received from a remote DRDA client. The length of a total number of SQLRSROW occurrences within the
DDM instance variable is greater than the maximum SQLRSLRD array, is inconsistent with the number of
length defined by DDM Level 3. This is invalid. result sets indicated in the RSLSETRM.

A DDM reply message (SYNTAXRM) will be returned to The application will receive SQLCODE -30020 and
the remote DRDA client. SQLSTATE 58009.

data (Collecting data). Analyze the statistics class 4 trace record identified
items:
DSNL031I. • Console output from the system on which the job
items:
• Console output from the system on which the job associated with the failing request.
period of time that spans the failure. If the DRDA server is Db2 for z/OS, then Db2
Db2 server, collect the following diagnostic items:
If the DRDA server is Db2 for z/OS, then Db2
Db2 server, collect the following diagnostic items:
• Console output from the system on which the job 00D35E35
00D35E34 Db2 has detected an error in the DDM SQLCINRD
Explanation in response to a DDM EXCSQLSTT command that
generated query result sets. The value of the single
Db2 has detected an error in the DDM SQLRSLRD element of the SQLNUMGRP, SQLNUM, defining the
reply data object received from the remote server total number of SQLCIROW occurrences within the
in response to a DDM EXCSQLSTT command SQLCINRD array, is either negative or is inconsistent
that generated query result sets. Within one with the size of the SQLCINRD array.
or more SQLRSROW occurrences, the lengths of
SQLRSNAME_m and SQLRSNAME_s are both non-0,
System action
but only one of these lengths should be non-0. The
data is invalid with regard to the Early SQLRSGRP An alert is generated and message DSNL031I is
group descriptor as defined by DRDA. written to the console. Refer to the description of this
SQLSTATE 58009.
SQLSTATE 58009.
Operator response

Analyze the statistics class 4 trace record identified At the Db2 requester, collect the following diagnostic
by the IFCID sequence number given in message items:
DSNL031I.
At the Db2 requester, collect the following diagnostic was run, and a listing of the SYSLOG data set for the
If the DRDA server is Db2 for z/OS, then Db2
• Statistics Class 4 trace record for the LUWID diagnostic information is available. In this case, at the
associated with the failing request. Db2 server, collect the following diagnostic items:
If the DRDA server is Db2 for z/OS, then Db2 • Console output from the system on which the job
diagnostic information is available. In this case, at the was run, and a listing of the SYSLOG data set for the
Db2 server, collect the following diagnostic items: period of time that spans the failure.
• Console output from the system on which the job 00D35E37
Explanation
00D35E36
command or DDM command data. An invalid IPADDR
Explanation length was sent on a SYNCLOG object.
Db2 has detected an error in the DDM SQLCINRD
reply data object received from the remote server System action
in response to a DDM EXCSQLSTT command that
generated query result sets. Within one or more A DDM reply message (SYNTAXRM) is returned to the
SQLCIROW occurrences, the lengths of SQLCNAME_m DRDA client.
and SQLCNAME_s are both non-0, but only one of
these lengths should be non-0. The data is invalid Operator response
with regard to the Early SQLCIGRP group descriptor
as defined by DRDA. Notify the system programmer.

SQLSTATE 58009.
and reporting the problem, see Collecting diagnostic At this remote server, collect the following diagnostic

DRDA client.
Operator response
00D35E38
Explanation
command or DDM command data. An invalid If you suspect an error in Db2, you might need to
SNAADDR length was sent on a SYNCLOG object. report the problem. For information about identifying
System action
A DDM reply message (SYNTAXRM) is returned to the Problem determination
DRDA client.
Notify the system programmer. At this local Db2, collect the following diagnostic item:
data (Collecting data). • Console output from the system on which the job
The statistics class 4 trace record identified by the requesting application.
message should be analyzed. 00D35E3A

Explanation
associated with the failing request. Db2 has detected an error while parsing a DDM
command or DDM command data. An invalid
At this remote server, collect the following diagnostic LOGNAME length was sent on a SYNCLOG object.
items:
DRDA client.
Operator response
00D35E39
Explanation
command or DDM command data. An invalid RDBNAM If you suspect an error in Db2, you might need to
length was sent on a SYNCLOG object. report the problem. For information about identifying

IFCID sequence number enumerated in the DSNL032I 00D35E3C
associated with the failing request. command or DDM command data. An invalid instance
variable was sent on a SYNCLOG object.
items:
System action
period of time that spans the failure. DRDA client.
00D35E3B Notify the system programmer.

command or DDM command data. An invalid report the problem. For information about identifying
LOGTSTMP length was sent on a SYNCLOG object. and reporting the problem, see Collecting diagnostic
System action
DRDA client. The statistics class 4 trace record identified by the
Operator response
IFCID sequence number enumerated in the DSNL032I 00D35E3D
• Statistics Class 4 trace record for the LUWID Db2 has detected an error in the DDM command data
associated with the failing request. object or DDM reply data object received from the
remote server as part of a DDM command or reply. The
At this remote server, collect the following diagnostic DDM level 6b length field is invalid.
items:

SQLSTATE 58008.
Problem determination was run, and a listing of the SYSLOG data set for the
IFCID sequence number enumerated in the DSNL031I • All dumps taken by the attachment facility or
message should be analyzed. requesting application.
At this local Db2, collect the following diagnostic 00D35E3F
items:
At this remote server, collect the following diagnostic command or DDM command data. A duplicate instance
items: variable was sent on a SYNCCTL command.
• All dumps taken by the attachment facility or DRDA client.
00D35E3E Operator response
Explanation
Db2 has detected an error while parsing a DDM System programmer response
command or DDM command data. An invalid instance
variable was sent on a SYNCCTL command.
DRDA client. Problem determination
Operator response IFCID sequence number enumerated in the DSNL032I

At this remote server, collect the following diagnostic System action
items:
• Console output from the system on which the job DRDA client.
Operator response
requesting application. Notify the system programmer.
00D35E40
Db2 has detected an error while parsing a DDM and reporting the problem, see Collecting diagnostic
command or DDM command data. An invalid data (Collecting data).
SYNCTYPE length was sent on a SYNCCTL command.
System action
A DDM reply message (SYNTAXRM) is returned to the IFCID sequence number enumerated in the DSNL032I
DRDA client. message should be analyzed.
Operator response
Notify the system programmer. associated with the failing request.
System programmer response items:
00D35E42
DSNL032I message. Explanation
At this local Db2, collect the following diagnostic item: Db2 has detected an error while parsing a DDM
command or DDM command data. An invalid UOWID
• Statistics Class 4 trace record for the LUWID length was sent on a SYNCCTL command.
At this remote server, collect the following diagnostic System action
items:
• Console output from the system on which the job DRDA client.
Operator response
00D35E41
Db2 has detected an error while parsing a DDM and reporting the problem, see Collecting diagnostic
command or DDM command data. An invalid RLSCONV data (Collecting data).
length was sent on a SYNCCTL command.

associated with the failing request. command or DDM command data. A duplicate instance
variable was sent on a SYNCRSY command.
items:
System action

command or DDM command data. An invalid instance report the problem. For information about identifying
variable was sent on a SYNCRSY command. and reporting the problem, see Collecting diagnostic
System action
Operator response
associated with the failing request. command or DDM command data. An invalid
RSYNCTYP length was sent on a SYNCRSY command.
items:
System action

items:
The statistics class 4 trace record identified by the 00D35E47

message should be analyzed. Explanation
At this local Db2, collect the following diagnostic item: Db2 has detected an error while parsing a DDM
• Statistics Class 4 trace record for the LUWID command or DDM command data. An invalid
associated with the failing request. UOWSTATE length was sent on a SYNCRSY command.

items: System action
• Console output from the system on which the job A DDM reply message (SYNTAXRM) is returned to the
was run, and a listing of the SYSLOG data set for the DRDA client.
• All dumps taken by the attachment facility or Operator response
00D35E46
Db2 has detected an error while parsing a DDM report the problem. For information about identifying
command or DDM command data. An invalid UOWID and reporting the problem, see Collecting diagnostic
length was sent on a SYNCRSY command. data (Collecting data).

A DDM reply message (SYNTAXRM) is returned to the The statistics class 4 trace record identified by the
DRDA client. IFCID sequence number enumerated in the DSNL032I
items:
The statistics class 4 trace record identified by the 00D35E48


command or DDM command data. An invalid FORGET report the problem. For information about identifying
length was sent on a SYNCCTL command. and reporting the problem, see Collecting diagnostic
System action
IFCID sequence number enumerated in the DSNL032I 00D35E4A
associated with the failing request. command or DDM command data. An invalid CNNTKN
length was sent on a SYNCLOG object.
items:
System action

command or DDM command data. An invalid TCPHOST report the problem. For information about identifying
length was sent on a SYNCLOG object. and reporting the problem, see Collecting diagnostic
System action

At this remote server, collect the following diagnostic SQL statement string were received, or the mixed-byte
items: SQL statement string is non-null, but has a zero length
or the single-byte SQL statement string is not null, but
has a zero length.
System action
requesting application. An alert is generated and message DSNL032I is
00D35E4B
Explanation A DDM reply message (SYNTAXRM) will be returned

to the remote requester. The application will receive
Db2 has detected an error while parsing a DDM SQLCODE -30020 and SQLSTATE 58009.
command or DDM command data. A required instance
variable was not sent on a SYNCLOG object.
Operator response

DRDA client.

and reporting the problem, see Collecting diagnostic DSNL032I message. For the Db2 system generating
data (Collecting data). the DSNL032I message, collect the following
diagnostic items:
IFCID sequence number enumerated in the DSNL032I In addition, identify all connected systems
message should be analyzed. participating in the processing of the remote request.
At this local Db2, collect the following diagnostic item: This includes the requester system to which the
• Statistics Class 4 trace record for the LUWID the target of the remote request. This may also include
associated with the failing request. intermediate server systems. For each system that is a
At this remote server, collect the following diagnostic Db2 system, collect the following diagnostic items:
items: • Console output and the listing of the SYSLOG data
• Console output from the system on which the job set from each connected site for the period of time
was run, and a listing of the SYSLOG data set for the spanning the failure.
period of time that spans the failure. For non-Db2 systems, refer to the documentation
• All dumps taken by the attachment facility or specific to those products for diagnostic procedures.
requesting application. If any dumps were generated on any Db2 system
00D35E4C participating in processing the remote request, collect

Db2 has detected an error while parsing an SQLSTT
object for an EXCSQLSET command received from a • All dumps created by this failure.
remote requester. Both a mixed-byte and a single-byte 00D35E4D

Explanation 00D35E4E
object for an EXCSQLSET command received from a Explanation
remote requester. The SQLSTT has an invalid object Db2 has detected an error while parsing an SQLSTT
length of less than 4. object for an EXCSQLSET command received from a
remote requester. The SQLSTT object length is larger
System action than the containing DSS carrier object.
message for further information. An alert is generated and message DSNL032I is
A DDM reply message (SYNTAXRM) will be returned written to the console. Refer to the description of this
to the remote requester. The application will receive message for further information.
SQLCODE -30020 and SQLSTATE 58009. A DDM reply message (SYNTAXRM) will be returned
Operator response SQLCODE -30020 and SQLSTATE 58009.
Operator response
by the IFCID sequence number enumerated in the Problem determination
DSNL032I message. For the Db2 system generating Analyze the statistics class 4 trace record identified
the DSNL032I message, collect the following by the IFCID sequence number enumerated in the
diagnostic items: DSNL032I message. For the Db2 system generating
• Statistics Class 4 trace record for the LUWID the DSNL032I message, collect the following
associated with the failing request. diagnostic items:
In addition, identify all connected systems • Statistics Class 4 trace record for the LUWID
participating in the processing of the remote request. associated with the failing request.
This includes the requester system to which the In addition, identify all connected systems
application is connected and the data server which is participating in the processing of the remote request.
the target of the remote request. This may also include This includes the requester system to which the
intermediate server systems. For each system that is a application is connected and the data server which is
Db2 system, collect the following diagnostic items: the target of the remote request. This may also include
• Console output and the listing of the SYSLOG data intermediate server systems. For each system that is a
set from each connected site for the period of time Db2 system, collect the following diagnostic items:
spanning the failure. • Console output and the listing of the SYSLOG data
For non-Db2 systems, refer to the documentation set from each connected site for the period of time
specific to those products for diagnostic procedures. spanning the failure.
If any dumps were generated on any Db2 system For non-Db2 systems, refer to the documentation
participating in processing the remote request, collect specific to those products for diagnostic procedures.
the following diagnostic items: If any dumps were generated on any Db2 system
• Listings of the SYS1.LOGREC data set, obtained by participating in processing the remote request, collect
executing IFCEREP1 at each connected site. the following diagnostic items:

00D35E4F • Listings of the SYS1.LOGREC data set, obtained by

Explanation
00D35E50
object for an EXCSQLSET command received from a
remote requester. The SQLSTT object length is too Explanation
small for a SET statement.
object for an EXCSQLSET command received from a
System action remote requester. The SQLSTT object length is larger
than the maximum length (32K) supported by Db2 for
an EXCSQLSET SQLSTT statement string.
System action
A DDM reply message (SYNTAXRM) will be returned
to the remote requester. The application will receive An alert is generated and message DSNL032I is
SQLCODE -30020 and SQLSTATE 58009. written to the console. Refer to the description of this
Operator response A DDM reply message (SYNTAXRM) will be returned
SQLCODE -30020 and SQLSTATE 58009.

Operator response
the DSNL032I message, collect the following Problem determination
diagnostic items:
• Statistics Class 4 trace record for the LUWID by the IFCID sequence number enumerated in the
associated with the failing request. DSNL032I message. For the Db2 system generating
diagnostic items:

• Console output and the listing of the SYSLOG data At the Db2 DRDA server, collect the following
set from each connected site for the period of time diagnostic items:
For non-Db2 systems, refer to the documentation was run, and a listing of the SYSLOG data set for the
specific to those products for diagnostic procedures. period of time that spans the failure.
If any dumps were generated on any Db2 system • All dumps taken by the attachment facility or
participating in processing the remote request, collect requesting application.
the following diagnostic items: 00D35E52
executing IFCEREP1 at each connected site. Explanation
Db2, acting as a DRDA server, has detected an error in
00D35E51 a DDM command data object received from the remote
client. The DDM object is the OUTOVR scalar of the
SQLDTARD collection. The FDOCA descriptor geometry
Explanation
is incorrect. The SQLCADTA row (RLO) MDD is either
Db2, acting as a DRDA server, has detected an error in invalid or has not been included within the SQLDTARD
a DDM command data object received from a remote descriptor. The descriptor is invalid.
client. The DDM object is the OUTOVR object. The size
of the OUTOVR is greater than 32KB and the DDM level System action
6b extended length field is invalid.
System action
A DSCINVRM reply message will be returned to the
remote DRDA client.
A SYNTAXRM reply message will be returned to the Operator response
remote DRDA client.
Operator response
items:
items:
recommendations.
diagnostic items:
recommendations.

00D35E54
Explanation
00D35E53
in a DDM command data object received from the
Explanation remote client. The DDM object is the OUTOVR scalar
Db2, acting as a DRDA server, has detected an error in of the SQLDTARD collection. The FDOCA descriptor
a DDM command data object received from the remote geometry is incorrect. Either the first component of
client. The DDM object is the OUTOVR scalar of the the SQLCADTA row is other than an SQLCAGRP (early)
SQLDTARD collection. The FDOCA descriptor geometry group or the number of elements taken from the
is incorrect. The SQLCADTA row triplet (RLO) is either SQLCAGRP or SQLCAGRP replication factor (or both)
invalid or has not been included within the SQLDTARD are incorrect. The descriptor is invalid.
descriptor. The descriptor is invalid.
System action
System action An alert is generated and message DSNL032I is
message for further information. A DSCINVRM reply message will be returned to the
A DSCINVRM reply message will be returned to the remote DRDA client.
remote DRDA client.
Operator response
Problem determination The statistics class 4 trace record identified by the
The statistics class 4 trace record identified by the IFCID sequence number enumerated in the DSNL032I
IFCID sequence number enumerated in the DSNL032I message should be analyzed.
message should be analyzed. If the remote DRDA client is a Db2 for z/OS system, at
If the remote DRDA client is a Db2 for z/OS system, at the Db2 DRDA client, collect the following diagnostic
the Db2 DRDA client, collect the following diagnostic items:
items: • Statistics Class 4 trace record for the LUWID
• Statistics Class 4 trace record for the LUWID associated with the failing request.
associated with the failing request. For other remote DRDA clients, refer to the
For other remote DRDA clients, refer to the client product documentation for diagnostic
client product documentation for diagnostic recommendations.
recommendations. At the Db2 DRDA server, collect the following
At the Db2 DRDA server, collect the following diagnostic items:
diagnostic items: • Console output from the system on which the job

00D35E55
Explanation
00D35E56
error in a DDM command data object received from
the remote client. The DDM object is the OUTOVR Explanation
scalar of the SQLDTARD collection. The FDOCA Db2, acting as a DRDA server, has detected an error in
descriptor geometry is incorrect. The first component a DDM command data object received from the remote
of the SQLCADTA row correctly enumerates the client. The DDM object is the OUTOVR scalar of the
elements of the SQLCAGRP; however, the second SQLDTARD collection. The FDOCA descriptor geometry
component, identifying the SQLDTAGRP (late) group, is is incorrect. One or more late environment descriptors
incorrect. Either the SQLDTAGRP local identifier (LID) is included within the previously specified SQLDTAGRP
is different from the LID of the SQLDTAGRP previously late group descriptor. However, the SQLDTARD row
specified or the number of elements taken from the (RLO) Meta Data Definition (MDD) is either incorrect
SQLDTAGRP replication factor (or both) are incorrect. or has not been included within the SQLDTARD
The descriptor is invalid. descriptor. The descriptor is invalid.

A DSCINVRM reply message will be returned to the A DSCINVRM reply message will be returned to the
remote DRDA client. remote DRDA client.



items: items:
For other remote DRDA clients, refer to the For other remote DRDA clients, refer to the
client product documentation for diagnostic client product documentation for diagnostic
recommendations. recommendations.
At the Db2 DRDA server, collect the following At the Db2 DRDA server, collect the following

00D35E58
Explanation
00D35E57
in a DDM command data object received from the
Explanation remote client. The DDM object is the OUTOVR scalar
Db2, acting as a DRDA server, has detected an error in of the SQLDTARD collection. The FDOCA descriptor
a DDM command data object received from the remote geometry is incorrect. Either the SQLCADTA local
client. The DDM object is the OUTOVR scalar of the identifier (LID) referenced within the SQLDTARD RLO
SQLDTARD collection. The FDOCA descriptor geometry did not match the LID defined within the SQLCADTA
is incorrect. Either the SQLDTARD is specified as other RLO or the number of elements or replication factor
than a row triplet (RLO) or the SQLDTARD RLO triplet is (or both) within the SQLDTARD RLO was non-zero. The
invalid. The descriptor is invalid. descriptor is invalid.

A DSCINVRM reply message will be returned to the A DSCINVRM reply message will be returned to the
remote DRDA client. remote DRDA client.



items: items:
For other remote DRDA clients, refer to the For other remote DRDA clients, refer to the
client product documentation for diagnostic client product documentation for diagnostic
recommendations. recommendations.
At the Db2 DRDA server, collect the following At the Db2 DRDA server, collect the following

00D35E59 00D35E5A
Db2, acting as a DRDA server, has detected an error Db2 has detected an error while parsing a DDM
in a DDM command data object received from the command or DDM command data. An invalid
remote client. The DDM object is the OUTOVR scalar NEWPSWD length was sent on a SECCHK command.
of the SQLDTARD collection. The FDOCA descriptor New passwords cannot exceed 255 bytes.
geometry is incorrect. Either the length specified in the
LL preceding the OUTOVR is greater than the length System action
of the OBJDSS carrier or the length of one of the
constituent geometries (triplet lengths) is inconsistent A DDM reply message (SYNTAXRM) is returned to the
with the length of the OUTOVR. The descriptor is local Db2.
invalid.
Operator response
System action
A DSCINVRM reply message will be returned to the report the problem. For information about identifying
remote DRDA client. and reporting the problem, see Collecting diagnostic
Operator response
report the problem. For information about identifying At this local Db2, collect the following diagnostic item:
You should also analyze the statistics class 4 trace
record identified by the IFCID sequence number
items:
If the remote DRDA client is a Db2 for z/OS system, at • All dumps taken by the attachment facility or
the Db2 DRDA client, collect the following diagnostic requesting application.
items:
00D35E5B
Explanation
client product documentation for diagnostic Db2 has detected an error while parsing the DDM
recommendations. ACCSEC command or its reply data. The encryption
connection key passed in the SECTKN instance
At the Db2 DRDA server, collect the following variable has an invalid length. The connection key
diagnostic items: must be a 32-byte security token.

If at the server, a DDM reply message (SYNTAXRM) is
returned to the local Db2.
IFCID sequence number enumerated in the DSNL032I • All dumps taken by the attachment facility or
message should be analyzed. requesting application.
At this local Db2, collect the following diagnostic item: 00D35E5D

associated with the failing request. Explanation
At this remote server, collect the following diagnostic Acting as a requester or a server, Db2 has detected
items: an error while parsing a DRDA object. The final length
computed by parsing the object using its descriptor is
• Console output from the system on which the job larger than the stated length of the object itself.
System action
requesting application. An alert is generated and message DSNL031I (if the
00D35E5C message DSNL032I (if the error is detected by Db2
Explanation the description of this message for further information.
Db2 has detected an error while parsing the DDM
SECCHK command or its reply data. The encrypted Operator response
password passed in the SECTKN instance variable has Notify the system programmer.
an invalid length. Db2 supports an 8-byte or a 16-byte
encrypted password.
If at the server, a DDM reply message (SYNTAXRM) is and reporting the problem, see Collecting diagnostic
returned to the local Db2. data (Collecting data).

Notify the system programmer. Analyze the statistics class 4 trace record identified
System programmer response DSNL032I message. For the Db2 system generating
If you suspect an error in Db2, you might need to diagnostic items:

In addition, identify all connected systems by the IFCID sequence number enumerated in the
participating in the processing of the remote request. DSNL031I or DSNL032I message.
application is connected and the data server which is For the Db2 system generating the DSNL031I or
the target of the remote request. This may also include DSNL032I message, collect the following diagnostic
intermediate server systems. For each system that is a items:
Db2 system, collect the following diagnostic items: • Statistics Class 4 trace record for the LUWID
• Console output and the listing of the SYSLOG data associated with the failing request.
set from each connected site for the period of time In addition, identify all connected systems
spanning the failure. participating in the processing of the remote request.
For non-Db2 systems, refer to the documentation This includes the requester system to which the
specific to those products for diagnostic procedures. application is connected and the data server which is
If any dumps were generated on any Db2 system intermediate server systems. For each system that is a
participating in processing the remote request, collect Db2 system, collect the following diagnostic items:
• Listings of the SYS1.LOGREC data set, obtained by set from each connected site for the period of time
executing IFCEREP1 at each connected site. spanning the failure.
• All dumps created by this failure. For non-Db2 systems, refer to the documentation
Related information specific to those products for diagnostic procedures.
DSNL032I (Db2 Messages) If any dumps were generated on any Db2 system
00D35E5E the following diagnostic items:
Acting as a requester or a server, Db2 has detected • All dumps created by this failure.
an error while parsing a DRDA early descriptor object.
The descriptor for the object indicates that additional 00D35E5F
nullable group data is to be parsed, but the object
length is too small to contain the group null indicator. Explanation
Acting as a requester or a server, Db2 has detected
System action an error while parsing a DRDA early descriptor object.
An alert is generated and message DSNL031I (if the The descriptor for the object indicates that additional
error is detected by Db2 acting as a requester) or group data is to be parsed, but the object length is too
message DSNL032I (if the error is detected by Db2 small to contain the additional group data.
the description of this message for further information. System action
Operator response error is detected by Db2 acting as a requester) or
Notify the system programmer. message DSNL032I (if the error is detected by Db2
and reporting the problem, see Collecting diagnostic Notify the system programmer.

DSNL031I or DSNL032I message. Problem determination
For the Db2 system generating the DSNL031I or Analyze the statistics class 4 trace record identified
DSNL032I message, collect the following diagnostic by the IFCID sequence number enumerated in the
items: DSNL032I message. For the Db2 system generating
This includes the requester system to which the In addition, identify all connected systems
application is connected and the data server which is participating in the processing of the remote request.
the target of the remote request. This may also include This includes the requester system to which the
intermediate server systems. For each system that is a application is connected and the data server which is
Db2 system, collect the following diagnostic items: the target of the remote request. This may also include
spanning the failure. • Console output and the listing of the SYSLOG data
the following diagnostic items: If any dumps were generated on any Db2 system
• All dumps created by this failure. • Listings of the SYS1.LOGREC data set, obtained by
00D35E60
Explanation 00D35E61

command or DDM command data. An invalid XID Explanation
length was received on a SYNCCTL command sent by a Db2 has detected an error while parsing a DDM
remote requester. command or DDM command data. An invalid XSHR
length was received on a SYNCCTL command sent by a
System action remote requester.

A DDM reply message (SYNTAXRM) is returned to the written to the console. Refer to the description of this
remote requester. message for further information.
Operator response remote requester.

Operator response


Analyze the statistics class 4 trace record identified The statistics class 4 trace record identified by the
by the IFCID sequence number enumerated in the IFCID sequence number enumerated in the DSNL032I
DSNL032I message. For the Db2 system generating message should be analyzed.
At the local Db2, collect the following diagnostic item:
diagnostic items:
At the remote server, collect the following diagnostic
items:
This includes the requester system to which the • Console output from the system on which the job
application is connected and the data server which is was run, and a listing of the SYSLOG data set for the
the target of the remote request. This may also include period of time that spans the failure.
intermediate server systems. For each system that is a • All dumps taken by the attachment facility or
Db2 system, collect the following diagnostic items: requesting application.
• Console output and the listing of the SYSLOG data .
spanning the failure. 00D35E63
specific to those products for diagnostic procedures. Explanation
If any dumps were generated on any Db2 system Db2 detected an error in a DDM command or DDM
participating in processing the remote request, collect command data. An invalid RDBNAM length was sent
the following diagnostic items: on an INTRDBRQS command.
executing IFCEREP1 at each connected site. System action
• All dumps created by this failure. If the length of the RDBNAM is greater than 255 (if
client supports long names) or greater than 18 (if
00D35E62 client does not support long names), then A DDM reply
message (SYNTAXRM) is returned to the DRDA client.
Explanation If the data in characters 17-18 of the RDBNAME is
non-blank, then a DDM reply message (VALNSPRM) is
Db2 detected an error in a DDM command or DDM
returned to the DRDA client.
command data. An invalid interrupt token was sent on
an INTRDBRQS command.
Operator response
A DDM reply message (SYNTAXRM or INTTKNRM) is
returned to the DRDA client. INTTKNRM is returned System programmer response
if the client is not authorized to interrupt an SQL If you suspect an error in Db2, you might need to
statement or the token length is not 30 bytes. In all report the problem. For information about identifying
other cases, SYNTAXRM is returned. and reporting the problem, see Collecting diagnostic
Operator response

Problem determination In addition, identify all connected systems
The statistics class 4 trace record identified by the This includes the requester system to which the
IFCID sequence number enumerated in the DSNL032I application is connected and the data server which is
message should be analyzed. the target of the remote request. This may also include
At the local Db2, collect the following diagnostic item: intermediate server systems. For each system that is a
associated with the failing request. • Console output and the listing of the SYSLOG data
At the remote server, collect the following diagnostic spanning the failure.
items:
• Console output from the system on which the job specific to those products for diagnostic procedures.
period of time that spans the failure. If any dumps were generated on any Db2 system
.
00D35E67 • All dumps created by this failure.
00D35E68
Explanation
Db2 has detected an error while parsing a DDM Explanation
SNDPKT command received from a remote requester.
The SNDPKT command contains an invalid instance Db2 has detected an error while parsing a DDM
variable code point. SNDPKT command received from a remote requester.
The SNDPKT command contains an instance variable
code point that has been duplicated.
System action
A DDM reply message (PRMNSPRM) is returned to the message for further information.
remote requester.
remote requester.
Operator response
Notify the system programmer. Operator response
This is most likely an error at the remote requester System programmer response
system. If you suspect an error in Db2, see the
information about identifying and reporting problems This is most likely an error at the remote requester
in Searching the IBM Support site for known problems system. If you suspect an error in Db2, see the
and solutions (Diagnosing Db2 problems). information about identifying and reporting problems
in Searching the IBM Support site for known problems
and solutions (Diagnosing Db2 problems).
Analyze the statistics class 4 trace record identified Problem determination
DSNL032I message. For the Db2 system generating Analyze the statistics class 4 trace record identified
the DSNL032I message, collect the following by the IFCID sequence number enumerated in the
diagnostic items: DSNL032I message. For the Db2 system generating
• Statistics Class 4 trace record for the LUWID diagnostic items:

• All dumps created by this failure. • Listings of the SYS1.LOGREC data set, obtained by
00D35E69
Explanation 00D35E6A
SNDPKT command received from a remote requester. Explanation
The SNDPKT command contains an invalid RESPKTSZ
instance variable - the value must be 4 bytes.
The SNDPKT command contains a RESPKTSZ instance
System action variable value that is not supported. The value must be
32767 or less.
A DDM reply message (SYNTAXRM) is returned to the An alert is generated and message DSNL032I is
Operator response A DDM reply message (VALNSPRM) is returned to the
remote requester.

This is most likely an error at the remote requester
information about identifying and reporting problems System programmer response
information about identifying and reporting problems
Problem determination in Searching the IBM Support site for known problems

Problem determination information about identifying and reporting problems
Analyze the statistics class 4 trace record identified and solutions (Diagnosing Db2 problems).
the DSNL032I message, collect the following Problem determination
diagnostic items listed in Analyze the statistics class 4 trace record identified
• Statistics Class 4 trace record for the LUWID by the IFCID sequence number enumerated in the
associated with the failing request. DSNL032I message. For the Db2 system generating
specific to those products for diagnostic procedures. • Console output and the listing of the SYSLOG data
the following diagnostic items: For non-Db2 systems, refer to the documentation
executing IFCEREP1 at each connected site. If any dumps were generated on any Db2 system
00D35E6B • Listings of the SYS1.LOGREC data set, obtained by
Db2 has detected an error while parsing a DDM 00D35E6C
The SNDPKT command contains an invalid RDBNAM
instance variable. Long variable name support has Explanation
been negotiated but the RDBNAM value length either Db2 has detected an error while parsing a DDM
exceeded the 255 byte limit or was too short. SNDPKT command received from a remote requester.
The SNDPKT command contains an invalid RDBNAM
System action instance variable. Long variable name support has not
been negotiated and the RDBNAM value must be 18
An alert is generated and message DSNL032I is bytes.
System action
remote requester. An alert is generated and message DSNL032I is
Operator response

This is most likely an error at the remote requester Notify the system programmer.

and solutions (Diagnosing Db2 problems). This is most likely an error at the remote requester
00D35E6D • Listings of the SYS1.LOGREC data set, obtained by
Db2 has detected an error while parsing a DDM 00D35E6E
The SNDPKT command contains an invalid RDBNAM Explanation
instance variable value that is not supported. Db2 only
accepts up to 16 characters. Db2 has detected an error while parsing a DDM
SYNCCTL command received from a remote requester.
The SYNCCTL command contains an invalid XAFLAGS
System action
remote requester.

A DDM reply message (SYNTAXRM) is returned to the System action
remote requester.
Operator response message for further information.
Notify the system programmer. A DDM reply message (SYNTAXRM) is returned to the
remote requester.
This is most likely an error at the remote requester Operator response
system. If you suspect an error in Db2, see the Notify the system programmer.
and solutions (Diagnosing Db2 problems). System programmer response
Problem determination system. If you suspect an error in Db2, see the
Analyze the statistics class 4 trace record identified in Searching the IBM Support site for known problems
by the IFCID sequence number enumerated in the and solutions (Diagnosing Db2 problems).
diagnostic items: Problem determination
• Statistics Class 4 trace record for the LUWID Analyze the statistics class 4 trace record identified
associated with the failing request. by the IFCID sequence number enumerated in the
In addition, identify all connected systems the DSNL032I message, collect the following
participating in the processing of the remote request. diagnostic items:
intermediate server systems. For each system that is a In addition, identify all connected systems
Db2 system, collect the following diagnostic items: participating in the processing of the remote request.
• Console output and the listing of the SYSLOG data This includes the requester system to which the
set from each connected site for the period of time application is connected and the data server which is
spanning the failure. the target of the remote request. This may also include
For non-Db2 systems, refer to the documentation Db2 system, collect the following diagnostic items:
If any dumps were generated on any Db2 system set from each connected site for the period of time
participating in processing the remote request, collect spanning the failure.
• Listings of the SYS1.LOGREC data set, obtained by specific to those products for diagnostic procedures.
• All dumps created by this failure. participating in processing the remote request, collect
00D35E6F the following diagnostic items:
Db2 has detected an error while parsing a DDM • All dumps created by this failure.
SYNCCTL command received from a remote requester. 00D35E70
The SYNCCTL command contains an invalid TIMEOUT
Explanation
ACCSEC command received from a remote requester.

The ACCSEC command contains an invalid ENCALG Explanation
ACCSEC command received from a remote requester.
System action The ACCSEC command contains an invalid ENCKEYLEN
An alert is generated and message DSNL032I is instance variable - the value must be 2 bytes.
A DDM reply message (SYNTAXRM) is returned to the An alert is generated and message DSNL032I is
Operator response A DDM reply message (SYNTAXRM) is returned to the

and solutions (Diagnosing Db2 problems). This is most likely an error at the remote requester
Problem determination in Searching the IBM Support site for known problems
00D35E71 • Listings of the SYS1.LOGREC data set, obtained by


00D35E72 Related information
Explanation
00D35E73
Acting as a server, Db2 detected an error while parsing
an SQLSTT object. The data portion of the object has
Explanation
a length that is smaller than the minimum size of 4
bytes. The first four bytes of the data portion contains Db2 has detected an error in the DDM reply message
the length of the SQL statement. or DDM reply data object received from the remote
server in response to a DDM command. The length
System action of the data to be parsed is inconsistent with the
descriptor. The error occurs when processing data for
An alert is generated and message DSNL032I is a rowset cursor.
System action
Operator response An alert is generated and message DSNL031I is
Notify the system programmer. message for further information.

diagnostic items: The statistics class 4 trace record identified by
In addition, identify all connected systems following diagnostic items:
For non-Db2 systems, refer to the references specific
to those products.

00D35E74 • Listings of the SYS1.LOGREC data set, obtained by

Explanation
00D35E75
server in response to a DDM command. The length Explanation
of the data to be parsed is inconsistent with the
descriptor. The error occurs when processing data for
SECCHK command received from a remote client. The
a rowset cursor.
SECCHK command contains an invalid USRREGNM
instance variable value that is not supported. The
System action value exceeded the 255 bytes limit.
DRDA client.
Operator response
If you suspect an error in Db2, you might need to System programmer response
This is most likely an error at the remote client system.
the IFCID sequence number enumerated in the Problem determination
At the local Db2, collect the diagnostic items:
intermediate server systems. For each system that is a If the remote client system, collect the diagnostic
Db2 system, collect the following diagnostic items: items:
• Console output and the listing of the SYSLOG data • Console output from the system on which the job
set from each connected site for the period of time was run, and a listing of the SYSLOG data set for the
spanning the failure. period of time that spans the failure.
For non-Db2 systems, refer to the references specific • All dumps taken by the attachment facility or
to those products. requesting application.
00D35E76

Db2 has detected an error while parsing a DDM Notification of the failure is returned to the application.
SECCHK command received from a remote client. The requested trusted connection is not established.
The SECCHK command contains an invalid USRORGID
instance variable value that is not supported. The Operator response
value must be 1024 bytes or less.
System action
DRDA client. This is most likely an error at the remote client system.
Operator response

This is most likely an error at the remote client system. You should analyze the statistics class 4 trace record
If you suspect an error in Db2, you might need to identified by the IFCID sequence number enumerated
report the problem. For information about identifying in the DSNL032I message.
At the local Db2, collect the diagnostic items:
You should analyze the statistics class 4 trace record • Statistics Class 4 trace record for the LUWID
identified by the IFCID sequence number enumerated associated with the failing request.
If the remote client system, collect the diagnostic
At the local Db2, collect the diagnostic items: items:
• SVC dump (or system dump), taken to SYS1.DUMPxx • Console output from the system on which the job
data set, as result of an operator-initiated dump was run, and a listing of the SYSLOG data set for the
command or SLIP trap exit. period of time that spans the failure.
If the remote client system, collect the diagnostic
00D35E78
items:
period of time that spans the failure. Db2 acts as a DRDA intermediate server passing input
• All dumps taken by the attachment facility or data to another DRDA server. It has detected an error
requesting application. in an SQLDTA object. A NUL-terminated string was
found in the FDODTA scalar where the NUL-terminator
00D35E77 could not be located within the data field as defined by
the DDM descriptor received.
Explanation
System action
SECCHK command received from a remote client. The The system generates an alert and returns message
SECCHK command contains an invalid USRSECTOK DSNL032I. Refer to the description of this message for
instance variable value that is not supported. The further information.
value must be 4096 bytes or less.

diagnostic items:
in the DSNL032I message. • Statistics Class 4 trace record for the LUWID
diagnostic items: If the requester is a Db2 for z/OS system, collect the
• SVC dump (or system dump), taken to SYS1.DUMPxx following diagnostic items:
00D35E7A
• All dumps taken by the attachment facility or Db2 acts as a DRDA intermediate server passing input
requesting application. data to another DRDA server. It has detected an error
00D35E79 system. The SQLDTA object length value computed
from parsing the DDM constituents of the SQLDTA
Explanation object is smaller than the stated length of the SQLDTA
object.
Db2 acts as a DRDA intermediate server passing input
data to another DRDA server. It has detected an error
System action
system. The SQLDTA object length value computed The system generates an alert and returns message
from parsing the DDM constituents of the SQLDTA DSNL032I. Refer to the description of this message for
object is larger than the stated length of the SQLDTA further information.
object.
System action

diagnostic items:

• Statistics Class 4 trace record for the LUWID • SVC dump (or system dump), taken to SYS1.DUMPxx
associated with the failing request. data set, as result of an operator-initiated dump
following diagnostic items: • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
A Db2 internal error was detected while processing a
00D36800 DISPLAY, START, or STOP RESTSVC command.

To satisfy an unconditional request for storage for a The agent is abended.
RESTFul service execution reply message, the RESTful
service execution function needs additional storage to Operator response
expand the reply buffer. However, the RESTful service
reply message buffer is already at the maximum Notify the system programmer.
allowed size.
The agent is abended. report the problem. For information about identifying
data.
Operator response
Diagnostic information is recorded in SYS1.LOGREC,
and a Db2dump is requested.
Db2(04E and 04F abends).
and a Db2 dump is requested. • SVC dump (or system dump), taken to SYS1.DUMPxx
Collect the following diagnostic items: command or SLIP trap exit.

Reason code identifiers that begin with 00D4 communicate normal and error situations with the IMS
attachment facility.
Every attempt is made to return to RTM with the retry
Explanation option. If the retry is successful, a message is sent to
The IMS attachment facility detected an invalid save the originating destination to show that the command
area chain pointer. This condition occurs only if the failed.
save area is overlaid or if the save area pointer is
invalid. System programmer response
The task is abended. and reporting the problem, see Collecting diagnostic

If the abend occurred in an IMS dependent region,
restart the region. If the abend occurred in the IMS Analyze the SYS1.LOGREC data. The log record
control region, restart the connection. Determine the contains the current IMS attachment facility trace
failing environment. If you suspect an error in Db2, entry, the first four characters of the command, the
you might need to report the problem. For information output destination, and the authorization ID for the
about identifying and reporting the problem, see failing command.
Collecting diagnostic data (Collecting data). Collect the following diagnostic items:
Analyze the dump. Register 13 plus four bytes is the command or SLIP trap exit.
address of the invalid save area chain pointer. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
Collect the following diagnostic items: • IMS dependent region, control region dump, or both.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • IMS system log information, for the period of time
• IMS dependent region, control region dump, or both.
• IMS console log.
• IMS system log information, for the period of time
spanning the failure. 00D40061
Explanation
00D40008
The IMS attachment facility could not establish a
Explanation connection with Db2 because an IMS /STOP SUBSYS
command was issued.
The IMS attachment facility command module's ESTAE
routine places this reason code in the variable
System action
recording area of SYS1.LOGREC. The reason code
indicates that the entry is not a standard Db2 entry. The application's SQLCA is updated with an SQLCODE
The reason code is followed by the current IMS -924 and reason code 00D40061. Control is returned
attachment facility trace entry, the first four characters to the application.
of the command, the output destination, and the
authorization ID. Operator response
This message records information in the variable
Issue the IMS /START SUBSYS command to establish a
recording area (VRA).
connection with Db2 and reenter the transaction.

System programmer response • 12 - Db2 connection unsuccessful. The external
subsystem encountered an error processing the
Determine why the IMS /STOP SUBSYS command was request.
issued.
• 24 - Db2 connection unsuccessful. The external
subsystem responded with a 'never connect' return
User response code from the initialization exit.
Wait for the IMS /START SUBSYS command to be • 28 - Db2 connection unsuccessful. IMS resources
issued before reentering the transaction. were unavailable to process the request.
• 32 - Db2 connection unsuccessful. An invalid EPL
Problem determination was encountered.
Analyze the application's SQLCA. • 36 - Db2 connection unsuccessful. Request rejected
due to the external subsystem invoking the
00D40062 subsystem termination service exit.
Control is returned to the application.
Explanation
The IMS attachment facility could not establish a Operator response
connection with Db2 because IMS is shutting down.
System action
The application's SQLCA is updated with an SQLCODE
-924 and reason code 00D40062. Control is returned This is an internal error. To be certain the proper
to the application. diagnostic information is available, stop the region
with a dump.
Operator response
Restart IMS.
The WAL control block in the dump contains an IMS
attach trace table. If you suspect an error in Db2,
System programmer response you might need to report the problem. For information
Determine why IMS was stopped. about identifying and reporting the problem, see
Reenter the transaction after IMS has been restarted. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
Analyze the application's SQLCA.
00D40063 spanning the failure.
Explanation
00D40069
The Db2 IMS attachment facility received an
unexpected return code from the IMS external
subsystem attach facility while attempting to start the
Explanation
subsystem connection to Db2. The Db2 IMS attachment facility received an
unexpected return code from the IMS external
System action subsystem attach facility while attempting to establish
a connection to Db2.
The application's SQLCA is updated with an SQLCODE
-924, reason code 00D40063, and the return code
received from the IMS external subsystem facility. One
System action
of the following return codes may appear. The application's SQLCA is updated with an SQLCODE
-924, reason code 00D40069, and the return code

received from the IMS External Subsystem Attach If you suspect an error in Db2, you might need to
Facility. Control is returned to the application. report the problem. For information about identifying

This is an internal error. To be certain the proper
diagnostic information is available, stop the region
with a dump.
The WAL control block in the dump contains an IMS were issued. Make sure that MSGLEVEL=(1,1) on the
attach trace table. If you suspect an error in Db2, JOB statement so that all diagnostic information is
you might need to report the problem. For information sent to SYSPRINT.
Collecting diagnostic data (Collecting data). • Copy of the DDITV02 SYSIN data set.
Collect the following diagnostic items: 00D44021

Explanation
executing IFCEREP1. The Db2-DL/I batch support cannot continue because
the length of a parameter value specified in the
DDITV02 SYSIN data set is incorrect.
System action
The Db2-DL/I batch support cannot continue and
00D44011 processing is terminated.

The Db2-DL/I batch support or IMS BMP job step Notify the system programmer.
cannot continue because the application program
could not be loaded.
System action Correct the DDITV02 SYSIN data set parameter value
in error and rerun the job. Make sure the correct data
The Db2-DL/I batch support or IMS BMP job step set name is specified by the DDITV02 DD statement
cannot continue and processing is terminated. and the DCB RECFM is F or FB for the data set.

Be sure the DDITV02 SYSIN data (for Db2-DL/I batch
support) or IMSBATCH procedure (for an IMS BMP job The parameter value length limits are the following
step) names a subsystem member (SSM) parameter numbers:
that points to a resource translation table (RTT). The • Db2 subsystem name: 0 < SSN < 5.
RTT maps the IMS application name to the Db2 plan
• LIT value < 5.
name.
• Db2 initialization module name = 8.
• Db2 optional resource translation module name < 9.

• Region error option value < 2. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• The command recognition value < 2. • SYSPRINT output, including JCL, for the application
• The connection name < 9. program or batch job, and system messages that
• The Db2 plan name < 9. JOB statement so that all diagnostic information is
• The application program load module name < 9. sent to SYSPRINT.
Register 8 indicates the delimiter following the field in • Copy of the DDITV02 SYSIN data set.
error. 00D44023
was run, and a listing of the SYSLOG data set for the The Db2-DL/I batch support cannot continue because
period of time that spans the failure. one or more of the DDITV02 SYSIN data set values are
• SYSABEND, SYSUDUMP, or SYSMDUMP output. incorrectly specified. The end of the input record was
• SYSPRINT output, including JCL, for the application detected before all the values were found.
were issued. Make sure that MSGLEVEL=(1,1) on the System action
sent to SYSPRINT. The Db2-DL/I batch support cannot continue and
processing is terminated.
• Copy of the DDITV02 SYSIN data set.
Explanation
The Db2-DL/I batch support cannot continue because System programmer response
the DDITV02 SYSIN data set cannot be opened or an
end of file was reached before a record was read. Correct the DDITV02 DD value or data set in error and
rerun the job. Make sure the correct data set name is
specified by the DDITV02 DD statement and the DCB
System action RECFM is F or FB for the data set.
The Db2-DL/I batch support cannot continue and If you suspect an error in Db2, you might need to
processing is terminated. report the problem. For information about identifying

System programmer response Check the DDITV02 DD SYSIN values for proper
format.
Correct the DDITV02 DD statement or data set in error
and rerun the job. Collect the following diagnostic items:
data (Collecting data). • SYSABEND, SYSUDUMP, or SYSMDUMP output.
See if a DDITV02 data set exists and contains a
properly formatted record.
sent to SYSPRINT.
Collect the following diagnostic items: • Copy of the DDITV02 SYSIN data set.

The Db2-DL/I batch support cannot continue because Notify the system programmer.
the DDITV02 SYSIN data set value for the Db2
initialization module refers to an incorrect module. System programmer response
Correct the DDITV02 SYSIN DD value for the region
System action
error option of R, Q, A, or null and rerun the job.
System programmer response Check the DDITV02 DD SYSIN value for the proper
value of the error option of R, Q, A, or null.
Correct the DDITV02 SYSIN DD value or data set
in error by specifying DSNMIN10 as the initialization Collect the following diagnostic items:
module and rerun the job.
and reporting the problem, see Collecting diagnostic • SYSABEND, SYSUDUMP, or SYSMDUMP output.
Problem determination were issued. Make sure that MSGLEVEL=(1,1) on the
Check the DDITV02 DD SYSIN value for the required JOB statement so that all diagnostic information is
parameter DSNMIN10. sent to SYSPRINT.
Collect the following diagnostic items: • Copy of the DDITV02 SYSIN data set.

• SYSABEND, SYSUDUMP, or SYSMDUMP output. The Db2-DL/I batch support cannot continue because
• SYSPRINT output, including JCL, for the application a connection could not be established to the Db2
program or batch job, and system messages that subsystem named in the DDITV02 SYSIN data set.
were issued. Make sure that MSGLEVEL=(1,1) on the This error usually occurs for one of these reasons:
• The Db2 subsystem name specified either in the
sent to SYSPRINT.
DDITV02 SYSIN data set (default) or in the member
• Copy of the DDITV02 SYSIN data set. defined by the IMSID-SSM combination is incorrect.
00D44025 • The Db2 system is not operational.

The Db2-DL/I batch support cannot continue because The Db2-DL/I batch support cannot continue and
the DDITV02 SYSIN data set value for the Db2 region processing is terminated.
error option is incorrect. Only R, Q, A, or null (specified
as ,,) are valid. Operator response
It might be necessary to start the Db2 subsystem
System action specified.

Either correct the DDITV02 DD SYSIN or the member The Db2-DL/I batch support cannot continue because
pointed to by the IMSID-SSM combination for the Db2 the Db2 create thread or signon failed.
subsystem name if it is incorrect, and rerun the job.
Otherwise, have the operator start the Db2 subsystem System action
if it is stopped.
processing terminates abnormally.
User response
Either check the DDITV02 DD SYSIN or the member User response
pointed to by the IMSID-SSM combination for the
proper Db2 subsystem name. Make sure the correct Verify that all required Db2 objects are available and
data set name is specified by the DDITV02 DD that the specified plan name is correct. If the problem
statement and the DCB RECFM is F or FB for the data persists, notify the system programmer.
set.
The WAL control block in the dump contains Problem determination
information about the connection and the IMS attach Examine the WAL control block in the dump, or any
trace table. Field WALSSID indicates the name of the X'5501FF00' IMS attachment log records in the IMS
Db2 subsystem being called. log data set (if available) for specific Db2 return and
The last entry in the trace table has an ID of ID00 and reason codes, along with the WALERN field which
the CALL STATUS contains the 2-byte return code and indicates the reason for the failure.
4-byte reason code of the failure. The 4-byte reason The WAL control block in the dump contains
code might provide additional diagnostic information information about the connection and the IMS attach
to help determine the cause of the failure. trace table. The last entry in the trace table will have
If you suspect an error in Db2, you might need to an ID of CTHD or SIGN and the CALL STATUS contains
report the problem. For information about identifying the two-byte return code and four-byte reason code of
and reporting the problem, see Collecting diagnostic the failure.
If the correct Db2 subsystem name was specified report the problem. For information about identifying
and was available, refer to the specific reason code and reporting the problem, see Collecting diagnostic
explanation for details about the error. data (Collecting data).
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• SYSPRINT output, including JCL, for the application • SYSPRINT output, including JCL, for the application
program or batch job, and system messages that program or batch job, and system messages that
were issued. Make sure that MSGLEVEL=(1,1) on the were issued. Make sure that MSGLEVEL=(1,1) on the
JOB statement so that all diagnostic information is JOB statement so that all diagnostic information is
sent to SYSPRINT. sent to SYSPRINT.
• Copy of the DDITV02 SYSIN data set. • Copy of the DDITV02 SYSIN data set.
• Copy of the DDOTV02 output data set. • Copy of the DDOTV02 output data set.
. 00D44033
00D44032

The Db2-DL/I batch support cannot continue because The Db2-DL/I batch support cannot continue because
the application is deadlocked or experienced a an unrecoverable error was encountered during
timeout. resolve indoubt processing between IMS and Db2.
The status of the current indoubt Db2 thread remains
System action unchanged.
Processing terminates and Db2 sends a message to

System action
the MVS console.
The Db2-DL/I batch support processing is terminated,
Operator response and a Db2 04E SVC dump is requested.
It might be necessary to schedule the application

Operator response
program when lock contentions or deadlock conditions
are less likely to occur. Enter the DISPLAY THREAD TYPE (INDOUBT)
command to determine the current status of indoubt
System programmer response thread processing between IMS and Db2 at the time of
the failure. Notify the system programmer.
To determine the reason for the deadlock or timeout
condition, review the information for the message that
was issued. Db2 issues message DSNT375I in the
case of a plan lock deadlock or DSNT376I in the case This may be an internal protocol error between the
of a plan lock timeout. IMS external subsystem attach facility and the Db2
IMS attachment facility, or an execution environment
error external to both IMS and Db2. Examine both the
IMS and MVS console logs for any error messages or
abnormal return codes associated with the DL/I batch
job.

Locate and examine any Db2 IMS attachment snap
records (code X'5501FE') that are present in the IMS
Problem determination log data set, and examine WAL trace table entries
included in the dump.
If a Db2 reason code is provided in either the WAL
trace entry, or the WALSFER2 field of the X'5501FE'
log record, follow the instructions associated with this
reason code for additional information concerning the
• SYSABEND, SYSUDUMP, or SYSMDUMP output. failure.
• SYSPRINT output, including JCL, for the application If you suspect an error in Db2, you might need to
program or batch job, and system messages that report the problem. For information about identifying
were issued. Make sure that MSGLEVEL=(1,1) on the and reporting the problem, see Collecting diagnostic
JOB statement so that all diagnostic information is data (Collecting data).
sent to SYSPRINT.
• Copy of the DDOTV02 output data set. • Console output from the system on which the job
Related information period of time that spans the failure.
DSNT375I (Db2 Messages) • Dynamic dump, taken to SYS1.DUMPxx data set, by
DSNT376I (Db2 Messages) Db2 (04E and 04F abends).
00D44034 • Listing of SYS1.LOGREC data set, obtained by

executing IFCEREP1.
• IMS trace output.

• IMS system log information, for the period of time JOB statement so that all diagnostic information is
spanning the failure. sent to SYSPRINT.
• SYSPRINT output, including JCL, for the application • Copy of the DDITV02 SYSIN data set.
program or batch job, and system messages that • Copy of the DDOTV02 output data set.
JOB statement so that all diagnostic information is 00D44036
sent to SYSPRINT.
• IMS console log. Explanation
• All dumps taken by the attachment facility or The Db2-DL/I batch support cannot continue because
requesting application. the authorization ID has been changed by the
• Console output from the system on which the job application program.
period from the last IPL to the time of the failure. System action
00D44035 The Db2-DL/I batch support cannot continue and
Explanation
The Db2-DL/I batch support cannot continue because Operator response
the PSB name used as the Db2 authorization ID Notify the system programmer.
begins with the character string SYSADM which is not
allowed.
System action This is a site problem. The application program has
modified the authorization ID.
processing is terminated. If you suspect an error in Db2, you might need to
System programmer response The authorization ID saved by Db2 does not match
This is a site problem. A PSB name beginning with the value in ASXBUSER or ASXBUSR8. Control block
SYSADM is being used as the authorization ID. modification has occurred. Register 3 plus X'34' is the
changed value.
report the problem. For information about identifying Collect the following diagnostic items:
Problem determination • SYSABEND, SYSUDUMP, or SYSMDUMP output.
The PSB= parameter of the job step execute statement • SYSPRINT output, including JCL, for the application
indicates the PSB name used. Register 3 plus X'34' is program or batch job, and system messages that
the authorization ID specified. were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
• Console output from the system on which the job • Copy of the DDITV02 SYSIN data set.
period of time that spans the failure. • Copy of the DDOTV02 output data set.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. 00D44037


The Db2-DL/I batch support cannot continue because The Db2-DL/I batch support cannot continue because
the stack of save areas has been exhausted. The error the record format (RECFM) for the DDOTV02 output
can occur when multiple levels of recursion have been data set has a format of fixed or fixed block.
invoked.
System action
System action
The Db2-DL/I batch support cannot continue and processing is terminated.
Operator response
Change the RECFM parameter in the DCB from fixed 'F'
Notify the system programmer or fixed blocked 'FB' to variable 'V' or variable blocked
'VB'. Specify LRECL=4092 and a BLKSIZE of at least
System programmer response LRECL+4. Then rerun the job.
This might be a multiple recursion problem caused by
the execution of a changed data capture exit.
Verify that the user exit(s) are not being recursively Problem determination
invoked during a database update operation.
Check the DDOTV02 DD for the proper DCB-RECFM
00D44038 value of 'V' or 'VB'.
Explanation
The Db2 IMS Attach facility attempted to notify the was run, and a listing of the SYSLOG data set for the
IMS subsystem that captured Db2 table data is ready period of time that spans the failure.
for propagation. However, the IMS exit manager was • Listing of SYS1.LOGREC data set, obtained by
not available for notification. executing IFCEREP1.
.
System action
00D44050
Db2 propagation processing is abnormally terminated.
Explanation
The Db2-DL/I batch support cannot continue because
This is a site problem. The required release of IMS is
a Db2 prepare problem was detected.
not available.
System action
User response
Problem determination Operator response

Verify that the IMS release that supports data
propagation from Db2 to IMS is installed.
This is an internal error. If you suspect an error in Db2,

attach trace table. The last entry in the trace table will JOB statement so that all diagnostic information is
have an ID of PREP. The CALL STATUS contains the sent to SYSPRINT.
two-byte return code and four-byte reason code of the
failure. • Copy of the DDITV02 SYSIN data set.
• Copy of the DDOTV02 output data set.
00D44052
• SYSABEND, SYSUDUMP, or SYSMDUMP output. The Db2-DL/I batch support cannot continue because
• SYSPRINT output, including JCL, for the application a Db2 abort problem was detected.
were issued. Make sure that MSGLEVEL=(1,1) on the System action
sent to SYSPRINT. The Db2-DL/I batch support cannot continue and
Operator response
00D44051

a Db2 commit continue problem was detected.
processing is terminated. Problem determination
The WAL control block in the dump contains an IMS
Operator response attach trace table. The last entry in the trace table will
have an ID of ABRT. The CALL STATUS contains the
failure.
attach trace table. The last entry in the trace table will JOB statement so that all diagnostic information is
have an ID of COMC. The CALL STATUS contains the sent to SYSPRINT.
failure. • Copy of the DDITV02 SYSIN data set.
00D44053

The Db2-DL/I batch support cannot continue because Notify the system programmer.
a DL/1 XRST call problem was detected.
System action
This is probably an application program error. Correct
The Db2-DL/I batch support cannot continue and the application program so it will issue the XRST
processing is terminated. call before any SQL statements are processed. Then
resubmit the job. Also make sure only one XRST call is
Operator response issued by the application program.
Check the DDOTV02 data set to see if an INDOUBT
unit of recovery has been erroneously aborted.
This is probably an application program error. Check and reporting the problem, see Collecting diagnostic
the PCB status code for a nonblank value, validate the data (Collecting data).
PCB used for the call, and validate the parameters
passed by the call. Correct the application program
and resubmit the job.
Follow normal IMS debugging techniques to gather the
DL/I documentation.
Follow normal IMS debugging techniques to gather the • SYSABEND, SYSUDUMP, or SYSMDUMP output.
IMS documentation. • SYSPRINT output, including JCL, for the application
• Console output from the system on which the job JOB statement so that all diagnostic information is
was run, and a listing of the SYSLOG data set for the sent to SYSPRINT.
program or batch job, and system messages that 00D44055
JOB statement so that all diagnostic information is Explanation
sent to SYSPRINT.
an IMS CHKP call problem was detected by IMS.
Explanation processing is terminated.
an IMS XRST call problem was detected. An XRST call, Operator response
if issued, must be issued before any SQL call is issued;
only one XRST call should be issued.

System action
This is probably an application program error. Check
the PCB status code for a nonblank value, validate the

PCB used for the call, and validate the parameters 2. Validate that the BKO= parameter for procedures is
passed by the call. Correct the application program set to Y.
and resubmit the job. 3. Resubmit the job.
If you suspect an error in Db2, you might need to Sometimes an application program error can cause
report the problem. For information about identifying this reason code. Complete the following actions to
and reporting the problem, see Collecting diagnostic correct the application error:
1. Check the PCB status code for a non-blank value.
Problem determination 2. Validate that the PCB used for the call is correct.
3. Validate the that parameters passed by the call is
correct.
IMS documentation.
4. Resubmit the job.
• SYSPRINT output, including JCL, for the application Problem determination
were issued. Make sure that MSGLEVEL=(1,1) on the Follow normal IMS debugging techniques to gather the
JOB statement so that all diagnostic information is IMS documentation.
sent to SYSPRINT. Collect the following diagnostic items:
• Copy of the DDITV02 SYSIN data set. • Console output from the system on which the job
• Copy of the DDOTV02 output data set. was run, and a listing of the SYSLOG data set for the
00D44056
Explanation • SYSPRINT output, including JCL, for the application
IMS detected a problem with the call to IMS ROLL or were issued. Make sure that MSGLEVEL=(1,1) on the
ROLB, which caused Db2 DL/I batch support to stop JOB statement so that all diagnostic information is
processing. One common reason for the problem is sent to SYSPRINT.
that a ROLB call was used with the BKO= parameter
for procedures set to N (which is the default setting),
and you used a temporary data set. • Copy of the DDOTV02 output data set.
00D44057
System action
The Db2 DL/I batch support processing is terminated. Explanation
Operator response an IMS call problem was detected by the Db2-DL/I
batch support. An IMS SYNC, ROLS, or SETS call is not
allowed.

One of two errors can result in this reason code: an
incorrect ROLB call or an application program error.
In most cases, the ROLB has incorrect settings and
data. Complete the following actions to correct the Operator response
ROLB call settings:
1. Validate that you are using an existing data set that
is not temporary.

This is probably an application program error. Correct • Console output from the system on which the job
the application program to use supported IMS calls was run, and a listing of the SYSLOG data set for the
and resubmit the job. period of time that spans the failure.
If you suspect an error in Db2, you might need to • SYSABEND, SYSUDUMP, or SYSMDUMP output.
report the problem. For information about identifying • SYSPRINT output, including JCL, for the application
and reporting the problem, see Collecting diagnostic program or batch job, and system messages that
data (Collecting data). were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
IMS documentation. • Copy of the DDOTV02 output data set.

Reason code identifiers that begin with 00D5 communicate normal and error situations with the XML
manager.
00D50001 00D50002
The amount of space allowed for processing XML The amount of space allowed for processing XML
values by a user has been exceeded. The amount of values by a subsystem has been exceeded. The
space allowed per user is 2GB. amount of space allowed for each subsystem is 50GB.

The operation is not allowed. Db2 issues the message, The operation is not allowed. Db2 issues the message,
"resource not available," to the invoker. "resource not available," to the invoker.

Check the SQL statements in the application for XML Monitor applications for storage use by XML values
usage. Monitor the application using a statistics trace using a statistics trace that includes IFCID 0002, or
that includes IFCID 0002, or an accounting trace that an accounting trace that includes IFCID 0003. Field
includes IFCID 0003. Field QXSTXMLV records the QXSTXMLV records the maximum amount of storage
maximum amount of storage that is used for XML that is used for XML values.
values.
The requested operation is not performed. SQLCODE
The requested operation is not performed. SQLCODE -904 is issued. Messages DSNT500I or DSNT501I
-904 is issued. Messages DSNT500I or DSNT501I might also be issued.
might also be issued.
• SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump
data set, as result of an operator-initiated dump command or SLIP trap exit.
command or SLIP trap exit. • Listing of SYS1.LOGREC data set, obtained by
• Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
executing IFCEREP1.
Related concepts
Related concepts Statistics trace (Db2 Performance)
Statistics trace (Db2 Performance) Accounting trace (Db2 Performance)
Accounting trace (Db2 Performance) Related information
Related information -904
-904 UNSUCCESSFUL EXECUTION CAUSED BY AN
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE. REASON reason-
UNAVAILABLE RESOURCE. REASON reason- code, TYPE OF RESOURCE resource-type, AND
code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name
RESOURCE NAME resource-name DSNT500I (Db2 Messages)
DSNT500I (Db2 Messages) DSNT501I (Db2 Messages)
00D50003

An XML subcomponent internal inconsistency was The SQL statement is rejected with SQLCODE-904 and
detected. this reason code. For a utility, the utility is rejected
with message DSNT500I and this reason code.
System action
The application program abends.
Install z/OS XML System Service. z/OS R1.7 or later is
Operator response required. If you are installing on z/OS R1.7, install z/OS
XML system service PTF.
00D50005

Explanation
This code generates an SVC dump and SYS1.LOGREC
entries. Use information from those two sources and The SQL statement could not be executed because
from the Problem Determination section of this code z/OS XML System Services for schema validation
to resolve the problem. If you suspect an error in Db2, service is not available.
about identifying and reporting the problem, see System action
The SQL statement is rejected with SQLCODE -904 and
this reason code.
The abend code can be issued by any of the XML System programmer response
subcomponent modules. The module name can be
Install z/OS XML System Services.
found in the SQLCA. SQLERRD1 in the SQLCA contains
a unique code that identifies the location within the Issue the following command to load the required
module where the error was detected. SQLERRM z/OS XML System Services module:
might contain some meaningful information for this
particular error. See the information about finding the SETPROG LPA,ADD,MODNAME=(GXLIMODV),
DSNAME=SYS1.SIEALNKE
SQLCA in For information about how to find the SQLCA,
see Finding the SQLCA (Diagnosing Db2 problems).. Related information
Collect the following diagnostic items: -904
• Listing of the results produced by the SQL RESOURCE NAME resource-name
statements.
00D50004
Explanation
The SQL statement or utility could not be executed
because z/OS XML System Service is not installed.

Reason code identifiers that begin with 00D6 communicate normal and error situations with Db2.
Explanation is requested.
Db2 detected an inconsistent condition. The index
entry for a LOB does not point to a valid LOB in the System programmer response
auxiliary table. The error is probably caused by an
extra index entry, but it could also result from a table If you suspect an error in Db2, you might need to
update not being redone when it should have been or report the problem. For information about identifying
from a point-in-time recovery. and reporting the problem, see Collecting diagnostic
System action
is requested. Message DSNI013I is issued to identify the index
page. Run the CHECK utility to identify the extent of
index inconsistency.
Message DSNI013I is issued to identify the index • Listing of SYS1.LOGREC data set, obtained by
page. Run the CHECK utility to identify the extent of executing IFCEREP1.
index inconsistency.
00D60803
period of time that spans the failure. An attempt was made to access a value in a column
• SVC dump (or system dump), taken to SYS1.DUMPxx with one of the LOB data types (BLOB, CLOB, DBCLOB),
data set, as result of an operator-initiated dump but the value of the column is no longer valid.
executing IFCEREP1. The operation is not allowed. Db2 returns 'resource
00D60100 not available' to its invoker.

Db2 detected an inconsistent condition. The index Use the CHECK LOB utility to identify the invalid LOBs.
entry for a LOB does not point to a valid LOB in the Use update to replace or delete to remove the invalid
auxiliary table. The error is probably caused by an LOBs.
extra index entry, but it could also result from a table If you suspect an error in Db2, you might need to
update not being redone when it should have been or report the problem. For information about identifying
from a point-in-time recovery. and reporting the problem, see Collecting diagnostic

The requested operation is not performed. An The requested operation is not performed.
was run, and a listing of the SYSLOG data set for the • SVC dump (or system dump), taken to SYS1.DUMPxx
period of time that spans the failure. data set, as result of an operator-initiated dump
data set, as result of an operator-initiated dump • Listing of SYS1.LOGREC data set, obtained by
command or SLIP trap exit. executing IFCEREP1.
00D60C03
executing IFCEREP1.
Related information
Explanation
-904
UNSUCCESSFUL EXECUTION CAUSED BY AN Unable to access a LOB data page because it is not
UNAVAILABLE RESOURCE. REASON reason- formatted or it belongs to another LOB.
RESOURCE NAME resource-name System action
DSNT500I (Db2 Messages) The operation is not allowed.
00D60C02 System programmer response

Run CHECK LOB to determine the extent of the
Explanation inconsistency.
Auxiliary index entry not found. An attempt was made If you suspect an error in Db2, you might need to
to access an auxiliary index, but the entry was missing. report the problem. For information about identifying
This could be caused by not recovering all the table and reporting the problem, see Collecting diagnostic
spaces in the a table space set to the same point in data (Collecting data).
time.
System action The requested operation is not performed.
The operation is not allowed. Collect the following diagnostic items:
Use the CHECK DATA to determine the rows of the period of time that spans the failure.
table which are inconsistent. Use SQL UPDATE or • SVC dump (or system dump), taken to SYS1.DUMPxx
DELETE to correct these errors. data set, as result of an operator-initiated dump
If you suspect an error in Db2, you might need to command or SLIP trap exit.

Reason code identifiers that begin with 00D7 communicate normal and error situations with the data
space manager.
00D70001 • Listing of the results produced by the SQL
statements.
Explanation • Listing of Db2 catalog tables.
Either the data space manager (DSM) subcomponent • SYSPRINT output, including JCL, for the application
of Db2 could not access some storage group definition, program or batch job, and system messages that
or the storage group contains no volume IDs. Possible were issued. Make sure that MSGLEVEL=(1,1) on the
sources of the error include use of an incorrect name JOB statement so that all diagnostic information is
for the storage group and removal of all volume IDs via sent to SYSPRINT.
ALTER STOGROUP without providing new ones. • Definitions of views and tables involved in the error.
00D70002
System action
A 'resource not available' code is returned to the caller. Explanation
The required data sets are not available to Db2.
System programmer response This is probably a user error. For example, the user
Notify the database administrator if appropriate. might have forgotten to create the needed VSAM data
Otherwise, check the SQLCA for the name of the clusters using access method services before issuing
storage group. Check this storage group (via an SQL a CREATE TABLESPACE request with the USING VCAT
SELECT on SYSIBM.SYSSTOGROUP) to ensure that parameter.
it exists. Check for associated SYSIBM.SYSVOLUMES
table entries to see if any volume IDs exist for this System action
storage group.
data (Collecting data). Take one or both of these actions:
• Make the needed data set available.
User response • Be sure it is cataloged in the appropriate integrated
If you are unable to resolve the problem catalog facility (ICF) catalog.
yourself, notify the system programmer or database The data set names appear in the SQLCA, in the
administrator. DSNP-prefixed message that contained this code, or
in an earlier DSNP-prefixed message for the same user
Problem determination (same connection and correlation IDs).
Obtain output listing from SELECT * FROM If the data set name is correct, is cataloged, and
SYSIBM.SYSSTOGROUP and SELECT * FROM appears in the VTOC, run the access method services
SYSIBM.SYSVOLUMES, details of the request that DIAGNOSE command on the integrated catalog facility
resulted in this code, and contents of the SQLCA. (ICF) catalog identified by the first qualifier of the data
Also obtain operator's console sheet showing related set name.
messages, if any. Use this documentation to determine
the cause of the problem. User response
Collect the following diagnostic items: If you are unable to resolve the problem, notify the
• Console output from the system on which the job system programmer or database administrator.

Problem determination messages DSNP002I or DSNP022I.If you suspect an
Obtain the following information to determine the For information about identifying and reporting the
cause of the problem: problem, see Collecting diagnostic data (Collecting
• Listings of the integrated catalog facility (ICF) data).
catalog and VTOC showing the data set This may occur if a user creates a data set with
• Details of the request that led to this code VSAM access method services (intending to use it for a
• The contents of the SQLCA table space or index), then creates the table space or
index via SQL CREATE statement, but forgets to specify
• The operator's console sheet showing any related USING VCAT.
messages
Another possibility is that the data set remained
Collect the following diagnostic items: from some prior, unsuccessfully completed DROP or
• Console output from the system on which the job DELETEor backout operation of Db2. This failure would
was run, and a listing of the SYSLOG data set for the probably occur if the data set or integrated catalog
period of time that spans the failure. facility (ICF) catalog were unavailable at the time of
the DROP or DELETE or backout. For example, packs
may be offline, or other operational problems may
exist. In this case, the table space would be dropped,
• IDCAMS LISTCAT output for the ICF (VSAM) catalog but the data sets could remain and be brought back
that contains the Db2 subsystem catalog that online at a later time.
There should have been some indication of this type
• VTOC listing of the disk volume on which the failing of failure at the time it occurred. (for example, some
operation occurred. DSNP-prefixed message indicating the data set was
• Listing of the results produced by the SQL not deleted). You might check recent console sheets
statements. for such a message; however, it may have happened a
• Listing of Db2 catalog tables. long time ago.

program or batch job, and system messages that System action
were issued. Make sure that MSGLEVEL=(1,1) on the Error indication is returned to the user.
sent to SYSPRINT.
Notify the database administrator if appropriate.
If you suspect an error in Db2, you might need to Otherwise, either use access method services to
report the problem. For information about identifying delete the data set or use a different name for the
and reporting the problem, see Collecting diagnostic table or index you are trying to create.
If the data set name is correct, is cataloged, and
Related concepts appears in the VTOC, run the access method services
DSNP messages (Db2 Messages) DIAGNOSE command against the integrated catalog
Related reference facility (ICF) catalog identified by the first qualifier of
CREATE TABLESPACE (Db2 SQL) the data set name.
Related information
DIAGNOSE command (DFSMS Access Method User response
Services for Catalogs)
If you are unable to resolve the problem
yourself, notify the system programmer or database
00D70003
administrator.
Explanation
Some or all of the data sets already exist. The data
Information is needed concerning the history of the
space manager (DSM) subcomponent of Db2 has
use of this data set; that is, of the table space/index
discovered the preexistence of a data set that has
name in conjunction with this database name. Listings
the same name as one it was about to create. The
of the console, integrated catalog facility (ICF) catalog,
name of the data set appears in the SQLCA or in
and VTOC may also be needed, with details of the

request that resulted in this code, and contents of the System action
SQLCA. Also obtain operator's console sheet showing
related messages, if any. Use this documentation to Error indication is returned to the user.
determine the cause of the problem.
Collect the following diagnostic items: System programmer response
• Console output from the system on which the job The user must commit the drop of the data set on the
was run, and a listing of the SYSLOG data set for the drop list. Collect the materials listed in the Problem
period of time that spans the failure. Determination section of this message to determine
the specific cause of the problem.
User response
data set, as result of an operator-initiated dump You must commit the drop prior to redefining. Notify
command or SLIP trap exit. the system programmer or database administrator, if
• IDCAMS LISTCAT output for the ICF (VSAM) catalog necessary.
defined the failing index or table. Problem determination
• VTOC listing of the disk volume on which the failing Documentation is needed showing activities from the
operation occurred. last committed action up to and including details of
• Listing of the results produced by the SQL the request that resulted in this code. You also need
statements. to examine the contents of the SQLCA. Also obtain
operator's console sheet showing related messages, if
any. Use this documentation to determine the cause of
• SYSPRINT output, including JCL, for the application the problem. If you suspect an error in Db2, you might
program or batch job, and system messages that need to report the problem. For information about
were issued. Make sure that MSGLEVEL=(1,1) on the identifying and reporting the problem, see Collecting
JOB statement so that all diagnostic information is diagnostic data (Collecting data).
sent to SYSPRINT.
Related concepts was run, and a listing of the SYSLOG data set for the
SQL communication area (SQLCA) (Db2 SQL) period of time that spans the failure.
Related reference • Dynamic dump, taken to SYS1.DUMPxx data set, by
Data set naming conventions (Db2 Db2 (04E and 04F abends).
Description of SQLCA fields (Db2 SQL) statements.
Related information
DSNP002I (Db2 Messages) program or batch job, and system messages that
DSNP022I (Db2 Messages) were issued. Make sure that MSGLEVEL=(1,1) on the
DIAGNOSE command (DFSMS Access Method JOB statement so that all diagnostic information is
Services for Catalogs) sent to SYSPRINT.
00D70004
00D70005
Explanation
Explanation
Certain data sets are pending deletion. Creation of a
new data set is blocked by the presence of the name The specified data set was access method services
on a drop list. This is usually a user error. It usually user-defined. It does not have the required Db2
occurs when the user has dropped an old object (table attributes.
space, index, and so forth) and then attempted to
redefine it without committing the drop.
System action
No action is taken with the named data set. An error
code is returned and a dump is not taken.

System programmer response defined the failing index or table.
Delete the named data set and define it with the • VTOC listing of the disk volume on which the failing
correct attributes. operation occurred.
Problem determination statements.
Obtain an access method services LISTCAT for the • Listing of Db2 catalog tables.
named data set's attributes. • SYSPRINT output, including JCL, for the application
Related tasks
Migration step 15: Define system data sets: JOB statement so that all diagnostic information is
DSNTIJIN (Db2 Installation and Migration) sent to SYSPRINT.
00D70006 • Definitions of views and tables involved in the error.
00D70007
Explanation
The data sets are not owned by this Db2 subsystem. Explanation
The data sets backing a table space or index can The specified data set must be cataloged in an ICF
be deleted only by the data space manager (DSM) catalog. It was found in a non-ICF catalog.
subcomponent of the Db2 subsystem that created
them or by one having the same authorization ID at the
time of installation. This is a safety feature to restrict System action
DSM from deleting data sets that might have been No action is taken with the named data set. An error
created by the user but that have a name that matches code is returned and a dump is not taken.
the one we are trying to delete. This safety feature
also prevents the deletion of data sets that might have
been created by some other Db2 subsystem and that Operator response
are still needed there. Notify the system programmer.

The data sets remain intact. Delete the named data set, define it again, and use an
ICF catalog
User response
If you are unable to resolve the problem Problem determination
yourself, notify the system programmer or database Obtain an access method series LISTCAT for the
administrator. named data set's catalog types.
Related tasks
Installation step 4: Define the ICF catalog and
Obtain integrated catalog facility (ICF) catalog and alias: DSNTIJCA (optional) (Db2 Installation and
VTOC listings, details of the request that resulted in Migration)
this code, and contents of the SQLCA. Also obtain Installation step 5: Define system data sets:
operator's console sheet showing related messages, if DSNTIJIN (Db2 Installation and Migration)
any. This documentation will assist you in determining Defining your own user-managed data sets (Db2
the cause of the problem. Administration Guide)
Collect the following diagnostic items: Related reference
• Console output from the system on which the job DEFINE CATALOG field (Db2 Installation and
was run, and a listing of the SYSLOG data set for the Migration)
00D70008

Explanation code, TYPE OF RESOURCE resource-type, AND
During allocation of a data set, Db2 detected that
the attributes for the data set were incorrect. The LISTCAT command (DFSMS Access Method
data set requires the extended format and extended Services for Catalogs)
addressability attributes that are defined through
DFSMS. If a key label is specified, the data set requires 00D70009
the extended format attribute that is defined through
DFSMS. Either the data set was defined without the Explanation
required attributes, or it was not defined through
The specified data set was access method services
DFSMS.
user-defined. It does not have the required Db2
attributes. The data set was defined with a Control
System action Interval (CI) size that is incompatible with the page
No data set is allocated. SQLCODE -904 is issued. size. A compatible CI size is either 4K or the page
Additional messages or codes might be issued. size. For example, if the page size is 32K, the
ControlIntervalSize parameter in the Define command
should be specified with either 4K or 32K. Db2
System programmer or storage recommends the use of the page size as the Control
administrator response Interval size.
Data sets that are larger than 4GB must belong to a
DFSMS data class that is defined with the extended System action
format and extended addressability attributes. Data
sets that use key label must belong to a DFSMS data
This reason code and the data set name are made
class that is defined with the extended format.
1. If the diagnostic message that issued this code
includes a reference to STOGROUP 00000001, System programmer response
then the data set is a catalog or directory data set.
Use the LISTCAT command to determine the name Ensure that the data set is defined with the compatible
of the data set. CI size, which is 4K or its page size.
2. Update the data set class definition in DFSMS. On
the DATA SET CLASS DEFINE panel, specify the User response
following values:
Delete the data set that was named and redefine it
Field Value with the correct CI attributes.
DATA SET NAME TYPE EXT

EXTENDED Y
Obtain an access method services LISTCAT for the
ADDRESSABILITY
named data set's attributes.
3. Make sure that the automatic class selection
Related concepts
routine associates this data set with this data class.
Control interval sizing (Db2 Administration
Guide)
User response Related tasks
Notify the system programmer or storage Defining your own user-managed data sets (Db2
administrator. Administration Guide)
Related reference
Problem determination VARY DS CONTROL INTERVAL field (DSVCI
Obtain the data set attribute information from the Migration)
corresponding SMS data class for the named data set.
Job DSNTIJIN (Db2 Installation and Migration)
Related information
-904 00D70010

Explanation For the name of the data set from which the name of
the table space, index space, and/or partition can be
This is an internal error. An attempt to extend a data derived, see message DSNP001I or DSNP007I and the
set failed because a problem was detected in the DSM SQLCA.
notify process.
System action
System action
No extension is done.
The data sharing extend is incomplete.

Operator response
Notify the system programmer or database Otherwise, if the table space is partitioned and there is
administrator. space in other partitions, you may be able to redefine
the table space with new partitioning parameters so
System programmer response that the data that has overloaded this partition is
directed to others. If the table space is not partitioned,
For additional information, see the description of you probably have more than one table residing in this
message DSNP021I. table space. Define another table space, unload this
one, then reload the tables into the separate spaces.
Problem determination (Be aware that this is a very large amount of data to
move. Careful planning is recommended.)
Obtain the console sheet showing the associated
DSNP021I message and any related messages If a large DGTT cannot be contained in a single existing
preceding that message. table space in the work file database, consider altering
the MAXPARTITIONS attribute to increase the number
If you suspect an error in Db2, you might need to of partitions if it is a PBG table space, or create larger
report the problem. For information about identifying table spaces. Because you do not control which table
and reporting the problem, see Collecting diagnostic space is used, the recommendation is to create all
data (Collecting data). work file table spaces with sufficient space.
00D70011
User response
Explanation If this condition occurs when inserting into a DGTT or
The data space manager (DSM) subcomponent of Db2 sort work file and other concurrent jobs are competing
has been requested to extend a table space or index the for storage space, try rerunning the job when the
space, but the table space or index space has already usage is less. If the same condition is encountered for
been extended to its maximum size. This situation DGTT use when no other jobs are running the table
does not mean that no more is space available in space is not big enough to hold all the data.
the page set for the requested insert. An additional If you are unable to resolve the problem
search will be performed for space in the current table yourself, notify the system programmer or database
space or index space. If space cannot be found, then administrator.
the data manager component will issue reason code
00C9009C for a partitioned page set or 00C9009D for
a non-partitioned page set. Problem determination
If this condition is encountered when trying to insert If you believe the table space or index space has
into a traditional sort work file, other table spaces in not yet reached maximum size, provide listings of the
the work file database are searched for space. If none console, integrated catalog facility (ICF) catalog, and
is available, the job fails with a "resource not available" VTOC.
code. If you suspect an error in Db2, you might need to
If this condition is encountered for a table space in report the problem. For information about identifying
a work file database when inserting into a DGTT, the and reporting the problem, see Collecting diagnostic
job might fail with resource unavailable because other data (Collecting data).
concurrent jobs are competing for storage in the work Collect the following diagnostic items:
file database. If it is encountered for DGTT use when
no other jobs are running, it indicates the table space
is not big enough to hold all the data.

• Console output from the system on which the job User response
period of time that spans the failure. Ensure that the correct password is being used. If you
are unable to resolve the problem yourself, notify the
• Dynamic dump, taken to SYS1.DUMPxx data set, by database administrator.
defined the failing index or table. Obtain output from SQL SELECT * FROM
• VTOC listing of the disk volume on which the failing SYSIBM.SYSTABLESPACE and (if storage group
operation occurred. related) SELECT * FROM SYSIBM.SYSSTOGROUP. Also
obtain integrated catalog facility (ICF) catalog listing,
• Listing of the results produced by the SQL details of the request that resulted in this code,
statements. and contents of the SQLCA. Also obtain operator's
• Listing of Db2 catalog tables. console sheet showing related messages, if any. This
• SYSPRINT output, including JCL, for the application documentation will assist you in determining the
program or batch job, and system messages that cause of the problem if it is not merely an incorrect
were issued. Make sure that MSGLEVEL=(1,1) on the password. If you suspect an error in Db2, If you
JOB statement so that all diagnostic information is suspect an error in Db2, you might need to report
sent to SYSPRINT. the problem. For information about identifying and
• Definitions of views and tables involved in the error. (Collecting data).
Related concepts Collect the following diagnostic items:
Related reference
Limits in Db2 for z/OS (Db2 SQL) period of time that spans the failure.
Data set naming conventions (Db2
Related information
DSNP001I (Db2 Messages)
DSNP007I (Db2 Messages) defined the failing index or table.
00D70012 • Listing of the results produced by the SQL
statements.
Explanation • Listing of Db2 catalog tables.
A password or security error has occurred. An attempt
to access a integrated catalog facility (ICF) catalog
entry for a cluster (data set) failed because of some
security violation. This is probably a user error. It
sent to SYSPRINT.
may be caused either by the incorrect specification
of a password or the changing of the password in • Definitions of views and tables involved in the error.
the Db2 catalog (via SQL ALTER) but not in the 00D70013
integrated catalog facility (ICF) catalog (via access
method services ALTER) or vice versa.
Explanation
System action A required integrated catalog facility (ICF) catalog
does not exist or is inaccessible. An attempt to access
A 'resource not available' code is returned to the user. an integrated catalog facility (ICF) catalog entry for a
cluster (data set) failed. This is probably a user error.
Notify the database administrator if appropriate. System action
Otherwise, check the passwords and/or RACF A 'resource not available' code is returned to the user.
authorizations.

Take the following actions: Abort the request.
• Check that the proper catalog name was specified
and is available to Db2. Operator response
• Check the associated DSNP012I message on the Notify the system programmer or database
operator's console for the integrated catalog facility administrator.
(ICF) return and reason codes.
• See the description of DSNP012I. System programmer response
• Look for any related messages on the console sheet. Notify the database administrator if appropriate.
• Refer to the appropriate MVS publication for a Otherwise, check the packs available to the data
description of message IDC3009I. set. They might merely be full or the data set might
have reached its maximum allowable extents. For
User response more information, see the description of message
DSNP001I.
If you are unable to resolve the problem, notify the
system programmer or database administrator.
User response
Problem determination Notify the operator, system programmer, or database
administrator.
Obtain the following to help you determine the cause
of the problem:
• Details of the request that resulted in this code
Obtain console sheet that shows associated
• Contents of the SQLCA DSNP001I, DSNO007I, or DSNP011I messages and
Collect the following diagnostic items: any related messages that precede them. This
documentation can assist you in determining the
• Console output from the system on which the job cause of the problem. For more information, see the
was run, and a listing of the SYSLOG data set for the description of these messages.
In some cases, this problem might occur because Db2
• Dynamic dump, taken to SYS1.DUMPxx data set, by encountered unexpected user-created catalog index
Db2 (04E and 04F abends). definitions that interfere with the migration process.
• IDCAMS LISTCAT output for the ICF (VSAM) catalog See the information about migration job DSNTIJPM
that contains the Db2 subsystem catalog that and the information about creating indexes on catalog
defined the failing index or table. tables in the description of CREATE INDEX.
• Listing of the results produced by the SQL Collect the following diagnostic items:
statements.
• SYSPRINT output, including JCL, for the application was run, and a listing of the SYSLOG data set for the
program or batch job, and system messages that period of time that spans the failure.
JOB statement so that all diagnostic information is • Dynamic dump, taken to SYS1.DUMPxx data set, by
sent to SYSPRINT. Db2 (04E and 04F abends).
• Definitions of views and tables involved in the error. • SVC dump (or system dump), taken to SYS1.DUMPxx
00D70014 command or SLIP trap exit.
An attempt to extend a data set failed, because a executing IFCEREP1.
problem was detected in media manager services. • IDCAMS LISTCAT output for the ICF (VSAM) catalog
One possible cause of this error is that a table was that contains the Db2 subsystem catalog that
created or the definition of a table was completed in a defined the failing index or table.
simple table space. Db2 attempted to insert a system • VTOC listing of the disk volume on which the failing
page in the table space, but there was not enough operation occurred.
room to insert the system page.

• Listing of the results produced by the SQL • SVC dump (or system dump), taken to SYS1.DUMPxx
statements. data set, as result of an operator-initiated dump
• SYSPRINT output, including JCL, for the application command or SLIP trap exit.
program or batch job, and system messages that • SYSABEND, SYSUDUMP, or SYSMDUMP output.
were issued. Make sure that MSGLEVEL=(1,1) on the • Listing of SYS1.LOGREC data set, obtained by
JOB statement so that all diagnostic information is executing IFCEREP1.
sent to SYSPRINT.
• Definitions of views and tables involved in the error. that contains the Db2 subsystem catalog that
Related tasks defined the failing index or table.
Run premigration queries (DSNTIJPM) (Db2 • VTOC listing of the disk volume on which the failing
Installation and Migration) operation occurred.
Related reference • Listing of the results produced by the SQL
CREATE INDEX (Db2 SQL) statements.
Related information • SYSPRINT output, including JCL, for the application
DSNP001I (Db2 Messages) program or batch job, and system messages that
00D70015 JOB statement so that all diagnostic information is
sent to SYSPRINT.
Explanation • Definitions of views and tables involved in the error.
An attempt to update the high-used RBA for a data set 00D70016
failed in media manager services.
Explanation
System action
This is an internal error. An attempt to extend a data
Abort the request. set failed because a problem was detected in the DSM
notify process.
Operator response
System action
Notify the system programmer or database
administrator. The data sharing extend is incomplete.

Notify the database administrator (DBA), if Notify the system programmer or database
appropriate. The DBA should be made aware of the administrator.
extend problem. However, this is probably a system
problem.
Problem determination For additional information, see the description of
message DSNP021I.
Obtain console sheet showing associated DSNP001I,
DSNO007I, or DSNP011I messages and any related
messages preceding them. This documentation will
assist you in determining the cause of the problem. Obtain the console sheet showing the associated
For additional information, see the description of these DSNP021I message and any related messages
messages. preceding that message.
Collect the following diagnostic items: If you suspect an error in Db2, you might need to
• Dynamic dump, taken to SYS1.DUMPxx data set, by 00D70017

An error occurred while attempting to obtain Abort the request.
information from an integrated catalog facility (ICF)
catalog. Operator response
System action
The request is terminated. System programmer response
Collect the materials listed in the Problem
Determination section of this message. If you suspect
Ensure that the proper packs and catalog are online an error in Db2, you might need to report the problem.
and operating correctly. See message DSNP012I. For information about identifying and reporting the
Problem determination data).

Request a dynamic dump. In the dump, the second
parameter passed to the data set inquiry function
identifies the table space or index space. The third
• Dynamic dump, taken to SYS1.DUMPxx data set, by parameter is the table space or index space object
Db2 (04E and 04F abends). descriptor block (OBD). The OBD indicates whether or
• SVC dump (or system dump), taken to SYS1.DUMPxx not the table space or index space is partitioned. If
data set, as result of an operator-initiated dump it is partitioned, the calling module is in error. If it is
command or SLIP trap exit. not partitioned, the test in the data set inquiry function
must be at fault.
• Listing of SYS1.LOGREC data set, obtained by Collect the following diagnostic items:
executing IFCEREP1. • Console output from the system on which the job
• IDCAMS LISTCAT output for the ICF (VSAM) catalog was run, and a listing of the SYSLOG data set for the
that contains the Db2 subsystem catalog that period of time that spans the failure.
defined the failing index or table. • Dynamic dump, taken to SYS1.DUMPxx data set, by
• Listing of the results produced by the SQL Db2 (04E and 04F abends).
statements. • IDCAMS LISTCAT output for the ICF (VSAM) catalog
• SYSPRINT output, including JCL, for the application that contains the Db2 subsystem catalog that
program or batch job, and system messages that defined the failing index or table.
were issued. Make sure that MSGLEVEL=(1,1) on the • Listing of the results produced by the SQL
JOB statement so that all diagnostic information is statements.
sent to SYSPRINT.
00D70018 program or batch job, and system messages that
Explanation
sent to SYSPRINT.
This is a Db2 internal error. One of the following • Definitions of views and tables involved in the error.
circumstances has occurred:
00D70019
• A data set inquiry function was called for a
partitioned table space or index space. Its function
applies only to nonpartitioned table spaces or index Explanation
spaces. The data space manager (DSM) subcomponent of Db2
• The reset function of data space manager (DSM) could not release the extend lock it acquired against a
was called on a table space that had been opened data set during an attempt to extend that data set.
incorrectly.

The SQL request that led to the abend is terminated, This is probably an internal error. An attempt to extend
and the unit of recovery that issued the request is a data set failed because a problem was detected
backed out. in media manager services during the DSM notify
process.
Operator response
System action
The request is terminated.
Operator response
Investigate the DSM messages associated with this
condition (at least message DSNP015I) for clues to the Notify the system programmer or database
problem. If you suspect an error in Db2, you might administrator.
identifying and reporting the problem, see Collecting System programmer response
For additional information, see the description of
message DSNP021I.
This problem is probably the result of either: (1) an Problem determination
attempt by DSM to free a lock it did not hold or,
(2) a problem in IRLM. The IRLM return and reason Obtain the console sheet showing the associated
codes appear in the associated DSNP015I message. DSNP021I message and any related messages
For additional information, see the description of this preceding that message.
message.
Collect the following diagnostic items: report the problem. For information about identifying
• SVC dump (or system dump), taken to SYS1.DUMPxx The data space manager (DSM) subcomponent of Db2
data set, as result of an operator-initiated dump could not write a required log record.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. System action
executing IFCEREP1. Abort the request.

that contains the Db2 subsystem catalog that Operator response
defined the failing index or table. Notify the system programmer.
statements. System programmer response
Collect the materials listed in the Problem
Determination section of this message.
JOB statement so that all diagnostic information is If you suspect an error in Db2, you might need to
sent to SYSPRINT. report the problem. For information about identifying
• Definitions of views and tables involved in the error. and reporting the problem, see Collecting diagnostic
00D70020

period of time that spans the failure. • Definitions of views and tables involved in the error.
00D70023
statements. Explanation
• SYSPRINT output, including JCL, for the application There is an insufficient amount of space in primary
program or batch job, and system messages that allocation to format control pages.
JOB statement so that all diagnostic information is System action
sent to SYSPRINT.
The requested table space or index space creation is
backed out.
archive tapes.
Operator response
00D70022
administrator.
Explanation
The data space manager subcomponent of Db2 is System programmer response
unable to acquire a needed lock. The extend request
can not be completed.
Otherwise, increase the primary allocation value in the
data set that was defined directly via access method
System action services. (This should not happen for storage group
related data sets, because the Db2 interpreter ensures
Abort the request.
a sufficient setting for the primary value.)
Operator response
Obtain integrated catalog facility (ICF) catalog and
VTOC listings, details of the request that led to
System programmer response this code, and contents of the SQLCA. If you
Obtain documentation from message DSNP014I. If suspect an error in Db2, you might need to report
you suspect an error in Db2, you might need to report the problem. For information about identifying and
the problem. For information about identifying and reporting the problem, see Collecting diagnostic data
reporting the problem, see Collecting diagnostic data (Collecting data). Results of SQL SELECT * FROM
(Collecting data). SYSIBM.SYSTABLESPACE may also be useful. Also
obtain the operator's console sheet showing related
messages, if any.
See message DSNP014I.
Collect the following diagnostic items: was run, and a listing of the SYSLOG data set for the
was run, and a listing of the SYSLOG data set for the • Dynamic dump, taken to SYS1.DUMPxx data set, by
period of time that spans the failure. Db2 (04E and 04F abends).
• Dynamic dump, taken to SYS1.DUMPxx data set, by • IDCAMS LISTCAT output for the ICF (VSAM) catalog
Db2 (04E and 04F abends). that contains the Db2 subsystem catalog that
• Listing of the results produced by the SQL defined the failing index or table.
statements. • VTOC listing of the disk volume on which the failing
• SYSPRINT output, including JCL, for the application operation occurred.
program or batch job, and system messages that • Listing of Db2 catalog tables.

• SYSPRINT output, including JCL, for the application • VTOC listing of the disk volume on which the failing
program or batch job, and system messages that operation occurred.
were issued. Make sure that MSGLEVEL=(1,1) on the • Listing of the results produced by the SQL
JOB statement so that all diagnostic information is statements.
sent to SYSPRINT.
• Definitions of views and tables involved in the error. program or batch job, and system messages that
00D70024 were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
Explanation
No data sets exist for a nonpartitioned table space or
index space. Because at least one existed at create If you suspect an error in Db2, you might need to
time, a serious problem might have occurred for this report the problem. For information about identifying
table space or index space. The name of the data set and reporting the problem, see Collecting diagnostic
that Db2 expected to find for the table space or index data (Collecting data).
space appears in message DSNP012I and/or in the Related concepts
SQLCA along with the reason code. SQL communication area (SQLCA) (Db2 SQL)
Related information
System action DIAGNOSE command (DFSMS Access Method
The request is terminated. Services for Catalogs)
DSNP012I (Db2 Messages)
Ensure that the data set and its pack are available to
Db2 and that the data set has not been inadvertently Explanation
deleted or migrated by any DASD operation.
An access method services request failed.
If the data set name is correct, is cataloged, and
appears in the VTOC, run the access method services
DIAGNOSE command on the integrated catalog facility System action
(ICF) catalog identified by the first qualifier of the data Abort the request.
set name.
Operator response
Obtain the following items: administrator.
• The integrated catalog facility (ICF) catalog
• The VTOC listings System programmer response
• Details of the request that led to this code Examine messages DSNP009I and DSNP010I on the
• Contents of the SQLCA operator's console for the access method services
messages they encompass. Refer to the appropriate
• The operator's console sheet showing related MVS publication for information about specific access
messages method services messages received.
was run, and a listing of the SYSLOG data set for the See the message DSNP009I description.
• IDCAMS LISTCAT output for the ICF (VSAM) catalog was run, and a listing of the SYSLOG data set for the
that contains the Db2 subsystem catalog that period of time that spans the failure.
defined the failing index or table. • Dynamic dump, taken to SYS1.DUMPxx data set, by

• IDCAMS LISTCAT output for the ICF (VSAM) catalog System action
defined the failing index or table. The request to extend the data set is terminated.
operation occurred. System programmer response
• Listing of the results produced by the SQL Notify the database administrator if appropriate.
statements. Otherwise, if you intended to allow physical extension
• SYSPRINT output, including JCL, for the application of the data set, change its secondary value to a
program or batch job, and system messages that nonzero quantity.
JOB statement so that all diagnostic information is Problem determination
sent to SYSPRINT.
Obtain the integrated catalog facility (ICF) catalog
• Definitions of views and tables involved in the error. and VTOC listings, and (if storage group-defined) the
00D70026 output from SELECT * FROM SYSIBM.SYSSTOGROUP.
Also obtain details of the request that resulted in
this code, contents of the SQLCA, and the operator's
Explanation console sheet showing related messages, if any.
This is an internal error. An attempt to extend a data Collect the following diagnostic items:
set failed because a problem was detected in the DSM
notify process. • Console output from the system on which the job
System action
The data sharing extend did not complete. Db2 (04E and 04F abends).
Operator response that contains the Db2 subsystem catalog that
administrator. • VTOC listing of the disk volume on which the failing
operation occurred.
System programmer response • Listing of the results produced by the SQL
statements.
message DSNP022I.
Obtain the console sheet showing the associated JOB statement so that all diagnostic information is
DSNP022I message and any related messages sent to SYSPRINT.
preceding that message. • Definitions of views and tables involved in the error.
00D70027 An HSM request for the recall of a migrated data set
failed.
Explanation
System action
The secondary allocation value is 0. No physical
extension is done. If this occurs in a create of a The HSM recall is aborted by data space manager and
segmented table, the primary allocation of the table control returns to the function that issued the recall
space is not big enough to allocate the first segment. request. The higher level function will not necessarily
The first segment consists of a number of pages which terminate processing since the data set may have
are defined in SEGSIZE. already been recalled.

If processing was terminated, notify the system Unexpected reason code was received from some Db2
programmer or database administrator. subcomponent invoked by data space manager (DSM).
Almost any DSNP module can issue this reason code.
If processing was terminated, investigate the reason System action
for the HSM failure via messages issued to the MVS
Abort the request.
operator's console. If you suspect an error in Db2,
about identifying and reporting the problem, see Operator response

Refer to the problem determination section(s) of the
There is not much the system programmer can do
associated Db2 and HSM messages which were issued
here, but see register 2 in the accompanying dump
to the MVS operator's console.
for the unexpected code. Its description may provide
Collect the following diagnostic item listed in a clue to the type of problem. If you suspect an
data).
00D70029
Explanation Obtain a listing of the SQL request that resulted in
Db2 could not access a data set because the data set this code and a listing of the contents of the SQLCA.
is on a volume that is offline. Also obtain operator's console sheet showing related
messages, if any. There should be at least one DSNP-
prefixed message containing the '00D70030' code.
System action Messages preceding it from other subcomponents
The request to access the data set is terminated. (having other prefixes beginning with DSN) may
provide additional details about the problem.
Ensure that the proper volumes are online. See • Console output from the system on which the job
console message DSNP012I or DSNT500I. was run, and a listing of the SYSLOG data set for the
Obtain the following logs to find the failing data set
name: • Listing of the results produced by the SQL
statements.
• The operator's console log that contains
either the related DSNP012I message with
CTLGRC=00000008 CTLGRSN=xxxx0532, or,
message DSNT500I with REASON 00D70029.
• The job log that contains the 00D70029 code. sent to SYSPRINT.
Use ISPF, ISMF, or other facility to locate the volumes • Definitions of views and tables involved in the error.
and device numbers where the data set resides. Vary
.
the volume, or volumes, back online.
00D70040
00D70030

An attempt to rename an existing data set failed, Notify the system programmer.
because a name does not conform to the naming
convention. Problem determination
This problem probably arises during execution of the
System action
REORG utility with SHRLEVEL REFERENCE or CHANGE.
Error indication is returned to the user. See message DSNP027I.
Notify the database administrator if appropriate. was run, and a listing of the SYSLOG data set for the
User response • IDCAMS LISTCAT output for the ICF (VSAM) catalog
Problem determination operation occurred.
This problem probably arises during execution of the • Listing of the results produced by the SQL
REORG utility with SHRLEVEL REFERENCE or CHANGE. statements.
See message DSNP027I or DSNP026I.
Collect the following diagnostic items: • SYSPRINT output, including JCL, for the application
• Console output from the system on which the job program or batch job, and system messages that
was run, and a listing of the SYSLOG data set for the were issued. Make sure that MSGLEVEL=(1,1) on the
period of time that spans the failure. JOB statement so that all diagnostic information is
sent to SYSPRINT.
that contains the Db2 subsystem catalog that • Definitions of views and tables involved in the error.
defined the failing index or table. 00D70042
operation occurred.
Explanation
statements. An attempt to rename an existing data set failed,
because the old and new names are not compatible.
• Listing of Db2 catalog tables. This problem might arise in one or both of the
• SYSPRINT output, including JCL, for the application following situations:
1. One data set name is a Db2 page set data set name
and another data set name is a non-Db2 page set
data set name.
sent to SYSPRINT.
2. Both are Db2 page set data set names, but there
is a mismatch in the catalog alias names, the
00D70041 database names, or the table space/index space
names.
Explanation
System action
An attempt to rename an existing data set failed.
Error indication is returned to the user.
System action
Error indication is returned to the user.

Notify the system programmer or database Notify the system programmer or database
administrator. administrator.

This problem probably arises during execution of the For additional information, see the description of
REORG utility with SHRLEVEL REFERENCE or CHANGE. message DSNP014I.
See message DSNP027I.
• Console output from the system on which the job Obtain the console sheet showing the associated
was run, and a listing of the SYSLOG data set for the DSNP014I message. If you suspect an error in Db2,
period of time that spans the failure. you might need to report the problem. For information
• IDCAMS LISTCAT output for the ICF (VSAM) catalog about identifying and reporting the problem, see
that contains the Db2 subsystem catalog that Collecting diagnostic data (Collecting data).
defined the failing index or table. 00D70045
statements. Explanation
An unexpected error was received in acquiring the
• SYSPRINT output, including JCL, for the application SY_PITR lock by data space manager during DEFINE
program or batch job, and system messages that or EXTEND processing of the data set.
sent to SYSPRINT.
System action
• Definitions of views and tables involved in the error. The data set DEFINE or EXTEND did not complete.
00D70043
Operator response
Explanation Notify the system programmer or database
administrator.
During the define cluster for a undefined data set, Db2
detected that the specified data set requested to be
defined already exists.
System action message DSNP015I.

User response Obtain the console sheet showing the associated
DSNP015I message. If you suspect an error in Db2,
Delete the existing cluster and rerun the job. you might need to report the problem. For information
00D70044 about identifying and reporting the problem, see
An unexpected error was received in acquiring the

SY_PITR lock by data space manager during DEFINE Explanation
or EXTEND processing of the data set. This is an internal error. An attempt to extend a data
set failed because an error is detected. The high used
System action page number of the pageset recorded in Db2 does
not match the high used control interval from the
The data set DEFINE or EXTEND did not complete. integrated catalog facility (ICF) catalog.

System action must be converted to SHAREOPTIONS(1,3) before the
database can be altered to ROSHARE OWNER.
The data sharing extend did not complete.
System action
Operator response
An SQLCODE -731 is returned to the user and the
Notify the system programmer or database ALTER DATABASE statement is not performed.
administrator.
User response
Use AMS ALTER SHAREOPTIONS to alter all user-
For additional information, see the description of defined data sets that are within this database
message DSNP007I. to SHAREOPTIONS(1,3), and resubmit the ALTER
DATABASE statement.
Obtain the console sheet showing the associated
DSNP007I message. If you suspect an error in Db2, Explanation
about identifying and reporting the problem, see A requested resource is not available. Either the
Collecting diagnostic data (Collecting data). data space manager (DSM) or some subcomponent
that it invoked discovered that some resource is not
00D70051 available. The name and type of the resource and the
reason it is unavailable are placed in the CT control
Explanation block by the subcomponent that made the discovery.
This information is made available to the user in the
One of the following is issued on a ROSHARE OWNER SQLCA and/or messages. The reason code in the CT/
database: SQLCA contains the identifier of the subcomponent
• A CREATE TABLESPACE statement that discovered the problem.
• A CREATE INDEX statement, or Almost any DSNP module can issue this reason code.
• The REORG utility with SHRLEVEL REFERENCE or
SHRLEVEL CHANGE using user-managed data sets System action
However, the data sets are not defined with VSAM Abort the current request.
SHAREOPTIONS(1,3).
Operator response
System action
An SQLCODE -731 is returned to the user (for CREATE administrator.
TABLESPACE or INDEX) The CREATE TABLESPACE or
INDEX statement or the REORG utility is not executed.
User response Notify the database administrator if appropriate.
Otherwise, determine what resource was unavailable
Use AMS ALTER SHAREOPTIONS to alter the data (from SQLCA information) and, if it is something you
set to SHAREOPTIONS(1,3) and resubmit the CREATE can control, make it available. If you suspect an
TABLESPACE or INDEX statement or the REORG utility. error in Db2, you might need to report the problem.
00D70052
data).
Explanation
An ALTER DATABASE statement is issued to convert Problem determination
a database to ROSHARE OWNER. But, within this
See the Problem Determination section in the
database, at least one user defined data set is not
description of the code that appears in the SQLCA or
defined with VSAM SHAREOPTIONS(1,3). All user-
CTRURESN field of the CT and/or in the description
defined data sets that are within this database
of any associated console messages. Obtain details of
the request that resulted in this code, and contents

of the SQLCA. Also obtain operator's console sheet Operator response
showing related messages, if any.
• Console output from the system on which the job System programmer response
period of time that spans the failure. If you suspect an error in Db2, you might need to
• Dynamic dump, taken to SYS1.DUMPxx data set, by and reporting the problem, see Collecting diagnostic
Db2 (04E and 04F abends). data (Collecting data).
statements. Problem determination
program or batch job, and system messages that Obtain the console sheet, dump, details of the request
were issued. Make sure that MSGLEVEL=(1,1) on the that led to this code, and contents of the SQLCA.
JOB statement so that all diagnostic information is Collect the following diagnostic items:
sent to SYSPRINT.
• Definitions of views and tables involved in the error. was run, and a listing of the SYSLOG data set for the
A severe error has occurred. For example, an invalid statements.
data space manager (DSM) function is invoked.
Almost any data space manager (DSM) function can program or batch job, and system messages that
issue this reason code. were issued. Make sure that MSGLEVEL=(1,1) on the
System action sent to SYSPRINT.
Abort the request. • Definitions of views and tables involved in the error.

Reason code identifiers that begin with 00D9 communicate normal and error situations with the recovery
manager.
Ensure the coupling facility for the SCA is available,
Explanation and restart Db2.
A recovery manager module received control from
its FRR for retry and found an invalid retry point Problem determination
identifier. The name of the module in which the failure
occurred appears in the SYS1.LOGREC entry showing If you suspect an error in Db2, you might need to
this reason code in register 15. report the problem. For information about identifying
System action
Standard Db2 diagnostic information is provided.
The error is recorded in SYS1.LOGREC, an SVC • Console output from the system on which the job
dump is scheduled, and Db2 subsystem termination was run, and a listing of the SYSLOG data set for the
is requested. The subsystem termination reason period of time that spans the failure.
code reflects the function for which retry was • Dynamic dump, taken to SYS1.DUMPxx data set, by
unsuccessfully attempted. Db2 (04E and 04F abends).
Operator response executing IFCEREP1.
Print SYS1.LOGREC, and restart Db2. 00D90004

This is a secondary subsystem error. Obtain a copy An error occurred while Db2 was attempting to create
of SYS1.LOGREC and the SVC dump for this failure a service task.
and for the original failure that resulted in the retry
attempt. System action
Standard Db2 diagnostic information is recorded in
SYS1.LOGREC, and an SVC dump is requested before
Examine the SYS1.LOGREC information and the dumps Db2 subsystem termination is initiated.
from both the original failure and this second failure
to determine if the recovery parameter area was Problem determination
damaged or if retry incorrectly restored registers for
the mainline module. If you suspect an error in Db2, you might need to
A failure occurred while Db2 was attempting to open • Console output from the system on which the job
an object in the shared communications area (SCA). was run, and a listing of the SYSLOG data set for the
Standard Db2 diagnostic information is recorded in Db2 (04E and 04F abends).
SYS1.LOGREC, and an SVC dump is requested before • Listing of SYS1.LOGREC data set, obtained by
Db2 subsystem termination is initiated. executing IFCEREP1.
00D90010

During the process of re-enabling data sharing, all If you suspect an error in Db2, you might need to
members, other than the surviving member, are forced report the problem. For information about identifying
to cold start. In the process of setting up the cold start and reporting the problem, see Collecting diagnostic
for this member, an active conditional restart control data (Collecting data).
record was discovered in the BSDS. This record could
not have been in the BSDS when data sharing was
disabled, and this Db2 should have been inactive since • Console output from the system on which the job
data sharing was disabled; therefore, it is unclear what was run, and a listing of the SYSLOG data set for the
the conditional restart control record is requesting. period of time that spans the failure.
Standard Db2 diagnostic information is recorded in • Listing of SYS1.LOGREC data set, obtained by
SYS1.LOGREC, and an SVC dump is requested before executing IFCEREP1.
Db2 subsystem termination is initiated. 00D90012

Use the change log inventory (DSNJU003) utility to An error occurred while Db2 was attempting to create
cancel the active conditional restart control record in a service task.
this member's BSDS.
System action
If you suspect an error in Db2, you might need to SYS1.LOGREC, and an SVC dump is requested before
report the problem. For information about identifying Db2 subsystem termination is initiated.
• Listing of SYS1.LOGREC data set, obtained by • Console output from the system on which the job
executing IFCEREP1. was run, and a listing of the SYSLOG data set for the
in use) obtained by using the Db2 print log map • Dynamic dump, taken to SYS1.DUMPxx data set, by
(DSNJU004) utility. Db2 (04E and 04F abends).
00D90011 executing IFCEREP1.
00D90013
Explanation
Db2 determined that the version of the shared Explanation
communications area (SCA) recorded within the SCA
did not match the version of the SCA returned from The restart parameters for TRKRSITE are invalid.
MVS. If TRKRSITE is YES on DSNZPARM and this
Db2 subsystem has not successfully restarted in
this 'Tracker Recovery cycle', Db2 requires special
System action
conditions before it can restart.
SYS1.LOGREC, and an SVC dump is requested before System action
Db2 subsystem termination is initiated.

Collect the SYS1.LOGREC and SVC dump, and contact An invalid function code was passed to a Db2 service
the system programmer. task.

Ensure that the Conditional Restart Control Record Standard Db2 diagnostic information is recorded in
is correct, then restart Db2. You can run the Print SYS1.LOGREC, and an SVC dump is requested before
Log Map Utility (DSNJU004) to examine the current Db2 subsystem termination is initiated.
Conditional Restart record. The following conditions
are correct: Problem determination
• BACKOUT = NO
• FORWARD = NO report the problem. For information about identifying
• Either an ENDRBA value for non-data sharing or an and reporting the problem, see Collecting diagnostic
ENDLRSN value for data sharing. In data sharing, the data (Collecting data).
ENDLRSN value must be the same for all members Collect the following diagnostic items:
restarting in this 'Tracker Recovery cycle'.
To avoid a cold start or log skipping in a tracker site, was run, and a listing of the SYSLOG data set for the
ensure that STARTRBA has no specified value. You can period of time that spans the failure.
create or modify the Conditional Restart parameters
with the Change Log Inventory Utility (DSNJU003). • Dynamic dump, taken to SYS1.DUMPxx data set, by
Related reference
DSNJU003 (change log inventory) (Db2 Utilities) executing IFCEREP1.
00D90020
00D90014
Explanation
Explanation During the process of re-enabling data sharing, the
The System Level Recovery restart was invalid. All surviving member of the previous data sharing disable
members of the data sharing group must truncate their must be the first member started. An attempt was
logs with the same LRSN value that was specified in made to start a member other than the surviving
the SYSPITR conditional restart parameter. member during the process of re-enabling data
sharing.
System action
System action
Operator response Db2 subsystem termination is initiated.
Collect the SYS1.LOGREC and SVC dump, and contact
the system programmer. Operator response
To initiate the data sharing re-enable process, start the
System programmer response surviving member of the previous data sharing disable
Ensure that the conditional restart control record is first.
correct, and then restart Db2. You can run the Print
Log Map utility (DSNJU004) to examine the current Problem determination
conditional restart record.
00D9001F report the problem. For information about identifying

executing IFCEREP1.
00D90021 Db2 (04E and 04F abends).
After data sharing is disabled, only the surviving 00D90050
member of the group can be started. An attempt
was made to start a member other than the surviving
Explanation
member.
Data sharing re-enable is canceled.
System action This Db2 member was canceled while waiting for other
members of the data sharing group to complete their
re-enable processing.
System action
Problem determination Standard Db2 diagnostic information is recorded in
Collect the following diagnostic items: To re-enable data sharing, start the surviving member
again.
• Dynamic dump, taken to SYS1.DUMPxx data set, by If you suspect an error in Db2, you might need to
Db2 (04E and 04F abends). report the problem. For information about identifying
00D90022 Collect the following diagnostic items:

After reading information from the BSDS of a peer
member in its data sharing group, this Db2 was not • Dynamic dump, taken to SYS1.DUMPxx data set, by
able to close the peer's BSDS. Db2 (04E and 04F abends).
executing IFCEREP1.
System action
00D900E0
Db2 subsystem termination is initiated. Explanation
A Db2 functional recovery routine invoked Db2
Problem determination subsystem termination because an unrecoverable
error was detected.

SYS1.LOGREC, and an SVC dump is requested before Collect the following diagnostic items:
Db2 subsystem termination is initiated. • Console output from the system on which the job
Collect the following diagnostic items: 00D900EC
During the process of re-enabling data sharing, a
• Dynamic dump, taken to SYS1.DUMPxx data set, by member other than the surviving member was not able
Db2 (04E and 04F abends). to complete it's portion of the re-enabling process.
00D900E1 Standard Db2 diagnostic information is recorded in
Explanation Db2 subsystem termination is initiated.
The operator replied 'NO' to message DSNR020I. See

message DSNR020I for more information. Problem determination
Db2 terminates. data (Collecting data).
Problem determination: Collect the following diagnostic items:
00D900EB • Console output from the system on which the job
Explanation period of time that spans the failure.
This abend reason code appears at a member, • Dynamic dump, taken to SYS1.DUMPxx data set, by
other than the surviving member, when the surviving Db2 (04E and 04F abends).
member is not able to complete the process of re- • Listing of SYS1.LOGREC data set, obtained by
enabling data sharing. This member cannot continue executing IFCEREP1.
because data sharing was not re-enabled successfully.
00D900F0
System action
Explanation
SYS1.LOGREC, and an SVC dump is requested before Db2 received an error while attempting to access
Db2 subsystem termination is initiated. shared communications area (SCA) information from
the coupling facility.
System action
Determine why the surviving member was not able to
complete the data sharing re-enable. Standard Db2 diagnostic information is recorded
in SYS1.LOGREC, and an SVC memory dump is
If you suspect an error in Db2, you might need to requested. Depending on the nature of the problem,
report the problem. For information about identifying Db2 subsystem termination might be initiated.

Collect the following documentation and contact IBM
Correct the problem with the coupling facility, and
Support:
restart Db2.
• SVC memory dump
• Syslog Problem determination
Additional documentation might be required, If you suspect an error in Db2, you might need to
depending on the exact nature of the error. report the problem. For information about identifying
00D900F1
Db2 received an error while attempting to read shared • Console output from the system on which the job
communications area (SCA) information from the was run, and a listing of the SYSLOG data set for the
coupling facility. period of time that spans the failure.
System action
Standard Db2 diagnostic information is recorded in executing IFCEREP1.
Db2 subsystem termination is initiated. 00D900F3

Correct the problem with the coupling facility, and Db2 received an error while attempting to read the
restart Db2. BSDS.

If you suspect an error in Db2, you might need to Standard Db2 diagnostic information is recorded in
report the problem. For information about identifying SYS1.LOGREC, and an SVC dump is requested before
and reporting the problem, see Collecting diagnostic Db2 subsystem termination is initiated.
Collect the following diagnostic items: System programmer response
• Console output from the system on which the job Correct the problem with the BSDS, and restart Db2.
00D900F2 Collect the following diagnostic items:
Explanation in use) obtained by using the Db2 print log map
Db2 received an error while attempting to write (DSNJU004) utility.
shared communications area (SCA) information to the • Console output from the system on which the job
coupling facility. was run, and a listing of the SYSLOG data set for the
SYS1.LOGREC, and an SVC dump is requested before • Listing of SYS1.LOGREC data set, obtained by
Db2 subsystem termination is initiated. executing IFCEREP1.

00D900F4 If you suspect an error in Db2, you might need to
Explanation
Db2 received an error while attempting to write to the
BSDS.
System action
(DSNJU004) utility.
Standard Db2 diagnostic information is recorded in • Console output from the system on which the job
SYS1.LOGREC, and an SVC dump is requested before was run, and a listing of the SYSLOG data set for the
Db2 subsystem termination is initiated. period of time that spans the failure.
Correct the problem with the BSDS, and restart Db2. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Problem determination 00D900F7
data (Collecting data). Db2 received an error while attempting to acquire a
lock.
• Contents of the BSDS (both copies if dual BSDS System action
(DSNJU004) utility. Standard Db2 diagnostic information is recorded in
SYS1.LOGREC, and an SVC dump might be requested.
• Console output from the system on which the job Depending on the error, Db2 might initiate subsystem
was run, and a listing of the SYSLOG data set for the termination.
• Dynamic dump, taken to SYS1.DUMPxx data set, by Problem determination
Register 4 points to the resource that Db2 was
attempting to lock.
executing IFCEREP1.
00D900F5
Db2 received an error while attempting to read the Collect the following diagnostic items:
BSDS of another member in the data sharing group.
Standard Db2 diagnostic information is recorded in • Dynamic dump, taken to SYS1.DUMPxx data set, by
SYS1.LOGREC, and an SVC dump is requested before Db2 (04E and 04F abends).
Db2 subsystem termination is initiated. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
System programmer response 00D900F8
Correct the problem with the BSDS, and restart Db2.
Explanation
Problem determination Db2 received an error while attempting to release
Register 4 contains the member ID of the member a lock used to serialize portions of restart or group
whose BSDS was being read. restart.

Standard Db2 diagnostic information is recorded in The starting Db2 subsystem is an incompatible release
SYS1.LOGREC, and an SVC dump is requested before of Db2 or the code does not have the proper level of
Db2 subsystem termination is initiated. SPE applied.

If you suspect an error in Db2, you might need to The Db2 subsystem terminates. An SVC dump might
report the problem. For information about identifying be requested.
Verify that:
• The correct load libraries are being used to start up
the Db2 subsystem.
• The correct level of SPE has been applied.
Db2 (04E and 04F abends). Related tasks
• Listing of SYS1.LOGREC data set, obtained by Migration step 1: Actions to complete before
executing IFCEREP1. migration (Db2 Installation and Migration)
00D900F9 00D90100
Db2 received an error while attempting to notify other A Db2 functional recovery routine invoked Db2
members in the data sharing group of a restart or subsystem termination because an unrecoverable
group restart event. error was detected.

Standard Db2 diagnostic information is recorded in Standard Db2 diagnostic information is recorded in
SYS1.LOGREC, and an SVC dump is requested before SYS1.LOGREC, and an SVC dump is requested before
Db2 subsystem termination is initiated. Db2 subsystem termination is initiated.

00D900FA 00D90110
Explanation

System action transaction. This is violation of the protocol and is not
allowed.
Db2 subsystem termination is initiated. System action
The Begin-UR request is failed and a SVC dump may
Problem determination be scheduled. The thread requesting the Begin-UR
might be abended. No resources are released because
If you suspect an error in Db2, you might need to a UR is not created for the thread and no resources
report the problem. For information about identifying may be held.
This is a protocol error. The application controlling the
• Console output from the system on which the job global transaction thread may not request that a new
was run, and a listing of the SYSLOG data set for the unit of recovery be created after the global transaction
period of time that spans the failure. has reached a decision point, either commit or abort.
Db2 (04E and 04F abends). Problem determination
Obtain the UR-control log records (type '0020'x) for all
executing IFCEREP1.
the threads in the global transaction to determine the
00D90111 sequence of events that led to the protocol violation.
Correct the application.
Explanation
System action An unexpected return code was received from RRS
when setting the type of interest in a Unit of Recovery
(UR).
System action
Problem determination The application is abended.
Collect the SYS1.LOGREC and SVCDUMP, and notify
This is probably either an error in Db2 or in RRS. If
you suspect an error in Db2, you might need to report
• Dynamic dump, taken to SYS1.DUMPxx data set, by the problem. For information about identifying and
Db2 (04E and 04F abends). reporting the problem, see Collecting diagnostic data
• Listing of SYS1.LOGREC data set, obtained by (Collecting data). If RRS has terminated, restart RRS.
executing IFCEREP1.
Examine the SVCDUMP to determine the cause of the
Explanation RRS failure. Register nine contains the return code
from the RRS ATRSIT request.
A thread that was participating in a global transaction
attempted to issue a Begin-UR after a decision point 00D92001
(commit or abort) was already reached for the global

The checkpoint/restart serial controller (DSNRCRSC) See the original error.
FRR invoked Db2 subsystem termination, because an
00D92004
unrecoverable error was detected while processing a
request.
Explanation
This is a Db2 subsystem termination reason code.
For further information, see IRLM abend codes (IRLM The shutdown checkpoint controller (DSNRCSHT) FRR
messages and codes). invoked Db2 subsystem termination, because an
System action shutdown checkpoint request.
Subsystem termination is initiated. Standard Db2 This is a Db2 subsystem termination reason code.
diagnostic information is recorded in SYS1.LOGREC, For further information, see IRLM abend codes (IRLM
and an SVC dump is requested for the associated messages and codes).
abend.
System action
Operator response Standard Db2 diagnostic information is recorded in
Print SYS1.LOGREC, and restart Db2. SYS1.LOGREC, and an SVC dump is requested for the
original error before Db2 subsystem termination is
initiated.
Obtain a copy of the SYS1.LOGREC and the SVC Operator response
dump for the original error, and follow the instructions
associated with it. Print SYS1.LOGREC, and restart Db2.

See the original error. Obtain a copy of SYS1.LOGREC and the SVC dump for
the original error.
00D92003
Explanation
See the original error.
The restart request servicer (DSNRRRQS) FRR
invoked Db2 subsystem termination, because an 00D92011
restart request. Explanation
This is a Db2 subsystem termination reason code. An invalid URE was found during checkpoint
For further information, see IRLM abend codes (IRLM processing. An overlay of the URE may have occurred.
messages and codes).
System action
System action
The checkpoint process will ABEND to prevent a
Standard Db2 diagnostic information is recorded in damaged URE from being written out to the log,
SYS1.LOGREC, and an SVC dump is requested for the and the subsystem will be terminated. This is to
original error before Db2 subsystem termination is prevent the loss or incorrect processing of a Db2 unit
initiated. of recovery (UR). Db2 Restart will use the previous
checkpoint and apply all the Db2 log records up to the
Operator response point of failure. Standard Db2 diagnostic information
is recorded in SYS1.LOGREC, and an SVC dump is
Print SYS1.LOGREC, and restart Db2. scheduled.

Obtain a copy of SYS1.LOGREC and the SVC dump for Collect the SYS1.LOGREC and SVCDUMP, and notify
the original error. the system programmer. Restart Db2.

executing IFCEREP1.
data set, as result of an operator-initiated dump Problem determination
Examine the SVCDUMP and the Db2 Trace Table in the
dump to determine the cause of the RURE overlay.
executing IFCEREP1.
An invalid GXID was found during checkpoint
processing. An overlay of the GXID might have
Problem determination occurred.
Examine the SVCDUMP and the Db2 Trace Table in the
dump to determine the cause of the URE overlay. System action
00D92012 The checkpoint process will abnormally terminate to
prevent a damaged GXID from being written out to
Explanation the log, and the subsystem will be terminated. This
is to prevent the loss of or incorrect processing of a
An invalid RURE was found during checkpoint Db2 unit of recovery. Db2 restart will use the previous
processing. An overlay of the RURE may have checkpoint and apply all the Db2 log records up to the
occurred. point of failure. Standard Db2 diagnostic information
is recorded in SYS1.LOGREC, and an SVC dump is
System action scheduled.
The checkpoint process will abend to prevent a

damaged RURE from being written out to the log,
Operator response
and the subsystem will be terminated. This is to Collect the SYS1.LOGREC and SVCDUMP, and notify
prevent the loss or incorrect processing of a Db2 the system programmer. Restart Db2.
unit of recovery. Db2 Restart will use the previous
checkpoint and apply all the Db2 log records up to the
point of failure. Standard Db2 diagnostic information
is recorded in SYS1.LOGREC, and an SVC dump is Collect the following diagnostic items:
scheduled.
Collect the SYS1.LOGREC and SVCDUMP, and notify • SVC dump (or system dump), taken to SYS1.DUMPxx
the system programmer. Restart Db2. data set, as result of an operator-initiated dump
executing IFCEREP1.

Examine the SVCDUMP and the Db2 Trace Table in the and reporting the problem, see Collecting diagnostic
dump to determine the cause of the GXID overlay. data (Collecting data).
DSNJU003 (change log inventory) (Db2 Utilities)
Explanation DSNJU004 (print log map) (Db2 Utilities)
An invalid URE was read from the log during the
00D92022
current status rebuild phase of restart. Restart cannot
process the damaged URE.
Explanation
System action An invalid RURE was read from the log during the
current status rebuild phase of restart. Restart cannot
The restart processing abends, which terminates the
process the damaged RURE.
subsystem. This is to prevent the loss or incorrect
processing of a Db2 unit of recovery.
System action
SYS1.LOGREC, and an SVC dump is scheduled. The The restart processing will abend, which will terminate
first 4 digits of the RBA of the invalid log record is the subsystem. This is to prevent the loss or incorrect
contained in register 3 and the last 8 digits in register processing of a Db2 unit of recovery.
4.
SYS1.LOGREC, and an SVC dump is scheduled. The
Operator response first 4 digits of the RBA of the invalid log record is
contained in register 3 and the last 8 digits in register
Do not attempt to restart Db2 until the error is
4.
resolved. Notify the system programmer and collect
the following diagnostic items listed in
Operator response
was run, and a listing of the SYSLOG data set for the Do not attempt to restart Db2 until the error is
period of time that spans the failure. resolved. Notify the system programmer and collect
• SVC dump (or system dump), taken to SYS1.DUMPxx the following diagnostic items listed in
executing IFCEREP1. • SVC dump (or system dump), taken to SYS1.DUMPxx
System programmer response command or SLIP trap exit.
Print the BSDS using the print log map (DSNJU004)
executing IFCEREP1.
utility. Find the checkpoint queue in the output listing
from DSNJU004.
Next, run the change log inventory (DSNJU003)
utility to create a conditional restart record with the Print the BSDS using the print log map (DSNJU004)
CHKPTRBA option specifying the Begin checkpoint utility. Find the checkpoint queue in the output listing
RBA found in the second entry of the checkpoint from DSNJU004.
queue. Restart Db2 using the conditional restart
Next, run the change log inventory (DSNJU003)
record found. If the same failure occurs, repeat the
utility to create a conditional restart record with the
conditional process using the next begin checkpoint
CHKPTRBA option specifying the begin checkpoint
RBA in the checkpoint queue.
RBA found in the second entry of the checkpoint
Repeat this process, going down the checkpoint queue queue. Restart Db2 using the conditional restart
until Db2 restarts. This will be prior to the time when record found. If the same failure occurs, repeat the
the invalid URE was written to the log. The restart conditional process using the next begin checkpoint
process is then able to apply all the log records to the RBA in the checkpoint queue.
end of the log.

Repeat this process, going down the checkpoint queue CHKPTRBA option specifying the begin checkpoint
until Db2 restarts. This will be prior to the time when RBA found in the second entry of the checkpoint
the invalid RURE was written to the log. The restart queue. Restart Db2 using the conditional restart
process is then able to apply all the log records to the record found. If the same failure occurs, repeat the
end of the log. conditional process using the next begin checkpoint
report the problem. For information about identifying Repeat this process, going down the checkpoint queue
and reporting the problem, see Collecting diagnostic until Db2 restarts. This will be prior to the time when
data (Collecting data). the invalid record was written to the log. The restart
process then applies all the log records to the end of
Related reference
the log.
DSNJU004 (print log map) (Db2 Utilities) If you suspect an error in Db2, you might need to
An invalid record was read from the log during the
current status rebuild phase of restart. Restart cannot DSNJU004 (print log map) (Db2 Utilities)
process the damaged log record.
00D92024
System action
Explanation
The restart processing will abnormally terminate,
During restart, the state of a logged unit of recovery
which will terminate the subsystem. This is to prevent
and the state of the global transaction which the unit
the loss or incorrect processing of a Db2 unit of
of recovery is part of are incompatible.
recovery.
System action
SYS1.LOGREC, and an SVC dump is scheduled. The
first 4 digits of the RBA of the invalid log record is The restart processing abnormally terminates, which
contained in register 3 and the last 8 digits in register terminates the subsystem. This is to prevent the loss
4. or incorrect processing of a Db2 unit of recovery.
Operator response SYS1.LOGREC, and an SVC dump is scheduled.
resolved. Notify the system programmer and collect Operator response
the following diagnostic items listed in
• Console output from the system on which the job resolved. Notify the system programmer and collect
was run, and a listing of the SYSLOG data set for the the following diagnostic items:
• SVC dump (or system dump), taken to SYS1.DUMPxx was run, and a listing of the SYSLOG data set for the
data set, as result of an operator-initiated dump period of time that spans the failure.
• Listing of SYS1.LOGREC data set, obtained by data set, as result of an operator-initiated dump
Print the BSDS using the Print Log Map (DSNJU004)
utility. Find the checkpoint queue in the output listing System programmer response
from DSNJU004.
Print the BSDS using the Print Log Map (DSNJU004)
Next, run the Change Log Inventory (DSNJU003) utility. Find the checkpoint queue in the output listing
utility to create a conditional restart record with the from DSNJU004.

Next, run the Change Log Inventory (DSNJU003) termination of this Db2 subsystem and that the
utility to create a conditional restart record with the subsystem was last started at a different release level.
CHKPTRBA option specifying the begin checkpoint
During migration to a new release or fallback to an
RBA found in the second entry of the checkpoint
older release, all activity must be quiesced and there
queue. Restart Db2 using the conditional restart
should be no active units of recovery. Db2 restart will
record found. If the same failure occurs, repeat the
fail until the situation is resolved.
conditional process using the next begin checkpoint
System action
Repeat this process, going down the checkpoint queue
until Db2 restarts. This will be prior to the time when The restart terminates abnormally, which terminates
the invalid record was written to the log. The restart the subsystem. This action is to prevent the loss or
process then applies all the log records to the end of incorrect processing of a Db2 unit of recovery. An
the log. SVC dump is scheduled and an entry is created in
SYS1.LOGREC.
data (Collecting data). Do not attempt to restart Db2 until the error is
resolved. Notify the system programmer and collect
Problem determination the required items for problem determination.
The state of the logged unit of recovery is reported
in register 1 and the state of the global transaction is System programmer response
provided in register 2. The meanings of these values Because all work must be quiesced before either
are shown below. migration or fallback of a Db2 subsystem, the
Unit of recovery state (in register 1): recommended action is to restart the Db2 subsystem
at the release level that created the outstanding unit
1
or units of recovery and let the units of recovery end
inflight
normally.
2
ensure abort You might need to use the RECOVER INDOUBT
command to resolve indoubt threads.
3
commit indoubt After all units of recovery have completed processing,
use the STOP DB2 command with MODE(QUIESCE)
4
to stop Db2. Then restart Db2 at the desired release
ensure commit
level. Using a different release level may require
Global Transaction State (in register 2): additional migration or fallback actions.
1 If it is not possible to restart Db2 at the release level
inflight that created the outstanding units of recovery, then a
2 cold start is required.
ensure abort 1. Print the BSDS using the DSNJU004 (print log map)
3 utility.
commit indoubt 2. Find the highest written RBA using the output from
4 DSNJU004.
ensure commit 3. Use the DSNJU003 (change log inventory) utility
Related reference to create a conditional restart record, specifying
the same value for STARTRBA and ENDRBA. The
RBA value must be an even multiple of 4096
DSNJU004 (print log map) (Db2 Utilities) (a hexadecimal value ending in 000) and should
be rounded up from the highest written RBA as
00D92025
indicated by the DSNJU004 output.
Explanation Additional actions might be necessary to recover from

possible data inconsistencies.
During restart, it was determined that at least one
unit of recovery (UR) was still active at the previous

Another option is to restore the Db2 logs and data to a Problem determination
prior consistent point in time.

Explanation
was run, and a listing of the SYSLOG data set for the The Db2 subsystem is terminated because an
period of time that spans the failure. unrecoverable error was detected during must-
complete processing for phase 2 of a commit-UR
request for an agent that is a participant in a global
transaction.
• Listing of SYS1.LOGREC data set, obtained by This is a Db2 subsystem termination reason code.
executing IFCEREP1. For further information, see IRLM abend codes (IRLM
Related tasks
Recovering from different Db2 for z/OS System action
problems (Db2 Administration Guide)
Related reference Standard Db2 diagnostic information is recorded in
SYS1.LOGREC, and an SVC dump is requested for the
DSNJU004 (print log map) (Db2 Utilities) initiated.
Related information
About Db2 and related commands (Db2
Operator response
Commands)
Recovering from unresolvable BSDS or log data Print SYS1.LOGREC, and restart Db2. Notify the system
set problem during restart (Db2 Administration programmer.
Guide)
00D93001
This is probably either an error in Db2 or in the
commit of the global transaction. If you suspect an
Explanation error in Db2, you might need to report the problem.
The commit/abort FRR (DSNRCAFR) invoked Db2 For information about identifying and reporting the
subsystem termination, because an unrecoverable problem, see Collecting diagnostic data (Collecting
error was detected during must-complete processing data).
for phase 2 of a commit-UR request.
This is a Db2 subsystem termination reason code. Problem determination
For further information, see IRLM abend codes (IRLM Db2 records on the SYS1.LOGREC data set and
messages and codes). requests an SVC dump. The error indicates that there
may be a problem with Db2 or with the commit
System action coordinator of the global transaction.
Standard Db2 diagnostic information is recorded in Collect the following diagnostic items:
initiated.
Print SYS1.LOGREC, and restart Db2. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
System programmer response 00D9300F
Obtain a copy of SYS1.LOGREC and the SVC dump for
the original error.

The commit/cancel secondary FRR invoked Db2
subsystem termination. This occurs only if functional If the agent were in a must-complete state (in-
recovery itself fails while processing a failure during commit2 or in-abort), the Db2 subsystem is also
must-complete processing for phase 2 of a commit-UR terminated with reason code '00D93001'. When the
request. subsystem is next restarted, recoverable activity for
this agent (such as an ensure-abort or ensure-commit
This is a Db2 subsystem termination reason code. UR) is handled to complete the commit or abort
For further information, see IRLM abend codes (IRLM process.

System action
This is a Db2 subsystem error. Collect the materials
Standard Db2 diagnostic information is recorded in mentioned in the Problem Determination section of
SYS1.LOGREC, and an SVC dump is requested for the this message.
original error. Standard Db2 diagnostic information is
also recorded in SYS1.LOGREC for the secondary error
before Db2 subsystem termination is initiated. Problem determination
Examine the SYS1.LOGREC data and the Db2 trace
Operator response table in the dump to establish whether either commit-
UR was invoked incorrectly or the control structure
Print SYS1.LOGREC, and restart Db2. that reflects the state (ACEPROG, UREPROG) was
damaged.
Obtain a copy of SYS1.LOGREC for both the original
and the secondary error, and the SVC dump for the Explanation
original error.
A subcomponent of Db2 invoked commit when the
agent state was invalid for commit-UR invocation.
Problem determination Commit-UR was invoked for an agent that was only
See the original error. retrieving data. Either commit-UR or abort-UR was
already in process, or the ACE progress state field was
00D93011 damaged.

A subcomponent of Db2 invoked commit when the Abnormal termination of the agent results, including
agent state was invalid for commit-UR invocation. backing out (abort-UR) of its activity to the previous
Commit-UR was requested for an agent that was point of consistency. This releases all locks held by the
modifying data. Either commit-UR or abort-UR was agent for its resources.
already in process, or the recovery structure (URE) was
damaged. Standard Db2 diagnostic information is recorded
in SYS1.LOGREC, and an SVC dump is scheduled.
Additional information, identified in the SDWA variable
System action recording area by reason code '00D9CCCC', is added to
Abnormal termination of the agent results, including the SDWA variable recording area.
backing out (abort-UR) of its activity to the previous If you suspect an error in Db2, you might need to
point of consistency. This releases all locks held by the report the problem. For information about identifying
agent for its resources. and reporting the problem, see Collecting diagnostic
Standard Db2 diagnostic information is recorded data (Collecting data).
in SYS1.LOGREC, and an SVC dump is scheduled.
Additional information, identified in the SDWA variable System programmer response
recording area by reason code '00D9CCCC', is added to
the SDWA variable recording area (VRA). This is a Db2 subsystem error. Collect the materials
mentioned in the Problem Determination section of
If you suspect an error in Db2, you might need to this message.

Examine the SYS1.LOGREC data and the Db2 trace This reason code indicates that a Db2 allied agent
table in the dump to establish whether either commit- does not need to participate in the Phase 2 (Continue
UR was invoked incorrectly or the control structure Commit) call, because all required work has been
(ACEPROG) was damaged. accomplished during the Phase 1 (Prepare) call.
00D93013 This reason code is generated by Recovery Manager
when it is determined that a Db2 allied agent has
not updated any Db2 resource since its last commit
Explanation
processing occurred.
The request to commit an agent that was a participant
in a global transaction failed because a mismatch System action
between the state of the agent and the state of the
global transaction. State field was damaged. The "yes" vote is registered with the Commit
coordinator.
System action 00D94001
Abnormal termination of the agent occurs, including
backing out (abort-UR) its activity to the previous point Explanation
of consistency. This releases all resource locks held by
The commit/abort FRR (DSNRCAFR) invoked Db2
the agent.
subsystem termination, because an unrecoverable
Standard Db2 diagnostic information is recorded in error was detected during must-complete processing
SYS1.LOGREC, and an SVC dump is scheduled. for an abort-UR request.
Operator response
Notify the system programmer. System action
System programmer response SYS1.LOGREC, and an SVC dump is requested for the
This is probably either an error in Db2 or in the
initiated.
For information about identifying and reporting the Operator response
Print SYS1.LOGREC, and restart Db2.
data).

Obtain a copy of SYS1.LOGREC and the SVC dump for
Db2 records on the SYS1.LOGREC data set and
the original error.
requests an SVC dump. The error indicates that there
coordinator of the global transaction. Problem determination
Collect the following diagnostic items: See the reason code for the original error.
Explanation
• Dynamic dump, taken to SYS1.DUMPxx data set, by An unrecoverable error was detected during must-
Db2 (04E and 04F abends). complete processing for an abort-UR request for an
• Listing of SYS1.LOGREC data set, obtained by agent that is a participant in a global transaction. A
executing IFCEREP1. Db2 subsystem termination might occur.
00D93100 This is a Db2 subsystem termination reason code.

Standard Db2 diagnostic information is recorded in Obtain a copy of the SYS1.LOGREC for both the original
SYS1.LOGREC, and an SVC dump is requested. and the secondary error, and the SVC dump for the
original error.
Operator response
Print SYS1.LOGREC, and restart Db2. Notify the system
programmer. See the original error.
00D94011
This is probably either an error in Db2 or in the Explanation
error in Db2, you might need to report the problem. A subcomponent of Db2 invoked abort at a point when
For information about identifying and reporting the the agent state is invalid for invoking the function that
problem, see Collecting diagnostic data (Collecting aborts units of recovery. Either abort-UR or commit-UR
phase 2 was already in process, or the agent structure
data).
was damaged.
System action
Db2 records on the SYS1.LOGREC data set and
Abnormal termination of the agent results and,
requests an SVC dump. The error indicates that there
because the agent is in a must-complete state,
the Db2 subsystem is terminated with reason code
coordinator of the global transaction.
'00D94001'. When the Db2 subsystem is restarted,
Collect the following diagnostic items: recoverable activity for this agent is handled to
complete the commit or abort process.
was run, and a listing of the SYSLOG data set for the Standard Db2 diagnostic information is recorded
period of time that spans the failure. in SYS1.LOGREC, and an SVC dump is scheduled.
• Dynamic dump, taken to SYS1.DUMPxx data set, by Additional information, identified in the SDWA variable
Db2 (04E and 04F abends). recording area by reason code '00D9AAAA7', is added
to the SDWA variable recording area. If you suspect an
, error in Db2, you might need to report the problem.
00D9400F For information about identifying and reporting the
data).
Explanation
The commit/abort FRR invoked Db2 subsystem System programmer response
termination. This occurs only if functional recovery
itself fails while processing a failure during must- This is a Db2 subsystem error. Collect the materials
complete processing for an abort-UR request. mentioned in the Problem Determination section of
this message.
For further information, see IRLM abend codes (IRLM
Examine the SYS1.LOGREC data and the Db2 trace
System action table in the dump to establish whether commit-
UR was invoked incorrectly or the control structure
Standard Db2 diagnostic information is recorded in (ACEPROG, UREPROG) was damaged.
original error. Standard Db2 diagnostic information is 00D94012
also recorded in SYS1.LOGREC for the secondary error
before Db2 subsystem termination is initiated. Explanation
During rollback, the end of the log was read before
Operator response all the expected log ranges were processed. The
Print SYS1.LOGREC, and restart Db2.

abend is accompanied by a Db2 abnormal subsystem Explanation
termination with reason code 00D94001.
A savepoint request encountered an invalid request
block. This is an internal error.
System action
The agent is abnormally terminated. Because the System action
agent is in a must-complete state, the Db2
subsystem is terminated with reason code 00D94001 Standard Db2 diagnostic information is recorded in
and message DSNV086E. Standard Db2 diagnostic SYS1.LOGREC, and an SVC dump is requested.
information is recorded in SYS1.LOGREC. An 04E-
D94012 SVC dump is requested. Operator response
Operator response SYS1.LOGREC, SVC dump, and console output. Notify
1. Run the print log map (DSNJU004) utility to print the system programmer.
the content of both BSDSs.
2. Print SYS1.LOGREC. Problem determination
3. Use the MVS DISPLAY DUMP command to get the At the time of the abend, general register zero contains
failure reason code from dump titles. the address of the invalid SRPL request block.
4. Notify your system programmer. 00D95001

Obtain a copy of the SYS1.LOGREC and the SVC dump The recovery manager's common FRR (DSNRCRFR)
for the original error. invoked Db2 subsystem termination, because an
To restart Db2, you must take one of the following unrecoverable error was detected during checkpoint
actions: (DSNRCPRC) processing.
• Add the missing archive log data sets back to the This is a Db2 subsystem termination reason code.
BSDS with the change log inventory (DSNJU003) For further information, see IRLM abend codes (IRLM
utility and increase the MAXARCH parameter in the messages and codes).
DSN6LOGP member of DSNZPARM to complete the
rollback. System action
• Restart Db2 with a conditional restart specifying Standard Db2 diagnostic information is recorded in
BACKOUT=NO to bypass the unit of recovery that is SYS1.LOGREC, and an SVC dump is requested for the
in-abort. original error before Db2 subsystem termination is
initiated.
At the time of the abend, registers 3 and 4 contain the Operator response
6-byte relative byte address (RBA) of the beginning of Print SYS1.LOGREC, and restart Db2.
this unit of recovery. Db2 must read the log back to
this point to complete the ROLLBACK of this unit of
recovery. System programmer response
Related tasks Obtain a copy of SYS1.LOGREC and the SVC dump for
Backing up and recovering your data (Db2 the original error.
Related reference Problem determination
DSNJU003 (change log inventory) (Db2 Utilities) See the original error.
00D95011
Related information
00D94001
Explanation
DSNV086E (Db2 Messages)
The recovery manager checkpoint (DSNRPBCW) FRR
00D94014 invoked Db2 subsystem termination, because an

unrecoverable error was detected while performing its 00D96011
checkpoint functions.
This is a Db2 subsystem termination reason code. Explanation
The restart participation FRR invoked Db2 subsystem
termination, because an unrecoverable error was
detected while processing log records during restart.
System action
Standard Db2 diagnostic information is recorded in For further information, see IRLM abend codes (IRLM
SYS1.LOGREC, and an SVC dump is requested for the messages and codes).
initiated.
System action
Operator response Standard Db2 diagnostic information is recorded in
Print SYS1.LOGREC, and restart Db2. original error before Db2 subsystem termination is
initiated.
Obtain a copy of the SYS1.LOGREC and the SVC dump
Operator response
for the original error. Print SYS1.LOGREC, correct the problem, and restart
Db2.
00D96001
for the original error.

The recovery manager's restart FRR invoked Db2
subsystem termination, because an unrecoverable
error was detected during the restart processor 00D96021
(DSNRRPRC) processing.
This is a Db2 subsystem termination reason code. Explanation
The Db2 subsystem was terminated during restart
because a failure occurred while attempting to read
the log forward MODE(DIRECT). It is accompanied by a
System action recovery log manager abend X'04E' with a reason code
Standard Db2 diagnostic information is recorded in describing the specific failure.
SYS1.LOGREC, and an SVC dump is requested for the Each time a portion of the log is skipped, a read direct
original error before Db2 subsystem termination is is used to validate the beginning RBA of the portion
initiated. that is read.
Operator response
Print SYS1.LOGREC, and restart Db2. System action
System programmer response SYS1.LOGREC, and an SVC dump is requested for the
Obtain a copy of the SYS1.LOGREC and the SVC dump original error before Db2 subsystem termination is
for the original error. initiated.

See the original error. 1. Run the print log map (DSNJU004) utility to print
content of both BSDSs.

2. Print SYS1.LOGREC. System programmer response
3. Follow instructions for the accompanying recovery Obtain a copy of the SYS1.LOGREC and the SVC dump
log manager error. Use the MVS DISPLAY DUMP for the original error.
command to get the failure reason code from dump
titles.
System programmer response At the time of the abend, registers 2 and 3 (as shown
in the dump or in SYS1.LOGREC) contain the 6-byte
Obtain a copy of the SYS1.LOGREC and the SVC dump relative byte address (RBA) of the last log record that
for the original error. If possible, correct the cause of was read before end-of-log was encountered.
original error and restart Db2.
Related concepts
Related concepts
X'E4......' codes restart (Db2 Administration Guide)
Reason code identifiers that begin with 00E4
IRLM abend codes (IRLM messages and codes)
communicate normal and error situations with
Db2 utilities. Related tasks
Preserving LOGREC data (Collecting data)
restart (Db2 Administration Guide) Related reference
IRLM abend codes (IRLM messages and codes) DSNJU004 (print log map) (Db2 Utilities)
Related tasks 00D96031
Related reference
Explanation
The restart FRR invoked Db2 subsystem termination,
00D96022 because a failure occurred while attempting to read
the log backward MODE(DIRECT). It is accompanied
by a recovery log manager abend X'04E' with a reason
Explanation
code describing the specific failure.
The restart FRR invoked abend, because, while reading
Each time a portion of the log is skipped, a read direct
the log forward during restart, the end-of-log was read
is used to validate the beginning RBA of the portion
before all recovery log scopes had been processed. It
that is read.
is followed by Db2 abnormal subsystem termination
with the same reason code ('00D96022'). This is a Db2 subsystem termination reason code.

abend before Db2 subsystem termination is initiated.
initiated.
Operator response
1. Run the print log map (DSNJU004) utility to print Operator response
1. Run the print log map (DSNJU004) utility to print
2. Print SYS1.LOGREC. content of both BSDSs.
3. Follow instructions for the accompanying recovery 2. Print SYS1.LOGREC.
log manager error. Use the MVS DISPLAY DUMP
3. Follow instructions for the accompanying recovery
titles.
4. Notify your system programmer. titles.
4. Start Db2 again.

Obtain a copy of the SYS1.LOGREC and the SVC dump The recovery manager's restart function detected an
for the original error. internal error.

See the accompanying abend reason code. Standard Db2 diagnostic information is recorded in
00D96032 error. For more information see message DSNL429.

During restart, the end of the log was read before Notify the system programmer.
all the expected log ranges had been processed. The
abend is accompanied by a Db2 abnormal subsystem
termination with the same reason code ('00D96032'). System programmer response
This is a Db2 subsystem termination reason code. See message DSNL429 for more information.
messages and codes). Problem determination
System action
Standard Db2 diagnostic information is recorded in was run, and a listing of the SYSLOG data set for the
SYS1.LOGREC. A 04E-D96032 SVC dump is requested. period of time that spans the failure.
The Db2 subsystem is terminated with DSNV086E
message. • SVC dump (or system dump), taken to SYS1.DUMPxx
Operator response
1. Run the print log map (DSNJU004) utility to print executing IFCEREP1.
00D98001
2. Print SYS1.LOGREC.
3. Use the MVS DISPLAY DUMP command to get the Explanation
failure reason code from dump titles.
4. Notify your system programmer. The recovery manager's common FRR (DSNRCRFR)
invoked Db2 subsystem termination, because an
unrecoverable error was detected during indoubt-
System programmer response UR (DSNRRIPR, DSNRRIRD, DSNRRIUN, DSNRIPMU)
Obtain a copy of the SYS1.LOGREC and the SVC dump processing.
for the original error. Determine where the log went. This is a Db2 subsystem termination reason code.
If you suspect an error in Db2, you might need to For further information, see IRLM abend codes (IRLM
report the problem. For information about identifying messages and codes).
data (Collecting data). before restarting.
System action
Problem determination Standard Db2 diagnostic information is recorded in
At the time of the abend, registers 2 and 3 contain original error before Db2 subsystem termination is
the 6-byte relative byte address (RBA) of the last initiated.
log record that was read before end-of-log was
encountered.
Operator response
00D96041
Print SYS1.LOGREC, restart Db2.

Obtain a copy of the SYS1.LOGREC and the SVC dump Standard Db2 diagnostic information is recorded in
for the original error. SYS1.LOGREC, and an SVC dump is requested for the
Problem determination initiated.

Operator response
00D98011
Explanation 2. Print SYS1.LOGREC.
The FRR for the resolve-indoubt-UR request servicer 3. Follow instructions for the accompanying recovery
(DSNRIURS) invoked Db2 subsystem termination, log manager error. Use the MVS DISPLAY DUMP
because an unrecoverable error was detected command to get the failure reason code from dump
processing a request. titles.
This is a Db2 subsystem termination reason code. 4. Start Db2 again.
messages and codes). System programmer response
System action
SYS1.LOGREC, and an SVC dump is requested for the Problem determination
initiated. See the accompanying abend reason code.
00D98022
Operator response
Print SYS1.LOGREC, and restart Db2. Explanation
Resolved indoubt invoked abend when end-of-log
System programmer response was reached before all ranges had been processed
for forward recovery. This abend is accompanied by
abnormal Db2 subsystem termination with the same
reason code ('00D98022').
Problem determination This is a Db2 subsystem termination reason code.

See the accompanying abend reason code. messages and codes).
00D98021
System action
Explanation Standard Db2 diagnostic information is recorded in
The resolved indoubt FRR invoked Db2 subsystem
termination because of a failure while attempting to
initiated.
read the log MODE(DIRECT) during forward recovery.
It is accompanied by a recovery log manager abend
X'04E' with a reason code describing the specific Operator response
failure.
Each time a portion of the log is skipped, a read direct content of both BSDSs.
is used to validate the beginning RBA of the portion 2. Print SYS1.LOGREC.
that is read.
This is a Db2 subsystem termination reason code. log manager error. Use the MVS DISPLAY DUMP
For further information, see IRLM abend codes (IRLM command to get the failure reason code from dump
messages and codes). titles.

4. Start Db2 again. Problem determination
See the accompanying abend reason code.
00D98032
Explanation
Problem determination Resolved indoubt FRR invoked abend when end-of-log
was reached before all ranges had been processed
At the time of the abend, registers 2 and 3 contain for backward recovery. This abend is accompanied by
the 6-byte relative byte address (RBA) of the last abnormal Db2 subsystem termination with the same
log record that was read before end-of-log was reason code ('00D98032').
encountered.
00D98031 For further information, see IRLM abend codes (IRLM
Explanation
The resolved indoubt FRR invoked Db2 subsystem System action
termination, because a failure occurred during an Standard Db2 diagnostic information is recorded in
attempt to read the log MODE(DIRECT) while reading SYS1.LOGREC, and an SVC dump is requested for the
the log backward. It is accompanied by a recovery log original error before Db2 subsystem termination is
manager abend X'04E' with a reason code describing initiated.
the specific failure.
Each time a portion of the log is skipped, a read direct Operator response
is used to validate the begin-scope RBA of the portion
that is read. 1. Run the print log map (DSNJU004) utility to print
2. Print SYS1.LOGREC.
messages and codes). 3. Follow instructions for the accompanying recovery
System action titles.
Standard Db2 diagnostic information is recorded in 4. Start Db2 again.
initiated. System programmer response
Operator response for the original error.

content of both BSDSs. Problem determination
2. Print SYS1.LOGREC. At the time of the abend, registers 2 and 3 contain
the 6-byte relative byte address (RBA) of the last
log record that was read before end-of-log was
encountered.
titles. 00D98600
4. Start Db2 again.
Explanation
System programmer response An internal error occurred during processing of a
Obtain a copy of the SYS1.LOGREC and the SVC dump deactivation or destruction request for a member of
for the original error. a data sharing group.

Depending on the circumstances, some combination of If the correct member was specified in the request,
the following actions occurs: quiesce the member, and restart the deactivation or
destruction process.
• An SVC dump is generated.
• Restart processing terminates. If an incorrect member was specified, use the change
log inventory (DSNJ003) utility RSTMBR command to
• Additional messages is issued. stop future attempts to process the member.
Related reference
Attempt to identify and resolve the problem:
00D98603
1. If other messages were issued in conjunction with
the error, correct the conditions that they describe
and try the request again. Explanation
2. If the problem persists, collect the information that A deactivation or destruction request for a member of
is identified in the problem determination section a data sharing group specified a member that was not
and contact IBM Support. properly shut down (as determined by its checkpoint
queue).
System action
• The SVC dump, if one is generated The request is ignored.
• The LOGREC and syslog from the time of the failure

00D98601
Quiesce the member before starting the deactivation
or destruction process:
Explanation
1. Restart the member.
A deactivation or destruction request for a member of
2. Make sure that the member has no outstanding
a data sharing group specified an invalid member ID.
work.
3. Stop the member with MODE(QUIESCE).
System action
The request is ignored. The invalid request record is Problem determination
deleted from the BSDS.
Use the print log map utility (DSNJU004) to see the
contents of the checkpoint queue.
Related concepts
Correct the member ID, and resubmit the request.
Starting a data sharing member (Db2 Data
Problem determination Stopping a data sharing member (Db2 Data
Use the LOGREC and syslog from the time of the failure Sharing Planning and Administration)
to aid in problem determination. Related reference
00D98602
00D98604
Explanation
A deactivation or destruction request for a member of Explanation
a data sharing group specified a member that was not
The BSDS for a data sharing member that was
quiesced.
the target of a deactivation or destruction request
encountered a read error when it attempted to access
System action the checkpoint queue.
The request is ignored.

The request is ignored. Depending on the Restart is abended.
circumstances, some combination of the following
actions occurs: Operator response
• An SVC dump is generated.
Inform the system programmer.
• Additional messages is issued.
Let the change log inventory (DSNJU003) utility select
Use the print log map utility (DSNJU004) to see the the checkpoint RBA when building the conditional
contents of the checkpoint queue. If no checkpoint restart record. If a specific checkpoint is desired, use
queue exists, verify that the member was successfully DSN1LOGP to print out the checkpoint log records
started at some time in the past. If the member has within a specified range. If manual selection of the
never been started, deactivate or destroy it. checkpoint RBA is desired, use the print log map
Related reference (DSNJU004) utility to print the checkpoint queue.
Print the checkpoint queue by using the CHKPTRBA
keyword.
00D98605
Explanation • Print the checkpoint records within the desired range
using DSN1LOGP.
The SCA did not contain a record for the target
member of a deactivation or destruction request, • Print the checkpoint queue using DSNJU004.
and the record in this Db2 subsystem's BSDS is not • Verify the checkpoint queue against the DSN1LOGP
current. report.
• If automatic checkpoint selection was used and the
System action checkpoint was invalid, find the valid checkpoint
RBA in the DSN1LOGP report. Use this checkpoint
The request is ignored. Additional messages might be
RBA in the CRCR using the CHKPTRBA keyword.
issued.
• If an explicit checkpoint was specified and the
checkpoint was invalid, let DSNJU003 automatically
choose the checkpoint by not specifying a
Use the print log map utility (DSNJU004) to see CHKPTRBA keyword.
information about each member's BSDS. Determine
00D99002
which member has current information for the target
member, and start that member (the one with current
information) before starting any target member that Explanation
has caused code 00D98605. Then resubmit the
Validation of the STARTRBA failed because either the
request.
end of the log was reached, or a bad log record
Related concepts was encountered while attempting to find the first
Starting a data sharing member (Db2 Data complete log record.
Restart abends.
00D99001
Operator response
Explanation Inform the system programmer.
An attempt to read the CHKPTRBA failed to return a
valid checkpoint record. This abend is issued after the System programmer response
DSNR015I error message is issued.
Check the console log for DSNJ (Log Manager)
messages; these may indicate failures in the Log

Manager processing, or may reveal additional useful the problem. For information about identifying and
information for diagnostic purposes. Use DSN1LOGP to reporting the problem, see Collecting diagnostic data
find a safe STARTRBA to use for restart. If a STARTRBA (Collecting data).
is specified, the Recovery Manager will use it as a
starting point. From the starting point, the Recovery User response
Manager will attempt to find the beginning of a valid
log record. Notify the system programmer.

Collect the following diagnostic items: RM standard diagnostic information is provided in
"Recovery Manager Reason Codes (X'D9')". In addition,
the following diagnostic information is provided in
registers:
Register 0
The data manager ERQUAL that identifies the place
within the data manager filter routine where the
(DSNJU004) utility.
error was detected
00D99003 Register 2,3
The RBA of the log record that was being read at
Explanation the time of the error
CSRONLY was specified in the conditional restart Register 8

record. Only the Db2 status phase of restart will The address of the selection block for the database
complete. services address space (ssnmDBM1)
Register 9
System action The address of the selection block for DSCF
Restart abends. 00D99900

Use the change log inventory (DSNJU003) utility to The request to commit the unit of recovery failed
cancel the current conditional restart record or create because the agent is a participant in a global
a new conditional restart record. transaction and the global transaction is going to be
backed out.
00D99004
System action
Explanation
The unit of recovery is not committed.
A log read failed because an internal error was
detected by the data manager while examining the log
User response
record during Db2 restart.
The application must roll back to the previous
System action COMMIT.
The execution unit writes a record to SYS1.LOGREC 00D9AAAA

and requests a SVC dump. Restart abends.
Explanation
Operator response This reason code identifies additional data stored in
Collect the SYS1.LOGREC and SVC dump. Notify the the SDWA variable recording area following a failure
system programmer. during abort-UR.
This reason code appears only in the SDWA variable
System programmer response recording area (VRA) and serves only to identify data
(in addition to the standard Db2 diagnostic information
Obtain the SYS1.LOGREC and the SVC dump. If you that is stored in the SDWA). This reason code is the
suspect an error in Db2, you might need to report first data item of the standard information. As such, it

always appears in the VRA of an SDWA for a primary 4
error completion/reason code. If no data is added, the URE address
reason code in the SDWA VRA is the same as that 4
associated with the completion code. DSNWRCRD return code
1
System action Retry flags
Five bytes of data preceded by code VRAHEX are
stored following the EBCDIC string 'RMC-COMMIT/ System programmer response
ABORT'.
Use this information with the instructions for the
Length specific failure. If you suspect an error in Db2, you
Data might need to report the problem. For information
1 byte about identifying and reporting the problem, see
Retry flags Collecting diagnostic data (Collecting data).
1 byte 00D9CCCC
Retry id
1 byte Explanation
Notification RMID
This reason code identifies additional data stored in
2 bytes
the SDWA variable recording area following a failure
ACE progress state (ACEPROG)
during commit-UR.
This reason code appears only in the SDWA variable
recording area (VRA) and serves only to identify
Use this information in conjunction with other data (in addition to the standard Db2 diagnostic
information for the primary failure. If you suspect an information, stored in the SDWA). This reason code
error in Db2, you might need to report the problem. is the first data item of the standard information. As
For information about identifying and reporting the such, it always appears in the VRA of an SDWA for a
problem, see Collecting diagnostic data (Collecting primary error completion/reason code.
data).
00D9BBBB System action
Five bytes of data preceded by code VRAHEX are
Explanation stored following the EBCDIC string 'RMC-COMMIT/
ABORT'.
This reason code identifies additional data stored in
the SDWA variable recording area following a failure Length
during begin-UR. Data
This reason code appears only in the SDWA variable 1 byte

recording area (VRA) and it serves only to identify Retry id
data (in addition to the standard Db2 diagnostic 1 byte
information, stored in the SDWA). This reason code Notification RMID
is the first data item of the standard information. As 1 byte
such, it always appears in the VRA of an SDWA for ACE progress state (ACEPROG)
a primary error completion/reason code. If no data is
added, the reason code in the SDWA VRA is the same 1 bit
as that associated with the completion code. In flight
1 bit
System action In-Commit1
1 bit
The following data is stored preceded by code Indoubt
VRAHEX.
1 bit
Length In-Commit2
Data
1 bit
4 End-Commit
Content of ACEURE

1 bit 4
In-Abort URE address
1 bit 4
End-Abort DSNWRCRD return code
1 bit
(Reserved) System programmer response
Use this information in conjunction with the
System programmer response information about the error completion code. If you
Use this information with the instructions for the suspect an error in Db2, you might need to report
specific failure. If you suspect an error in Db2, you the problem. For information about identifying and
might need to report the problem. For information reporting the problem, see Collecting diagnostic data
about identifying and reporting the problem, see (Collecting data).
Collecting diagnostic data (Collecting data). 00D9F001
00D9EEEE
Explanation
Explanation An internal error was detected during recovery
This reason code identifies additional data stored in manager processing.
the SDWA variable recording area following a failure
during end-UR. System action
This reason code appears only in the SDWA variable The request is terminated and an SVC memory dump
recording area (VRA) and serves only to identify is scheduled.
data (in addition to the standard Db2 diagnostic
information, stored in the SDWA). This reason code
is the first data item of the standard information. As
Collect the following documentation and contact IBM
such, it always appears in the VRA of an SDWA for a
Support:
primary error completion/reason code.
• SVC memory dump
System action • Syslog
The following data is stored preceded by code Additional documentation might be required,
VRAHEX. depending on the exact nature of the error.
Length
Data

Chapter 16. X'E2......' codes
Reason code identifiers that begin with 00E2 communicate normal and error situations with the storage
manager.
00E20001 • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Explanation 00E20002
The get variable storage function detected that input
parameters passed by the invoker were invalid. Explanation
The free variable storage function detected that input
System action parameters (either the pool address or the pool type)
passed by the invoker were invalid.
The agent is abended.


and a Db2 dump is requested. The following general
purpose registers contain the indicated diagnostic Problem determination
information:
• Register 4 contains the address of the pool header and a Db2 dump is requested. The following general
block (PHB), which contains information for the purpose registers contain the indicated diagnostic
current status of the pool. information:
• Register 7 contains the value of the caller's saved • Register 4 contains the address of the pool header
register 14. block (PHB), which contains information for the
• Register 3 contains the input request length. current status of the pool.
• Register 5 contains the input request owner ID. • Register 7 contains the value of the caller's saved
register 14.
Offset X'1EF' in the SDWA contains a VRACAN key of
X'3D', followed by the module name of the Storage Offset X'1EF' in the SDWA contains a VRACAN key of
Manager invoker. X'3D', followed by the module name of the Storage
Manager invoker.
Db2 (04E and 04F abends). • Dynamic dump, taken to SYS1.DUMPxx data set, by
data set, as result of an operator-initiated dump • SVC dump (or system dump), taken to SYS1.DUMPxx
command or SLIP trap exit. data set, as result of an operator-initiated dump

• Listing of SYS1.LOGREC data set, obtained by the time the pool was created indicated that the pool
executing IFCEREP1. was already at maximum size.
00E20003
System action
Explanation The agent is abended.
In order to satisfy an unconditional request for
storage, the get variable storage function needed to Operator response
obtain storage from GETMAIN to expand a storage Notify the system programmer.
pool. However, GETMAIN indicated that sufficient
storage in the private area was not available.
The agent is abended. and reporting the problem, see Collecting diagnostic
Operator response
System programmer response and a Db2 dump is requested. Register 4 contains the
address of the pool header block (PHB). Register 7
Increase region size. contains the value of the caller's saved register 14.
At offset 1EF in the SDWA, there is a VRACAN key
of '3D' (in HEX), followed by the module name of the
Diagnostic information is recorded in SYS1.LOGREC, Storage Manager invoker.
and a Db2 dump is requested. Register 2 contains
the ASID, in hexadecimal, of the private area to be
printed. Register 4 contains the address of the pool • Console output from the system on which the job
header block (PHB). Register 7 contains the value of was run, and a listing of the SYSLOG data set for the
the caller's saved register 14. period of time that spans the failure.
At offset X'221' in the SDWA, there is a VRACAN key • Dynamic dump, taken to SYS1.DUMPxx data set, by
of '3D' (in HEX), followed by the module name of the Db2 (04E and 04F abends).
storage manager invoker. • SVC dump (or system dump), taken to SYS1.DUMPxx
Collect the following diagnostic items: data set, as result of an operator-initiated dump
executing IFCEREP1.
• Dynamic dump, taken to SYS1.DUMPxx data set, by 00E20005
• SVC dump (or system dump), taken to SYS1.DUMPxx Explanation
data set, as result of an operator-initiated dump The free variable storage function detected that the
command or SLIP trap exit. address of a block being freed was invalid. That is, it
• Listing of SYS1.LOGREC data set, obtained by did not lie within an existing storage pool.
executing IFCEREP1.
00E20004 System action
Explanation
In order to satisfy an unconditional request for Operator response
storage, the get variable storage function needed to Notify the system programmer.
obtain additional storage (from GETMAIN) to expand a
storage pool. However, the pool attributes defined at

If you suspect an error in Db2, you might need to Diagnostic information is recorded in SYS1.LOGREC,
report the problem. For information about identifying and a Db2 dump is requested. Register 4 contains the
and reporting the problem, see Collecting diagnostic address of the pool header block (PHB). Register 7
data (Collecting data). contains the value of the caller's saved register 14.
Register 11 contains the address of the free block.
Problem determination At offset 1EF in the SDWA, there is a VRACAN key
Storage Manager invoker.
and a Db2 dump is requested. Register 4 contains the
address of the pool header block (PHB). Register 7 Collect the following diagnostic items:
contains the value of the caller's saved register 14.
Register 11 contains the address of the invalid block to
be freed.
At offset 1EF in the SDWA, there is a VRACAN key • Dynamic dump, taken to SYS1.DUMPxx data set, by
of '3D' (in HEX), followed by the module name of the Db2 (04E and 04F abends).
• Console output from the system on which the job command or SLIP trap exit.
was run, and a listing of the SYSLOG data set for the • Listing of SYS1.LOGREC data set, obtained by
period of time that spans the failure. executing IFCEREP1.
command or SLIP trap exit. The allocate variable storage pool function detected
• Listing of SYS1.LOGREC data set, obtained by that the input parameters passed by the invoker were
executing IFCEREP1. invalid.

Explanation
The free variable storage function detected that the Operator response
block being freed was not allocated. That is, it was
already free. Notify the system programmer.

The agent is abended. If you suspect an error in Db2, you might need to
Operator response
If you suspect an error in Db2, you might need to and a Db2 dump is requested. The following general
report the problem. For information about identifying purpose registers contain the indicated diagnostic
and reporting the problem, see Collecting diagnostic information:
• Register 2 contains the input parameter list address.
• Register 3 contains the input maximum pool size.
• Register 4 contains the input expansion segment
size.
Chapter 16. X'E2......' codes 941

• Register 5 contains the input initial segment size. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
The trace information contains the address of the
invalid parameter list. 00E20009
Explanation
was run, and a listing of the SYSLOG data set for the The get fixed blocks function detected that input
period of time that spans the failure. parameters passed by the invoker were invalid.
• SVC dump (or system dump), taken to SYS1.DUMPxx The agent is abended.
Operator response
00E20008
The free variable storage pool function detected that and reporting the problem, see Collecting diagnostic
the input parameter (PHB, pool header block) did not data (Collecting data).
represent an existing pool.
System action
The agent is abended. and a Db2 dump is requested. The following general
purpose registers contain the indicated diagnostic
Operator response information:
Notify the system programmer. • Register 4 contains the address of the pool header
block (PHB).
System programmer response • Register 7 contains the value of the caller's saved
register 14.
report the problem. For information about identifying • Register 5 contains the number of blocks requested.
and reporting the problem, see Collecting diagnostic The invalid input parameters are also contained in the
data (Collecting data). trace information.
Offset X'1EF' in the SDWA contains a VRACAN key of
Problem determination X'3D', followed by the module name of the Storage
Diagnostic information is recorded in SYS1.LOGREC, Manager invoker.
and a Db2 dump is requested. The trace information Collect the following diagnostic items:
contains the address of the invalid PHB (pool header
block). • Console output from the system on which the job
• Console output from the system on which the job • Dynamic dump, taken to SYS1.DUMPxx data set, by
was run, and a listing of the SYSLOG data set for the Db2 (04E and 04F abends).
• Dynamic dump, taken to SYS1.DUMPxx data set, by data set, as result of an operator-initiated dump
Db2 (04E and 04F abends). command or SLIP trap exit.
• SVC dump (or system dump), taken to SYS1.DUMPxx • Listing of SYS1.LOGREC data set, obtained by
data set, as result of an operator-initiated dump executing IFCEREP1.
00E2000A

The get tracked storage function requested storage Increase region size.
from the DSNSGETM function for a tracking element
in order to track the storage to be returned to the Problem determination
invoker. However, storage for the tracking element was
unavailable. The invoker's request was unconditional. Diagnostic information is recorded in SYS1.LOGREC,
System action
printed. Register 4 contains the address of the pool
The agent is abended. header block (PHB). Register 7 contains the value of
the caller's saved register 14. The trace information
Operator response contains the number of blocks requested.
At offset 1EF in the SDWA, there is a VRACAN key
Diagnostic information is recorded in SYS1.LOGREC, data set, as result of an operator-initiated dump
and a Db2 dump is requested. Register 2 contains the command or SLIP trap exit.
ASID, in hexadecimal, of the private area to be printed.
Collect the following diagnostic items: executing IFCEREP1.
• Console output from the system on which the job 00E2000C
Explanation
Db2 (04E and 04F abends). In order to satisfy an unconditional request, the get
fixed block(s) function needed to obtain additional
storage to expand a storage pool. However, the pool
attributes defined at the time the pool was created
indicated that the pool was already at maximum size.
executing IFCEREP1.
System action
00E2000B
Explanation
Operator response
In order to satisfy an unconditional request, the get
storage to expand a storage pool. However, GETMAIN
indicated that insufficient storage existed in the System programmer response
private area.
Operator response

Problem determination the value of the caller's saved register 14. Register 11
contains the address of the invalid block to be freed.
and a Db2 dump is requested. Register 4 contains the At offset X'1EF' in the SDWA, there is a VRACAN key
address of the pool header block (PHB). Register 7 of X'3D', followed by the module name of the storage
contains the value of the caller's saved register 14. manager invoker.
The trace information contains the number of blocks Collect the following diagnostic items:
requested.
At offset 1EF in the SDWA, there is a VRACAN key was run, and a listing of the SYSLOG data set for the
of '3D' (in HEX), followed by the module name of the period of time that spans the failure.
Collect the following diagnostic items: Db2 (04E and 04F abends).
• Console output from the system on which the job • SVC dump (or system dump), taken to SYS1.DUMPxx
was run, and a listing of the SYSLOG data set for the data set, as result of an operator-initiated dump
period of time that spans the failure. command or SLIP trap exit.
• Dynamic dump, taken to SYS1.DUMPxx data set, by • Listing of SYS1.LOGREC data set, obtained by
Db2 (04E and 04F abends). executing IFCEREP1.
• SVC dump (or system dump), taken to SYS1.DUMPxx 00E2000E
Explanation
executing IFCEREP1. Db2 detected that a segment of storage within the
pool on which the request was directed was invalid or
00E2000D contained an invalid 'free chain' of free blocks in the
segment.
Explanation
Db2 detected that either the address of a block being System action
freed (the only block or a block on a chain of blocks) The agent is abended.
was invalid or the block did not lie within an existing
storage pool.
Operator response

Operator response The most likely cause of the problem is a storage
overlay or an invalid storage request from a Db2
Notify the system programmer. component. A product other than Db2 could cause the
storage overlay problem.
The most likely cause of the problem is a storage Problem determination
overlay or an invalid storage request from a Db2 If you suspect an error in Db2, you might need to
component. A product other than Db2 could cause the report the problem. For information about identifying
storage overlay problem. and reporting the problem, see Collecting diagnostic
Problem determination Diagnostic information is recorded in SYS1.LOGREC,
If you suspect an error in Db2, you might need to and a Db2 dump is requested. Register 4 contains the
report the problem. For information about identifying address of the pool header block (PHB). Register 7
and reporting the problem, see Collecting diagnostic contains the value of the caller's saved register 14.
data (Collecting data). Register 11 contains the address of the block to be
freed if freeing a fixed block.

At offset X'1EF' in the SDWA, there is a VRACAN key • Dynamic dump, taken to SYS1.DUMPxx data set, by
of X'3D', followed by the module name of the Storage Db2 (04E and 04F abends).
Manager invoker. • SVC dump (or system dump), taken to SYS1.DUMPxx

The allocate fixed-block pool function detected an
invalid input parameter passed by its invoker.
executing IFCEREP1.
System action
00E2000F
Explanation
Operator response
The free fixed block(s) function detected that the only
block, or the one block on the chain of blocks, being
freed did not represent an allocated block; that is, it
was already free. System programmer response
Operator response
and a Db2 dump is requested. The following general
System programmer response purpose registers contain the indicated diagnostic
If you suspect an error in Db2, you might need to information:
report the problem. For information about identifying • Register 2 contains the input parameter list address.
• Register 3 contains the input request block size.
• Register 4 contains the input maximum pool size.
Problem determination • Register 5 contains the input expansion segment
size.
and a Db2 dump is requested. Register 4 contains the The trace information also contains the address of the
address of the pool header block (PHB). Register 7 invalid parameter list.
contains the value of the caller's saved register 14. Collect the following diagnostic items:
Register 11 contains the address of the free block.
At offset 1EF in the SDWA, there is a VRACAN key was run, and a listing of the SYSLOG data set for the
of '3D' (in HEX), followed by the module name of the period of time that spans the failure.
executing IFCEREP1.

00E20011 System programmer response
Explanation report the problem. For information about identifying
The free fixed-block pool function detected that the and reporting the problem, see Collecting diagnostic
input parameter either was not a valid pool header data (Collecting data).
block (PHB), or it did not represent an existing pool.
System action Diagnostic information is recorded in SYS1.LOGREC,
The agent is abended. and a Db2 dump is requested. The following general
purpose registers contain the indicated diagnostic
information:
Operator response
• Register 2 contains the input parameter list address.
• Register 3 contains the input request length.
• Register 4 contains the input storage class.
The trace information has the address of the invalid
parameter list.
Diagnostic information is recorded in SYS1.LOGREC, • Dynamic dump, taken to SYS1.DUMPxx data set, by
and a Db2 dump is requested. The trace information Db2 (04E and 04F abends).
has the address of the pool header block (PHB). • SVC dump (or system dump), taken to SYS1.DUMPxx
executing IFCEREP1.
data set, as result of an operator-initiated dump The get tracked storage from GETMAIN function was
command or SLIP trap exit. unable to obtain sufficient storage in private area to
• Listing of SYS1.LOGREC data set, obtained by satisfy an unconditional request.
executing IFCEREP1.
Explanation
The get tracked storage from the GETMAIN function Operator response
detected an invalid input parameter passed by its Notify the system programmer.
invoker.

System action
Increase region size.
Operator response
Notify the system programmer. and a Db2 dump is requested. Register 2 contains

printed. The trace information has the address of the • Listing of SYS1.LOGREC data set, obtained by
parameter list. executing IFCEREP1.
Collect the following diagnostic items: 00E20015
The allocate stack function, which is always
• Dynamic dump, taken to SYS1.DUMPxx data set, by unconditional, requested storage from GETMAIN to
Db2 (04E and 04F abends). obtain a stack segment. GETMAIN indicated that 8K
• SVC dump (or system dump), taken to SYS1.DUMPxx bytes of private area storage in subpool 229 was not
data set, as result of an operator-initiated dump available.
executing IFCEREP1.
00E20014
Operator response
The free tracked storage function detected that the
area requested to be freed was not valid. Either the System programmer response
address did not represent storage currently allocated
(via the DSNSGETM function), or the storage class Increase maximum private storage.
passed as input to DSNSFREM did not match the class
assigned to the storage by DSNSGETM. Problem determination
System action and a Db2 dump is requested. There is probably a
The agent is abended. shortage of private area storage in the address space
in which the failure occurred. Register 2 contains the
Operator response
data (Collecting data). • SVC dump (or system dump), taken to SYS1.DUMPxx
Diagnostic information is recorded in SYS1.LOGREC, executing IFCEREP1.
and a Db2 dump is requested. The trace information
00E20016
has the address of the storage and the storage class.
Explanation
The get stack storage function, in order to satisfy
an unconditional request for stack storage, requested
storage from GETMAIN. However, GETMAIN indicated
• Dynamic dump, taken to SYS1.DUMPxx data set, by that sufficient storage in subpool 229 was not
Db2 (04E and 04F abends). available.
data set, as result of an operator-initiated dump System action

Notify the system programmer. period of time that spans the failure.
Increase region size. • SVC dump (or system dump), taken to SYS1.DUMPxx
Diagnostic information is recorded in SYS1.LOGREC, executing IFCEREP1.
ASID, in hexadecimal, of the private area to be printed. 00E20018
Explanation
was run, and a listing of the SYSLOG data set for the The get stack storage function detected that the
period of time that spans the failure. amount of storage requested by the invoker was
• Dynamic dump, taken to SYS1.DUMPxx data set, by invalid. For a 31-bit request the amount was less than
Db2 (04E and 04F abends). or equal to zero. For a 64-bit request the amount was
either less than or equal to zero or it exceeded the
• SVC dump (or system dump), taken to SYS1.DUMPxx maximum allowable request size.
System action
executing IFCEREP1. The thread is abended.
00E20017 System action:

The free stack storage function detected that the Notify the system programmer.
address of the area to be freed did not lie within
allocated storage in the stack indicated by the System programmer response
requester.
The agent is abended. data (Collecting data).

Notify the system programmer. Diagnostic information is recorded in SYS1.LOGREC,
and a Db2 dump is requested.
data (Collecting data). • Dynamic dump, taken to SYS1.DUMPxx data set, by
ASID, in hexadecimal, of the private area to be printed. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
00E20019

The purge pool function detected that input If you suspect an error in Db2, you might need to
parameters passed by the invoker were invalid. report the problem. For information about identifying

Operator response Diagnostic information is recorded in SYS1.LOGREC,
Notify the system programmer. return code from DSN3EST0; this is the MVS ESTAE
return code.
and a Db2 dump is requested. The following general command or SLIP trap exit.
registers contain the indicated diagnostic information: • Listing of SYS1.LOGREC data set, obtained by
• Register 4 contains the input pool address. executing IFCEREP1.
• Register 5 contains the input pool owner ID. 00E2001B

The trace information also contains the input
parameters. Explanation
Collect the following diagnostic items: The SETLOCK OBTAIN function issued a nonzero
return code.
• Dynamic dump, taken to SYS1.DUMPxx data set, by The invoker of storage manager functions is
Db2 (04E and 04F abends). abnormally terminated.
data set, as result of an operator-initiated dump Operator response
executing IFCEREP1.
00E2001A
ESTAE recovery can not be established, because either data (Collecting data).
an unexpected error occurred, or SCB is not available.
System action Diagnostic information is recorded in SYS1.LOGREC,
The agent is abended. and a Db2 dump is requested.

The Db2 subsystem is abended. In some cases, the
• SVC dump (or system dump), taken to SYS1.DUMPxx FRR is established by the caller of the storage manager
data set, as result of an operator-initiated dump (SM) subcomponent. When this is the case, the SVC
command or SLIP trap exit. dump is requested by the caller. When this is not the
• Listing of SYS1.LOGREC data set, obtained by case, the SM requests the SVC dump.
executing IFCEREP1.
00E2001C Operator response
Explanation
The purge stack function detected that one of the System programmer response
SKBs (stack block) is not valid and the SKB chain is If you suspect an error in Db2, you might need to
possibly damaged. report the problem. For information about identifying
The SKB chain is repaired and processing continues.
Operator response A Db2 dump is requested, but in some cases the dump
request is made by the caller of storage manager,
rather than by storage manager itself. Register 6
contains the address of the EB.
and a Db2 dump is requested. The trace information command or SLIP trap exit.
contains the address of the EB for which the stack
segments are to be purged.
executing IFCEREP1.
00E2001E
Explanation
• Dynamic dump, taken to SYS1.DUMPxx data set, by The get stack storage function detected that two
Db2 (04E and 04F abends). asynchronous (unrelated) agents use the same stack
storage.
command or SLIP trap exit. System action
• Listing of SYS1.LOGREC data set, obtained by The agent is abended.
executing IFCEREP1.
00E2001D Operator response
Explanation
Either GPVT (global pool anchor) or LPVT (local pool System programmer response
anchor) is damaged, and no storage managed by If you suspect an error in Db2, you might need to
storage manager can be accessed. report the problem. For information about identifying

and reporting the problem, see Collecting diagnostic At offset 1EF in the SDWA, there is a VRACAN key
data (Collecting data). of '3D' (in HEX), followed by the module name of the
Diagnostic information is recorded in SYS1.LOGREC, • Console output from the system on which the job
and a Db2 dump is requested. Register 2 contains was run, and a listing of the SYSLOG data set for the
the address of the stack segment (SKB). Register 6 period of time that spans the failure.
contains the address of the EB. In the event of an • Dynamic dump, taken to SYS1.DUMPxx data set, by
ABEND, DSNTFRCV saves information in the VRA of the Db2 (04E and 04F abends).
SDWA.
• Console output from the system on which the job command or SLIP trap exit.
command or SLIP trap exit. The get variable pool function needed to obtain
storage (from GETMAIN) to create pool header
block (PHB) to represent the pool, but GETMAIN
executing IFCEREP1.
indicated that sufficient storage in private area was not
00E2001F available.

In order to satisfy an unconditional request for The agent is abended.
storage, the get variable storage function needed to
obtain storage (from GETMAIN) to expand a storage Operator response
pool. However, GETMAIN indicated that sufficient
storage in common service area (CSA) to expand the Notify the system programmer.
pool was not available.
System action
Operator response
Notify the system programmer. and a Db2 dump is requested. Register 2 contains the
Increase common service area (CSA) size. • Console output from the system on which the job
Diagnostic information is recorded in SYS1.LOGREC, Db2 (04E and 04F abends).
and a Db2 dump is requested. The common service
area (CSA) portion of the dump should be printed. • SVC dump (or system dump), taken to SYS1.DUMPxx
Register 4 contains the address of the pool header data set, as result of an operator-initiated dump
block (PHB). Register 7 contains the value of the command or SLIP trap exit.
caller's saved register 14. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
00E20021

The get variable pool function needed to obtain Increase common service area (CSA) size.
storage (from GETMAIN) to create pool header block
(PHB) to represent the pool, but GETMAIN indicated Problem determination
that sufficient storage in common service area (CSA)
was not available. Diagnostic information is recorded in SYS1.LOGREC,
address of the pool header block (PHB). Register 7
System action
contains the value of the saved caller's register 14.
The agent is abended. The common service area (CSA) portion of the dump
should be printed.
Operator response At offset 1EF in the SDWA, there is a VRACAN key
Increase common service area (CSA) size. • Console output from the system on which the job
Diagnostic information is recorded in SYS1.LOGREC, Db2 (04E and 04F abends).
and a Db2 dump is requested. The common service • SVC dump (or system dump), taken to SYS1.DUMPxx
area (CSA) portion of the dump should be printed. data set, as result of an operator-initiated dump
Collect the following diagnostic items: command or SLIP trap exit.
period of time that spans the failure. 00E20023
The get fixed pool function needed to obtain storage
(from GETMAIN) to create pool header block (PHB)
to represent the pool, but GETMAIN indicated that
• Listing of SYS1.LOGREC data set, obtained by sufficient storage in private area was not available.
executing IFCEREP1.
Explanation
In order to satisfy an unconditional request, the get Operator response
storage to expand a storage pool. However, GETMAIN
indicated that sufficient storage in common service
area (CSA) was not available. System programmer response
System action
The agent is abended. Problem determination
Operator response and a Db2 dump is requested. Register 2 contains the

period of time that spans the failure. The get tracked storage from GETMAIN function was
unable to obtain sufficient storage in common service
• Dynamic dump, taken to SYS1.DUMPxx data set, by area (CSA) to satisfy an unconditional request.
System action
command or SLIP trap exit. The agent is abended.
00E20024 Notify the system programmer.

To create a pool header block (PHB) that represents Increase common service area (CSA) size.
the pool, the get fixed pool function requested storage
from GETMAIN. However, GETMAIN indicated that Problem determination
insufficient storage existed in the common service
area (CSA) to satisfy the request. Diagnostic information is recorded in SYS1.LOGREC,
and a Db2 dump is requested. The trace information
has the address of the parameter list. The common
System action
service area (CSA) portion of the dump should be
The agent is abended. printed.
Operator response
Increase common service area (CSA) size.
Diagnostic information is recorded in SYS1.LOGREC, • Listing of SYS1.LOGREC data set, obtained by
and a Db2 dump is requested. The common service executing IFCEREP1.
area (CSA) portion of the dump should be printed.
00E20026
period of time that spans the failure. Either the allocate stack storage function or the get
stack storage function was unable to obtain 4KB of
• Dynamic dump, taken to SYS1.DUMPxx data set, by private area storage in subpool 229 for an all-segment
Db2 (04E and 04F abends). table in which a record (representing a stack storage
• SVC dump (or system dump), taken to SYS1.DUMPxx segment) was to be inserted.
System action
executing IFCEREP1. The invoker of the function is abended.
00E20025
Operator response

System programmer response 4
address of the pool header block (PHB)
7
value of the caller's saved register 14
11
Diagnostic information is recorded in SYS1.LOGREC, address of the block to be freed
and a Db2 dump is requested. There is probably a
The block to be freed includes two parts: a four word
shortage of private area storage in the address space
header of control information and the block itself. The
in which the failure occurred. Register 2 contains the
second word in the header (offset of 4) is the length of
the block.
The third word in the header (offset of 8) is the
• Console output from the system on which the job address of the storage requester. The block is made
was run, and a listing of the SYSLOG data set for the up of two parts: allocated storage and two words of
period of time that spans the failure. unallocated storage (padding area of '03').
• Dynamic dump, taken to SYS1.DUMPxx data set, by At offset 1EF in the SDWA, there is a VRACAN key
Db2 (04E and 04F abends). of '3D' (in HEX), followed by the module name of the
• SVC dump (or system dump), taken to SYS1.DUMPxx Storage Manager invoker.
00E20028
Explanation
executing IFCEREP1.
Either the get stack, deallocate stack or release stack
00E20027
storage function detected that an SKB was invalid or
was not represented accurately in the all-segment
Explanation table.
The free variable storage function detected that
unallocated storage in the block being freed has been System action
modified.
The invoker is abended.


Problem determination value of the stack segment (SKB).
Diagnostic information is recorded in SYS1.LOGREC, 00E20029
The following general purpose registers (GPRs) contain Explanation
The free variable storage function detected that
GPR although the address of the block being freed was
Content within the specified storage pool it was not the
address of the beginning of a variable block.

The agent is abended. The invoker is abended.



Diagnostic information is recorded in SYS1.LOGREC, Diagnostic information is recorded in SYS1.LOGREC,
and a Db2 dump is requested. and a Db2 dump is requested. Register 6 contains the
address of the current execution block (EB). This EB
has a pointer to the current head stack block (SKB)
that is encountering the problem.
GPR
Content Collect the following diagnostic items:
4 • Console output from the system on which the job

value of the pool header block (PHB) was run, and a listing of the SYSLOG data set for the
7
address of the caller's saved register 14 • Dynamic dump, taken to SYS1.DUMPxx data set, by
11
address of the invalid block to be freed • SVC dump (or system dump), taken to SYS1.DUMPxx
At offset 1EF in the SDWA, there is a VRACAN key command or SLIP trap exit.
Storage Manager invoker. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
00E2002B
Explanation
• Dynamic dump, taken to SYS1.DUMPxx data set, by This abend code is used to force percolation in the
Db2 (04E and 04F abends). case when an abend is encountered while in Storage
Manager code and the Storage Manager has been
called recursively.
executing IFCEREP1. Refer to the originating abend code.
00E2002A 00E2002E
The SMC Recovery Stack Management function Db2 detected an internal error during the freeing of
detected that the number of allowed entries in the data space storage.
SMC Recovery Stack has been exceeded, or the
structure has been incorrectly modified.

The requested function is not performed. A Db2 dump Diagnostic information is recorded in SYS1.LOGREC,
is requested. and a Db2 dump is requested.
Operator response
This is a Db2 internal error. If you suspect an error
in Db2, you might need to report the problem. • SVC dump (or system dump), taken to SYS1.DUMPxx
For information about identifying and reporting the data set, as result of an operator-initiated dump
problem, see Collecting diagnostic data (Collecting command or SLIP trap exit.
data). • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Problem determination 00E20030
and a Db2 dump is requested. Explanation
Collect the following diagnostic items: Db2 detected that the free chain in a 64-bit object
• Console output from the system on which the job might be damaged or might be unexpectedly fully
was run, and a listing of the SYSLOG data set for the allocated.
Db2 (04E and 04F abends). The requested function is not performed. A Db2 dump
• SVC dump (or system dump), taken to SYS1.DUMPxx is requested.
command or SLIP trap exit. Operator response
00E2002F System programmer response

Explanation
Db2 detected an internal error during the freeing of For information about identifying and reporting the
data space storage. problem, see Collecting diagnostic data (Collecting
data).
System action
The requested function is not performed. A Db2 dump
is requested. Diagnostic information is recorded in SYS1.LOGREC,
For information about identifying and reporting the • SVC dump (or system dump), taken to SYS1.DUMPxx
problem, see Collecting diagnostic data (Collecting data set, as result of an operator-initiated dump
data). command or SLIP trap exit.

executing IFCEREP1.
00E20031
Explanation
Db2 is unable to create a 64-bit object. in Db2, you might need to report the problem.
data).
The requested function is not performed. A Db2 dump
is requested.
Operator response Diagnostic information is recorded in SYS1.LOGREC,
00E20033
Explanation
in Db2, you might need to report the problem. The amount of combined real and auxiliary storage
For information about identifying and reporting the used by the Db2 address space has reached or
problem, see Collecting diagnostic data (Collecting exceeded the maximum amount allowed by the
data). value specified for the REALSTORAGE_MAX subsystem
parameter.
System action
and a Db2 dump is requested. The Db2 subsystem abnormally terminated with
reason code 00E20033. A dump and LOGREC entry
Collect the following diagnostic items: might have been issued and Db2 terminated with
• Console output from the system on which the job DSNV086E.
period of time that spans the failure. Operator response
• Dynamic dump, taken to SYS1.DUMPxx data set, by Notify the system programmer.
command or SLIP trap exit. If you suspect an error in Db2, you might need to
• Listing of SYS1.LOGREC data set, obtained by report the problem. For information about identifying
executing IFCEREP1. and reporting the problem, see Collecting diagnostic
00E20032
Explanation
Db2 detected an internal error while processing and a Db2 dump is requested.
storage. This abend reason code is issued by the
The value that you specified can be found the
CSECT indicated in the dump title.
REALSTORAGE_MAX subsystem parameter, and the
amount of the combined real and auxiliary storage
System action used is recorded in the dump.
The requested function is not performed. A Db2 dump Collect the following diagnostic items:
is requested.

The agent detecting the problem abends, and an SVC
• SVC dump (or system dump), taken to SYS1.DUMPxx dump is requested.
Operator response
and IFCID225 records.
Related concepts
Db2 subsystem storage requirements (Db2 Obtain a copy of SYS1.LOGREC and the SVC dump.
Installation and Migration) If you suspect an error in Db2, you might need to
Related tasks report the problem. For information about identifying
Calculating real storage requirements (Db2 and reporting the problem, see Collecting diagnostic
Installation and Migration) data (Collecting data).
Related reference 00E20042
REALSTORAGE_MAX in macro DSN6SPRM (Db2
Installation and Migration)
Explanation
Related information
DSNS001I (Db2 Messages) Additional 64-bit stack storage is needed but could not
be obtained.
00E20040 This code typically reflects an internal Db2 error.

Either the free or discard 64-bit stack queue has been Db2 terminates with this reason code.
corrupted.
This code typically reflects an internal Db2 error. Operator response
System action
Db2 terminates with this reason code. System programmer response
Operator response
Obtain a copy of SYS1.LOGREC and the SVC dump. 00E20043
An invalid head 64-bit stack segment was used for a
get or free stack request.
00E20041 This code typically reflects an internal Db2 error.

An invalid 64-bit stack segment has been freed. The invoker abends.
This code typically reflects an internal Db2 error.
Operator response


Reason code identifiers that begin with 00E3 communicate normal and error situations with the service
controller.
The BIND function is abended. All effects of the
Explanation BIND operation are rolled back. A record is written to
A service controller internal inconsistency has been SYS1.LOGREC, and an SVC dump is requested.
encountered. This is probably a Db2 subsystem error.
Operator response
A record is written to SYS1.LOGREC, and an SVC
dump is requested. The execution unit is abnormally System programmer response
terminated.
This is a Db2 internal error. Obtain a copy of
SYS1.LOGREC and the SVC dump. If you suspect an
Notify the system programmer. For information about identifying and reporting the
data).
This is a Db2 internal error. Obtain a copy of Problem determination
error in Db2, you might need to report the problem. The service controller code, using the data manager
For information about identifying and reporting the restore function, has detected an error while trying
problem, see Collecting diagnostic data (Collecting to undo the results of a BIND operation. The data
data). manager return and reason code encountered can be
found in the CTDMRETC and CTSIRCOD fields of the
cursor table pointed to by register 7 in the SDWA.
The service controller has detected an internal
inconsistency. The problem can be determined by • Console output from the system on which the job
analyzing the CSECT involved in the abend. was run, and a listing of the SYSLOG data set for the
• Console output from the system on which the job Db2 (04E and 04F abends).
Db2 (04E and 04F abends). 00E30004

00E30003 This abend is issued by the service controller
initialization module whenever an error return code
is received from a database services subcomponent
Explanation participating in the Db2 startup process. This abend
An error was returned from a data manager restore ensures that Db2 is terminated.
operation. This abend is issued to ensure that changes
made to the catalog by a failing BIND function are
backed out.

System action 8 (8)
Pointer to a structure containing a character string
The database services shutdown process is initiated SSCM followed by a 32-bit map representing the
after an SVC dump is requested, and a record is following information:
written to the SYS1.LOGREC data set. Db2 is abended.
Bit 0
1 if Db2 has successfully 'signed on' to IRLM
Operator response
10 (16)
Notify the system programmer. Error found upon return from the SCC startup
initialization process
System programmer response Bit 1
1 if the buffer manager subcomponent
initialization process is completed
SYS1.LOGREC and the SVC dump. .If you suspect an
error in Db2, you might need to report the problem. Bit 2
For information about identifying and reporting the 1 if the data manager subcomponent
problem, see Collecting diagnostic data (Collecting initialization process is completed
data). Bit 3
1 if the data space manager subcomponent
Problem determination initialization process is completed
Bit 4
A list of all database services subcomponents whose
Not used
initialization process has been completed may be
obtained from the SVC dump requested by this abend. Bit 5
Register 2 in the SDWA points to a structure that 1 if the RDS subcomponent initialization
contains the following diagnostic information: process is completed
0 (0) Bit 6
Module qualifier that identifies the area within Not applicable
DSNTSTRT at which the error was detected. The Bit 7
qualifier should be: 1 if the SCC initialization process is completed
A (10) Bit 8
Error found upon return from the SCC startup 1 if the LOB Manager initialization is completed
initialization process Bits 9 to 31
B (11) Not used
Error found upon return from the SCC IRLM
C (12)
identify process
Pointer to invoked subcomponent's RMFT.
C (12)
Error found upon return from the buffer From this information the appropriate subcomponent's
manager initialization process startup process may be identified.
D (13) Collect the following diagnostic items:

Error found upon return from the data manager • Console output from the system on which the job
initialization process was run, and a listing of the SYSLOG data set for the
E (14) period of time that spans the failure.
Error found upon return from the data space • Dynamic dump, taken to SYS1.DUMPxx data set, by
manager initialization process Db2 (04E and 04F abends).
F (15) • Listing of SYS1.LOGREC data set, obtained by
Error found upon return from the RDS executing IFCEREP1.
initialization process or LOB Manager
initialization process. Related tasks
2 (2)
Error return code from the invoked subcomponent
00E30005
4 (4)
Error reason code from the invoked subcomponent

A service task could not be created during the A service task could not be created during the
database services initialization process. This is database services delete process. This is probably a
probably a Db2 error. Db2 error.

A record is written to SYS1.LOGREC, and an SVC dump A record is written to SYS1.LOGREC, and an SVC dump
is requested. Db2 is abended. is requested. Db2 is abended.


This is possibly a Db2 internal error. Obtain a copy of This is possibly a Db2 internal error. Obtain a copy of
SYS1.LOGREC and the SVC dump. If you suspect an SYS1.LOGREC and the SVC dump. If you suspect an
error in Db2, you might need to report the problem. error in Db2, you might need to report the problem.
For information about identifying and reporting the For information about identifying and reporting the
problem, see Collecting diagnostic data (Collecting problem, see Collecting diagnostic data (Collecting
data). data).

Register 2 in the SDWA points to a structure that Register 2 in the SDWA points to a structure that
contains the following diagnostic information: contains the following diagnostic information:
0 (0) 0 (0)
Should equal X'3' Should equal X'3'
2 (2) 2 (2)
Return code from the service task creation Return code from the service task creation
function of the agent services manager (ASM) function of the agent services manager (ASM)
subcomponent subcomponent
4 (4) 4 (4)
Abend reason code from the service task creation Abend reason code from the service task creation
function of the agent services manager (ASM) function of the agent services manager (ASM)
subcomponent subcomponent
8 (8) 8 (8)
Not used Not used
C (12) C (12)
Not used Not used
00E30006 00E30008

Explanation problem, see Collecting diagnostic data (Collecting
data).
DSNTSTR2 loaded an incorrect version of the
system parameter CSECT DSN6SPRM while Db2 was
executing. Message DSNT103I is generated before the Problem determination
abend occurs. This error is detected when a module invokes the
macro DSNTSFRR to disconnect a functional recovery
System action element (FRE) from a functional recovery chain to
which it is not connected. The name of the module
Db2 is terminated. passing the invalid FRE is the module issuing the
abend.
Restart Db2 with a -START DB2 PARM= command, • Dynamic dump, taken to SYS1.DUMPxx data set, by
where the parameter block that follows the 'PARM=' Db2 (04E and 04F abends).
parameter specifies an MVS/XA version of the Db2 • Listing of SYS1.LOGREC data set, obtained by
subsystem parameters. executing IFCEREP1.
00E3000B
• Console output from the system on which the job The database services section (DSN6SPRM) in the Db2
was run, and a listing of the SYSLOG data set for the initialization parameter module (DSNZPARM) does not
period of time that spans the failure. exist.
executing IFCEREP1.
is requested. Db2 is abended.
• Listing of DSNZPARM module used.
00E3000A Operator response
Explanation
A bad recovery element was detected by the database System programmer response
services standard ESTAE and FRR recovery routines.
This is probably an installation error. Obtain a copy of
This is probably a Db2 subsystem error.
SYS1.LOGREC and the SVC dump.
System action
A record is written to SYS1.LOGREC, and an SVC dump and reporting the problem, see Collecting diagnostic
is requested. The execution unit is abended. data (Collecting data).

Notify the system programmer. Register 2 in the SDWA points to a structure that
contains the following diagnostic information:
System programmer response 0 (0)
Should equal X'1'

2 (2) • Dynamic dump, taken to SYS1.DUMPxx data set, by
Return code from the get descriptor function of the Db2 (04E and 04F abends).
system parameter manager (SPM) subcomponent • SVC dump (or system dump), taken to SYS1.DUMPxx
of Db2 data set, as result of an operator-initiated dump
4 (4) command or SLIP trap exit.
Not applicable • Listing of SYS1.LOGREC data set, obtained by
8 (8) executing IFCEREP1.
Not applicable
00E3000D
C (12)
Not applicable
Explanation
First, ensure that DSNZPARM was installed correctly.
Then, using the return code from SPM, determine why A failure occurred and was detected while an ESTAE
the descriptor is not available. functional recovery was being established.

System action
was run, and a listing of the SYSLOG data set for the The executing unit is abended. A record is written to
period of time that spans the failure. SYS1.LOGREC.

executing IFCEREP1.
• Listing of DSNZPARM module used. System programmer response
00E3000C Obtain a copy of SYS1.LOGREC, and determine the
cause of the problem from the information that
precedes this entry.
Explanation
A database services TCB service task that cannot be Problem determination
reinstated has been abnormally terminated. Entries
in SYS1.LOGREC that precede this entry indicate the Collect the following diagnostic items:
source of the error.
The executing unit is abended. A record is written to • Dynamic dump, taken to SYS1.DUMPxx data set, by
SYS1.LOGREC. Db2 (04E and 04F abends).
Operator response data set, as result of an operator-initiated dump
executing IFCEREP1.
00E3000E
Obtain a copy of SYS1.LOGREC, and determine the
cause of the problem from the information that
precedes this entry. Explanation
The execution unit supporting the database services
Problem determination checkpoint process has abended. The CSECT involved
in the abend writes a record to SYS1.LOGREC and
Collect the following diagnostic items: requests an SVC dump.
Db2 is abended. A record is written to SYS1.LOGREC.

Operator response 8 (8)
Not applicable
C (12)
Not applicable
The abend is generated whenever the Db2 load
Obtain a copy of SYS1.LOGREC, and determine the module DSNTFEPL is not link-edited with a load
cause of the problem from the information that module entry point name of DSNTF. To correct this,
precedes this entry. link-edit DSNTFEPL again with the correct entry point
name.
period of time that spans the failure. • Dynamic dump, taken to SYS1.DUMPxx data set, by
• Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (04E and 04F abends).
Db2 (04E and 04F abends). • SVC dump (or system dump), taken to SYS1.DUMPxx
• Listing of SYS1.LOGREC data set, obtained by data set, as result of an operator-initiated dump
00E3000F
executing IFCEREP1.
The database services functional recovery load

module, DSNTF, has an unrecognizable entry point.
Explanation
The database services initialization process could not
System action read the Db2 bootstrap data set (BSDS).

System action
Operator response is requested. Db2 is abended.

Operator response

Register 2 in the SDWA points to a structure that

0 (0) This error can usually be traced to a VSAM error
Should equal X'4' occurring while reading the BSDS. Before examining
the dump, examine the operator console log and
2 (2) SYSLOG to determine if VSAM has encountered any
Not applicable errors on the BSDS.
4 (4)
Not applicable

Register 2 in the SDWA points to a structure that Problem determination
0 (0)
Should equal X'2' • Console output from the system on which the job
2 (2)
Return code from a BSDS read request function of
the recovery log manager (RLM) subcomponent • Dynamic dump, taken to SYS1.DUMPxx data set, by
4 (4)
Abend reason code from a BSDS read request • SVC dump (or system dump), taken to SYS1.DUMPxx
function of the recovery log manager (RLM) data set, as result of an operator-initiated dump
subcomponent command or SLIP trap exit.
8 (8) • Listing of SYS1.LOGREC data set, obtained by
Not applicable executing IFCEREP1.
C (12) • Listing of DSNZPARM module used.
Not applicable 00E30014
was run, and a listing of the SYSLOG data set for the The value specified in the DSN6SYSP CSECT to define
period of time that spans the failure. reserve storage for a 'must complete' process is either
• Dynamic dump, taken to SYS1.DUMPxx data set, by negative or 0.
• SVC dump (or system dump), taken to SYS1.DUMPxx System action
command or SLIP trap exit. Db2 is terminated.

• Contents of the BSDS (both copies if dual BSDS Notify the system programmer.
00E30013 Reassemble DSN6SPRM and relink-edit the
DSNZPARM load module. This is done by resubmitting
Explanation the installation job stream, DSNTIJUZ, that built the
load module named in the -START DB2 command
The value specified in the DSN6SYSP CSECT to define 'PARM='
reserve storage is either negative or zero.
System action
Db2 is terminated.
Notify the system programmer. • Dynamic dump, taken to SYS1.DUMPxx data set, by
System programmer response • SVC dump (or system dump), taken to SYS1.DUMPxx
Reassemble DSN6SPRM and relink-edit the
DSNZPARM load module. This is done by resubmitting
the installation job stream, DSNTIJUZ, that built the • Listing of SYS1.LOGREC data set, obtained by
load module named in the -START DB2 command executing IFCEREP1.
'PARM=' parameter. • Listing of DSNZPARM module used.
00E30017

While loading the Db2 database services function Reassemble and link-edit a DSNHDECP or exit with the
recovery and emergency shutdown modules, the default name.
Service Controller function abends with this reason
00E3001E
code. This is because it detected a load module which
was loaded with an invalid addressing capability. The
abend is preceded by message DSNT107E. Explanation
A statement in the package could not be processed
System action successfully because it would require access to a
Db2 database services startup is terminated. remote location and the package was last bound with
DBPROTOCOL(PRIVATE).

System action
Refer to message DSNT107E.
The execution of the package section fails.
User response
Refer to message DSNT107E.
Rebind the plan or package with the
00E3001B DBPROTOCOL(DRDA) bind option.
Run the Private Protocol to DRDA Protocol Catalog
Explanation Analysis tool, DSNTP2DP to obtain a set of conversion
commands to convert packages in the system to use
A plan could not be executed because the system
DRDA protocol.
from which you are attempting to run is disabled or
unknown. The system type might be unknown if the Related tasks
attach library that you are using is from a previous Preparing your system for DRDA access (Db2
release of Db2 that does not support the ENABLE and Installation and Migration)
DISABLE options of the bind operation.
00E30021
System action
The plan is not allocated.
Explanation
A processing error has occurred during authorization
System programmer response checking.
Refer to the SYSIBM.SYSPLSYSTEM table to determine

the systems from which the plan can be executed, or
System action
correct the attach library. The request to allocate a plan to the authorization ID is
denied.
00E3001D

A DSNHDECP name, authorization exit name, signon
exit name or access control exit name other than
the default name is not supported in an environment System programmer response
executing early code from a prior release. If Db2
detects early code from a prior release and a
DSNHDECP or exit that is not the default name Db2
start-up will be terminated with this reason code.

Db2 start-up is abended with reason code 00E3001D.

period of time that spans the failure. A processing error has occurred during authorization
checking.
executing IFCEREP1.
System action
00E30034
The IRLM query request is denied.
Explanation
Operator response
The authorization ID associated with this connection is
not authorized to use the specified plan name or the Notify the system programmer.
specified plan name does not exist.
The request to allocate a plan to the authorization ID is report the problem. For information about identifying
denied. and reporting the problem, see Collecting diagnostic
User response
Verify that the correct plan name was specified. If the
plan exists, then authority to execute the plan must be Collect the following diagnostic items:
granted. • Console output from the system on which the job
00E30035 was run, and a listing of the SYSLOG data set for the

executing IFCEREP1.
A processing error has occurred during authorization
checking. 00E30037

The request to allocate a plan to the authorization ID is An internal logic error occurred while invoking a
denied. distributed transaction manager function.

Notify the system programmer. Db2 writes a SYS1.LOGREC record and requests a SVC
dump.

Operator response
report the problem. For information about identifying Collect the SYS1.LOGREC listing and the SVC dump.
Collect the following diagnostic items: and reporting the problem, see Collecting diagnostic
User response
executing IFCEREP1.
00E30036

period of time that spans the failure. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Db2 (04E and 04F abends). 00E30041
00E30040 An internal error occurred when trying to obtain a limit
from the resource limit specification table.
Explanation
System action
An internal logic error occurred while the catalog
access function was being invoked. A record is written to SYST1.LOGREC, and an SVC
dump is requested. The requested execution unit is
abended.
System action
The START RLIMIT command fails. The governing Operator response
status prior to issuing this command continues
unchanged. Notify the system programmer.

data (Collecting data). Collect the following diagnostic items:
At the time of the abend, the registers contain the
following information: • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Register
Contents 00E30063
0
Address of the catalog access package parameter Explanation
list
The BIND PACKAGE or CREATE PROCEDURE request
2 attempted to insert more than the maximum
Catalog access return code supported number of records for a single package into
3 the SYSIBM.SYSPACKSTMT catalog table. The number
Catalog access reason code of SYSPACKSTMT records for a single package cannot
exceed 2,147,483,647.
4
Data manager return code
5 System action
Data manager reason code The BIND PACKAGE subcommand or the CREATE
7 PROCEDURE SQL statement fails.
CT address

Break the application into smaller applications so that Notify the system programmer.
each packages requires fewer records.
Severity
8 (error) report the problem. For information about identifying
Related reference
Limits in Db2 for z/OS (Db2 SQL)
User response
00E30064 An invalid field in the DBRM was found while
Explanation: processing the BIND command. The DBRM might
Db2 detected that a resource was unavailable during be bad. Rebuild the DBRM and reissue the BIND
the automatic rebind process or when stopping command.
databases, table spaces, or index spaces.
The automatic rebind or the process of stopping the • Console output from the system on which the job
specified databases, table spaces, or index spaces was run, and a listing of the SYSLOG data set for the
fails. period of time that spans the failure.
Operator response data set, as result of an operator-initiated dump
executing IFCEREP1.
00E30066
The service controller's BIND processor has detected
an invalid release dependency mark in the cursor
User response table.
If the unavailable resource is detected during
an automatic rebind, issue an explicit REBIND System action
subcommand, which either resolves the problem or
The BIND command fails.
provides more details about the problem in the output.
Operator response
Severity
8 (error)
Explanation report the problem. For information about identifying
The service controller's BIND processor detected an and reporting the problem, see Collecting diagnostic
error in the user's database request module (DBRM) data (Collecting data).
while building the SYSDBRM record.
The BIND command fails.

• Console output from the system on which the job 00000104
was run, and a listing of the SYSLOG data set for the Subcommand information block (SIB).
period of time that spans the failure. 00000201
• SVC dump (or system dump), taken to SYS1.DUMPxx DBRM member name list.
data set, as result of an operator-initiated dump 00000202
command or SLIP trap exit. Plan-ID list.
• Listing of SYS1.LOGREC data set, obtained by 00000203
executing IFCEREP1. Message block in user storage. Other register
The service controller module DSNTBBP detected an contents are as follows:
unknown value in the CTRELDEP field of the BIND
R R
CT. The BIND CT is pointed to by GPR7 at the time
3 4
of the abend and is mapped by DSNDCT. The one
byte CTRELDEP field should have been set by the RDS < 4 Simple reference
BIND processor (DSNXEPR) or one of the functions it
• R8 = zero
invokes.
00E30067 > > MVCL
0 4
• R8 = From address
Explanation • R4 = move length
The BIND process program abended while attempting To and from lengths are equal.
to use a BIND parameter. This usually indicates that
the parameter list provided to the service controller 0 > GETMAIN for user storage failed
BIND function is invalid (such as invalid addresses or 4
• R4 = storage length required
incorrect key).
• R8 = GETM
System action To fix this problem, increase your region

size.
is requested. The BIND subcommand is terminated. < > FREEMAIN of user storage failed
0 4
• R4 = length of storage of free
System programmer response • R8 = address of storage to free
If you suspect an error in Db2, you might need to 00000204
report the problem. For information about identifying Message block in user storage. R8 = Message block
and reporting the problem, see Collecting diagnostic address.
data (Collecting data). Except as indicated above, the information in the other
registers is as follows:
User response R3
Notify the system programmer. Parameter address
R4
Problem determination Parameter length
R5
Register 2 contains an indication of the type of Parameter storage key
parameter as follows:
R8
00000101 Input parameter list address
Input parameter list.
00000205
00000102 Package-list name list.
Communication information block (CIB).
00000206
00000103 ENABLE/DISABLE system list.
Invalid BIND subcommand name. Registers 3 and
4 contain the invalid subcommand name. Collect the following diagnostic items:

period of time that spans the failure. A record is written to SYS1.LOGREC, and an SVC dump
Operator response
attachment facility) session involved in the problem. System programmer response
00E30068 This is an internal Db2 error. Obtain a copy of
A function invoked by a BIND subcommand has problem, see Collecting diagnostic data (Collecting
returned an unexpected error. data).

A record is written to SYS1.LOGREC, and an SVC dump The service controller code has detected an internal
is requested. The BIND subcommand is terminated. inconsistency. The problem can be determined by
analyzing the CSECT involved in the abend.
This is an internal Db2 error. Obtain a copy of • Console output from the system on which the job
SYS1.LOGREC and the SVC dump. If you suspect an was run, and a listing of the SYSLOG data set for the
error in Db2, you might need to report the problem. period of time that spans the failure.
data).
executing IFCEREP1.
User response
00E30070
Explanation
An attempt was made to use the Internal Resource
The service controller code has detected an internal Lock Manager (IRLM) facilities, but the IRLM was not
inconsistency. The problem can be determined by available. Either the IRLM had not been started by
analyzing the CSECT involved in the abend. the operator, or the IRLM has encountered a problem
Collect the following diagnostic items: causing it to terminate abnormally.
period of time that spans the failure. A record is written to SYS1.LOGREC, and an SVC
• Dynamic dump, taken to SYS1.DUMPxx data set, by dump is requested. The requesting execution unit is
Db2 (04E and 04F abends). abended.
00E30069 The IRLM should be started before the Db2 subsystem
is started. If this does not resolve the problem (that
Explanation is, if the IRLM actually was started before Db2 was
started) notify the system programmer.
An attempt to allocate a cursor table (CT) failed.

This is probably not a Db2 problem. Obtain a copy of Obtain a copy of SYS1.LOGREC and the SVC dump.
SYS1.LOGREC and the SVC dump. If you suspect an error in Db2, you might need to
data (Collecting data). If the error was caused by a previously unsuccessful
QUIT from the IRLM, manually stop IRLM. If IMS is
User response using the same IRLM, refer to the IMS documentation
to determine the effect of IRLM terminating while IMS
Notify the system programmer. is connected.
If you are running multiple versions of Db2, ensure
Problem determination that the SSNAME specified by the DSN6SPRM macro
If IRLM abended, and if you suspect an error in Db2, during the installation of the member DSNZPARM is
you might need to report the problem. For information not the same as the SSNAME in another version of
about identifying and reporting the problem, see Db2.
Collecting diagnostic data (Collecting data). Otherwise,
ensure that the IRLM is started before the -START DB2 Problem determination
command is issued.
A previously unsuccessful sign-off from the IRLM is
Collect the following diagnostic items: documented by an abend of X'00E30075' during the
previous termination of Db2.
was run, and a listing of the SYSLOG data set for the Collect the following diagnostic items:
• Dynamic dump, taken to SYS1.DUMPxx data set, by was run, and a listing of the SYSLOG data set for the
Db2 (04E and 04F abends). period of time that spans the failure.
• Listing of DSNZPARM module used. • SVC dump (or system dump), taken to SYS1.DUMPxx
• IRLM trace output. data set, as result of an operator-initiated dump
00E30071
executing IFCEREP1.
Explanation
• Listing of DSNZPARM module used.
Either Db2 terminated without successfully signing • IRLM trace output.
off from IRLM, or another subsystem with the same
SSNAME is still connected. This abend reason code 00E30072
accompanies message DSNT380I.
Explanation
System action An error was encountered during an IRLM lock query
A record is written to SYS1.LOGREC, and an SVC dump request.
System action
Operator response A record is written to SYS1.LOGREC, and an SVC dump
Determine if another Db2 subsystem is active. If is requested. The execution unit is terminated.
another subsystem is not active, and IMS is not sharing
the same IRLM, cancel IRLM prior to starting Db2. Operator response
Regardless, notify the system programmer.

System programmer response error in Db2, you might need to report the problem.
This is a Db2 internal error. Obtain a copy of problem, see Collecting diagnostic data (Collecting
SYS1.LOGREC and the SVC dump. If you suspect an data).
problem, see Collecting diagnostic data (Collecting Problem determination
data). The service controller (SC) subcomponent has
detected an internal inconsistency. The problem can
Problem determination be determined by analyzing the CSECT involved in the
abend.
At the time of the abend, the registers contains the
following information: Collect the following diagnostic items:
R2 • Console output from the system on which the job
Address of the lock request RLPL was run, and a listing of the SYSLOG data set for the
R4
Address of the IRLM query request RLPL • Dynamic dump, taken to SYS1.DUMPxx data set, by
R5
Address of the IRLM query RLQD • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
R7
CT address • IRLM trace output.
00E30074
period of time that spans the failure. A global out-of-storage condition was encountered by
• Dynamic dump, taken to SYS1.DUMPxx data set, by the Internal Resource Lock Manager (IRLM) during the
Db2 (04E and 04F abends). processing of a LOCK or UNLOCK request.

• IRLM trace output. A record is written to SYS1.LOGREC, and an SVC
dump is requested. The requesting execution unit is
Related concepts abended.
IRLM return and reason codes (IRLM messages
and codes)
Operator response

An unrecoverable system error occurred while This is probably not a Db2 problem. Obtain a copy of
processing a LOCK or UNLOCK request. SYS1.LOGREC and the SVC dump.
A record is written to SYS1.LOGREC, and an SVC dump and reporting the problem, see Collecting diagnostic
is requested. The requested execution unit is abended. data (Collecting data).

Notify the system programmer. The name of the module issuing the abend is recorded
in the SYS1.LOGREC entry. It is also recorded in the
SVC dump as the CSECT involved in the abend. A
System programmer response parameter in the IRLM procedure specifies the amount
This is a Db2 internal error. Obtain a copy of of the common service area (CSA) to be used by IRLM.
SYS1.LOGREC and the SVC dump. If you suspect an Take one of the following actions:

• Increase the CSA limit. • SVC dump (or system dump), taken to SYS1.DUMPxx
• Use a local IRLM (that is, an IRLM option that causes data set, as result of an operator-initiated dump
IRLM to operate from another address space). command or SLIP trap exit.
• Using IRLM lock tracing, determine what application • Listing of SYS1.LOGREC data set, obtained by
is acquiring so many locks that it causes the IRLM executing IFCEREP1.
CSA limit to be exceeded. • Listing of the IRLM procedure.
An attempt to sign-off from IRLM failed.
System action
executing IFCEREP1. A record is written to SYS1.LOGREC, and an SVC dump
00E30075
Operator response
Explanation
During the normal sign-off from IRLM or during
the abnormal shutdown of Db2, an AUTO-STOP of
IRLM using SVC 34 abnormally terminated. Message System programmer response
DSNT383I is issued. This is probably an internal Db2 error. Obtain a copy
of SYS1.LOGREC and the SVC dump. If you suspect an
A record is written to SYS1.LOGREC, and an SVC dump problem, see Collecting diagnostic data (Collecting
is requested. Db2 is abended. data).

Notify the system programmer. The service controller subcomponent has detected
an internal inconsistency. The problem can be
System programmer response determined by analyzing the CSECT involved in the
abend. This CSECT is found in both the SYS1.LOGREC
This is probably a Db2 internal error. Obtain a copy of and the SVC dump.
error in Db2, you might need to report the problem. The request parameter list (RLPL) used during
For information about identifying and reporting the the sign-off process resides in the IRLM interface
problem, see Collecting diagnostic data (Collecting manager's communication block (DSNTLMC) from
data). ACOM.
The name of the CSECT issuing the abend is found in was run, and a listing of the SYSLOG data set for the
both the SYS1.LOGREC and the SVC dump. Register 2 period of time that spans the failure.
contains the SVC return code. • Dynamic dump, taken to SYS1.DUMPxx data set, by
executing IFCEREP1.
period of time that spans the failure. 00E30077

A database command processor encountered an error Notify the system programmer.
when attempting to create a cursor block (CUB) on a
Db2 catalog table. System programmer response
This may be an internal Db2 error or an operator
System action
procedure problem. Obtain a copy of SYS1.LOGREC
An error was detected during the generation of and the SVC dump. If you suspect an error in Db2,
messages to satisfy a DATABASE command. A you might need to report the problem. For information
DSNT305I message appears on the console of the about identifying and reporting the problem, see
requester, with the RC parameter of 12 and a REASON Collecting diagnostic data (Collecting data).
parameter of X'00E30089'.
Operator response
In the SVC dump, register 2 contains the return code
Notify the system programmer. and register 3 contains the reason code from the
identify function to the IRLM. Examine the reason
System programmer response code in register 3, either from the dump or system
console log. A reason code of X'4004' indicates
This is probably an internal Db2 error. Obtain a copy that the identify function code (51, X'33') does not
of SYS1.LOGREC and the SVC dump. If you suspect an exist in the IRLM SSVT. This may be due to the
error in Db2, you might need to report the problem. operator issuing a stop IRLM command followed by
For information about identifying and reporting the a start Db2 command before the IRLM has completed
problem, see Collecting diagnostic data (Collecting termination processing. The sequence of commands
data). can be determined from the system console log.
A reason code of X'4008' indicates that the IRLM
Problem determination is unavailable, that is, IRLM is not started and
Diagnostic information may be found in the Display the autostart is not requested by parameters in
Command Communication Area, whose address is DSNZPARM.
found in register 8, and by the Display Command Collect the following diagnostic items:
subcode in register 2.
IRLM called the service controller IRLM interface
status exit with register 0 equal to 1 in order to • Listing of SYS1.LOGREC data set, obtained by
notify Db2 that IRLM is terminating. This is not a Db2 executing IFCEREP1.
subsystem error. .
00E3007A
System action
Db2 is abended when IRLM is terminated before Db2 Explanation
is terminated. An entry is written to SYS1.LOGREC.
Db2 encountered an IRLM request error indicating that
00E30079 IRLM is not available to take requests.

An error was encountered on return from the Internal Db2 terminates because it cannot complete an IRLM
Resource Lock Manager (IRLM) IDENTIFY function. request.

A record is written to SYS1.LOGREC, and an SVC dump Notify the system programmer.

Look for the IRLM error code or messages to find out An attempt was made to start the Internal Resource
why IRLM is not available to take the Db2 request. Lock Manager (IRLM) using the MGCR (SVC 34), and a
Most likely, IRLM is terminating at the same time. nonzero return code was returned.
report the problem. For information about identifying System action

Refer to the IRLM problem determination process. Notify the system programmer.
was run, and a listing of the SYSLOG data set for the Examine the SVC return code to determine whether
period of time that spans the failure. this is a system problem or a Db2 internal problem.
executing IFCEREP1. If you suspect an error in Db2, you might need to
00E3007B
Explanation
An IRLM operation returned a non-zero return code. Problem determination
Register 2 contains the SVC return code.
System action
is requested. The application abnormally terminates.
Notify the system programmer. Db2 (04E and 04F abends).
Check whether system activities at the time of the • Listing of the IRLM procedure.
abend caused unexpected results from the IRLM 00E30081
operation. Check the system for any IRLM-related
problems that can cause the operation to fail. If
necessary, obtain a copy of SYS1.LOGREC, the SVC Explanation
dump, and lock traces at the time of the abend. If An attempt was made to start the Internal Resource
you suspect an error in Db2, you might need to report Lock Manager (IRLM). IRLM did not come up in the
the problem. For information about identifying and time limit specified to Db2.
(Collecting data).
System action
Problem determination A record is written to SYS1.LOGREC, and an SVC dump
Check the system for any unusual IRLM activities or
messages at the time of the abend.
Operator response
00E30080

If you need to increase the IRLM startup time setting, period of time that spans the failure.
contact IBM Support for guidance.
• Console output from the system on which the job 00E30083
Explanation
Db2 (04E and 04F abends). This agent has been selected as the victim of a
deadlock or timeout.
executing IFCEREP1. This reason code is not used in abends.
• Listing of DSNZPARM module used. 00E30084
00E30082 Explanation
Message DSNT305I appears on the console of the
Explanation requester with RC=8 and REASON=E'00E30084'. This
message tells the requester that an error was detected
IRLM discovered a bad request parameter list (RLPL). while building the database command display. Other
This may occur if the RLPL storage is overlaid while an entries in the SYS1.LOGREC help to identify the source
agent is suspended. of the error.

The execution unit is abended. This is a Db2 subsystem error. No SVC dump is
requested because a previous dump of the failing
Operator response subcomponent is expected.

Operator response

SYS1.LOGREC and the SVC dump. If you suspect an System programmer response
error in Db2, you might need to report the problem. Obtain a copy of SYS1.LOGREC and the SVC dump.
For information about identifying and reporting the If you suspect an error in Db2, you might need to
problem, see Collecting diagnostic data (Collecting report the problem. For information about identifying
data). and reporting the problem, see Collecting diagnostic
Problem determination 00E30085
An IRLM request was made that IRLM could not honor
immediately. IRLM called DSNTLSUS to suspend the Explanation
request. While waiting, the request parameter list
(RLPL) was changed and is no longer valid. Someone An error was indicated by the RDS Authorization
may be reusing the RLPL, or the storage may have function. This is an internal Db2 error.
been overlaid.
Register 2 contains a pointer to the RLPL. System action
A record is written to SYS1.LOGREC, and an SVC
Problem determination dump is requested. The command is abended after
displaying a DSNT305I message with an RC parameter
Collect the following diagnostic items: of 12 and a REASON parameter of X'00E30089'.

Operator response entries in the SYS1.LOGREC identify the source of the
error.
System action
A DSNT305I message appears on the console of the
This is an internal Db2 error. Obtain a copy of requester, with an RC parameter of 12 and a REASON
SYS1.LOGREC and the SVC dump. If you suspect an parameter of X'00E30089'. This is probably a Db2
error in Db2, you might need to report the problem. subsystem error. No SVC dump is requested because a
For information about identifying and reporting the prior dump of the failing subcomponent is expected.
data).
Operator response
The error return code address of the Display Command

Communication Area is found in register 8. System programmer response
00E30086 See the SYS1.LOGREC for prior failure.
00E30090
Explanation
An error was indicated by the data manager (DM) Explanation
subcomponent. This is probably an internal Db2 error. A service controller internal inconsistency has been
encountered during message generation.
System action
A record is written to SYS1.LOGREC, and an SVC System action
dump is requested. The command is abended after A record is written to SYS1.LOGREC, and an SVC dump
displaying a DSNT305I message with an RC parameter is requested. The execution unit is abended.
of 12 and a REASON parameter of X'00E30089'.
Operator response
Operator response
This is probably an internal error. Obtain a copy of report the problem. For information about identifying
SYS1.LOGREC and the SVC dump. If you suspect an and reporting the problem, see Collecting diagnostic
error in Db2, you might need to report the problem. data (Collecting data).
data). Problem determination
At the time of the abend, register 2 contains the
Problem determination message number that was to be generated.
The error return code of the data manager may be Collect the following diagnostic items:
found in the cursor table (CT), the address of which is • Console output from the system on which the job
found in register 7. was run, and a listing of the SYSLOG data set for the
00E30089 period of time that spans the failure.
This code is used in the REASON parameter of the 00E30091

DSNT305I database command message to inform
the requester that the execution unit supporting the
database command processor has terminated. Other

A failure was detected during the retry process of Db2
recovery.
System action The service controller recovery module has detected
an internal inconsistency. The problem can be
Db2 is abended after a record is written to determined by analyzing the CSECT involved in the
SYS1.LOGREC and an SVC dump is requested. abend. The name of this CSECT is found in both the
Notify the system programmer. • Dynamic dump, taken to SYS1.DUMPxx data set, by
System programmer response • SVC dump (or system dump), taken to SYS1.DUMPxx
This is probably an internal Db2 error. Obtain a copy of data set, as result of an operator-initiated dump
SYS1.LOGREC and the an SVC dump. If you suspect an command or SLIP trap exit.
data). 00E30095

This abend is issued by DSNTFRCV of the service Db2 is unable to acquire a modify lock because of
controller (SC) subcomponent. an incompatible retained lock held by one or more
other Db2 subsystems in the Db2 data sharing group.
Collect the following diagnostic items: Retained locks are locks that persist across Db2
• Console output from the system on which the job abnormal terminations.
• Dynamic dump, taken to SYS1.DUMPxx data set, by SQLCODE -904 is returned to the user. This reason
Db2 (04E and 04F abends). code and the resource name are also returned.
00E30092 Use the DISPLAY DATABASE command to display
the Db2 member names owning the retained locks.
Explanation You must restart those subsystems to remove the
'resource unavailable' condition.
A retry recovery failure has been detected. This is a
critical error. Problem determination:
00E30096
System action
Db2 is abended. This is probably a Db2 subsystem Explanation
error. Db2 is unable to acquire a modify lock. Lock
negotiation failed because this request was involved
Operator response in lock negotiation with other Db2 subsystems and the
request was denied.
System action
A 'resource unavailable' condition is returned to the
Obtain a copy of the SYS1.LOGREC and the SVC dump. user. This reason code, the resource type, and the
If you suspect an error in Db2, you might need to resource name are also returned.

Determine why the lock request failed. One possible A conversion error occurred during Db2 startup. This
cause of the lock request failure is if another Db2 conversion is used to determine if conversion services
subsystem in the Db2 data sharing group is abnormally are set up correctly.
terminating.
System action
User response
Db2 terminates.
Resubmit the request.
User response
See message DSNT552I to resolve the problem.
report the problem. For information about identifying 00E3009A
00E30097 During Db2 startup, Db2 detected a difference
between the CCSIDs recorded in the BSDS and the
CCSIDs specified by the version of DSNHDECP module
Explanation
or user-supplied application defaults module that that
Db2 encountered an IRLM error indicating that IRLM was loaded during startup. Db2 startup terminated
detected an 'out of record list' storage condition. to avoid potential data corruption issues. Message
DSNT108I is generated before the abend occurs.
The record list is a part of the coupling facility lock
structured that contains the 'modify locks' (those locks
that would be retained in case of a failure). System action
Subsystem startup is terminated.
System action
DSNT500I or SQLCODE -904 is returned to the user. Operator response
This reason code and the resource name are also
See message DSNT108I.
returned.

Operator response
Determine the reason for the termination of Db2
startup. See message DSNT108I.

The coupling facility lock structure is declared too
small. If this condition becomes a prevalent problem,
you need to redistribute the coupling facility lock 00E3009B
structure storage resource to make more room for the
record list. You can make room for the record list in on
Explanation
of two ways:
Db2 detected an invalid CCSID specification during
• Issue a rebuild.
startup. Db2 startup has terminated to avoid
• Dynamically change the lock structure size. potential data corruption issues. Message DSNT109I
Refer to Db2 Data Sharing: Planning and is generated before the abend occurs.
Administration for more details about these options.
System action
00E30099
Subsystem startup is terminated.
Operator response

Determine the reason for the termination of Db2 period of time that spans the failure.
startup. See message DSNT109I.
See message DSNT109I. executing IFCEREP1.
00E3009E 00E30101
The plan depends on new facilities of the release from The result of issuing a SETFRR macro indicates that
which fall back has occurred. this FRR is not the top FRR.

The allocation for the user failed. A record is written to SYS1.LOGREC. An SVC dump is
requested.
Warn the user community NOT to run this plan until
you have remigrated to the newer release. This is probably a Db2 internal error. Obtain a copy of
User response error in Db2, you might need to report the problem.
Do not use this plan until your Db2 subsystem is problem, see Collecting diagnostic data (Collecting
remigrated to the newer release. data).
00E30100
This reason code can be returned in the following • Dynamic dump, taken to SYS1.DUMPxx data set, by
cases: Db2 (04E and 04F abends).
• A parallel task running on a Db2 terminates • Listing of SYS1.LOGREC data set, obtained by
abnormally. executing IFCEREP1.
• An assisting Db2 terminates abnormally. 00E30104

The member name where the failure occurred is This reason code is used by the service controller (SC)
returned to the application as the resource name in subcomponent to respond NO on a prepare-to-commit
SQLCODE -904. In a non-data-sharing environment, notification.
the member name is blank, and the failure occurs on
the local Db2.
System action
Operator response If the service controller indicates that Db2 cannot
commit to perform the work requested by the
Enter DISPLAY GROUP from an active Db2 to see application since the last commit point, it responds
if a Db2 subsystem is down. Restart the failed Db2 NO on the prepare-to-commit notification (COMMIT1).
subsystem. This forces the commit to be changed to an abort,
causing the work performed by the application since
Problem determination the last commit point to be backed out.

IRLM was informed of a link failure to a coupling
facility that contains a lock table being actively used Explanation
by this data sharing group. You have attempted to execute a package that does
not exist. This reason code is used by the automatic
System action package BIND function to indicate that no record
exists in SYSIBM.SYSPACKAGE for the package-ID you
The Db2 subsystem is terminated with this reason are attempting to run, so package allocation fails.
code.
System action
Package allocation fails.
See IRLM message DXRxxxE to determine the root
cause of the failure and the appropriate corrective
action. User response
Problem determination: Determine if the object name was correctly specified.
If so, ensure that the package exists (by selecting from
00E30301 SYSIBM.SYSPACKAGE).
00E30305
Explanation
You have attempted to execute a plan that does not Explanation
exist. This reason code is used by the automatic
BIND function to indicate that no record exists in This reason code is used by the automatic bind
SYSIBM.SYSPLAN for the plan-ID you are attempting function to indicate that the package that is currently
to run, so plan allocation fails. being allocated is not operational.
If a package becomes invalid, the VALID column in
System action the SYSIBM.SYSPACKAGE table is set to a value other
than Y. The next time that the package is allocated,
The plan is not executed.
automatic rebinding is triggered.
If the automatic rebind succeeds, the package
User response
becomes valid again. (The value in the VALID column
Determine if the object name was correctly specified. is changed to 'Y'.) If the automatic rebind fails,
If so, ensure that the plan exists (by selecting from the package remains invalid and might become
SYSIBM.SYSPLAN). inoperative. (The value in the VALID column stays
the same and the value of the OPERATIVE column is
00E30302
changed to 'N'.) The allocation fails, and this code is
issued.
Explanation
This reason code is used by the automatic BIND System action
function to indicate that the plan currently being
Agent allocation fails or DROP package fails.
allocated is not operational. The automatic BIND for
the plan failed because the plan was dependent on
something that was altered or dropped. An unavailable System programmer response
database might also cause this problem. Determine what made the package not operational,
and issue a REBIND subcommand for the package.
System action Related concepts
The autobind fails, and the plan cannot be allocated. Changes that invalidate packages (Db2
System programmer response Automatic rebinds (Db2 Application
Determine what made the plan not operational. Make
Related reference
sure the required database is available. Issue a
REBIND subcommand for the plan. Invalid and inoperative packages (Managing
Security)

SYSPACKAGE catalog table (Db2 SQL) Explanation
This subcode is found in register 2 to clarify abend
00E30306 reason code X'00E30077'. See X'00E30077' for more
information.
This reason code is returned when the automatic bind

for plan is disabled. The automatic bind is disabled Explanation
through the installation process. This subcode is found in register 2 to clarify abend
reason code X'00E30077'. See X'00E30077' for more
System action information.
The plan is not automatically bound. 00E30501

Rebind the plan prior to execution. A warning occurred because the length of time that a
thread was idle exceeded the warning setting for the
00E30307 MONITOR IDLE THREADS keyword in a monitor profile
for one of the following filtering scopes:
Explanation • LOCATION
This reason code is used by the REBIND PACKAGE • PRDID
process to indicate that the REBIND command cannot
• ROLE_AUTHID
be phased in. The maximum number of copies for the
package has been reached. • ROLE
• AUTHID
System action • COLLID_PKGNAME
An error indication is returned. • COLLID
• PKGNAME
System programmer response • CLIENT_APPLNAME
The unavailable resource name has the thread token • CLIENT_USERID
of the long running thread which prevents phased-out • CLIENT_WRKSTNNAME
copies of the package from being deleted. Quiesce
the thread that executes the phased-out copy of the The server thread was holding Db2 resources and the
package, then try the REBIND command again. requesting application did not make a request to the
Db2 server thread for an extended period of time.
00E30402
System action
Explanation
A warning alert is issued, but the processing continues
This subcode is found in register 2 to clarify abend normally.
information. Db2 issues message DSNT771I.
00E30405
Operator response
This subcode is found in register 2 to clarify abend

information. Review the information provided in message
DSNT771I. Determine why the requesting application
00E30406
did not make a request to the Db2 server in the
specified time.
If the application requires additional time:

1. Modify the MONITOR IDLE • If the ATTRIBUTE1 value is EXCEPTION_ROLLBACK,
THREADS warning threshold in the the server thread is aborted. The connection with the
SYSIBM.DSN_PROFILE_ATTRIBUTES table. remote application is maintained.
2. Issue the START PROFILE command to refresh the If the aborted transaction performed database
warning threshold value. updates, the application environment is placed in a
Related tasks must-abort state so that the application environment
is made aware of the resources that have been
Monitoring idle threads by using profile tables
destroyed as a result of the aborted threads.
Monitoring and controlling Db2 by using profile Important: If either of the following situations are
tables (Db2 Administration Guide) true, Db2 hides the EXCEPTION_ROLLBACK event
Related reference from the remote application environment:
DSN_PROFILE_ATTRIBUTES profile table (Db2 – The aborted transaction performed only read-only
Performance) operations.
Related information – The transaction committed or aborted, but the
DSNT771I (Db2 Messages) associated database access thread remained
active before it became idle.
00E30502
Because the EXCEPTION_ROLLBACK event is not
visible to the remote application environment
Explanation in those cases, it might appear to the
A thread was canceled because the length of time that remote application environment that the database
a thread was idle exceeded the exception setting for resources are unexpectedly disappearing. For
the MONITOR IDLE THREADS keyword in a monitor example, held cursors, kept dynamic statements,
profile for one of the following filtering scopes: and declared temporary tables that were
created in the transaction are destroyed.
• LOCATION Use EXCEPTION_ROLLBACK only if the remote
• PRDID application environment can account for this
apparent loss of database resources.
• ROLE_AUTHID
• ROLE
Operator response
• AUTHID
• COLLID_PKGNAME
• COLLID
• PKGNAME
Review the information provided in message
• CLIENT_APPLNAME DSNT772I. Determine why the requesting application
• CLIENT_USERID did not make a request to the Db2 server in the
• CLIENT_WRKSTNNAME specified time.
The server thread was holding Db2 resources and the This condition typically occurs for one of the following
requesting application did not make a request to the reasons:
Db2 server thread for an extended period of time. • The ACTIVE thread option was specified in the DDF
THREADS field of the DSNTIPR installation panel,
System action and a requester application or its user did not make
a request to the Db2 server for an extended period
Db2 issues message DSNT772I. (such as a lengthy user absence). As a result, the
The subsequent system action depends on server thread becomes susceptible to cancellation
the ATTRIBUTE1 column value in the because of the timeout value.
SYSIBM.DSN_PROFILE_ATTRIBUTES table: Action: Determine why the requesting application
• If the ATTRIBUTE1 value is EXCEPTION, did not make a request to the Db2 server in the
Db2 abnormally terminates the execution unit, specified time.
terminates the server thread to release resources • The INACTIVE thread option was specified in the
that might affect other threads, and terminates the DDF THREADS field of the DSNTIPR installation
connection with the remote application. panel, and a requester application or its user failed

to commit before an extended dormant period Determine if there are sufficient connections allowed
(such as user absence). It is also possible that, for the LOCATION filtering scope. If additional
despite committing before an extended dormant connections are required:
period, database resources are still held because
1. Increase the MONITOR CONNECTIONS
of other existing conditions. As a result, the server
warning threshold value in the
thread cannot be moved to the inactive state and
SYSIBM.DSN_PROFILE_ATTRIBUTES table.
becomes susceptible to being canceled because of
the timeout value. 2. Issue the START PROFILE command to refresh the
warning threshold value.
Action: Determine why the server thread was not
moved to the inactive state. Related tasks
Monitoring remote connections by using profile
If the application requires additional time:
tables (Db2 Administration Guide)
1. Modify the MONITOR IDLE Monitoring and controlling Db2 by using profile
THREADS exception threshold in the tables (Db2 Administration Guide)
SYSIBM.DSN_PROFILE_ATTRIBUTES table. Related reference
2. Issue the START PROFILE command to refresh the DSN_PROFILE_ATTRIBUTES profile table (Db2
exception threshold value. Performance)
Related tasks Related information
Monitoring idle threads by using profile tables DSNT772I (Db2 Messages)
Monitoring and controlling Db2 by using profile 00E30504
DSNTIPR: Distributed data facility panel 1 (Db2 A connection to the database server could not be
Installation and Migration) made because the number of connections exceeded
DSN_PROFILE_ATTRIBUTES profile table (Db2 the exception setting for the MONITOR CONNECTIONS
Performance) keyword in a monitor profile for the LOCATION filtering
Related information scope.
System action
00E30503
The connection is not made. Db2 issues message
DSNT772I.
Explanation
A warning occurred because the number of Operator response
connections exceeded the warning setting for the
MONITOR CONNECTIONS keyword in a monitor profile Notify the system programmer.
for the LOCATION filtering scope.
System action Review the information provided in message
Processing continues. DSNT772I.
Db2 issues message DSNT772I. Determine if there are sufficient connections allowed
for the LOCATION filtering scope. If additional
connections are required:
Operator response
1. Increase the MONITOR CONNECTIONS
Notify the system programmer. exception threshold value in the
System programmer response 2. Issue the START PROFILE command to refresh the
Review the information provided in message exception threshold value.
DSNT772I.
Application programmer response
Retry the connection request.

Related tasks 2. Issue the START PROFILE command to refresh the
Monitoring remote connections by using profile warning threshold value.
tables (Db2 Administration Guide) Related tasks
Monitoring and controlling Db2 by using profile Monitoring threads by using profile tables (Db2
tables (Db2 Administration Guide) Administration Guide)
Related reference Monitoring and controlling Db2 by using profile
DSN_PROFILE_ATTRIBUTES profile table (Db2 tables (Db2 Administration Guide)
Performance) Related reference
Related information DSN_PROFILE_ATTRIBUTES profile table (Db2
DSNT772I (Db2 Messages) Performance)
Related information
00E30505
A warning occurred because the number of concurrent
active threads exceeded the warning setting for the Explanation
MONITOR THREADS keyword in a monitor profile for
Db2 was unable to service the connection request
one of the following filtering scopes:
because the number of concurrent active threads
• LOCATION exceeded the exception threshold for the MONITOR
• PRDID THREADS keyword in a monitor profile for the
LOCATION filtering scope.
• ROLE_AUTHID
• ROLE System action
• AUTHID
When the MONITOR THREADS exception threshold
• COLLID_PKGNAME value is set to zero, the connection is terminated.
• COLLID
Otherwise, the connection remains active and the
• PKGNAME thread is queued until other threads deallocate or
• CLIENT_APPLNAME go inactive, providing an available slot. The thread
resumes when a slot becomes available and the
• CLIENT_USERID
number of the concurrent active threads goes below
• CLIENT_WRKSTNNAME the profile exception threshold, unless another thread
is next in the queue.
System action In both cases, Db2 issues message DSNT772I.
Db2 issues message DSNT772I.
Operator response
Operator response
System programmer response DSNT772I.
Review the information provided in message Determine if there are sufficient threads allowed for
DSNT772I. the LOCATION filtering scope. If additional threads are
required:
Determine if there are sufficient thread allowed for the
applicable filtering scopes. If additional connections 1. Increase the MONITOR THREADS
are required: exception threshold value in the
1. Increase the MONITOR THREADS
2. Issue the START PROFILE command to refresh the
exception threshold value.

Application programmer response System programmer response
If the connection is terminated, retry the connection Review the information provided in message
request. DSNT772I.
Related tasks Determine if there are sufficient threads allowed for
Monitoring idle threads by using profile tables the applicable filtering scope or scopes. If additional
(Db2 Administration Guide) threads are required:
Monitoring and controlling Db2 by using profile 1. Increase the MONITOR THREADS
tables (Db2 Administration Guide) exception threshold value in the
Related reference SYSIBM.DSN_PROFILE_ATTRIBUTES table.
DSN_PROFILE_ATTRIBUTES profile table (Db2 2. Issue the START PROFILE command to refresh the
Performance) exception threshold value.
Related information
DSNT772I (Db2 Messages) Application programmer response
00E30507 If the connection is terminated, review the information
provided in SQLCODE -30041. Retry the connection
request.
Explanation
Related tasks
The connection could not access Db2 because the
Monitoring threads by using profile tables (Db2
number of concurrent active threads exceeded the
exception threshold for the MONITOR THREADS Administration Guide)
keyword in a monitor profile for one of the following Monitoring and controlling Db2 by using profile
filtering scopes. tables (Db2 Administration Guide)
Related reference
• PRDID
• ROLE Performance)
• AUTHID Related information
• ROLE_AUTHID DSNT772I (Db2 Messages)
• LOCATION -30041
EXECUTION FAILED DUE TO UNAVAILABLE
RESOURCES THAT WILL AFFECT THE
System action SUCCESSFUL EXECUTION OF SUBSEQUENT
When the MONITOR THREADS exception threshold COMMANDS AND SQL STATEMENTS. REASON
value is set to zero, the connection is terminated. reason-code TYPE OF RESOURCE resource-type
RESOURCE NAME resource-name PRODUCT ID
Otherwise, the connection remains active and the product-identifier RDBNAME rdbname
thread is queued until other threads deallocate or
go inactive, providing an available slot. The thread 00E30508
number of the concurrent active threads goes below
the profile exception threshold, unless another thread Explanation
is next in the queue. Db2 queues and suspends the Db2 was unable to process the SQL statement
number of the concurrent active threads up to the because the number of concurrent active threads
profile exception threshold. Once it is exceeded, Db2 exceeded the exception threshold for the MONITOR
rejects the connection request and returns SQLCODE THREADS keyword in a monitor profile for one of the
-30041. following filtering scopes.
In both cases, Db2 issues message DSNT772I. • COLLID
• PKGNAME
Operator response • COLLID_PKGNAME
Notify the system programmer. • CLIENT_APPLNAME
• CLIENT_USERID
• CLIENT_WRKSTNNAME

System action reason-code TYPE OF RESOURCE resource-type
RESOURCE NAME resource-name PRODUCT ID
When the MONITOR THREADS exception threshold product-identifier RDBNAME rdbname
value is set to zero, the connection is terminated.
Otherwise, the connection remains active and the 00E30509
go inactive, providing an available slot. The thread Explanation
number of the concurrent active threads goes below A warning occurred because the number of
the profile exception threshold, unless another thread connections exceeded the warning setting for the
is next in the queue. Db2 queues and suspends the MONITOR ALL CONNECTIONS keyword in a monitor
number of the concurrent active threads up to the profile for the LOCATION filtering scope.
profile exception threshold. Once it is exceeded, Db2
rejects the connection request and returns SQLCODE System action
-30041.
In both cases, Db2 issues message DSNT772I.
Operator response
Operator response

DSNT772I. Review the information provided in message
DSNT772I.
Determine if there are sufficient threads allowed for
the applicable filtering scope or scopes. If additional Determine if there are sufficient connections allowed
threads are required: for the LOCATION filtering scope. If additional
1. Increase the MONITOR THREADS
exception threshold value in the 1. Increase the MONITOR ALL CONNECTONS
SYSIBM.DSN_PROFILE_ATTRIBUTES table. warning threshold value in the
exception threshold value. 2. Issue the START PROFILE command to refresh the
Application programmer response Related tasks

Monitoring idle threads by using profile tables
If the connection is terminated, review the information (Db2 Administration Guide)
provided in SQLCODE -30041. Retry the connection
Monitoring and controlling Db2 by using profile
request.
Monitoring idle threads by using profile tables DSN_PROFILE_ATTRIBUTES profile table (Db2
(Db2 Administration Guide) Performance)
Monitoring and controlling Db2 by using profile Related information
tables (Db2 Administration Guide) DSNT772I (Db2 Messages)
Related reference -30041
DSN_PROFILE_ATTRIBUTES profile table (Db2 EXECUTION FAILED DUE TO UNAVAILABLE
Performance) RESOURCES THAT WILL AFFECT THE
Related information SUCCESSFUL EXECUTION OF SUBSEQUENT
DSNT772I (Db2 Messages) COMMANDS AND SQL STATEMENTS. REASON
-30041 reason-code TYPE OF RESOURCE resource-type
EXECUTION FAILED DUE TO UNAVAILABLE RESOURCE NAME resource-name PRODUCT ID
RESOURCES THAT WILL AFFECT THE product-identifier RDBNAME rdbname
SUCCESSFUL EXECUTION OF SUBSEQUENT
00E3050A
COMMANDS AND SQL STATEMENTS. REASON

A connection to the database server could not Notify the system programmer.
be made because the number of connections
exceeded the exception setting for the MONITOR ALL System programmer response
CONNECTIONS keyword in a monitor profile for the
LOCATION filtering scope. Review the information provided in message
DSNT772I.
System action Determine if there are sufficient threads allowed for
the LOCATION filtering scope. If additional threads are
The connection is not made.
required:
1. Increase the MONITOR ALL THREADS
Operator response SYSIBM.DSN_PROFILE_ATTRIBUTES table.
Notify the system programmer. 2. Issue the START PROFILE command to refresh the
System programmer response Related tasks
Review the information provided in message Monitoring remote connections by using profile
DSNT772I. tables (Db2 Administration Guide)
Monitoring and controlling Db2 by using profile
Determine if there are sufficient connections allowed tables (Db2 Administration Guide)
for the LOCATION filtering scope. If additional
Related reference
1. Increase the MONITOR ALL CONNECTIONS Performance)
exception threshold value in the Related information
exception threshold value. 00E3050C
Related tasks
Monitoring remote connections by using profile Explanation
tables (Db2 Administration Guide) Db2 was unable to service the connection request
Monitoring and controlling Db2 by using profile because the number of concurrent active threads
tables (Db2 Administration Guide) exceeded the exception threshold for the MONITOR
Related reference ALL THREADS keyword in a monitor profile for the
DSN_PROFILE_ATTRIBUTES profile table (Db2 LOCATION filtering scope.
Performance)
Related information System action
When the MONITOR ALL THREADS exception
threshold value is set to zero, the connection is
00E3050B
terminated.
Explanation Otherwise, the connection remains active and the

A warning occurred because the number of concurrent go inactive, providing an available slot. The thread
active threads exceeded the warning setting for the resumes when a slot becomes available and the
MONITOR ALL THREADS keyword in a monitor profile number of the concurrent active threads goes below
for the LOCATION filtering scope the profile exception threshold, unless another thread
is next in the queue.
System action In both cases, Db2 issues message DSNT772I.
Operator response

System programmer response specification table that was used to derive the limit.
Determine why the limit was exceeded.
DSNT772I. Related information
-905
Determine if there are sufficient threads allowed for
UNSUCCESSFUL EXECUTION DUE TO
the LOCATION filtering scope. If additional threads are
RESOURCE LIMIT BEING EXCEEDED,
required:
RESOURCE NAME = resource-name LIMIT =
1. Increase the MONITOR ALL THREADS limit-amount1 CPU SECONDS (limit-amount2
exception threshold value in the SERVICE UNITS) DERIVED FROM limit-source
00E30701
exception threshold value.
Explanation
Related tasks
Monitoring remote connections by using profile A resource was unavailable because the parallel
tables (Db2 Administration Guide) group for a query was stopped, such as when a
Monitoring and controlling Db2 by using profile CLOSE CURSOR was issued before all parallel tasks
tables (Db2 Administration Guide) completed their work.
Related reference
DSN_PROFILE_ATTRIBUTES profile table (Db2 System action
Performance) The SQL statement is terminated with SQLCODE -904.
Related information
Related concepts
Parallel processing (Db2 Performance)
00E30700 Related information
-904
Explanation UNSUCCESSFUL EXECUTION CAUSED BY AN
A resource limit as determined from the active code, TYPE OF RESOURCE resource-type, AND
resource limit specification table has been exceeded. RESOURCE NAME resource-name
The SQL statement has been terminated with an
SQLCODE -905. 00E30800

The current SQL statement contains an SQLCODE An attempt was made to identify to an IRLM that does
-905. not support the level of function Db2 needs. Message
DSNT803I accompanies this abend reason code.
Operator response
System action
Message DSNT803I is issued to the console, and Db2
System programmer response terminates abnormally with this reason code. A record
is written to SYS1.LOGREC. No SVC dump is taken.
An SQL statement used too much resource space. If
you suspect an error in Db2, you might need to report
reporting the problem, see Collecting diagnostic data Ensure that the statement in your IRLM startup
(Collecting data). procedure is referencing the correct IRLM code
library and that IRLM is at the appropriate level of
User response maintenance
See the text for the SQLCODE -905. It will specify the 00E30802
resource limit that was exceeded. The SQLCODE -905
text will also include the name of the resource limit

Db2 was not able to identify to IRLM because another If you suspect an error in Db2, you might need to
subsystem already identified to IRLM. Message report the problem. For information about identifying
DSNT811E accompanies this abend reason code. and reporting the problem, see Collecting diagnostic
System action 00E30806
Message DSNT811E is issued to the console. Db2
terminates abnormally with this reason code. A record Explanation
is written to SYS1.LOGREC. No SVC dump is taken.
IRLM could not successfully join its IRLM data sharing
group. Message DSNT800I accompanies this abend
System programmer response reason code.
IRLM Version 2.1 enforces a one to one (1:1) mapping
between IRLM and Db2. Multiple DBMS subsystems System action
can no longer use the same IRLM. Ensure that:
Message DSNT800I is issued to the console, and Db2
• Each Db2 subsystem is associated with its own IRLM abnormally terminates with this reason code. A record
subsystem. is written to SYS1.LOGREC. No SVC dump is taken.
• The correct IRLM procedure name and subsystem
name are specified in the Db2 system parameters. System programmer response
Problem determination: Some possible reasons why IRLM could not join its
00E30803 data sharing group are:
• The lock structure is not properly defined in the
Explanation active MVS CFRM administrative policy. The lock
structure name is a concatenation of the Db2
An error occurred in one of the Db2-supplied exits to data sharing group name and the string 'LOCK1',
IRLM. This abend reason code is issued only in a Db2 separated by an underscore (_). For example, if
sharing data environment and indicates an internal the Db2 data sharing group name is DSNCAT,
error in Db2 or IRLM. DSNCAT_LOCK1 would be the lock structure name.
Ensure that the lock structure is properly defined in
System action the active MVS CFRM policy. The name of the lock
A record is written to SYS1.LOGREC and an SVC dump structure that IRLM attempted to access is given in
is initiated. Db2 terminates abnormally. message DSNT800I. IRLM issues message DXR138E
to indicate that the lock structure definition could
not be accessed in the active MVS CFRM policy.
• IRLM could not connect the lock structure. The
If you suspect an error in Db2, you might need to reason for the connect failure is given in IRLM
report the problem. For information about identifying message DXR135E.
• IRLM could not join its data sharing group. The
reason for the join failure is given in IRLM message
00E30805 DXR134E.
• IRLM joined the wrong group. The set of IRLMs that
Explanation are connected to a given lock structure must all be
members of the same group.
Db2 could not activate one of the exits used with IRLM
for data sharing. This is a Db2 internal error. Ensure that the GROUP parameter is correctly
specified in the IRLM startup procedure. If you
give an incorrect group name, IRLM connects the
System action lock structure, and then times out waiting for
A record is written to SYS1.LOGREC and an SVC dump responses from other connectors. IRLM issues
is initiated. Db2 terminates abnormally. message DXR133I for the timeout.
00E30807

Db2 failed on the IRLM Identify request because The IRLM return and reason codes are in the
no lock structure name was specified. Message SYS1.LOGREC record.
DSNT810E accompanies this abend reason code.
Message DSNT810E is issued to the console, and Db2

Explanation
terminates abnormally with this reason code. A record
is written to SYS1.LOGREC. No SVC dump is taken. Db2 failed on the IRLM Identify request because IRLM
did not return the lock structure version ID. Message
System programmer response DSNT809I accompanies this abend reason code.
This condition occurs if you are not running Db2 in

System action
data sharing mode, but the associated IRLM is running
with global scope (SCOPE=GLOBAL in the IRLM startup Message DSNT809I is issued to the console, and Db2
procedure). If you are not running Db2 in data abnormally terminates with this reason code. A record
sharing mode, ensure that the associated IRLM startup is written to SYS1.LOGREC. No SVC dump is taken.
procedure specifies SCOPE=LOCAL. Conversely, if
you are running Db2 in data sharing mode, ensure System programmer response
that the associated IRLM startup procedure specifies
SCOPE=GLOBAL. This condition occurs if you are running Db2 in data
sharing mode, but the associated IRLM is running
with local scope (SCOPE=LOCAL in the IRLM startup
00E30808 procedure). If you are running Db2 in data sharing
mode, ensure that the associated IRLM startup
procedure specifies SCOPE=GLOBAL. Conversely, if
Explanation
you are not running Db2 in data sharing mode, ensure
Db2 issued an IRLM PURGE request to purge retained that the associated IRLM startup procedure specifies
locks, but the PURGE request was not successful. This SCOPE=LOCAL.
abend reason code accompanies message DSNT807I.
System action
is initiated. The Db2 restart process is terminated.

Reason code identifiers that begin with 00E4 communicate normal and error situations with Db2 utilities.
Many of the utilities codes ask you to determine the failing environment. This means that you should
determine the following things:
• The address space in which the failure occurred
• The utility that was running
• Whether it was a restart of a utility that failed previously
• Whether the job step invocation was through the DSNUTILB program
• Whether a -DISPLAY or -TERM UTILITY command was involved.
To assist you in determining the problem, register 2 might contain a secondary reason code. This
secondary reason code might be an IBM internal reason code; therefore, it might not be documented
in this manual.
When Db2 resources are unavailable to utilities, message DSNT500I is issued along with the utility reason
code. Refer to message DSNT500I for the correct action.
No cursor table was present at entry to database
Explanation services portion of utility.
A function of Db2 was invoked and attempted to
establish a functional recovery environment. The System action
functional recovery element (FRE) that was created
was not the first one. The utility job step that caused the function to
be requested is abended. Utility processing is not
initiated.
System action
A record is written to SYS1.LOGREC, and an SVC dump System programmer response
is requested. The execution unit is abended.
This is an internal error. Determine the failing
environment. If you suspect an error in Db2, you might
Operator response need to report the problem. For information about
Notify the system programmer. identifying and reporting the problem, see Collecting
in Db2, you might need to report the problem. Collect the following diagnostic items:
For information about identifying and reporting the • Console output from the system on which the job
problem, see Collecting diagnostic data (Collecting was run, and a listing of the SYSLOG data set for the
data). period of time that spans the failure.
executing IFCEREP1.
was run, and a listing of the SYSLOG data set for the • SYSPRINT output, including JCL, for the application
period of time that spans the failure. program or batch job, and system messages that
sent to SYSPRINT.
executing IFCEREP1.
SORT.
00E40001

Db2 (for 04E and 04F abends). Availability of this Db2 (for 04E and 04F abends). Availability of this
dump is dependent on the failing environment. dump is dependent on the failing environment.
Availability of these dumps is dependent on the Availability of these dumps is dependent on the
failing environment. failing environment.
00E40002 00E40003
The caller of the database services portion of the An error occurred while getting FRBPARM from
utility was in the wrong protect key. application storage.

The utility job step that caused the function to be The utility job step that caused the function to be
requested is abended. The utility job is placed in the requested is abended. The utility job is placed in the
stopped state. stopped state.

Determine the failing environment. Determine the failing environment., in particular
whether invocation was through program DSNUTILB.
If a JOBLIB or STEPLIB is being used in the batch
utility job, check that all application program libraries
included in the concatenation are authorized.
Check that the batch utility program DSNUTILB was data (Collecting data).
included in the MVS program properties table during
the installation of Db2. The entry for DSNUTILB in the Problem determination
MVS program properties table was provided by MVS.
If you suspect an error in Db2, you might need to If the environment was DSNUTILB, the problem could
report the problem. For information about identifying be internal.
User response
executing IFCEREP1.
• Listing of SYS1.LOGREC data set, obtained by SORT.
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application Db2 (for 04E and 04F abends). Availability of this
program or batch job, and system messages that dump is dependent on the failing environment.
sent to SYSPRINT.
SORT. 00E40004

Explanation data set identified by the UTPRINT DD statement in
the utility job step.
An error occurred while getting FRB from application
storage. Error message DSNU044I, that contains the nonzero
reason code, is directed to the device/data set
identified by the SYSPRINT DD statement in the utility
System action job step.
The utility job step that caused the function to be If DFSORT cannot be loaded, the utility output
requested is abended. The utility job is placed in the contains DSNU1640I.
stopped state.
Operator response
An operator with SYSOPR authority can issue the
Determine the failing environment. In particular, -TERM UTILITY command to release the resources
determine whether invocation was through program claimed by the stopped utility (this may not be
DSNUTILB. If you suspect an error in Db2, you might necessary).
diagnostic data (Collecting data). User response
Determine the cause of the error. If the error can
Problem determination be corrected, the utility may be restarted from
the beginning of the sort phase by using the
If the environment was DSNUTILB, the problem could 'RESTART(PHASE)' parameter. If the error prevents the
be internal. utility from completing, the -TERM command should
Collect the following diagnostic items: be issued to remove the stopped utility from the
system. The -TERM UTILITY should seldom be used
• Console output from the system on which the job when the stopped utility is REORG.
executing IFCEREP1. This abend is accompanied by the utility message
• SYSPRINT output, including JCL, for the application DSNU044I, that contains the sort reason code and
program or batch job, and system messages that an SVC dump, or by a DSNU1640I message. In most
were issued. Make sure that MSGLEVEL=(1,1) on the cases, the error messages from SORT that are sent
JOB statement so that all diagnostic information is to the device/data set identified by the UTPRINT DD
sent to SYSPRINT. statement identify the problem. The dump may not
be needed. If SORT is unable to open the UTPRINT
• UTPRINT output, produced by utility invocation of data set, only the message and abend are provided.
SORT. In this case, correct the problem associated with
• Dynamic dump, taken to SYS1.DUMPxx data set, by the UTPRINT DD statement, and restart the job with
Db2 (for 04E and 04F abends). Availability of this the RESTART(PHASE) option. If DFSORT could not
dump is dependent on the failing environment. be loaded then make sure that the DFSORT program
• SYSABEND, SYSUDUMP, or SYSMDUMP output. libraries are accessible by the utility job.
Availability of these dumps is dependent on the Collect the following diagnostic items:
executing IFCEREP1.
A nonzero reason code was returned from MVS sort or
DFSORT could not be loaded. • SYSPRINT output, including JCL, for the application
Any error message generated by sort in conjunction sent to SYSPRINT.
with the nonzero reason code is directed to the device/ • UTPRINT output, produced by utility invocation of
SORT.

• Dynamic dump, taken to SYS1.DUMPxx data set, by User response
Db2 (for 04E and 04F abends). Availability of this
dump is dependent on the failing environment. If applicable, correct the resource unavailable
condition identified by the DSNT500I message. For
• SYSABEND, SYSUDUMP, or SYSMDUMP output. an explanation of resource types, see . Either restart
Availability of these dumps is dependent on the the utility from the last commit point or terminate the
failing environment. utility and submit it again.
00E40006 If DSNT500I was not issued, register 2 contains
a secondary Db2 reason code that gives more
Explanation information about the problem. If the secondary
reason code is not documented in this manual, it is
An error was detected while manipulating the utility- an internal IBM code. Consult the system programmer
in-progress bits of the database exception table to diagnose the problem.
(DBET). The error might occur due to one of the
following conditions:
• The SYSIBM.SYSUTIL table and the DBET are out of
sync. If the condition cannot be corrected, determine the
• The utility-in-progress condition was not properly
reset after execution of a prior utility. Collect the following diagnostic items:
• A resource unavailable condition exists. • Console output from the system on which the job
Utility processing is abended. This abend might be
executing IFCEREP1.
accompanied by message DSNT500I. An SDUMP
might be requested. • SYSPRINT output, including JCL, for the application
System programmer response JOB statement so that all diagnostic information is
Use the -DISPLAY UTILITY command to display the sent to SYSPRINT.
status of any utilities in progress. Determine if another • UTPRINT output, produced by utility invocation of
utility is active on the same table space. Use the SORT.
-DISPLAY DATABASE command to determine if the
table space has a utility-in-progress condition set on.
The utility-in-progress bit is turned on only for table dump is dependent on the failing environment.
spaces. If a utility is run against an index, the utility- • SYSABEND, SYSUDUMP, or SYSMDUMP output.
in-progress bit is turned on for the appropriate table Availability of these dumps is dependent on the
space. failing environment.
A utility-in-progress condition set without a • Copy of the log for this period, so that additional
corresponding entry for an active or stopped utility DSN1LOGP reports can be produced for problem
in the SYSUTIL table is an inconsistent condition determination.
caused by a prior error. To resolve this, issue a
-START DATABASE command specifying the proper 00E40007
table space with the ACCESS(FORCE) parameter. This
causes the utility-in-progress status to be cleared. Explanation
If the problem cannot be corrected, determine the The COPY utility function is unable to open the table
failing environment. space as directed. The failure can occur because the
If you suspect an error in Db2, you might need to table space is currently not available. The failure can
report the problem. For information about identifying also be an internal error.
If the table space is currently not available, a
DSNT500I RESOURCE UNAVAILABLE message is
directed to the device or data set identified by the

SYSPRINT DD statement. The utility job step is placed • SYSABEND, SYSUDUMP, or SYSMDUMP output.
in the stopped state. Availability of these dumps is dependent on the
Operator response .
After the environmental information is determined, Related reference
an operator with SYSOPR authority can terminate the COPY (Db2 Utilities)
utility job step and free the resources, but this might Related information
not be necessary.
System programmer response 00E40009

If a DSNT500I message preceded the abend, use the
contents of that message for problem determination. Explanation
Otherwise, determine the failing environment.
An error was detected while attempting to access the
If you suspect an error in Db2, you might need to target object (table space or index space).
Utilities processing is abended. The abend might be
accompanied by message DSNT500I. The DSNT500I
User response
message might be preceded by other related
If the abend was accompanied by a DSNT500I messages on the console. An SDUMP might be taken.
message, use that message to determine the cause of
the resource unavailability. You can restart the utility User response
when the resource becomes available, or you can
terminate the utility job step and resubmit the job at Correct the 'resource unavailable' condition identified
a later time. by the DSNT500I message. Either restart the utility
from the last commit point or terminate the utility and
If a DSNT500I message was not issued, an internal start it again from the beginning. If DSNT500I was not
processing error occurred. Provide the system issued, register 2 contains a secondary Db2 reason
programmer with dumps and messages for fault code that gives more information about the problem. If
analysis. the secondary reason code is not documented in this
manual, it is an internal IBM code.
This is an internal error. Problem determination
Collect the following diagnostic items: If the condition cannot be corrected, determine the
failing environment. If you suspect an error in Db2,
• Console output from the system on which the job you might need to report the problem. For information
was run, and a listing of the SYSLOG data set for the about identifying and reporting the problem, see
period of time that spans the failure. Collecting diagnostic data (Collecting data).
executing IFCEREP1.
JOB statement so that all diagnostic information is • Listing of SYS1.LOGREC data set, obtained by
sent to SYSPRINT. executing IFCEREP1.
• UTPRINT output, produced by utility invocation of • SYSPRINT output, including JCL, for the application
SORT. program or batch job, and system messages that
• Dynamic dump, taken to SYS1.DUMPxx data set, by were issued. Make sure that MSGLEVEL=(1,1) on the
Db2 (for 04E and 04F abends). Availability of this JOB statement so that all diagnostic information is
dump is dependent on the failing environment. sent to SYSPRINT.
SORT.

• Dynamic dump, taken to SYS1.DUMPxx data set, by Explanation
dump is dependent on the failing environment. This is an internal control error. The utility
subcomponent that manages the function control
• SYSABEND, SYSUDUMP, or SYSMDUMP output. flow associated with Db2 database services has been
Availability of these dumps is dependent on the requested to perform a function that it does not
failing environment. recognize.
00E4000A
System action
Explanation The utility job step that caused the function to be
An error has been detected while force closing a page requested is abended. The utility job is placed in the
set. stopped state.

Utilities processing is abended. An operator with SYSOPR authority can issue the
-TERM UTILITY command to free resources (this might
not be necessary).
This is an internal error. Determine the failing System programmer response
environment. If you suspect an error in Db2, you might
need to report the problem. For information about If you suspect an error in Db2, you might need to
identifying and reporting the problem, see Collecting report the problem. For information about identifying
diagnostic data (Collecting data). and reporting the problem, see Collecting diagnostic
User response
User response
To determine how much of the requested function
within the job step was completed, examine the data
Problem determination set/device identified by SYSPRINT. Consult the system
Collect the following diagnostic items: programmer to diagnose the problem. Determine
whether the utility job step should be terminated in
• Console output from the system on which the job order to release resources.
executing IFCEREP1. Collect the following diagnostic items:
sent to SYSPRINT.
executing IFCEREP1.
SORT.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • UTPRINT output, produced by utility invocation of
Availability of these dumps is dependent on the SORT.
00E4000C Db2 (for 04E and 04F abends). Availability of this

00E4000D 00E4000E
An error was detected while scanning or updating An error was detected while attempting to create a
table SYSIBM.SYSUTIL. cursor block (CUB).

Utilities processing is abended. The abend might Utilities processing is abended. The abend might
be accompanied by message DSNT500I. An SDUMP be accompanied by message DSNT500I. An SDUMP
might be taken. might be taken.

Correct the 'resource unavailable' condition identified Correct the 'resource unavailable' condition identified
by the DSNT500I message. Either restart the utility by the DSNT500I message. Either restart the utility
from the last commit point or terminate the utility and from the last commit point or terminate the utility and
start it again from the beginning. start it again from the beginning.
Refer to Resource types (Db2 Messages) for an If DSNT500I was not issued, register 2 contains
explanation of resource type codes. a secondary Db2 reason code that gives more
information about the problem. If the secondary
If DSNT500I was not issued, register 2 contains
an internal IBM code.
an internal IBM code. Problem determination
If the condition cannot be corrected, determine the
Problem determination failing environment. If you suspect an error in Db2,
about identifying and reporting the problem, see Collect the following diagnostic items:
sent to SYSPRINT.
JOB statement so that all diagnostic information is • UTPRINT output, produced by utility invocation of
sent to SYSPRINT. SORT.
• UTPRINT output, produced by utility invocation of • Dynamic dump, taken to SYS1.DUMPxx data set, by
SORT. Db2 (for 04E and 04F abends). Availability of this
Db2 (for 04E and 04F abends). Availability of this • SYSABEND, SYSUDUMP, or SYSMDUMP output.
dump is dependent on the failing environment. Availability of these dumps is dependent on the

Related information Operator response
Resource types (Db2 Messages) -TERM UTILITY command to free resources (this might
not be necessary).
00E4000F

Explanation
Check the IRLM return and reason codes in the RLPL.
An error was detected while checking or setting the
state of the database exception table (DBET). This
abend might be accompanied by message DSNT500I.
System action
Utilities processing is abended. An SDUMP might be User response
requested.
Consult the system programmer to diagnose the
problem. Determine if the utility should be terminated.
User response
Correct the 'resource unavailable' condition identified Problem determination
by message DSNT500I. Either restart the utility from
the last commit point or terminate the utility and
restart it from the beginning. Refer to Resource types • Console output from the system on which the job
(Db2 Messages) in for an explanation of resource type was run, and a listing of the SYSLOG data set for the
codes. period of time that spans the failure.
If DSNT500I was not issued, register 2 contains • Listing of SYS1.LOGREC data set, obtained by
a secondary Db2 reason code that gives more executing IFCEREP1.
information about the problem. • SYSPRINT output, including JCL, for the application
If the condition cannot be corrected, determine the program or batch job, and system messages that
failing environment. were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
If you suspect an error in Db2, you might need to SORT.
report the problem. For information about identifying • Dynamic dump, taken to SYS1.DUMPxx data set, by
and reporting the problem, see Collecting diagnostic Db2 (for 04E and 04F abends). Availability of this
data (Collecting data). dump is dependent on the failing environment.
00E40010 • SYSABEND, SYSUDUMP, or SYSMDUMP output.
Explanation failing environment.
A request to IRLM on behalf of a Db2 utility to lock 00E40011

a page or an entire table space has failed. This is
either an internal Db2 or an IRLM problem. The error Explanation
occurred in the database services address space.
An attempt to extend the error range information in the
database allocation table (DBAT) failed.
System action
The utility job is abended. An SVC dump is requested System action
(with the address of the IRLM parameter list, RLPL, in
register 4). The utility is placed in the stopped state. The I/O error that did not get recorded in the DBAT
table was reported in error message DSNU086E, that
was directed to the device/data set identified by the
SYSPRINT DD statement. The utility job step is placed
in the stopped state.

An operator with SYSOPR authority can issue the Utilities processing is abended. The abend might
-TERM UTILITY command to release the resources be accompanied by message DSNT500I. An SDUMP
claimed by the stopped utility (this might not be might be taken.
necessary).
User response
Correct the 'resource unavailable' condition identified
Determine the failing environment. If you suspect an by the DSNT500I message. Either restart the utility
error in Db2, you might need to report the problem. from the last commit point or terminate the utility and
For information about identifying and reporting the start it again from the beginning. Refer to Resource
problem, see Collecting diagnostic data (Collecting types (Db2 Messages) in for an explanation of resource
data). type codes.
User response a secondary Db2 reason code that gives more
The system programmer should be notified and given
the relevant environmental information. Subsequent
to its correction, the stopped utility can be restarted
using the RESTART option, or it can be terminated and
resubmitted at a later time. Problem determination
Collect the following diagnostic items: Collecting diagnostic data (Collecting data).
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application executing IFCEREP1.
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of sent to SYSPRINT.
SORT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (for 04E and 04F abends). Availability of this
Db2 (for 04E and 04F abends). Availability of this dump is dependent on the failing environment.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. Availability of these dumps is dependent on the
Availability of these dumps is dependent on the failing environment.
00E40012 SORT.
00E40013
Explanation
An error was detected while attempting to find a Explanation
database descriptor block (DBD) address.
An error was detected while creating a ECB exit for
-STOP DB2.

data).
Utilities processing is abended.
User response
Determine the failing environment. If you suspect an
For information about identifying and reporting the Problem determination
problem, see Collecting diagnostic data (Collecting This is an internal error.
data).
This is an internal error. • SYSPRINT output, including JCL, for the application
period of time that spans the failure. • UTPRINT output, produced by utility invocation of
executing IFCEREP1. • Dynamic dump, taken to SYS1.DUMPxx data set, by
were issued. Make sure that MSGLEVEL=(1,1) on the • SYSABEND, SYSUDUMP, or SYSMDUMP output.
JOB statement so that all diagnostic information is Availability of these dumps is dependent on the
sent to SYSPRINT. failing environment.
SORT. 00E40015

Db2 (for 04E and 04F abends). Availability of this Explanation
dump is dependent on the failing environment. A RECOVER utility was initiated with the ERROR
• SYSABEND, SYSUDUMP, or SYSMDUMP output. RANGE option specified. The request was rejected
Availability of these dumps is dependent on the when it was determined that there was not a sufficient
failing environment. number of alternate tracks for the pages in the error
range to be recovered.
00E40014
System action
Explanation
The abend was issued in the database services
An error was detected from the terminate thread address space. The dumps requested are dependent
function. upon the JCL of the utility job step. The utility job step
is abended. The utility is placed in the 'stopped' state.
System action
Utilities processing is abended. Operator response
System programmer response -TERM UTILITY command to free resources (this might
not be necessary).

User response R2
Address of media manager interface block (MMIB).
Recovery can be accomplished by resubmitting the
RECOVER utility without the ERROR RANGE option. R3
Recovery can be by data set or the table space as a Address of field containing VSAM RBA to be
whole. converted.
R4
Address of area to receive CCHHR.
R5
Collect the following diagnostic items: MMCNVT places UCB address here.
• Console output from the system on which the job R8
was run, and a listing of the SYSLOG data set for the Return code from media manager. If you suspect
period of time that spans the failure. an error in media manager, refer to z/OS DFSMSdfp
• Listing of SYS1.LOGREC data set, obtained by Diagnosis.
executing IFCEREP1. If you suspect an error in Db2, you might need to
• SYSPRINT output, including JCL, for the application report the problem. For information about identifying
program or batch job, and system messages that and reporting the problem, see Collecting diagnostic
were issued. Make sure that MSGLEVEL=(1,1) on the data (Collecting data).
sent to SYSPRINT. Problem determination
SORT. Collect the following diagnostic items:
• Dynamic dump, taken to SYS1.DUMPxx data set, by • Console output from the system on which the job
Db2 (for 04E and 04F abends). Availability of this was run, and a listing of the SYSLOG data set for the
dump is dependent on the failing environment. period of time that spans the failure.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • Listing of SYS1.LOGREC data set, obtained by
Availability of these dumps is dependent on the executing IFCEREP1.
failing environment. • SYSPRINT output, including JCL, for the application
00E40016
Explanation sent to SYSPRINT.
A Recover utility was initiated with the ERROR RANGE • UTPRINT output, produced by utility invocation of
option specified. An error was detected by the SORT.
media manager while processing a MMCNVT macro • Dynamic dump, taken to SYS1.DUMPxx data set, by
invocation. This is an internal error within either Db2 or Db2 (for 04E and 04F abends). Availability of this
the media manager. dump is dependent on the failing environment.
System action Availability of these dumps is dependent on the
The utility job step that caused the function to be failing environment.
requested is abended. The utility job is placed in the 00E40017
stopped state.
Explanation
Operator response
An error was detected from terminate identify.
-TERM UTILITY command to free resources if that
should prove necessary (this might not be necessary). System action
The MMCNVT macro converts a VSAM RBA to its System programmer response
physical track address (CCHHR). At the time of abend, Determine the failing environment. If you suspect an
the following registers contain relevant information: error in Db2, you might need to report the problem.

data). This abend is forced to allow restart of the utility
when work data sets are used and the disposition is
(MOD,DELETE,CATLG).
User response
00E4001A
Explanation
An error was detected while using SVC 99 to allocate,
This is an internal error. deallocate, or retrieve information dynamically on the
Collect the following diagnostic items: data set.
period of time that spans the failure. Utility processing is abended.
Determine the failing environment. If the utility is
called from a stored procedure, check to see if the
refresh of WLM cannot progress, for example because
of an MVS authorization error. If the WLM refresh
sent to SYSPRINT.
failed, issue a VARY command to refresh the WLM
• UTPRINT output, produced by utility invocation of environment.
SORT.
dump is dependent on the failing environment. Notify the system programmer.
Availability of these dumps is dependent on the Problem determination
This is a Db2 internal error. If the error occurs during
00E40018 utility execution through a stored procedure, this
ABEND indicates that a failure occurred during an
SVC 99 operation, and the utility cleanup (ESTAE) will
Explanation attempt to refresh the WLM address space.
Either an error was detected during the execution of a
restarted utility or a condition was detected that might
have required restart of a utility. A message is issued • Console output from the system on which the job
prior to this abend code to indicate the type of error. was run, and a listing of the SYSLOG data set for the
executing IFCEREP1.
Utility processing is abended.
System programmer response were issued. Make sure that MSGLEVEL=(1,1) on the
Check messages issued prior to this abend code to JOB statement so that all diagnostic information is
determine the cause of the error. Correct the error, and sent to SYSPRINT.
restart the job. • UTPRINT output, produced by utility invocation of
SORT.
User response • Dynamic dump, taken to SYS1.DUMPxx data set, by
Notify the system programmer. dump is dependent on the failing environment.

• SYSABEND, SYSUDUMP, or SYSMDUMP output. User response
failing environment. Correct the 'resource unavailable' condition identified
by the DSNT500I message. Either restart the utility
00E4001B from the last commit point or terminate the utility and
start it again from the beginning. Refer to Resource
Explanation types (Db2 Messages) in for an explanation of resource
type codes.
A Db2 utility has attempted to allocate a data set to
the generic unit name SYSALLDA, but the allocation If DSNT500I was not issued, register 2 contains
has failed. This dynamic allocation was attempted a secondary Db2 reason code that gives more
because the utility had been requested to perform information about the problem. If the secondary
sorts in parallel, a DFSPARM data set was present in reason code is not documented in this manual, it is
the job JCL, the DFSPARM data set was allocated to an internal IBM code.
SYSIN, and no SORTDEVT specification was supplied
in the utility control statement. Problem determination
System action failing environment. If you suspect an error in Db2,
Utility processing is abended. you might need to report the problem. For information
User response
If the failing utility was REORG, and the UNLOAD
phase had completed, restart the utility after taking • Console output from the system on which the job
one of the following actions: was run, and a listing of the SYSLOG data set for the
• Delete the DFSPARM data set from the job JCL.
• Create a DASD data set containing the DFSORT executing IFCEREP1.
control statements you want to use and change the
job JCL to point to that data set instead of SYSIN.
If the failing utility was not REORG, or if it was were issued. Make sure that MSGLEVEL=(1,1) on the
REORG and the UNLOAD phase had not completed, JOB statement so that all diagnostic information is
use the -TERM command to terminate the utility. Then sent to SYSPRINT.
resubmit the job after taking one of the following • UTPRINT output, produced by utility invocation of
actions: SORT.
• Delete the DFSPARM data set from the job JCL. • Dynamic dump, taken to SYS1.DUMPxx data set, by
• Create a DASD data set containing the DFSORT Db2 (for 04E and 04F abends). Availability of this
control statements you want to use and change the dump is dependent on the failing environment.
job JCL to point to that data set instead of SYSIN. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• Use the SORTDEVT keyword in the utility control Availability of these dumps is dependent on the
statement to specify a generic device unit name failing environment.
(such as SYSDA) that can be used to do the dynamic
00E4001D
allocation.
00E4001C Explanation
An error was detected while attempting to read a row
Explanation from the SYSIBM.SYSSYNONYMS table.
An error was detected while attempting to map
externals to a specific file object descriptor (OBD). System action
Utilities processing is abended. The abend might
System action be accompanied by message DSNT500I. An SDUMP
Utilities processing is abended. The abend might might be taken.
be accompanied by message DSNT500I. An SDUMP
might be taken.

start it again from the beginning. Refer to Resource start it again from the beginning.
types (Db2 Messages) in for an explanation of resource
type codes.
If DSNT500I was not issued, register 2 contains information about the problem. If the secondary
a secondary Db2 reason code that gives more reason code is not documented in this manual, it is
information about the problem. an internal IBM code.

If the condition cannot be corrected, determine the If the condition cannot be corrected, determine the
failing environment. If you suspect an error in Db2, failing environment. If you suspect an error in Db2,
you might need to report the problem. For information you might need to report the problem. For information
about identifying and reporting the problem, see about identifying and reporting the problem, see
Collecting diagnostic data (Collecting data). Collecting diagnostic data (Collecting data).
• SYSPRINT output, including JCL, for the application • SYSABEND, SYSUDUMP, or SYSMDUMP output.
program or batch job, and system messages that • Listing of SYS1.LOGREC data set, obtained by
were issued. Make sure that MSGLEVEL=(1,1) on the executing IFCEREP1.
sent to SYSPRINT. • SYSPRINT output, including JCL, for the application
• UTPRINT output, produced by utility invocation of were issued. Make sure that MSGLEVEL=(1,1) on the
SORT. JOB statement so that all diagnostic information is
• Dynamic dump, taken to SYS1.DUMPxx data set, by sent to SYSPRINT.
Db2 (for 04E and 04F abends). Availability of this • UTPRINT output, produced by utility invocation of
dump is dependent on the failing environment. SORT.
00E4001F
Explanation
00E4001E
An error was detected while attempting to read a row
from the SYSIBM.SYSINDEXES table.
Explanation
An error was detected while attempting to read a row System action
from the SYSIBM.SYSTABLES table.
System action
might be taken.
be accompanied by message DSNT500I. An SDUMP User response
might be taken.

types (Db2 Messages) in for an explanation of resource User response
type codes.
information about the problem. If the secondary Problem determination
reason code is not documented in this manual, it is It is normal for utility jobs which began when the
an internal IBM code. database services address space (ssnmDBM1) was
running, to abend with this code if the database
Problem determination address space terminates while the utility is running.
Diagnose the issue that caused the database services
If the condition cannot be corrected, determine the address space (ssnmDBM1) to shut down.
you might need to report the problem. For information Collect the following diagnostic items:
about identifying and reporting the problem, see • Console output from the system on which the job
Collecting diagnostic data (Collecting data). was run, and a listing of the SYSLOG data set for the
executing IFCEREP1.
period of time that spans the failure. • SYSPRINT output, including JCL, for the application
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application sent to SYSPRINT.
SORT.
sent to SYSPRINT. • Dynamic dump, taken to SYS1.DUMPxx data set, by
SORT.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. 00E40021
failing environment. Explanation
00E40020 Utility processing was performing an authorization
checkfor the utility user and specified object, when
Explanation an error was detected. A necessary resource for the
check was not available.
The utility batch address space attempted a resource
access request (RARQ) to the database services
address space (ssnmDBM1) but the database address System action
space has ended or is in the process of shutting down. Utility processing is abended.

Utilities processing is abended. Make the resource available and take one of the
following actions:
System programmer response • Terminate the utility by issuing a -TERM UTILITY
Restart the failed utility job steps or terminate and command, and resubmit the utility.
resubmit them. • Resubmit the utility with the RESTART parameter.

executing IFCEREP1.
This abend is accompanied by the message JOB statement so that all diagnostic information is
DSNT500I, that identifies the unavailable resource. sent to SYSPRINT.
The message is written to the SYSPRINT data set. • UTPRINT output, produced by utility invocation of
Related tasks SORT.
Restarting an online utility (Db2 Utilities) • Dynamic dump, taken to SYS1.DUMPxx data set, by
Related reference Db2 (for 04E and 04F abends). Availability of this
Related information • SYSABEND, SYSUDUMP, or SYSMDUMP output.
00E40022 .
00E40023
Explanation
An error was detected while attempting to read a row Explanation
from the SYSIBM.SYSUTIL table.
The internal protocols required for utility update
of table the SYSIBM.SYSUTIL have been violated.
System action Utility modifications to SYSIBM.SYSUTIL were not
Utilities processing is abended. The abend might committed.
might be taken. System action
The utility job step that caused the function to be
User response requested is abended. The utility job is placed in the
Correct the 'resource unavailable' condition identified stopped state.
from the last commit point or terminate the utility and Operator response
types (Db2 Messages) in for an explanation of resource An operator with SYSOPR authority can issue the
type codes. -TERM UTILITY command to release the resources
claimed by the stopped utility (this might not be
If DSNT500I was not issued, register 2 contains necessary).
an internal IBM code. Determine the failing environment. If you suspect an
Problem determination For information about identifying and reporting the
If the condition cannot be corrected, determine the data).
Collecting diagnostic data (Collecting data). This is an internal error.
Collect the following diagnostic items: Collect the following diagnostic item listed in
• REPAIR dump of all SYSUTIL pages.

00E40024 User response
Explanation by the DSNT500I message. Either restart the utility
Internal protocols required for utility serialization were from the last commit point or terminate the utility and
violated. Specifically, utility serialization cleanup was start it again from the beginning. Refer to Resource
not invoked upon completion of utility processing. This types (Db2 Messages) in for an explanation of resource
error can happen if during utility restart, the utility type codes.
control statement is modified improperly. If DSNT500I was not issued, register 2 contains
System action information about the problem. If the secondary
The utility job step is terminated, placing the utility in an internal IBM code.
the stopped state.
Operator response
An operator with SYSOPR authority can issue the failing environment. If you suspect an error in Db2,
TERM UTILITY command to release the resources you might need to report the problem. For information
claimed by the stopped utility, however this action about identifying and reporting the problem, see
might not be necessary. Collecting diagnostic data (Collecting data).
Determine the failing environment. If you suspect an was run, and a listing of the SYSLOG data set for the
problem, see Collecting diagnostic data (Collecting • Listing of SYS1.LOGREC data set, obtained by
data). executing IFCEREP1.
Collect the following diagnostic items: JOB statement so that all diagnostic information is
sent to SYSPRINT.
• REPAIR dump of all SYSUTIL pages.
Related reference SORT.
00E40025
Explanation
Utility processing attempted to allocate resources for failing environment.
this utility job step. The allocate protocol has returned
00E40027
a nonzero return code.

An error has been detected while attempting to update
a row of the SYSIBM.SYSUTIL table.
might be taken.
System action
Operator response Utilities processing is abended. The abend might
might be taken.
-TERM UTILITY command to release the resources
claimed by the stopped utility, but this might not be
necessary.

Correct the 'resource unavailable' condition identified Determine the failing environment. If you suspect an
by the DSNT500I message. Either restart the utility error in Db2, you might need to report the problem.
from the last commit point or terminate the utility and For information about identifying and reporting the
start it again from the beginning. Refer to Resource problem, see Collecting diagnostic data (Collecting
types (Db2 Messages) in for an explanation of resource data).
type codes.
If DSNT500I was not issued, register 2 contains User response
Collecting diagnostic data (Collecting data). • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
• Listing of SYS1.LOGREC data set, obtained by sent to SYSPRINT.
executing IFCEREP1. • UTPRINT output, produced by utility invocation of
• SYSPRINT output, including JCL, for the application SORT.
were issued. Make sure that MSGLEVEL=(1,1) on the Db2 (for 04E and 04F abends). Availability of this
JOB statement so that all diagnostic information is dump is dependent on the failing environment.
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of Availability of these dumps is dependent on the
SORT. failing environment.
Explanation
Availability of these dumps is dependent on the An error has been detected while attempting to read a
failing environment. row from the SYSIBM.SYSUTIL table.
00E40028
System action
Explanation Utilities processing is abended. The abend might
An error has been detected while attempting to might be taken.
COMMIT.
User response
System action
Utilities processing is abended. by the DSNT500I message. Either restart the utility
types (Db2 Messages) in for an explanation of resource
type codes.

If DSNT500I was not issued, register 2 contains problem, see Collecting diagnostic data (Collecting
a secondary Db2 reason code that gives more data).
reason code is not documented in this manual, it is Problem determination
If the condition cannot be corrected, determine the • Console output from the system on which the job
failing environment. If you suspect an error in Db2, was run, and a listing of the SYSLOG data set for the
you might need to report the problem. For information period of time that spans the failure.
about identifying and reporting the problem, see • Dynamic dump, taken to SYS1.DUMPxx data set, by
Collecting diagnostic data (Collecting data). Db2 (04E and 04F abends).
Collect the following diagnostic items: • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• Console output from the system on which the job • DSN1LOGP detail report that contains log records
was run, and a listing of the SYSLOG data set for the associated with the damaged page.
period of time that spans the failure. • Detailed description of events immediately prior to
• Listing of SYS1.LOGREC data set, obtained by and during the abend.
program or batch job, and system messages that • All dumps taken by the attachment facility or
were issued. Make sure that MSGLEVEL=(1,1) on the requesting application.
sent to SYSPRINT. 00E4002B
SORT. Explanation
• Dynamic dump, taken to SYS1.DUMPxx data set, by The utility check pending protocol detected invalid
Db2 (for 04E and 04F abends). Availability of this parameters for the setting or resetting of the check
dump is dependent on the failing environment. pending state.
Availability of these dumps is dependent on the System action
The utility job is abended.
00E4002A
Explanation
During utility restart processing, a record in the error in Db2, you might need to report the problem.
SYSUTILX checkpoint/restart area was not recognized. For information about identifying and reporting the
The utility might not be restartable. problem, see Collecting diagnostic data (Collecting
data).
System action
Utility processing is abended. User response
Operator response
An operator with SYSOPR authority can issue the Problem determination
-TERM UTILITY command to release the resources This is an internal error.
claimed by the stopped utility.
Determine the failing environment. If you suspect an period of time that spans the failure.

sent to SYSPRINT. Db2 (for 04E and 04F abends). Availability of this
• Dynamic dump, taken to SYS1.DUMPxx data set, by dump is dependent on the failing environment.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. failing environment.
Availability of these dumps is dependent on the 00E4002E
00E4002D Explanation
During utility serialization or utility restart, an attempt
Explanation to either read or retrieve from SYSUTIL or SYSUTILX
This abend is issued as a result of an error other has failed.
than the 'resource unavailable' condition that was
encountered while attempting to update a Db2 catalog System action
for the setting or resetting of the check pending state.
Db2 abends the utility job.
System action
An SVC dump is requested, the error flag in the DBA
table is set on for the table space for which the check Determine the failing environment. If you suspect an
pending state is being set or reset, and processing error in Db2, you might need to report the problem.
continues. For information about identifying and reporting the
data).
Determine the failing environment. If you suspect an User response
For information about identifying and reporting the Notify the system programmer.
User response
Determine the reason for the catalog access error. • Listing of SYS1.LOGREC data set, obtained by
This abend is accompanied by console message executing IFCEREP1.
DSNU972I. See the problem determination for this • SYSPRINT output, including JCL, for the application
message for a description of how processing is program or batch job, and system messages that
affected by this error. were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
was run, and a listing of the SYSLOG data set for the • UTPRINT output, produced by utility invocation of
period of time that spans the failure. SORT.
• Listing of SYS1.LOGREC data set, obtained by • Unformatted DSN1PRNT output of the

executing IFCEREP1. DSNDB01.DBD01 page set. Locate the inconsistent
DBD in the DSNDB01.DBD01 page set by using

the method described in Finding a DBD in a dump Explanation
(Diagnosing Db2 problems).
Internal control blocks were scanned for internal
00E40030 IDs representing the SYSIBM.SYSUTIL table. No
corresponding ID was found.
Explanation
A -DISPLAY UTILITY or -TERM UTILITY command has
System action
failed in the command subsystem. The utility job step is terminated, placing the utility in
the stopped state.
System action
Command processing is terminated. For -TERM
Operator response
UTILITY, all previous actions taken by the command An operator with SYSOPR authority can issue the
are backed out. TERM UTILITY command to release the resources
claimed by the stopped utility, but this might not be
System programmer response necessary.

For information about identifying and reporting the Determine the failing environment. If you suspect an
problem, see Collecting diagnostic data (Collecting error in Db2, you might need to report the problem.
data). For information about identifying and reporting the
This error is accompanied by additional messages

and/or SVC dumps that identify the failure in the utility
command subsystem. Refer to this manual under This is an internal error.
those messages and/or codes for additional problem
determination. Collect the following diagnostic item listed in
Collect the following diagnostic items: • REPAIR dump of all SYSUTIL pages.

• Listing of SYS1.LOGREC data set, obtained by The utility message generator was unable to obtain
executing IFCEREP1. the requested storage. The available storage used to
• SYSPRINT output, including JCL, for the application buffer messages produced by the database memory is
program or batch job, and system messages that full and a request to obtain more storage from subpool
were issued. Make sure that MSGLEVEL=(1,1) on the 229 failed.
sent to SYSPRINT. System action
SORT. Utility processing abends. No SYSABEND dump or SVC
dump is requested.
dump is dependent on the failing environment. User response
• SYSABEND, SYSUDUMP, or SYSMDUMP output. This abend occurs due to a system resource limit.
Availability of these dumps is dependent on the It might be necessary to modify the utility control
failing environment. statement.
00E40033 If the abend occurs as a result of the LOAD utility,

attempt to restart the job. If failure recurs, it might
be necessary to change the discard limit or correct
the situation that caused many error messages to be
produced.

If the abend occurs as a result of the REPAIR utility, System action
change the beginning page number to the last page
number printed plus one, or change the number of Utility processing is abended and the utility is placed in
pages to be dumped to a smaller number. Resubmit a stopped state.
the job.
If the abend occurs as a result of the REBUILD INDEX System programmer response
utility, the unique index might have to be dropped and If the conditions identified in the DSNT500I
re-created as a nonunique index. If a unique index message can not be corrected, determine the failing
is required and the data contains a large number of environment. If you suspect an error in Db2, you might
duplicates, the duplicates must be reduced before need to report the problem. For information about
attempting to rebuild the index again. identifying and reporting the problem, see Collecting
Refer to the prior error messages to determine how to User response
correct the problem. Correct the 'resource unavailable' condition identified
by the DSNT500I message. Then, either restart the
00E40035
utility from the last commit point or terminate the
utility and restart it from the beginning.
Explanation
The -START ACCESS FORCE command was issued Problem determination
when DSNDB01.SYSUTILX was in a pending state,
Refer to the description for message DSNT500I.
which prohibits further processing. The pending state
was either copy or recovery pending. Refer to Resource types (Db2 Messages) in for an
explanation of resource type codes.
Explanation
System programmer response A failure has occurred during an attempt to free
Issue a -DISPLAY DATABASE command to determine storage.
the state of DSNDB01.SYSUTILX. If the state is
copy pending, do a full image copy. If the state is System action
recovery pending, use the RECOVER utility to recover
DSNDB01.SYSUTILX. The utility job step that caused the function to be
requested is abended. The utility job is placed in the
If you suspect an error in Db2, you might need to stopped state.
Operator response
An operator with SYSOPR authority can terminate the
User response utility job step and free the resources (this might not
be necessary). However, this should not be done until
Notify the system programmer so that the pending after the diagnostic environment has been established.
condition can be resolved.
An error was returned from the DSNILREQ protocol
during page level locking. This abend code is
data).
accompanied by message DSNT500I that explains the
'resource unavailable' condition.

executing IFCEREP1.
executing IFCEREP1.
sent to SYSPRINT.
SORT.
SORT. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
dump is dependent on the failing environment. 00E40053
Availability of these dumps is dependent on the Explanation
An invalid OBID of zero was found by the module that
00E40051 maps external object names to OBIDs.

Invalid OTYPE was passed to DSNUGMAP. The utility job step that caused the function to be
System action stopped state.

Operator response
stopped state. An operator with SYSOPR authority can terminate the
utility job step and free any resources (this might not
Operator response be necessary). However, this should not be done until
after the diagnostic environment has been established.
An operator with SYSOPR authority can terminate
the utility job step and free up any resources (this
might not be necessary). However, this should not be
done until after the diagnostic environment has been Determine the failing environment. If you suspect an
established. error in Db2, you might need to report the problem.
System programmer response problem, see Collecting diagnostic data (Collecting
data).
User response
problem, see Collecting diagnostic data (Collecting Notify the system programmer.
data).
OBIDs are extracted from the Db2 catalog.
This is an internal error. The OBID for a table space is found in the
Collect the following diagnostic items: SYSIBM.SYSTABLESPACE table. The OBID for a table
is found in the SYSIBM.SYSTABLES table. The OBID for
• Console output from the system on which the job a index is found in the SYSIBM.SYSINDEXES table. If
was run, and a listing of the SYSLOG data set for the the object exists, the OBID cannot be zero.

period of time that spans the failure. • Console output from the system on which the job
executing IFCEREP1.
were issued. Make sure that MSGLEVEL=(1,1) on the • SYSPRINT output, including JCL, for the application
JOB statement so that all diagnostic information is program or batch job, and system messages that
sent to SYSPRINT. were issued. Make sure that MSGLEVEL=(1,1) on the
SORT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by SORT.
dump is dependent on the failing environment. • Dynamic dump, taken to SYS1.DUMPxx data set, by
• SYSABEND, SYSUDUMP, or SYSMDUMP output. dump is dependent on the failing environment.
failing environment. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
00E40070 failing environment.
00E40071
Explanation
A utility data set could not be opened. The abend Explanation
was issued to place the utility in the stopped state for
review and correction. An I/O error was encountered on a required OS/VS
data set. An abend was issued to place the utility in a
stopped state for review and correction. Resubmit the
System action utility.
Utility error message DSNU034I, DSNU036I, This abend might also be issued by a utility that uses
DSNU037I, DSNU039I or DSNU041I was issued subtasks, if one subtask encounters an abend B37,
to identify the DD statement associated with the D37, or E37 on a data set, and another subtask tries to
DCB that could not be opened. If none of those write to the data set.
messages were issued, the SYSPRINT DD statement
was omitted. The utility job step is placed in the
stopped state. System action
One of two utility error messages (DSNU032E or
Operator response DSNU040I) is sent to the data set or device associated
with the SYSPRINT DD statement of the utility job
An operator with SYSOPR authority can terminate the step. The error message identifies the error and the
utility to release the held resources, but this may not data set in error.
be necessary.
If the abend is issued by utility subtasks, DSNU016I is
issued instead of DSNU032E or DSNU040I.
The utility is stopped at the beginning of the phase
Correct the JCL, and resubmit the job. that used the OS/VS data set.

If the ddname is one you submitted, review and An operator with SYSOPR authority can terminate the
correct it. Then resubmit the job. If the ddname utility and release any held resources (this might not
is one the system provided, consult the system be necessary).
programmer. If neither message was issued, verify
that the SYSPRINT DD statement exists.

If the utility message was DSNU032E, the job can be dump is dependent on the failing environment.
restarted if an undamaged output data set is provided.
Obtain an undamaged output data set, and restart the • SYSABEND, SYSUDUMP, or SYSMDUMP output.
utility job step with the RESTART(PHASE) option. The Availability of these dumps is dependent on the
job cannot be restarted if an unload data set, during failing environment.
the RELOAD phase of either the LOAD or REORG, is Related reference
used as input instead of output. z/OS MVS System Codes
If the utility message was DSNU040I, determine the Related information
problem as described in Problem Determination. Then DSNU016I (Db2 Messages)
either resubmit the utility job using the RESTART DSNU032E (Db2 Messages)
option, or terminate the utility job step.
DSNU040I (Db2 Messages)
If the utility message was DSNU016I, determine the
cause of the B37, D37, or E37 abend and take the 00E40072
appropriate action. Normally, you will need to either
allocate more storage for the data set, or change the Explanation
allocation to a volume that has more space available.
An error was encountered while processing a BSAM
data set.
Problem determination depends upon which error System action
message was directed to the data set/device identified
by the SYSPRINT DD statement. A message identifying the error might have been sent
to the data set/device associated with the SYSPRINT
If DSNU032E was issued, an I/O error was DD statement of the utility job step. If no prior
encountered on a required utility work data set. The message was produced, a dump was requested.
message describes the error and the data set in error. The utility job step that caused the function to be
If DSNU040I was issued, an error has occurred requested is abended. The utility job is placed in the
during BSAM access to the data set defined by the stopped state.
DD statement specified in the message. The DECB
provided as a hexadecimal string contains the ECB in Operator response
the first four bytes. The first byte of the ECB contains
status bits that indicate the cause of the error. Notify the user or system programmer.
There might be an IOS (I/O subsystem) message on

the MVS console SYSLOG indicating the type of I/O System programmer response
error that occurred. If an IOS message was issued, Review the job output and failing environment. If a
follow the problem determination directions for the message was produced to identify the error, correct
message. Refer to the appropriate MVS publication for the error and resubmit or restart the job. If no
the meaning of the status bits. message was produced, then a dump should have
Collect the following diagnostic items: been requested. If you suspect an error in Db2, you
• Console output from the system on which the job about identifying and reporting the problem, see
was run, and a listing of the SYSLOG data set for the Collecting diagnostic data (Collecting data).
• Listing of SYS1.LOGREC data set, obtained by User response
executing IFCEREP1.
If a message was produced to identify the error, refer
to that message description for the proper action. If
no message can be found, then notify the system
programmer.
sent to SYSPRINT.
SORT. Problem determination depends upon which error
message, if any, was directed to the data set/device

identified by the SYSPRINT DD statement. If a Problem determination
message was produced, it describes the type of
error and data set involved. Refer to the message This is an internal error.
description for information on what action to take. Collect the following diagnostic items:
If no message was produced, then this might be an
internal error. • Console output from the system on which the job
was run, and a listing of the SYSLOG data set for the Db2 (04E and 04F abends).
period of time that spans the failure. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• UTPRINT output, produced by utility invocation of • UTPRINT output, produced by utility invocation of
SORT. SORT.
Db2 (for 04E and 04F abends). Availability of this 00E40074
• SYSABEND, SYSUDUMP, or SYSMDUMP output. Explanation
Availability of these dumps is dependent on the An internal error was encountered while processing
failing environment. a BSAM data set. The utility in progress issued an
00E40073 internal point to a BSAM data set which is opened for
write. Point is only valid for data sets opened for read.
Explanation
System action
An internal error was encountered while processing
a BSAM data set. The utility in progress issued an The utility job step is terminated, placing the utility in
internal read to a BSAM data set after end-of-file was the stopped state.
returned for the data set.
Operator response
System action An operator with SYSOPR authority can issue the
The utility job step is terminated, placing the utility in -TERM UTILITY command to release the resources
the stopped state. claimed by the stopped utility (this might not be
necessary).
Operator response
-TERM UTILITY command to release the resources Determine the failing environment. If you suspect an
claimed by the stopped utility (this might not be error in Db2, you might need to report the problem.
necessary). For information about identifying and reporting the
data).
Determine the failing environment. If you suspect an Problem determination
For information about identifying and reporting the This is an internal error.
problem, see Collecting diagnostic data (Collecting Collect the following diagnostic items:
data).

• Console output from the system on which the job Operator response
period of time that spans the failure. If necessary, an operator with SYSOPR authority can
issue the -TERM UTILITY command to release the
• Listing of SYS1.LOGREC data set, obtained by resources claimed by the stopped utility.
executing IFCEREP1.
• Source listing of the failing application program.
program or batch job, and system messages that This error may occur for a data set allocated by a JCL
were issued. Make sure that MSGLEVEL=(1,1) on the DD card or by a TEMPLATE utility control statement.
JOB statement so that all diagnostic information is If the problem determination indicates an error in the
sent to SYSPRINT. way the data set was specified, fix the JCL DD card or
the TEMPLATE control statement and resubmit the job.
00E40075 If a problem is indicated in the I/O subsystem, then
correct the problem before resubmitting the job.
Explanation
An end-of-data (EOD) has been encountered while
User response
attempting to reposition an input data set during the If the problem persists, then notify the system
restart of a utility. programmer.

Processing is abnormally terminated. A system dump The abend code is accompanied by message
is requested. DSNU031I which provides the data set name, return
code and reason code values returned from the
User response dynamic allocation request. Refer to MVS Authorized
Assembler Services Guide for a complete description
Review the JCL and ensure that the input data set is of the possible return and reason codes from
correct. Further analysis might be necessary. DYNALLOC. Error messages in the job log might give
more information about the problem. Analyze these
Problem determination messages to determine the source of the error and the
actions required to correct the error.
00E40079
• SYSABEND, SYSUDUMP, or SYSMDUMP output. A utility work data set has a block size that is too small
Availability of these dumps is dependent on the to accommodate the data to be written. An abend is
failing environment. issued to place the utility job step in a stopped state.
This allows the error to be reviewed and corrected,
and the job step to be resubmitted.
sent to SYSPRINT.
Utility error message DSNU038I is directed to the
00E40076 device/data set identified by the SYSPRINT DD
statement. The utility job step is placed in the stopped
state.
Explanation
The DYNALLOC SVC returned an unexpected return User response
code when attempting to deallocate a data set.
Delete the data set in error. Change the JCL so that
the block size for the data set with the ddname
System action
nominated in error message DSNU038I is at least the
Processing is halted. indicated block size. Resubmit the utility job step with
RESTART(PHASE) option.

Utility error message DSNU038I is directed to the sent to SYSPRINT.
device/data set identified by the SYSPRINT DD
statement. It gives the name of DD statement that • UTPRINT output, produced by utility invocation of
defines the data set with the inadequate block size SORT.
and gives the minimum block size in bytes. • Dynamic dump, taken to SYS1.DUMPxx data set, by
• Console output from the system on which the job • SYSABEND, SYSUDUMP, or SYSMDUMP output.
was run, and a listing of the SYSLOG data set for the Availability of these dumps is dependent on the
period of time that spans the failure. failing environment.
00E40081
executing IFCEREP1.
program or batch job, and system messages that Explanation
were issued. Make sure that MSGLEVEL=(1,1) on the The REORG utility has completed the UNLOAD phase
JOB statement so that all diagnostic information is while processing in a shared mode and has attempted
sent to SYSPRINT. to change to an exclusive mode for the RELOAD and
• UTPRINT output, produced by utility invocation of subsequent phases. Utility processing has detected an
SORT. internal error.
Db2 (for 04E and 04F abends). Availability of this System action
• SYSABEND, SYSUDUMP, or SYSMDUMP output. requested is abended. The utility job is placed in the
Availability of these dumps is dependent on the stopped state.
00E40080 Operator response
Explanation -TERM UTILITY command to release the resources
An error has been detected during utility termination
necessary).
cleanup. The DSNXKACC CLOSEALL protocol has
returned an error.
System action Determine the failing environment. If you suspect an
The utility job step is placed in the stopped state.
This abend code might be accompanied by a
DSNT500I error message that might indicate a Problem determination
correctable problem.
If the DSNT500I message has not been issued or if
Collect the following diagnostic item listed in
the problem can not be corrected, collect the following
diagnostic items: • REPAIR dump of all SYSUTIL pages.
Explanation
executing IFCEREP1. An error has been detected by utility serialization
protocols. Protocols were issued in the wrong order.

This is an internal error and cannot be corrected by the information about the error or message DSNI002I
user. is issued if the problem occurred while running the
START DATABASE ACCESS(FORCE) command.
System action
System action
Utility processing is abnormally terminated and the
utility is placed in a stopped state. An SDUMP is Either the utility job step is terminated and the utility
requested. is placed in a stopped state or the START DATABASE
command abnormally terminates.
Operator response
error in Db2, you might need to report the problem. An operator with SYSOPR authority can issue the
For information about identifying and reporting the -TERM UTILITY command if the user does not want to
problem, see Collecting diagnostic data (Collecting attempt to restart the utility. For the START DATABASE
data). command, rerun the command.

The -TERM UTIL command can be issued to free Determine the failing environment. If you suspect an
resources held by the failing utility. error in Db2, you might need to report the problem.
00E40083 problem, see Collecting diagnostic data (Collecting
data). For the START DATABASE command, no
Explanation response is needed.
An error was detected by utility serialization protocols.
Required parameters are missing or contain invalid User response
values. Notify the system programmer. An attempt can be
This is an internal error and cannot be corrected by the made to restart the utility or rerun the START
user. DATABASE command.
00E40090
System action
Utility processing is abnormally terminated and the Explanation
utility is placed in a stopped state. An SDUMP is
Utility processing is unable to invoke the designated
requested.
utility, because an internal error has occurred. The
specified utility is not recognized by the utility job
System programmer response controller.
error in Db2, you might need to report the problem. System action
The utility job step is terminated, placing the utility in
the stopped state.
data).
Operator response
User response
Issue the -TERM UTIL command to free resources held
by the failing utility.
00E40085 necessary).

A utility serialization LOCK or UNLOCK request has Determine the failing environment. If you suspect an
received an error from the IRLM. Either message error in Db2, you might need to report the problem.
DSNU099I is issued prior to this abend code to provide For information about identifying and reporting the

data).
This is an internal error. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
sent to SYSPRINT.
00E40096
Explanation
Availability of these dumps is dependent on the Utility access path creation has detected an invalid
failing environment. OBID. The specified value is too small, too large, or
does not exist in the subsystem.
00E40091
System action
Explanation
Utility access path creation was invoked specifying an
incorrect OBID.
stopped state.
System action
Operator response
The utility job step is terminated, placing the utility in
the stopped state.
Operator response necessary).
-TERM UTILITY command to release the resources System programmer response
necessary).
data).
data).

• Listing of SYS1.LOGREC data set, obtained by program or batch job, and system messages that
executing IFCEREP1. were issued. Make sure that MSGLEVEL=(1,1) on the
• SYSPRINT output, including JCL, for the application JOB statement so that all diagnostic information is
program or batch job, and system messages that sent to SYSPRINT.
were issued. Make sure that MSGLEVEL=(1,1) on the • UTPRINT output, produced by utility invocation of
JOB statement so that all diagnostic information is SORT.
• UTPRINT output, produced by utility invocation of Db2 (for 04E and 04F abends). Availability of this
SORT. dump is dependent on the failing environment.
• Dynamic dump, taken to SYS1.DUMPxx data set, by • SYSABEND, SYSUDUMP, or SYSMDUMP output.
Db2 (for 04E and 04F abends). Availability of this Availability of these dumps is dependent on the
dump is dependent on the failing environment. failing environment.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. 00E400A1
Explanation
00E400A0
Utility has detected the number of database objects to
be processed exceeds the maximum amount allowed.
Explanation
An error was detected while the internal structure to System action
access the tables of a table space was being built. The
table space had no tables. The utility job is abended, and the utility is placed in
the stopped state.
System action
requested is abended. The utility job is placed in the The utility cannot be restarted. An operator with
stopped state. SYSOPR authority can issue the -TERM UTILITY
command to release the resources claimed by the
stopped utility.
Operator response
00E400AE
claimed by the stopped utility (this might not be Explanation
necessary). A DSNGDALT macro invocation returned a nonzero
return code. An attempt to modify a DBD by setting
System programmer response the OBDPSRBAFmt or OBDPIRBAFmt bit on was
unsuccessful. This state is informational, indicating
Determine the failing environment. If you suspect an whether the page set is or is not in extended RBA
error in Db2, you might need to report the problem. format.
data). System action
Processing is abended.
This is an internal error. Operator response
Collect the following diagnostic items: If the failing utility is a REBUILD INDEX during
a Disaster Recovery, this abend might be avoided
• Console output from the system on which the job by modifying the REBUILD INDEX statement.
was run, and a listing of the SYSLOG data set for the Terminate the utility and resubmit it by specifying
period of time that spans the failure. RBALRSN_CONVERSION NONE on the REBUILD

INDEX statement. Alternatively, contact IBM Support System programmer response
for guidance on preventing object conversion by Db2
utilities, and how to remove the workaround when the Determine the failing environment. If you suspect an
Disaster Recovery is completed. error in Db2, you might need to report the problem.
System programmer response data).
During some Disaster Recovery scenarios
DSNDB01.DBD01, DSNDB01.SYSDBDXA or their User response
indexes might not be available yet, causing this abend
code. This abend might be caused by an unavailable
resource. Check for a DSNT500I message being issued
User response: prior to the abend. A dump will be suppressed in
This abend might be caused by an unavailable this case. If no 'resource unavailable' condition is
resource. Check for a DSNT500I message that is being indicated, notify the system programmer.
issued before the abend. A dump is suppressed in
this case. If no 'resource unavailable' condition is
indicated, notify the system programmer. Problem determination
This is an internal error. was run, and a listing of the SYSLOG data set for the
• Console output from the system on which the job executing IFCEREP1.
• Listing of SYS1.LOGREC data set, obtained by were issued. Make sure that MSGLEVEL=(1,1) on the
executing IFCEREP1. JOB statement so that all diagnostic information is
program or batch job, and system messages that • UTPRINT output, produced by utility invocation of
were issued. Make sure that MSGLEVEL=(1,1) on the SORT.
• UTPRINT output, produced by utility invocation of dump is dependent on the failing environment.
• Dynamic dump, taken to SYS1.DUMPxx data set, by Availability of these dumps is dependent on the
Db2 (for 04E and 04F abends). Availability of this failing environment.
00E400B0
failing environment. Explanation
Related information Utilities invocation of CREATE THREAD has ended
abnormally.
00E400AF System action

The utility job step is terminated. No record of the
Explanation utility job step remains in the system.
A DSNGDALT macro invocation has returned a nonzero
return code. An attempt to modify a DBD by setting the System programmer response
OBDIFIB bit on was unsuccessful.
System action For information about identifying and reporting the

problem, see Collecting diagnostic data (Collecting User response
data).
User response 00E400C1

Explanation
Problem determination Db2 failed while attempting to latch or unlatch an
index page. This is an internal error.
• Console output from the system on which the job The utility job step that caused the function to be
was run, and a listing of the SYSLOG data set for the requested is abended. The utility job is placed in the
period of time that spans the failure. stopped state.
Determine the failing environment.
JOB statement so that all diagnostic information is User response
sent to SYSPRINT.
SORT.
Db2 (for 04E and 04F abends). Availability of this If you suspect an error in Db2, you might need to
dump is dependent on the failing environment. report the problem. For information about identifying
failing environment. 00E400C2
00E400C0
Explanation
Explanation Db2 received an unexpected return code from MVS.
This code is issued for the following situations:
• A -STOP DB2 MODE(FORCE) command has been System action
entered while a utility was executing.
• A -STOP DB2 MODE(QUIESCE) command has been The utility job step that caused the function to be
entered while a utility with multiple input statements requested is abended. The utility job is placed in the
stopped state.
was executing and the current input statement
execution has completed.
• During abnormal system termination. System programmer response
System action
Utility processing is abended. User response
Determine the reason that the -STOP DB2 command Problem determination
was issued. After Db2 has been started again, the If you suspect an error in Db2, you might need to
utility job can be restarted. report the problem. For information about identifying

00E400C3 00E400CD
An error was detected during the restart of a Db2 received an error while trying to allocate a tape
utility that uses a TEMPLATE name specification to device.
dynamically allocate the data sets. The data sets that
need to be reused for restart were not found. System action
System action
requested abnormally terminated. The utility job is
Utility processing is abended. placed in the stopped state.

Examine the JCL and ensure that the TEMPLATE Determine the failing environment.
control statement specifies the correct disposition for
the data sets. Further analysis might be needed. User response
This abend is forced to allow restart of the utility when Problem determination
work data sets are used and the disposition is not
MOD, DELETE, and CATLG (for example, not If you suspect an error in Db2, you might need to
DISP=(MOD,DELETE,CATLG) and reporting the problem, see Collecting diagnostic
).
00E400D0
00E400CA
Explanation
Explanation
A conversion error occurred during the conversion of a
Db2 received an error when accessing the integrated
string to a different coded character set.
catalog facility catalog.
This code typically accompanies message DSNU299I,
which can provide additional information.
System action
The utility job step that caused the function to be System action
requested abnormally terminated. The utility job is
placed in the stopped state. The utility job abends. The dump is suppressed.

Determine the failing environment. Review the contents of message DSNU299I and take
the appropriate action.
User response
If the problem persists, contact IBM Support Collect
Examine the SYSLOG for error messages to help • Console output from the system on which the job
determine the cause of the failure. was run, and a listing of the SYSLOG data set for the
data (Collecting data). • SYSPRINT output, including JCL, for the application

were issued. Make sure that MSGLEVEL=(1,1) on the Register 2 or the utility job output might contain
JOB statement so that all diagnostic information is a secondary Db2 reason code that provides more
sent to SYSPRINT. information about the problem. If the secondary
• UTPRINT output, produced by utility invocation of reason code is not documented among the other Db2
SORT. reason codes, notify the system programmer.
Db2 (for 04E and 04F abends). Availability of this Problem determination
dump is dependent on the failing environment. If you suspect an error in Db2, you might need to
• SYSABEND, SYSUDUMP, or SYSMDUMP output. report the problem. For information about identifying
Availability of these dumps is dependent on the and reporting the problem, see Collecting diagnostic
failing environment. data (Collecting data).
• The dump from an execution of the utility with the Collect the following diagnostic items:
DIAGNOSE ALLDUMPS statement in the utility job.
Related information command or SLIP trap exit.
DSNU299I (Db2 Messages) • SYSABEND, SYSUDUMP, or SYSMDUMP output.
00E400D5
executing IFCEREP1.
An attempt to retrieve restart or redo information for were issued. Make sure that MSGLEVEL=(1,1) on the
utility processing was unsuccessful. JOB statement so that all diagnostic information is
sent to SYSPRINT.
System action • UTPRINT output, produced by utility invocation of
SORT.
Utilities processing abends. The abend might be
accompanied by other messages. An SDUMP might be Related concepts
taken. Group buffer pool checkpoint (Db2 Data Sharing
Planning and Administration)
BACKUP SYSTEM (Db2 Utilities)
If the abend code was received for the BACKUP
SYSTEM utility, try running BACKUP SYSTEM again. If 00E400E0
the abend occurs repeatedly, review the checkpoint
frequency of each Db2 member and the group
bufferpool checkpoint frequency. Consider adjusting Explanation
them to make them uniform with each other. An attempt to modify the catalog information was
If register 2 or the utility job output contains an unsuccessful.
undocumented reason code, it is an internal IBM code.
Collect the information that is identified in the problem System action
determination section and contact IBM Support.
User response might be taken.
Check the other messages in the utility job output to
determine the cause of the error. If possible, correct System programmer response
the problem and restart the utility. If the error prevents
the utility from completing, terminate the utility and If DSNT500I was not issued and register 2 contains an
start it again from the beginning. undocumented reason code, it is an internal IBM code.
Collect the information that is identified in the problem

Correct the "resource unavailable" condition that was If DSNT500I was not issued and register 2 contains an
identified by the DSNT500I message. Either restart the undocumented reason code, it is an internal IBM code.
utility from the last checkpoint, or terminate the utility Collect the information that is identified in the problem
and start it again from the beginning. determination section and contact IBM Support.
a secondary Db2 reason code that gives more User response
Correct the "resource unavailable" condition that was
reason code is not documented among the other Db2
identified by the DSNT500I message. Either restart the
reason codes, notify the system programmer.
utility from the last checkpoint, or terminate the utility
and start it again from the beginning.
If you suspect an error in Db2, you might need to a secondary Db2 reason code that gives more
report the problem. For information about identifying information about the problem. If the secondary
and reporting the problem, see Collecting diagnostic reason code is not documented among the other Db2
data (Collecting data). reason codes, notify the system programmer.
• SVC dump (or system dump), taken to SYS1.DUMPxx and reporting the problem, see Collecting diagnostic
data set, as result of an operator-initiated dump data (Collecting data).
command or SLIP trap exit. Collect the following diagnostic items:
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • Console output from the system on which the job
• Listing of SYS1.LOGREC data set, obtained by was run, and a listing of the SYSLOG data set for the
executing IFCEREP1. period of time that spans the failure.
• SYSPRINT output, including JCL, for the application • SVC dump (or system dump), taken to SYS1.DUMPxx
program or batch job, and system messages that data set, as result of an operator-initiated dump
were issued. Make sure that MSGLEVEL=(1,1) on the command or SLIP trap exit.
JOB statement so that all diagnostic information is • SYSABEND, SYSUDUMP, or SYSMDUMP output.
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of executing IFCEREP1.
SORT.
Related information program or batch job, and system messages that
DSNT500I (Db2 Messages) were issued. Make sure that MSGLEVEL=(1,1) on the
00E400E1 sent to SYSPRINT.
Explanation SORT.
An attempt to modify one of the real-time statistics Related information
tables in the catalog information was unsuccessful. DSNT500I (Db2 Messages)
System action 00E400E2

Explanation
might be taken. An error was detected while attempting to read a row
from the SYSIBM.SYSPENDINGDDL table.

System action If message DSNT500I is not issued: Register
2 contains a secondary Db2 reason code that
Utilities processing terminates. Message DSNT500I provides more information about the problem.
might be issued, and an SDUMP might be taken. Take the appropriate action for this reason code.
If no information is available, notify the system
System programmer response programmer.
If the condition cannot be corrected, determine the Related information
failing environment. If you suspect an error in Db2, DSNT500I (Db2 Messages)
about identifying and reporting the problem, see 00E400E4
Explanation
User response An attempt to modify the catalog information
If message DSNT500I is issued: Correct the "resource was unsuccessful. The RBA_FORMAT column in
unavailable" condition that is identified by the SYSINDEXPART or SYSTABLEPART could not be
message. Terminate the utility and start it again from updated. This column is informational, indicating
the beginning. whether the object is or is not in extended RBA format.
If message DSNT500I is not issued: Register
2 contains a secondary Db2 reason code that System action
provides more information about the problem. Utilities processing abends. The abend might be
Take the appropriate action for this reason code. accompanied by message DSNT500I. An SDUMP
If no information is available, notify the system might be taken.
programmer.
If the failing utility is a REBUILD INDEX during
Related information
a Disaster Recovery, this abend might be avoided
DSNT500I (Db2 Messages) by modifying the REBUILD INDEX statement.
Terminate the utility and resubmit it by specifying
00E400E3 RBALRSN_CONVERSION NONE on the REBUILD
INDEX statement. Alternatively, contact IBM Support
Explanation for guidance on preventing object conversion by Db2
utilities, and how to remove the workaround when the
An error was detected while materializing pending
Disaster Recovery is completed.
definition changes.

System action
If DSNT500I was not issued and register 2 contains an
Utilities processing terminates. Message DSNT500I
undocumented reason code, it is an internal IBM code.
might be issued.
Collect the information that is identified in the problem
If the condition cannot be corrected, determine the User response
failing environment. If you suspect an error in Db2, Correct the resource unavailable condition that was
you might need to report the problem. For information identified by the DSNT500I message. Either restart the
about identifying and reporting the problem, see utility from the last checkpoint, or terminate the utility
Collecting diagnostic data (Collecting data). and start it again from the beginning.
User response a secondary Db2 reason code that gives more
If message DSNT500I is issued: Correct the "resource
reason code is not documented among the other Db2
unavailable" condition that is identified by the
reason codes, notify the system programmer.
message. Terminate the utility and start it again from
the beginning.

Collect the following diagnostic items: were issued. Make sure that MSGLEVEL=(1,1) on the
period of time that spans the failure. • Dynamic dump, taken to SYS1.DUMPxx data set, by
• SVC dump (or system dump), taken to SYS1.DUMPxx Db2 (04E and 04F abends).
data set, as result of an operator-initiated dump • SYSABEND, SYSUDUMP, or SYSMDUMP output.
command or SLIP trap exit. Availability of these dumps is dependent on the
• SYSABEND, SYSUDUMP, or SYSMDUMP output. failing environment.
Availability of these dumps is dependent on the Related information
• Listing of SYS1.LOGREC data set, obtained by DSNT500I (Db2 Messages)
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application 00E40100
were issued. Make sure that MSGLEVEL=(1,1) on the Explanation
sent to SYSPRINT. Db2 failed during execution of the DSNBGETP macro.
SORT. System action
Related information The utility job step that caused the function to be
DSNT500I (Db2 Messages) requested is abended. The utility job is placed in the
stopped state.
00E400E5
Explanation Determine the failing environment. If the problem is
An error occurred while attempting to invalidate the caused by a resource that is unavailable, resolve the
dynamic statement cache for a table space, table, or unavailable resource and run the utility again.If you
index. suspect an error in Db2, you might need to report
Utility processing abends.
User response
If the error is caused by a 'resource unavailable'
condition, try to identify a related DSNT500I or Problem determination
DSNT376I message in the console output for
problem determination. Ensure that other applications This is problem can be caused by a resource not
have performed a commit operation, or START available condition or it can be an internal error.
DYNQUERYCAPTURE commands have completed. Collect the following diagnostic items:
Then, try the request again.
If no apparent reason can be found for this error, was run, and a listing of the SYSLOG data set for the
contact IBM Support. period of time that spans the failure.
sent to SYSPRINT.

• UTPRINT output, produced by utility invocation of 00E40102
SORT.
dump is dependent on the failing environment. The data manager subcomponent of Db2 failed during
execution of the DSNICCOB macro.
failing environment. System action
00E40101 The utility job step that caused the function to be
stopped state.
Explanation
Db2 failed during execution of the DSNBSETW macro. System programmer response
The utility job step that caused the function to be For information about identifying and reporting the
requested is abended. The utility job is placed in the problem, see Collecting diagnostic data (Collecting
stopped state. data).

Determine the failing environment. If you suspect an Notify the system programmer.
data). This is an internal error.
executing IFCEREP1.
sent to SYSPRINT.
SORT.
executing IFCEREP1.
sent to SYSPRINT. Availability of these dumps is dependent on the
SORT. 00E40103
The data manager subcomponent of Db2 failed during
• SYSABEND, SYSUDUMP, or SYSMDUMP output. execution of the DSNICCUB macro.

Utility processing is abended. The abend might be The utility job step that caused the function to be
accompanied by message DSNT500I. An SDUMP requested is abended. The utility job is placed in the
might be taken. stopped state.

Correct the 'resource unavailable' condition identified Determine the failing environment. If you suspect an
by the DSNT500I message. Either restart the utility error in Db2, you might need to report the problem.
from the last commit point or terminate the utility and For information about identifying and reporting the
start it again from the beginning. problem, see Collecting diagnostic data (Collecting
data).
information about the problem. If the secondary User response
failing environment. If you suspect an error in Db2, Collect the following diagnostic items:
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of dump is dependent on the failing environment.
• Dynamic dump, taken to SYS1.DUMPxx data set, by Availability of these dumps is dependent on the
Db2 (for 04E and 04F abends). Availability of this failing environment.
Explanation
00E40104 execution of the DSNIDLET macro.

The data manager subcomponent of Db2 failed during Utility processing is abended. The abend might be
execution of the DSNIDISP macro. accompanied by message DSNT500I. An SDUMP
might be taken.

start it again from the beginning. Refer to Resource start it again from the beginning. If DSNT500I was not
types (Db2 Messages) for an explanation of resource issued, register 2 contains a secondary Db2 reason
type codes. code that gives more information about the problem. If
the secondary reason code is not documented in this
Problem determination you might need to report the problem. For information
sent to SYSPRINT.
Explanation
00E40106
execution of the DSNIISRT macro.
Explanation
The data manager subcomponent of Db2 failed during System action
execution of the DSNILRDO macro.
Utility processing is abended. The abend might be
System action might be taken.
accompanied by message DSNT500I. An SDUMP User response
might be taken.

from the last commit point or terminate the utility and types (Db2 Messages) for an explanation of resource
start it again from the beginning. type codes.
If DSNT500I was not issued, register 2 contains If DSNT500I was not issued, register 2 contains
a secondary Db2 reason code that gives more a secondary Db2 reason code that gives more
information about the problem. If the secondary information about the problem. If the secondary
reason code is not documented in this manual, it is reason code is not documented in this manual, it is
an internal IBM code. an internal IBM code.

SORT. SORT.
00E40108 00E40109
The data manager subcomponent of Db2 failed during The data manager subcomponent of Db2 failed during
execution of the DSNINEXH macro. execution of the DSNIPGER macro.

Utility processing is abended. The abend might be Utility processing is abended. The abend might be
accompanied by message DSNT500I. An SDUMP accompanied by message DSNT500I. An SDUMP

start it again from the beginning. Refer to Resource start it again from the beginning. Refer to Resource

types (Db2 Messages) in for an explanation of resource If DSNT500I was not issued, register 2 contains
type codes. a secondary Db2 reason code that gives more
sent to SYSPRINT.
SORT. Db2 (for 04E and 04F abends). Availability of this
Availability of these dumps is dependent on the 00E4010B
00E4010A Explanation
Db2 failed during execution of the DSNIPZOP macro.
Explanation
Db2 failed during execution of the DSNIPSCB macro. System action
System action accompanied by message DSNT500I. An SDUMP
might be taken.
might be taken. User response
User response by the DSNT500I message. Either restart the utility
start it again from the beginning.
from the last commit point or terminate the utility and If DSNT500I was not issued, register 2 contains
start it again from the beginning. a secondary Db2 reason code that gives more

If the condition cannot be corrected, determine the about identifying and reporting the problem, see
failing environment. If you suspect an error in Db2, Collecting diagnostic data (Collecting data).
Collecting diagnostic data (Collecting data). • Console output from the system on which the job
• SYSABEND, SYSUDUMP, or SYSMDUMP output. 00E4010D
Explanation
00E4010C
execution of the DSNISETH macro.
Explanation
The data manager subcomponent of Db2 failed during System action
execution of the DSNIREPL macro.
accompanied by message DSNT500I. An SDUMP User response
might be taken.
User response from the last commit point or terminate the utility and
Correct the 'resource unavailable' condition identified start it again from the beginning.
by the DSNT500I message. Either restart the utility If DSNT500I was not issued, register 2 contains
from the last commit point or terminate the utility and a secondary Db2 reason code that gives more
start it again from the beginning. information about the problem. If the secondary
If DSNT500I was not issued, register 2 contains reason code is not documented in this manual, it is
a secondary Db2 reason code that gives more an internal IBM code.

SORT. SORT.
00E4010E 00E4010F
The data manager subcomponent of Db2 failed during The data manager subcomponent of Db2 failed during
execution of the DSNISRCF macro. execution of the DSNIURBA macro.



• SYSPRINT output, including JCL, for the application • Listing of SYS1.LOGREC data set, obtained by
program or batch job, and system messages that executing IFCEREP1.
were issued. Make sure that MSGLEVEL=(1,1) on the • SYSPRINT output, including JCL, for the application
JOB statement so that all diagnostic information is program or batch job, and system messages that
sent to SYSPRINT. were issued. Make sure that MSGLEVEL=(1,1) on the
• UTPRINT output, produced by utility invocation of JOB statement so that all diagnostic information is
SORT. sent to SYSPRINT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by • UTPRINT output, produced by utility invocation of
Db2 (for 04E and 04F abends). Availability of this SORT.
dump is dependent on the failing environment. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. Availability of these dumps is dependent on the
Availability of these dumps is dependent on the failing environment.
00E40111
00E40110
Explanation
Explanation
The data space manager subcomponent of Db2 failed
The data space manager subcomponent of Db2 failed during execution of the DSNPXTND macro.
during execution of the reset of an index space or table
space page set. System action
The utility job is abended. DSM provides diagnostic
System action
information.
The utility job is abnormally terminated. The abend
might be accompanied by message DSNT500I. An System programmer response
SDUMP might be taken.
User response
Correct the 'resource unavailable' condition identified problem, see Collecting diagnostic data (Collecting
by the DSNT500I message. Either restart the utility or data).
terminate the utility and submit it again.

period of time that spans the failure. • UTPRINT output, produced by utility invocation of
were issued. Make sure that MSGLEVEL=(1,1) on the • SYSABEND, SYSUDUMP, or SYSMDUMP output.
JOB statement so that all diagnostic information is Availability of these dumps is dependent on the
sent to SYSPRINT. failing environment.
00E40113
SORT.
dump is dependent on the failing environment. The data space manager subcomponent of Db2 failed
• SYSABEND, SYSUDUMP, or SYSMDUMP output. during execution of the reset of an index space or table
Availability of these dumps is dependent on the space page set.
The utility job is abnormally terminated. The abend
Explanation might be accompanied by message DSNT500I. An
SDUMP might be taken.
DSNUGMAP, a utilities program, failed.

System action
If the condition identified cannot be corrected,
The utility job step that caused the function to be determine the failing environment. If you suspect an
requested is abended. The utility job is placed in the error in Db2, you might need to report the problem.
stopped state. For information about identifying and reporting the

error in Db2, you might need to report the problem. User response
For information about identifying and reporting the Correct the 'resource unavailable' condition identified
problem, see Collecting diagnostic data (Collecting by the DSNT500I message and either restart the
data). utility or terminate the utility and submit it again.
User response a secondary Db2 reason code that will give more
information about the problem. Notify the system
Notify the system programmer. programmer.

This is an internal error. See message DSNT500I in this manual for a 'resource
Collect the following diagnostic items: unavailable' condition.
• SYSPRINT output, including JCL, for the application Db2 (04E and 04F abends).
program or batch job, and system messages that • Listing of SYS1.LOGREC data set, obtained by
were issued. Make sure that MSGLEVEL=(1,1) on the executing IFCEREP1.

program or batch job, and system messages that Availability of these dumps is dependent on the
were issued. Make sure that MSGLEVEL=(1,1) on the failing environment.
00E40115
sent to SYSPRINT.
SORT. Explanation
• SYSABEND, SYSUDUMP, or SYSMDUMP output. The data manager subcomponent of Db2 failed during
Availability of these dumps is dependent on the execution of DSNIUSTP.
Explanation requested is abended. The utility job is placed in the
stopped state.
Db2 failed during execution of DSNICLPS.

System action
The utility job step that caused the function to be error in Db2, you might need to report the problem.
requested is abended. The utility job is placed in the For information about identifying and reporting the
stopped state. problem, see Collecting diagnostic data (Collecting
data).
error in Db2, you might need to report the problem. Notify the system programmer.

executing IFCEREP1.
sent to SYSPRINT. • SYSABEND, SYSUDUMP, or SYSMDUMP output.

Either DSN3SYNC or DSN3ABRT failed. Determine the failing environment. If you suspect an
The utility job step that caused the function to be data).
stopped state.
User response

data).
User response was run, and a listing of the SYSLOG data set for the
executing IFCEREP1.
This is an internal error. program or batch job, and system messages that
• Console output from the system on which the job sent to SYSPRINT.
executing IFCEREP1. Db2 (for 04E and 04F abends). Availability of this
• SYSPRINT output, including JCL, for the application dump is dependent on the failing environment.
were issued. Make sure that MSGLEVEL=(1,1) on the Availability of these dumps is dependent on the
JOB statement so that all diagnostic information is failing environment.
sent to SYSPRINT.
00E40118
SORT.
Explanation
Db2 (for 04E and 04F abends). Availability of this The data space manager subcomponent of Db2 failed
dump is dependent on the failing environment. during execution of the DSNPGNPO macro.
The utility job is abended. The DSM provides any
00E40117 required diagnostic information, such as messages,
dumps, or log records.
Explanation
DSNURBXB, a utilities module, failed.
The utility job step that caused the function to be problem, see Collecting diagnostic data (Collecting
requested is abended. The utility job is placed in the data).
stopped state.

Notify the system programmer. Determine the failing environment. If you suspect an
This is an internal error. data).
00E40119
Explanation Make sure the SYSLGRNX table space is not empty
before applying the log.
This abend reason code is issued in these instances:
• During recovery, a full image copy was not found for
the Db2 directory or the Db2 catalog table space. • Console output from the system on which the job
• The MERGECOPY utility did not recognize a record was run, and a listing of the SYSLOG data set for the
from the SYSIBM.SYSCOPY catalog table. period of time that spans the failure.
executing IFCEREP1.
System action
The utility job is abended. program or batch job, and system messages that
Operator response JOB statement so that all diagnostic information is
sent to SYSPRINT.
• Listings of SYSIBM.SYSCOPY and either
SYSIBM.SYSLGRNX, SYSLGRNG, or both.
Determine the failing environment. If you suspect an Db2 (for 04E and 04F abends). Availability of this
error in Db2, you might need to report the problem. dump is dependent on the failing environment.
problem, see Collecting diagnostic data (Collecting 00E4011B
data).
Explanation
Problem determination The data manager subcomponent of Db2 failed during
When the recovery of the Db2 catalog or directory the execution of DSNIHDFM or DSNIHIFM.
table space is requested, make sure that a full image
copy has been taken first. If the MERGECOPY utility System action
abended, either issue a select statement or run the
REPORT utility to check the SYSIBM.SYSCOPY table for Utility processing is abended. The abend might be
invalid rows. accompanied by message DSNT500I. An SDUMP
might be requested.
00E4011A
User response
Explanation
An error occurred in the RECOVER utility while by the DSNT500I message. Either restart the utility or
applying log with log RBA=0. terminate the utility and execute it from the beginning.
System action a secondary Db2 reason code that gives more
The utility job is abended. information about the problem. If the secondary
Operator response

Problem determination • Db2 log output, including any Db2 recovery log
archive tapes.
failing environment. If you suspect an error in Db2, • Listings of SYSIBM.SYSCOPY and either
you might need to report the problem. For information SYSIBM.SYSLGRNX, SYSLGRNG, or both.
about identifying and reporting the problem, see • Dynamic dump, taken to SYS1.DUMPxx data set, by
Collecting diagnostic data (Collecting data). Db2 (for 04E and 04F abends). Availability of this
• Console output from the system on which the job Availability of these dumps is dependent on the
was run, and a listing of the SYSLOG data set for the failing environment.
00E4011D
executing IFCEREP1.
Explanation
00E4011C
Db2 detected an error during execution of the
DSNIDDRN macro. This is an internal error.
Explanation
The log manager subcomponent of Db2 failed during System action
execution of the DSNJLGR macro.
System action
stopped state.
requested is abended. The utility job is placed in the System programmer response
stopped state.
Register 2 contains a secondary reason code. If the problem, see Collecting diagnostic data (Collecting
secondary reason code is not documented in this data).
User response
failing environment. If you suspect an error in Db2, Problem determination
period of time that spans the failure. Db2 (04E and 04F abends).
• Listing of SYS1.LOGREC data set, obtained by • SYSABEND, SYSUDUMP, or SYSMDUMP output.
executing IFCEREP1. • Detailed description of events immediately prior to
• Listing of Db2 log output. and during the abend.
• Contents of the BSDS (both copies if dual BSDS • SYSPRINT output, including JCL, for the application
in use) obtained by using the Db2 print log map program or batch job, and system messages that
(DSNJU004) utility. were issued. Make sure that MSGLEVEL=(1,1) on the
were issued. Make sure that MSGLEVEL=(1,1) on the • REPAIR dump of all SYSUTIL pages.
sent to SYSPRINT.

period from the last IPL to the time of the failure. If the condition cannot be corrected, determine the
00E4011F you might need to report the problem. For information
Explanation Collecting diagnostic data (Collecting data).
The RECOVER utility is unable to clear the group buffer Collect the following diagnostic items:
pool pending status. • Console output from the system on which the job
The RECOVER utility abends with this code.
executing IFCEREP1.
If you suspect an error in Db2, you might need to were issued. Make sure that MSGLEVEL=(1,1) on the
report the problem. For information about identifying JOB statement so that all diagnostic information is
and reporting the problem, see Collecting diagnostic sent to SYSPRINT.
data (Collecting data). • UTPRINT output, produced by utility invocation of
Collect the following diagnostic items: SORT.
was run, and a listing of the SYSLOG data set for the Db2 (for 04E and 04F abends). Availability of this
period of time that spans the failure. dump is dependent on the failing environment.
Db2 (04E and 04F abends). Availability of these dumps is dependent on the
executing IFCEREP1. 00E40121
00E40120
Explanation
Explanation A RDJFCB macro invocation returned a nonzero return
code.
A delete of SYSLGRNX information failed during -TERM
UTILITY command processing for a REORG utility in
the RELOAD phase. System action
System action
Utility processing is abended. The abend might be System programmer response
accompanied by message DSNT500I. An SDUMP Determine the failing environment. If you suspect an
might be taken. error in Db2, you might need to report the problem.
User response problem, see Collecting diagnostic data (Collecting
data).
from the last commit point or terminate the utility and User response
start it again from the beginning. This is probably a user error. A DD statement might be
If DSNT500I was not issued, register 2 contains missing or specified incorrectly. If the DD statements
a secondary Db2 reason code that gives more appear to be correct, there might be another cause
information about the problem. If the secondary of the error and you should notify the system
reason code is not documented in this manual, it is programmer.

The DD statement referred to by the COPYDDN Utility The RECOVER TABLESPACE utility cannot access
keyword might be missing or specified incorrectly. If the SYSIBM.SYSVOLUMES catalog table to process
COPYDDN was not specified, a DD statement with a a concurrent copy produced by the DFDSS DUMP
default name equal to SYSCOPY must be present in the command.
job step.
The RECOVER TABLESPACE utility abends.
Explanation
A IEFAB4UV invocation returned a nonzero return System programmer response
code. Resolve the access problem to the SYSVOLUMES
catalog table. Then restart the RECOVER TABLESPACE
System action utility.
Processing is abnormally terminated.
Operator response See the console for additional diagnostic messages.
error in Db2, you might need to report the problem. • Dynamic dump, taken to SYS1.DUMPxx data set, by
For information about identifying and reporting the Db2 (04E and 04F abends).
problem, see Collecting diagnostic data (Collecting • Listing of SYS1.LOGREC data set, obtained by
data). executing IFCEREP1.
A down level internal control block was detected.
System action
• Listing of SYS1.LOGREC data set, obtained by The utility job step that requested the function is
executing IFCEREP1. abended. The abend is accompanied by message
DSNU424I.
were issued. Make sure that MSGLEVEL=(1,1) on the System programmer response
JOB statement so that all diagnostic information is Refer to the APAR mentioned in message DSNU424I.
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of User response
SORT.
Refer to the APAR mentioned in message DSNU424I.
User response
Refer to the APAR mentioned in message DSNU424I.
00E40123
00E40125

The RECOVER utility was recovering an index space The RECOVER INDEX/INDEXSPACE utility abends.
with index versioning active. The utility issued the
DSNDBIXD macro which calls the Index Manager System programmer response
subcomponent. An error occurred while the Index
Manager was building an internal control block. Determine the failing environment.
The RECOVER INDEX/INDEXSPACE utility abends.

User response
Determine the failing environment. For information on
identifying and reporting the problem., see Diagnostic
aids for single systems and data sharing (Diagnosing
Db2 problems). Problem determination
User response
executing IFCEREP1.
sent to SYSPRINT.
00E40163
Explanation
Availability of these dumps is dependent on the An error was detected during activity history recording
failing environment. insert of SYSIBM.SYSLGRNG or SYSLGRNX.
00E40126
System action
Explanation Processing is abended.
The RECOVER utility was recovering an index space
with index versioning active. The utility issued the System programmer response
DSNDIDPB macro which calls the Index Manager
subcomponent. An error occurred while the Index
Manager was building the Index Descriptor Page.

data).
User response period of time that spans the failure.
executing IFCEREP1.
This is an internal error. were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
sent to SYSPRINT. 00E40165
SORT. Explanation
An error was detected during an execution unit switch
while performing application history recording or drop
processing.
System action
00E40164

Explanation
An error was detected during activity history recording
update of SYSIBM.SYSLGRNG or SYSLGRNX.
System action data).
User response
error in Db2, you might need to report the problem. Problem determination
data). Collect the following diagnostic items:
executing IFCEREP1.

sent to SYSPRINT.
00E40167
Explanation
00E40166
A delete of SYSIBM.SYSCOPY information failed during
DROP processing.
Explanation
A delete of SYSIBM.SYSLGRNX information failed System action
during DROP processing.
System action
accompanied by message DSNT500I. An SDUMP Determine the failing environment. If you suspect an
might be taken. error in Db2, you might need to report the problem.
User response
data).
by the DSNT500I message. Either restart the utility User response
start it again from the beginning. Notify the system programmer.
a secondary Db2 reason code that gives more Problem determination
information about the problem. If the secondary This is an internal error.
an internal IBM code. Collect the following diagnostic items:
failing environment. If you suspect an error in Db2, • Listing of SYS1.LOGREC data set, obtained by
you might need to report the problem. For information executing IFCEREP1.
about identifying and reporting the problem, see • SYSPRINT output, including JCL, for the application
Collecting diagnostic data (Collecting data). program or batch job, and system messages that
• Console output from the system on which the job sent to SYSPRINT.
SORT.
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application dump is dependent on the failing environment.

failing environment. The COPY or RECOVER utility was executing in
PARALLEL mode. An error occurred in the data
00E40168 transport mechanism while data was being transferred
between the batch and the online Db2 address spaces.
Explanation
The buffer manager (BM) subcomponent of Db2 failed
System action
during the execution of the DSNBPFPP macro. The COPY or RECOVER utility abends.

The utility job step that caused the function to be Determine the failing environment.
stopped state. If you suspect an error in Db2, you might need to
data).
User response This is an internal error.
This is a Db2 subsystem internal error. period of time that spans the failure.
executing IFCEREP1.
• Listing of SYS1.LOGREC data set, obtained by JOB statement so that all diagnostic information is
executing IFCEREP1. sent to SYSPRINT.
• SYSPRINT output, including JCL, for the application • UTPRINT output, produced by utility invocation of
program or batch job, and system messages that SORT.
were issued. Make sure that MSGLEVEL=(1,1) on the • Dynamic dump, taken to SYS1.DUMPxx data set, by
JOB statement so that all diagnostic information is Db2 (for 04E and 04F abends). Availability of this
sent to SYSPRINT. dump is dependent on the failing environment.
• UTPRINT output, produced by utility invocation of • SYSABEND, SYSUDUMP, or SYSMDUMP output.
SORT. Availability of these dumps is dependent on the
• Dynamic dump, taken to SYS1.DUMPxx data set, by failing environment.
00E40189
failing environment. An error was detected while inserting records from
00E40170 SYSIBM.SYSCOPY.

accompanied by message DSNT500I. An SDUMP Explanation
might be requested. An error was detected while deleting records from
SYSIBM.SYSCOPY.
User response
Correct the 'resource unavailable' condition identified System action
by the DSNT500I message. Either restart the utility Utility processing is abended. The abend might be
from the last commit point, or terminate the utility and accompanied by message DSNT500I. An SDUMP
start it again from the beginning. might be requested.
a secondary Db2 reason code that gives more User response
reason code is not documented in this manual, it is Correct the 'resource unavailable' condition identified
an internal IBM code. by the DSNT500I message. Either restart the utility
If the condition cannot be corrected, determine the a secondary Db2 reason code that gives more
failing environment. If you suspect an error in Db2, information about the problem. If the secondary
you might need to report the problem. For information reason code is not documented in this manual, it is
about identifying and reporting the problem, see an internal IBM code.
00E40190 Problem determination
Explanation failing environment. If you suspect an error in Db2,
An error was detected while scanning the you might need to report the problem. For information
SYSIBM.SYSCOPY catalog table. about identifying and reporting the problem, see
accompanied by message DSNT500I. An SDUMP Explanation
might be requested. An invalid call to DSNULOG1 was detected when a
partial recovery function in DSNULOG1 was invoked.
User response The passed parameter is not a TOCOPY or TORBA to
SYSCOPY, SYSUTILX, or DSNDB01.
from the last commit point or terminate the utility and System action
start it again from the beginning. Utility processing is abended.
a secondary Db2 reason code that gives more System programmer response
reason code is not documented in this manual, it is Determine the failing environment. If you suspect an
an internal IBM code. error in Db2, you might need to report the problem.
failing environment. If you suspect an error in Db2, User response
about identifying and reporting the problem, see Notify the system programmer.

This is an internal error. The utility job step that requested the function is
abended. The utility job is placed in the stopped state.
00E40193

Explanation
An error was detected while a utility was attempting
to retrieve catalog table information. This is an internal
error. User response
System action
The utility job is abended. A SYSABEND dump of batch Problem determination
storage and an SVC dump of the database services If you suspect an error in Db2, you might need to
storage are requested. report the problem. For information about identifying
Determine the failing environment. Collect the following diagnostic items:
executing IFCEREP1.
data (Collecting data). • SYSPRINT output, including JCL, for the application
period of time that spans the failure. ,
executing IFCEREP1. 00E40195

program or batch job, and system messages that Explanation
were issued. Make sure that MSGLEVEL=(1,1) on the This is an internal error. An error was detected running
JOB statement so that all diagnostic information is the COPY utility with the SHRLEVEL CHANGE option.
sent to SYSPRINT.
dump is dependent on the failing environment. The utility job step that requested the function is
abended. The utility job is placed in the stopped state.
failing environment. System programmer response
00E40194 Determine the failing environment.

This is an internal error. An error was detected running Notify the system programmer.
the COPY utility with the SHRLEVEL CHANGE option.

and reporting the problem, see Collecting diagnostic • SVC dump (or system dump), taken to SYS1.DUMPxx
data (Collecting data). data set, as result of an operator-initiated dump
• Dynamic dump, taken to SYS1.DUMPxx data set, by program or batch job, and system messages that
Db2 (04E and 04F abends). were issued. Make sure that MSGLEVEL=(1,1) on the
• SYSABEND, SYSUDUMP, or SYSMDUMP output. JOB statement so that all diagnostic information is
program or batch job, and system messages that 00E40197
sent to SYSPRINT. Explanation
00E40196 Db2 detected an error while deleting rows from the
catalog history table.
Explanation
System action
Db2 detected an error while reading the catalog
history tables. Utilities processing is abended. The abend might
might be taken.
System action
Utilities processing is abended. The abend might User response
might be taken. Correct the 'resource unavailable' condition that is
identified by the DSNT500I message, terminate the
utility, and start it again from the beginning.
User response
Correct the 'resource unavailable' condition that is a secondary Db2 reason code that gives more
identified by the DSNT500I message, terminate the information about the problem. If the secondary
utility, and start it again from the beginning. reason code is not documented here, it is an internal
If DSNT500I was not issued, register 2 contains IBM code.
reason code is not documented here, it is an internal
IBM code.
Problem determination about identifying and reporting the problem, see
If the condition cannot be corrected, determine the Collecting diagnostic data (Collecting data).
about identifying and reporting the problem, see • Console output from the system on which the job
Collecting diagnostic data (Collecting data). was run, and a listing of the SYSLOG data set for the

• SYSABEND, SYSUDUMP, or SYSMDUMP output. Related concepts
• Listing of SYS1.LOGREC data set, obtained by How to report recovery information (Db2
executing IFCEREP1. Administration Guide)
• SYSPRINT output, including JCL, for the application Related reference
program or batch job, and system messages that -TERM UTILITY (Db2) (Db2 Commands)
were issued. Make sure that MSGLEVEL=(1,1) on the REPORT (Db2 Utilities)
SORT. Explanation
00E40198 RUNSTATS was unable to reposition and continue
processing after a COMMIT.
Explanation
System action
Db2 detected an error during utility processing of
SYSIBM.SYSLGRNX records for log apply. A SYSLGRNX Utility processing is abended.
record with a log range that is a candidate for log apply
was found for a member that has been destroyed. System programmer response
Log apply processing for this log range is not possible
because the logs and BSDS for a destroyed member Determine the failing environment. If you suspect an
are not available. error in Db2, you might need to report the problem.
System action
data).
The utility job abends and an SVC dump is requested.
User response
Use the TERM UTIL command to terminate the utility.
Run the REPORT utility on all of the objects, and Problem determination
review the output to determine which object has a
SYSLGRNX record for the destroyed member. Choose Collect the following diagnostic items:
a recovery point that will not require logs from the • Console output from the system on which the job
destroyed member to recover the identified object. was run, and a listing of the SYSLOG data set for the
• SVC dump (or system dump), taken to SYS1.DUMPxx sent to SYSPRINT.
command or SLIP trap exit. • UTPRINT output, produced by utility invocation of
SORT.
• Listing of SYS1.LOGREC data set, obtained by Db2 (for 04E and 04F abends). Availability of this
executing IFCEREP1. dump is dependent on the failing environment.
program or batch job, and system messages that Availability of these dumps is dependent on the
were issued. Make sure that MSGLEVEL=(1,1) on the failing environment.
SORT.

An error was detected while scanning a table space or An error was detected in a parameter list passed to the
index during RUNSTATS processing. RUNSTATS message-formatting routine.

Utilities processing is abended. Utilities processing is abended.

If message DSNT500I was issued, refer to that Determine the failing environment. If you suspect an
message for problem determination. Otherwise, this error in Db2, you might need to report the problem.
is an internal error. If you suspect an error in Db2, For information about identifying and reporting the
you might need to report the problem. For information problem, see Collecting diagnostic data (Collecting
about identifying and reporting the problem, see data).
User response
User response
If message DSNT500I was issued, assure that the
indicated resource is available and resubmit the job, Problem determination
otherwise notify the system programmer.
This is an internal error. • Console output from the system on which the job
sent to SYSPRINT.
,
failing environment. 00E40204
Related reference
RUNSTATS (Db2 Utilities) Explanation
Related information An error was detected while attempting to locate the
DSNT500I (Db2 Messages) PB0 control block for a table space partition.
00E40203
System action

User response
executing IFCEREP1.
• Listing of SYS1.LOGREC data set, obtained by • UTPRINT output, produced by utility invocation of
executing IFCEREP1. SORT.
• SYSPRINT output, including JCL, for the application • Dynamic dump, taken to SYS1.DUMPxx data set, by
program or batch job, and system messages that Db2 (for 04E and 04F abends). Availability of this
were issued. Make sure that MSGLEVEL=(1,1) on the dump is dependent on the failing environment.
• UTPRINT output, produced by utility invocation of failing environment.
SORT. 00E40206
• SYSABEND, SYSUDUMP, or SYSMDUMP output. Db2 detected an error while updating the
Availability of these dumps is dependent on the statistics in the SYSIBM.SYSCOLUMNS or
failing environment. SYSIBM.SYSCOLUMNS_HIST catalog table.
,
System action
00E40205
Explanation might be taken.
An error was returned from COMMIT or ABORT
processing during RUNSTATS. User response
Correct the 'resource unavailable' condition that is
System action identified by the DSNT500I message, terminate the
System programmer response a secondary Db2 reason code that gives more
Determine the failing environment. If you suspect an reason code is not documented here, it is an internal
error in Db2, you might need to report the problem. IBM code.
data).

you might need to report the problem. For information • Console output from the system on which the job
about identifying and reporting the problem, see was run, and a listing of the SYSLOG data set for the
Collecting diagnostic data (Collecting data). period of time that spans the failure.
Collect the following diagnostic items: • SVC dump (or system dump), taken to SYS1.DUMPxx
command or SLIP trap exit. • SYSPRINT output, including JCL, for the application
• SYSABEND, SYSUDUMP, or SYSMDUMP output. program or batch job, and system messages that
sent to SYSPRINT.
JOB statement so that all diagnostic information is 00E40208
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of Explanation
SORT.
Db2 detected an error while updating the
00E40207 statistics in the SYSIBM.SYSINDEXPART or
SYSIBM.SYSINDEXPART_HIST Catalog table.
Explanation
Db2 detected an error while updating System action
the statistics in the SYSIBM.SYSINDEXES or Utilities processing is abended. The abend might
SYSIBM.SYSINDEXES_HIST Catalog table. be accompanied by message DSNT500I. An SDUMP
might be taken.
System action
Utilities processing is abended. The abend might User response
be accompanied by message DSNT500I. An SDUMP Correct the 'resource unavailable' condition that is
might be taken. identified by the DSNT500I message, terminate the
User response If DSNT500I was not issued, register 2 contains
Correct the 'resource unavailable' condition that is a secondary Db2 reason code that gives more
identified by the DSNT500I message, terminate the information about the problem. If the secondary
utility, and start it again from the beginning. reason code is not documented in this manual, it is
reason code is not documented here, it is an internal If the condition cannot be corrected, determine the
IBM code. failing environment. If you suspect an error in Db2,

• SVC dump (or system dump), taken to SYS1.DUMPxx • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • SYSPRINT output, including JCL, for the application
sent to SYSPRINT.
00E40210
SORT.
Explanation
00E40209
Db2 detected an error while updating the statistics in
the SYSIBM.SYSTABLES or SYSIBM.SYSTABLES_HIST
Explanation Catalog table.
statistics in the SYSIBM.SYSTABLEPART or System action
SYSIBM.SYSTABLEPART_HIST Catalog table.
be accompanied by message DSNT500I. An SDUMP User response
might be taken.
User response utility, and start it again from the beginning.
Correct the 'resource unavailable' condition that is If DSNT500I was not issued, register 2 contains
identified by the DSNT500I message, terminate the a secondary Db2 reason code that gives more
utility, and start it again from the beginning. information about the problem. If the secondary
If DSNT500I was not issued, register 2 contains reason code is not documented here, it is an internal
a secondary Db2 reason code that gives more IBM code.
reason code is not documented here, it is an internal Problem determination
IBM code.
If the condition cannot be corrected, determine the about identifying and reporting the problem, see
failing environment. If you suspect an error in Db2, Collecting diagnostic data (Collecting data).
Collecting diagnostic data (Collecting data). • Console output from the system on which the job

00E40212
sent to SYSPRINT.
SORT. A 'resource unavailable' condition was detected while
00E40211 attempting to access a catalog table during RUNSTATS
processing.
Explanation
System action
An error was detected while updating the statistics in
the SYSIBM.SYSTABLESPACE Catalog table. Utility processing is abended. The abend will be
might be taken.
System action
Utilities processing is abended. The abend might Operator response
might be taken. Notify the system programmer.

Correct the 'resource unavailable' condition identified If the condition identified cannot be corrected,
by the DSNT500I message, terminate the utility and determine the failing environment and
start it again from the beginning. If you suspect an error in Db2, you might need to
If DSNT500I was not issued, register 2 contains report the problem. For information about identifying
a secondary Db2 reason code that gives more and reporting the problem, see Collecting diagnostic
information about the problem. If the secondary data (Collecting data).
an internal IBM code. User response
Problem determination by the DSNT500I message and restart the utility.
If the condition cannot be corrected, determine the If DSNT500I was not issued, register 2 contains
failing environment. If you suspect an error in Db2, a secondary Db2 reason code that will give more
you might need to report the problem. For information information about the problem. Notify the system
about identifying and reporting the problem, see programmer.
• SVC dump (or system dump), taken to SYS1.DUMPxx period of time that spans the failure.
SORT.

• Dynamic dump, taken to SYS1.DUMPxx data set, by JOB statement so that all diagnostic information is
Db2 (for 04E and 04F abends). Availability of this sent to SYSPRINT.
dump is dependent on the failing environment. • UTPRINT output, produced by utility invocation of
• SYSABEND, SYSUDUMP, or SYSMDUMP output. SORT.
00E40214
Explanation
statistics in the SYSIBM.SYSTABSTATS or
Db2 detected an error while updating SYSIBM.SYSTABSTATS_HIST catalog table.
the statistics in the SYSIBM.SYSCOLDIST or
SYSIBM.SYSCOLDIST_HIST catalog table. System action
Utilities processing is abended. Message DSNT500I
System action
might accompany this abend. An SDUMP might be
Utilities processing is abended. Message DSNT500I taken.
taken. System programmer response
determine the failing environment. If you suspect an
If the condition identified cannot be corrected, error in Db2, If you suspect an error in Db2, you might
determine the failing environment. If you suspect an need to report the problem. For information about
error in Db2, If you suspect an error in Db2, you might identifying and reporting the problem, see Collecting
need to report the problem. For information about diagnostic data (Collecting data).
diagnostic data (Collecting data). User response
User response
Correct the 'resource unavailable' condition that is utility, and start it again from the beginning.
If DSNT500I was not issued, register 2 contains information about the problem. If the secondary
a secondary Db2 reason code that gives more reason code is not documented here, it is an internal
information about the problem. If the secondary IBM code. Notify the system programmer.
IBM code. Notify the system programmer. Problem determination
• SYSABEND, SYSUDUMP, or SYSMDUMP output. executing IFCEREP1.

SORT.
Explanation the SYSIBM.SYSCOLSTATS catalog table.
statistics in the SYSIBM.SYSINDEXSTATS or System action
SYSIBM.SYSINDEXSTATS_HIST catalog table.
System action taken.
might accompany this abend. An SDUMP might be System programmer response
taken.
System programmer response error in Db2, If you suspect an error in Db2, you might
error in Db2, If you suspect an error in Db2, you might
identifying and reporting the problem, see Collecting User response
by the DSNT500I message, terminate the utility, and
User response start it again from the beginning. If DSNT500I was not
issued, register 2 contains a secondary Db2 reason
code that gives more information about the problem. If
manual, it is an internal IBM code. Notify the system
If DSNT500I was not issued, register 2 contains programmer.
IBM code. Notify the system programmer. Collect the following diagnostic items:
SORT.

An error was detected while updating the statistics in Db2 detected an error while updating the
the SYSIBM.SYSCOLDISTSTATS catalog table. statistics in the SYSIBM.SYSLOBSTATS or
SYSIBM.SYSLOBSTATS_HIST Catalog table.
System action
System action
might accompany this abend. An SDUMP might be Utilities processing is abended. The abend might
taken. be accompanied by message DSNT500I. An SDUMP
might be taken.
User response
determine the failing environment. If you suspect an Correct the 'resource unavailable' condition that is
error in Db2, If you suspect an error in Db2, you might identified by the DSNT500I message, terminate the
need to report the problem. For information about utility, and start it again from the beginning.
User response reason code is not documented here, it is an internal
IBM code.
by the DSNT500I message, terminate the utility, and
start it again from the beginning. If DSNT500I was not Problem determination
issued, register 2 contains a secondary Db2 reason
code that gives more information about the problem. If
manual, it is an internal IBM code. Notify the system
programmer.

• SYSABEND, SYSUDUMP, or SYSMDUMP output. executing IFCEREP1.
SORT. 00E40220
00E40218
Explanation
An error was detected while accessing the
SYSIBM.SYSSTOGROUP catalog table during
STOSPACE processing.



SORT. SORT.
00E40221 00E40222
An error was detected while accessing the An error was detected while accessing the
SYSIBM.SYSTABLEPART catalog table. SYSIBM.SYSINDEXPART catalog table during
STOSPACE processing.



SORT. SORT.
00E40223 00E40224
An error was detected while accessing the An error was detected while accessing the
SYSIBM.SYSTABLESPACE catalog table. SYSIBM.SYSINDEXES catalog table during STOSPACE
processing.

Utility processing is abended. The abend might be Utilities processing is abended.
might be taken. System programmer response
User response
Correct the 'resource unavailable' condition identified For information about identifying and reporting the
by the DSNT500I message. Either restart the utility problem, see Collecting diagnostic data (Collecting
from the last commit point or terminate the utility and data).
Collecting diagnostic data (Collecting data). • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
sent to SYSPRINT.
Explanation
Availability of these dumps is dependent on the An error occurred while updating the statistics in the
failing environment. SYSIBM.SKSKEYTARGETSTATS catalog table.
.
System action
00E40225
Explanation taken.
An error has been detected by DSNPSCAT during
STOSPACE processing. System programmer response

For information about identifying and reporting the User response
data). Correct the resource unavailable condition that is
identified by the DSNT500I message. Terminate
the utility, and start it again from the beginning.
User response If DSNT500I was not issued, register 2 contains
Correct the resource unavailable condition identified a secondary Db2 reason code that gives more
by the DSNT500I message. Terminate the utility and information about the problem.
start it again from the beginning. If DSNT500I was not
issued, register 2 contains a secondary Db2 reason Problem determination
code that gives more information about the problem.
This is an internal error. period of time that spans the failure.
Collect the following diagnostic items: • SVC dump (or system dump), taken to SYS1.DUMPxx
command or SLIP trap exit. • SYSPRINT output, including JCL, for the application
• SYSABEND, SYSUDUMP, or SYSMDUMP output. program or batch job, and system messages that
executing IFCEREP1.
sent to SYSPRINT.
SORT.
JOB statement so that all diagnostic information is 00E40228
sent to SYSPRINT.
SORT.
00E40227 the SYSIBM.SYSKEYTGTDISTSTATS catalog table.

An error was detected while updating the Utilities processing is abended. Message DSNT500I
statistics in the SYSIBM.SYSKEYTARGETS or might accompany this abend. An SDUMP might be
SYSIBM.SYSKEYTARGETS_HIST catalog table. taken.

Utilities processing is abended. Message DSNT500I If the condition identified cannot be corrected,
might accompany this abend. An SDUMP might be determine the failing environment. If you suspect an
taken. error in Db2, If you suspect an error in Db2, you might
System programmer response identifying and reporting the problem, see Collecting
For information about identifying and reporting the User response
problem, see Collecting diagnostic data (Collecting Correct the resource unavailable condition identified
data). by the DSNT500I message, terminate the utility, and
start it again from the beginning. If DSNT500I was not

issued, register 2 contains a secondary Db2 reason Problem determination
• SVC dump (or system dump), taken to SYS1.DUMPxx • SYSABEND, SYSUDUMP, or SYSMDUMP output.
executing IFCEREP1.
sent to SYSPRINT.
00E40230
SORT.
Explanation
00E40229
An error was detected while accessing the statistics in
the SYSIBM.SYSTABLES_PROFILES catalog table.
Explanation
An error was detected while updating the System action
statistics in the SYSIBM.SYSKEYTGTDIST or
SYSIBM.SYSKEYTGTDIST_HIST catalog table. Utility processing abends. Message DSNT500I might
accompany this abend. An SDUMP might be
generated.
System action
Utilities processing is abended. Message DSNT500I System programmer response
taken. If the condition identified cannot be corrected,
determine the failing environment.
If the condition identified cannot be corrected, and reporting the problem, see Collecting diagnostic
determine the failing environment. If you suspect an data (Collecting data).
error in Db2, If you suspect an error in Db2, you might
identifying and reporting the problem, see Collecting User response
diagnostic data (Collecting data). If message DSNT500I accompanies this code, correct
the resource unavailable condition identified by the
User response message. Terminate the utility, and start it again from
the beginning.
Correct the resource unavailable condition identified
by the DSNT500I message. Terminate the utility, and If message DSNT500I was not issued, register 2
start it again from the beginning. If DSNT500I was not contains a secondary Db2 reason code that gives more
issued, register 2 contains a secondary Db2 reason information about the problem.

period of time that spans the failure. Determine the failing environment. If you suspect an
• SVC dump (or system dump), taken to SYS1.DUMPxx For information about identifying and reporting the
data set, as result of an operator-initiated dump problem, see Collecting diagnostic data (Collecting
command or SLIP trap exit. data).
executing IFCEREP1.
were issued. Make sure that MSGLEVEL=(1,1) on the Problem determination
JOB statement so that all diagnostic information is This is an internal error.
sent to SYSPRINT.
SORT. • Console output from the system on which the job
00E40231 period of time that spans the failure.
Invalid data was detected while accessing the • SYSPRINT output, including JCL, for the application
statistics in the SYSIBM.SYSCOLSTATS catalog table. program or batch job, and system messages that
sent to SYSPRINT.
Utility processing abends with message DSNU1384I .
SORT.
Message DSNU1384I indicates the invalid column data Db2 (for 04E and 04F abends). Availability of this
that was found in the catalog table. Correct the catalog dump is dependent on the failing environment.
data identified by the message. Terminate the utility, • SYSABEND, SYSUDUMP, or SYSMDUMP output.
and start it again from the beginning. Availability of these dumps is dependent on the
Related tasks failing environment.
Collecting statistics by using Db2 utilities (Db2 00E40301
Performance)
SYSCOLSTATS catalog table (Db2 SQL)
An error was encountered while attempting to obtain
Related information
the high used RBA for the data sets associated with
DSNU1384I (Db2 Messages) the table space being reorganized.
00E40300
System action
Explanation Processing abnormally terminates.
An error occurred in END INDEX LOAD processing
following a sequence of index entry loads. Operator response
System action
The utility job is abended. A SYSABEND dump of batch System programmer response
storage is requested. Determine the reason the high used RBA could not be
obtained, correct the situation, and restart the utility.

The data sets associated with the table space being dump is dependent on the failing environment.
reorganized must be opened in order to obtain the high
used RBA. Ensure that the data sets are available and • SYSABEND, SYSUDUMP, or SYSMDUMP output.
can be opened by the utility. Availability of these dumps is dependent on the
00E40303
• Listing of SYS1.LOGREC data set, obtained by An attempt was made to access the
executing IFCEREP1. SYSIBM.SYSINDEXES catalog table to retrieve the
NAME, CREATOR, TBNAME and TBCREATOR columns.
00E40302 An error was returned from the DSNXKACC protocol
used to access SYSIBM.SYSINDEXES.
Explanation
An error occurred while attempting to force a page set System action
closed. The utility job is abended. Unless a 'resource
unavailable' condition was indicated, a SYSABEND
System action dump of batch storage is requested.
The utility job is abended. A SYSABEND dump of batch

storage is requested. System programmer response
Determine the failing environment. If you suspect an problem, see Collecting diagnostic data (Collecting
error in Db2, you might need to report the problem. data).
data). User response
If a 'resource unavailable' message was issued,
User response refer to the description for that message. If the
unavailable resource becomes available, the utility
Notify the system programmer. step is restartable.

This is an internal error. This might be an internal error.
SORT. SORT.

dump is dependent on the failing environment. An error occurred during the reset of an index space or
table space page set or page set partition.
00E40304 The utility job is abended. The abend may be
accompanied by message DSNT500I. The DSNT500I
may be preceded by other related messages on the
Explanation console. An SDUMP may be taken.
An error occurred during key/RID pair delete
processing for a nonclustering index. System programmer response
System action determine the failing environment. If you suspect an
The utility job is abended. A SYSABEND dump of batch error in Db2, you might need to report the problem.
storage is requested. For information about identifying and reporting the
data).
For information about identifying and reporting the Correct the 'resource unavailable' condition identified
problem, see Collecting diagnostic data (Collecting by the DSNT500I message and either restart the
data). utility or terminate the utility and submit it again.
a secondary Db2 reason code that will give more
User response information about the problem. Notify the system
Notify the system programmer. programmer.

This is an internal error. See message DSNT500I in this manual. See the
secondary reason code from register 2.
Db2 (for 04E and 04F abends). Availability of this • Listing of SYS1.LOGREC data set, obtained by
dump is dependent on the failing environment. executing IFCEREP1.
SORT. SORT.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. • Dynamic dump, taken to SYS1.DUMPxx data set, by
Availability of these dumps is dependent on the Db2 (for 04E and 04F abends). Availability of this
failing environment. dump is dependent on the failing environment.
• Listing of SYS1.LOGREC data set, obtained by • SYSABEND, SYSUDUMP, or SYSMDUMP output.
executing IFCEREP1. Availability of these dumps is dependent on the
00E40305
00E40306

An error occurred during a locate or create PSCB for a The utility job is abended. A SYSABEND dump of batch
table space or index space page set. storage is requested.

The utility job is abended. A SYSABEND dump of batch Determine the failing environment. If you suspect an
storage is requested. error in Db2, you might need to report the problem.
data).
User response
data).
User response
This is an internal error. period of time that spans the failure.
executing IFCEREP1.
An error occurred while attempting to allocate or
00E40307 deallocate storage for the table space record buffer.

An error occurred during the creation of a dynamic The utility job is abended. A SYSABEND dump of batch
cursor block (CUB) for a table space or index space storage is requested.
page set.

executing IFCEREP1.
sent to SYSPRINT.
SORT.
executing IFCEREP1.
SORT. 00E4030A
A mismatch was found between the total number
• SYSABEND, SYSUDUMP, or SYSMDUMP output. of keys processed during the current phase and the
Availability of these dumps is dependent on the total number of keys expected to be processed in this
failing environment. phase.
00E40309
System action
Explanation The utility job is abnormally terminated, and all target
An error occurred during the construction of an index objects are placed in rebuild pending state. Message
entry. The error occurred while reading the table space DSNU255I was issued earlier to report both the
record, while extracting the key from the table space keys processed and the keys expected. A dump is
record, or while connecting the entry into the index. requested.

The utility job is abended. A SYSABEND dump of batch Determine the failing environment. If you suspect an
storage is requested. error in Db2, you might need to report the problem.
problem, see Collecting diagnostic data (Collecting TERM the utility and re-access the indexes by
data). running REPAIR utility to reset the rebuild pending
states on indexes. Run the CHECK INDEX utility
to determine if any of the affected indexes are
User response inconsistent. Inconsistent indexes may be recovered
Notify the system programmer. by the REBUILD INDEX or RECOVER utility.

If working data set was manipulated by user during period of time that spans the failure.
restart process, make sure it was handled properly.
• Console output from the system on which the job 00E4030C
Explanation
Db2 (04E and 04F abends). An internal error occurred while building the
dictionary.
executing IFCEREP1.
System action
• SYSPRINT output, including JCL, for the application The utility is stopped.
were issued. Make sure that MSGLEVEL=(1,1) on the Operator response
sent to SYSPRINT. If necessary, an operator with SYSOPR authority can
issue the -TERM UTILITY command to release the
• UTPRINT output, produced by utility invocation of resources claimed by the stopped utility.
SORT.
00E4030B System programmer response
A mismatch was found between the total number of For information about identifying and reporting the
records processed during the current phase and the problem, see Collecting diagnostic data (Collecting
total number of records expected to be processed in data).
this phase.
System action Collect the following diagnostic items: listed in
The utility job is abnormally terminated. Message • Console output from the system on which the job
DSNU254I was issued earlier to report the records was run, and a listing of the SYSLOG data set for the
that were processed and the records that were period of time that spans the failure.
expected. A dump is requested.
Determine the failing environment.If you suspect an • Listing of SYS1.LOGREC data set, obtained by
error in Db2, you might need to report the problem. executing IFCEREP1.
problem, see Collecting diagnostic data (Collecting • SYSPRINT output, including JCL, for the application
data). program or batch job, and system messages that
Notify the System Programmer. • UTPRINT output, produced by utility invocation of
SORT.
Problem determination 00E4030D
Make sure that the unload data set was handled
correctly. Explanation
Collect the following diagnostic items: listed in A LOAD or REORG utility detected an index that was
potentially in a physically inconsistent state, which

prohibited the LOAD or REORG utility from completing • The log record implies that before an update, the
its processing for that index. data record was a regular or overflow data record,
but the mapping table implies that the data record
System action was a pointer data record.
The utility job is abended. No SYSABEND dump or SVC

System action
dump is requested.
User response requested abends. The utility job is placed in the
stopped state.
If the abend occurred during REORG utility processing,
all indexes that were not built must be rebuilt
using the Db2 Rebuild Index utility. To determine
which indexes did not complete processing, use This is an internal error. Determine the failing
the Db2 -DISPLAY DATABASE command with the environment. If you suspect an error in Db2, you might
SPACENAM and RESTRICT options. Indexes that have need to report the problem. For information about
not completed processing are in a 'RBDP' (rebuild identifying and reporting the problem, see Collecting
pending) or 'PSRBD' (page set rebuild pending) state. diagnostic data (Collecting data).
Terminate the failed REORG utility using the Db2
-TERM UTIL command. Submit a job to rebuild Problem determination
the inconsistent indexes using the Db2 REBUILD or
RECOVER Index utility. Collect the following diagnostic items:
If the abend occurred during LOAD utility processing, • Console output from the system on which the job
the data might need to be rebuilt if one or more of the was run, and a listing of the SYSLOG data set for the
indexes not built is unique. In that case, rebuilding the period of time that spans the failure.
indexes without first rebuilding the data could cause • Dynamic dump, taken to SYS1.DUMPxx data set, by
error messages for duplicate keys to be issued during Db2 (04E and 04F abends).
the REBUILD utility processing.
executing IFCEREP1.
Message DSNU548I is issued before this abend and • SYSPRINT output, including JCL, for the application
specifies which index was in a 'PSRDB' (page set program or batch job, and system messages that
rebuild pending) state. The LOAD or REORG utility were issued. Make sure that MSGLEVEL=(1,1) on the
could not process an index in such a state and JOB statement so that all diagnostic information is
abnormally terminated. 'PSRDB' is set for secondary sent to SYSPRINT.
indexes of a partitioned table space and indicates
that the index might be physically inconsistent. This • UTPRINT output, produced by utility invocation of
occurs when a Db2 utility physically alters such an SORT.
index during utility processing (that is, during the build 00E4030F
process for that index). If the utility is unable to
complete that process, the index is left in the 'PSRDB'
state and must be rebuilt before Db2 can use it. Explanation
00E4030E After the last iteration of log processing, one or more
index keys in the shadow copy are not unique.
Explanation REORG with SHRLEVEL CHANGE operates as follows:
In REORG with SHRLEVEL CHANGE, during processing 1. Unloads data from the original copy of the area
of the log, a log record is inconsistent with the table (table space or partition) being reorganized
that maps between old and new RIDs. Specifically, one 2. Reloads into a shadow copy of that area
of these is true: 3. Iteratively applies the log (which records
• The log record implies that before an update, the applications' writing of the original copy) to the
data record was a pointer data record, but the shadow copy so that the shadow copy and the
mapping table implies that the data record was a original copy contain the same data
regular or overflow data record. If the table space has any unique indexes, those
indexes will enforce uniqueness of the relevant index

keys in the original copy. Those index keys should also Problem determination
be unique in the shadow copy.
The utility job step that caused the function to be period of time that spans the failure.
requested abends. The utility job is placed in the
stopped state. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
This is an internal error. Determine the failing were issued. Make sure that MSGLEVEL=(1,1) on the
environment. If you suspect an error in Db2, you might JOB statement so that all diagnostic information is
need to report the problem. For information about sent to SYSPRINT.
identifying and reporting the problem, see Collecting • UTPRINT output, produced by utility invocation of
diagnostic data (Collecting data). SORT.
Problem determination Db2 (for 04E and 04F abends). Availability of this
Collect the following diagnostic items: dump is dependent on the failing environment.
• Listing of SYS1.LOGREC data set, obtained by Commit processing failed because of one of the
executing IFCEREP1. following reasons:
• SYSPRINT output, including JCL, for the application • One of the resource managers voted NO.
• The service controller (SC) subcomponent
responded NO on a prepare-to-commit notification.
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of System action
SORT. Utility processing is abended.
00E40310
Explanation Determine the failing environment. If you suspect an
An error occurred during the restart of a LOAD or error in Db2, you might need to report the problem.
REORG utility execution. An appropriate error message For information about identifying and reporting the
is issued. problem, see Collecting diagnostic data (Collecting
data).
System action
User response
The utility is abended.
User response
Respond to the error message issued prior to the
abend by making the correction in the input as The problem might be due to a communication
indicated. Then restart the LOAD or REORG utility error. Refer to the CAUSE field in the corresponding
execution. DSNU016I or DSNU017I message.

Explanation
Related reference
An error occurred while the first or next key entry was
SYSCOPY catalog table (Db2 SQL)
being retrieved from an index.
Related information
System action
00E40312 storage is requested.

An error occurred during abort processing. Determine the failing environment. If you suspect an
The utility is abended. A SYSABEND dump of batch data).
storage is requested.
User response
data).
This is an internal error. • SYSPRINT output, including JCL, for the application

SORT.
dump is dependent on the failing environment. An error occurred while repositioning the main cursor
block (CUB). The error occurred at the location defined
• SYSABEND, SYSUDUMP, or SYSMDUMP output. by the record identifier (RID) of the last table space
Availability of these dumps is dependent on the record that was retrieved.
Explanation storage is requested.
An error occurred while repositioning the cursor block
(CUB) to the last index entry that was retrieved. System programmer response
The utility job is abended. A SYSABEND dump of batch For information about identifying and reporting the
storage is requested. problem, see Collecting diagnostic data (Collecting
data).
User response
error in Db2, you might need to report the problem. Notify the system programmer.
data).
This is an internal error. executing IFCEREP1.
sent to SYSPRINT.
executing IFCEREP1.
SORT.
SORT.
dump is dependent on the failing environment. Explanation
• SYSABEND, SYSUDUMP, or SYSMDUMP output. An error occurred while the first or next record entry
Availability of these dumps is dependent on the was being retrieved from a table space.

The utility job is abended. A SYSABEND dump of batch data).
User response
data).
User response
executing IFCEREP1.
sent to SYSPRINT.
SORT.
Availability of these dumps is dependent on the An error occurred while preparing for or ending a
failing environment. series of data record loads or while attempting a data
00E40317 record load.
One possible cause for this error is that the primary
Explanation space allocation for the shadow data set is too small.
An object descriptor block (OBD) could not be found
for the OBID associated with the object descriptor. System action
The utility job is abended.
System action
The utility job is abended. A SYSABEND dump of batch System programmer response
storage is requested. Determine the failing environment. If you suspect an
System programmer response For information about identifying and reporting the
Determine the failing environment. If you suspect an data).

sent to SYSPRINT.
executing IFCEREP1.
SORT.
SORT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by .
Db2 (for 04E and 04F abends). Availability of this 00E4031A
failing environment. One or more broken pages were detected
in the shadow data set while copying pages
00E40319 for the inline copy during REORG TABLESPACE
SHRLEVEL(CHANGE). Message DSNU518I in the job
Explanation output identifies each broken page.
An error occurred while retrieving information from the
SYSIBM.SYSTABLES catalog table. System action
The utility job is abended. An SDUMP of the database
System action services address space (ssnmDBM1) is requested.
storage is requested. System programmer response
Determine the failing environment. If you suspect an problem, see Collecting diagnostic data (Collecting
error in Db2, you might need to report the problem. data).
data). User response
User response
This is an internal error. was run, and a listing of the SYSLOG data set for the

• Listing of SYS1.LOGREC data set, obtained by 3
executing IFCEREP1. In the utilterm phase, it renames the original
• SYSPRINT output, including JCL, for the application data set from the temporary name to the shadow
program or batch job, and system messages that name (for user-managed data sets). It deletes the
were issued. Make sure that MSGLEVEL=(1,1) on the temporary for Db2-managed data sets.
JOB statement so that all diagnostic information is This abend code means that during the switch phase
sent to SYSPRINT. of REORG, one of these errors was detected:
• Definitions of table spaces, tables, and indexes 1
involved in the error. On rename 1, a data set with a temporary name
• REPAIR dump of all SYSUTIL pages. already exists.
• Console output from the system on which the job 2
was run, and a listing of the SYSLOG data set for the On rename 2, a data set with an original name
period from the last IPL to the time of the failure. already exists.
• DSN1COPY-generated copy of the table and index, These error conditions can arise for a Db2-managed or
taken before any recovery is performed. user-managed data set.
• Definitions of table spaces, tables, and indexes Message DSNU360I also appears, with the name of
involved in the error. The object identifiers (OBIDs) the data set and with a context code of 1, or 2.
identified with each table in the table space with the
error can be obtained from SYSIBM.SYSTABLES.
System action
• Copy of the log for this period, so that additional
DSN1LOGP reports can be produced for problem The utility job step that caused the function to be
determination. requested abends. The utility job is placed in the
stopped state.
• Printed contents of the SYSIBM.IPNAMES table.
• Printed contents of the SYSIBM.IPLIST table.
User response
Related information
• Delete the data set and then restart the utility.
00E4031B • TERM the utility. Delete the data set before trying to
execute REORG again with SHRLEVEL REFERENCE or
Explanation CHANGE.
For the area (table space or partition) being 00E4031C
reorganized, REORG with SHRLEVEL REFERENCE or
CHANGE unloads data from the original data sets Explanation
and reloads data into shadow data sets. REORG then
exchanges the names of the original and shadow data For the area (table space or partition) being
sets, using temporary names during the renaming. reorganized, REORG with SHRLEVEL REFERENCE or
CHANGE unloads data from the original data sets
The original name of a data set is in the form and reloads data into shadow data sets. REORG then
catname.DSNDBx.dbname.psname. I0001.Annn. exchanges the names of the original and shadow data
The shadow name of a data set is in the form sets, using temporary names during the renaming.
catname.DSNDBx.dbname.psname. S0001.Annn.
The temporary name of a data set is in the form The original name of a data set is in the form
catname.DSNDBx.dbname.psname. T0001.Annn. catname.DSNDBx.dbname.psname. I0001.Annn.
REORG uses such data sets for indexes as well as data. The shadow name of a data set is in the form
catname.DSNDBx.dbname.psname. S0001.Annn.
To exchange the names of the original and shadow The temporary name of a data set is in the form
data sets, REORG performs the following renaming: catname.DSNDBx.dbname.psname. T0001.Annn.
1 REORG uses such data sets for indexes as well as data.
In the switch phase, it renames the original data
To exchange the names of the original and shadow
set from the original name to the temporary name
data sets, REORG performs the following renaming:
2
1
In the switch phase, it renames the shadow data
In the switch phase, it renames the original data
set from the shadow name to the original name
set from the original name to the temporary name

2 Problem determination
In the switch phase, it renames the shadow data
set from the shadow name to the original name Collect the following diagnostic items:
3 • Console output from the system on which the job
In the utilterm phase, it renames the original was run, and a listing of the SYSLOG data set for the
data set from the temporary name to the shadow period of time that spans the failure.
name (for user-managed data sets). It deletes the • SVC dump (or system dump), taken to SYS1.DUMPxx
temporary for Db2-managed data sets. data set, as result of an operator-initiated dump
If a -TERM UTILITY is issued after any renaming, the command or SLIP trap exit.
-TERM UTILITY undoes the renaming that the REORG • SYSABEND, SYSUDUMP, or SYSMDUMP output.
performed by renaming: • Listing of SYS1.LOGREC data set, obtained by
4 executing IFCEREP1.
The original data set from the shadow name to the • IDCAMS LISTCAT output for the ICF (VSAM) catalog
temporary name that contains the Db2 subsystem catalog that
5 defined the failing index or table.
The shadow data set from the original name to the • VTOC listing of the disk volume on which the failing
shadow name operation occurred.
6 • SYSPRINT output, including JCL, for the application
The original data set from the temporary name to program or batch job, and system messages that
the original name were issued. Make sure that MSGLEVEL=(1,1) on the
During REORG, or during -TERM UTILITY, an attempt JOB statement so that all diagnostic information is
to rename a data set failed due to a system problem. sent to SYSPRINT.
This error condition can arise for a Db2-managed or 00E40320
user-managed data set.
Message DSNP027I also appears, with the old and Explanation
new names of the data set and with other information.
A failure occurred while attempting to restart the
RELOAD phase of the LOAD or REORG utility.
System action
The job step that caused the function to be requested System action
abends. The utility job or the -TERM UTILITY
command is placed in the stopped state. The utility job is abended. A SYSABEND dump of batch
This is an internal error. Determine the failing
environment. If you suspect an error in Db2, you might Determine the failing environment. If you suspect an
need to report the problem. For information about error in Db2, you might need to report the problem.
identifying and reporting the problem, see Collecting For information about identifying and reporting the
diagnostic data (Collecting data). problem, see Collecting diagnostic data (Collecting
data).
User response
User response
If this condition arises during renaming 1, 2, or 3, and
you can correct the problem. Choose between these Notify the system programmer.
actions:
• Correct the problem and then RESTART the utility. Problem determination
• TERM the utility. This is an internal error.
If this condition arises during renaming 1, 2, or 3, and Collect the following diagnostic items:
you cannot correct the problem, TERM the utility and
notify the system programmer.
If this condition arises during renaming 4, 5, or 6, period of time that spans the failure.
notify the system programmer.

SORT.
00E40322
dump is dependent on the failing environment. Explanation
• SYSABEND, SYSUDUMP, or SYSMDUMP output. An error occurred while attempting to add an entry to
Availability of these dumps is dependent on the an index.
Processing of the index for which the error occurred
Explanation is terminated. The index is internally identified as an
unavailable resource. A utility error message identifies
An error occurred while retrieving information from the the index for which the error occurred. An SVC dump
SYSIBM.SYSCOLUMNS catalog table. of the database services storage is requested but
will be suppressed if a previous 'resource unavailable'
System action message has been issued to document the condition.
The processing of index entries for other indexes
The utility job is abended. A SYSABEND dump of batch proceeds.

Determine the failing environment. If you suspect an error in Db2, you might need to report the problem.
error in Db2, you might need to report the problem. For information about identifying and reporting the
For information about identifying and reporting the problem, see Collecting diagnostic data (Collecting
problem, see Collecting diagnostic data (Collecting data).
data).
User response
User response
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application program or batch job, and system messages that
program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the
were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is
JOB statement so that all diagnostic information is sent to SYSPRINT.
sent to SYSPRINT.
SORT.

• Dynamic dump, taken to SYS1.DUMPxx data set, by For information about identifying and reporting the
Db2 (for 04E and 04F abends). Availability of this problem, see Collecting diagnostic data (Collecting
dump is dependent on the failing environment. data).
Availability of these dumps is dependent on the User response
00E40323
Explanation
An error occurred during the execution of a LOAD
or REORG utility. Prior to this abend, error messages
identifying the specific problem were issued. The • Console output from the system on which the job
abend is issued so that work data sets, which will be was run, and a listing of the SYSLOG data set for the
needed if the utility is restarted, are saved. period of time that spans the failure.
System action executing IFCEREP1.
Utility processing is abended. No SYSABEND dump or • SYSPRINT output, including JCL, for the application
SVC dump is requested. program or batch job, and system messages that
Respond to the error messages issued prior to the • Dynamic dump, taken to SYS1.DUMPxx data set, by
abend. Correct the input and either -TERM the utility Db2 (for 04E and 04F abends). Availability of this
and resubmit it or resubmit the utility with the dump is dependent on the failing environment.
RESTART parameter. If you suspect an error in Db2,
00E40325
Explanation
When work data sets are used and the
disposition is MOD, DELETE, and CATLG, An error occurred during the construction of an index.
(DISP=(MOD,DELETE,CATLG)), this abend still allows The error occurred while loading the index entries into
you to restart the utility. Refer to the prior error the index page set.
messages to determine how to correct the problem.
Explanation storage and an SVC dump of the database services
storage are requested.
An error occurred during the construction of an index
entry. The error occurred while extracting the key from
the table space. System programmer response
storage and an SVC dump of the database services
data).
User response

This is an internal error. were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
period of time that spans the failure. Db2 (for 04E and 04F abends). Availability of this
executing IFCEREP1. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• SYSPRINT output, including JCL, for the application failing environment.
were issued. Make sure that MSGLEVEL=(1,1) on the 00E40327
sent to SYSPRINT. Explanation
An error occurred when Db2 retrieved information
from the SYSIBM.SYSXMLRELS catalog table.
System action
failing environment. The utility job abnormally terminates. Db2 requests a
SYSABEND dump of batch storage.
00E40326

An error occurred during the construction of an index.
The error occurred during sort.
storage and an SVC dump of the database services User response

For information about identifying and reporting the • Console output from the system on which the job
problem, see Collecting diagnostic data (Collecting was run, and a listing of the SYSLOG data set for the
data). period of time that spans the failure.
User response executing IFCEREP1.
Notify the system programmer. • SYSPRINT output, including JCL, for the application
Problem determination JOB statement so that all diagnostic information is
This is an internal error. sent to SYSPRINT.
Collect the following diagnostic items: • UTPRINT output, produced by utility invocation of
SORT.
executing IFCEREP1.

• SYSABEND, SYSUDUMP, or SYSMDUMP output. Problem determination
failing environment. If this abend is due to an unavailable resource,
message DSNT500I provides sufficient problem
Related reference determination and correction information. Register 2
SYSXMLRELS catalog table (Db2 SQL) contains a secondary reason code that might provide
additional information.
00E40333
00E40335
Explanation
Explanation
An error occurred while attempting a forced write of
RELOAD phase data buffers. An error has been detected while attempting to read a
row from the SYSIBM.SYSRELS table.
System action
System action
RELOAD phase processing is terminated. An SDUMP of
the database services address space (ssnmDBM1) is The utility job is abended.
requested.
System programmer response Determine the failing environment. If you suspect an
data).
00E40334
User response
Explanation
LOAD or REORG utility processing was attempting
to retrieve COLUMN information from the This is an internal error.
SYSIBM.SYSFIELDS catalog table when an error was
detected.
Utility processing is abended. An SDUMP is requested
unless this abend is accompanied by a DSNT500I
message written to the SYSPRINT data set.
System programmer response sent to SYSPRINT.
Correct the indicated error, if possible, and resubmit • Dynamic dump, taken to SYS1.DUMPxx data set, by
the terminated utility job with the RESTART parameter. Db2 (for 04E and 04F abends). Availability of this
If the problem can not be corrected, and if you suspect dump is dependent on the failing environment.
an error in Db2, If you suspect an error in Db2, you • SYSABEND, SYSUDUMP, or SYSMDUMP output.
might need to report the problem. For information Availability of these dumps is dependent on the
about identifying and reporting the problem, see failing environment.
00E40336
User response
Explanation
LOAD or REORG utility used the DSNXIFPS protocol to
invoke a field procedure for encode or decode and an

error code was returned that indicates a Db2 internal JOB statement so that all diagnostic information is
error. sent to SYSPRINT.
System action SORT.
Utility processing is abended. An SDUMP is requested. • Dynamic dump, taken to SYS1.DUMPxx data set, by
User response
Notify the system programmer. Availability of these dumps is dependent on the
Problem determination .
This is an internal error. If you suspect an error in Db2, 00E40341
Collecting diagnostic data (Collecting data). Explanation
00E40340 A failure occurred during reset processing for a LOAD
REPLACE or LOAD PART REPLACE utility.
Explanation
System action
The LOAD or REPAIR utility used the DSNXVCCR
protocol to invoke a conversion routine for a date/time The utility job is abended. An SDUMP of the database
data type. An error code was returned that indicates a services address space (ssnmDBM1) is requested.
Db2 internal error.
The utility job is abended. An SDUMP of the database error in Db2, you might need to report the problem.
services address space (ssnmDBM1) is requested. For information about identifying and reporting the
data).
For information about identifying and reporting the Notify the system programmer.
User response
executing IFCEREP1.

Explanation
Availability of these dumps is dependent on the The subtask performing an MVS sort terminated
failing environment. abnormally.
00E40343
System action
Explanation Any error message generated by sort in conjunction
with the abend is directed to the device/data set
The LOAD or REORG utility used the DSNJCKLO identified by the UTPRINT DD statement in the utility
protocol to obtain the current log RBA. An error code job step.
was returned that indicates a Db2 internal error.
Operator response
System action
The utility job is abended. An SDUMP of the database -TERM UTILITY command to release the resources
services address space (ssnmDBM1) is requested. claimed by the stopped utility (this might not be
necessary).
User response
error in Db2, you might need to report the problem. Determine the cause of the error. If the error
For information about identifying and reporting the can be corrected, the utility can be restarted from
problem, see Collecting diagnostic data (Collecting the beginning of the reload phase by using the
data). 'RESTART(PHASE)' parameter. If the error prevents the
utility from completing, the -TERM command should
User response be issued to remove the stopped utility from the
system.
This error can be caused by abend 00E40005 and
This is an internal error. error message DSNU044I issued from the subtask. If
Collect the following diagnostic items: this is the case, correct the error causing the subtask
to abend. In most cases, the error messages from
• Console output from the system on which the job SORT that are sent to the device/data set identified
was run, and a listing of the SYSLOG data set for the by the UTPRINT DD statement identify the problem.
period of time that spans the failure. The dump might not be needed. If SORT is unable
• Listing of SYS1.LOGREC data set, obtained by to open the UTPRINT data set, only the message
executing IFCEREP1. and abend are provided. In this case, correct the
problem associated with the UTPRINT DD statement,
and restart the job with the RESTART(PHASE) option.
were issued. Make sure that MSGLEVEL=(1,1) on the Collect the following diagnostic items:
sent to SYSPRINT.
• UTPRINT output, produced by utility invocation of period of time that spans the failure.
SORT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by executing IFCEREP1.
• SYSABEND, SYSUDUMP, or SYSMDUMP output. were issued. Make sure that MSGLEVEL=(1,1) on the
Availability of these dumps is dependent on the JOB statement so that all diagnostic information is
failing environment. sent to SYSPRINT.
.

• UTPRINT output, produced by utility invocation of JOB statement so that all diagnostic information is
SORT. sent to SYSPRINT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by • UTPRINT output, produced by utility invocation of
Db2 (for 04E and 04F abends). Availability of this SORT.
dump is dependent on the failing environment. • Dynamic dump, taken to SYS1.DUMPxx data set, by
• SYSABEND, SYSUDUMP, or SYSMDUMP output. Db2 (for 04E and 04F abends). Availability of this
Availability of these dumps is dependent on the dump is dependent on the failing environment.
,
00E40346
00E40347
The LOAD or REORG subtask creating a COPY data set
This utility's main task is abending because one of
terminated abnormally.
its subtasks terminated abnormally. The subtask itself
issues an abend before this one is issued.
System action
Any error message generated by the subtask in System action
conjunction with the abend is directed to the device
Any error message generated by the subtask in
and data set identified by the SYSPRINT DD statement
conjunction with the abend is directed to the device
in the utility job step.
and data set identified by the SYSPRINT DD statement
in the utility job step.
Operator response
An operator with SYSOPR authority can issue the Operator response
TERM UTILITY command to release the resources
necessary).
necessary).
User response
Determine the cause of the error. If you can correct User response
the error, restart the utility from the beginning of
Determine the cause of the error in the subtask. If
the reload phase by using the 'RESTART(PHASE)'
you can correct the error, restart the utility from the
parameter. If the error prevents the utility from
beginning of the phase by using the 'RESTART(PHASE)'
completing, issue the -TERM command to remove the
parameter. If the error prevents the utility from
stopped utility from the system.
completing, issue the TERM UTILITY command to
remove the stopped utility from the system.
This error can be caused by out of space situations Problem determination
on the data sets identified by the COPYDDN and
RECOVERYDDN keywords. If this is the case, correct
the data set allocations and restart the job with the • Console output from the system on which the job
RESTART(PHASE) option. was run, and a listing of the SYSLOG data set for the

dump is dependent on the failing environment. Either terminate or restart the utility.
. To restart the utility: Specify the RESTART parameter

on the utility job to restart at the last commit point.
00E40350
To terminate the utility: Use the -TERM UTILITY
command to terminate the utility, then run the CHECK
Explanation LOB utility to identify any LOBs in the LOB table space
An error has been returned from LOB MANAGER insert that are not associated with a row in the base table.
or retrieve. Related tasks
Restarting an online utility (Db2 Utilities)
Utilities processing is abended. -TERM UTILITY (Db2) (Db2 Commands)
CHECK LOB (Db2 Utilities)
User response 00E40353
Register 2 contains a secondary Db2 reason code that
will give more information about the problem. Notify Explanation
An error was detected while reorganizing a LOB table
space.
This is an internal error. System action
Collect the following diagnostic items: Utilities processing is abended.
will give more information about the problem. Notify
executing IFCEREP1.
program or batch job, and system messages that Collect the following diagnostic items:
SORT. Db2 (04E and 04F abends).
00E40351 • SYSABEND, SYSUDUMP, or SYSMDUMP output.
LOAD RESUME YES for a table space containing • SYSPRINT output, including JCL, for the application
a table with CLOB, BLOB or DBCLOB columns program or batch job, and system messages that
cannot be restarted in the RELOAD phase with the were issued. Make sure that MSGLEVEL=(1,1) on the
RESTART(PHASE) parameter. JOB statement so that all diagnostic information is
sent to SYSPRINT.
System action • UTPRINT output, produced by utility invocation of
SORT.
00E40355

An error was detected while unloading or reorganizing Determine the failing environment. If you suspect an
a table space. A seclabel column was found to be in error in Db2, you might need to report the problem.
error. For information about identifying and reporting the

User response

will give more information about the problem. Notify
the system programmer. If the reason code is 24 ('18'X), then the failure is
caused by an incorrect Language Environment (LE)
Problem determination system error.
executing IFCEREP1.
sent to SYSPRINT.
SORT.
An error was detected during REORG processing after
. an ALTER TABLE statement with a DROP COLUMN
clause was issued.
00E40356
System action
Explanation
The utility job is abended. An SYSABEND dump of
The LOAD utility used the DSNXVNUM protocol to batch storage is requested.
invoke a conversion routine for decimal floating-point
data type. An error was returned that indicates an
environmental error. System programmer response
The utility job is abended. An SDUMP of the database problem, see Collecting diagnostic data (Collecting
services address space (ssnmDBM1). data).
User response

This is an internal error. dump is dependent on the failing environment.
Collect the following diagnostic items: • SYSABEND, SYSUDUMP, or SYSMDUMP output.
• Console output from the system on which the job Availability of these dumps is dependent on the
was run, and a listing of the SYSLOG data set for the failing environment.
period of time that spans the failure. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1. • SYSPRINT output, including JCL, for the application
• SYSPRINT output, including JCL, for the application program or batch job, and system messages that
program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the
were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is
JOB statement so that all diagnostic information is sent to SYSPRINT.
sent to SYSPRINT. • UTPRINT output, produced by utility invocation of
• UTPRINT output, produced by utility invocation of SORT.
SORT. • IDCAMS PRINT output of the CDDS data set, or a
• Dynamic dump, taken to SYS1.DUMPxx data set, by copy of the CDDS data set.
failing environment. An error has been detected while scanning for a
specified key in REPAIR by KEY processing.
00E40358
System action
Explanation
An internal error occurred when the compression
dictionary data set (CDDS) was accessed.
The utility is placed in the stopped state. For information about identifying and reporting the
Operator response data).
If the utility is holding resources that are required

by other jobs, issue the -TERM UTILITY command to User response
release the held resources. Notify the system programmer.

Determine the failing environment. If you suspect an This is an internal error.
For information about identifying and reporting the Collect the following diagnostic items:
problem, see Collecting diagnostic data (Collecting • Console output from the system on which the job
data). was run, and a listing of the SYSLOG data set for the
sent to SYSPRINT.

SORT.
dump is dependent on the failing environment. An error has been returned from the get-page function,
DSNBGETP.
00E40403 Utilities processing is abended.

An error has been detected while scanning for Determine the failing environment. If you suspect an
the requested RECORD during REPAIR by record error in Db2, you might need to report the problem.
processing. For information about identifying and reporting the
data).
System action
Utilities processing is abended. User response
Determine the failing environment. If you suspect an Problem determination
data).
User response period of time that spans the failure.
executing IFCEREP1.
sent to SYSPRINT.
SORT.
Explanation
Db2 (for 04E and 04F abends). Availability of this An error has been returned from the open-piece
dump is dependent on the failing environment. function, DSNBOPPP.
failing environment. Utilities processing is abended.

User response
executing IFCEREP1.
SORT. 00E40410
• SYSABEND, SYSUDUMP, or SYSMDUMP output. The data manager protocol DSNISETR returned an
Availability of these dumps is dependent on the error.
System action
00E40406
Explanation
An error has been returned from the replace-page
function, DSNBRELP. Determine the failing environment. If you suspect an
System action
Utilities processing is abended. data).

Determine the failing environment. If you suspect an This is an internal error.
For information about identifying and reporting the 00E40411
data).

An error has been returned from a DSNIDLET dump is dependent on the failing environment.
or DSNODELL protocol during REPAIR DELETE
processing. • SYSABEND, SYSUDUMP, or SYSMDUMP output.
System action
Related reference
Utilities processing is abended. REPAIR (Db2 Utilities)
Related information
System programmer response DSNT500I (Db2 Messages)
error in Db2, you might need to report the problem. 00E40414
problem, see Collecting diagnostic data (Collecting Explanation
data).
An error was detected while trying to determine the
highest member ID in the data sharing environment.
Problem determination This is an internal error.
System action
00E40413
Explanation
An error has been detected by the REPAIR utility.
The utility job step is placed in the stopped state. data (Collecting data).
Message DSNT500I might be issued in conjunction
with this error. 00E40415

A DSNT500I error message issued in conjunction with An error was detected while trying to determine the
this error might indicate a correctable problem. If member name for the data sharing member ID. This is
DSNT500I was issued in conjunction with the error, an internal error.
correct the conditions that it describes and try the
request again. System action
If the DSNT500I message has not been issued or if Utilities processing is abended.
the problem can not be corrected, collect the following
diagnostic items:
• Listing of SYS1.LOGREC data set, obtained by data (Collecting data).
executing IFCEREP1.
00E40417
sent to SYSPRINT.
for the object identifier (OBID) that is associated with
• UTPRINT output, produced by utility invocation of the object descriptor. Either the database descriptor
SORT. (DBD) address or the OBID is zero.

The utility job is abended. A SYSABEND dump of batch Utilities processing is abended.
data).
User response
User response
This abend might be accompanied by one or more
This code identifies an internal error. The name of DSN messages to the operator's console. The DSN
the control section (CSECT) that is involved is given messages might indicate a user error that can be
in VRARRK5. The full CSECT name given in the dump corrected. If DSN messages do not accompany this
title. message, the likely cause of the abend is an internal
error.
executing IFCEREP1. • Listing of SYS1.LOGREC data set, obtained by
program or batch job, and system messages that • SYSPRINT output, including JCL, for the application
were issued. Make sure that MSGLEVEL=(1,1) on the program or batch job, and system messages that
JOB statement so that all diagnostic information is were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT. JOB statement so that all diagnostic information is
SORT. • UTPRINT output, produced by utility invocation of
• Dynamic dump, taken to SYS1.DUMPxx data set, by SORT.
Db2 (for 04E and 04F abends). Availability of this • Dynamic dump, taken to SYS1.DUMPxx data set, by
dump is dependent on the failing environment. Db2 (for 04E and 04F abends). Availability of this
• SYSABEND, SYSUDUMP, or SYSMDUMP output. dump is dependent on the failing environment.
Availability of these dumps is dependent on the • SYSABEND, SYSUDUMP, or SYSMDUMP output.
failing environment. Availability of these dumps is dependent on the
• The DBID and OBID shown in the abend diagnostics failing environment.
that precede the DSNU016I message in the failing 00E40517
utility job step.
00E40500 for the object identifier (OBID) that is associated with
the object descriptor. The failure occurred accessing
the object descriptor for the Db2 Catalog.
Explanation
An error was returned by the reset function,
DSNPRSPS or DSNPREST.

System action the REPAIR DBD utility. The utility terminates and all
work up to the time of abend is backed out.
System action
System programmer response The execution unit driving this function proceeds
normally. A user dump is requested.
For information about identifying and reporting the Operator response
problem, see Collecting diagnostic data (Collecting Notify the system programmer, request the user dump,
data). and print the SYS1.LOGREC, and the BSDS.

Notify the system programmer. If you suspect an error in Db2, If you suspect an
This code identifies an internal error. The name of data).
the control section (CSECT) that is involved is given
in VRARRK5. The full CSECT name given in the dump
title. Problem determination
Collect the following diagnostic items: SYSOUT might contain the record being processed at
the time of abnormal termination.
was run, and a listing of the SYSLOG data set for the The following general purpose registers (GPRs) contain
period of time that spans the failure. the indicated diagnostic information:
• Listing of SYS1.LOGREC data set, obtained by GPR
executing IFCEREP1. Content
• SYSPRINT output, including JCL, for the application 2
program or batch job, and system messages that Address of the error message
were issued. Make sure that MSGLEVEL=(1,1) on the 5
JOB statement so that all diagnostic information is Address of the load table
sent to SYSPRINT.
SORT. • Console output from the system on which the job
dump is dependent on the failing environment. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
Availability of these dumps is dependent on the • SYSABEND, SYSUDUMP, or SYSMDUMP output.
failing environment. Availability of these dumps is dependent on the
• The DBID and OBID shown in the abend diagnostics
that precede the DSNU016I message in the failing 00E40601
utility job step.
DSNU016I (Db2 Messages) There was a utility abend in the Db2 database services
address space (ssnmDBM1).
00E40600
This abend can be issued by either the CATMAINT or
the REPAIR DBD utility. The utility terminates and all
Explanation
work up to the time of abend is backed out. This error
There was a utility abend on the batch side of Db2. occurs when CATMAINT receives a non-zero SQL code
This abend can be issued by either the CATMAINT or when issuing SQL statements to alter the catalog.

System action • SVC dump (or system dump), taken to SYS1.DUMPxx
The execution unit driving this function proceeds command or SLIP trap exit.
normally.
executing IFCEREP1.
Operator response
Related reference
Notify the system programmer, request the SVC dump, CATMAINT (Db2 Utilities)
and print the SYS1.LOGREC, and the BSDS.
REPAIR (Db2 Utilities)
Related information
System programmer response DSNU778I (Db2 Messages)
Check the DSNU778I message in the job output. -601
THE NAME (VERSION OR VOLUME SERIAL
NUMBER) OF THE OBJECT TO BE DEFINED
OR THE TARGET OF A RENAME STATEMENT IS
IDENTICAL TO THE EXISTING NAME (VERSION
OR VOLUME SERIAL NUMBER) object-name OF
If this reason code is issued as the result of running THE OBJECT TYPE object-type
the CATMAINT job during a migration effort, and it is
-904
accompanied by SQL code -601, perform the following
steps:
1. Terminate the CATMAINT job. code, TYPE OF RESOURCE resource-type, AND
2. Fall back to the previous version of Db2 for z/OS. RESOURCE NAME resource-name
3. Drop the object name that is identified by SQL code 00E70081

-601.
00E40609
4. Redefine the object name that is identified by SQL
code -601 with IDCAMS.
Explanation
5. Update to the version of Db2 for z/OS that you are
migrating to. A DBD was encountered which is noncontiguous in
6. Run the CATMAINT job again. the EDM pool due to prior operations and the DBD is
currently accessed by users. The utility requires the
If this reason code is issued as the result of running a DBD to be contiguous in the EDM pool.
REPAIR DBD DIAGNOSE job, you might need to report
the error to IBM software support.
System action
Problem determination The utility that detected this condition returns
"RESOURCE NOT AVAILABLE" to its invoker.
User response
GPR
Allow all SQL access to this database to cease; this will
Content
allow the DBD to be flushed from the EDM pool. After
2 all users have finished accessing the database, invoke
Address of the error message the utility again. A contiguous DBD will be brought into
7 the EDM pool.
Address of CT
00E40617
Check the utility job output for detailed error
messages and resolve them. Explanation
• Console output from the system on which the job for the object identifier (OBID) that is associated with
was run, and a listing of the SYSLOG data set for the the object descriptor. The failure occurred accessing
period of time that spans the failure. the object descriptor for the Db2 Catalog.

The utility job is abended. A SYSABEND dump of batch An error has been detected by CHECK DATA utility
storage is requested. during table scanning processing. The data manager
protocol DSNISRCF has returned an error.
System action
error in Db2, you might need to report the problem. Utility processing is abended.
problem, see Collecting diagnostic data (Collecting System programmer response
data).
User response
Notify the system programmer. problem, see Collecting diagnostic data (Collecting
data).
User response
This code identifies an internal error. The name of
the control section (CSECT) that is involved is given Notify the system programmer.
in VRARRK5. The full CSECT name given in the dump
title. Problem determination
• Listing of SYS1.LOGREC data set, obtained by was run, and a listing of the SYSLOG data set for the
executing IFCEREP1. period of time that spans the failure.
• SYSPRINT output, including JCL, for the application • Listing of SYS1.LOGREC data set, obtained by
program or batch job, and system messages that executing IFCEREP1.
were issued. Make sure that MSGLEVEL=(1,1) on the 00E40703
sent to SYSPRINT.
Explanation
SORT. An error has been detected by CHECK DATA utility
during table scanning processing. The data manager
protocol DSNINXTR has returned an error.
System action
Availability of these dumps is dependent on the Utility processing is abended.
• The DBID and OBID shown in the abend diagnostics System programmer response
that precede the DSNU016I message in the failing
utility job step. Determine the failing environment. If you suspect an
Related information For information about identifying and reporting the
DSNU016I (Db2 Messages) problem, see Collecting diagnostic data (Collecting
data).
00E40702
User response

This is an internal error. Determine the failing environment. If you suspect an
• Console output from the system on which the job problem, see Collecting diagnostic data (Collecting
was run, and a listing of the SYSLOG data set for the data).
executing IFCEREP1.
00E40704
Explanation
The CHECK DATA utility detected an error during table
scanning processing or delete processing. The data
manager protocol DSNISETR returned an error. • Console output from the system on which the job
Utility processing abends. executing IFCEREP1.
System programmer response 00E40706

Explanation
For information about identifying and reporting the The CHECK DATA utility detected an error while
problem, see Collecting diagnostic data (Collecting processing primary keys matching. The data manager
data). protocol DSNKSET returned an error.

Notify the system programmer. Utility processing abended.

This is an internal error. Determine the failing environment. If you suspect an
• Console output from the system on which the job problem, see Collecting diagnostic data (Collecting
was run, and a listing of the SYSLOG data set for the data).
executing IFCEREP1.
00E40705
Explanation
The data manager protocol DSNIEXTK returned an
error.
executing IFCEREP1.

00E40707 Problem determination
Explanation
The CHECK DATA utility detected an error while
processing primary keys matching. The data manager • Console output from the system on which the job
protocol DSNKNEX returned an error. was run, and a listing of the SYSLOG data set for the

executing IFCEREP1.
Utility processing abended.
00E40709

Explanation
error in Db2, you might need to report the problem. An error has been detected by the CHECK DATA
For information about identifying and reporting the utility during positioning of records for cascade delete
problem, see Collecting diagnostic data (Collecting processing. The data manager protocol DSNINEXD has
data). returned an error.

Notify the system programmer. Utilities processing is abended.

This is an internal error. Notify the system programmer.

• Listing of SYS1.LOGREC data set, obtained by For information about identifying and reporting the
executing IFCEREP1. problem, see Collecting diagnostic data (Collecting
00E40708 data).

The CHECK DATA utility detected an error while Correct the error condition identified by the DSNT500I
positioning records for cascade delete processing. The message, terminate the utility and restart it from the
data manager protocol DSNISETD returned an error. beginning.

Utility processing abended. This is an internal error.
For information about identifying and reporting the • Listing of SYS1.LOGREC data set, obtained by
problem, see Collecting diagnostic data (Collecting executing IFCEREP1.
data).
00E4070A
User response

The CHECK DATA utility detected an error during Correct the 'resource unavailable' condition identified
insert records processing. The data manager protocol by the DSNT500I message. Either restart the utility
DSNISRT returned an error. from the last commit point or terminate the utility and
System action types (Db2 Messages) in for an explanation of resource
type codes.
Utility processing abended.
System programmer response information about the problem. If the secondary
Determine the failing environment. If you suspect an reason code is not documented in this manual, it is
error in Db2, you might need to report the problem. an internal IBM code.
data).
User response you might need to report the problem. For information
Review the definition of the exception tables involved about identifying and reporting the problem, see
to determine if the following conditions are causing the Collecting diagnostic data (Collecting data).
error: Collect the following diagnostic items:
• The exception table has referential constraints. • Console output from the system on which the job
• The exception table has unique indexes. was run, and a listing of the SYSLOG data set for the
• The exception table "table-name2" is identical with
"table-name1" in the FOR EXCEPTION keyword. • Listing of SYS1.LOGREC data set, obtained by
executing IFCEREP1.
If none of these is the cause, notify the system
programmer. • SYSPRINT output, including JCL, for the application
If the errors listed in the User Response section are sent to SYSPRINT.
not the cause, this is an internal error. • UTPRINT output, produced by utility invocation of
SORT.
• Console output from the system on which the job Db2 (for 04E and 04F abends). Availability of this
was run, and a listing of the SYSLOG data set for the dump is dependent on the failing environment.
• Listing of SYS1.LOGREC data set, obtained by Availability of these dumps is dependent on the
executing IFCEREP1. failing environment.
00E4070D 00E4070F
An error was detected while attempting to update the An error was detected during the execution of a
EPOCH column of SYSIBM.SYSTABLEPART table. restarted utility. A message is issued prior to this
abend code to indicate the type of error.
System action
Utilities processing is abended. The abend might System action
be accompanied by message DSNT500I. An SDUMP Utility processing is abended.
might be taken.

Check messages issued prior to this abend code to The utility is abended as requested.
determine the cause of the error. Correct the error, and
restart the job. User response
Continue with the diagnosis procedure in progress.
This abend is forced to allow restart of the utility
when work data sets are used and the disposition is
(MOD,DELETE,CATLG).
00E40800
Explanation The ABEND option of the DIAGNOSE utility was
When the utility performs dynamic allocation of sort invoked to force an abend on a particular instance of
data sets, the total number of data sets in each sort a specified utility TRACEID or message. The instance
group must be less than 255. This reason code might of that TRACEID or message was encountered during
be issued after message DSNU3341I. utility processing while DIAGNOSE mode was active
and an abend was forced to occur at that point.
Explanation
System programmer response The DIAGNOSE utility failed while attempting to set
the batch utility address space nonswappable.
Provide more disk space for sort work data sets
by either adding volumes to the sort pool or
by defragmenting the existing sort volumes. Then System action
resubmit the job.
Sort work data sets are allocated in primary quantities
Determine the environment for the SYSEVENT
only, so this error occurs when the sort volumes are
TRANSWAP failure. If you suspect an error in Db2,
very fragmented or are used to their full capacity.
Verify the number of free tracks and the size of about identifying and reporting the problem, see
the largest contiguous block of tracks on your sort Collecting diagnostic data (Collecting data).
volumes to see whether more volumes need to be
added to the sort pool or if defragmentation is User response
necessary. Defragmentation might be required if many
tracks are still available on each volume but the largest Terminate the utility and restart it from the beginning.
contiguous block is very small. If the problem persists, wait until fewer applications
are running on the system before resubmitting the job.
Related information
00E40900 The DIAGNOSE utility attempted to set the batch
utility address space nonswappable by issuing a
Explanation SYSEVENT TRANSWAP operation. The operation failed
to set the address space nonswappable.
The DIAGNOSE utility forced an ABEND. The specified
instance of the specified utility TRACEID or message, Collect the following diagnostic items:
from the DIAGNOSE ABEND utility input statement, • Console output from the system on which the job
was encountered during utility processing while was run, and a listing of the SYSLOG data set for the
DIAGNOSE mode was on. period of time that spans the failure.

executing IFCEREP1.
An error has been detected while creating the service
• SYSPRINT output, including JCL, for the application task for the DIAGNOSE WAIT function.
sent to SYSPRINT. Utilities processing is abended. An SVC dump is
• SYSABEND, SYSUDUMP, or SYSMDUMP output. requested.
failing environment. Operator response

A bad parameter has been detected for the DIAGNOSE Determine the failing environment. If you suspect an
WAIT function. error in Db2, you might need to report the problem.
data).
Utilities processing is abended. An SVC dump is
requested.
Operator response This is an internal error.
problem, see Collecting diagnostic data (Collecting • SYSPRINT output, including JCL, for the application
data). program or batch job, and system messages that
sent to SYSPRINT.
Collect the following diagnostic items: SORT.
was run, and a listing of the SYSLOG data set for the Db2 (for 04E and 04F abends). Availability of this
period of time that spans the failure. dump is dependent on the failing environment.
• Listing of SYS1.LOGREC data set, obtained by ,
executing IFCEREP1.
00E40904
JOB statement so that all diagnostic information is An error has been detected during the DIAGNOSE
sent to SYSPRINT. WAIT function.
SORT. System action
Utilities processing is abended. An SVC dump is
requested.
00E40903

Notify the system programmer. This is an internal error.
data).
This is an internal error. JOB statement so that all diagnostic information is
sent to SYSPRINT.
• Console output from the system on which the job SORT.
• Listing of SYS1.LOGREC data set, obtained by dump is dependent on the failing environment.
executing IFCEREP1.
,
program or batch job, and system messages that 00E40906
JOB statement so that all diagnostic information is Explanation
sent to SYSPRINT.
An error has been detected while issuing a WTOR
message.
SORT.
System action
dump is dependent on the failing environment. Utilities processing is abended. An SVC dump is
, requested.
00E40905 Operator response

Explanation
An error has been detected while deleting the service System programmer response
task for the DIAGNOSE WAIT function.
System action
Utilities processing is abended. An SVC dump is problem, see Collecting diagnostic data (Collecting
requested. data).

Notify the system programmer. This is an internal error.
data).

JOB statement so that all diagnostic information is • Listing of SYS1.LOGREC data set, obtained by
sent to SYSPRINT. executing IFCEREP1.
• UTPRINT output, produced by utility invocation of • SYSPRINT output, including JCL, for the application
SORT. program or batch job, and system messages that
, • UTPRINT output, produced by utility invocation of
SORT.
00E40907
Explanation dump is dependent on the failing environment.
An error has been detected while attempting to map 00E40908
externals to a specific database descriptor (DBD).
Explanation
System action
The utility function is unable to process the data
Utilities processing is abended. The abend may be because the data type of the column was altered from
accompanied by message DSNT500I. An SDUMP may DECIMAL(19,0) to BIGINT, but a value in the column is
be taken. outside the range of BIGINT.

Notify the system programmer. Utilities processing is abended. The utility job is placed
in the stopped state.
If the condition identified cannot be corrected, Programmer response
determine the failing environment. If you suspect an Alter the column data type back to DECIMAL(19,0)
error in Db2, you might need to report the problem. and refer description of the ALTER TABLE statement
For information about identifying and reporting the for information about how to change DECIMAL(19,0)
problem, see Collecting diagnostic data (Collecting columns to BIGINT.
data).
Related concepts
Big integer (BIGINT) (Db2 SQL)
User response
Related reference
Correct the 'resource unavailable' condition identified ALTER TABLE (Db2 SQL)
by the DSNT500I message and either restart the utility
from the last commit point or terminate the utility 00E41000
and start it again from the beginning. If DSNT500I
was not issued, register 2 contains a secondary Db2
reason code that will give more information about the
Explanation
problem. An internal error has occurred. A utility general service
was called incorrectly.
See message DSNT500I in this manual. Refer to
System action
Resource types (Db2 Messages) in for an explanation The utility job step is placed in the stopped state.
of resource type codes.
None

This abend should never occur. If you suspect an • Console output from the system on which the job
error in Db2, you might need to report the problem. was run, and a listing of the SYSLOG data set for the
For information about identifying and reporting the period of time that spans the failure.
problem, see Collecting diagnostic data (Collecting • SVC dump (or system dump), taken to SYS1.DUMPxx
data). data set, as result of an operator-initiated dump
User response • SYSABEND, SYSUDUMP, or SYSMDUMP output.
The general services DSNUGDYN and DSNUGTDS • SYSPRINT output, including JCL, for the application
can be bypassed by not using TEMPLATE dynamic program or batch job, and system messages that
allocation. were issued. Make sure that MSGLEVEL=(1,1) on the
sent to SYSPRINT.
00E4D5D2
This abend is placed at logic points that will occur only
through a programming error.
System action
executing IFCEREP1.
• SYSPRINT output, including JCL, for the application Utility processing abends.
were issued. Make sure that MSGLEVEL=(1,1) on the User response
sent to SYSPRINT. Any 00E4D5D2 is an internal error. The abend
message identifies the module and offset that is in
• UTPRINT output, produced by utility invocation of error.
SORT.
• Dynamic dump, taken to SYS1.DUMPxx data set, by Problem determination
dump is dependent on the failing environment. If you suspect an error in Db2, you might need to
• SYSABEND, SYSUDUMP, or SYSMDUMP output. report the problem. For information about identifying
Availability of these dumps is dependent on the and reporting the problem, see Collecting diagnostic
failing environment. data (Collecting data).
00E41002 00E4E2D7
An error occurred during the loading of an XML This abend is issued by the following Db2-supplied
column. utility stored procedures:
• DSNUTILS
System action • DSNUTILU
The utility job is abended. A SYSABEND dump is • DSNUTILV
requested. An unexpected SQL error occurred during the
execution of the stored procedure. These errors are
User response usually caused by an environment or installation
problem.

The stored procedure abnormally terminates with and reporting the problem, see Collecting diagnostic
SQLCODE -471. data (Collecting data).
Check the WLM address space for the routine that was run, and a listing of the SYSLOG data set for the
is specified in the message for the -471 SQLCODE period of time that spans the failure.
to determine the cause of the problem. Review the
installation process and ensure that the correct levels • Detailed description of events immediately prior to
of libraries were used, and that all of the installation and during the abend.
steps were followed. • Output from the BIND attempt.
User response
If you cannot correct the problem, gather information
about the failing environment.

Reason code identifiers that begin with 00E5 communicate normal and error situations with the agent
services manager.
00E50001 be written to SYS1.LOGREC and a Db2 SVC dump will
be requested. Examine SYS1.LOGREC and, if available,
the SVC dump to determine the subcomponent and
Explanation
module requesting the latch.
A latch acquisition request violates latch deadlock
00E50002
prevention protocols. If the request was unconditional,
the execution unit owns a latch at a level equal to or
greater than the level of the requested latch. If the Explanation
request was conditional, the execution unit already
A release latch request was issued for a latch not
owns a latch at the requested level. This is a Db2
held by the requesting execution unit. This is a Db2
subsystem error.
subsystem error.


Notify the system programmer of the abend.
Notify the system programmer of the abend.

Collect the necessary diagnostic material. If you
(Collecting data).
(Collecting data).

This abend is issued by the in-line expansions of the
This abend is issued from within the in-line
latch acquisition macros DSNVLTHS and DSNVLTHX.
expansions of the latch release macros DSNVUNLS
At the time of the abend, diagnostic information has and DSNVUNLX and from module DSNVXUL0.
been placed in general registers 2 through 5.
At the time of the abend, diagnostic information is
Register placed in general registers 2 through 5.
Contents
If the abend is issued from the in-line expansion
2 macros, then the registers are set as follows:
Latch class number (1-32).
Register
3 Contents
Address of the latch.
2
4, 5 Latch class number (1-32)
Latch class name (1 to 8 characters, left-justified).
3
Registers 2-12 of the invoking module were saved in Address of the latch
the save area pointed to by register 13 at the time the
4, 5
error was detected.
Latch class name (1-8 characters, left justified)
It is the responsibility of the requesting resource
If the abend is issued from DSNVXUL0, then the
manager to have functional recovery in place before
registers are set as follows:
requesting a latch. It is expected that a record will

Register • Listing of SYS1.LOGREC data set, obtained by
Contents executing IFCEREP1.
2 00E50004
Latch class number (1-32)
3 Explanation
Address of the latch
An error was found while attempting to resume a
4
waiter after a latch was released. This abend is issued
Address of the holder of the latch
when the next resource options block (ROB) to be
5 resumed is the same as the immediately previous
First waiter for the latch ROB. That is, the ROBCHNA of a ROB points to itself.
Registers 2-12 of the abending module were saved in
the save area pointed to by register 13 at the time the System action
error was detected.
The current execution unit is abended.
It is the responsibility of the requesting resource
manager to have functional recovery in place while
holding a latch. A record is written to SYS1.LOGREC,
Operator response
and a Db2 SVC dump is requested. Examine Notify the system programmer.
SYS1.LOGREC and, if available, the SVC dump to
determine the subcomponent and module requesting
the latch.
Collect the necessary diagnostic materials. If you
00E50003
Explanation reporting the problem, see Collecting diagnostic data
(Collecting data).
An execution unit that is requesting a latch already
owns that latch. This is a Db2 subsystem error.
System action A record is written to SYS1.LOGREC, and a Db2 SVC
dump is requested.
Collect the necessary diagnostic materials. If you • Listing of SYS1.LOGREC data set, obtained by
suspect an error in Db2, you might need to report executing IFCEREP1.
reporting the problem, see Collecting diagnostic data 00E50005
(Collecting data).
Explanation
Problem determination A resource options block (ROB) which was to be
A record is written to SYS1.LOGREC and a Db2 SVC added to a latch waiter chain was discovered to be
dump is requested. on the chain already. The same ROB cannot be on the
same latch waiter chain twice. This is probably a Db2
Collect the following diagnostic items: subsystem error.

Notify the system programmer. At the time of the abend, general register zero contains
the address of the latch upon which the execution
System programmer response unit is supposedly waiting and general register two
contains the address of the resource options block
Collect the necessary diagnostic materials. If you (ROB) which was put on the latch waiter chain.
suspect an error in Db2, If you suspect an error in Db2,
A record is written to SYS1.LOGREC and a Db2 SVC
dump is requested.
Collecting diagnostic data (Collecting data). Collect the following diagnostic items:
At the time of the abend, general register three period of time that spans the failure.
contains the address of the ROB which would have • Dynamic dump, taken to SYS1.DUMPxx data set, by
been added to the latch waiter chain. Db2 (04E and 04F abends).
A record is written to SYS1.LOGREC and a Db2 SVC • Listing of SYS1.LOGREC data set, obtained by
dump is requested. executing IFCEREP1.

period of time that spans the failure. An execution unit which, according to tracking
• Dynamic dump, taken to SYS1.DUMPxx data set, by information, is currently suspended on a latch waiter
Db2 (04E and 04F abends). chain issued a request to test or to release a latch. A
• Listing of SYS1.LOGREC data set, obtained by single execution unit cannot be doing both at the same
executing IFCEREP1. time. This is probably a Db2 subsystem error.
00E50006
System action
Explanation The requesting execution unit is abended.
An execution unit which, according to tracking

Operator response
information, is currently suspended on a latch waiter
chain issued a request to acquire a latch. A single Notify the system programmer.
execution unit cannot be doing both at the same time.
This is probably a Db2 subsystem error. System programmer response
System action
The requesting execution unit is abended. the problem. For information about identifying and

System programmer response At the time of the abend, general register zero contains
the address of the latch upon which the execution
Collect the necessary diagnostic materials. If you unit is supposedly waiting and general register two
suspect an error in Db2, you might need to report contains the address of the resource options block
the problem. For information about identifying and (ROB) which was put on the latch waiter chain.
A record is written to SYS1.LOGREC and a Db2 SVC
(Collecting data).
dump is requested.

period of time that spans the failure. The requesting execution unit is abended.
executing IFCEREP1.
Explanation suspect an error in Db2, If you suspect an error in Db2,
A latch manager module detected that an execution about identifying and reporting the problem, see
unit requesting latch manager service pointed to an Collecting diagnostic data (Collecting data).
invalid execution block (EB). This is probably a Db2
subsystem error.
System action A record is written to SYS1.LOGREC and a Db2 SVC
dump is requested.
Collect the necessary diagnostic materials. If you • Listing of SYS1.LOGREC data set, obtained by
suspect an error in Db2, If you suspect an error in Db2, executing IFCEREP1.
about identifying and reporting the problem, see 00E50012
Explanation
Problem determination A caller in TCB mode requested the SRB redispatch
A record is written to SYS1.LOGREC and a Db2 SVC function. SRB redispatch can only be requested by
dump is requested. SRB-mode callers. This is probably a Db2 subsystem
error.
period of time that spans the failure. The requesting task is abended.
executing IFCEREP1.
Explanation suspect an error in Db2, you might need to report
A latch manager module detected an invalid resource reporting the problem, see Collecting diagnostic data
options block (ROB) while processing a request for (Collecting data).
service. This is probably a Db2 subsystem error.
This may be either an abend reason code or a Db2
subsystem termination code.

Problem determination failing subcomponent. For example, the ACEMC (must
complete) bit should be off.
The recovery routine in DSNVSDC0 creates diagnostic
material, an entry in SYS1.LOGREC and a Db2 SVC In some cases, this problem might occur because Db2
dump is requested. These must be examined to encountered unexpected user-created catalog index
determine the task and resource manager which made definitions that interfere with the migration process.
the illegal request. See the information about migration job DSNTIJPM
and the information about creating indexes on catalog
Collect the following diagnostic items: tables in the description of CREATE INDEX.
executing IFCEREP1.
00E50013 executing IFCEREP1.
Related tasks
Explanation Run premigration queries (DSNTIJPM) (Db2
A Db2 execution unit has been abended. This abend Installation and Migration)
code must ultimately be issued by resource managers Related reference
when the CANCEL exit is driven as a result of a CREATE INDEX (Db2 SQL)
suspend request.
00E50014
System action
The agent cancel processing continues. Explanation
Normally, this situation does not result in a dump. Either the execution block (EB) or the agent services
However, a dump might result if the situation is global communication area (VGCA) was invalid. The
encountered by other resource managers, outside of error was detected when the agent services resume
Db2. When that happens, the dump can be ignored or function attempted to resume a TCB in an address
suppressed. space other than the primary of the resume requester.
This is a subsystem error.
Operator response
System action
Notify the system programmer only if the abend
results in the termination of the Db2 subsystem. The error is percolated (passed) to the recovery
routine for the TCB that was to have been resumed.

Operator response
This reason code may be issued as a result
of any connected TCB abend, or operator -STOP Notify the system programmer.
DB2 MODE(FORCE) command. No further action is
required. System programmer response
The recovery routine for the CSECT issuing this reason The recovery routine for the CSECT issuing this reason
code records information in the variable recording area code records information in the variable recording area
(VRA). If you suspect an error in Db2, you might (VRA). If you suspect an error in Db2, you might
need to report the problem. For information about need to report the problem. For information about
identifying and reporting the problem, see Collecting identifying and reporting the problem, see Collecting
diagnostic data (Collecting data). diagnostic data (Collecting data).

If Db2 abends, examine the SVC dump to determine An entry is written to SYS1.LOGREC, and a Db2 dump
the suspended resource manager and the state of the is requested by the FRR DSNVSRR. Examine the SVC

dump and determine the resource manager module Collect the following diagnostic items:
requesting the resume operation. Register 3 contains
the SRB address. Register 5 contains the EB address.
If the VGCA is invalid, its address is in register 8. The
EB in question is that of the target TCB.
00E5001A
Explanation
executing IFCEREP1. A CANCEL THREAD command caused the thread to
be terminated. A dump is provided for diagnostic
00E50015
purposes as a result of the CANCEL command DUMP
keyword.
Explanation
The MVS control block (either RB or STSV - SRB Status System action
Save Area) that was the intended object of a resume
Db2 writes a SYS1.LOGREC record and requests an
request was invalid. The RB or STSV address was
SVC dump. The execution unit abends.
obtained from the Db2 EB (execution block) at offset
X'1C' This is a subsystem error.
Operator response
If the CSECT that abends is DSNVRSRB, the error is
percolated (passed) to the recovery routine for the System programmer response
TCB that was to have been resumed. If the CSECT The comm

db2z 12 Codesbook

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

db2z 12 Codesbook

Uploaded by

Copyright:

Available Formats

Db2 12 for z/OS

About this information .......................................................................................... v

Part 1. SQL codes.................................................................................................. 1

Chapter 1. Success (0) and warning (+) SQL codes.................................................................................... 3

Chapter 2. Error (−) SQL codes ................................................................................................................. 39

Part 2. Db2 reason codes................................................................................... 373

Chapter 3. X'C1......' codes.......................................................................................................................375

Chapter 4. X'C2......' codes.......................................................................................................................391

Chapter 5. X'C5......' codes.......................................................................................................................447

Chapter 6. X'C6......' codes.......................................................................................................................453

Chapter 7. X'C8......' codes.......................................................................................................................455

Chapter 8. X'C9......' codes.......................................................................................................................457

Chapter 9. X'D1......' codes.......................................................................................................................527

Chapter 10. X'D3......' codes.................................................................................................................... 597

Chapter 11. X'D4......' codes.................................................................................................................... 871

Chapter 12. X'D5......' codes.................................................................................................................... 885

Chapter 13. X'D6......' codes.................................................................................................................... 887

Chapter 14. X'D7......' codes.................................................................................................................... 889

Chapter 15. X'D9......' codes.................................................................................................................... 909

Chapter 16. X'E2......' codes.....................................................................................................................939

Chapter 17. X'E3......' codes.....................................................................................................................961

Chapter 18. X'E4......' codes.....................................................................................................................995

Chapter 20. X'E6......' codes.................................................................................................................. 1147

Chapter 21. X'E7......' codes.................................................................................................................. 1189

Chapter 22. X'E8......' codes.................................................................................................................. 1219

Chapter 23. X'E9......' codes.................................................................................................................. 1243

Chapter 24. X'F1......' codes...................................................................................................................1247

Chapter 25. X'F3......' codes...................................................................................................................1249

Chapter 26. X'F7......' codes...................................................................................................................1319

Chapter 27. X'F9......' codes...................................................................................................................1325

Appendix A. SNA sense codes ......................................................................... 1331

Appendix B. New, changed, and deleted codes................................................. 1339

Appendix C. z/OS diagnostic services............................................................... 1341

Appendix D. SQLSTATE values and common error codes....................................1343

Appendix E. Db2 abend completion codes (X'04E' and X'04F)............................1375

Appendix F. Resource types............................................................................. 1377

Appendix G. Service task plan names............................................................... 1383

Appendix H. ABEND codes associated with DSN1COPY misuse......................... 1385

© Copyright IBM Corp. 1983, 2023 v

Who should read this information

Db2 Utilities Suite for z/OS

Terminology and citations

vi About this information

Accessibility features for Db2 for z/OS

Related accessibility information

IBM and accessibility

How to send your comments about Db2 for z/OS documentation

About this information vii

Db2 SQL return code format

Db2 reason code format

Subcomponent identifiers in Db2 messages and codes

viii About this information

About this information ix

How to find additional information about messages

x Db2 12 for z/OS: Codes (Last updated: 2023-11-28)

SQLCODE value Meaning SQLCODE descriptions

SQLCODE = 100 No data was found. For example, a FETCH +100

How applications receive SQL codes

Tokens in SQL code message text

© Copyright IBM Corp. 1983, 2023 1

2 Db2 12 for z/OS: Codes (Last updated: 2023-11-28)

List of success and warning SQL codes

000 SUCCESSFUL EXECUTION System action