S001 - AN INPUT/OUTPUT ERROR CONDITION WAS ENCOUNTERED DURING EXECUTION OF A CHECK/GET/PUT MACRO INSTRUCTION. EITHER NO SYNAD ROUTINE WAS PROVIDED TO HANDLE THE ERROR, OR DCB=EROPT=ABE WAS SPECIFIED OR DEFAULTED.
IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S001 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S001-RC)POSSIBLE CAUSE
INPUT RECORD DESCRIBED INCORRECTLY, LENGTH ERROR
TRIED TO READ AFTER ENCOUNTERING END OF FILE
RECFM V IS INCOMPATIBLE WITH TRTCH ET
TRIED TO WRITE ON AN INPUT FILE
READ INTO A TABLE WHOSE SUBSCRIPT WAS ZERO
INCORRECT LABEL PARAMETER
TRTCH PARM WAS WRONG
TAPE BEING READ IN WRONG DENSITY
DIRECTORY OF PDS WAS OVERWRITTEN
NSL LABEL HAD INCORRECT DSNAME, OPERATOR CANCELLED
TRUE I/O FAILURE, UCB SHOW REDUNDANCY
HARDWARE ERROR - BAD TAPE OR TAPE DRIVE
SECONDARY SPACE ALLOCATION FOR DASD OUTPUT FILE TOO SMALL (SEE SB37)
COBOL - INCORRECT USE OF BLOCK CONTAINS CLAUSE
- HAD RECORDING MODE F WHEN GENERATED, BUT NOT WHEN READ
S001 - 01 - AN I/O ERROR OCCURRED DURING BDAM CREATE, BSAM, BISAM, QSAM, OR BDAM AND NO SYNAD EXIT WAS SPECIFIED BY THE USER.
S001 - 02 - AN ERROR WAS ENCOUNTERED WHILE ATTEMPTING TO CLOSE THE DATASET.
**S001 - 03 - FOR QSAM, AN ERROR WAS ENCOUNTERED THAT COULD NOT BE ACCEPTED.
S001 - 04 - FOR QSAM, ABE OR AN INVALID VALUE FOR EROPT PARAMETER IN THE DCB AND/OR NO ERROR HANDLING (SYNAD) EXIT WAS SPECIFIED.
S001 - 05 - FOR QSAM, A GET WAS ISSUED AFTER END-OF-FILE.
S002 - RECORD IS GREATER THAN 32,768 BYTES, EXCEEDS MAXIMUM TRACK LENGTH OR STATED BLOCKSIZE, COULD NOT BE CONTAINED IN ONE EXTENT, OR TOO MANY TRACKS SPECIFIED FOR CYLINDER OVERFLOW.
IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
S002 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S002-RC)
POSSIBLE CAUSE
DCB HAD THE WRONG BLOCK SIZE
IEHMOVE - ATTEMPT TO RENAME DATA SET WHEN NEW NAME ALREADY EXISTS
WRONG RECORD FORMAT SPECIFIED IN JCL
S002 - 04 - AN INVALID RECORD WAS ENCOUNTERED ON A GET OPERATION.
THE LENGTH FIELD OF A RECORD DESCRIPTOR WORD (RDW) FOR A VARIABLE LENGTH RECORD SPECIFIES A VALUE LESS THAN 4.
S002 - 08 - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OR WRITE OPERATION. THE RECORD OR BLOCK LENGTH PLUS THE KEY LENGTH AND REQUIRED OVERHEAD ADD UP TO MORE THAN 32,767 BYTES.
S002 - 0C - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OR WRITE OPERATION. THE RECORD OR BLOCK LENGTH PLUS THE KEY LENGTH AND REQUIRED OVERHEAD IS GREATER THAN THE DASD TRACK CAPACITY.
S002 - 10 - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OPERATION;
THE DATASET USES THE TRACK OVERFLOW FEATURE. THE RDW FOR A VARIABLE LENGTH RECORD SPECIFIES A LENGTH GREATER THAN 32,752.
S002 - 14 - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OR WRITE OPERATION. THE RECORD LENGTH IS GREATER THAN THE BLOCKSIZE SPECIFIED IN THE DCB.
S002 - 18 - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OPERATION;
THE DATASET USES THE VARIABLE RECORD FORMAT. THE LENGTH VALUE OF THE RDW IS EITHER: LESS THAN 4, GREATER THAN 32,767, GREATER THAN THE BLOCKSIZE SPECIFIED IN THE DCB, OR LESS THAN 5 IF ASA CONTROL CHARACTERS ARE BEING USED.
S002 - 1C - THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. A WRITE MACRO WAS ISSUED FOR A RECORD LARGER THAN THE TRACK CAPACITY, AND THE RECORD FORMAT DOES NOT USE THE TRACK OVERFLOW FEATURE.
S002 - 20 - THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. A WRITE MACRO WAS ISSUED CAUSING A SECONDARY EXTENT TO BE OBTAINED. THE BLOCK WILL NOT FIT ON THE AMOUNT OF SPACE ALLOCATED FOR THE
SECONDARY EXTENT.
S002 - 24 - THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. A WRITE MACRO WAS ISSUED TO WRITE OUT A BLOCK LARGER THAN THE PRIMARY EXTENT ON THE PREALLOCATED DATASET. THIS COULD ALSO OCCUR IF ALLOCATION OF THE PRIMARY EXTENT WAS NON-CONTIGUOUS AND ANY OF THE SECONDARY EXTENTS WERE SMALLER THAN THE BLOCK.
S002 - 28 - THE ERROR OCCURRED DURING THE CREATION OF A DIRECT DATASET. DURING THE EXECUTION OF OPEN IT WAS DETECTED THAT THE BLOCKSIZE WAS LARGER THAN THE PRIMARY EXTENT.
S002 - 2C - THE ERROR OCCURRED WHILE OPENING AN ISAM DATASET. TOO MANY TRACKS WERE SPECIFIED FOR CYLINDER OVERFLOW.
S002 - 30 - ONE OF THE FOLLOWING IS TRUE:
- A READ WAS ISSUED BUT THE LENGTH TO BE READ WAS ZERO.
- A QSAM PUT WITH MOVE MODE WAS ISSUED FOR RECFM=F, FB OR U BUT DCBLRECL CONTAINED A NON-POSITIVE VALUE.
S002 - 34 - A READ MACRO WAS ISSUED FOR AN OUTPUT-ONLY DASD DATA SET.
S002 - 3C - PDSE MEMBER CREATION WAS PREVENTED BECAUSE THE PDSE ALREADY HAD THE MAXIMUM NUMBER OF MEMBERS (2**19 - 2).
S002 - 50 - SERIALIZATION OF AN INTERNAL SAM CONTROL BLOCK (SACB) USED FOPR PROCESSING HAS BEEN VIOLATED.
S002 - 54 - DEBCHK FAILURE DURING PDSE PROCESSING.
S002 - 58 - AN INTERNAL SAM CONTROL BLOCK (SACB) USED FOR PROCESSING PDSE REQUESTS IS INCORRECT.
S002 - 5C - AN INTERNAL SAM CONTROL BLOCK (FRQ) USED FOR QUEUING PDSE REQUESTS IS INCORRECT.
S002 - 60 - NON-ZERO KEYLENGTH SPECIFIED FOR OUTPUT PDSE MEMBER.
S002 - 64 - FOR BSAM, THE READ OR WRITE REQUEST COULD NOT BE ACCEPTED BECAUSE THE VALUE OF NCP INT THE DCB HAD ALREADY BEEN REACHED.
S002 - 68 - INCORRECT BLOCKSIZE SPECIFIED.
S002 - 6C - UNABLE TO CREATE A PDSE MEMBER.
S002 - 70 - UNABLE TO UPDATE AN INTERNAL SAM CONTROL BLOCK (PACB) USED FOR PDSE PROCESSING WITH INFORMATION CONCERNING THE MEMBER BEING ACCESSED.
S002 - 74 - AN INTERNAL SAM CONTROL BLOCK (PACB) USED FOR STORING PDSE DIRECTORY AND MEMBER INFORMATION IS INCORRECT.
S002 - 78 - ERROR RETURN FROM IGWFMPCR WHEN ATTEMPTING TO GIVE CONTROL TO A ROUTINE TO PROCESS PDSE REQUESTS.
S002 - 7C - POINT DETECTED THAT INFORMATION CONCERNING THE MEMBER BEING ACCESSED IS NOT FOUND IN THE PACB.
S002 - 80 - POINT DETECTED AN ERROR WHILE ATTEMPTING TO SYNCHRONIZE DATA ON OUTPUT.
S002 - 84 - POINT DETECTED AN ERROR WHILE ATTEMPTING TO RECONNECT TO A PDSE MEMBER FOR HOLD.
S002 - 88 - POINT DETECTED AN ERROR WHILE ATTEMPTING TO RECONNECT TO A PDSE MEMBER FOR I/O.
S002 - 8C - POINT DETECTED AN ERROR WHILE ATTEMPTING TO DISCONNECT FROM A PDSE MEMBER.
S002 - 90 - POINT DETECTED AN ERROR WHILE ATTEMPTING TO CONNECT TO A PDSE MEMBER.
S002 - 94 - INCORRECT ATTEMPT TO CREATE A PDSE MEMBER SINCE THE MAXIMUM NUMBER OF MEMBERS HAVE ALREADY BEEN CREATED.
S002 - 98 - UNABLE TO COMPLETE A WRITE REQUEST ISSUED WITHIN A PDSE MEMBER.
S002 - 9C - INCORRECT UPDATE WRITE DETECTED. ALL OUTSTANDING READS HAD NOT BEEN CHECKED PRIOR TO THE WRITE.
S002 - A0 - INCORRECT ATTEMPT TO ACCESS A PDSE DIRECTORY. EITHER:
- WRITE ATTEMPTED TO THE DIRECTORY OF A PDSE.
- READ ATTEMPTED TO THE DIRECTORY OF A PDSE AND EITHER THE RECFM WAS NOT F WITH BLKSIZE >= 256
OR RECFM WAS NOT U WITH BLKSIZE >= 256.
S002 - A4 - UNABLE TO COMPLETE THE READ AGAINST THE PDSE DIRECTORY DUE TO AN ERROR RETURN CODE FROM AN SMS SERVICE USED TO OBTAIN DIRECTORY INFORMATION.
S002 - A8 - MAXIMUM NUMBER OF RECORDS IN MEMBER HAS BEEN EXCEEDED.
S002 - AC - BAD BUFFER FORMAT DETECTED FOR VARIABLE LENGTH RECORDS.
EITHER:
- RDW LENGTH IS LESS THAN 4.
- LENGTH OF SPANNED RECORD IS GREATER THAN 32760.
- THE SUM OF THE LENGTHS IN THE RDWS PLUS 4 DOES NOT EQUAL THE LENGTH SPECIFIED IN THE BDW.
- RECFM DOES NOT SPECIFY BLOCKED BUT MORE THAN 1 RDW IN BUFFER.
S002 - B0 - EITHER RECFM=F AND DCBBLKSI DOES NOT EQUAL DCBLRECL, OR RECFM=FB AND DCBBLKSI IS NOT A MULTIPLE OF DCBLRECL.
S003 - THE ERROR OCCURED DURING END-OF-BLOCK PROCESSING USING EITHER BSAM OR QSAM. THE ERROR OCURRED BECAUSE THE I/O MACRO INSTRUCTIONS FOR A 3525-ASSOCIATED DATA SET WERE NOT EXECUTED IN THE PROPER SEQUENCE.
- IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
- S003 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S003-RC)
S003 - 01 - THE ERROR WAS A READ SEQUENCE ERROR.
S003 - 02 - THE ERROR WAS A PUNCH SEQUENCE ERROR.
S003 - 03 - THE ERROR WAS A PRINT SEQUENCE ERROR.
S004 - THE ERROR OCCURED DURING OPEN PROCESSING USING EITHER BSAM OR QSAM BECAUSE A CONFLICTING OR INVALID DCB PARAMETER (FUNC OR RELATED PARAMETER) IS SPECIFIED.
- IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
- S004 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S004-RC)
S004 - 01 - INVALID DCB FUNC PARAMETER SPECIFIED.
S004 - 02 - INVALID COMBINATION OF DCB FUNC PARAMETER AND CNTRL MACRO SPECIFIED.
S004 - 03 - CONFLICTING ACCESS METHODS SPECIFIED.
S004 - 04 - INVALID DCB SPECIFIED FOR 3505 OR 3525.
S004 - 05 - INVALID FORMAT CARD OR AN INVALID DEVICE SPECIFIED WITH OPTICAL MARK READ (OMR).
S004 - 06 - DATA PROTECTION IMAGE NOT FOUND IN THE SYS1.IMAGELIB DATA SET, VOLUME CONTAINING SYS1.IMAGELIB NOT MOUNTED, OR SYS1.IMAGELIB NOT CATALOGED.
S005 - THE ERROR OCCURRED BECAUSE OF AN INVALID DECB DURING READ PROCESSING USING BSAM.
- IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
- S005 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S005-RC)
S005 - 04 - A REQUIRED ADDRESS WAS NOT SPECIFIED IN THE DECB. THIS CAN BE EITHER THE HEADER ADDRESS AND/OR THE AREA ADDRESS.
S005 - 08 - THE RBL TYPE OF READ WAS NOT USED FOR THE 3886.
S006 - THE PROGRAM HAD AN INCORRECT AUTHORIZATION TO RUN A 1419.
S008 - THE ERROR OCCURRED DURING EXECUTION OF A SYNAD ROUTINE. THE ROUTINE WAS GIVEN CONTROL FOLLOWING EXECUTION OF A BSAM CHECK MACRO INSTRUCTION.
S013 - CONFLICTING OR UNSUPPORTED PARAMETERS IN DCB; MEMBER NAME SPECIFIED IN DD NOT FOUND; NO DIRECTORY ALLOCATION SUBPARAMETER IN DD.
- IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE
- S013 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S013-RC)
POSSIBLE CAUSE
DCB PARAMETERS CONFLICT, NO BLKSIZE OR NOT VALID MULTIPLE OF LRECL
MISSING OR MISPLACED SYSIN DD CARD
PARTITIONED DATA SET MEMBER NOT FOUND
MERGE - SORTIN01 DOES NOT CONTAIN THE MAXIMUM BLOCKSIZE
JCL - TRIED TO CREATE A PDS WITHOUT ALLOCATING DIRECTORY BLOCKS
S013 - 04 - AMERICAN NATIONAL STANDARD LABELS WERE SPECIFIED IN THE LABEL PARAMETER OF THE DD STATEMENT, BUT ARE NOT SUPPORTED BY THE SYSTEM. CORRECT THE LABEL PARAMETER.
- OPTCD=Q WAS SPECIFIED BUT IS NOT SUPPORTED BY THE SYSTEM. CORRECT THE DCB OPTCD OPTION.
S013 - 08 - AMERICAN NATIONAL STANDARD LABELS WERE SPECIFIED IN THE LABEL PARAMETER OF THE DD STATEMENT, BUT THE UNIT PARAMETER SPECIFIED A 7-TRACK TAPE DRIVE. ANSI LABELS A VALID ONLY FOR 9-TRACK UNITS.
S013 - 0C - A BUFFER LENGTH OF 0 WAS SPECIFIED FOR A BDAM DATASET FOR WHICH DYNAMIC BUFFERING WAS REQUESTED.
S013 - 10 - AN OPEN MACRO WAS ISSUED FOR A NULL DATASET AND BLKSIZE AND BUFL ARE BOTH 0. SPECIFY ONE OR THE OTHER AS NON-ZERO.
S013 - 14 - AN OPEN MACRO WAS ISSUED WITH OUTPUT OR OUTIN SPECIFIED. DCB SPECIFIES DSORG=PO, BUT THE DSCB INDICATES THE DATASET IS NOT PARTITIONED. CHANGE DSORG TO PS, OR CREATE DATASET AS PDS.
- AN OPEN MACRO WAS ISSUED WITH INPUT SPECIFIED. THE DSCB INDICATES THAT DSORG=PO, BUT THE DCB SPECIFIES NEITHER DSORG=PO NOR PS.
S013 - 18 - AN OPEN WAS ISSUED FOR A PARTITIONED DATASET. THE SPECIFIED MEMBER NAME WAS NOT FOUND IN THE DATASET.
S013 - 1C - AN OPEN MACRO WAS ISSUED FOR A PARTITIONED DATASET, BUT AN I/O ERROR WAS ENCOUNTERED SEARCHING THE DIRECTORY.
S013 - 20 - OPEN MACRO INSTR FOR SEQUENTIAL DATASET USING DCB, BLKSIZE IS NOT A MULTIPLE OF THE LRECL.
S013 - 24 - AN OPEN WAS ISSUED WITH INPUT, INOUT, RDBACK, OR UPDATE SPECIFIED, BUT THE DCB MACRF DID NOT SPECIFY EXCP, GET, OR READ.
S013 - 28 - AN OPEN MACRO WAS ISSUED WITH OUTPUT OR OUTIN SPECIFIED, BUT THE DCB DID NOT SPECIFY A MACRF OF EXCP, PUT, OR WRITE.
S013 - 2C - A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE WITH EXCHANGE BUFFERING WAS OPENED FOR INPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0.
S013 - 30 - A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE WITH EXCHANGE BUFFERING WAS OPENED FOR OUTPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS (DCBBUFCB) WAS 0.
S013 - 34 - INVALID LRECL(INCOMPATIBLE DCB INFO)
S013 - 38 - AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET ON A DIRECT ACCESS DEVICE WITH TRACK OVERFLOW, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS ZERO. THIS TYPE OF ERROR OFTEN OCCURS IF A DCB IS SHARED BY TWO OR MORE TASKS, OR IS OPENED AND CLOSED SEVERAL TIMES WITHIN ONE JOB STEP.
S013 - 3C - A SEQUENTIAL DATASET WAS OPENED FOR INPUT OR OUTPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0. THIS TYPE OF ERROR OFTEN OCCURS IF A DCB IS SHARED BY TWO OR MORE TASKS, OR IS OPENED AND CLOSED SEVERAL TIMES WITHIN ONE JOB STEP.
S013 - 40 - A SEQUENTIAL OR DIRECT DATASET WAS OPENED FOR INPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0.
S013 - 44 - AN OPEN MACRO WAS ISSUED FOR A DATASET ON A DIRECT ACCESS DEVICE FOR WHICH CHAINED SCHEDULING WAS SPECIFIED, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0.
S013 - 48 - AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS ZERO.
S013 - 4C - AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE. THE SYSTEM DETERMINED THAT A BUFFER POOL EXISTED FOR THIS DATASET AND MADE THE APPROPIATE TEST SHOWN BELOW WITH UNSATISFACTORY RESULTS:
- IF THE DATA WAS TO BE SENT DIRECTLY TO A UNIT RECORD DEVICE (NO SPOOLING), THE BUFFER LENGTH VALUE IN THE BUFFER CONTROL BLOCK HAD TO BE EQUAL TO OR GREATER THAN THE VALUE SPECIFIED IN THE DCB FOR LOGICAL RECORD LENGTH (LRECL).
- OTHERWISE, THE BUFFER LENGTH VALUE IN THE BUFFER CONTROL BLOCK HAD TO BE EQUAL TO OR GREATER THAN THE VALUE SPECIFIED IN THE DCB FOR BLKSIZE.
S013 - 50 - AN OPEN MACRO ISSUED FOR A DATASET ALLOCATED TO A PRINTER DID NOT HAVE OUTPUT SPECIFIED AS AN OPEN OPTION.
S013 - 54 - NO SECONDARY CONTROL UNIT COULD NOT BE FOUND FOR A 1419.
S013 - 58 - AN OPEN MACRO WAS ISSUED FOR A PAPER TAPE DATASET AND CONCATENATION WITH UNLIKE ATTRIBUTES WAS SPECIFIED.
S013 - 5C - AN OPEN MACRO WAS ISSUED FOR A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE. THE DATASET CONTAINED SPANNED VARIABLE LENGTH RECORDS LARGER THAN 32,756 BUT GET LOCATE MODE WAS NOT USED.
ALTERNATIVELY, BFTEK=A WAS SPECIFIED WITH MACRF=GM OR MACRF=PM.
S013 - 60 - AN OPEN MACRO WAS ISSUED FOR A DATASET WITH A DCB SPECIFYING RECFM=F, AND BLKSIZE WAS NOT EQUAL TO LRECL. CORRECT THE RECFM TO FB, OR MAKE LRECL AND BLKSIZE EQUAL.
S013 - 64 - AN OPEN MACRO WAS ISSUED FOR A NULL DATASET USING AN ACCESS METHOD OTHER THAN QSAM OR BSAM. THIS IS A NO-NO.
S013 - 68 - AN OPEN WAS ISSUED FOR A DATASET WHOSE DCB SPECIFIED BLKSIZE GREATER THAN 32,767, WHICH IS THE MAXIMUM ALLOWED.
S013 - 6C - AN OPEN MACRO WAS ISSUED FOR A DATASET WITH RECFM=T IN THE DCB, REQUESTING TRACK OVERFLOW, BUT THE DIRECT ACCESS DEVICE DOES NOT SUPPORT TRACK OVERFLOW.
S013 - 70 - AN OPEN MACRO WAS ISSUED FOR A DATASET ON MAGNETIC TAPE. A CONFLICT EXISTS AMONG LABEL PARAMETERS ON THE DD STATEMENT, AND DCBRECFM, DCBOPTCD, DCBBUFOF, AND DCBUSASI GIVE THE APPEARANCE
OF MIXED USASI AND EBCDIC ATTRIBUTES TO THE DATASET; OR OPTCD=Q WAS SPECIFIED FOR A DATASET ON A DEVICE OTHER THAN MAGNETIC TAPE.
S013 - 74 - AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET, BUT THE OPEN OPTION DID NOT SPECIFY INPUT.
S013 - 78 - AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET. THE BUFL PARAMETER IN THE DCB WAS SPECIFIED AS ZERO.
S013 - 7C - AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET, BUT THE LRECL PARAMETER IN THE DCB WAS ZERO.
S013 - 80 - AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET, BUT THE BUFL WAS LESS THAN THE LRECL.
S013 - 84 - AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET. THE NUMBER OF BUFFERS SPECIFIED IN THE BUFFER POOL CONTROL BLOCK IS NOT THE SAME AS THAT SPECIFIED IN THE DCBBUFNO.
S013 - 88 - AN OPEN MACRO WAS ISSUED FOR A TELECOMMUNICATIONS DEVICE BUT THE DCBDSORG DID NOT SPECIFY TSO.
S013 - 8C - AN OPEN MACRO WAS ISSUED FOR A DIRECT ORGANIZATION DATASET (BDAM) BUT THE DCBRECFM PARAMETER WAS NOT SPECIFIED.
S013 - A4 - A DCB WAS OPENED FOR A SYSIN OR SYSOUT DATASET BUT THE DSORG WAS NOT SPECIFIED AS PS.
S013 - A8 - AN INVALID RECORD FORMAT WAS REQUESTED FOR A SYSIN OR SYSOUT DATASET. (RECFM=D, VS, OR VBS ARE INVALID FOR SYSIN)
S013 - AC - A QSAM OPEN WAS ISSUED WITH A NON-ZERO KEYLENGTH IN THE DCB WHICH IS NOT SUPPORTED. (NOW SUPPORTED, BUT WITH INPUT ONLY.)
S013 - B0 - AN OPEN MACRO WAS ISSUED WITH THE RDBACK OPTION FOR A DCB SPECIFYING A RECORD FORMAT OF VARIABLE SPANNED RECORDS. THESE ARE CONFLICTING PARAMETERS.
S013 - B4 - AN OPEN MACRO WAS ISSUED WITH THE INOUT/OUTIN OPTION FOR A DCB SPECIFYING THE QSAM MACRF VALUES; THESE ARE CONFLICTING PARAMETERS.
S013 - B8 - AN OPEN MACRO WAS ISSUED FOR THE 3890 DOCUMENT PROCESSOR AND DCBHDR WAS NOT SPECIFIED IN THE DCB.
S013 - BC - A SYSIN OR SYSOUT DCB WAS OPENED WITH INVALID OPTIONS. EITHER OPEN SPECIFIED UPDAT OR RDBACK, OR THE POINT MACRO FUNCTION WAS SPECIFIED IN MACRF=RP OR WP. REPOSITIONING OR UPDATING A SPOOLED DATASET IS NOT PERMITTED.
S013 - C0 - A SYSIN OR SYSOUT DATASET COULD NOT BE OPENED BY A JOB ENTRY SUBSYSTEM. THE FAILING DCB IS NOT OPENED, HOWEVER THE TASK IS NOT TERMINATED. PROCESSING CONTINUES FOR OTHER DCBS OPENED.
S013 - C4- DURING THE CREATION OF A DIRECT DATASET, THE OPEN ROUTINE FOUND THAT THE DCB SPECIFIED READ(R) OR GET(G) IN THE MACRF FIELD. ONLY WRITE LOAD (WL) IS ALLOWED.
S013 - C8 - THE OPEN SUBSYSTEM EXECUTOR MODULE WAS PASSED AN ERROR RETURN CODE IN REGISTER 15 AFTER ISSUING THE IEFSSREQ MACRO TO CONNECT THE USER'S ACB TO THE SUBSYSTEM. THIS INDICATES THE SUBSYSTEM WAS NOT OPERATING.
S013 - CC - SETPRT PROCESSING FAILED TO SET UP THE DEVICE DURING AN OPEN FOR THE IBM 3800 PRINTING SUBSYSTEM.
S013 - D0 - AN INVALID RECORD FORMAT OF FBS OR FS WAS SPECIFIED FOR A PARTITIONED DATA SET.
S013 - D0 - A DB/DBS RECORD FORMAT WAS SPECIFIED FOR QSAM LOCATE MODE, BUT THE LOGICAL RECORD INTERFACE IS NOT PRESENT IN THE ASSOCIATED BUFFER CONTROL BLOCK; IE. SEGMENT MODE IS IMPLIED.
S013 - D8 - A CONFLICT HAS OCCURRED FOR THE SPANNED RECORD FORMAT EXTENDED LOGICAL RECORD INTERFACE (XLRI). BUFFER CONTROL BLOCK; IE. SEGMENT MODE IS IMPLIED.
S013 - E4 - THE LIMIT OF 123 EXTENTS FOR A CONCATENATED PARTITIONED DATA SET HAS BEEN EXCEEDED. (USED TO BE 256 EXTENTS?)
S013 - E8 - THE OPEN VERIFICATION FUNCTION OF THE IEFSSREQ MACRO RETURNED AN ERROR CODE IN REGISTER 15.
S014 - 04 - (04 IS THE ONLY POSSIBLE RETURN CODE ASSOCIATED WITH S014)
- THE TASK WHICH ISSUED A CLOSE FOR A DASD DATA SET WAS NOT THE TASK WHICH OPENED THE DATA SET.
S016 - AN ERROR OCCURRED IN SAM SIO/PAGE FIX OR DASD END-OF-BLOCK MODULES BECAUSE OF ONE OF THE FOLLOWING:
- THE DASD END-OF-BLOCK MODULES ISSUED AN EXCPVR SVC REQUEST ON BEHALF OF A USER REQUEST, BUT A PREVIOUS EXCPVR SVC REQUEST HAD NOT COMPLETED. ONE OF THE FOLLOWINF OCCURRED:
- A DATA EXTENT CONTROL BLOCK (DECB) WAS USED TWICE.
- MULTIPLE READS OR WRITES WERE ISSUED, BUT ONLY THE LAST READ OR WRITE WAS CHECKED.
- AN EXCPVR SVC REQUEST ON BEHALF OF A USER REQUEST WAS GOING TO BE ISSUED TO READ A DATA SET THAT IS EXECUTE ACCESS PROTECTED, BUT THE USER IS NOT IN SUPERVISOR STATE. (THE SAM SIO APPENDAGE ISSUED THIS ABEND.)
S020 - DURING AN OPEN FOR A BDAM DATA SET THE CONTROL PROGRAM FOUND THAT DCBMACRF DID NOT CONTAIN AN A, K OR I (RC=04), OR THE BDAM DATA SET CONTAINED ZERO EXTENTS (RC=08).
S021 - A CALLER OF THE ASCBCHAP ROUTINE PASSED TO ASCBCHAP AN ASCB ADDRESS THAT HAD BITS SET TO ONE IN ITS HIGH ORDER BYTE.
S022 - THE VPSS ENCOUNTERED A MISSING DEVICE END ON CONTROL PORT 0.
S023 - LNKLST LOOKASIDE (LLA) COULD NOT OBTAIN ALL THE LNKLST DIRECTORY ENTRIES.
S024 - AN ABNORMAL TERMINATION OCCURRED IN PRINT SERVICES FACILITY.
S027 - AN ABNORMAL TERMINATION OCCURRED IN PRINT SERVICES FACILITY.
S028 - A PAGING OPERATION HAS NOT COMPLETED SUCCESSFULLY DUE TO ONE OF THE FOLLOWING:
- A PERMANENT I/O ERROR OCCURRED WHILE ATTEMPTING A PAGE-IN OR SWAP-IN OPERATION. THE DATA BEING PAGED IN OR SWAPPED IN IS LOST.
- A REAL STORAGE MANAGEMENT ROUTINE OR ANOTHER SYSTEM ROUTINE PERFORMING A SERVICE FOR RSM SUFFERED AN INTERMEDIATE ERROR. THE FUNCTION PERFORMED IS TERMINATED.
- A AUXILIARY STORAGE MANAGEMENT ROUTINE SUFFERED A TRANSLATION ERROR WHILE USING THE CONTROL REGISTER OF ANOTHER ADDRESS SPACE TO UPDATE THAT ADDRESS SPACE'S LSQA.
S029 - LINES EXCEEDED
S02A - JES2 FOUND THAT DATA MANAGEMENT CONTROL BLOCKS OR THE JES2 UBUF CONTROL BLOCK WAS NO LONGER VALID DURING EXECUTION OF A DATA MANAGEMENT REQUEST FOR A SPOOL DATA SET.
S02B - A USER EXIT ROUTINE ISSUED A RETURN CODE GREATER THAN THAT SPECIFIED IN THE &MAXRC PARAMETER OF THE $EXIT### MACRO.
S02C - AN ERROR OCCURRED IN JES2 SUPPORT OF AN FSS ADDRESS SPACE.
S02D - THE JES2 MAIN TASK WAS ABENDED BY THE OPERATOR OR A CATASTROPHIC ERROR.
S030 - DURING A BISAM OR QISAM OPEN DCBMACRF DID NOT INDICATE A VALID MODE OF OPERATION.
S031 - SPACE REQUESTED NOT AVAILABLE, DECREASE THE SPACE ALLOCATION
S032 - DURING A BISAM OR QISAM OPEN DCBMACRF WAS NOT VALID FOR ISAM.
S03B - ISAM DATASET TO BE PROCESSED, BUT NOT CREATED OR ITS DCB NOT CLOSED AFTER CREATION.
POSSIBLE CAUSE
- DATASET WAS TO BE WRITTEN ON BUT WAS OPENED AS INPUT
- LRECL/BLKSIZE PROBLEM EXISTS - INVALID VALUES OR NOT MULTIPLES
S03D - THE ERROR OCCURRED DURING THE EXECUTION OF A QISAM OR BISAM OR BDAM MACRO INSTRUCTION.
- IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S03D OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S03D-RC)
S03D - 04 - AN OPEN MACRO WAS ISSUED FOR AN INDEXED SEQUENTIAL OR DIRECT DATASET. THE VOLUME SERIAL NUMBERS ON THE DD STATEMENT WERE NOT SPECIFIED IN THE SAME ORDER THAT THE DATASET WAS CREATED.
S03D - 08 - AN OPEN MACRO WAS ISSUED FOR AN INDEXED SEQUENTIAL DATASET. THE FIRST VOLUME OF THE DATASET DOE NOT HAVE A FORMAT2 DSCB.
S03D - 0C - AN OPEN MACRO WAS ISSUED FOR A DIRECT DATASET. THE DATASET HAS AN INDEXED SEQUENTIAL ORGANIZATION.
S046 - SORT CAPACITY EXCEEDED
S047 - AN UNAUTHORIZED PROGRAM REQUESTED A RESTRICTED SVC.
S04B - AN INVALID OPERATION CODE WAS PASSED TO A TSO LINKAGE ASSIST ROUTINE (LAR).
S04B - 04 - THE LAR (IKJEFTSL) FOR THE TERMINAL MONITOR PROGRAM (TMP) RECEIVED AN INVALID FUNCTION NUMBER.
S04B - 08 - THE SERVICE ROUTINE'S LAR (IKJTSLAR) WAS INVOKED AT IKJTSLAR, WHICH IS AN INVALID SERVICE ROUTINE ENTRY POINT.
S04C - THE TERMINAL MONITOR PROGRAM (TMP) WAS INVOKED AT ENTRY POINT IKJEFT1A AND THE TMP DETACHED A PROGRAM THAT COMPLETED WITH A NON-ZERO COMPLETION CODE (WHICH IS IN REGISTER 15).
S04E - INTERNAL IBM DATABASE 2 (DB2) ERROR.
S04F - DB2 ABNORMAL TERMINATION TO AVOID DATA INTEGRITY PROBLEMS.
S052 - A PROGRAM MADE AN INVALID PC/AUTH REQUEST. CHECK THE CODE IN REGISTER 15.
S053 - A PROGRAM MADE A PC/AUTH REQUEST BUT AN ERROR PREVENTED NORMAL COMPLETION. CHECK THE CODE IN REGISTER 15.
S061 - I/O ERROR IN SORT EXEC, CHECK FOR DATA MESSAGES
S063 - SORTIN DATA PROBLEM
S064 - AN ADDRESS SPACE THAT HOLDS A CROSS MEMORY LOCAL LOCK (CML LOCK) TERMINATED ABNORMALLY BEFORE IT FREED THE LOCK.
S66D - LIBRARY ACCESS PROBLEM. LOOKS THE SAME AS A S106 ABEND. (LLA)
S071 - THE OPERATOR PRESSED THE RESTART KEY TO ACTIVATE THE SYSTEM'S RECOVERY AND TERMINATION PROCESS. THE PROGRAM RUNNING AT THE TIME THE OPERATOR PRESSED THE RESTART BUTTON WAS SENT THROUGH
ABEND PROCESSING BECAUSE THE OPERATOR DETERMINED IT WAS IN A NONCANCELABLE LOOP OR WAIT STATE.
S078 - RCT (REGION CONTROL TASK) PROCESSING HAS RECEIVED AN UNACCEPTABLE RETURN CODE FROM AN INVOKED ROUTINE AND CANNOT CONTINUE PROCESSING. RCT RECOVERY RECORDS THE ERROR IN SYS1.LOGREC, PERFORMS RESOURCE CLEAN-UP, REQUESTS A SYS1.DUMP OF THE ADDRESS SPACE AND THEN REQUESTS ADDRESS TERMINATION.
S079 - RCT (REGION CONTROL TASK) ATTENTION EXIT PROCESSING HAS RECEIVED AN UNACCEPTABLE RETURN CODE FROM AN INVOKED ROUTINE AND CANNOT CONTINUE PROCESSING. RCT RECOVERY RECORDS THE ERROR IN
SYS1.LOGREC, PERFORMS RESOURCE CLEAN-UP, REQUESTS A SYS1.DUMP OF THE ADDRESS SPACE AND THEN REQUESTS ADDRESS TERMINATION.
S07C - SUPERVISOR CONTROL RECOVERY HAS DETECTED AN ERROR WHICH REQUIRES THAT THE CURRENT TASK BE TERMINATED OR THAT THE CURRENT ADDRESS SPACE BE TERMINATED.
S07F - DURING RECOVERY, VERIFICATION OF THE TCB QUEUE ASSOCIATED WITH THE TERMINATED ADDRESS SPACE RESULTED IN AN EMPTY TCB QUEUE.
S0A7 - DURING Z NET,CANCEL COMMAND PROCESSING, VTAM FOUND THAT A USER HAD NOT SPECIFIED A TPEND EXIT ROUTINE, OR VTAM COULD NOT SCHEDULE A USER'S TPEXIT ROUTINE.
S0A8 - VTAM DETECTED AN ERROR DURING EXECUTION OF AN APPLICATION PROGRAM. THE TWO LOW-ORDER BYTES OF REGISTER 15 CONTAIN A HEXADECIMAL REASON CODE.
- 2101 - A VTAM VALIDITY CHECK OF THE USER'S RPL FAILED BECAUSE THE RPL DOES NOT HAVE THE SAM PROTECTION KEY AS THE APPLICATION PROGRAM'S TCB.
- 7001 - THE USER'S RPL OR ECB IS INVALID.
S0A9 - EITHER A HALT NET,CANCEL COMMAND WAS ENTERED OR AN ERROR OCCURRED DURING EXECUTION OF A VTAM MODULE. THE TWO LOW-ORDER BYTES OF REGISTER-15 CONTAIN A HEXIDECIMAL REASON CODE.
- 0000 - A HALT NET,CANCEL COMMAND HAS BEEN PROCESSED.
- 10F1 - THE ACF/VTAM STAE RETRY ROUTINE ISSUED AN ABEND 0A9 IN ORDER TO GIVE CONTROL TO THE USER RECOVERY ROUTINE (STAE EXIT ROUTINE).
- 3100 - THERE ARE NOT ENOUGH I/O BUFFERS TO SATISFY A VTAM STORAGE REQUEST.
- 3111 - A VTAM MODULE FINISHED PROCESSING BEFORE IT RELEASED A LOCK.
- 3141 - A VTAM DESTINATION VECTOR TABLE (DVT) ENTRY IS INVALID FOR THE DEFINED ATTACHMENT.
- 7002 - A VTAM REQUEST FOR STORAGE FAILED
- 7003 - A VTAM REQUEST TO RELEASE STORAGE FAILED BECAUSE THE STORAGE HAD ALREADY BEEN RELEASED.
- 7004 - VTAM COULD NOT OBTAIN A LOCAL MEMORY LOCK.
- 7009 - VTAM WAS UNABLE TO RESTORE ITS REGISTERS AFTER A USER EXIT ROUTINE RETURNED CONTROL TO VTAM.
- 7071 - A RELSTORE WAS ISSUED FOR A PREVIOSLY FREED BUFFER.
- 7141 - CONTROL CANNOT BE PASSED TO THE PROPER VTAM MODULE. EITHER A VTAM DESTINATION VECTOR TABLE ENTRY IS INVALID FOR THE DEFINED ATTACHMENT OR VTAM STOARGE HAS BEEN ALTERED.
S0AA - AN ABEND CONDITION OCCURRED DURING EXECUTION OF VTAM. THE ERROR COULD NOT BE ASSOCIATED WITH ANY PARTICULAR TCB. ALL TASKS IN THE ADDRESS SPACE ARE ABNORMALLY TERMINATED.
S0AE - IOS SUPPORT OF SYSTEM RESTART PROCESSING FOUND THAT THE I/O PURGE MODULE (IGC0001F) WAITING FOR THE COMPLETION OF AN I/O REQUEST. THE SYSTEM ABNORMALLY TERMINATES ALL TASKS IN THE ADDRESS SPACE, THEN THE SYSTEM TERMINATES THE ADDRESS SPACE.
S0B0 - AN UNCORRECTABLE ERROR WAS DETECTED BY THE SWA MANAGER. IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S0B0-RC)
S0B0 - 04 - INVALID FUNCTION REQUESTED.
S0B0 - 08 - INVALID SVA (DOES NOT POINT TO THE BEGINNING OF A SWA PREFIX OR THE SWA PREFIX HAS BEEN DESTROYED).
S0B0 - 0C - ATTEMPTING TO READ A BLOCK NOT YET WRITTEN.
S0B0 - 10 - INVALID LENGTH (0 OR NEGATIVE FOR ASSIGN LOCATE OR ATTEMPTING TO READ OR WRITE A RECORD, WHICH IS NOT 176 BYTES, IN MOVE MODE).
S0B0 - 14 - INVALID COUNT FIELD (0 FOR READ, WRITE, ASSIGN OR 00 FOR WRITE AND ASSIGN).
S0B0 - 18 - QMNGRIO MACRO WAS ISSUED WITH BOTH OR NEITHER OF THE READ AND WRITE BITS SET.
S0B0 - 1C - INVALID ID (THE CALLER ATTEMPTED TO WRITE A BLOCK FOR THE FIRST TIME AND HAS EITHER PASSED A NON-EXISTING ID OR HAS FAILED TO PASS ONE AND THE BLOCK DOES NOT HAVE AN IMBEDDED ID).
S0B0 - 20 - INVALID BLOCK POINTER (WRITE LOCATE IS ATTEMPTING TO WRITE AND IS PASSING A BLOCK POINTER WHICH IS NOT VALID FOR THE SVA REQUESTED).
S0C1 - OPERATION EXCEPTION - AN OPERATION CODE IS NOT ON THE MACHINE
POSSIBLE CAUSE
- SUBSCRIPT ERROR
- CLOBBERED CODE TRIED TO READ A FILE THAT WAS NOT OPEN
- MISSPELLED DDNAME
- ERROR IN PARAMETERS PASSED TO SUBROUTINES
- MISSING DD CARD
- RECORDING MODE WAS WRONG, OR DENSITY WAS INCORRECT
- BAD LOAD MODULE, POSSIBLE BAD OBJECT DECK OR MISSING SUBROUTINE
- FORTRAN - MISSING DIMENSION STATEMENT, SAME NAME FOR ARRAY AND A SUBROUTINE
- COBOL - SUBROUTINE PROG ID WAS THE SAME AS THE ENTRY NAME
- COBOL - TRIED TO CALL WITHIN COBOL F SORT INPUT/OUTPUT PROCEDURE
- COBOL - TRIED TO CALL A SUBROUTINE WHICH COULD NOT BE FOUND
- COBOL - INCOMPLETE DCB FOR SORTIN
- COBOL - USING SORT VERB, DDNAME WAS NOT SORTOUT WHEN THE GIVING OPTION WAS USED.
- COBOL - EXECUTING SORT-USING AFTER OPENING SORTIN
S0C2 - PRIVILEGED OPERATION EXCEPTION
POSSIBLE CAUSE
- UNINTENTIONAL BRANCH TO INVALID INSTRUCTION DUE TO SUBSCRIPT ERROR
- COBOL - MISSING PERIOD AT END OF PARAGRAPH OR PARAGRAPH NAMES
- MISSING GOBACK AFTER SORT VERB - LOGIC FELL INTO INPUT PROCEDURE
- ACCEPT VERB EXECUTED WHEN NO SYSIN DD WAS AVAILABLE.
S0C3 - EXECUTION EXCEPTION - THE SUBJECT INSTRUCTION OF EXECUTE IS ANOTHER EXECUTE.
POSSIBLE CAUSE
- UNINTENTIONAL BRANCH, LOSS OF ADDRESSABILITY.
S0C4 - PROTECTION EXCEPTION - A VIRTUAL ADDRESS COULD NOT BE TRANSLATED INTO A REAL ADDRESS.
POSSIBLE CAUSE
- INVALID ADDRESS WAS REFERENCED DUE TO SUBSCRIPT ERROR OR BAD PARMS
- THE KEY OF AN INSTRUCTION OR AN OPERAND IN STORAGE DOES NOT
- MATCH THE PROTECTION KEY IN THE PSW (INTERRUPT CODE 4)
- THE VIRTUAL SEGMENT OR PAGE WAS NEVER ALLOCATED (INTERRUPT CODE 10 OR 11, RESPECTIVELY)
- THE PAGE WAS PAGED OUT AND THE ROUTINE REQUESTING THE CODE WAS DISABLED FOR I/O INTERRUPTS (INTERRUPT CODE 11)
- COBOL - IN GROUP MOVE, RECEIVING RECORD VARIABLE LENGTH DEFINED WRONG
- TRIED MOVING VAR. LENGTH REC. LARGER THAN TARGET FIELD MAX
- TRIED TO READ OR WRITE A FILE WHICH WAS NOT OPEN
- USED DD DUMMY AND LOGIC SAYS AT END MOVE HIGH VALUES TO FD
- TRIED TO CALL WITHIN COBOL F SORT INPUT/OUTPUT PROCEDURE
- U WITH SORT - TRIED TO GOBACK IN THE OUTPUT PROCEDURE
S0C5 - ADDRESSING EXCEPTION - AN ADDRESS BEYOND THE AVAILABLE REAL STORAGE WAS REQUETED
POSSIBLE CAUSE
- SEE S0C1 FOR MORE INFORMATION
- SUBSCRIPT ERROR - REFERENCED BEYOND TABLE IN PROGRAM RUNNING V=R
- COBOL - PERFORMED PROCEDURE NOT EXITED PROPERLY
- RECORD DESCRIBED TOO SHORT
- REFERENCED A RECORD WITHOUT GIVING A READ
- TRIED TO USE WRITE WITHOUT FROM OPTION ON APPLY WRITE ONLY FILE
S0C6 - SPECIFICATION EXCEPTION - AN INCORRECT BOUNDARY WAS SPECIFIED. USUALLY CAUSED BY UNINTENTIONAL BRANCH TO INVALID INSTRUCTION.
S0C7 - DATA EXCEPTION - DECIMAL DATA IS INCORRECT OR IMPROPERLY OVERLAPPED OR NOT VALIDLY INITIALIZED.
POSSIBLE CAUSE
- SUBSCRIPT ERROR, REFERENCED BEYOND TABLE
- COBOL - WORKING STORAGE NOT INITIALIZED
- BAD DATA, SHOULD CHECK DATA FOR ERRORS
- GARBAGE IN A FIELD BEING TESTED OR DISPLAYED
- MOVE ZEROES TO GROUP LEVEL IS DISPLAY, HAD SUBLEVELS THAT WERE NOT
- PERIOD MISSING AFTER IMPERATIVE STATEMENTS WITHIN AT END CLAUSE
- BINARY FIELD IN AN ARITHMETIC OPERATION IS NOT LARGE ENOUGH TO ACCEPT RESULT (FOR MORE INFORMATION, SEE DESCRIPTION OF S0C1)
S0C8 - FIXED POINT OVERFLOW EXCEPTION NOTE - MASKED BY FORTRAN
S0C9 - FIXED POINT DIVIDE EXCEPTION NOTE - MASKED BY FORTRAN
S0CA - DECIMAL OVERFLOW EXCEPTION THE DESTINATION FIELD IS TOO SMALL TO CONTAIN THE RESULT FIELD
IN A DECIMAL OPERATION.
S0CB - DECIMAL DIVIDE EXCEPTION A QUOTIENT EXCEEDS THE SPECIFIED DATA FIELD SIZE.
S0CC - EXPONENT OVERFLOW EXCEPTION A FLOATING POINT NUMBER EXCEEDS THE MAXIMUM SIZE.
NOTE - THIS ERROR IS DETECTED AND FIXED IN FORTRAN
S0CD - EXPONENT UNDERFLOW EXCEPTION A FLOATING POINT NUMBER IS SMALLER THAN THE MINIMUM.
NOTE - FORTRAN WILL SET THE RESULT TO ZERO AND CONTINUE PROCESSING
S0CE - SIGNIFICANCE EXCEPTION A FLOATING POINT ADDITION OR SUBTRACTION RESULTS IN AN ALL ZERO FRACTION
NOTE - THIS IS MASKED IN FORTRAN
S0CF - FLOATING POINT DIVIDE EXCEPTION - DIVIDE BY ZERO
NOTE - THIS ERROR IS DETECTED AND NOTED BY FORTRAN
S0D2 - A PROGRAM CHECK WAS DETECTED; AN INTERRUPTION CODE OF 18 X'12' (TRANSLATION SPECIFICATION EXCEPTION) HAS OCCURRED. THERE IS INVALID DATA IN EITHER CONTROL REGISTERS ZERO OR ONE, OR A SEGMENT OR PAGE TABLE. THE ERROR IS THE RESULT OF A HARDWARE ERROR OR A PROGRAM RUNNING IN KEY ZERO HAS CAUSED DATA DAMAGE.
S0D3 - A PROGRAM CHECK, INTERRUPTION CODE 19 X'13' (SPECIAL OPERATION ERROR) HAS OCCURRED. A PRIVILEGED PROGRAM ISSUED A SET SYSTEM MASK. THIS INSTRUCTION IS NOT VALID IN OS/VS2 (SINCE RELEASE 2).
S0D9 - A PROGRAM CHECK, INTERRUPTION CODE 38 (PAGE FAULT ASSIST ERROR) HAS OCCURRED. EITHER A HARDWARE ERROR OCCURRED OR A PROGRAM RUNNING IN KEY ZERO CAUSED DATA DAMAGE.
S0E0 - AN INVALID OR UNRECOGNIZED PROGRAM INTERRRUPT OCCURRED.
POSSIBLE CAUSE
- THIS LEVEL OF MVS IS NOT THE CORRECT ONE FOR THE HARDWARE, ESPECIALLY IF THE INTERRUPT CODE IS UNKNOWN.
S0E0 - 1D - A SQUARE ROOT EXECEPTION OCCURED.
S0E0 - 1E - AN UNNORMALIZED OPERAND EXECEPTION OCCURED.
S0E0 - 28 - RESERVED BIT POSITIONS IN AN ALET WERE NON-ZERO.
S0E0 - 29 - AN ALET SPECIFIED AN INVALID ACCESS LIST ENTRY.
S0E0 - 2A - AN ALET SPECIFIED A PREVIOUSLY DELETED ACCESS LIST ENTRY.
S0E0 - 2B - AN ACCESS LIST ENTRY SPECIFIED AN INVALID DATA SPACE.
S0E0 - 2C - THE SEQUENCE NUMBER IN THE ASTE THAT THE ACCESS LIST ENTRY REFERS TO IS NOT EQUAL TO THE NUMBER IN THE ACCESS LIST ENTRY.
S0E0 - 2D - A PRIVATE ACCESS LIST ENTRY IS SPECIFIED, AND THE CURRENT EAX IS NOT AUTHORIZED TO THE TARGET ADDRESS SPACE.
S0E0 - 30 - A STACKING INTRUCTION WAS ISSUED WHEN THE LINKAGE STACK WAS FULL.
S0E0 - 31 - AN UNSTACKING INTRUCTION WAS ISSUED WHEN THE LINKAGE STACK HAS NO STACK ENTRIES.
S0E0 - 32 - A LINKAGE STACK SPECIFICATION INTERRUPT OCCURED.
S0E0 - 33 - AN INVALID LINKAGE STACK ENTRY (LSE) TYPE WAS ENCOUNTERED BY THE HARDWARE OR BY AN UNSTACKING OPERATION.
S0E0 - 34 - A PR INSTRUCTION WAS ISSUED AGAINST A LINKAGE STACK ENTRY THAT HAS THE UNSTACK SUPPRESSION BIT SET. MVS SETS THIS BIT IN A LINKAGE STACK ENTRY TO PREVENT SVC ROUTINES FROM UNSTACKING
ENTRIES THEY DID NOT ADD TO THE STACK.
S0E1 - THE ERROR OCCURRED WHILE PROCESSING THE FIRST EXCP OF A VIO DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.
S0E2 - THE ERROR OCCURRED WHILE PROCESSING THE FIRST EXCP OF A VIO DATASET. THE SYSTEM WAS UNABLE TO ASSIGN, LOCATE, FIX, FREE, OR ACCESS VIO PAGES FOR THE DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.
S0E3 - THE ERROR OCCURRED WHILE PROCESSING A VIO DATASET. THE SYSTEM WAS UNABLE TO ASSIGN, LOCATE, FIX, FREE, OR ACCESS VIO PAGES FOR THE DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.
S0E4 - THE ERROR OCCURRED WHILE TRYING TO SCRATCH A VIO DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.
S0E5 - UNABLE TO DISCONNECT THE VIRTUAL TRACK BUFFER FORM THE VIO DATASET. PLEASE REPORT THIS PROBLEM TO THE SYSTEMS GROUP.
S0E6 - UNABLE TO PROCESS A DATA SET THAT HAS ALREADY BEEN SCRATCHED.
S0F0 - AN ERROR OCCURRED WHILE PROCESSING A MACHINE CHECK INTERRUPTION. IN AN ATTEMPT TO RECOVER THE SYSTEM THE INTERRUPTED TASK WAS TERMINATED.
S0F1 - PROGRAM INTERRUPTION IN I/O INTERRUPTION HANDLER RECORD DESCRIBED AS WRONG LENGTH
S0F2 - I/O INTERRUPT PROCESSING ERROR. I/O RECOVERY ROUTINE FAILED. CLOBBERED IOB OR OTHER SVC PARAMETERS - SEE S0C1
S0F3 - MACHINE CHECK INTERRUPTION DISK I/O FAILURE OR MACHINE TROUBLE
S0F8 - THE ISSUER OF AN SVC WAS EITHER IN SRB MODE, HELD A LOCK, WAS DISABLED, OR WAS IN CROSS MEMORY MODE.
S0F8 - 04 - THE SVC ISSUER WAS NOT IN TCB MODE.
S0F8 - 08 - THE SVC ISSUER HELD A LOCK.
S0F8 - 0C - THE SVC ISSUER WAS DISABLED.
S0F8 - 10 - THE SVC ISSUER WAS IN CROSS MEMORY MODE.
S0F8 - 14 - THE SVC ISSUER HAD AN ENABLED UNLOCKED TASK MODE FRR. IE. EUT=YES WAS SPECIFIED ON THE SETFRR MACRO.
S0F8 - 18 - THE SVC ISSUER WAS IN AR ADDRESS SPACE CONTROL MODE FOR AN SVC WHICH DOES NOT ALLOW THIS.
S0F8 - 1C - THE SVC ISSUER WAS NOT AUTHORIZED FOR SVC MICROCODE ASSIST.
S0F9 - THE ERROR OCCURRED WHILE TRYING TO ACQUIRE OR RELEASE AN SVRB.
S0F9 - 00- LSQA HAS BEEN EXHAUSTED AND AN SVRB CANNOT BE CREATED TO HONOUR AN SVC REQUEST IN THE ADDRESS SPACE.
S0F9 - 04 - AN SVRB BEING FREED MAY NOT BELONG TO THE SVRB POOL.
S0FB - A TRANSLATION EXCEPTION HAS OCCURRED. INVALID CONTENTS WERE DETECTED IN CONTROL REGISTER 0.
S0FC - A TRANSLATION ERROR OCCURRED WHILE REFERENCING DATA NOT IN THE HOME ADDRESS SPACE. BAD DAT TABLES OR WRONG STO ADDRESS.
S0FD - A TYPE 6 SVC REQUESTED THE SVC FIRST LEVEL INTERRUPT HANDLER (FLIH) TO SCHEDULE A CROSS MEMORY SRB. T6EXIT MACRO POINTS TO SRB WHERE SRBASCB IS NOT HOME ASCB.
S0FE - AN ERROR WAS DETECTED WHILE RMF WAS SAMPLING DATA ABOUT THE STATE OF THE SYSTEM.
S100 - I/O INTERBLOCK GAP DETECTED WHEN WRITING RECORD
S101 - DURING EXECUTION OF A WAIT MACRO, THE PROBLEM PROGRAM SPECIFIED MORE EVENTS THAN THERE WERE ECBS.
S102 - THE ERROR OCCURRED DURING EXECUTION OF A POST MACRO INSTRUCTION. THE CONTROL PROGRAM FOUND AN INVALID EVENT CONTROL BLOCK ADDRESS, OR THE ECB WAS IN A STORAGE AREA WITH A PROTECTION KEY DIFFERENT FROM THAT OF THE TASK ISSUING THE MACRO.
S102 - 00 - INVALID ECB FOR POST IN THE USER'S KEY.
S102 - 04 - INVALID ECB FOR AN XMPOST (CROSS MEMORY POST).
S102 - 08 - INVALID ECB FOR BRANCH ENTRY POST IN THE USER'S KEY.
S102 - 0C - INVALID ECB FOR BRANCH ENTRY XMPOST.
S104 - GETMAIN ERROR. AN AUTHORIZED PROGRAM REQUESTED VIRTUAL STORAGE THAT REQUIRES MORE REAL STORAGE THAN IS AVAILABLE.
S104 - 04 - NOT ENOUGH REAL STORAGE FOR SPACE IN SQA SUBPOOL.
S104 - 08 - NOT ENOUGH REAL STORAGE FOR SPACE IN FIXED CSA SUBPOOL.
S104 - 0C - NOT ENOUGH REAL STORAGE FOR SPACE IN LSQA SUBPOOL.
S104 - 1C - LSQA REQUEST FAILED - PAGE TABLE PAGED OUT.
S104 - 20 - AUTHORIZED PRIVATE REQUEST FAILED - PAGE TABLE PAGED OUT.
S106 - CAN'T FIND IBM SUBTOUTINE. RECOMPILE AND RERUN. AN ERROR WAS DETECTED BY THE CONTROL PROGRAM WHEN IT ATTEMPTED TO FETCH THE REQUESTED PROGRAM INTO VIRTUAL STORAGE.
POSSIBLE CAUSE
- PREVIOUS LKED STEP FAILED TO OUTPUT A SYSLMOD, NEEDS LARGER SIZE= I/O ERROR - MACHINE TROUBLE OR DISK FAILURE
S106-D - INVALID RECORD TYPE IN LOAD MODULE
S106 - 0E - THE CONTROL PROGRAM FOUND AN INVALID ADDRESS IN THE LOAD MODULE. CHECK REGISTER 0:
- 20 - ERROR CONVERTING TTR.
- 24 - BLOCK IS OUTSIDE OF THE MODULE.
- 28 - AN ADCON LOCATION IS INVALID.
S106-F - UNCORRECTABLE I/O ERROR WHEN LOADING MODULE.
S106 - 10 - THE CONTROL PROGRAM DETECTED A RELOCATION ERROR IN THE LOAD MODULE.
**S10A - GETMAIN ERROR. A PROGRAM REQUESTED VIRTUAL STORAGE THAT REQUIRES MORE REAL STORAGE THAN IS AVAILABLE.
S10A - 04 - NOT ENOUGH REAL STORAGE FOR SPACE IN SQA SUBPOOL.
S10A - 08 - NOT ENOUGH REAL STORAGE FOR SPACE IN FIXED CSA SUBPOOL.
S10A - 0C - NOT ENOUGH REAL STORAGE FOR SPACE IN LSQA SUBPOOL.
S10A - 1C - LSQA REQUEST FAILED - PAGE TABLE PAGED OUT.
S10A - 20 - AUTHORIZED PRIVATE REQUEST FAILED - PAGE TABLE PAGED OUT.
S10B - TIME SERVICE ROUTINE ERROR - ERROR IN INPUT PARAMETERS.
S10D - JOBSTEP TASK ABENDED WHEN A SUBTASK THAT IS ALSO A JOBSTEP TASK IS IN STEP-MUST-COMPLETE STATUS.
S10E - SPIE MACRO ERROR. THE PICA ADDRESS IS INVALID.
S112 - INVALID INPUT WAS PASSED TO SVC 18 BY THE BLDL OR FIND MACRO. REQUIRES MORE REAL STORAGE THAN IS AVAILABLE.
POSSIBLE CAUSE
THE DCB HAS BEEN OVERLAID, ESPECIALLY DCBDEBAD OR DCBPOINT.
S112 - 01 - PARAMETER LIST NOT IN CALLER'S STORAGE.
S112 - 02 - DCB NOT IN CALLER'S STORAGE.
S112 - 03 - DCB DOES NOT POINT TO A VALID DEB.
S112 - 04 - PROGRAM CHECK OCCURRED IN THE POINT ROUTINE.
S112 - 13 - DCB DOES NOT POINT TO A VALID DEB. DCB DUMPED TO GTF.
S112 - 14 - PROGRAM CHECK OCCURRED IN THE POINT ROUTINE. THE DCB IS DUMPED TO THE GTF DATA SET.
S113 - AN ERROR OCCURRED DURING AN OPEN WITH A TYPE=J OPERAND.
S113 - 08 - A JFCB EXTENSION BLOCK WAS NEEDED FOR PROCESSING A PHYSICAL SEQUENTIAL DATA SET BUT NONE WAS AVAILABLE.
S113 - 0C - AN OPEN TYPE=J WAS ISSUED, BUT NO JFCB EXIT WAS FOUND IN THE DCB EXIT LIST. SPECIFY A JFCB EXIT, SUPPLY THE JFCB.
S113 - 18 - A JFCB EXTENSION BLOCK WAS NEEDED FOR PROCESSING A DIRECT OR INDEX SEQUENTIAL DATA SET.
S113 - 20 - END-OF-VOLUME ENCOUNTERED FOR A VSAM DATA SET. MULTI-VOLUME VSAM FILES CANNOT BE OPENED WITH A DCB.
S113 - 24 - OPEN ISSUED TO A MULTI-VOLUME VSAM DATA SET. MULTI-VOLUME VSAM FILES CANNOT BE OPENED WITH A DCB.
S113 - 28 - OPEN ATTEMPT FOR CONCATENATED VSAM USING A DCB.
S113 - 2C - OPEN ATTEMPT FOR VSAM USING A DCB WHEN THE CALLER WAS NOT APF AUTHORIZED OR IN SUPERVISOR STATE.
S113 - 30 - INVALID JCL DISPOSITION DETECTED FOR VSAM OPENED WITH A
DCB. ONLY ALLOWED (OLD,KEEP,KEEP) OR (SHR,KEEP,KEEP).
S113 - 34 - AN UNSUPPORTED DCB OPTION WAS SPECIFIED FOR A VSAM DATA
SET OPENED WITH A DCB. ONLY VALID OPTIONS ARE INPUT AND UPDAT.
S113 - 38 - AN OPEN WAS ISSUED FOR A VSAM DATA SET WITH A DCB,
BUT THE VTOC DOES NOT INDICATE THAT IT IS A VSAM DATA SET.
S115 - SVC 21 (STOW) ERROR. THE DCB DID NOT POINT TO A VALID DEB,
OR THE DEB DID NOT POINT BACK TO THE DCB.
S117 - AN I/O ERROR OCCURRED DURING A BSAM CLOSE TYPE=T MACRO.
S118 - INVALID PARAMETERS WERE PASSED TO DEVTYPE (SVC 24).
*IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE*
*S118 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S118-RC)
S118 - 01 - THE DDNAME (ADDRESS IN GPR 1) WAS NOT IN CALLER'S REGION.
S118 - 02 - OUTPUT AREA (ADDRESS IN GPR 0) WAS NOT IN CALLER'S REGION.
S11A - A PROTECTION CHECK OCCURRED WHEN THE SYSTEM TRIED TO STORE
INTO A USER SUPPLIED OS/VS CAMLST WORK AREA.
S121 - A MODULE ISSUED SVC 33 (IOHALT) WITH THE LOW ORDER BIT OF
GPR1 OFF, WHICH INDICATES THE PRE-XA (2-BYTE UCB ADDR) INTERFACE.
S122 - EITHER THE OPERATOR OR THE JOB ENTRY SUBSYSTEM CANCELLED THE
JOB, REQUESTING A DUMP. CHECK THE JOB LOG LISTING FOR MORE INFO.
S128 - AN INVALID ADDRESS LIST WAS SPECIFIED FOR AN EXTRACT MACRO.
LIST NOT ON A FULLWORD BOUNDARY OR NOT IN JOB STEP'S STORAGE.
S12D - INVALID SEGMENT TABLE IN AN OVERLAY PROGRAM
SEE S0C1
S12E - ERROR FOUND IN INPUT PARAMETERS TO TTIMER SERVICE ROUTINE.
S130 - THE DEQ MACRO SPECIFIED A RESOURCE NOT PREVIOUSLY SPECIFIED BY
BY AN ENQ MACRO. THAT IS, THE PROGRAM HAD NOT REQUESTED CONTROL
OF A RESOURCE IT WAS ATTEMPTING TO RELEASE.
S137 - 14 - I/O ERROR READING HEADER LABELS FOR A DATASET
S137 - 18 - I/O ERROR WHILE POSITIONING A TAPE FOR THE FIRST DATA RECORD
S137 - 10 - I/O ERROR WHILE POSITIONING A TAPE FOR THE END OF A DATASET
S137 - 1C - AN INVALID TRAILER RECORD WAS READ DURING THE END-OF-VOLUME
S137 - I/O ERROR READING EOF ON MAGNETIC TAPE
S213 - 04 - I/O ERROR WRITTEN IN THE DCB OF A DATAET
S213 - 08 - DATASET NOT FOUND ON VOLUME
S04E - RESOURCE UNAVAILABLE, CONTENTION, BAD INPUT, COULD BE ANYTHING READ SYSTEM MESSAGE CODE AND REASON CODE
S213 - 04 - I/O ERROR WRITING DCB OF A DATASET
S213 - 18 - DATASET NOT FOUND ON VOLUME
S214 - 04 - I/O ERROR READING A USER LABEL ON A TAPE
S214 - 08 - I/O ERROR
S214 - 0C - EQC - I/O ERROR ON TAPE DRIVE
S222 - JOB CANCELLED
S237 - 04 - HARDWARE ERROR - BLOCK OF DATA MISSED OR SKIPPED
S237 - 08 - DSN ON HEADER LABEL DOESN'T MATCH VOLUME SERIAL
S237 - 567 - HARDWARE ERROR. THE BLOCK COUNT DOES NOT MATCH TRAILER LABEL
S306 - INSUFFICIENT ACCESS AUTHORITY
S30E - BAD DATA(CHECK ONCODE),CONTENTION
S311 - I/O ERROR READING HEADER LABELS FOR A DATASET
S322 - TIMED OUT, POSSIBLY NO TIME PARAMETER OR OTHER INFO MISSING
S413 - 04 - UNIT NOT AVAILABLE FOR MOUNTING VOLUME
S413 - 08 - AN I/O ERROR OCCURRED POSITIONING A MAGNETIC TAPE VOLUME TABE DRIVE PROBLEM(IF 'EQC' OR 'SIM' IN MSG) TAPE PROBLEM(IF 'SEQ' IN MSG)
S413 - 0C -
S413 - 18 - UTPROC=RESTART DID NOT WORK
S413 - 20 - I/O ERROR READING VOLUME LABEL ON A DASD VOLUME
S413 - 34 - NO REFERBACK, NO LABEL
S522 - TIMED OUT - TAPE NOT MOUNTED, HSM RECALL
S546 - CANCELLED BY OPERATOR OR SYSTEM
S567 - HARDWARE ERROR - BLOCK OF DATA MISSED OR SKIPPED
S613 - 08 - TAPE POSITIONING ERROR
S613(SF13) - BAD TAPE OR DRIVE - ERROR READING LABEL ON TAPE IF YOU SEE MESSAGE IN RMDS OUTPUT: DATA SET NAME DOES NOT MATCH FOR A MASTER VOLUME INSTALLATION OPTION ALLOWS UPDATE OF ONLY THE LAST FILE ON MASTER VOLUMES CHECK JCL AT FAILED STEP TO MAKE SURE LABEL IS CORRECT - POSSIBLY NO LABEL
S637 - OC - CONCATENATION ON UNLIKE ATTRIBUTES
S637 - 2C - I/O ERROR READING HEADER LABEL ON TAPE
S637 - 34 - I/O ERROR READING END OF VOLUME LABEL
S706 - A LOAD MODULE MARKED FOR THE LINKAGE EDITOR IS NON-EXECUTABLE
S714 - BAD TAPE OR TAPE DRIVE
S714 - 0C - BAD TAPE DRIVES
S718 - NOT ENOUGH REGION TO LOAD MODULES
S722 - LINES EXCEEDED, ADD A MAIN LINES CARD - //*MAIN LINES=(100,WARNING)
S737 - 24 - DSN NOT FOUND
S777 - DATA CHECK. TRANSMIT ON INPUT
S806 - PROGRAM NOT FOUND IN LIBRARY, CONTENTION, NO DATA TRANSMITTED
S813 - 04 - I/O ERROR READING HEADER LABEL ON TAPE
S822 - REGION REQUESTED/REQUIRED COULD NOT BE OBTAINED
S837 - SPACE PROBLEM WITH OUTPUT DATASET, VOL SER COUNT TOO LOW 'VOL=(,,,10)'
S848 - NOT ENOUGH REGION. INCREASE THE REGION SIZE, 'REGION=4096K'
S878 - NOT ENOUGH REGION. INCREASE THE REGION SIZE, 'REGION=4096K' OR DECREASE REGION=4M(SAME AS REGION=4096K) REGION=0M ALL STORAGE AVAILABE BELOW THE LINE
S878 - 10 - GETMAIN PROBLEM - INSUFFICIENT STORAGE
S913 - INSUFFICIENT ACCESS AUTHORITY(RACF)
S922 - SPECIFIED MU TIME EXCEEDED
S2333 - DB2 TABLE TIMESTAMP MISMATCH
SB37 - 04 - NOT ENOUGH SPACE WAS ALLOCATED
SD37 - OUTPUT DSN USED ALL PRIMARY SPACE
SA13 - 14 - END OF FILE MARK DATASET NOT ON TAPE
S0C4 - ENTRY NOT FOUND
SE37 - ALL SPACE USED ON CURRENT VOLUME. SPECIFY MORE VOLUMES
JCLI - SYNTAX, DATASET NOT FOUND JCL - SYNTAX, DATASET NOT FOUND, SPACE, DUPLICATE NAME, CONTENTION COULD BE ANYTHING
07D5 - I/O ERROR
2001 - CONTENTION
2005 - I/O ERROR
2004 - BAD DATA(07D)
2016 - EMPTY GENERATIONS
0406 -
44004 - SQL
013 - OPEN ERROR
028 - PAGING I/O ERROR
052-084 - INVALID CHARACTER ID
076-002 - UNABLE TO OPEN DATASET
072-053 - UNABLE TO OPEN DDNAME
0CX - PROGRAM CHECK EXCEPTIONS:
0C1 - OPERATION,
OC4 - PROTECTION/ADDRESSING,
0C5 - ADDRESSING,
0C6 - SPECIFICATION,
0C7 - DATA
706 - NON-EXECUTABLE PROGRAM
804 - INSUFFICIENT VIRTUAL STORAGE
806 - UNABLE TO LOAD (LINK ETC) PROGRAM
80A - INSUFFICIENT VIRTUAL STORAGE
852 - BAD DATA
878 - INSUFFICIENT VIRTUAL STORAGE
998 - POSSIBLE CONTENTION, TABLESPACE IN USE
737 - I/O ERROR
A14 - I/O ERROR
B37 - INSUFFICIENT DASD SPACE ON SEQUENTIAL DATASET
D37 - INSUFFICIENT DASD SPACE - NO SECONDARY SPACE ALLOCATED
E37 - INSUFFICIENT DASD SPACE ON PARTITIONED DATASET
SQL Abends
Negative values (Errors)
-102 String constant is too long.
-117 The number of values in the INSERT does not match the number of columns.
-180 Bad data in Date/Time/Timestamp.
-181 Bad data in Date/Time/Timestamp.
-199 Illegal use of the specified keyword.
-204 Object not defined to DB2.
-205 Column name not in table.
-206 Column does not exist in any table of the SELECT.
-216 Not the same number of expressions on both sides of the comparison in a SELECT .
-224 FETCH cannot make an INSENSITIVE cursor SENSITIVE.
-229 The locale specified in a SET LOCALE statement was not found.
-305 Null indicator needed.
-311 Varchar, insert or update. -LEN field with the right data length not set.
-482 The procedure returned no locators.
-501 Cursor not open on FETCH.
-502 Opening cursor that is already open.
-503 Updating column needs to be specified.
-530 Referential integrity preventing the INSERT/UPDATE
-532 Referential integrity (DELETE RESTRICT rule) preventing the DELETE.
-536 Referential integrity (DELETE RESTRICT rule) preventing the DELETE.
-545 Check constraint preventing the INSERT/UPDATE.
-551 Authorization failure
-747 The table is not available.
-803 Duplicate key on insert or update.
-805 DBRM or package not found in plan.
-811 More than one row retrieved in SELECT INTO.
-818 Plan and program: timestamp mismatch.
-904 Unavailable resource. Someone else is locking your data.
-911 Deadlock or timeout. Rollback has been done.
-913 Deadlock or timeout. No rollback.
-922 Authorization needed.
-927 The language interface was called but no connection had been made.
-936
-1741
-20000
Positive Values (Warnings)
+100 Row not found or end of cursor.
+222 Trying to fetch a row within a DELETE statement.
+223 Trying to fetch a row within an UPDATE statement.
+231 FETCH after a BEFORE or AFTER but not on a valid row.
+304 Value cannot be assigned to this host variable because it is out of range.
+802 The null indicator was set to -2 as an arithmetic statement didn't work.[
SQLCODE= -104 - ILLEGAL SYMBOL, ILLEGAL TOKEN IN SQL STATEMENT
SQLCODE= -110 - EMPTY TABLE, BAD QUERY
SQLCODE= -180 - THE STRING REPRESENTATION OF A DATETIME VALUE BAD DATA HAS INVALID SYNTAX
SQLCODE= -181 - THE STRING REPRESENTATION OF A DATETIME VALUE IS BAD DATA NOT A VALID DATETIME VALUE
SQLCODE= -204 - UNDEFINED TABLE NAME - TABLE NAME DOESN'T EXIST UNDEFINED ALIAS - ALIAS DOES NOT EXIST
SQLCODE= -305 - THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT BECAUSE NO INDICATOR VARIABLE IS SPECIFIED
SQLCODE= -501 - CURSOR IS CLOSED DUE TO PREVIOUS CONDITIONS
SQLCODE= -551 - DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION DROP ALIAS ON OBJECT
SQLCODE= -556 - CANNOT HAVE THE EXECUTE PRIVILEGE, REVOKED BY DB2DBA BECAUSE THE REVOKEE DOES NOT POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT
SQLCODE= -562 - A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY HAS THE PRIVILEGE FROM THE GRANTOR
SQLCODE= -626 - THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE PAGE SET IS NOT STOPPED - CALL DBA
SQLCODE= -803 - DATA PROBLEM - MAY BE BAD PART NUMBER COULD BE DUPLICATE VALUES IN EXISTING ROW
SQLCODE= -805 - BIND PROBLEM
SQLCODE= -811 - ERROR ON SQL TABLE
SQLCODE= -818 - LOAD MODULE AND DBR MODULE OUT OF SYNCH NEED TO DO BIND REPLACE OR REBIND
SQLCODE= -904 - CONTENTION
SQLCODE= -911 - CONTENTION
SQLCODE= -922 - TIME STAMP PROBLEM AFTER REBIND
SQLCODE= -923 - DB2 ERROR - SOME DB2 COMPONENT NOT AVAILABLE
SQLCODE= -924 - SUBSYSTEM NOT AVAIALABLE, CONTENTION IN DATABASE
ONCODE=9 - DATA PROBLEM
ONCODE=22 - LENGTH OF RECORD VARIABLE GREATER THAN RECORD LENGTH
ONCODE=0084 - UNDEFINED FILE CONDITION RAISE
ONCODE=1040 - SPACE PROBLEM
ONCODE=3920 - STORAGE PROBLEM
ONCODE=8094 - PROTECTION EXCEPTION - CAUSED BY BAD COMPILE - CALL ADM, B37(SPACE PROBLEM)
ONCODE=8097 - BAD DATA, DATA EXCEPTION
ONCODE=9050 - BAD DATA
MENSAGENS DE ERRO ENCONTRADAS EM JOB OUTPUT'S E QUE DEVEM SER LEVADAS EM CONTA:
'INVALID', 'ERROR', 'RESOURCE NOT AVAILABLE', 'PROGRAM NOT FOUND', 'INVALID RECORD LENGTH', 'FAILED', 'UTILITY NOT COMPATIBLE', 'DOES NOT MATCH', 'DUPLICATE', 'DATASET ALREADY USED'
DUPLICATE DATASET NAME - EITHER THE PROGRAM CONTAINS TWO DATASETS WITH THE SAME NAME, OR A DELETE UNCATALOG STEP IS NOT WORKING
'DUPLICATE UTILITY' AND 'EMPTY DATASET'
EQC - EQUIPMENT CHECK
FBI - FAILED BY INITIATOR - CHECK THE JCL FOR THE CAUSE OF THE ABEND
PROTECTION EXCEPTION - CAUSED BY A BAD COMPILE. CONTACT A PROGRAMMER
OPEN - MESSAGE STATES THAT DATASETS ARE OPEN
SEQ - TAPE DRIVE PROBLEM
UNABLE TO ALLOCATE SORTWORK SPACE - NO SORTWORK SPACE AVAILABLE. WAIT
A LITTLE WHILE UNTIL SOME JOBS FINISH PROCESSING AND THEN RESUBMIT THE
JOBS.
WRONG PASSWORD OR ACCESS NOT ALLOWED - MEANS THAT THE JOB HAS NOT A SECURITY (ACF,RACF) RULE TO EXECUTE ON THAT SCHEDULLING TOOL OR FOR ONE DATASET, ETC.
REASON CODE 00E30083 - DEADLOCK - CONTENTION
REASON CODE 00D70024 - RESOURCE UNAVAILABLE
REASON CODE 00E40034 - STORAGE UNAVAILABLE
REASON CODE 1008 - FTP LINE DOWN
REASON CODE OOE40034 - STORAGE PROBLEM - NOT ENOUGH STORAGE
SIM - PROBLEM WITH DRIVE OR TAPE, I/O ERROR
JCL - ENVIRONMENT CHANGED. NOW UNABLE TO ALLOCATE
-102 String constant is too long.
-117 The number of values in the INSERT does not match the number of columns.
-180 Bad data in Date/Time/Timestamp.
-181 Bad data in Date/Time/Timestamp.
-199 Illegal use of the specified keyword.
-204 Object not defined to DB2.
-205 Column name not in table.
-206 Column does not exist in any table of the SELECT.
-216 Not the same number of expressions on both sides of the comparison in a SELECT .
-224 FETCH cannot make an INSENSITIVE cursor SENSITIVE.
-229 The locale specified in a SET LOCALE statement was not found.
-305 Null indicator needed.
-311 Varchar, insert or update. -LEN field with the right data length not set.
-482 The procedure returned no locators.
-501 Cursor not open on FETCH.
-502 Opening cursor that is already open.
-503 Updating column needs to be specified.
-530 Referential integrity preventing the INSERT/UPDATE
-532 Referential integrity (DELETE RESTRICT rule) preventing the DELETE.
-536 Referential integrity (DELETE RESTRICT rule) preventing the DELETE.
-545 Check constraint preventing the INSERT/UPDATE.
-551 Authorization failure
-747 The table is not available.
-803 Duplicate key on insert or update.
-805 DBRM or package not found in plan.
-811 More than one row retrieved in SELECT INTO.
-818 Plan and program: timestamp mismatch.
-904 Unavailable resource. Someone else is locking your data.
-911 Deadlock or timeout. Rollback has been done.
-913 Deadlock or timeout. No rollback.
-922 Authorization needed.
-927 The language interface was called but no connection had been made.
-936
-1741
-20000
Positive Values (Warnings)
+100 Row not found or end of cursor.
+222 Trying to fetch a row within a DELETE statement.
+223 Trying to fetch a row within an UPDATE statement.
+231 FETCH after a BEFORE or AFTER but not on a valid row.
+304 Value cannot be assigned to this host variable because it is out of range.
+802 The null indicator was set to -2 as an arithmetic statement didn't work.[
SQLCODE= -104 - ILLEGAL SYMBOL, ILLEGAL TOKEN IN SQL STATEMENT
SQLCODE= -110 - EMPTY TABLE, BAD QUERY
SQLCODE= -180 - THE STRING REPRESENTATION OF A DATETIME VALUE BAD DATA HAS INVALID SYNTAX
SQLCODE= -181 - THE STRING REPRESENTATION OF A DATETIME VALUE IS BAD DATA NOT A VALID DATETIME VALUE
SQLCODE= -204 - UNDEFINED TABLE NAME - TABLE NAME DOESN'T EXIST UNDEFINED ALIAS - ALIAS DOES NOT EXIST
SQLCODE= -305 - THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT BECAUSE NO INDICATOR VARIABLE IS SPECIFIED
SQLCODE= -501 - CURSOR IS CLOSED DUE TO PREVIOUS CONDITIONS
SQLCODE= -551 - DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION DROP ALIAS ON OBJECT
SQLCODE= -556 - CANNOT HAVE THE EXECUTE PRIVILEGE, REVOKED BY DB2DBA BECAUSE THE REVOKEE DOES NOT POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT
SQLCODE= -562 - A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY HAS THE PRIVILEGE FROM THE GRANTOR
SQLCODE= -626 - THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE PAGE SET IS NOT STOPPED - CALL DBA
SQLCODE= -803 - DATA PROBLEM - MAY BE BAD PART NUMBER COULD BE DUPLICATE VALUES IN EXISTING ROW
SQLCODE= -805 - BIND PROBLEM
SQLCODE= -811 - ERROR ON SQL TABLE
SQLCODE= -818 - LOAD MODULE AND DBR MODULE OUT OF SYNCH NEED TO DO BIND REPLACE OR REBIND
SQLCODE= -904 - CONTENTION
SQLCODE= -911 - CONTENTION
SQLCODE= -922 - TIME STAMP PROBLEM AFTER REBIND
SQLCODE= -923 - DB2 ERROR - SOME DB2 COMPONENT NOT AVAILABLE
SQLCODE= -924 - SUBSYSTEM NOT AVAIALABLE, CONTENTION IN DATABASE
ONCODE=9 - DATA PROBLEM
ONCODE=22 - LENGTH OF RECORD VARIABLE GREATER THAN RECORD LENGTH
ONCODE=0084 - UNDEFINED FILE CONDITION RAISE
ONCODE=1040 - SPACE PROBLEM
ONCODE=3920 - STORAGE PROBLEM
ONCODE=8094 - PROTECTION EXCEPTION - CAUSED BY BAD COMPILE - CALL ADM, B37(SPACE PROBLEM)
ONCODE=8097 - BAD DATA, DATA EXCEPTION
ONCODE=9050 - BAD DATA
MENSAGENS DE ERRO ENCONTRADAS EM JOB OUTPUT'S E QUE DEVEM SER LEVADAS EM CONTA:
'INVALID', 'ERROR', 'RESOURCE NOT AVAILABLE', 'PROGRAM NOT FOUND', 'INVALID RECORD LENGTH', 'FAILED', 'UTILITY NOT COMPATIBLE', 'DOES NOT MATCH', 'DUPLICATE', 'DATASET ALREADY USED'
DUPLICATE DATASET NAME - EITHER THE PROGRAM CONTAINS TWO DATASETS WITH THE SAME NAME, OR A DELETE UNCATALOG STEP IS NOT WORKING
'DUPLICATE UTILITY' AND 'EMPTY DATASET'
EQC - EQUIPMENT CHECK
FBI - FAILED BY INITIATOR - CHECK THE JCL FOR THE CAUSE OF THE ABEND
PROTECTION EXCEPTION - CAUSED BY A BAD COMPILE. CONTACT A PROGRAMMER
OPEN - MESSAGE STATES THAT DATASETS ARE OPEN
SEQ - TAPE DRIVE PROBLEM
UNABLE TO ALLOCATE SORTWORK SPACE - NO SORTWORK SPACE AVAILABLE. WAIT
A LITTLE WHILE UNTIL SOME JOBS FINISH PROCESSING AND THEN RESUBMIT THE
JOBS.
WRONG PASSWORD OR ACCESS NOT ALLOWED - MEANS THAT THE JOB HAS NOT A SECURITY (ACF,RACF) RULE TO EXECUTE ON THAT SCHEDULLING TOOL OR FOR ONE DATASET, ETC.
REASON CODE 00E30083 - DEADLOCK - CONTENTION
REASON CODE 00D70024 - RESOURCE UNAVAILABLE
REASON CODE 00E40034 - STORAGE UNAVAILABLE
REASON CODE 1008 - FTP LINE DOWN
REASON CODE OOE40034 - STORAGE PROBLEM - NOT ENOUGH STORAGE
SIM - PROBLEM WITH DRIVE OR TAPE, I/O ERROR
JCL - ENVIRONMENT CHANGED. NOW UNABLE TO ALLOCATE
SQLCODES for DB2 Version 7 - II
SQLCODES for DB2 Version 7
Scroll down to see ALL the SQLCODES there are in Version 7.The most common ones
are at the top.
.+100| SQLSTATE 02000 Row not found or end of cursor
. 100, NOT FOUND: ROW NOT FOUND FOR FETCH, UPDATE, OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE
.-102, String constant is too long
.-102, ERROR: LITERAL STRING IS TOO LONG. STRING BEGINS
.-117, The number of values you are trying to INSERT does not match the number of columns
.117, WARNING: THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER OF OBJECT COLUMNS
.-117, ERROR: THE NUMBER OF ASSIGNED VALUES IS NOT THE SAME AS THE NUMBER OF SPECIFIED OR IMPLIED COLUMNS
.-180 SQLSTATE 22007, Bad data in Date/Time/Timestamp
String representation of DATE, TIME, TIMESTAMP is invalid
.-180, ERROR: THE DATE, TIME, OR TIMESTAMP VALUE IS INVALID
.-181 SQLSTATE 22007, Bad data in Date/Time/Timestamp
Value for DATE, TIME, TIMESTAMP is invalid
.-181, ERROR: THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE
.-199, Illegal use of the specified keyword.
.-204, Object not defined to DB2
. 204, WARNING: IS AN UNDEFINED NAME
.-204, ERROR: IS AN UNDEFINED NAME
.-205, Column name not in specified table
.-205, ERROR: IS NOT A COLUMN OF TABLE
.-206, Column does not exist in any table in the SELECT
.-206, ERROR: IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR
ANY TABLE IDENTIFIED IN A FROM CLAUSE, OR IS NOT A COLUMN OF THE
TRIGGERING TABLE OF A TRIGGER
. 206, WARNING: IS NOT A COLUMN OF AN INSERTED TABLE,
UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE
.-216, You need to use the same number of expressions on both sides of the
comparison.
when using multiple operands in a comparison,
Correct example:
WHERE (E.SALARY, E.COMM) IN (SELECT S.PAY, S.COMMISSION
Incorrect example:
WHERE (E.SALARY, E.COMM, E.BONUS)
IN (SELECT S.PAY, S.COMMISSION
. 222, Trying to fetch a row that fell through a DELETE hole
.+223, Trying to fetch a row that fell through an UPDATE hole
.-224, FETCH cannot make an INSENSITIVE cursor SENSITIVE
.-229, The locale specified in a SET LOCALE statement was not found.
.-229, ERROR: THE LOCALE SPECIFIED IN A SET LOCALE OR OTHER STATEMENT THAT IS LOCALE SENSITIVE WAS NOT FOUND
.+231, FETCH but you did a BEFORE or AFTER and you are not on a valid row
.+304, Value cannot be assigned to this host variable because it is out of range
.-304, ERROR: A VALUE WITH DATA TYPE CANNOT BE ASSIGNED TO A HOST
VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST
VARIABLE IN POSITION WITH DATA TYPE
.304, WARNING: A VALUE WITH DATA TYPE CANNOT BE ASSIGNED TO A HOST
VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST
VARIABLE IN POSITION WITH DATA TYPE
.-305, Null indicator needed
.-305, ERROR: THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE
NUMBER BECAUSE NO INDICATOR VARIABLE IS SPECIFIED
.-311, Varchar, insert or update. You didn’t set the -LEN field with the right data length
.-311, ERROR: THE LENGTH OF INPUT HOST VARIABLE NUMBER IS NEGATIVE OR GREATER THAN THE MAXIMUM
.-482, The procedure returned no locators
.-482, ERROR: THE PROCEDURE RETURNED NO LOCATORS
.-501, Cursor not open on FETCH
.-501, ERROR: THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT OPEN
.-502, Opening cursor that is already open
.-502, ERROR: THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN
.-503, Updating column which needs to be specified in FOR UPDATE OF
.-503, ERROR: A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN
THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR
.-530 SQLSTATE 23503, Referential integrity prevents the INSERT/UPDATE
.-530, ERROR: THE INSERT OR UPDATE VALUE OF FOREIGN KEY IS INVALID
.-532 SQLSTATE 23504Referential integrity (DELETE RESTRICT rule) prevents the DELETE
.-532, ERROR: THE RELATIONSHIP RESTRICTS THE DELETION OF ROW WITH RID X''
.-532 SQLSTATE 42914, Referential integrity (DELETE RESTRICT rule) prevents the DELETE
.-515 SQLSTATE 23513, Check constraint prevents the INSERT/UPDATE
.-747, The table specified is not available because tables and/or indexes need to be created.
.-747, ERROR: TABLE IS NOT AVAILABLE UNTIL THE AUXILIARY TABLES AND
INDEXES FOR ITS EXTERNALLY STORED COLUMNS HAVE BEEN CREATED
.+802, The null indicator was set to -2 because an arithmetic statement didn't work.
.-802, ERROR: EXCEPTION ERROR HAS OCCURRED DURING OPERATION ON DATA, POSITION
. 802, WARNING: EXCEPTION ERROR HAS OCCURRED DURING OPERATION ON DATA, POSITION
.-803, SQLSTATE 23505 Duplicate key on insert or update
.-803, ERROR: AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE INDEX IN
INDEX SPACE CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN
CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X''
.-805, DBRM or package not found in plan Is plan name correct?
.-805, ERROR: DBRM OR PACKAGE NAME NOT FOUND IN PLAN REASON
.-811, More than one row retrieved in SELECT INTO
.-811, ERROR: THE RESULT OF AN EMBEDDED SELECT STATEMENT OR A SUBSELECT
IN THE SET CLAUSE OF AN UPDATE STATEMENT IS A TABLE OF MORE THAN
ONE ROW, OR THE RESULT OF A SUBQUERY OF A BASIC PREDICATE IS MORE
THAN VALUE
.-818, Plan and program: timestamp mismatch
.-818, ERROR: THE PRECOMPILER-GENERATED TIMESTAMP IN THE LOAD MODULE IS
DIFFERENT FROM THE BIND TIMESTAMP BUILT FROM THE DBRM
.-904 SQLSTATE 57011, Unavailable resource. Someone is locking the data
you need you may choose to terminate the program
.-904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE.
REASON , TYPE OF RESOURCE , AND RESOURCE NAME
.-911 SQLSTATE 40000, Deadlock or timeout. Rollback has been done.
.-911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK
OR TIMEOUT. REASON, TYPE OF RESOURCE, AND RESOURCE NAME
.-913 SQLSTATE 40502, Your program was the victim of a deadlock or timeout.
NO rollback has been done. You should do a ROLLBACK.
.-913, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT.
REASON CODE , TYPE OF RESOURCE , AND RESOURCE NAME
.-922, Authorization needed
.-922, ERROR: AUTHORIZATION FAILURE: ERROR. REASON
.-927, The language interface was called but no connection had been made.
Execute the program with the DSN command.
All the sqlcodes from -991 to +883 in DB2 Version 7.
.-927, ERROR: THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING
ENVIRONMENT WAS NOT ESTABLISHED. THE PROGRAM SHOULD BE INVOKED
UNDER THE DSN COMMAND
.-991, ERROR: CALL ATTACH WAS UNABLE TO ESTABLISH AN IMPLICIT CONNECT OR OPEN TO DB2. RC1= RC2=
.-981, ERROR: THE SQL STATEMENT FAILED BECAUSE THE RRSAF CONNECTION IS
NOT IN A STATE THAT ALLOWS SQL OPERATIONS, REASON
.-950, ERROR: THE LOCATION NAME SPECIFIED IN THE CONNECT STATEMENT IS
INVALID OR NOT LISTED IN THE COMMUNICATIONS DATABASE
.-948, ERROR: DISTRIBUTED OPERATION IS INVALID
.-947, ERROR: THE SQL STATEMENT FAILED BECAUSE IT WILL CHANGE A TABLE
DEFINED WITH DATA CAPTURE CHANGES, BUT THE DATA CANNOT BE PROPAGATED
.-939, ERROR: ROLLBACK REQUIRED DUE TO UNREQUESTED ROLLBACK OF A REMOTE SERVER
.-929, ERROR: FAILURE IN A CHANGED DATA CAPTURE EXIT:
.-926, ERROR: ROLLBACK NOT VALID IN IMS OR CICS ENVIRONMENT
.-925, ERROR: COMMIT NOT VALID IN IMS OR CICS ENVIRONMENT
.-924, ERROR: DB2 CONNECTION INTERNAL ERROR, , ,
. 923, ERROR: CONNECTION NOT ESTABLISHED: DB2 , REASON , TYPE , NAME
.-919, ERROR: A ROLLBACK OPERATION IS REQUIRED
.-918, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE A CONNECTION HAS BEEN LOST
.-917, ERROR: BIND PACKAGE FAILED
.-910, ERROR: THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A DROP OR ALTER IS PENDING
.-909, ERROR: THE OBJECT HAS BEEN DELETED OR ALTERED
.-908, ERROR: ERROR USING AUTHORITY. BIND, REBIND, OR AUTO-REBIND OPERATION IS NOT ALLOWED
.-906, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION IS DISABLED DUE TO A PRIOR ERROR
.-905, ERROR: UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED,
RESOURCE NAME = LIMIT = CPU SECONDS ( SERVICE UNITS) DERIVED FROM
.-902, ERROR: POINTER TO ESSENTIAL CONTROL BLOCK(RDA/CT) HAS VALUE 0, REBIND REQUIRED
.-901, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES
NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS
.-900, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE APPLICATION
PROCESS IS NOT CONNECTED TO AN APPLICATION SERVER
.-882, ERROR: SAVEPOINT DOES NOT EXIST
.-881, ERROR: A SAVEPOINT WITH NAME ALREADY EXISTS, BUT THIS SAVEPOINT NAME CANNOT BE REUSED
.-880, ERROR: SAVEPOINT DOES NOT EXIST OR IS INVALID IN THIS CONTEXT
.-879, ERROR: CREATE OR ALTER STATEMENT FOR CANNOT DEFINE A COLUMN, DISTINCT
TYPE, FUNCTION OR STORED PROCEDURE PARAMETER AS MIXED OR GRAPHIC WITH
ENCODING SCHEME
.-878, ERROR: THE PLAN_TABLE USED FOR EXPLAIN CANNOT BE ASCII
.-877, ERROR: CCSID ASCII IS NOT ALLOWED FOR THIS DATABASE OR TABLE SPACE
.-876, ERROR: CANNOT BE CREATED, REASON
.-875, ERROR: CANNOT BE USED WITH THE ASCII DATA REFERENCED
.-874, ERROR: THE ENCODING SCHEME SPECIFIED FOR THE MUST BE THE SAME AS
THE CONTAINING TABLE SPACE OR OTHER PARAMETERS
.-873, ERROR: DATA ENCODED WITH DIFFERENT CCSIDS CANNOT BE REFERENCED IN THE SAME SQL STATEMENT
.-872, ERROR: A VALID CCSID HAS NOT YET BEEN SPECIFIED FOR THIS SUBSYSTEM
.-870, ERROR: THE NUMBER OF HOST VARIABLES IN THE STATEMENT IS NOT EQUAL TO THE NUMBER OF DESCRIPTORS
.-867, ERROR: INVALID SPECIFICATION OF A ROWID COLUMN
.-846, ERROR: INVALID SPECIFICATION OF AN IDENTITY COLUMN
.-843, ERROR: THE SET CONNECTION OR RELEASE STATEMENT MUST SPECIFY AN EXISTING CONNECTION
.-842, ERROR: A CONNECTION TO ALREADY EXISTS
.-840, ERROR: TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST
.-822, ERROR: THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR VARIABLE ADDRESS
.-820, ERROR: THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE CONTAINS A VALUE THAT IS NOT VALID IN THIS RELEASE
.-819, ERROR: THE VIEW CANNOT BE PROCESSED BECAUSE THE LENGTH OF ITS PARSE TREE IN THE CATALOG IS ZERO
.-817, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE STATEMENT WILL RESULT IN A PROHIBITED UPDATE OPERATION
.-815, ERROR: A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY
SPECIFIED IN A SUBSELECT OF A BASIC PREDICATE OR A SET CLAUSE OF
AN UPDATE STATEMENT
.-812, ERROR: THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE A BLANK COLLECTION-ID
WAS FOUND IN THE CURRENT PACKAGESET SPECIAL REGISTER WHILE TRYING TO FORM
A QUALIFIED PACKAGE NAME FOR PROGRAM USING PLAN
.-808, ERROR: THE CONNECT STATEMENT IS NOT CONSISTENT WITH THE FIRST CONNECT STATEMENT
.-807, ERROR: ACCESS DENIED: PACKAGE IS NOT ENABLED FOR ACCESS FROM
. 807, WARNING: THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW
.-804, ERROR: AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT, REASON
.-798, ERROR: YOU CANNOT INSERT A VALUE INTO A COLUMN THAT IS DEFINED WITH
THE OPTION GENERATED ALWAYS. COLUMN NAME
.-797, ERROR: ATTEMPT TO CREATE TRIGGER WITH AN UNSUPPORTED TRIGGERED SQL STATEMENT
.-771, ERROR: INVALID SPECIFICATION OF A ROWID COLUMN
.-770, ERROR: TABLE CANNOT HAVE A LOB COLUMN UNLESS IT ALSO HAS A ROWID COLUMN
.-769, ERROR: SPECIFICATION OF CREATE AUX TABLE DOES NOT MATCH THE CHARACTERISTICS OF THE BASE TABLE
.-768, ERROR: AN AUXILIARY TABLE ALREADY EXISTS FOR THE SPECIFIED COLUMN OR PARTITION
.-767, ERROR: MISSING OR INVALID COLUMN SPECIFICATION FOR INDEX
.-766, ERROR: THE OBJECT OF A STATEMENT IS AN AUXILIARY TABLE FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED
.-765, ERROR: TABLE IS NOT COMPATIBLE WITH DATABASE
.-764, ERROR: A LOB TABLE SPACE AND ITS ASSOCIATED BASE TABLE SPACE MUST BE IN THE SAME DATABASE
.-763, ERROR: INVALID TABLE SPACE NAME
.-752, ERROR: THE CONNECT STATEMENT IS INVALID BECAUSE THE PROCESS IS NOT IN THE CONNECTABLE STATE
.-751, ERROR: (SPECIFIC NAME ) ATTEMPTED TO EXECUTE AN SQL STATEMENT THAT IS NOT ALLOWED
.-750, ERROR: THE SOURCE TABLE CANNOT BE RENAMED BECAUSE IT IS REFERENCED IN EXISTING VIEW DEFINITIONS OR TRIGGER DEFINITIONS
.-748, ERROR: AN INDEX ALREADY EXISTS ON AUXILIARY TABLE
.-746, ERROR: THE SQL STATEMENT IN AN EXTERNAL FUNCTION, TRIGGER, OR IN STORED PROCEDURE VIOLATES THE NESTING SQL RESTRICTION
.-742, ERROR: DSNDB07 IS THE IMPLICIT WORK FILE DATABASE
.-741, ERROR: A DATABASE IS ALREADY DEFINED FOR MEMBER
.-740, ERROR: FUNCTION IS DEFINED WITH THE OPTION MODIFIES SQL DATA WHICH IS
NOT VALID IN THE CONTEXT IN WHICH IT WAS INVOKED
.-739, ERROR: ALTER FUNCTION FAILED BECAUSE FUNCTIONS CANNOT MODIFY DATA WHEN THEY ARE PROCESSED IN PARALLEL
.-737, ERROR: IMPLICIT TABLE SPACE NOT ALLOWED
.-736, ERROR: INVALID OBID SPECIFIED
.-735, ERROR: DATABASE CANNOT BE ACCESSED BECAUSE IT IS NO LONGER A SHARED DATABASE
.-734, ERROR: THE ROSHARE ATTRIBUTE OF A DATABASE CANNOT BE ALTERED FROM ROSHARE READ
.-733, ERROR: THE DESCRIPTION OF A TABLE SPACE, INDEX SPACE, OR TABLE IN A ROSHARE
READ DATABASE MUST BE CONSISTENT WITH ITS DESCRIPTION IN THE OWNER SYSTEM
.-732, ERROR: THE DATABASE IS DEFINED ON THIS SUBSYSTEM WITH THE ROSHARE READ
ATTRIBUTE BUT THE TABLE SPACE OR INDEX SPACE HAS NOT BEEN DEFINED ON THE
OWNING SUBSYSTEM
.-731, ERROR: USER-DEFINED DATASET MUST BE DEFINED WITH SHAREOPTIONS (1,3)
.-730, ERROR: THE PARENT OF A TABLE IN A READ-ONLY SHARED DATABASE MUST ALSO BE A TABLE IN A
READ-ONLY SHARED DATABASE
.-729, ERROR: A STORED PROCEDURE SPECIFYING COMMIT ON RETURN CANNOT BE THE TARGET OF
A NESTED CALL STATEMENT
.-728, ERROR: DATA TYPE IS NOT ALLOWED IN DB2 PRIVATE PROTOCOL PROCESSING
.-726, ERROR: BIND ERROR ATTEMPTING TO REPLACE PACKAGE =. THERE ARE ENABLE OR
DISABLE ENTRIES CURRENTLY ASSOCIATED WITH THE PACKAGE
.-725, ERROR: THE SPECIAL REGISTER AT LOCATION WAS SUPPLIED AN INVALID VALUE
.-724, ERROR: THE ACTIVATION OF THE OBJECT WOULD EXCEED THE MAXIMUM LEVEL OF INDIRECT SQL CASCADING
.-723, ERROR: AN ERROR OCCURRED IN A TRIGGERED SQL STATEMENT IN TRIGGER ,
SECTION NUMBER. INFORMATION RETURNED: SQLCODE , SQLSTATE , AND MESSAGE TOKENS
.-722, ERROR: ERROR USING AUTHORITY PACKAGE DOES NOT EXIST
.-721, ERROR: BIND ERROR FOR PACKAGE = CONTOKEN = ''X IS NOT UNIQUE SO IT CANNOT BE CREATED
.-720, ERROR: BIND ERROR, ATTEMPTING TO REPLACE PACKAGE = WITH VERSION = BUT THIS VERSION ALREADY EXISTS
.-719, ERROR: BIND ADD ERROR USING AUTHORITY PACKAGE ALREADY EXISTS
.-718, ERROR: REBIND OF PACKAGE FAILED BECAUSE IBMREQD OF IS INVALID
.-717, ERROR: FOR WITH MARK FAILED BECAUSE DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED
.-716, ERROR: PROGRAM PRECOMPILED WITH INCORRECT LEVEL FOR THIS RELEASE
.-715, ERROR: PROGRAM WITH MARK FAILED BECAUSE IT DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED
.-713, ERROR: THE REPLACEMENT VALUE FOR IS INVALID
.-697, ERROR: OLD OR NEW CORRELATION NAMES ARE NOT ALLOWED IN A TRIGGER DEFINED
WITH THE FOR EACH STATEMENT CLAUSE. OLD_TABLE OR NEW_TABLE NAMES ARE NOT
ALLOWED IN A TRIGGER WITH THE BEFORE CLAUSE
.-696, ERROR: THE DEFINITION OF TRIGGER INCLUDES AN INVALID USE OF CORRELATION NAME OR TRANSITION TABLE NAME . REASON CODE=
.-694, ERROR: THE DDL STATEMENT CANNOT BE EXECUTED BECAUSE A DROP IS PENDING ON THE DDL REGISTRATION TABLE
.-693, ERROR: THE COLUMN IN DDL REGISTRATION TABLE OR INDEX IS NOT DEFINED PROPERLY
.-692, ERROR: THE REQUIRED UNIQUE INDEX FOR DDL REGISTRATION TABLE DOES NOT EXIST
.-691, ERROR: THE REQUIRED REGISTRATION TABLE DOES NOT EXIST
.-690, ERROR: THE STATEMENT IS REJECTED BY DATA DEFINITION CONTROL SUPPORT. REASON
.-689, ERROR: TOO MANY COLUMNS DEFINED FOR A DEPENDENT TABLE
.-688, ERROR: INCORRECT DATA RETURNED FROM FIELD PROCEDURE, ,
.-687, ERROR: FIELD TYPES INCOMPARABLE
.-686, ERROR: COLUMN DEFINED WITH A FIELD PROCEDURE CAN NOT COMPARE WITH ANOTHER COLUMN WITH DIFFERENT FIELD PROCEDURE
.-685, ERROR: INVALID FIELD TYPE,
.-684, ERROR: THE LENGTH OF LITERAL LIST BEGINNING IS TOO LONG
.-683, ERROR: THE SPECIFICATION FOR COLUMN, DISTINCT TYPE, FUNCTION, OR PROCEDURE CONTAINS INCOMPATIBLE CLAUSES
.-682, ERROR: FIELD PROCEDURE COULD NOT BE LOADED
.-681, ERROR: COLUMN IN VIOLATION OF INSTALLATION DEFINED FIELD PROCEDURE RT: , RS: , MSG:
.-680, ERROR: TOO MANY COLUMNS SPECIFIED FOR A TABLE, VIEW, OR TABLE FUNCTION
.-679, ERROR: THE OBJECT CANNOT BE CREATED BECAUSE A DROP IS PENDING ON THE OBJECT
.-678, ERROR: THE LITERAL SPECIFIED FOR THE INDEX LIMIT KEY MUST CONFORM TO THE DATA
TYPE OF THE CORRESPONDING COLUMN
.-677, ERROR: INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION
.-676, ERROR: ONLY A 4K PAGE BUFFERPOOL CAN BE USED FOR AN INDEX
.-672, ERROR: OPERATION DROP NOT ALLOWED ON TABLE
.-671, ERROR: THE BUFFERPOOL ATTRIBUTE OF THE TABLE SPACE CANNOT BE ALTERED AS
SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE TABLE SPACE
.-670, ERROR: THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT
.-669, ERROR: A TABLE IN A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED
.-668, ERROR: THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDIT PROCEDURE
.-667, ERROR: THE CLUSTERING INDEX FOR A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED
.-666, ERROR: CANNOT BE EXECUTED BECAUSE IS IN PROGRESS
.-665, ERROR: THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID
.-663, ERROR: THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR GREATER THAN THE
NUMBER OF COLUMNS IN THE KEY OF INDEX
.-662, ERROR: A PARTITIONED INDEX CANNOT BE CREATED ON A NON-PARTITIONED TABLE SPACE
.-661, ERROR: INDEX CANNOT BE CREATED ON PARTITIONED TABLE SPACE BECAUSE THE
NUMBER OF PART SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS
OF THE TABLE SPACE
.-660, ERROR: INDEX CANNOT BE CREATED ON PARTITIONED TABLE SPACE BECAUSE KEY LIMITS ARE NOT SPECIFIED
.-658, ERROR: A CANNOT BE DROPPED USING THE STATEMENT
. 658, WARNING: THE SUBPAGES VALUE IS IGNORED FOR THE CATALOG INDEX
.-655, ERROR: THE CREATE OR ALTER STOGROUP IS INVALID BECAUSE THE STORAGE GROUP
WOULD HAVE BOTH SPECIFIC AND NON-SPECIFIC VOLUME IDS
. 655, WARNING: STOGROUP HAS BOTH SPECIFIC AND NONSPECIFIC VOLUME IDS. IT WILL NOT BE ALLOWED IN FUTURE RELEASES.
.-653, ERROR: TABLE IN PARTITIONED TABLE SPACE IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED
. 653, WARNING: TABLE IN PARTITIONED TABLE SPACE IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED
.-652, ERROR: VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION PROCEDURE
.-651, ERROR: TABLE DESCRIPTION EXCEEDS MAXIMUM SIZE OF OBJECT DESCRIPTOR
.-650, ERROR: THE ALTER INDEX CANNOT BE EXECUTED, REASON
. 650, WARNING: THE TABLE BEING CREATED OR ALTERED CAN NOT BECOME A DEPENDENT TABLE
.-647, ERROR: BUFFERPOOL CANNOT BE SPECIFIED BECAUSE IT HAS NOT BEEN ACTIVATED
.-646, ERROR: TABLE CANNOT BE CREATED IN SPECIFIED TABLE SPACE BECAUSE IT ALREADY CONTAINS A TABLE
.-644, ERROR: INVALID VALUE SPECIFIED FOR KEYWORD IN STATEMENT
.-643, ERROR: CHECK CONSTRAINT EXCEEDS MAXIMUM ALLOWABLE LENGTH
.-642, ERROR: TOO MANY COLUMNS IN UNIQUE CONSTRAINTS
.-640, ERROR: LOCKSIZE ROW CANNOT BE SPECIFIED BECAUSE TABLE IN THIS TABLESPACE HAS TYPE 1 INDEX
.-639, ERROR: 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
.-638, ERROR: TABLE CANNOT BE CREATED BECAUSE COLUMN DEFINITION IS MISSING
.-637, ERROR: DUPLICATE KEYWORD
.-636, ERROR: THE PARTITIONING KEYS FOR PARTITION ARE NOT SPECIFIED IN ASCENDING OR DESCENDING ORDER
.-635, ERROR: THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL
.-634, ERROR: THE DELETE RULE MUST NOT BE CASCADE
.-633, ERROR: THE DELETE RULE MUST BE
.-632, ERROR: THE TABLE CANNOT BE DEFINED AS A DEPENDENT OF BECAUSE OF DELETE RULE RESTRICTIONS
.-631, ERROR: FOREIGN KEY IS TOO LONG OR HAS TOO MANY COLUMNS
.-630, ERROR: THE WHERE NOT NULL SPECIFICATION IS INVALID FOR TYPE 1 INDEXES
.-629, ERROR: SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY CANNOT CONTAIN NULL VALUES
.-628, ERROR: THE CLAUSES ARE MUTUALLY EXCLUSIVE
. 627, ERROR: THE ALTER STATEMENT IS INVALID BECAUSE THE PAGESET HAS USER-MANAGED DATA SETS
.-626, ERROR: THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGE SET IS NOT STOPPED
. 626, WARNING: DROPPING THE INDEX TERMINATES ENFORCEMENT OF THE UNIQUENESS OF A KEY
THAT WAS DEFINED WHEN THE TABLE WAS CREATED
.-625, ERROR: TABLE DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PARENT KEY
. 625, WARNING: THE DEFINITION OF TABLE HAS BEEN CHANGED TO INCOMPLETE
.-624, ERROR: TABLE ALREADY HAS A PRIMARY KEY
.-623, ERROR: A CLUSTERING INDEX ALREADY EXISTS ON TABLE
.-622, ERROR: FOR MIXED DATA IS INVALID BECAUSE THE MIXED DATA INSTALL OPTION IS NO
.-621, ERROR: DUPLICATE DBID WAS DETECTED AND PREVIOUSLY ASSIGNED TO
.-620, ERROR: KEYWORD IN STATEMENT IS NOT PERMITTED FOR A SPACE IN THE DATABASE
.-619, ERROR: OPERATION DISALLOWED BECAUSE THE WORK FILE DATABASE IS NOT STOPPED
.-618, ERROR: OPERATION IS NOT ALLOWED ON SYSTEM DATABASES
.-617, ERROR: A TYPE 1 INDEX IS NOT VALID FOR TABLE
.-616, ERROR: CANNOT BE DROPPED BECAUSE IT IS REFERENCED BY
.-615, ERROR: IS NOT ALLOWED ON A PACKAGE IN USE
.-614, ERROR: THE INDEX CANNOT BE CREATED OR THE LENGTH OF THE COLUMN CANNOT BE
CHANGED BECAUSE THE SUM OF THE INTERNAL LENGTHS OF THE IDENTIFIED COLUMNS
IS GREATER THAN THE ALLOWABLE MAXIMUM
.-613, ERROR: THE PRIMARY KEY OR A UNIQUE CONSTRAINT IS TOO LONG OR HAS TOO MANY COLUMNS
.-612, ERROR: IS A DUPLICATE COLUMN NAME
.-611, ERROR: ONLY LOCKMAX 0 CAN BE SPECIFIED WHEN THE LOCK SIZE OF THE TABLESPACE IS TABLESPACE OR TABLE
.-607, ERROR: OPERATION OR OPTION IS NOT DEFINED FOR THIS OBJECT
.-604, ERROR: A DATA TYPE DEFINITION SPECIFIES AN INVALID LENGTH, PRECISION, OR SCALE ATTRIBUTE
.-603, ERROR: A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS ROWS
WHICH ARE DUPLICATES WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS
.-602, ERROR: TOO MANY COLUMNS SPECIFIED IN A CREATE INDEX
.-601, ERROR: THE NAME OF THE OBJECT TO BE CREATED OR THE TARGET OF A RENAME
STATEMENT IS IDENTICAL TO THE EXISTING NAME OF THE OBJECT TYPE
.-594, ERROR: ATTEMPT TO CREATE A NULLABLE ROWID OR DISTINCT TYPE COLUMN
.-593, ERROR: NOT NULL MUST BE SPECIFIED FOR ROWID OR DISTINCT TYPE COLUMN
- 592, ERROR: NOT AUTHORIZED TO CREATE FUNCTIONS OR PROCEDURES IN WLM ENVIRONMENT
.-590, ERROR: PARAMETER NAME IS NOT UNIQUE IN THE CREATE FOR ROUTINE
.-586, ERROR: THE TOTAL LENGTH OF THE CURRENT PATH SPECIAL REGISTER CANNOT EXCEED 254 CHARACTERS
.-585, ERROR: THE SCHEMA NAME CANNOT APPEAR MORE THAN ONCE IN THE CURRENT PATH
. 585, WARNING: THE SCHEMA NAME APPEARS MORE THAN ONCE IN THE CURRENT PATH
.-582, ERROR: THE SEARCH-CONDITION IN A SEARCHED-WHENCLAUSE CANNOT BE A QUANTIFIED
PREDICATE, IN PREDICATE, OR AN EXISTS PREDICATE
.-581, ERROR: THE DATA TYPES OF THE RESULT-EXPRESSIONS OF A CASE EXPRESSION ARE NOT COMPATIBLE
.-580, ERROR: THE RESULT-EXPRESSIONS OF A CASE EXPRESSION CANNOT ALL BE NULL
.-579, ERROR: ATTEMPTED TO READ DATA WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION
.-577, ERROR: ATTEMPTED TO MODIFY DATA WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION
.-574, ERROR: THE SPECIFIED DEFAULT VALUE OR IDENTITY ATTRIBUTE VALUE CONFLICTS WITH THE DEFINITION OF COLUMN
.-573, ERROR: TABLE DOES NOT HAVE A UNIQUE KEY WITH THE SPECIFIED COLUMN NAMES
.-571, ERROR: THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE
.-567, ERROR: AUTHORIZATION ERROR USING AUTHORITY PACKAGE = PRIVILEGE =
.-559, ERROR: ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED
.-558, ERROR: INVALID CLAUSE OR COMBINATION OF CLAUSES ON A GRANT OR REVOKE
. 558, WARNING: THE WITH GRANT OPTION IS IGNORED
.-557, ERROR: INCONSISTENT GRANT/REVOKE KEYWORD. PERMITTED KEYWORDS ARE
.-556, ERROR: CANNOT HAVE THE PRIVILEGE REVOKED BY BECAUSE THE REVOKEE DOES NOT
POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT
.-555, ERROR: AN AUTHORIZATION ID CANNOT REVOKE A PRIVILEGE FROM ITSELF
.-554, ERROR: AN AUTHORIZATION ID CANNOT GRANT A PRIVILEGE TO ITSELF
.-553, ERROR: SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS
. 552, WARNING: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
.-551, ERROR: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
.-551, ERROR: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION ON OBJECT
. 551, WARNING: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION ON OBJECT
.-549, ERROR: THE STATEMENT IS NOT ALLOWED FOR BECAUSE THE BIND OPTION DYNAMICRULES(RUN) IS NOT IN EFFECT FOR
.-548, ERROR: A CHECK CONSTRAINT THAT IS DEFINED WITH IS INVALID
.-546, ERROR: THE CHECK CONSTRAINT IS INVALID
.-545, ERROR: THE REQUESTED OPERATION IS NOT ALLOWED BECAUSE A ROW DOES NOT SATISFY THE CHECK CONSTRAINT
.-544, ERROR: THE CHECK CONSTRAINT SPECIFIED IN THE ALTER TABLE STATEMENT CANNOT
BE ADDED BECAUSE AN EXISTING ROW VIOLATES THE CHECK CONSTRAINT
.-543, ERROR: A ROW IN A PARENT TABLE CANNOT BE DELETED BECAUSE THE CHECK CONSTRAINT RESTRICTS THE DELETION
-542, ERROR: CANNOT BE A COLUMN OF A PRIMARY KEY, A UNIQUE CONSTRAINT, OR A PARENT KEY BECAUSE IT CAN CONTAIN NULL VALUES
.-540, ERROR: THE DEFINITION OF TABLE IS INCOMPLETE BECAUSE IT LACKS A PRIMARY INDEX OR A REQUIRED UNIQUE INDEX
.-539, ERROR: TABLE DOES NOT HAVE A PRIMARY KEY
.-538, ERROR: FOREIGN KEY DOES NOT CONFORM TO THE DESCRIPTION OF A PARENT KEY OF TABLE
.-537, ERROR: THE PRIMARY KEY CLAUSE, A FOREIGN KEY CLAUSE, OR A UNIQUE CLAUSE
IDENTIFIES COLUMN MORE THAN ONCE
.-536, ERROR: THE DELETE STATEMENT IS INVALID BECAUSE TABLE CAN BE AFFECTED BY THE OPERATION
.-534, ERROR: THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE-ROW UPDATE
.-533, ERROR: INVALID MULTIPLE-ROW INSERT
.-531, ERROR: PARENT KEY IN A PARENT ROW CANNOT BE UPDATED BECAUSE IT HAS ONE OR MORE DEPENDENT ROWS IN RELATIONSHIP
.-526, ERROR: THE REQUESTED OPERATION OR USAGE DOES NOT APPLY TO TEMPORARY TABLE
.-525, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS IN ERROR AT BIND
TIME FOR SECTION = PACKAGE = CONSISTENCY TOKEN = X''
.-519, ERROR: THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT OF THE OPENED CURSOR
.-518, ERROR: THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT
.-517, ERROR: CURSOR CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOT IDENTIFY A PREPARED SELECT STATEMENT
.-516, ERROR: THE DESCRIBE FOR STATIC STATEMENT DOES NOT IDENTIFY A PREPARED STATEMENT
.-514, ERROR: THE CURSOR IS NOT IN A PREPARED STATE
.-513, ERROR: THE ALIAS MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE ALIAS
.-512, ERROR: STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID
.-511, ERROR: THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE TABLE DESIGNATED BY THE CURSOR CANNOT BE MODIFIED
.-510, ERROR: THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE STATEMENT CANNOT BE MODIFIED
.-509, ERROR: THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT THE SAME TABLE DESIGNATED BY THE CURSOR
.-508, ERROR: THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT POSITIONED ON A ROW
.-507, ERROR: THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT OPEN
.-504, ERROR: THE CURSOR NAME IS NOT DEFINED
.-500, ERROR: THE IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION WAS DESTROYED
.-499, ERROR: CURSOR HAS ALREADY BEEN ASSIGNED TO THIS OR ANOTHER RESULT SET FROM PROCEDURE
.-497, ERROR: THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASE
.-496, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET
THAT WAS NOT CREATED BY THE CURRENT SERVER
.-495, ERROR: ESTIMATED PROCESSOR COST OF PROCESSOR SECONDS ( SERVICE UNITS) IN COST
CATEGORY EXCEEDS A RESOURCE LIMIT ERROR THRESHOLD OF SERVICE UNITS
.-492, ERROR: THE CREATE FUNCTION FOR HAS A PROBLEM WITH PARAMETER NUMBER . IT MAY
INVOLVE A MISMATCH WITH A SOURCE FUNCTION
.-491, ERROR: CREATE STATEMENT FOR USER-DEFINED FUNCTION MUST HAVE A RETURNS CLAUSE, AND
EITHER THE EXTERNAL CLAUSE (WITH OTHER REQUIRED KEYWORDS) OR THE SOURCE CLAUSE
.-490, ERROR: NUMBER DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF
ALLOWABLE VALUES IN THIS CONTEXT (, )
.-487, ERROR: ATTEMPTED TO EXECUTE AN SQL STATEMENT WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION
.-483, ERROR: IN CREATE FUNCTION FOR STATEMENT, THE NUMBER OF PARAMETERS DOES NOT MATCH THE NUMBER OF PARAMETERS OF THE SOURCE FUNCTION
.-480, ERROR: THE PROCEDURE HAS NOT YET BEEN CALLED
.-478, ERROR: DROP OR REVOKE ON OBJECT TYPE CANNOT BE PROCESSED BECAUSE OBJECT OF TYPE IS DEPENDENT ON IT
.-476, ERROR: REFERENCE TO FUNCTION WAS NAMED WITHOUT A SIGNATURE, BUT THE FUNCTION IS NOT UNIQUE WITHIN ITS SCHEMA
.-475, ERROR: THE RESULT TYPE OF THE SOURCE FUNCTION CANNOT BE CAST TO THE RETURNS TYPE OF THE USER-DEFINED FUNCTION
.-473, ERROR: A USER DEFINED DATA TYPE CANNOT BE CALLED THE SAME NAME AS A SYSTEM PREDEFINED TYPE (BUILT-IN TYPE)
.-472, ERROR: CURSOR WAS LEFT OPEN BY EXTERNAL FUNCTION (SPECIFIC NAME )
.-471, ERROR: INVOCATION OF FUNCTION OR PROCEDURE FAILED DUE TO REASON
.-470, ERROR: SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT PARAMETER , BUT THE
STORED PROCEDURE DOES NOT SUPPORT NULL VALUES
.-469, ERROR: SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER
.-463, ERROR: EXTERNAL FUNCTION (SPECIFIC NAME ) HAS RETURNED AN INVALID SQLSTATE, WITH DIAGNOSTIC TEXT
.-461, ERROR: A VALUE WITH DATA TYPE CANNOT BE CAST TO TYPE
.-458, ERROR: IN A REFERENCE TO FUNCTION BY SIGNATURE, A MATCHING FUNCTION COULD NOT BE FOUND
.-457, ERROR: A FUNCTION OR DISTINCT TYPE CANNOT BE CALLED SINCE IT IS RESERVED FOR SYSTEM USE
.-456, ERROR: IN CREATE FUNCTION FOR , THE SPECIFIC NAME ALREADY EXISTS IN THE SCHEMA
.-455, ERROR: IN CREATE FUNCTION FOR , THE SCHEMA NAME PROVIDED FOR THE SPECIFIC NAME DOES NOT MATCH THE SCHEMA NAME OF THE FUNCTION
.-454, ERROR: THE SIGNATURE PROVIDED IN THE CREATE FUNCTION STATEMENT FOR MATCHES
THE SIGNATURE OF SOME OTHER FUNCTION ALREADY EXISTING IN THE SCHEMA
.-453, ERROR: THERE IS A PROBLEM WITH THE RETURNS CLAUSE IN THE CREATE FUNCTION STATEMENT FOR
.-451, ERROR: THE DEFINITION, IN THE CREATE FUNCTION FOR CONTAINS DATA TYPE
WHICH IS NOT APPROPRIATE FOR AN EXTERNAL FUNCTION WRITTEN IN THE GIVEN LANGUAGE
.-450, ERROR: USER-DEFINED FUNCTION OR STORED PROCEDURE , PARAMETER NUMBER , OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH
.-449, ERROR: CREATE OR ALTER STATEMENT FOR FUNCTION OR PROCEDURE CONTAINS AN INVALID
FORMAT OF THE EXTERNAL NAME CLAUSE OR IS MISSING THE EXTERNAL NAME CLAUSE
.-444, ERROR: USER PROGRAM COULD NOT BE FOUND
.-443, ERROR: EXTERNAL FUNCTION (SPECIFIC NAME ) HAS RETURNED AN ERROR SQLSTATE WITH DIAGNOSTIC TEXT
.-441, ERROR: INVALID USE OF 'DISTINCT' OR 'ALL' WITH SCALAR FUNCTION
.-440, ERROR: NO BY THE NAME HAVING COMPATIBLE ARGUMENTS WAS FOUND IN THE CURRENT PATH
.-438, ERROR: APPLICATION RAISED ERROR WITH DIAGNOSTIC TEXT:
.-435, ERROR: AN INVALID SQLSTATE IS SPECIFIED IN THE FUNCTION RAISE_ERROR OR IN A SIGNAL SQLSTATE STATEMENT
.-433, ERROR: VALUE IS TOO LONG
.-430, ERROR: (SPECIFIC NAME ) HAS ABNORMALLY TERMINATED
.-427, ERROR: DYNAMIC ROLLBACK NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED
.-426, ERROR: DYNAMIC COMMIT NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED
.-423, ERROR: INVALID VALUE FOR LOCATOR IN POSITION
.-421, ERROR: THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE THE SAME NUMBER OF COLUMNS
.-420, ERROR: THE VALUE OF A CHARACTER STRING ARGUMENT WAS NOT ACCEPTABLE TO THE FUNCTION
.-419, ERROR: A DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT WOULD HAVE A NEGATIVE SCALE
.-418, ERROR: A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETER MARKERS
.-417, ERROR: A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER MARKERS AS THE OPERANDS OF THE SAME OPERATOR
.-416, ERROR: AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN
.-415, ERROR: THE CORRESPONDING COLUMNS, , OF THE OPERANDS OF A UNION OR A UNION
ALL DO NOT HAVE COMPARABLE COLUMN DESCRIPTIONS
.-414, ERROR: A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A STRING
.-413, ERROR: OVERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION
.-412, ERROR: THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS
.-411, ERROR: CURRENT SQLID CANNOT BE USED IN A STATEMENT THAT REFERENCES REMOTE OBJECTS
.-410, ERROR: THE FLOATING POINT LITERAL CONTAINS MORE THAN 30 CHARACTERS
.-409, ERROR: INVALID OPERAND OF A COUNT FUNCTION
.-408, ERROR: THE VALUE IS NOT COMPATIBLE WITH THE DATA TYPE OF ITS TARGET
.-407, ERROR: AN UPDATE, INSERT, OR SET VALUE IS NULL, BUT THE OBJECT COLUMN CANNOT CONTAIN NULL VALUES
.-406, ERROR: A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECT COLUMN
.-405, ERROR: THE NUMERIC LITERAL CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF RANGE
.-404, ERROR: THE SQL STATEMENT SPECIFIES A STRING THAT IS TOO LONG
.-402, ERROR: AN ARITHMETIC FUNCTION OR OPERATOR IS APPLIED TO CHARACTER OR DATETIME DATA
.-401, ERROR: THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE
.-400, ERROR: THE CATALOG HAS THE MAXIMUM NUMBER OF USER DEFINED INDEXES
.-399, ERROR: ATTEMPTED TO INSERT AN INVALID VALUE INTO A ROWID COLUMN
.-398, ERROR: A LOCATOR WAS REQUESTED FOR HOST VARIABLE NUMBER BUT THE VARIABLE IS NOT A LOB
.-397, ERROR: THE OPTION GENERATED IS SPECIFIED WITH A COLUMN THAT IS NOT A ROW ID OR DISTINCT TYPE BASED ON A ROW ID
.-396, ERROR: ATTEMPTED TO EXECUTE AN SQL STATEMENT DURING FINAL CALL PROCESSING
.-392, ERROR: SQLDA PROVIDED FOR CURSOR HAS BEEN CHANGED FROM THE PREVIOUS FETCH
.-390, ERROR: THE FUNCTION NAME , SPECIFIC NAME , IS NOT VALID IN THE CONTEXT IN WHICH IT OCCURS
.-373, ERROR: DEFAULT CANNOT BE SPECIFIED FOR IDENTITY COLUMN
.-372, ERROR: ONLY ONE ROWID OR IDENTITY COLUMN IS ALLOWED IN A TABLE
.-359, ERROR: THE RANGE OF VALUES FOR THE IDENTITY COLUMN IS EXHAUSTED
.-355, ERROR: A LOB COLUMN IS TOO LARGE TO BE LOGGED
.-352, ERROR: AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION OF THE INPUT-LIST
.-351, ERROR: AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION OF THE SELECT-LIST
.-350, ERROR: INVALID SPECIFICATION OF A LARGE OBJECT COLUMN
.-339, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED FROM AN ASCII BASED DRDA APPLICATION REQUESTOR TO A V2R2 DB2 SUBSYSTEM
.-338, ERROR: AN ON CLAUSE IS INVALID
.-333, ERROR: THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE SUBTYPE
KNOWN AT BIND TIME AND THE DIFFERENCE CANNOT BE RESOLVED BY TRANSLATION
.-332, ERROR: SYSSTRINGS DOES NOT DEFINE A TRANSLATION FROM CCSID TO
.-331, ERROR: A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE IT CANNOT
BE TRANSLATED. REASON , CHARACTER , POSITION
. 331, WARNING: THE NULL VALUE HAS BEEN ASSIGNED TO A HOST VARIABLE BECAUSE THE
STRING CANNOT BE TRANSLATED. REASON , CHARACTER , HOST VARIABLE
.-330, ERROR: A STRING CANNOT BE USED BECAUSE IT CANNOT BE TRANSLATED. REASON, CHARACTER , HOST VARIABLE
.-327, ERROR: THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITION RANGE FOR THE LAST PARTITION
.-314, ERROR: THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE
.-313, ERROR: THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKERS
.-312, ERROR: IS AN UNDEFINED OR UNUSABLE HOST VARIABLE OR IS USED IN A DYNAMIC SQL STATEMENT OR A TRIGGER DEFINITION
.-310, ERROR: DECIMAL HOST VARIABLE OR PARAMETER CONTAINS NON-DECIMAL DATA
.-309, ERROR: A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE
.-303, ERROR: A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER BECAUSE THE DATA TYPES ARE NOT COMPARABLE
.-302, ERROR: THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE
.-301, ERROR: THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER CANNOT BE USED AS SPECIFIED BECAUSE OF ITS DATA TYPE
.-300, ERROR: THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER IS NOT NUL-TERMINATED
.-251, ERROR: TOKEN IS NOT VALID
.-250, ERROR: THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME
.-240, ERROR: THE PART CLAUSE OF A LOCK TABLE STATEMENT IS INVALID
.-221, ERROR: "SET OF OPTIONAL COLUMNS" IN EXPLANATION TABLE IS INCOMPLETE.
OPTIONAL COLUMN IS MISSING
.-220, ERROR: THE COLUMN IN EXPLANATION TABLE IS NOT DEFINED PROPERLY
. 220, WARNING: THE COLUMN IN EXPLANATION TABLE IS NOT DEFINED PROPERLY
.-219, ERROR: THE REQUIRED EXPLANATION TABLE DOES NOT EXIST
. 219, WARNING: THE REQUIRED EXPLANATION TABLE DOES NOT EXIST
.-214, ERROR: AN EXPRESSION STARTING WITH IN THE CLAUSE IS NOT VALID. REASON CODE =
.-212, ERROR: IS SPECIFIED MORE THAN ONCE IN THE REFERENCING CLAUSE OF A TRIGGER DEFINITION
.-208, ERROR: THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN IS NOT PART OF THE RESULT TABLE
.-203, ERROR: A REFERENCE TO COLUMN IS AMBIGUOUS
. 203, WARNING: THE QUALIFIED COLUMN NAME WAS RESOLVED USING A NON-UNIQUE OR UNEXPOSED NAME
.-199, ERROR: ILLEGAL USE OF KEYWORD , TOKEN WAS EXPECTED
.-198, ERROR: THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY
.-197, ERROR: QUALIFIED COLUMN NAMES IN ORDER BY CLAUSE NOT PERMITTED WHEN UNION OR UNION ALL SPECIFIED
.-191, ERROR: A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA
.-190, ERROR: ATTRIBUTES OF COLUMN IN TABLE ARE NOT COMPATIBLE WITH THE EXISTING COLUMN
.-189, ERROR: CCSID IS UNKNOWN OR INVALID FOR THE DATA TYPE OR SUBTYPE
.-188, ERROR: THE STRING REPRESENTATION OF A NAME IS INVALID
.-187, ERROR: 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
.-186, ERROR: THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN INCREASED
AND EXECUTING PROGRAM RELIES ON THE OLD LENGTH
.-185, ERROR: THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HAS BEEN INSTALLED
.-184, ERROR: AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARKER
.-183, ERROR: AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHIN THE VALID RANGE OF DATES
.-182, ERROR: AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS INVALID
.-173, ERROR: UR IS SPECIFIED ON THE WITH CLAUSE BUT THE CURSOR IS NOT READ-ONLY
.-171, ERROR: THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT OF IS INVALID
.-170, ERROR: THE NUMBER OF ARGUMENTS SPECIFIED FOR IS INVALID
.-164, ERROR: DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH QUALIFICATION
.-161, ERROR: THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFY THE VIEW DEFINITION
.-160, ERROR: THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW
.-159, ERROR: DROP OR COMMENT ON IDENTIFIES A(N) RATHER THAN A(N)
.-158, ERROR: THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAME AS THE
NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE, OR THE NUMBER OF COLUMNS
SPECIFIED IN THE CORRELATION CLAUSE IN A FROM CLAUSE IS NOT THE SAME AS THE
NUMBER OF COLUMNS IN THE CORRESPONDING TABLE, VIEW, TABLE EXPRESSION, OR
TABLE FUNCTION
.-157, ERROR: ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE. IS NOT THE NAME OF A TABLE
.-156, ERROR: THE STATEMENT DOES NOT IDENTIFY A TABLE
.-154, ERROR: THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION IS NOT VALID
.-153, ERROR: THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION DOES NOT INCLUDE A UNIQUE NAME FOR EACH COLUMN
.-152, ERROR: THE DROP CLAUSE IN THE ALTER STATEMENT IS INVALID BECAUSE IS A
.-151, ERROR: THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMN INDICATES THAT IT CANNOT BE UPDATED
.-150, ERROR: THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW OR
TRANSITION TABLE FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED
.-148, ERROR: THE SOURCE TABLE CANNOT BE RENAMED OR ALTERED
.-147, ERROR: ALTER FUNCTION FAILED BECAUSE SOURCE FUNCTIONS CANNOT BE ALTERED
.-144, ERROR: INVALID SECTION NUMBER
.-142, ERROR: THE SQL STATEMENT IS NOT SUPPORTED
.-138, ERROR: THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT OF RANGE
.-137, ERROR: THE LENGTH RESULTING FROM IS GREATER THAN
.-136, ERROR: SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES
.-134, ERROR: IMPROPER USE OF LONG STRING COLUMN OR AN EXPRESSION OF MAXIMUM LENGTH GREATER THAN 255
.-133, ERROR: A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID
BECAUSE ALL COLUMN REFERENCES IN ITS ARGUMENT ARE NOT CORRELATED TO THE
GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO
.-132, ERROR: AN OPERAND OF IS NOT VALID
.-131, ERROR: STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES
.-130, ERROR: THE ESCAPE CLAUSE CONSISTS OF MORE THAN ONE CHARACTER, OR THE STRING
PATTERN CONTAINS AN INVALID OCCURRENCE OF THE ESCAPE CHARACTER
.-129, ERROR: THE STATEMENT CONTAINS TOO MANY TABLE NAMES
.-128, ERROR: INVALID USE OF NULL IN A PREDICATE
.-127, ERROR: DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT
.-126, ERROR: THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE
.-125, ERROR: AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT
.-123, ERROR: THE PARAMETER IN POSITION IN THE FUNCTION MUST BE A CONSTANT OR KEYWORD
.-122, ERROR: 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 THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE
.-121, ERROR: THE COLUMN IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OR SET TRANSITION VARIABLE STATEMENT
.-120, ERROR: A WHERE CLAUSE, SET CLAUSE, VALUES CLAUSE, OR A SET ASSIGNMENT STATEMENT INCLUDES A COLUMN FUNCTION
.-119, ERROR: A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN THE GROUP BY CLAUSE
.-118, ERROR: THE OBJECT TABLE OR VIEW OF THE DELETE OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE
.-115, ERROR: A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR IS FOLLOWED
BY A PARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY
.-114, ERROR: THE LOCATION NAME DOES NOT MATCH THE CURRENT SERVER
.-113, ERROR: INVALID CHARACTER FOUND IN: . REASON CODE
.-112, ERROR: THE OPERAND OF A COLUMN FUNCTION IS ANOTHER COLUMN FUNCTION
.-111, ERROR: A COLUMN FUNCTION DOES NOT INCLUDE A COLUMN NAME
. 111, WARNING: THE SUBPAGES OPTION IS NOT SUPPORTED FOR TYPE 2 INDEXES
.-110, ERROR: INVALID HEXADECIMAL LITERAL BEGINNING
. 110, WARNING: SQL UPDATE TO A DATA CAPTURE TABLE NOT SIGNALED TO ORIGINATING SUBSYSTEM
.-109, ERROR: CLAUSE IS NOT PERMITTED
.-108, ERROR: THE NAME IS QUALIFIED INCORRECTLY
.-107, ERROR: THE NAME IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS
.-105, ERROR: INVALID STRING
.-104, ERROR: ILLEGAL SYMBOL "". SOME SYMBOLS THAT MIGHT BE LEGAL ARE:
.-103, ERROR: IS AN INVALID NUMERIC LITERAL
.-101, ERROR: THE STATEMENT IS TOO LONG OR TOO COMPLEX
.-097, ERROR: THE USE OF LONG VARCHAR OR LONG VARGRAPHIC IS NOT ALLOWED IN THIS CONTEXT
.-084, ERROR: UNACCEPTABLE SQL STATEMENT
.-079, ERROR: QUALIFIER FOR DECLARED GLOBAL TEMPORARY TABLE OR INDEX MUST BE SESSION, NOT
.-060, ERROR: INVALID SPECIFICATION :
.-029, ERROR: INTO CLAUSE REQUIRED
.-010, ERROR: THE STRING CONSTANT BEGINNING IS NOT TERMINATED
.-007, ERROR: STATEMENT CONTAINS THE ILLEGAL CHARACTER
. 000, SUCCESSFUL EXECUTION
. 012, WARNING: THE UNQUALIFIED COLUMN NAME WAS INTERPRETED AS A CORRELATED REFERENCE
. 098, WARNING: A DYNAMIC SQL STATEMENT ENDS WITH A SEMICOLON
. 162, WARNING: TABLE SPACE . HAS BEEN PLACED IN CHECK PENDING
. 218, WARNING: THE SQL STATEMENT REFERENCING A REMOTE OBJECT CANNOT BE EXPLAINED
. 236, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED FOR COLUMNS
. 237, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED BECAUSE AT LEAST
ONE OF THE COLUMNS BEING DESCRIBED IS A DISTINCT TYPE
. 238, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT SQLVAR ENTRIES ARE NEEDED
FOR COLUMNS BECAUSE AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A LOB
. 239, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED FOR COLUMNS BECAUSE
AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A DISTINCT TYPE
. 339, WARNING: THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED BUT THERE MAY BE
SOME CHARACTER CONVERSION INCONSISTENCIES
. 394, WARNING: USER SPECIFIED OPTIMIZATION HINTS USED DURING ACCESS PATH SELECTION
. 395, WARNING: USER SPECIFIED OPTIMIZATION HINTS ARE INVALID (REASON CODE = '').
THE OPTIMIZATION HINTS ARE IGNORED
. 402, WARNING: LOCATION IS UNKNOWN
. 403, WARNING: THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS STATEMENT DOES NOT EXIST
. 434, WARNING: OPTION IS A DEPRECATED FEATURE
. 445, WARNING: VALUE HAS BEEN TRUNCATED
. 462, WARNING: EXTERNAL FUNCTION OR PROCEDURE (SPECIFIC NAME ) HAS RETURNED A
WARNING SQLSTATE, WITH DIAGNOSTIC TEXT
. 464, WARNING: PROCEDURE RETURNED QUERY RESULT SETS, WHICH EXCEEDS THE DEFINED LIMIT
. 466, WARNING: PROCEDURE RETURNED QUERY RESULT SETS
. 494, WARNING: NUMBER OF RESULT SETS IS GREATER THAN NUMBER OF LOCATORS
. 495, WARNING: ESTIMATED PROCESSOR COST OF PROCESSOR SECONDS ( SERVICE UNITS) IN
COST CATEGORY EXCEEDS A RESOURCE LIMIT WARNING THRESHOLD OF SERVICE UNITS
. 535, WARNING: THE RESULT OF THE POSITIONED UPDATE OR DELETE MAY DEPEND ON THE
ORDER OF THE ROWS
. 541, WARNING: THE REFERENTIAL OR UNIQUE CONSTRAINT HAS BEEN IGNORED BECAUSE IT IS A DUPLICATE
. 561, WARNING: THE ALTER, INDEX, REFERENCES, AND TRIGGER PRIVILEGES CANNOT BE
GRANTED TO PUBLIC AT ALL LOCATIONS
. 562, WARNING: A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY
HAS THE PRIVILEGE FROM THE GRANTOR
. 599, WARNING: COMPARISON FUNCTIONS ARE NOT CREATED FOR A DISTINCT TYPE BASED
ON A LONG STRING DATA TYPE
. 610, WARNING: A CREATE/ALTER ON OBJECT HAS PLACED OBJECT IN PENDING
. 645, WARNING: WHERE NOT NULL IS IGNORED BECAUSE THE INDEX KEY CANNOT CONTAIN NULL VALUES
. 664, WARNING: THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE PARTITIONED
INDEX EXCEEDS THE LENGTH IMPOSED BY THE INDEX MANAGER
. 738, WARNING: DEFINITION CHANGE OF MAY REQUIRE SIMILAR CHANGE ON READ-ONLY SYSTEMS
. 799, WARNING: A SET STATEMENT REFERENCES A SPECIAL REGISTER THAT DOES NOT EXIST AT THE SERVER SITE
. 806, WARNING: BIND ISOLATION LEVEL RR CONFLICTS WITH TABLESPACE LOCKSIZE PAGE
OR LOCKSIZE ROW AND LOCKMAX 0
. 863, WARNING: THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED
. 883, WARNING: ROLLBACK TO SAVEPOINT OCCURRED WHEN THERE WERE OPERATIONS THAT CANNOT
BE UNDONE OR AN OPERATION THAT CANNOT BE UNDONE OCCURRED WHEN THERE WAS A
SAVEPOINT OUTSTANDING
Scroll down to see ALL the SQLCODES there are in Version 7.The most common ones
are at the top.
.+100| SQLSTATE 02000 Row not found or end of cursor
. 100, NOT FOUND: ROW NOT FOUND FOR FETCH, UPDATE, OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE
.-102, String constant is too long
.-102, ERROR: LITERAL STRING IS TOO LONG. STRING BEGINS
.-117, The number of values you are trying to INSERT does not match the number of columns
.117, WARNING: THE NUMBER OF INSERT VALUES IS NOT THE SAME AS THE NUMBER OF OBJECT COLUMNS
.-117, ERROR: THE NUMBER OF ASSIGNED VALUES IS NOT THE SAME AS THE NUMBER OF SPECIFIED OR IMPLIED COLUMNS
.-180 SQLSTATE 22007, Bad data in Date/Time/Timestamp
String representation of DATE, TIME, TIMESTAMP is invalid
.-180, ERROR: THE DATE, TIME, OR TIMESTAMP VALUE IS INVALID
.-181 SQLSTATE 22007, Bad data in Date/Time/Timestamp
Value for DATE, TIME, TIMESTAMP is invalid
.-181, ERROR: THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID DATETIME VALUE
.-199, Illegal use of the specified keyword.
.-204, Object not defined to DB2
. 204, WARNING: IS AN UNDEFINED NAME
.-204, ERROR: IS AN UNDEFINED NAME
.-205, Column name not in specified table
.-205, ERROR: IS NOT A COLUMN OF TABLE
.-206, Column does not exist in any table in the SELECT
.-206, ERROR: IS NOT A COLUMN OF AN INSERTED TABLE, UPDATED TABLE, OR
ANY TABLE IDENTIFIED IN A FROM CLAUSE, OR IS NOT A COLUMN OF THE
TRIGGERING TABLE OF A TRIGGER
. 206, WARNING: IS NOT A COLUMN OF AN INSERTED TABLE,
UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM CLAUSE
.-216, You need to use the same number of expressions on both sides of the
comparison.
when using multiple operands in a comparison,
Correct example:
WHERE (E.SALARY, E.COMM) IN (SELECT S.PAY, S.COMMISSION
Incorrect example:
WHERE (E.SALARY, E.COMM, E.BONUS)
IN (SELECT S.PAY, S.COMMISSION
. 222, Trying to fetch a row that fell through a DELETE hole
.+223, Trying to fetch a row that fell through an UPDATE hole
.-224, FETCH cannot make an INSENSITIVE cursor SENSITIVE
.-229, The locale specified in a SET LOCALE statement was not found.
.-229, ERROR: THE LOCALE SPECIFIED IN A SET LOCALE OR OTHER STATEMENT THAT IS LOCALE SENSITIVE WAS NOT FOUND
.+231, FETCH but you did a BEFORE or AFTER and you are not on a valid row
.+304, Value cannot be assigned to this host variable because it is out of range
.-304, ERROR: A VALUE WITH DATA TYPE CANNOT BE ASSIGNED TO A HOST
VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST
VARIABLE IN POSITION WITH DATA TYPE
.304, WARNING: A VALUE WITH DATA TYPE CANNOT BE ASSIGNED TO A HOST
VARIABLE BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST
VARIABLE IN POSITION WITH DATA TYPE
.-305, Null indicator needed
.-305, ERROR: THE NULL VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE
NUMBER BECAUSE NO INDICATOR VARIABLE IS SPECIFIED
.-311, Varchar, insert or update. You didn’t set the -LEN field with the right data length
.-311, ERROR: THE LENGTH OF INPUT HOST VARIABLE NUMBER IS NEGATIVE OR GREATER THAN THE MAXIMUM
.-482, The procedure returned no locators
.-482, ERROR: THE PROCEDURE RETURNED NO LOCATORS
.-501, Cursor not open on FETCH
.-501, ERROR: THE CURSOR IDENTIFIED IN A FETCH OR CLOSE STATEMENT IS NOT OPEN
.-502, Opening cursor that is already open
.-502, ERROR: THE CURSOR IDENTIFIED IN AN OPEN STATEMENT IS ALREADY OPEN
.-503, Updating column which needs to be specified in FOR UPDATE OF
.-503, ERROR: A COLUMN CANNOT BE UPDATED BECAUSE IT IS NOT IDENTIFIED IN
THE UPDATE CLAUSE OF THE SELECT STATEMENT OF THE CURSOR
.-530 SQLSTATE 23503, Referential integrity prevents the INSERT/UPDATE
.-530, ERROR: THE INSERT OR UPDATE VALUE OF FOREIGN KEY IS INVALID
.-532 SQLSTATE 23504Referential integrity (DELETE RESTRICT rule) prevents the DELETE
.-532, ERROR: THE RELATIONSHIP RESTRICTS THE DELETION OF ROW WITH RID X''
.-532 SQLSTATE 42914, Referential integrity (DELETE RESTRICT rule) prevents the DELETE
.-515 SQLSTATE 23513, Check constraint prevents the INSERT/UPDATE
.-747, The table specified is not available because tables and/or indexes need to be created.
.-747, ERROR: TABLE IS NOT AVAILABLE UNTIL THE AUXILIARY TABLES AND
INDEXES FOR ITS EXTERNALLY STORED COLUMNS HAVE BEEN CREATED
.+802, The null indicator was set to -2 because an arithmetic statement didn't work.
.-802, ERROR: EXCEPTION ERROR HAS OCCURRED DURING OPERATION ON DATA, POSITION
. 802, WARNING: EXCEPTION ERROR HAS OCCURRED DURING OPERATION ON DATA, POSITION
.-803, SQLSTATE 23505 Duplicate key on insert or update
.-803, ERROR: AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE INDEX IN
INDEX SPACE CONSTRAINS COLUMNS OF THE TABLE SO NO TWO ROWS CAN
CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING ROW IS X''
.-805, DBRM or package not found in plan Is plan name correct?
.-805, ERROR: DBRM OR PACKAGE NAME NOT FOUND IN PLAN REASON
.-811, More than one row retrieved in SELECT INTO
.-811, ERROR: THE RESULT OF AN EMBEDDED SELECT STATEMENT OR A SUBSELECT
IN THE SET CLAUSE OF AN UPDATE STATEMENT IS A TABLE OF MORE THAN
ONE ROW, OR THE RESULT OF A SUBQUERY OF A BASIC PREDICATE IS MORE
THAN VALUE
.-818, Plan and program: timestamp mismatch
.-818, ERROR: THE PRECOMPILER-GENERATED TIMESTAMP IN THE LOAD MODULE IS
DIFFERENT FROM THE BIND TIMESTAMP BUILT FROM THE DBRM
.-904 SQLSTATE 57011, Unavailable resource. Someone is locking the data
you need you may choose to terminate the program
.-904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN UNAVAILABLE RESOURCE.
REASON , TYPE OF RESOURCE , AND RESOURCE NAME
.-911 SQLSTATE 40000, Deadlock or timeout. Rollback has been done.
.-911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN ROLLED BACK DUE TO DEADLOCK
OR TIMEOUT. REASON, TYPE OF RESOURCE, AND RESOURCE NAME
.-913 SQLSTATE 40502, Your program was the victim of a deadlock or timeout.
NO rollback has been done. You should do a ROLLBACK.
.-913, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR TIMEOUT.
REASON CODE , TYPE OF RESOURCE , AND RESOURCE NAME
.-922, Authorization needed
.-922, ERROR: AUTHORIZATION FAILURE: ERROR. REASON
.-927, The language interface was called but no connection had been made.
Execute the program with the DSN command.
All the sqlcodes from -991 to +883 in DB2 Version 7.
.-927, ERROR: THE LANGUAGE INTERFACE (LI) WAS CALLED WHEN THE CONNECTING
ENVIRONMENT WAS NOT ESTABLISHED. THE PROGRAM SHOULD BE INVOKED
UNDER THE DSN COMMAND
.-991, ERROR: CALL ATTACH WAS UNABLE TO ESTABLISH AN IMPLICIT CONNECT OR OPEN TO DB2. RC1= RC2=
.-981, ERROR: THE SQL STATEMENT FAILED BECAUSE THE RRSAF CONNECTION IS
NOT IN A STATE THAT ALLOWS SQL OPERATIONS, REASON
.-950, ERROR: THE LOCATION NAME SPECIFIED IN THE CONNECT STATEMENT IS
INVALID OR NOT LISTED IN THE COMMUNICATIONS DATABASE
.-948, ERROR: DISTRIBUTED OPERATION IS INVALID
.-947, ERROR: THE SQL STATEMENT FAILED BECAUSE IT WILL CHANGE A TABLE
DEFINED WITH DATA CAPTURE CHANGES, BUT THE DATA CANNOT BE PROPAGATED
.-939, ERROR: ROLLBACK REQUIRED DUE TO UNREQUESTED ROLLBACK OF A REMOTE SERVER
.-929, ERROR: FAILURE IN A CHANGED DATA CAPTURE EXIT:
.-926, ERROR: ROLLBACK NOT VALID IN IMS OR CICS ENVIRONMENT
.-925, ERROR: COMMIT NOT VALID IN IMS OR CICS ENVIRONMENT
.-924, ERROR: DB2 CONNECTION INTERNAL ERROR, , ,
. 923, ERROR: CONNECTION NOT ESTABLISHED: DB2 , REASON , TYPE , NAME
.-919, ERROR: A ROLLBACK OPERATION IS REQUIRED
.-918, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE A CONNECTION HAS BEEN LOST
.-917, ERROR: BIND PACKAGE FAILED
.-910, ERROR: THE SQL STATEMENT CANNOT ACCESS AN OBJECT ON WHICH A DROP OR ALTER IS PENDING
.-909, ERROR: THE OBJECT HAS BEEN DELETED OR ALTERED
.-908, ERROR: ERROR USING AUTHORITY. BIND, REBIND, OR AUTO-REBIND OPERATION IS NOT ALLOWED
.-906, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THIS FUNCTION IS DISABLED DUE TO A PRIOR ERROR
.-905, ERROR: UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED,
RESOURCE NAME = LIMIT = CPU SECONDS ( SERVICE UNITS) DERIVED FROM
.-902, ERROR: POINTER TO ESSENTIAL CONTROL BLOCK(RDA/CT) HAS VALUE 0, REBIND REQUIRED
.-901, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY A SYSTEM ERROR THAT DOES
NOT PRECLUDE THE SUCCESSFUL EXECUTION OF SUBSEQUENT SQL STATEMENTS
.-900, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE APPLICATION
PROCESS IS NOT CONNECTED TO AN APPLICATION SERVER
.-882, ERROR: SAVEPOINT DOES NOT EXIST
.-881, ERROR: A SAVEPOINT WITH NAME ALREADY EXISTS, BUT THIS SAVEPOINT NAME CANNOT BE REUSED
.-880, ERROR: SAVEPOINT DOES NOT EXIST OR IS INVALID IN THIS CONTEXT
.-879, ERROR: CREATE OR ALTER STATEMENT FOR CANNOT DEFINE A COLUMN, DISTINCT
TYPE, FUNCTION OR STORED PROCEDURE PARAMETER AS MIXED OR GRAPHIC WITH
ENCODING SCHEME
.-878, ERROR: THE PLAN_TABLE USED FOR EXPLAIN CANNOT BE ASCII
.-877, ERROR: CCSID ASCII IS NOT ALLOWED FOR THIS DATABASE OR TABLE SPACE
.-876, ERROR: CANNOT BE CREATED, REASON
.-875, ERROR: CANNOT BE USED WITH THE ASCII DATA REFERENCED
.-874, ERROR: THE ENCODING SCHEME SPECIFIED FOR THE MUST BE THE SAME AS
THE CONTAINING TABLE SPACE OR OTHER PARAMETERS
.-873, ERROR: DATA ENCODED WITH DIFFERENT CCSIDS CANNOT BE REFERENCED IN THE SAME SQL STATEMENT
.-872, ERROR: A VALID CCSID HAS NOT YET BEEN SPECIFIED FOR THIS SUBSYSTEM
.-870, ERROR: THE NUMBER OF HOST VARIABLES IN THE STATEMENT IS NOT EQUAL TO THE NUMBER OF DESCRIPTORS
.-867, ERROR: INVALID SPECIFICATION OF A ROWID COLUMN
.-846, ERROR: INVALID SPECIFICATION OF AN IDENTITY COLUMN
.-843, ERROR: THE SET CONNECTION OR RELEASE STATEMENT MUST SPECIFY AN EXISTING CONNECTION
.-842, ERROR: A CONNECTION TO ALREADY EXISTS
.-840, ERROR: TOO MANY ITEMS RETURNED IN A SELECT OR INSERT LIST
.-822, ERROR: THE SQLDA CONTAINS AN INVALID DATA ADDRESS OR INDICATOR VARIABLE ADDRESS
.-820, ERROR: THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE CONTAINS A VALUE THAT IS NOT VALID IN THIS RELEASE
.-819, ERROR: THE VIEW CANNOT BE PROCESSED BECAUSE THE LENGTH OF ITS PARSE TREE IN THE CATALOG IS ZERO
.-817, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE THE STATEMENT WILL RESULT IN A PROHIBITED UPDATE OPERATION
.-815, ERROR: A GROUP BY OR HAVING CLAUSE IS IMPLICITLY OR EXPLICITLY
SPECIFIED IN A SUBSELECT OF A BASIC PREDICATE OR A SET CLAUSE OF
AN UPDATE STATEMENT
.-812, ERROR: THE SQL STATEMENT CANNOT BE PROCESSED BECAUSE A BLANK COLLECTION-ID
WAS FOUND IN THE CURRENT PACKAGESET SPECIAL REGISTER WHILE TRYING TO FORM
A QUALIFIED PACKAGE NAME FOR PROGRAM USING PLAN
.-808, ERROR: THE CONNECT STATEMENT IS NOT CONSISTENT WITH THE FIRST CONNECT STATEMENT
.-807, ERROR: ACCESS DENIED: PACKAGE IS NOT ENABLED FOR ACCESS FROM
. 807, WARNING: THE RESULT OF DECIMAL MULTIPLICATION MAY CAUSE OVERFLOW
.-804, ERROR: AN ERROR WAS FOUND IN THE APPLICATION PROGRAM INPUT PARAMETERS FOR THE SQL STATEMENT, REASON
.-798, ERROR: YOU CANNOT INSERT A VALUE INTO A COLUMN THAT IS DEFINED WITH
THE OPTION GENERATED ALWAYS. COLUMN NAME
.-797, ERROR: ATTEMPT TO CREATE TRIGGER WITH AN UNSUPPORTED TRIGGERED SQL STATEMENT
.-771, ERROR: INVALID SPECIFICATION OF A ROWID COLUMN
.-770, ERROR: TABLE CANNOT HAVE A LOB COLUMN UNLESS IT ALSO HAS A ROWID COLUMN
.-769, ERROR: SPECIFICATION OF CREATE AUX TABLE DOES NOT MATCH THE CHARACTERISTICS OF THE BASE TABLE
.-768, ERROR: AN AUXILIARY TABLE ALREADY EXISTS FOR THE SPECIFIED COLUMN OR PARTITION
.-767, ERROR: MISSING OR INVALID COLUMN SPECIFICATION FOR INDEX
.-766, ERROR: THE OBJECT OF A STATEMENT IS AN AUXILIARY TABLE FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED
.-765, ERROR: TABLE IS NOT COMPATIBLE WITH DATABASE
.-764, ERROR: A LOB TABLE SPACE AND ITS ASSOCIATED BASE TABLE SPACE MUST BE IN THE SAME DATABASE
.-763, ERROR: INVALID TABLE SPACE NAME
.-752, ERROR: THE CONNECT STATEMENT IS INVALID BECAUSE THE PROCESS IS NOT IN THE CONNECTABLE STATE
.-751, ERROR: (SPECIFIC NAME ) ATTEMPTED TO EXECUTE AN SQL STATEMENT THAT IS NOT ALLOWED
.-750, ERROR: THE SOURCE TABLE CANNOT BE RENAMED BECAUSE IT IS REFERENCED IN EXISTING VIEW DEFINITIONS OR TRIGGER DEFINITIONS
.-748, ERROR: AN INDEX ALREADY EXISTS ON AUXILIARY TABLE
.-746, ERROR: THE SQL STATEMENT IN AN EXTERNAL FUNCTION, TRIGGER, OR IN STORED PROCEDURE VIOLATES THE NESTING SQL RESTRICTION
.-742, ERROR: DSNDB07 IS THE IMPLICIT WORK FILE DATABASE
.-741, ERROR: A DATABASE IS ALREADY DEFINED FOR MEMBER
.-740, ERROR: FUNCTION IS DEFINED WITH THE OPTION MODIFIES SQL DATA WHICH IS
NOT VALID IN THE CONTEXT IN WHICH IT WAS INVOKED
.-739, ERROR: ALTER FUNCTION FAILED BECAUSE FUNCTIONS CANNOT MODIFY DATA WHEN THEY ARE PROCESSED IN PARALLEL
.-737, ERROR: IMPLICIT TABLE SPACE NOT ALLOWED
.-736, ERROR: INVALID OBID SPECIFIED
.-735, ERROR: DATABASE CANNOT BE ACCESSED BECAUSE IT IS NO LONGER A SHARED DATABASE
.-734, ERROR: THE ROSHARE ATTRIBUTE OF A DATABASE CANNOT BE ALTERED FROM ROSHARE READ
.-733, ERROR: THE DESCRIPTION OF A TABLE SPACE, INDEX SPACE, OR TABLE IN A ROSHARE
READ DATABASE MUST BE CONSISTENT WITH ITS DESCRIPTION IN THE OWNER SYSTEM
.-732, ERROR: THE DATABASE IS DEFINED ON THIS SUBSYSTEM WITH THE ROSHARE READ
ATTRIBUTE BUT THE TABLE SPACE OR INDEX SPACE HAS NOT BEEN DEFINED ON THE
OWNING SUBSYSTEM
.-731, ERROR: USER-DEFINED DATASET MUST BE DEFINED WITH SHAREOPTIONS (1,3)
.-730, ERROR: THE PARENT OF A TABLE IN A READ-ONLY SHARED DATABASE MUST ALSO BE A TABLE IN A
READ-ONLY SHARED DATABASE
.-729, ERROR: A STORED PROCEDURE SPECIFYING COMMIT ON RETURN CANNOT BE THE TARGET OF
A NESTED CALL STATEMENT
.-728, ERROR: DATA TYPE IS NOT ALLOWED IN DB2 PRIVATE PROTOCOL PROCESSING
.-726, ERROR: BIND ERROR ATTEMPTING TO REPLACE PACKAGE =. THERE ARE ENABLE OR
DISABLE ENTRIES CURRENTLY ASSOCIATED WITH THE PACKAGE
.-725, ERROR: THE SPECIAL REGISTER AT LOCATION WAS SUPPLIED AN INVALID VALUE
.-724, ERROR: THE ACTIVATION OF THE OBJECT WOULD EXCEED THE MAXIMUM LEVEL OF INDIRECT SQL CASCADING
.-723, ERROR: AN ERROR OCCURRED IN A TRIGGERED SQL STATEMENT IN TRIGGER ,
SECTION NUMBER. INFORMATION RETURNED: SQLCODE , SQLSTATE , AND MESSAGE TOKENS
.-722, ERROR: ERROR USING AUTHORITY PACKAGE DOES NOT EXIST
.-721, ERROR: BIND ERROR FOR PACKAGE = CONTOKEN = ''X IS NOT UNIQUE SO IT CANNOT BE CREATED
.-720, ERROR: BIND ERROR, ATTEMPTING TO REPLACE PACKAGE = WITH VERSION = BUT THIS VERSION ALREADY EXISTS
.-719, ERROR: BIND ADD ERROR USING AUTHORITY PACKAGE ALREADY EXISTS
.-718, ERROR: REBIND OF PACKAGE FAILED BECAUSE IBMREQD OF IS INVALID
.-717, ERROR: FOR WITH MARK FAILED BECAUSE DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED
.-716, ERROR: PROGRAM PRECOMPILED WITH INCORRECT LEVEL FOR THIS RELEASE
.-715, ERROR: PROGRAM WITH MARK FAILED BECAUSE IT DEPENDS ON FUNCTIONS OF THE RELEASE FROM WHICH FALLBACK HAS OCCURRED
.-713, ERROR: THE REPLACEMENT VALUE FOR IS INVALID
.-697, ERROR: OLD OR NEW CORRELATION NAMES ARE NOT ALLOWED IN A TRIGGER DEFINED
WITH THE FOR EACH STATEMENT CLAUSE. OLD_TABLE OR NEW_TABLE NAMES ARE NOT
ALLOWED IN A TRIGGER WITH THE BEFORE CLAUSE
.-696, ERROR: THE DEFINITION OF TRIGGER INCLUDES AN INVALID USE OF CORRELATION NAME OR TRANSITION TABLE NAME . REASON CODE=
.-694, ERROR: THE DDL STATEMENT CANNOT BE EXECUTED BECAUSE A DROP IS PENDING ON THE DDL REGISTRATION TABLE
.-693, ERROR: THE COLUMN IN DDL REGISTRATION TABLE OR INDEX IS NOT DEFINED PROPERLY
.-692, ERROR: THE REQUIRED UNIQUE INDEX FOR DDL REGISTRATION TABLE DOES NOT EXIST
.-691, ERROR: THE REQUIRED REGISTRATION TABLE DOES NOT EXIST
.-690, ERROR: THE STATEMENT IS REJECTED BY DATA DEFINITION CONTROL SUPPORT. REASON
.-689, ERROR: TOO MANY COLUMNS DEFINED FOR A DEPENDENT TABLE
.-688, ERROR: INCORRECT DATA RETURNED FROM FIELD PROCEDURE, ,
.-687, ERROR: FIELD TYPES INCOMPARABLE
.-686, ERROR: COLUMN DEFINED WITH A FIELD PROCEDURE CAN NOT COMPARE WITH ANOTHER COLUMN WITH DIFFERENT FIELD PROCEDURE
.-685, ERROR: INVALID FIELD TYPE,
.-684, ERROR: THE LENGTH OF LITERAL LIST BEGINNING IS TOO LONG
.-683, ERROR: THE SPECIFICATION FOR COLUMN, DISTINCT TYPE, FUNCTION, OR PROCEDURE CONTAINS INCOMPATIBLE CLAUSES
.-682, ERROR: FIELD PROCEDURE COULD NOT BE LOADED
.-681, ERROR: COLUMN IN VIOLATION OF INSTALLATION DEFINED FIELD PROCEDURE RT: , RS: , MSG:
.-680, ERROR: TOO MANY COLUMNS SPECIFIED FOR A TABLE, VIEW, OR TABLE FUNCTION
.-679, ERROR: THE OBJECT CANNOT BE CREATED BECAUSE A DROP IS PENDING ON THE OBJECT
.-678, ERROR: THE LITERAL SPECIFIED FOR THE INDEX LIMIT KEY MUST CONFORM TO THE DATA
TYPE OF THE CORRESPONDING COLUMN
.-677, ERROR: INSUFFICIENT VIRTUAL STORAGE FOR BUFFERPOOL EXPANSION
.-676, ERROR: ONLY A 4K PAGE BUFFERPOOL CAN BE USED FOR AN INDEX
.-672, ERROR: OPERATION DROP NOT ALLOWED ON TABLE
.-671, ERROR: THE BUFFERPOOL ATTRIBUTE OF THE TABLE SPACE CANNOT BE ALTERED AS
SPECIFIED BECAUSE IT WOULD CHANGE THE PAGE SIZE OF THE TABLE SPACE
.-670, ERROR: THE RECORD LENGTH OF THE TABLE EXCEEDS THE PAGE SIZE LIMIT
.-669, ERROR: A TABLE IN A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED
.-668, ERROR: THE COLUMN CANNOT BE ADDED TO THE TABLE BECAUSE THE TABLE HAS AN EDIT PROCEDURE
.-667, ERROR: THE CLUSTERING INDEX FOR A PARTITIONED TABLE SPACE CANNOT BE EXPLICITLY DROPPED
.-666, ERROR: CANNOT BE EXECUTED BECAUSE IS IN PROGRESS
.-665, ERROR: THE PART CLAUSE OF AN ALTER STATEMENT IS OMITTED OR INVALID
.-663, ERROR: THE NUMBER OF KEY LIMIT VALUES IS EITHER ZERO, OR GREATER THAN THE
NUMBER OF COLUMNS IN THE KEY OF INDEX
.-662, ERROR: A PARTITIONED INDEX CANNOT BE CREATED ON A NON-PARTITIONED TABLE SPACE
.-661, ERROR: INDEX CANNOT BE CREATED ON PARTITIONED TABLE SPACE BECAUSE THE
NUMBER OF PART SPECIFICATIONS IS NOT EQUAL TO THE NUMBER OF PARTITIONS
OF THE TABLE SPACE
.-660, ERROR: INDEX CANNOT BE CREATED ON PARTITIONED TABLE SPACE BECAUSE KEY LIMITS ARE NOT SPECIFIED
.-658, ERROR: A CANNOT BE DROPPED USING THE STATEMENT
. 658, WARNING: THE SUBPAGES VALUE IS IGNORED FOR THE CATALOG INDEX
.-655, ERROR: THE CREATE OR ALTER STOGROUP IS INVALID BECAUSE THE STORAGE GROUP
WOULD HAVE BOTH SPECIFIC AND NON-SPECIFIC VOLUME IDS
. 655, WARNING: STOGROUP HAS BOTH SPECIFIC AND NONSPECIFIC VOLUME IDS. IT WILL NOT BE ALLOWED IN FUTURE RELEASES.
.-653, ERROR: TABLE IN PARTITIONED TABLE SPACE IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED
. 653, WARNING: TABLE IN PARTITIONED TABLE SPACE IS NOT AVAILABLE BECAUSE ITS PARTITIONED INDEX HAS NOT BEEN CREATED
.-652, ERROR: VIOLATION OF INSTALLATION DEFINED EDIT OR VALIDATION PROCEDURE
.-651, ERROR: TABLE DESCRIPTION EXCEEDS MAXIMUM SIZE OF OBJECT DESCRIPTOR
.-650, ERROR: THE ALTER INDEX CANNOT BE EXECUTED, REASON
. 650, WARNING: THE TABLE BEING CREATED OR ALTERED CAN NOT BECOME A DEPENDENT TABLE
.-647, ERROR: BUFFERPOOL CANNOT BE SPECIFIED BECAUSE IT HAS NOT BEEN ACTIVATED
.-646, ERROR: TABLE CANNOT BE CREATED IN SPECIFIED TABLE SPACE BECAUSE IT ALREADY CONTAINS A TABLE
.-644, ERROR: INVALID VALUE SPECIFIED FOR KEYWORD IN STATEMENT
.-643, ERROR: CHECK CONSTRAINT EXCEEDS MAXIMUM ALLOWABLE LENGTH
.-642, ERROR: TOO MANY COLUMNS IN UNIQUE CONSTRAINTS
.-640, ERROR: LOCKSIZE ROW CANNOT BE SPECIFIED BECAUSE TABLE IN THIS TABLESPACE HAS TYPE 1 INDEX
.-639, ERROR: 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
.-638, ERROR: TABLE CANNOT BE CREATED BECAUSE COLUMN DEFINITION IS MISSING
.-637, ERROR: DUPLICATE KEYWORD
.-636, ERROR: THE PARTITIONING KEYS FOR PARTITION ARE NOT SPECIFIED IN ASCENDING OR DESCENDING ORDER
.-635, ERROR: THE DELETE RULES CANNOT BE DIFFERENT OR CANNOT BE SET NULL
.-634, ERROR: THE DELETE RULE MUST NOT BE CASCADE
.-633, ERROR: THE DELETE RULE MUST BE
.-632, ERROR: THE TABLE CANNOT BE DEFINED AS A DEPENDENT OF BECAUSE OF DELETE RULE RESTRICTIONS
.-631, ERROR: FOREIGN KEY IS TOO LONG OR HAS TOO MANY COLUMNS
.-630, ERROR: THE WHERE NOT NULL SPECIFICATION IS INVALID FOR TYPE 1 INDEXES
.-629, ERROR: SET NULL CANNOT BE SPECIFIED BECAUSE FOREIGN KEY CANNOT CONTAIN NULL VALUES
.-628, ERROR: THE CLAUSES ARE MUTUALLY EXCLUSIVE
. 627, ERROR: THE ALTER STATEMENT IS INVALID BECAUSE THE PAGESET HAS USER-MANAGED DATA SETS
.-626, ERROR: THE ALTER STATEMENT IS NOT EXECUTABLE BECAUSE THE PAGE SET IS NOT STOPPED
. 626, WARNING: DROPPING THE INDEX TERMINATES ENFORCEMENT OF THE UNIQUENESS OF A KEY
THAT WAS DEFINED WHEN THE TABLE WAS CREATED
.-625, ERROR: TABLE DOES NOT HAVE AN INDEX TO ENFORCE THE UNIQUENESS OF THE PARENT KEY
. 625, WARNING: THE DEFINITION OF TABLE HAS BEEN CHANGED TO INCOMPLETE
.-624, ERROR: TABLE ALREADY HAS A PRIMARY KEY
.-623, ERROR: A CLUSTERING INDEX ALREADY EXISTS ON TABLE
.-622, ERROR: FOR MIXED DATA IS INVALID BECAUSE THE MIXED DATA INSTALL OPTION IS NO
.-621, ERROR: DUPLICATE DBID WAS DETECTED AND PREVIOUSLY ASSIGNED TO
.-620, ERROR: KEYWORD IN STATEMENT IS NOT PERMITTED FOR A SPACE IN THE DATABASE
.-619, ERROR: OPERATION DISALLOWED BECAUSE THE WORK FILE DATABASE IS NOT STOPPED
.-618, ERROR: OPERATION IS NOT ALLOWED ON SYSTEM DATABASES
.-617, ERROR: A TYPE 1 INDEX IS NOT VALID FOR TABLE
.-616, ERROR: CANNOT BE DROPPED BECAUSE IT IS REFERENCED BY
.-615, ERROR: IS NOT ALLOWED ON A PACKAGE IN USE
.-614, ERROR: THE INDEX CANNOT BE CREATED OR THE LENGTH OF THE COLUMN CANNOT BE
CHANGED BECAUSE THE SUM OF THE INTERNAL LENGTHS OF THE IDENTIFIED COLUMNS
IS GREATER THAN THE ALLOWABLE MAXIMUM
.-613, ERROR: THE PRIMARY KEY OR A UNIQUE CONSTRAINT IS TOO LONG OR HAS TOO MANY COLUMNS
.-612, ERROR: IS A DUPLICATE COLUMN NAME
.-611, ERROR: ONLY LOCKMAX 0 CAN BE SPECIFIED WHEN THE LOCK SIZE OF THE TABLESPACE IS TABLESPACE OR TABLE
.-607, ERROR: OPERATION OR OPTION IS NOT DEFINED FOR THIS OBJECT
.-604, ERROR: A DATA TYPE DEFINITION SPECIFIES AN INVALID LENGTH, PRECISION, OR SCALE ATTRIBUTE
.-603, ERROR: A UNIQUE INDEX CANNOT BE CREATED BECAUSE THE TABLE CONTAINS ROWS
WHICH ARE DUPLICATES WITH RESPECT TO THE VALUES OF THE IDENTIFIED COLUMNS
.-602, ERROR: TOO MANY COLUMNS SPECIFIED IN A CREATE INDEX
.-601, ERROR: THE NAME OF THE OBJECT TO BE CREATED OR THE TARGET OF A RENAME
STATEMENT IS IDENTICAL TO THE EXISTING NAME OF THE OBJECT TYPE
.-594, ERROR: ATTEMPT TO CREATE A NULLABLE ROWID OR DISTINCT TYPE COLUMN
.-593, ERROR: NOT NULL MUST BE SPECIFIED FOR ROWID OR DISTINCT TYPE COLUMN
- 592, ERROR: NOT AUTHORIZED TO CREATE FUNCTIONS OR PROCEDURES IN WLM ENVIRONMENT
.-590, ERROR: PARAMETER NAME IS NOT UNIQUE IN THE CREATE FOR ROUTINE
.-586, ERROR: THE TOTAL LENGTH OF THE CURRENT PATH SPECIAL REGISTER CANNOT EXCEED 254 CHARACTERS
.-585, ERROR: THE SCHEMA NAME CANNOT APPEAR MORE THAN ONCE IN THE CURRENT PATH
. 585, WARNING: THE SCHEMA NAME APPEARS MORE THAN ONCE IN THE CURRENT PATH
.-582, ERROR: THE SEARCH-CONDITION IN A SEARCHED-WHENCLAUSE CANNOT BE A QUANTIFIED
PREDICATE, IN PREDICATE, OR AN EXISTS PREDICATE
.-581, ERROR: THE DATA TYPES OF THE RESULT-EXPRESSIONS OF A CASE EXPRESSION ARE NOT COMPATIBLE
.-580, ERROR: THE RESULT-EXPRESSIONS OF A CASE EXPRESSION CANNOT ALL BE NULL
.-579, ERROR: ATTEMPTED TO READ DATA WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION
.-577, ERROR: ATTEMPTED TO MODIFY DATA WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION
.-574, ERROR: THE SPECIFIED DEFAULT VALUE OR IDENTITY ATTRIBUTE VALUE CONFLICTS WITH THE DEFINITION OF COLUMN
.-573, ERROR: TABLE DOES NOT HAVE A UNIQUE KEY WITH THE SPECIFIED COLUMN NAMES
.-571, ERROR: THE STATEMENT WOULD RESULT IN A MULTIPLE SITE UPDATE
.-567, ERROR: AUTHORIZATION ERROR USING AUTHORITY PACKAGE = PRIVILEGE =
.-559, ERROR: ALL AUTHORIZATION FUNCTIONS HAVE BEEN DISABLED
.-558, ERROR: INVALID CLAUSE OR COMBINATION OF CLAUSES ON A GRANT OR REVOKE
. 558, WARNING: THE WITH GRANT OPTION IS IGNORED
.-557, ERROR: INCONSISTENT GRANT/REVOKE KEYWORD. PERMITTED KEYWORDS ARE
.-556, ERROR: CANNOT HAVE THE PRIVILEGE REVOKED BY BECAUSE THE REVOKEE DOES NOT
POSSESS THE PRIVILEGE OR THE REVOKER DID NOT MAKE THE GRANT
.-555, ERROR: AN AUTHORIZATION ID CANNOT REVOKE A PRIVILEGE FROM ITSELF
.-554, ERROR: AN AUTHORIZATION ID CANNOT GRANT A PRIVILEGE TO ITSELF
.-553, ERROR: SPECIFIED IS NOT ONE OF THE VALID AUTHORIZATION IDS
. 552, WARNING: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
.-551, ERROR: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION
.-551, ERROR: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION ON OBJECT
. 551, WARNING: DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION ON OBJECT
.-549, ERROR: THE STATEMENT IS NOT ALLOWED FOR BECAUSE THE BIND OPTION DYNAMICRULES(RUN) IS NOT IN EFFECT FOR
.-548, ERROR: A CHECK CONSTRAINT THAT IS DEFINED WITH IS INVALID
.-546, ERROR: THE CHECK CONSTRAINT IS INVALID
.-545, ERROR: THE REQUESTED OPERATION IS NOT ALLOWED BECAUSE A ROW DOES NOT SATISFY THE CHECK CONSTRAINT
.-544, ERROR: THE CHECK CONSTRAINT SPECIFIED IN THE ALTER TABLE STATEMENT CANNOT
BE ADDED BECAUSE AN EXISTING ROW VIOLATES THE CHECK CONSTRAINT
.-543, ERROR: A ROW IN A PARENT TABLE CANNOT BE DELETED BECAUSE THE CHECK CONSTRAINT RESTRICTS THE DELETION
-542, ERROR: CANNOT BE A COLUMN OF A PRIMARY KEY, A UNIQUE CONSTRAINT, OR A PARENT KEY BECAUSE IT CAN CONTAIN NULL VALUES
.-540, ERROR: THE DEFINITION OF TABLE IS INCOMPLETE BECAUSE IT LACKS A PRIMARY INDEX OR A REQUIRED UNIQUE INDEX
.-539, ERROR: TABLE DOES NOT HAVE A PRIMARY KEY
.-538, ERROR: FOREIGN KEY DOES NOT CONFORM TO THE DESCRIPTION OF A PARENT KEY OF TABLE
.-537, ERROR: THE PRIMARY KEY CLAUSE, A FOREIGN KEY CLAUSE, OR A UNIQUE CLAUSE
IDENTIFIES COLUMN MORE THAN ONCE
.-536, ERROR: THE DELETE STATEMENT IS INVALID BECAUSE TABLE CAN BE AFFECTED BY THE OPERATION
.-534, ERROR: THE PRIMARY KEY CANNOT BE UPDATED BECAUSE OF MULTIPLE-ROW UPDATE
.-533, ERROR: INVALID MULTIPLE-ROW INSERT
.-531, ERROR: PARENT KEY IN A PARENT ROW CANNOT BE UPDATED BECAUSE IT HAS ONE OR MORE DEPENDENT ROWS IN RELATIONSHIP
.-526, ERROR: THE REQUESTED OPERATION OR USAGE DOES NOT APPLY TO TEMPORARY TABLE
.-525, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT WAS IN ERROR AT BIND
TIME FOR SECTION = PACKAGE = CONSISTENCY TOKEN = X''
.-519, ERROR: THE PREPARE STATEMENT IDENTIFIES THE SELECT STATEMENT OF THE OPENED CURSOR
.-518, ERROR: THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED STATEMENT
.-517, ERROR: CURSOR CANNOT BE USED BECAUSE ITS STATEMENT NAME DOES NOT IDENTIFY A PREPARED SELECT STATEMENT
.-516, ERROR: THE DESCRIBE FOR STATIC STATEMENT DOES NOT IDENTIFY A PREPARED STATEMENT
.-514, ERROR: THE CURSOR IS NOT IN A PREPARED STATE
.-513, ERROR: THE ALIAS MUST NOT BE DEFINED ON ANOTHER LOCAL OR REMOTE ALIAS
.-512, ERROR: STATEMENT REFERENCE TO REMOTE OBJECT IS INVALID
.-511, ERROR: THE FOR UPDATE CLAUSE CANNOT BE SPECIFIED BECAUSE THE TABLE DESIGNATED BY THE CURSOR CANNOT BE MODIFIED
.-510, ERROR: THE TABLE DESIGNATED BY THE CURSOR OF THE UPDATE OR DELETE STATEMENT CANNOT BE MODIFIED
.-509, ERROR: THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT THE SAME TABLE DESIGNATED BY THE CURSOR
.-508, ERROR: THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT POSITIONED ON A ROW
.-507, ERROR: THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT OPEN
.-504, ERROR: THE CURSOR NAME IS NOT DEFINED
.-500, ERROR: THE IDENTIFIED CURSOR WAS CLOSED WHEN THE CONNECTION WAS DESTROYED
.-499, ERROR: CURSOR HAS ALREADY BEEN ASSIGNED TO THIS OR ANOTHER RESULT SET FROM PROCEDURE
.-497, ERROR: THE MAXIMUM LIMIT OF INTERNAL IDENTIFIERS HAS BEEN EXCEEDED FOR DATABASE
.-496, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED BECAUSE IT REFERENCES A RESULT SET
THAT WAS NOT CREATED BY THE CURRENT SERVER
.-495, ERROR: ESTIMATED PROCESSOR COST OF PROCESSOR SECONDS ( SERVICE UNITS) IN COST
CATEGORY EXCEEDS A RESOURCE LIMIT ERROR THRESHOLD OF SERVICE UNITS
.-492, ERROR: THE CREATE FUNCTION FOR HAS A PROBLEM WITH PARAMETER NUMBER . IT MAY
INVOLVE A MISMATCH WITH A SOURCE FUNCTION
.-491, ERROR: CREATE STATEMENT FOR USER-DEFINED FUNCTION MUST HAVE A RETURNS CLAUSE, AND
EITHER THE EXTERNAL CLAUSE (WITH OTHER REQUIRED KEYWORDS) OR THE SOURCE CLAUSE
.-490, ERROR: NUMBER DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF
ALLOWABLE VALUES IN THIS CONTEXT (, )
.-487, ERROR: ATTEMPTED TO EXECUTE AN SQL STATEMENT WHEN THE DEFINITION OF THE FUNCTION OR PROCEDURE DID NOT SPECIFY THIS ACTION
.-483, ERROR: IN CREATE FUNCTION FOR STATEMENT, THE NUMBER OF PARAMETERS DOES NOT MATCH THE NUMBER OF PARAMETERS OF THE SOURCE FUNCTION
.-480, ERROR: THE PROCEDURE HAS NOT YET BEEN CALLED
.-478, ERROR: DROP OR REVOKE ON OBJECT TYPE CANNOT BE PROCESSED BECAUSE OBJECT OF TYPE IS DEPENDENT ON IT
.-476, ERROR: REFERENCE TO FUNCTION WAS NAMED WITHOUT A SIGNATURE, BUT THE FUNCTION IS NOT UNIQUE WITHIN ITS SCHEMA
.-475, ERROR: THE RESULT TYPE OF THE SOURCE FUNCTION CANNOT BE CAST TO THE RETURNS TYPE OF THE USER-DEFINED FUNCTION
.-473, ERROR: A USER DEFINED DATA TYPE CANNOT BE CALLED THE SAME NAME AS A SYSTEM PREDEFINED TYPE (BUILT-IN TYPE)
.-472, ERROR: CURSOR WAS LEFT OPEN BY EXTERNAL FUNCTION (SPECIFIC NAME )
.-471, ERROR: INVOCATION OF FUNCTION OR PROCEDURE FAILED DUE TO REASON
.-470, ERROR: SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT PARAMETER , BUT THE
STORED PROCEDURE DOES NOT SUPPORT NULL VALUES
.-469, ERROR: SQL CALL STATEMENT MUST SPECIFY AN OUTPUT HOST VARIABLE FOR PARAMETER
.-463, ERROR: EXTERNAL FUNCTION (SPECIFIC NAME ) HAS RETURNED AN INVALID SQLSTATE, WITH DIAGNOSTIC TEXT
.-461, ERROR: A VALUE WITH DATA TYPE CANNOT BE CAST TO TYPE
.-458, ERROR: IN A REFERENCE TO FUNCTION BY SIGNATURE, A MATCHING FUNCTION COULD NOT BE FOUND
.-457, ERROR: A FUNCTION OR DISTINCT TYPE CANNOT BE CALLED SINCE IT IS RESERVED FOR SYSTEM USE
.-456, ERROR: IN CREATE FUNCTION FOR , THE SPECIFIC NAME ALREADY EXISTS IN THE SCHEMA
.-455, ERROR: IN CREATE FUNCTION FOR , THE SCHEMA NAME PROVIDED FOR THE SPECIFIC NAME DOES NOT MATCH THE SCHEMA NAME OF THE FUNCTION
.-454, ERROR: THE SIGNATURE PROVIDED IN THE CREATE FUNCTION STATEMENT FOR MATCHES
THE SIGNATURE OF SOME OTHER FUNCTION ALREADY EXISTING IN THE SCHEMA
.-453, ERROR: THERE IS A PROBLEM WITH THE RETURNS CLAUSE IN THE CREATE FUNCTION STATEMENT FOR
.-451, ERROR: THE DEFINITION, IN THE CREATE FUNCTION FOR CONTAINS DATA TYPE
WHICH IS NOT APPROPRIATE FOR AN EXTERNAL FUNCTION WRITTEN IN THE GIVEN LANGUAGE
.-450, ERROR: USER-DEFINED FUNCTION OR STORED PROCEDURE , PARAMETER NUMBER , OVERLAYED STORAGE BEYOND ITS DECLARED LENGTH
.-449, ERROR: CREATE OR ALTER STATEMENT FOR FUNCTION OR PROCEDURE CONTAINS AN INVALID
FORMAT OF THE EXTERNAL NAME CLAUSE OR IS MISSING THE EXTERNAL NAME CLAUSE
.-444, ERROR: USER PROGRAM COULD NOT BE FOUND
.-443, ERROR: EXTERNAL FUNCTION (SPECIFIC NAME ) HAS RETURNED AN ERROR SQLSTATE WITH DIAGNOSTIC TEXT
.-441, ERROR: INVALID USE OF 'DISTINCT' OR 'ALL' WITH SCALAR FUNCTION
.-440, ERROR: NO BY THE NAME HAVING COMPATIBLE ARGUMENTS WAS FOUND IN THE CURRENT PATH
.-438, ERROR: APPLICATION RAISED ERROR WITH DIAGNOSTIC TEXT:
.-435, ERROR: AN INVALID SQLSTATE IS SPECIFIED IN THE FUNCTION RAISE_ERROR OR IN A SIGNAL SQLSTATE STATEMENT
.-433, ERROR: VALUE IS TOO LONG
.-430, ERROR: (SPECIFIC NAME ) HAS ABNORMALLY TERMINATED
.-427, ERROR: DYNAMIC ROLLBACK NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED
.-426, ERROR: DYNAMIC COMMIT NOT VALID AT AN APPLICATION SERVER WHERE UPDATES ARE NOT ALLOWED
.-423, ERROR: INVALID VALUE FOR LOCATOR IN POSITION
.-421, ERROR: THE OPERANDS OF A UNION OR UNION ALL DO NOT HAVE THE SAME NUMBER OF COLUMNS
.-420, ERROR: THE VALUE OF A CHARACTER STRING ARGUMENT WAS NOT ACCEPTABLE TO THE FUNCTION
.-419, ERROR: A DECIMAL DIVIDE OPERATION IS INVALID BECAUSE THE RESULT WOULD HAVE A NEGATIVE SCALE
.-418, ERROR: A STATEMENT STRING TO BE PREPARED CONTAINS AN INVALID USE OF PARAMETER MARKERS
.-417, ERROR: A STATEMENT STRING TO BE PREPARED INCLUDES PARAMETER MARKERS AS THE OPERANDS OF THE SAME OPERATOR
.-416, ERROR: AN OPERAND OF A UNION CONTAINS A LONG STRING COLUMN
.-415, ERROR: THE CORRESPONDING COLUMNS, , OF THE OPERANDS OF A UNION OR A UNION
ALL DO NOT HAVE COMPARABLE COLUMN DESCRIPTIONS
.-414, ERROR: A LIKE PREDICATE IS INVALID BECAUSE THE FIRST OPERAND IS NOT A STRING
.-413, ERROR: OVERFLOW OCCURRED DURING NUMERIC DATA TYPE CONVERSION
.-412, ERROR: THE SELECT CLAUSE OF A SUBQUERY SPECIFIES MULTIPLE COLUMNS
.-411, ERROR: CURRENT SQLID CANNOT BE USED IN A STATEMENT THAT REFERENCES REMOTE OBJECTS
.-410, ERROR: THE FLOATING POINT LITERAL CONTAINS MORE THAN 30 CHARACTERS
.-409, ERROR: INVALID OPERAND OF A COUNT FUNCTION
.-408, ERROR: THE VALUE IS NOT COMPATIBLE WITH THE DATA TYPE OF ITS TARGET
.-407, ERROR: AN UPDATE, INSERT, OR SET VALUE IS NULL, BUT THE OBJECT COLUMN CANNOT CONTAIN NULL VALUES
.-406, ERROR: A CALCULATED OR DERIVED NUMERIC VALUE IS NOT WITHIN THE RANGE OF ITS OBJECT COLUMN
.-405, ERROR: THE NUMERIC LITERAL CANNOT BE USED AS SPECIFIED BECAUSE IT IS OUT OF RANGE
.-404, ERROR: THE SQL STATEMENT SPECIFIES A STRING THAT IS TOO LONG
.-402, ERROR: AN ARITHMETIC FUNCTION OR OPERATOR IS APPLIED TO CHARACTER OR DATETIME DATA
.-401, ERROR: THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT COMPARABLE
.-400, ERROR: THE CATALOG HAS THE MAXIMUM NUMBER OF USER DEFINED INDEXES
.-399, ERROR: ATTEMPTED TO INSERT AN INVALID VALUE INTO A ROWID COLUMN
.-398, ERROR: A LOCATOR WAS REQUESTED FOR HOST VARIABLE NUMBER BUT THE VARIABLE IS NOT A LOB
.-397, ERROR: THE OPTION GENERATED IS SPECIFIED WITH A COLUMN THAT IS NOT A ROW ID OR DISTINCT TYPE BASED ON A ROW ID
.-396, ERROR: ATTEMPTED TO EXECUTE AN SQL STATEMENT DURING FINAL CALL PROCESSING
.-392, ERROR: SQLDA PROVIDED FOR CURSOR HAS BEEN CHANGED FROM THE PREVIOUS FETCH
.-390, ERROR: THE FUNCTION NAME , SPECIFIC NAME , IS NOT VALID IN THE CONTEXT IN WHICH IT OCCURS
.-373, ERROR: DEFAULT CANNOT BE SPECIFIED FOR IDENTITY COLUMN
.-372, ERROR: ONLY ONE ROWID OR IDENTITY COLUMN IS ALLOWED IN A TABLE
.-359, ERROR: THE RANGE OF VALUES FOR THE IDENTITY COLUMN IS EXHAUSTED
.-355, ERROR: A LOB COLUMN IS TOO LARGE TO BE LOGGED
.-352, ERROR: AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION OF THE INPUT-LIST
.-351, ERROR: AN UNSUPPORTED SQLTYPE WAS ENCOUNTERED IN POSITION OF THE SELECT-LIST
.-350, ERROR: INVALID SPECIFICATION OF A LARGE OBJECT COLUMN
.-339, ERROR: THE SQL STATEMENT CANNOT BE EXECUTED FROM AN ASCII BASED DRDA APPLICATION REQUESTOR TO A V2R2 DB2 SUBSYSTEM
.-338, ERROR: AN ON CLAUSE IS INVALID
.-333, ERROR: THE SUBTYPE OF A STRING VARIABLE IS NOT THE SAME AS THE SUBTYPE
KNOWN AT BIND TIME AND THE DIFFERENCE CANNOT BE RESOLVED BY TRANSLATION
.-332, ERROR: SYSSTRINGS DOES NOT DEFINE A TRANSLATION FROM CCSID TO
.-331, ERROR: A STRING CANNOT BE ASSIGNED TO A HOST VARIABLE BECAUSE IT CANNOT
BE TRANSLATED. REASON , CHARACTER , POSITION
. 331, WARNING: THE NULL VALUE HAS BEEN ASSIGNED TO A HOST VARIABLE BECAUSE THE
STRING CANNOT BE TRANSLATED. REASON , CHARACTER , HOST VARIABLE
.-330, ERROR: A STRING CANNOT BE USED BECAUSE IT CANNOT BE TRANSLATED. REASON, CHARACTER , HOST VARIABLE
.-327, ERROR: THE ROW CANNOT BE INSERTED BECAUSE IT IS OUTSIDE THE BOUND OF THE PARTITION RANGE FOR THE LAST PARTITION
.-314, ERROR: THE STATEMENT CONTAINS AN AMBIGUOUS HOST VARIABLE REFERENCE
.-313, ERROR: THE NUMBER OF HOST VARIABLES SPECIFIED IS NOT EQUAL TO THE NUMBER OF PARAMETER MARKERS
.-312, ERROR: IS AN UNDEFINED OR UNUSABLE HOST VARIABLE OR IS USED IN A DYNAMIC SQL STATEMENT OR A TRIGGER DEFINITION
.-310, ERROR: DECIMAL HOST VARIABLE OR PARAMETER CONTAINS NON-DECIMAL DATA
.-309, ERROR: A PREDICATE IS INVALID BECAUSE A REFERENCED HOST VARIABLE HAS THE NULL VALUE
.-303, ERROR: A VALUE CANNOT BE ASSIGNED TO OUTPUT HOST VARIABLE NUMBER BECAUSE THE DATA TYPES ARE NOT COMPARABLE
.-302, ERROR: THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE
.-301, ERROR: THE VALUE OF INPUT HOST VARIABLE OR PARAMETER NUMBER CANNOT BE USED AS SPECIFIED BECAUSE OF ITS DATA TYPE
.-300, ERROR: THE STRING CONTAINED IN HOST VARIABLE OR PARAMETER IS NOT NUL-TERMINATED
.-251, ERROR: TOKEN IS NOT VALID
.-250, ERROR: THE LOCAL LOCATION NAME IS NOT DEFINED WHEN PROCESSING A THREE-PART OBJECT NAME
.-240, ERROR: THE PART CLAUSE OF A LOCK TABLE STATEMENT IS INVALID
.-221, ERROR: "SET OF OPTIONAL COLUMNS" IN EXPLANATION TABLE IS INCOMPLETE.
OPTIONAL COLUMN IS MISSING
.-220, ERROR: THE COLUMN IN EXPLANATION TABLE IS NOT DEFINED PROPERLY
. 220, WARNING: THE COLUMN IN EXPLANATION TABLE IS NOT DEFINED PROPERLY
.-219, ERROR: THE REQUIRED EXPLANATION TABLE DOES NOT EXIST
. 219, WARNING: THE REQUIRED EXPLANATION TABLE DOES NOT EXIST
.-214, ERROR: AN EXPRESSION STARTING WITH IN THE CLAUSE IS NOT VALID. REASON CODE =
.-212, ERROR: IS SPECIFIED MORE THAN ONCE IN THE REFERENCING CLAUSE OF A TRIGGER DEFINITION
.-208, ERROR: THE ORDER BY CLAUSE IS INVALID BECAUSE COLUMN IS NOT PART OF THE RESULT TABLE
.-203, ERROR: A REFERENCE TO COLUMN IS AMBIGUOUS
. 203, WARNING: THE QUALIFIED COLUMN NAME WAS RESOLVED USING A NON-UNIQUE OR UNEXPOSED NAME
.-199, ERROR: ILLEGAL USE OF KEYWORD , TOKEN WAS EXPECTED
.-198, ERROR: THE OPERAND OF THE PREPARE OR EXECUTE IMMEDIATE STATEMENT IS BLANK OR EMPTY
.-197, ERROR: QUALIFIED COLUMN NAMES IN ORDER BY CLAUSE NOT PERMITTED WHEN UNION OR UNION ALL SPECIFIED
.-191, ERROR: A STRING CANNOT BE USED BECAUSE IT IS INVALID MIXED DATA
.-190, ERROR: ATTRIBUTES OF COLUMN IN TABLE ARE NOT COMPATIBLE WITH THE EXISTING COLUMN
.-189, ERROR: CCSID IS UNKNOWN OR INVALID FOR THE DATA TYPE OR SUBTYPE
.-188, ERROR: THE STRING REPRESENTATION OF A NAME IS INVALID
.-187, ERROR: 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
.-186, ERROR: THE LOCAL DATE LENGTH OR LOCAL TIME LENGTH HAS BEEN INCREASED
AND EXECUTING PROGRAM RELIES ON THE OLD LENGTH
.-185, ERROR: THE LOCAL FORMAT OPTION HAS BEEN USED WITH A DATE OR TIME AND NO LOCAL EXIT HAS BEEN INSTALLED
.-184, ERROR: AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE CONTAINS A PARAMETER MARKER
.-183, ERROR: AN ARITHMETIC OPERATION ON A DATE OR TIMESTAMP HAS A RESULT THAT IS NOT WITHIN THE VALID RANGE OF DATES
.-182, ERROR: AN ARITHMETIC EXPRESSION WITH A DATETIME VALUE IS INVALID
.-173, ERROR: UR IS SPECIFIED ON THE WITH CLAUSE BUT THE CURSOR IS NOT READ-ONLY
.-171, ERROR: THE DATA TYPE, LENGTH, OR VALUE OF ARGUMENT OF IS INVALID
.-170, ERROR: THE NUMBER OF ARGUMENTS SPECIFIED FOR IS INVALID
.-164, ERROR: DOES NOT HAVE THE PRIVILEGE TO CREATE A VIEW WITH QUALIFICATION
.-161, ERROR: THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW DOES NOT SATISFY THE VIEW DEFINITION
.-160, ERROR: THE WITH CHECK OPTION CANNOT BE USED FOR THE SPECIFIED VIEW
.-159, ERROR: DROP OR COMMENT ON IDENTIFIES A(N) RATHER THAN A(N)
.-158, ERROR: THE NUMBER OF COLUMNS SPECIFIED FOR THE VIEW IS NOT THE SAME AS THE
NUMBER OF COLUMNS SPECIFIED BY THE SELECT CLAUSE, OR THE NUMBER OF COLUMNS
SPECIFIED IN THE CORRELATION CLAUSE IN A FROM CLAUSE IS NOT THE SAME AS THE
NUMBER OF COLUMNS IN THE CORRESPONDING TABLE, VIEW, TABLE EXPRESSION, OR
TABLE FUNCTION
.-157, ERROR: ONLY A TABLE NAME CAN BE SPECIFIED IN A FOREIGN KEY CLAUSE. IS NOT THE NAME OF A TABLE
.-156, ERROR: THE STATEMENT DOES NOT IDENTIFY A TABLE
.-154, ERROR: THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION IS NOT VALID
.-153, ERROR: THE STATEMENT IS INVALID BECAUSE THE VIEW OR TABLE DEFINITION DOES NOT INCLUDE A UNIQUE NAME FOR EACH COLUMN
.-152, ERROR: THE DROP CLAUSE IN THE ALTER STATEMENT IS INVALID BECAUSE IS A
.-151, ERROR: THE UPDATE STATEMENT IS INVALID BECAUSE THE CATALOG DESCRIPTION OF COLUMN INDICATES THAT IT CANNOT BE UPDATED
.-150, ERROR: THE OBJECT OF THE INSERT, DELETE, OR UPDATE STATEMENT IS A VIEW OR
TRANSITION TABLE FOR WHICH THE REQUESTED OPERATION IS NOT PERMITTED
.-148, ERROR: THE SOURCE TABLE CANNOT BE RENAMED OR ALTERED
.-147, ERROR: ALTER FUNCTION FAILED BECAUSE SOURCE FUNCTIONS CANNOT BE ALTERED
.-144, ERROR: INVALID SECTION NUMBER
.-142, ERROR: THE SQL STATEMENT IS NOT SUPPORTED
.-138, ERROR: THE SECOND OR THIRD ARGUMENT OF THE SUBSTR FUNCTION IS OUT OF RANGE
.-137, ERROR: THE LENGTH RESULTING FROM IS GREATER THAN
.-136, ERROR: SORT CANNOT BE EXECUTED BECAUSE THE SORT KEY LENGTH IS GREATER THAN 4000 BYTES
.-134, ERROR: IMPROPER USE OF LONG STRING COLUMN OR AN EXPRESSION OF MAXIMUM LENGTH GREATER THAN 255
.-133, ERROR: A COLUMN FUNCTION IN A SUBQUERY OF A HAVING CLAUSE IS INVALID
BECAUSE ALL COLUMN REFERENCES IN ITS ARGUMENT ARE NOT CORRELATED TO THE
GROUP BY RESULT THAT THE HAVING CLAUSE IS APPLIED TO
.-132, ERROR: AN OPERAND OF IS NOT VALID
.-131, ERROR: STATEMENT WITH LIKE PREDICATE HAS INCOMPATIBLE DATA TYPES
.-130, ERROR: THE ESCAPE CLAUSE CONSISTS OF MORE THAN ONE CHARACTER, OR THE STRING
PATTERN CONTAINS AN INVALID OCCURRENCE OF THE ESCAPE CHARACTER
.-129, ERROR: THE STATEMENT CONTAINS TOO MANY TABLE NAMES
.-128, ERROR: INVALID USE OF NULL IN A PREDICATE
.-127, ERROR: DISTINCT IS SPECIFIED MORE THAN ONCE IN A SUBSELECT
.-126, ERROR: THE SELECT STATEMENT CONTAINS BOTH AN UPDATE CLAUSE AND AN ORDER BY CLAUSE
.-125, ERROR: AN INTEGER IN THE ORDER BY CLAUSE DOES NOT IDENTIFY A COLUMN OF THE RESULT
.-123, ERROR: THE PARAMETER IN POSITION IN THE FUNCTION MUST BE A CONSTANT OR KEYWORD
.-122, ERROR: 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 THE SELECT CLAUSE BUT NOT IN THE GROUP BY CLAUSE
.-121, ERROR: THE COLUMN IS IDENTIFIED MORE THAN ONCE IN THE INSERT OR UPDATE OR SET TRANSITION VARIABLE STATEMENT
.-120, ERROR: A WHERE CLAUSE, SET CLAUSE, VALUES CLAUSE, OR A SET ASSIGNMENT STATEMENT INCLUDES A COLUMN FUNCTION
.-119, ERROR: A COLUMN IDENTIFIED IN A HAVING CLAUSE IS NOT INCLUDED IN THE GROUP BY CLAUSE
.-118, ERROR: THE OBJECT TABLE OR VIEW OF THE DELETE OR UPDATE STATEMENT IS ALSO IDENTIFIED IN A FROM CLAUSE
.-115, ERROR: A PREDICATE IS INVALID BECAUSE THE COMPARISON OPERATOR IS FOLLOWED
BY A PARENTHESIZED LIST OR BY ANY OR ALL WITHOUT A SUBQUERY
.-114, ERROR: THE LOCATION NAME DOES NOT MATCH THE CURRENT SERVER
.-113, ERROR: INVALID CHARACTER FOUND IN: . REASON CODE
.-112, ERROR: THE OPERAND OF A COLUMN FUNCTION IS ANOTHER COLUMN FUNCTION
.-111, ERROR: A COLUMN FUNCTION DOES NOT INCLUDE A COLUMN NAME
. 111, WARNING: THE SUBPAGES OPTION IS NOT SUPPORTED FOR TYPE 2 INDEXES
.-110, ERROR: INVALID HEXADECIMAL LITERAL BEGINNING
. 110, WARNING: SQL UPDATE TO A DATA CAPTURE TABLE NOT SIGNALED TO ORIGINATING SUBSYSTEM
.-109, ERROR: CLAUSE IS NOT PERMITTED
.-108, ERROR: THE NAME IS QUALIFIED INCORRECTLY
.-107, ERROR: THE NAME IS TOO LONG. MAXIMUM ALLOWABLE SIZE IS
.-105, ERROR: INVALID STRING
.-104, ERROR: ILLEGAL SYMBOL "". SOME SYMBOLS THAT MIGHT BE LEGAL ARE:
.-103, ERROR: IS AN INVALID NUMERIC LITERAL
.-101, ERROR: THE STATEMENT IS TOO LONG OR TOO COMPLEX
.-097, ERROR: THE USE OF LONG VARCHAR OR LONG VARGRAPHIC IS NOT ALLOWED IN THIS CONTEXT
.-084, ERROR: UNACCEPTABLE SQL STATEMENT
.-079, ERROR: QUALIFIER FOR DECLARED GLOBAL TEMPORARY TABLE OR INDEX MUST BE SESSION, NOT
.-060, ERROR: INVALID SPECIFICATION :
.-029, ERROR: INTO CLAUSE REQUIRED
.-010, ERROR: THE STRING CONSTANT BEGINNING IS NOT TERMINATED
.-007, ERROR: STATEMENT CONTAINS THE ILLEGAL CHARACTER
. 000, SUCCESSFUL EXECUTION
. 012, WARNING: THE UNQUALIFIED COLUMN NAME WAS INTERPRETED AS A CORRELATED REFERENCE
. 098, WARNING: A DYNAMIC SQL STATEMENT ENDS WITH A SEMICOLON
. 162, WARNING: TABLE SPACE . HAS BEEN PLACED IN CHECK PENDING
. 218, WARNING: THE SQL STATEMENT REFERENCING A REMOTE OBJECT CANNOT BE EXPLAINED
. 236, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED FOR COLUMNS
. 237, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED BECAUSE AT LEAST
ONE OF THE COLUMNS BEING DESCRIBED IS A DISTINCT TYPE
. 238, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT SQLVAR ENTRIES ARE NEEDED
FOR COLUMNS BECAUSE AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A LOB
. 239, WARNING: SQLDA INCLUDES SQLVAR ENTRIES, BUT ARE REQUIRED FOR COLUMNS BECAUSE
AT LEAST ONE OF THE COLUMNS BEING DESCRIBED IS A DISTINCT TYPE
. 339, WARNING: THE SQL STATEMENT HAS BEEN SUCCESSFULLY EXECUTED BUT THERE MAY BE
SOME CHARACTER CONVERSION INCONSISTENCIES
. 394, WARNING: USER SPECIFIED OPTIMIZATION HINTS USED DURING ACCESS PATH SELECTION
. 395, WARNING: USER SPECIFIED OPTIMIZATION HINTS ARE INVALID (REASON CODE = '').
THE OPTIMIZATION HINTS ARE IGNORED
. 402, WARNING: LOCATION IS UNKNOWN
. 403, WARNING: THE LOCAL OBJECT REFERENCED BY THE CREATE ALIAS STATEMENT DOES NOT EXIST
. 434, WARNING: OPTION IS A DEPRECATED FEATURE
. 445, WARNING: VALUE HAS BEEN TRUNCATED
. 462, WARNING: EXTERNAL FUNCTION OR PROCEDURE (SPECIFIC NAME ) HAS RETURNED A
WARNING SQLSTATE, WITH DIAGNOSTIC TEXT
. 464, WARNING: PROCEDURE RETURNED QUERY RESULT SETS, WHICH EXCEEDS THE DEFINED LIMIT
. 466, WARNING: PROCEDURE RETURNED QUERY RESULT SETS
. 494, WARNING: NUMBER OF RESULT SETS IS GREATER THAN NUMBER OF LOCATORS
. 495, WARNING: ESTIMATED PROCESSOR COST OF PROCESSOR SECONDS ( SERVICE UNITS) IN
COST CATEGORY EXCEEDS A RESOURCE LIMIT WARNING THRESHOLD OF SERVICE UNITS
. 535, WARNING: THE RESULT OF THE POSITIONED UPDATE OR DELETE MAY DEPEND ON THE
ORDER OF THE ROWS
. 541, WARNING: THE REFERENTIAL OR UNIQUE CONSTRAINT HAS BEEN IGNORED BECAUSE IT IS A DUPLICATE
. 561, WARNING: THE ALTER, INDEX, REFERENCES, AND TRIGGER PRIVILEGES CANNOT BE
GRANTED TO PUBLIC AT ALL LOCATIONS
. 562, WARNING: A GRANT OF A PRIVILEGE WAS IGNORED BECAUSE THE GRANTEE ALREADY
HAS THE PRIVILEGE FROM THE GRANTOR
. 599, WARNING: COMPARISON FUNCTIONS ARE NOT CREATED FOR A DISTINCT TYPE BASED
ON A LONG STRING DATA TYPE
. 610, WARNING: A CREATE/ALTER ON OBJECT HAS PLACED OBJECT IN PENDING
. 645, WARNING: WHERE NOT NULL IS IGNORED BECAUSE THE INDEX KEY CANNOT CONTAIN NULL VALUES
. 664, WARNING: THE INTERNAL LENGTH OF THE LIMIT-KEY FIELDS FOR THE PARTITIONED
INDEX EXCEEDS THE LENGTH IMPOSED BY THE INDEX MANAGER
. 738, WARNING: DEFINITION CHANGE OF MAY REQUIRE SIMILAR CHANGE ON READ-ONLY SYSTEMS
. 799, WARNING: A SET STATEMENT REFERENCES A SPECIAL REGISTER THAT DOES NOT EXIST AT THE SERVER SITE
. 806, WARNING: BIND ISOLATION LEVEL RR CONFLICTS WITH TABLESPACE LOCKSIZE PAGE
OR LOCKSIZE ROW AND LOCKMAX 0
. 863, WARNING: THE CONNECTION WAS SUCCESSFUL BUT ONLY SBCS WILL BE SUPPORTED
. 883, WARNING: ROLLBACK TO SAVEPOINT OCCURRED WHEN THERE WERE OPERATIONS THAT CANNOT
BE UNDONE OR AN OPERATION THAT CANNOT BE UNDONE OCCURRED WHEN THERE WAS A
SAVEPOINT OUTSTANDING
Suscribirse a:
Entradas (Atom)