+098 A DYNAMIC SQL STATEMENT ENDS WITH A SEMICOLON
ROW NOT FOUND FOR FETCH, UPDATE OR DELETE, OR THE
+100 RESULT OF A QUERY IS AN EMPTY TABLE
SQL UPDATE TO A DATA CAPTURE TABLE NOT SIGNALED TO
+110 ORIGINATING SUBSYSTEM
+111 THE SUBPAGES OPTION IS NOT SUPPORTED FOR TYPE 2 INDEXES
THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE
+117 NUMBER OF OBJECT COLUMNS
TABLESPACE database-name.tablespace-name HAS BEEN PLACED IN
+162 CHECK PENDING
THE QUALIFIED COLUMN NAME column-name WAS RESOLVED
+203 USING A NON-UNIQUE OR UNEXPOSED NAME
+204 name IS AN UNDEFINED NAME
column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED
+206 TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE
THE SQL STATEMENT REFERENCING A REMOTE OBJECT CANNOT
+218 BE EXPLAINED
+219 THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST
THE COLUMN column-name IN EXPLANATION TABLE table-name IS +220 NOT DEFINED PROPERLY
A VALUE WITH DATA TYPE data-type1 CANNOT BE ASSIGNED TO A
HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE +304 OF THE HOST VARIABLE IN POSITION position-number WITH DATA TYPE data-type2
THE NULL VALUE HAS BEEN ASSIGNED TO A HOST VARIABLE
+331 BECAUSE THE STRING CANNOT BE TRANSLATED. REASON reason- code, CHARACTER code-point, HOST VARIABLE position-number
THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED, BUT
+339 THERE MAY BE SOME CHARACTER CONVERSION INCONSISTENCIES
+402 LOCATION location IS UNKNOWN
THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS
+403 STATEMENT DOES NOT EXIST
THE RESULT OF THE POSITIONED UPDATE OR DELETE MAY
+535 DEPEND ON THE ORDER OF THE ROWS.
THE REFERENTIAL OR UNIQUE CONSTRAINT name HAS BEEN
+541 IGNORED BECAUSE IT IS A DUPLICATE
auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
+551 operation ON OBJECT object-name
auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
+552 operation
+558 THE WITH GRANT OPTION IS IGNORED
THE ALTER, INDEX, AND REFERENCES PRIVILEGES CANNOT BE
+561 GRANTED TO PUBLIC AT ALL LOCATIONS
A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE
+562 ALREADY HAS THE PRIVILEGE FROM THE GRANTOR +610 INDEX index-name HAS BEEN PLACED IN RECOVER PENDING
THE DEFINITION OF TABLE table-name HAS BEEN CHANGED TO
+625 INCOMPLETE
DROPPING THE INDEX TERMINATES ENFORCEMENT OF THE
+626 UNIQUENESS OF A KEY THAT WAS DEFINED WHEN THE TABLE WAS CREATED
WHERE NOT NULL IS IGNORED BECAUSE THE INDEX KEY CANNOT
+645 CONTAIN NULL VALUES
THE TABLE BEING CREATED OR ALTERED CANNOT BECOME A
+650 DEPENDENT TABLE
TABLE table-name IN PARTITIONED TABLESPACE tspace-name IS NOT
+653 AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED
THE SUBPAGES VALUE IS IGNORED FOR THE CATALOG INDEX
+658 index-name
THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE
+664 PARTITIONED INDEX index-name EXCEEDS THE LENGTH IMPOSED BY THE INDEX MANAGER
DEFINITION CHANGE OF object object_name MAY REQUIRE SIMILAR
+738 CHANGE ON READ-ONLY SYSTEMS
EXCEPTION ERROR exception-type HAS OCCURRED DURING operation-
+802 type OPERATION ON data-type DATA, POSITION position-number
BIND ISOLATION LEVEL RR CONFLICTS WITH TABLESPACE
+806 LOCKSIZE PAGE OR LOCKSIZE ROW AND LOCKMAX 0
THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE
+807 OVERFLOW
THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE
+863 SUPPORTED TYPE 1 INDEXES WITH SUBPAGES GREATER THAN 1 CANNOT +2000 BECOME GROUP BUFFER POOL DEPENDENT IN A DATA SHARING ENVIRONMENT
OPERATION COMPLETED SUCCESSFULLY BUT A DISTRIBUTION
+30100 PROTOCOL VIOLATION HAS BEEN DETECTED. ORIGINAL SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE=original-sqlstate
Error SQLCODE
-007 STATEMENT CONTAINS THE ILLEGAL CHARACTER character
-010 THE STRING CONSTANT BEGINNING string IS NOT TERMINATED
-029 INTO CLAUSE REQUIRED
-060 INVALID type SPECIFICATION : spec
-084 UNACCEPTABLE SQL STATEMENT
-101 THE STATEMENT IS TOO LONG OR TOO COMPLEX
-102 LITERAL STRING IS TOO LONG. STRING BEGINS string
-103 literal IS AN INVALID NUMERIC LITERAL
ILLEGAL SYMBOL "token". SOME SYMBOLS THAT MIGHT BE LEGAL
-104 ARE: token-list
-105 INVALID STRING
-107 THE NAME name IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS size
-109 clause CLAUSE IS NOT PERMITTED
-110 INVALID HEXADECIMAL LITERAL BEGINNING string
-111 A COLUMN FUNCTION DOES NOT INCLUDE A COLUMN NAME
-112 THE OPERAND OF A COLUMN FUNCTION IS ANOTHER COLUMN
FUNCTION
-113 INVALID CHARACTER FOUND IN string, REASON CODE - nnn
THE LOCATION NAME location DOES NOT MATCH THE CURRENT
-114 SERVER
A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR
-115 operator IS FOLLOWED BY A PARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY
THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE
-117 NUMBER OF OBJECT COLUMNS
THE OBJECT TABLE OR VIEW OF THE INSERT, DELETE, OR UPDATE
-118 STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE
A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED
-119 IN THE GROUP BY CLAUSE
A WHERE CLAUSE OR SET CLAUSE INCLUDES A COLUMN
-120 FUNCTION
THE COLUMN name IS IDENTIFIED MORE THAN ONCE IN THE
-121 INSERT OR UPDATE STATEMENT
A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A
COLUMN NAME AND A COLUMN FUNCTION IN THE SELECT -122 CLAUSE OR A COLUMN NAME IS CONTAINED IN THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE
AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A
-125 COLUMN OF THE RESULT
THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE
-126 AND AN ORDER BY CLAUSE
-127 DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT
-128 INVALID USE OF NULL IN A PREDICATE
-129 THE STATEMENT CONTAINS TOO MANY TABLE NAMES
THE ESCAPE CLAUSE CONSISTS OF MORE THAN ONE CHARACTER,
-130 OR THE STRING PATTERN CONTAINS AN INVALID OCCURRENCE OF THE ESCAPE CHARACTER
STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA
-131 TYPES
A LIKE PREDICATE IS INVALID BECAUSE THE SECOND OPERAND
-132 IS NOT A STRING
A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS
INVALID BECAUSE ALL COLUMN REFERENCES IN ITS ARGUMENT -133 ARE NOT CORRELATED TO THE GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO
IMPROPER USE OF LONG STRING COLUMN column-name OR A HOST
-134 VARIABLE OF MAXIMUM LENGTH GREATER THAN 254
SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS
-136 GREATER THAN 4000 BYTES
-137 RESULT OF CONCATENATION TOO LONG
THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS
-138 OUT OF RANGE
-144 INVALID SECTION NUMBER number
THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS
-150 A VIEW FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED
THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG
-151 DESCRIPTION OF COLUMN column-name INDICATES THAT IT CANNOT BE UPDATED
THE DROP clause CLAUSE IN THE ALTER STATEMENT IS INVALID
-152 BECAUSE constraint-name IS A constraint-type THE CREATE VIEW STATEMENT DOES NOT INCLUDE A REQUIRED -153 COLUMN LIST
THE CREATE VIEW FAILED BECAUSE THE VIEW DEFINITION
-154 CONTAINS A UNION, A UNION ALL, OR A REMOTE OBJECT
-156 THE STATEMENT DOES NOT IDENTIFY A TABLE
ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY
-157 CLAUSE. object-name IS NOT THE NAME OF A TABLE.
THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE
-158 SAME AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE
DROP OR COMMENT ON token IDENTIFIES A(N) token RATHER THAN
-159 A(N) token
THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED
-160 VIEW
THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING
-161 ROW DOES NOT SATISFY THE VIEW DEFINITION
auth-id1 DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH
-164 QUALIFICATION authorization ID
THE NUMBER OF ARGUMENTS SPECIFIED FOR function-name IS
-170 INVALID
THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT nn OF
-171 function-name IS INVALID
UR IS SPECIFIED ON THE WITH CLAUSE BUT THE CURSOR IS NOT
-173 READ-ONLY
THE STRING REPRESENTATION OF A DATETIME VALUE HAS
-180 INVALID SYNTAX
THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A
-181 VALID DATETIME VALUE AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS -182 INVALID
AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A
-183 RESULT THAT IS NOT WITHIN THE VALID RANGE OF DATES
AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE
-184 CONTAINS A PARAMETER MARKER
THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR
-185 TIME AND NO LOCAL EXIT HAS BEEN INSTALLED
THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN
-186 INCREASED AND EXECUTING PROGRAM RELIES ON THE OLD LENGTH
A REFERENCE TO A CURRENT DATE/TIME SPECIAL REGISTER IS
-187 INVALID BECAUSE THE MVS TOD CLOCK IS BAD OR THE MVS PARMTZ IS OUT OF RANGE
-188 THE STRING REPRESENTATION OF A NAME IS INVALID
CCSID ccsid IS UNKNOWN OR INVALID FOR THE DATA TYPE OR
-189 SUBTYPE
-191 A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA
QUALIFIED COLUMN NAMES IN ORDER BY CLAUSE NOT
-197 PERMITTED WHEN UNION OR UNION ALL SPECIFIED
THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE
-198 STATEMENT IS BLANK OR EMPTY
ILLEGAL USE OF KEYWORD keyword. TOKEN token-list WAS
-199 EXPECTED
-203 A REFERENCE TO COLUMN column-name IS AMBIGUOUS
-204 name IS AN UNDEFINED NAME
-205 column-name IS NOT A COLUMN OF TABLE table-name
column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED -206 TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE
THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS
-208 NOT PART OF THE RESULT TABLE
THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE
-198 STATEMENT IS BLANK OR EMPTY
ILLEGAL USE OF KEYWORD keyword. TOKEN token-list WAS
-199 EXPECTED
-203 A REFERENCE TO COLUMN column-name IS AMBIGUOUS
-204 name IS AN UNDEFINED NAME
-205 column-name IS NOT A COLUMN OF TABLE table-name
column-name IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED
-206 TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE
THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN name IS
-208 NOT PART OF THE RESULT TABLE
-219 THE REQUIRED EXPLANATION TABLE table-name DOES NOT EXIST
THE COLUMN column-name IN EXPLANATION TABLE table-name IS
-220 NOT DEFINED PROPERLY
"SET OF OPTIONAL COLUMNS" IN EXPLANATION TABLE table-name
-221 IS INCOMPLETE. OPTIONAL COLUMN column-name IS MISSING
THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING
-250 A THREE-PART OBJECT NAME
-251 TOKEN name IS NOT VALID
THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER
-300 position-number IS NOT NUL-TERMINATED THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER -301 position-number CANNOT BE USED AS SPECIFIED BECAUSE OF ITS DATA TYPE
THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER
-302 position-number IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE
A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE
-303 NUMBER position-number BECAUSE THE DATA TYPES ARE NOT COMPARABLE
A VALUE WITH DATA TYPE data-type1 CANNOT BE ASSIGNED TO A
HOST VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE -304 OF THE HOST VARIABLE IN POSITION position-number WITH DATA TYPE data-type2
THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST
-305 VARIABLE NUMBER position-number BECAUSE NO INDICATOR VARIABLE IS SPECIFIED
A PREDICATE IS INVALID BECAUSE A REFERENCED HOST
-309 VARIABLE HAS THE NULL VALUE
DECIMAL HOST VARIABLE OR PARAMETER number CONTAINS NON
-310 DECIMAL DATA.
THE LENGTH OF INPUT HOST VARIABLE NUMBER position-number IS
-311 NEGATIVE OR GREATER THAN THE MAXIMUM
-312 UNDEFINED OR UNUSABLE HOST VARIABLE variable-name
THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO
-313 THE NUMBER OF PARAMETER MARKERS
THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE
-314 REFERENCE
A STRING CANNOT BE USED BECAUSE IT CANNOT BE
-330 TRANSLATED. REASON reason-code, CHARACTER code-point, HOST VARIABLE position-number A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE -331 IT CANNOT BE TRANSLATED. REASON reason-code, CHARACTER code-point, POSITION position-number
SYSSTRINGS DOES NOT DEFINE A TRANSLATION FROM CCSID ccsid
-332 TO ccsid
THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE
-333 SUBTYPE KNOWN AT BIND TIME AND THE DIFFERENCE CANNOT BE RESOLVED BY TRANSLATION
-338 AN ON CLAUSE IS INVALID
THE SQL STATEMENT CANNOT BE EXECUTED FROM AN ASCII
-339 BASED DRDA APPLICATION REQUESTOR TO A V2R2 DB2 SUBSYSTEM
AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION ""
-351 ON A PREPARE or DESCRIBE OPERATION
THE CATALOG HAS THE MAXIMUM NUMBER OF USER DEFINED
-400 INDEXES
THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION
-401 ARE NOT COMPARABLE
AN ARITHMETIC FUNCTION OR OPERATOR arith-fop IS APPLIED TO
-402 CHARACTER OR DATETIME DATA
THE UPDATE OR INSERT STATEMENT SPECIFIES A STRING THAT IS
-404 TOO LONG column-name
THE NUMERIC LITERAL literal CANNOT BE USED AS SPECIFIED
-405 BECAUSE IT IS OUT OF RANGE
A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN
-406 THE RANGE OF ITS OBJECT COLUMN
AN UPDATE OR INSERT VALUE IS NULL, BUT THE OBJECT
-407 COLUMN column-name CANNOT CONTAIN NULL VALUES AN UPDATE OR INSERT VALUE IS NOT COMPARABLE WITH THE -408 DATA TYPE OF ITS OBJECT COLUMN column-name
-409 INVALID OPERAND OF A COUNT FUNCTION
THE FLOATING POINT LITERAL literal CONTAINS MORE THAN 30
-410 CHARACTERS
CURRENT SQLID CANNOT BE USED IN A STATEMENT THAT
-411 REFERENCES REMOTE OBJECTS
THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE
-412 COLUMNS
A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS
-414 NOT A STRING
THE CORRESPONDING COLUMNS, column-number, OF THE
-415 OPERANDS OF A UNION OR A UNION ALL DO NOT HAVE COMPARABLE COLUMN DESCRIPTIONS
-416 AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN
A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER
-417 MARKERS AS THE OPERANDS OF THE SAME OPERATOR
A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID
-418 USE OF PARAMETER MARKERS
THE DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE
-419 RESULT WOULD HAVE A NEGATIVE SCALE
THE VALUE OF A CHARACTER STRING ARGUMENT WAS NOT
-420 ACCEPTABLE TO THE function-name FUNCTION
THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE THE
-421 SAME NUMBER OF COLUMNS
DYNAMIC COMMIT NOT VALID AT AN APPLICATION SERVER
-426 WHERE UPDATES ARE NOT ALLOWED DYNAMIC ROLLBACK NOT VALID AT AN APPLICATION SERVER -427 WHERE UPDATES ARE NOT ALLOWED
THE NUMBER OF PARAMETERS IN THE PARAMETER LIST DOES
NOT MATCH THE NUMBER OF PARAMETERS EXPECTED FOR -440 STORED PROCEDURE name, AUTHID authid, LUNAME luname. number PARAMETERS WERE EXPECTED.
-444 USER PROGRAM name COULD NOT BE FOUND
STORED PROCEDURE name, PARAMETER NUMBER number,
-450 OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH
SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST
-469 VARIABLE FOR PARAMETER number.
SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT
-470 PARAMETER number, BUT THE STORED PROCEDURE DOES NOT SUPPORT NULL VALUES
SQL CALL FOR STORED PROCEDURE name FAILED DUE TO REASON
-471 rc
THE IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION
-500 WAS DESTROYED
THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS
-501 NOT OPEN
THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY
-502 OPEN
A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED
-503 IN THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR
-504 THE CURSOR NAME cursor-name IS NOT DEFINED
THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT
-507 IS NOT OPEN THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT -508 IS NOT POSITIONED ON A ROW
THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT
-509 IS NOT THE SAME TABLE DESIGNATED BY THE CURSOR
THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR
-510 DELETE STATEMENT CANNOT BE MODIFIED
THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE
-511 TABLE DESIGNATED BY THE CURSOR CANNOT BE MODIFIED
-512 STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID
THE ALIAS alias-name MUST NOT BE DEFINED ON ANOTHER LOCAL
-513 OR REMOTE ALIAS
-514 THE CURSOR cursor-name IS NOT IN A PREPARED STATE
THE DESCRIBE STATEMENT DOES NOT IDENTIFY A PREPARED
-516 STATEMENT
CURSOR cursor-name CANNOT BE USED BECAUSE ITS STATEMENT
-517 NAME DOES NOT IDENTIFY A PREPARED SELECT STATEMENT
THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID
-518 PREPARED STATEMENT
THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT
-519 OF THE OPENED CURSOR cursor-name
THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS IN
-525 ERROR AT BIND TIME FOR SECTION = sectno PACKAGE = pkgname CONSISTENCY TOKEN = X'contoken'
THE INSERT OR UPDATE VALUE OF FOREIGN KEY constraint-name IS
-530 INVALID
THE PRIMARY KEY IN A PARENT ROW CANNOT BE UPDATED
-531 BECAUSE IT HAS ONE OR MORE DEPENDENT ROWS IN RELATIONSHIP constraint-name THE RELATIONSHIP constraint-name RESTRICTS THE DELETION OF -532 ROW WITH RID X'rid-number'
-533 INVALID MULTIPLE-ROW INSERT
THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE-
-534 ROW UPDATE
THE DELETE STATEMENT IS INVALID BECAUSE TABLE table-name
-536 CAN BE AFFECTED BY THE OPERATION
THE PRIMARY KEY CLAUSE, A FOREIGN KEY CLAUSE, OR A
-537 UNIQUE CLAUSE IDENTIFIES COLUMN column-name MORE THAN ONCE
FOREIGN KEY name DOES NOT CONFORM TO THE DESCRIPTION OF
-538 THE PRIMARY KEY OF TABLE table-name
-539 TABLE table-name DOES NOT HAVE A PRIMARY KEY
THE DEFINITION OF TABLE table-name IS INCOMPLETE BECAUSE IT
-540 LACKS A PRIMARY INDEX OR A REQUIRED UNIQUE INDEX
column-name CANNOT BE A COLUMN OF A PRIMARY KEY OR A
-542 UNIQUE CONSTRAINT BECAUSE IT CAN CONTAIN NULL VALUES
A ROW IN A PARENT TABLE CANNOT BE DELETED BECAUSE THE
-543 CHECK CONSTRAINT check-constraint RESTRICTS THE DELETION
THE CHECK CONSTRAINT SPECIFIED IN THE ALTER TABLE
-544 STATEMENT CANNOT BE ADDED BECAUSE AN EXISTING ROW VIOLATES THE CHECK CONSTRAINT
THE REQUESTED OPERATION IS NOT ALLOWED BECAUSE A ROW
-545 DOES NOT SATISFY THE CHECK CONSTRAINT check-constraint
-546 THE CHECK CONSTRAINT constraint-name IS INVALID
A CHECK CONSTRAINT THAT IS DEFINED WITH column-name IS
-548 INVALID THE statement STATEMENT IS NOT ALLOWED FOR object_type1 -549 object_name BECAUSE THE BIND OPTION DYNAMICRULES(BIND) IN THE object_type2 IS IN EFFECT
auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
-551 operation ON OBJECT object-name
auth-id DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
-552 operation
-553 auth-id SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS
-554 AN AUTHORIZATION ID CANNOT GRANT A PRIVILEGE TO ITSELF
AN AUTHORIZATION ID CANNOT REVOKE A PRIVILEGE FROM
-555 ITSELF
authid2 CANNOT HAVE THE privilege PRIVILEGE on_object REVOKED
-556 BY authid1 BECAUSE THE REVOKEE DOES NOT POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT
INVALID CLAUSE OR COMBINATION OF CLAUSES ON A GRANT OR
-558 REVOKE
-559 ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED
bind-type AUTHORIZATION ERROR USING auth-id AUTHORITY
-567 PACKAGE = package-name PRIVILEGE = privilege
-571 THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE
THE SPECIFIED DEFAULT VALUE CONFLICTS WITH THE COLUMN
-574 DEFINITION.
THE NAME OF THE OBJECT TO BE CREATED IS IDENTICAL TO THE
-601 EXISTING NAME name OF THE OBJECT TYPE obj-type
-602 TOO MANY COLUMNS SPECIFIED IN A CREATE INDEX
A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE -603 CONTAINS ROWS WHICH ARE DUPLICATES WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS
A COLUMN DEFINITION SPECIFIES AN INVALID LENGTH,
-604 PRECISION, OR SCALE ATTRIBUTE
-607 OPERATION OR OPTION operation IS NOT DEFINED FOR THIS OBJECT
ONLY LOCKMAX 0 CAN BE SPECIFIED WHEN THE LOCK SIZE OF
-611 THE TABLESPACE IS TABLESPACE OR TABLE
-612 column-name IS A DUPLICATE COLUMN NAME
THE PRIMARY KEY OR A UNIQUE CONSTRAINT IS TOO LONG OR
-613 HAS TOO MANY COLUMNS
THE INDEX CANNOT BE CREATED BECAUSE THE SUM OF THE
-614 INTERNAL LENGTHS OF THE IDENTIFIED COLUMNS IS GREATER THAN THE ALLOWABLE MAXIMUM
-615 operation-type IS NOT ALLOWED ON A PACKAGE IN USE
obj-type1 obj-name1 CANNOT BE DROPPED BECAUSE IT IS
-616 REFERENCED BY obj-type2 obj-name2
A TYPE 1 INDEX CANNOT BE DEFINED ON A TABLE IN A TABLE
-617 SPACE WITH LOCKSIZE ROW
-618 OPERATION operation IS NOT ALLOWED ON SYSTEM DATABASES
OPERATION DISALLOWED BECAUSE THE WORK FILE DATABASE
-619 IS NOT STOPPED
KEYWORD keyword IN stmt type STATEMENT IS NOT PERMITTED FOR
-620 A TABLE SPACE IN THE WORK FILE DATABASE
DUPLICATE DBID dbid WAS DETECTED AND PREVIOUSLY
-621 ASSIGNED TO database-name
-622 FOR MIXED DATA IS INVALID BECAUSE THE MIXED DATA
INSTALL OPTION IS NO
-623 A CLUSTERING INDEX ALREADY EXISTS ON TABLE table-name
-624 TABLE table-name ALREADY HAS A PRIMARY KEY
TABLE table-name DOES NOT HAVE AN INDEX TO ENFORCE THE
-625 UNIQUENESS OF THE PRIMARY KEY
THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGE
-626 SET IS NOT STOPPED
THE ALTER STATEMENT IS INVALID BECAUSE THE PAGESET HAS
-627 USER-MANAGED DATA SETS
-628 THE CLAUSES ARE MUTUALLY EXCLUSIVE.
SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY name
-629 CANNOT CONTAIN NULL VALUES
THE WHERE NOT NULL SPECIFICATION IS INVALID FOR TYPE 1
-630 INDEXES
-631 FOREIGN KEY name IS TOO LONG OR HAS TOO MANY COLUMNS
THE TABLE CANNOT BE DEFINED AS A DEPENDENT OF table-name
-632 BECAUSE OF DELETE RULE RESTRICTIONS
-633 THE DELETE RULE MUST BE delete-rule
-634 THE DELETE RULE MUST NOT BE CASCADE
THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET
-635 NULL
THE PARTITIONING KEYS ARE NOT SPECIFIED IN ASCENDING OR
-636 DESCENDING ORDER
-637 DUPLICATE keyword KEYWORD
TABLE table-name CANNOT BE CREATED BECAUSE COLUMN -638 DEFINITION IS MISSING
A NULLABLE COLUMN OF A FOREIGN KEY WITH A DELETE RULE
-639 OF SET NULL CANNOT BE A COLUMN OF THE KEY OF A PARTITIONED INDEX
LOCKSIZE ROW CANNOT BE SPECIFIED BECAUSE TABLE IN THIS
-640 TABLESPACE HAS TYPE 1 INDEX
-642 TOO MANY COLUMNS IN UNIQUE CONSTRAINTS
-643 CHECK CONSTRAINT EXCEEDS MAXIMUM ALLOWABLE LENGTH
INVALID VALUE SPECIFIED FOR KEYWORD keyword IN stmt-type
-644 TATEMENT
TABLE table-name CANNOT BE CREATED IN PARTITIONED/DEFAULT
-646 TABLE SPACE tspace-name BECAUSE IT ALREADY CONTAINS A TABLE
BUFFERPOOL bp-name CANNOT BE SPECIFIED BECAUSE IT HAS
-647 NOT BEEN ACTIVATED
-650 THE ALTER INDEX CANNOT BE EXECUTED, REASON reason
TABLE DESCRIPTION EXCEEDS MAXIMUM SIZE OF OBJECT
-651 DESCRIPTOR.
VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION
-652 PROCEDURE proc-name
TABLE table-name IN PARTITIONED TABLE SPACE tspace-name IS NOT
-653 AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED
THE CREATE OR ALTER STOGROUP IS INVALID BECAUSE THE
-655 STORAGE GROUP WOULD HAVE BOTH SPECIFIC AND NON- SPECIFIC VOLUME IDS
-660 INDEX index-name CANNOT BE CREATED ON PARTITIONED TABLE
SPACE tspace-name BECAUSE KEY LIMITS ARE NOT SPECIFIED
INDEX index-name CANNOT BE CREATED ON PARTITIONED TABLE
SPACE tspace-name BECAUSE THE NUMBER OF PART -661 SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS OF THE TABLE SPACE
A PARTITIONED INDEX CANNOT BE CREATED ON A NON-
-662 PARTITIONED TABLE SPACE tspace-name
THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR
-663 GREATER THAN THE NUMBER OF COLUMNS IN THE KEY OF INDEX index-name
THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR
-665 INVALID
stmt-verb object CANNOT BE EXECUTED BECAUSE function IS IN
-666 PROGRESS
THE CLUSTERING INDEX FOR A PARTITIONED TABLE SPACE
-667 CANNOT BE EXPLICITLY DROPPED
THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE
-668 TABLE HAS AN EDIT PROCEDURE
A TABLE IN A PARTITIONED TABLE SPACE CANNOT BE
-669 EXPLICITLY DROPPED
THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE
-670 LIMIT
THE BUFFERPOOL ATTRIBUTE OF THE TABLE SPACE CANNOT BE
-671 ALTERED AS SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE TABLE SPACE
-672 OPERATION DROP NOT ALLOWED ON TABLE table_name
-676 A 32K PAGE BUFFERPOOL MAY NOT BE USED FOR AN INDEX
-677 INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION
THE LITERAL literal SPECIFIED FOR THE INDEX LIMIT KEY MUST -678 CONFORM TO THE DATA TYPE data-type OF THE CORRESPONDING COLUMN column-name
THE OBJECT name CANNOT BE CREATED BECAUSE A DROP IS
-679 PENDING ON THE OBJECT
-680 TOO MANY COLUMNS SPECIFIED FOR A TABLE
COLUMN column-name IN VIOLATION OF INSTALLATION DEFINED
-681 FIELD PROCEDURE. RT: return-code, RS: reason-code, MSG: message- token
-682 FIELD PROCEDURE procedure-name COULD NOT BE LOADED
INVALID COLUMN TYPE FOR FIELDPROC, BIT DATA, SBCS DATA,
-683 OR MIXED DATA OPTION, column-name
-684 THE LENGTH OF LITERAL LIST BEGINNING string IS TOO LONG
-685 INVALID FIELD TYPE, column-name
COLUMN DEFINED WITH A FIELD PROCEDURE CAN NOT COMPARE
-686 WITH ANOTHER COLUMN WITH DIFFERENT FIELD PROCEDURE
-687 FIELD TYPES INCOMPARABLE
INCORRECT DATA RETURNED FROM FIELD PROCEDURE, column-
-688 name, msgno
-689 TOO MANY COLUMNS DEFINED FOR A DEPENDENT TABLE
THE STATEMENT IS REJECTED BY DATA DEFINITION CONTROL
-690 SUPPORT. REASON reason-code
-691 THE REQUIRED REGISTRATION TABLE table-name DOES NOT EXIST
THE REQUIRED UNIQUE INDEX index-name FOR DDL REGISTRATION
-692 TABLE table-name DOES NOT EXIST THE COLUMN column-name IN DDL REGISTRATION TABLE OR -693 INDEX table-name (index-name) IS NOT DEFINED PROPERLY
THE DDL STATEMENT CANNOT BE EXECUTED BECAUSE A DROP IS
-694 PENDING ON THE DDL REGISTRATION TABLE table-name
-713 THE REPLACEMENT VALUE FOR special-register IS INVALID
PROGRAM program-name WITH MARK release-dependency-mark FAILED
-715 BECAUSE IT DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED
PROGRAM program-name PRECOMPILED WITH INCORRECT LEVEL
-716 FOR THIS RELEASE.
bind-type FOR object-type object-name WITH MARK release-dependency-
-717 mark FAILED BECAUSE object-type DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED.
REBIND FOR PACKAGE package-name FAILED BECAUSE IBMREQD
-718 OF ibmreqd IS INVALID
BIND ADD ERROR USING auth-id AUTHORITY PACKAGE package-
-719 name ALREADY EXISTS
BIND ERROR, ATTEMPTING TO REPLACE PACKAGE = package_name
-720 WITH VERSION = version2 BUT THIS VERSION ALREADY EXISTS
BIND ERROR FOR PACKAGE = pkg-id CONTOKEN = 'contoken'X IS
-721 NOT UNIQUE SO IT CANNOT BE CREATED
bind-type ERROR USING auth-id AUTHORITY PACKAGE package-name
-722 DOES NOT EXIST
BIND ERROR ATTEMPTING TO REPLACE PACKAGE = . THERE ARE
-726 ENABLE OR DISABLE ENTRIES CURRENTLY ASSOCIATED WITH THE PACKAGE
THE PARENT OF A TABLE IN A READ-ONLY SHARED DATABASE
-730 MUST ALSO BE A TABLE IN A READ-ONLY SHARED DATABASE USER-DEFINED DATASET dsname MUST BE DEFINED WITH -731 SHAREOPTIONS(1,3)
THE DATABASE IS DEFINED ON THIS SUBSYSTEM WITH THE
-732 ROSHARE READ ATTRIBUTE BUT THE TABLE SPACE OR INDEX SPACE HAS NOT BEEN DEFINED ON THE OWNING SUBSYSTEM
THE DESCRIPTION OF A TABLE SPACE, INDEX SPACE, OR TABLE IN
-733 A ROSHARE READ DATABASE MUST BE CONSISTENT WITH ITS DESCRIPTION IN THE OWNER SYSTEM
THE ROSHARE ATTRIBUTE OF A DATABASE CANNOT BE ALTERED
-734 FROM ROSHARE READ
DATABASE dbid CANNOT BE ACCESSED BECAUSE IT IS NO
-735 LONGER A SHARED DATABASE
-736 INVALID OBID obid SPECIFIED
-737 IMPLICIT TABLE SPACE NOT ALLOWED
A WORK FILE DATABASE IS ALREADY DEFINED FOR MEMBER
-741 member-name
-742 DSNDB07 IS THE IMPLICIT WORK FILE DATABASE
A STORED PROCEDURE HAS BEEN PLACED IN MUST_ROLLBACK
-751 STATE DUE TO SQL OPERATION name
THE CONNECT STATEMENT IS INVALID BECAUSE THE PROCESS IS
-752 NOT IN THE CONNECTABLE STATE
EXCEPTION ERROR 'exception-type' HAS OCCURRED DURING
-802 'operation-type' OPERATION ON 'data-type' DATA, POSITION 'position- number'
AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE THE
INDEX IN INDEX SPACE indexspace-name CONSTRAINS COLUMNS OF -803 THE TABLE SO NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X'rid' AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT -804 PARAMETERS FOR THE SQL STATEMENT. REASON reason
DBRM or PACKAGE NAME location-name.collection-id.dbrm-
-805 name.consistency -token NOT FOUND IN PLAN plan-name. REASON reason
ACCESS DENIED: PACKAGE package-name IS NOT ENABLED FOR
-807 ACCESS FROM connection-type connection-name
THE CONNECT STATEMENT IS NOT CONSISTENT WITH THE FIRST
-808 CONNECT STATEMENT
THE RESULT OF AN EMBEDDED SELECT STATEMENT IS A TABLE
-811 OF MORE THAN ONE ROW, OR THE RESULT OF THE SUBQUERY OF A BASIC PREDICATE IS MORE THAN ONE VALUE
THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE A BLANK
COLLECTION-ID WAS FOUND IN THE CURRENT PACKAGESET -812 SPECIAL REGISTER WHILE TRYING TO FORM A QUALIFIED PACKAGE NAME FOR PROGRAM program-name.consistency-token USING PLAN plan-name
A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY
-815 SPECIFIED IN AN EMBEDDED SELECT STATEMENT OR A SUBQUERY OF A BASIC PREDICATE
THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE
-817 STATEMENT WILL RESULT IN A PROHIBITED UPDATE OPERATION
THE PRECOMPILER-GENERATED TIMESTAMP x IN THE LOAD
-818 MODULE IS DIFFERENT FROM THE BIND TIMESTAMP y BUILT FROM THE DBRM z
THE VIEW CANNOT BE PROCESSED BECAUSE THE LENGTH OF ITS
-819 PARSE TREE IN THE CATALOG IS ZERO
THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE catalog-
-820 table CONTAINS A VALUE THAT IS NOT VALID IN THIS RELEASE
THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR
-822 INDICATOR VARIABLE ADDRESS -840 TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST
-842 A CONNECTION TO location-name ALREADY EXISTS
THE SET CONNECTION OR RELEASE STATEMENT MUST SPECIFY
-843 AN EXISTING CONNECTION
THE NUMBER OF HOST VARIABLES IN THE STATEMENT IS NOT
-870 EQUAL TO THE NUMBER OF DESCRIPTORS
THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE
-900 APPLICATION PROCESS IS NOT CONNECTED TO AN APPLICATION SERVER
UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT
-901 DOES NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS
POINTER TO THE ESSENTIAL CONTROL BLOCK (CT/RDA) HAS
-902 VALUE 0, REBIND REQUIRED
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE
-904 RESOURCE. REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name
UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING
EXCEEDED, RESOURCE NAME = resource-name LIMIT = limit-amount1 -905 CPU SECONDS (limit-amount2 SERVICE UNITS) DERIVED FROM limit- source
THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS
-906 FUNCTION IS DISABLED DUE TO A PRIOR ERROR
bind-type ERROR USING auth-id AUTHORITY BIND, REBIND OR AUTO-
-908 REBIND OPERATION IS NOT ALLOWED
-909 THE OBJECT HAS BEEN DELETED
THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A
-910 DROP OR ALTER IS PENDING THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO -911 DEADLOCK OR TIMEOUT. REASON reason-code, TYPE OF RESOURCE resource-type, AND RESOURCE NAME resource-name
UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR
-913 TIMEOUT. REASON CODE reason-code, TYPE OF RESOURCE resource- type, AND RESOURCE NAME resource-name
THE NUMBER OF HOST VARIABLE PARAMETERS FOR A STORED
PROCEDURE IS NOT EQUAL TO THE NUMBER OF EXPECTED HOST -2001 VARIABLE PARAMETERS. ACTUAL NUMBER sqldanum, EXPECTED NUMBER opnum
EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR
THAT WILL NOT AFFECT THE SUCCESSFUL EXECUTION OF -30000 SUBSEQUENT COMMANDS OR SQL STATEMENTS: REASON reason- code (sub-code)
EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR
-30020 THAT CAUSED DEALLOCATION OF THE CONVERSATION: REASON <reason-code (sub-code)>
EXECUTION FAILED DUE TO A DISTRIBUTION PROTOCOL ERROR
THAT WILL AFFECT THE SUCCESSFUL EXECUTION OF -30021 SUBSEQUENT COMMANDS OR SQL STATEMENTS: MANAGER manager AT LEVEL level NOT SUPPORTED ERROR
COMMIT REQUEST WAS UNSUCCESSFUL, A DISTRIBUTION
PROTOCOL VIOLATION HAS BEEN DETECTED, THE -30030 CONVERSATION HAS BEEN DEALLOCATED. ORIGINAL SQLCODE=original-sqlcode AND ORIGINAL SQLSTATE=original-sqlstate
EXECUTION FAILED DUE TO UNAVAILABLE RESOURCES THAT
WILL NOT AFFECT THE SUCCESSFUL EXECUTION OF SUBSEQUENT -30040 COMMANDS OR SQL STATEMENTS. REASON <reason-code> TYPE OF RESOURCE <resource-type> RESOURCE NAME <resource-name> PRODUCT ID <pppvvrrm> RDBNAME <rdbname>
EXECUTION FAILED DUE TO UNAVAILABLE RESOURCES THAT
WILL AFFECT THE SUCCESSFUL EXECUTION OF SUBSEQUENT -30041 COMMANDS AND SQL STATEMENTS REASON <reason-code> TYPE OF RESOURCE <resource-type> RESOURCE NAME <resource-name> PRODUCT ID <pppvvrrm> RDBNAME <rdbname>
-30050 <command-or-SQL-statement-type> COMMAND OR SQL STATEMENT
INVALID WHILE BIND PROCESS IN PROGRESS
BIND PROCESS WITH SPECIFIED PACKAGE NAME AND
-30051 CONSISTENCY TOKEN NOT ACTIVE
-30052 PROGRAM PREPARATION ASSUMPTIONS ARE INCORRECT
-30053 OWNER AUTHORIZATION FAILURE
-30060 RDB AUTHORIZATION FAILURE
-30061 RDB NOT FOUND
-30070 <command> COMMAND NOT SUPPORTED ERROR
-30071 <object-type> OBJECT NOT SUPPORTED ERROR
-30072 <parameter>:<subcode> PARAMETER NOT SUPPORTED ERROR
-30073 <parameter>:<subcode> PARAMETER VALUE NOT SUPPORTED ERROR
-30074 REPLY MESSAGE WITH codepoint (svrcod) NOT SUPPORTED ERROR
-30080 COMMUNICATION ERROR code (subcode)
REMOTE OPERATION INVALID FOR APPLICATION EXECUTION