+162
TABLESPACE {dbname} HAS BEEN PLACED IN CHECK PENDING.
+100
ROW NOT FOUND FOR FETCH, UPDATE OR DELETE, OR THE RESULT OF
A QUERY IN AN EMPTY TABLE (ie. EOF).
+304
A VALUE WITH DATATYPE {type} CANNOT BE ASSIGNED TO A HOST
VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE
HOST VARIABLE IN POSITION {pos#} WITH DATA TYPE {datatype}.
+402
LOCATION {location} IS UNKNOWN.
+403
THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS STATEMENT
DOES NOT EXIST.
+558
THE WITH GRANT OPTION IS IGNORED BECAUSE GRANT IS TO PUBLIC.
+560
THE WITH GRANT OPTION IS IGNORED FOR UPDATE(COLUMN-LIST).
+561
THE ALTER AND INDEX PRIVILEGES CANNOT BE GRANTED TO
"PUBLIC AT ALL LOCATIONS".
+625
THE DEFINITIONOF TABLE {tablename} HAS BEEN CHANGED TO
INCOMPLETE.
+802
EXCEPTION ERROR {exceptiontype} HAS OCCURRED DURING
{operation-type} OPERATION ON {data-type} DATA, POSITION
{pos#}.
-007
STATEMENT CONTAINS THE ILLEGAL CHARACTER {character}.
-010
THE STRING CONSTANT BEGINNING {string} IS NOT TERMINATED.
-060
INVALID {type} SPECIFICATION: {spec}.
-084
UNACCEPTABLE SQL STATEMENT
-101
THE STATEMENT IS TOO LONG OR TOO COMPLEX.
-102
THE LENGTH OF THE STRING CONSTANT BEGINNING {string} IS
GREATER THAN 254 CHARACTERS OR 124 GRAPHIC CHARACTERS.
-103
{literal} IS AN INVALID NUMERIC LITERAL.
-104
ILLEGAL SYMBOL {token} VALID SYMBOLS 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
OR DISTINCT FOLLOWED BY AN EXPRESSION.
-113
INVALID CHARACTER FOUND IN NAME {name}.
-115
A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR
IS FOLLOWED BY A PARENTHESIZED LIST OR BY ANY OR ALL
WITHOUT A SUBQUERY.
-117
THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER
OF OBJECT COLUMNS.
-118
THE OBJECT TABLE OR VIEW OF THE INSERT, DELETE, OR UPDATE
STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE.
-119
A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN
THE GROUP BY CLAUSE.
-121
THE COLUMN {name} IS IDENTIFIED MORE THAN ONCE IN THE INSERT
OR UPDATE STATEMENT.
-120
A WHERE CLAUSE OR SET CLAUSE INCLUDES A COLUMN FUNCTION OR A
WHERE CLAUSE REFERENCES A COLUMN {name} WHICH IS DERIVED
FROM A COLUMN FUNCTION OR EXPRESSION IN A VIEW DEFINITION.
-122
A SELECT STATEMENT WITH NO GROUP BY CLAUSE CONTAINS A COLUMN
NAME AND A COLUMN FUNCTION IN THE SELECT CLAUSE OR A COLUMN
NAME IS CONTAINED IN SELECT CLAUSE BUT NOT GROUP BY CLAUSE.
-125
AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A
COLUMN OF THE RESULT SET.
-126
THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE 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.
-131
STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES.
-132
A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT
A COLUMN OR THE SECOND OPERAND IS NOT A STRING
-133
A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS
INVALID. IT INLCLUDES AN EXPRESSION THAT APPLIES TO AN
OPERATOR TO A CORRELATED REFERENCE.
-134
IMPROPER USE OF LONG STRING COLUMN {column_name} OR A HOST
VARIABLE OF MAXIMUM LENGTH GREATER THAN 254
-136
SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS
GREATER THAN 4000 BYTES.
-138
THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT
OF RANGE.
-150
THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A
VIEW FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED.
-151
THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG
DESCRIPTION OF COLUMN {column-name} INDICATES THAT IT CANNOT
BE UPDATED.
-153
THE CREATE VIEW STATEMENT DOES NOT INCLUDE A REQUIRED
COLUMN LIST.
-154
THE CREATE VIEW FAILED BECAUSE THE VIEW DEFINITION CONTAINS
A UNION, A UNION ALL, OR A REMOTE OBJECT.
-156
THE STATEMENT DOES NOT IDENTIFY A TABLE.
-157
ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE,
{object-name} IS NOT THE NAME OF A TABLE.
-158
THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAMW
AS THE NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE.
-159
DROP OR COMMENT ON {token} IDENTIFIES A {token} RATHER THAN
A {token}.
-160
THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW.
-161
THE INSERT OF UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW
DOES NOT SATISFY THE VIEW DEFINITION.
-164
{auth-id} DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH
QUALIFICATION {authorization} ID.
-170
THE NUMBER OF ARGUMENTS SPECIFIED FOR {function-name} IS
INVALID.
-171
THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT {nn} OF
FUNCTION {function-name} IS INVALID.
-180
THE STRING REPRESENTATION OF A DATETIME VALUE HAS AN
INVALID SYNTAX.
-181
THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A
VALID DATETIME VALUE (ie. invalid date: 02/31/91)
-182
AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IN INVALID.
-183
AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT
THAT IS NOT WITHIN THE VALID RANGE OF DATES.
-184
AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A
PARAMETER MARKER.
-185
THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME
AND NO LOCAL EXIT HAS BEEN INSTALLED.
-186
THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN
INCREASED AND EXECUTING PROGRAM RELIES ON THE OLD LENGTH.
-187
A REFERENCE TO A CURRENT DATE/TIME SPECIAL REGISTER IS
INVALID BECAUSE THE MVS TOD CLOCK IS BAD OR THE MVS PARMTZ
IS OUT OF RANGE.
-198
THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT
IS BLANK OR EMPTY.
-199
ILLEGAL USE OF KEYWORD {keyword}. TOKEN {token-list} WAS
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}.
-206
{column-name} IS NOT A COLUMN OF AN INSERTED TABLE,
UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE.
-207
THE ORDER CLAUSE IS INVALID BECAUSE IT INCLUDES A COLUMN
NAME BUT APPLIES TO THE RESULT SET OF A UNION OR UNION ALL.
-208
THE ORDER CLAUSE IS INVALID BECAUSE COLUMN {column-name} IS
NOT PART OF THE RESULT TABLE.
-219
THE REQUIRED EXPLANATION TABLE {table-name} DOES NOT EXIST.
-220
THE COLUMN {column-name} IN EXPLANATION TABLE {table-name}
IS NOT DEFINED PROPERLY.
-221
"SET OF OPERATIONAL COLUMNS" IN EXPLANATION TABLE
{table-name} IS INCOMPLETE. OPTIONAL COLUMN {column-name}
IS MISSING.
-250
THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A
THREE-PART OBJECT NAME.
-251
TOKEN {token} IS NOT VALID.
-301
THE VALUE OF INPUT HOST VARIABLE NUMBER {pos#} CANNOT BE
USED AS SPECIFIED BECAUSE OF ITS DATA TYPE.
-302
THE VALUE OF INPUT VARIABLE NUMBER {pos#} IS INVALID OR
TOO LARGE FOR THE TARGET COLUMN.
-303
A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER
{pos#} BECAUSE THE DATE TYPES ARE NOT COMPARABLE.
-304
A VALUE WITH DATATYPE {datatype1} CANNOT BE ASSIGNED TO A
HOST VARIABLE BECAUSE THE VALUE IS NOT WOTHIN THE RANGE OF
THE HOST VAR IN POSITION {pos#} WITH DATATYPE {datatype2}.
-305
THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE
NUMBER {pos#} BECAUSE NO INDICATOR VARIABLE WAS SPECIFIED.
-309
A PREDICATE IN INVALID BECAUSE A REFERENCED HOST VARIABLE
HAS THE NULL VALUE.
-312
UNDEFINED OR UNUSABLE HOST VARIABLE {variable-name}.
-313
THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE
NUMBER OF PARAMETER MARKERS.
-314
THE STATEMENT CONTAINS AN AMIBIGUOUS HOST VARIABLE
REFERENCE.
-401
THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE
NOT COMPARIBLE.
-402
AN ARITHMETIC FUNCTION OR OPERATOR {arith-fop} IS APPLIED
TO CHARACTER OR DATETIME DATA.
-404
THE UPDATE OR INSERT STATEMENT SPECIFIES A STRING THAT IS
TO LONG {column-name}.
-405
THE NUMERIC LITERAL {literal} CANNOT BE USED AS SPECIFIED
BECAUSE IT IS OUT OF RANGE.
-406
A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE
RANGE OF ITS OBJECT COLUMN.
-407
AN UPDATE OR INSERT IS NULL, BUT THE OBJECT COLUMN
{column-name} CANNOT CONTAIN NULL VALUES.
-408
AN UPDATE OR INSERT VALUE IS NOT COMPARABLE WITH THE DATA
TYPE OF ITS OBJECT COLUMN {column-name}.
-409
INVALID OPERAND OF A COUNT FUNCTION.
-410
THE FLOATING POINT LITERAL {literal} CONTAINS MORE THAN 30
CHARACTERS.
-411
THE CURRENT DATETIME, CURRENT SQLID OR USER KEYWORD CANNOT
BE USED AS SPECIFIED.
-412
THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS.
-414
THE NUMERIC OR DATETIME COLUMN {column-name} IS SPECIFIED
IN A LIKEPREDICATE.
-415
THE CORRESPONDING COLUMNS {column-number}, OF THE OPERANDS
OF A UNION OR UNION ALL DO NOT HAVE COMPARABLE COLUMN
DESCRIPTIONS.
-416
AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN.
-417
THE STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER
MARKERS ASTHE OPERANDS OF THE SAME OPERATOR.
-418
THE STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE
OF PARAMETER MARKERS.
-419
DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT
WOULD HAVE A NEGATIVE SCALE.
-421
THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE THE SAME
NUMBER OF COLUMNS.
-501
THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT
OPEN.
-502
THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN.
-503
A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN
THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR.
-504
THE CURSOR NAME {cursor-name} IS NOT IDENTIFIED.
-507
THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS
NOT OPEN.
-508
NOT POSITIONED ON A ROW.
-509
THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS
NOT THE SAME TABLE DESIGNATED BY THE CURSOR.
-510
THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE
STATEMENT CANNOT BE MODIFIED.
-511
THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE TABLE
DESIGNATED BY THE CURSOR CANNOT BE MODIFIED.
-607
OPERATION {operation} IS NOT DEFINED FOR SYSTEM TABLES.
-612
{column-name} IS A DUPLICATE COLUMN NAME.
-613
THE PRIMARY KEY IS TOO LONG OR HAS TOO MANY COLUMNS.
-614
THE INDEX CANNOT BE CREATED BECAUSE THE SUM OF THE INTERNAL
LENGTHS OF THE IDENTIFIED COLUMNS IS GREATER THAN THE
ALLOWABLE MAXIMUM.
-616
{obj-type1 obj-name1} CANNOT BE DROPPED BECAUSE IS IS
REFERENCED BY {obj-type2 obj-name2}.
-618
OPERATION {operation} IS NOT ALLOWED ON SYSTEM DATABASES.
-619
OPERATION DISALLOWED BECAUSE THE WORKFILE DATABASE IS NOT
STOPPED.
-620
KEYWORD {keyword} IN {statement type} STATEMENT IS NOT
PERMITTED FOR A TABLESPACE IN THE WORKFILE DATABASE.
-621
DUPLICATE DBID {abid} WAS DETECTED AND PREVIOUSLY ASSIGNED
TO {database-name}
-623
A CLUSTERING INDEX ALREADY EXISTS ON TABLE {table_name}.
-624
TABLE {table-name} ALREADY HAS A PRIMARY KEY.
-625
TABLE {table-name} DOES NOT HAVE AN INDEX TO ENFORCE THE
UNIQUENESS OF THE PRIMARY KEY.
-626
THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGESET
IS NOT STOPPED.
-627
THE ALTER STATEMENT IS INVALID BECAUSE THE PAGESET HAS USER
MANAGED DATA SETS.
-628
A SEGMENTED TABLESPACE MAY NOT BE PARTITIONED.
-629
SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY {name}
CANNOT CONTAIN NULL VALUES.
-631
FOREIGN KEY {name} IS TOO LONG OR HAS TOO MANY COLUMNS.
-632
THE TABLE CANNOT BE DEFINED AS A DEPENDENT OF {table-name}
BECAUSE OF DELETE RULE RESTRICTIONS.
-633
THE DELETE RULE MUST BE {delete-rule}.
-634
THE DELETE RULE MUST NOT BE CASCADE.
-635
THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL.
-636
THE PARTITIONING KEYS ARE NOT SPECIFIED IN ASCENDING OR
DESCENDING ORDER.
-637
DUPLICATE {keyword} KEYWORD.
-638
TABLE {table-name} CANNOT BE CREATED BECAUSE THE COLUMN
DEFINITION IS MISSING.
-639
A NULLABLE COLUMN OF A FOREIGN KEY WITH A DELETE RULE OF
SET NULL CANNOT BE A COLUMN OF THE KEY OF A PARTITIONED
INDEX.
-644
INVALID VALUE SPECIFIED FOR KEYWORD {keyword} IN
{statement-type} STATEMENT.
-646
TABLE {table-name} CANNOT BE CREATED IN PARTITIONED/DEFAULT
TABLESPACE {tspace-name} BECAUSE IT ALREADY CONTAINS A
TABLE.
-647
BUFFERPOOL {bpool-name} CANNOT BE SPECIFIED BECAUSE IT HAS
NOT BEEN ACTIVATED.
-652
VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION
PROCEDURE {proc-name}.
-653
TABLE {table-name} IN PARTITIONED TABLESPACE {tspace-name}
IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT
BEEN CREATED.
-660
INDEX {index-name} CANNOT BE CREATED ON PARTITIONED
TABLESPACE {tspace-name} BECAUSE KEY LIMITS ARE NOT
SPECIFIED.
-661
INDEX {idx-name} CANNOT BE CREATED ON PARTITIONED TABLESPACE
{tspace-name} BECAUSE THE NUMBER OF PART SPECS IS NOT EQUAL
THE NUMBER OF PARTITIONS OF THE TABLESPACE.
-662
A PARTITIONED INDEX CANNOT BE CREATED ON A NON-PARTITIONED
TABLESPACE {tspace-name}.
-663
THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR GREATER
THAN THE NUMBER OF COLUMNS IN THE KEY OF INDEX {idx-name}.
-664
THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE
PARTITIONED INDEX {idx-name} EXCEEDS THE LENGTH IMPOSED BY
THE INDEX MANAGER.
-665
THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID.
-666
{stmt-verb object} CANNOT BE EXECUTED BECAUSE {function} IS
IN PROGRESS.
-667
THE CLUSTERING INDEX FOR A PARTITIONED TABLESPACE CANNOT BE
EXPLICITLY DROPPED.
-668
THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE
HAS AN EDIT PROCEDURE.
-669
A TABLE IN A PARTITIONED TABLESPACE CANNOT BE EXPLICITLY
DROPPED.
-670
THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT.
-671
THE BUFFERPOOL ATTRIBUTE OF THE TABLESPACE CANNOT BE ALTERED
AS SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE
TABLESPACE.
-676
A 32K PAHE BUFFERPOOL MAY NOT BE USED FOR AN INDEX.
-677
INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION.
-678
THE LITERAL {literal} SPECIFIED FOR THE INDEX LIMIT KEY MUST
CONFORM TO THE DATATYPE {datatype} OF THE CORRESPONDING
COLUMN {column-name}.
-679
THE OBJECT {name} CANNOT BE CREATED BECAUSE A DROP IS
PENDING ON THE OBJECT.
-680
TOO MANY COLUMNS SPECIFIED FOR A TABLE.
-681
COLUMN {column-name} IN VIOLATION OF INSTALLATION DEFINED
FIELD PROCEDURE. RT: return-code, RS: reason-code,
MSG: message-token.
-682
FIELD PROCEDURE {proc-name} COULD NOT BE LOADED.
-683
INVALID COLUMN TYPE FOR FIELDPROC OR BIT DATA OPTION,
{column-name}.
-684
THE LENGTH OF LITERAL LIST BEGINNING {string} IS TOO LONG.
-685
INVALID FIELD TYPE, {column-name}.
-686
COLUMN DEFINED WITH A FIELD PROCEDURE CANNOT COMPARE WITH
ANOTHER COLUMN WITH DIFFERENT FIELD PROCEDURE.
-687
FIELD TYPE INCOMPARABLE.
-688
INCORRECT DATA RETURNED FROM FIELD PROCEDURE, {column-name,
msgno}.
-802
EXCEPTION ERROR {exception-type} HAS OCCURRED DURING
{operation-type} OPERATION ON {data-type} DATA,
POSITION {pos#}.
-803
AN INSERTED OR UPDATED VALUE INVALID BECAUSE THE INDEX
CONSTRAINS COLUMNS OF THE TABLE SUCH THAT NO TWO ROWS CAN
CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID IS {rid}.
-804
AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT
PARAMETERS FOR THE SQL STATEMENT.
-805
PROGRAM NAME {program-name} NOT FOUND IN PLAN {plan-name}.
-811
THE RESULT OF AN IMBEDDED SELECT IS A TABLE OF MORE THAN ONE
ROW, OR THE RESULT OF THE SUBQUERY OF A BASIC PREDICATE IS
MORE THAN ONE VALUE.
-815
A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY
SPECIFIED IN AN EMBEDDED SELECT STATEMENT OR A SUBQUERY OF
A BASIC PREDICATE.
-817
THE INSERT, UPDATE, DELETE, DDL, OR AUTHORIZATION STATEMENT
CANNOT BE EXECUTED BECAUSE THE IMS/VS TRANSACTION IS
INQUIRY ONLY.
-818
THE PRECOMPILER-GENERATED TIMESTAMP x IN THE LOAD MODULE IS
DIFFERENT FROM THE BIND TIMESTAMP y BUILT FROM THE DBRM.
-819
THE VIEW CANNOT BE PROCESSED BECAUSE THE LENGTH OF ITS PARSE
TREE IN THE CATALOG IS ZERO.
-820
THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE {catalog-tbl}
CONTAINS A VALUE THAT IS NOT VALID IN THIS RELEASE.
-822
THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR
VARIABLE ADDRESS.
-840
TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST.
-901
UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES
NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL
STATEMENTS.
-904
UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE.
REASON {reason-code}, TYPE OF RESOURCE {resource-type}, AND
RESOURCE NAME {resource-name}.
-905
UNSUCCESSFULL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED
, RESOURCE NAME = resource-name LIMIT = limit-amt1 CPU
SECONDS limit-amt2 SERVICE UNITS, DERIVED FROM limit-source.
-906
THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION
IS DISABLED DUE TO A PRIOR ERROR.
-907
UNABLE TO DETERMINE IF THE ATTEMPT TO COMMIT UPDATES MADE AT
A REMOTE SITE WAS SUCCESSFUL OR NOT.
-909
THE OBJECT HAS BEEN DELETED.
-910
THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A DROP
OR ALTER IS PENDING.
-911
THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO
DEADLOCK OR TIMEOUT. REASON reason-code, TYPE OF RESOURCE
resource-type, AND RESOURCE NAME resource-name.
-913
UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT. REASON
CODE reason-code, TYPE OF RESOURCE resource-type, AND
RESOURCE NAME resource-name.
-922
CONNECTION AUTHORIZATION FAILURE: error-type ERROR.
-923
CONNECTION NOT ESTABLISHED: DB2 condition REASON reason-code
, TYPE resource-type, NAME resource-name.
-924
DB2 CONNECTION INTERNAL ERROR, function-code, retuen-code,
reason-code.
-925
COMMIT NOT VALID IN IMS/VS OR CICS ENVIRONMENT.
-926
ROLLBAKC NOT VALID IN IMS/VS OR CICS ENVIRONMENT.
-927
THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING
ENVIRONMENT WAS NOT ESTABLISHED. THE PROGRAM SHOULD BE
INVOKED UNDER THE DSN COMMAND.
You Loser! You have to enter a code to find one! Try again.