Copyright: Copyright ® 1996 by Software AG


Messages and Codes
Contents

Manual Ordering

Preface

Preface

Messages and Return Codes

0 SUCCESS

100 ROW NOT FOUND

200 DUPLICATE KEY

250 DUPLICATE SECONDARY KEY

300 INTEGRITY VIOLATION

320 VIEW VIOLATION

350 REFERENTIAL INTEGRITY VIOLATED

360 FOREIGN KEY INTEGRITY VIOLATION

400 LOCK COLLISION

450 LOCK COLLISION CAUSED BY PENDING LOCKS

500 LOCK REQUEST TIMEOUT

600 WORK ROLLED BACK

650 WORK ROLLED BACK

700 SESSION INACTIVITY TIMEOUT (WORK ROLLED BACK)

750 TOO MANY SQL STATEMENTS (WORK ROLLED BACK)

802 NUMERIC OPERATION EXCEPTION ERROR

12001 Message Number: <12...>         Parameter: <text or number>

12003 <table>: inserted <number>, rejected <number> lines

12004 <table>: <number> lines updated, <number> lines invalid

12005 Sum of updates <number>, sum of invalid lines <number>

12006 Sum of inserted lines <number>, sum of rejected lines <number>

12007 Last transaction committed at input line <number>

12008 Rows written : <number>

12010 Other errors

12900 No syntax errors detected, execution begins...

12901 <text> definitions are currently generated

12902 SQL statement successfully executed

12903 SELECT or SHOW successful, LOAD does not display results

12904 The specified number of rows has been loaded

12905 Execution terminated

12906 No syntax errors detected

12907 Now processing <text> data of table <table name>

12908 LOAD statement successfully executed

12910 HELP will display information concerning this error

12920 If you want to leave, please press END again

12921 Costwarning: for execution enter RUN again

12922 Attention, no CREATE TABLE statement (VIEW or no OWNER privilege)

12923 Not all tables could be loaded

12924 CLUSTER part has been ignored

12930 Please mount next tape, then press function key to go on

12931 Please mount tape no <number> (this is tape no <number>)

12940 Difference fixed/variable length, take over the source table definition?

12941 DROPPED COLUMNS, takeover of the source table definition acceptable?

12942 Different constraints, take over the source table definition?

12943 Default values differ - generate the same state as in the source file?

12944 INDEX definitions differ - generate the same state as in the source file?

12945 Data types differ - generate the same state as in the source file?

12950 SQLMODE &1, AUTOCOMMIT OFF

12951 SQLMODE &1; AUTOCOMMIT

12952 SQLMODE &1; NOLOG

12990 LOAD run aborted

12991 Overflow occurred, execution aborted

12992 Execution of control file aborted (RETURN statement executed)

13001 SQL command successfully executed

13002 Command successfully executed

13003 <number> row(s) updated

13004 <number> row(s) deleted

13005 To quit the QUERY session restrike END

13006 Costwarning: for execution enter RUN again

13007 Command rejected - command buffer empty

13008 No entries in command history

13009 Bottom of command history

13010 Top of command history

13011 Command name too long - truncated to 18 characters

13012 Reconnected after timeout

13013 Result may be incomplete, some locations are not accessible

13014 The result is the following command

13015 Command not executed

13016 No commands found

13019 SQLMODE : ANSI

13020 SQLMODE : ORACLE

13021 SQLMODE : DB2

13022 SQLMODE : ADABAS

14101 Bottom reached

14102 Top reached

14103 Leftmost column reached

14104 Rightmost column reached

14105 Output on printer

14106 Nothing to print

14107 Result table printed -  for immediate output press PRINT again

14108 PUT command executed

14109 Warning: command history overflow

14110 value too large, maximum value assumed

14111 Result table printed, for immediate output enter CLOSE

14112 No DETAIL rows found

21200 Repeat Password

21201 To choose a parameter: place the cursor and press <ENTER>

21203 CONDITIONS: NO ERRORS DETECTED

21204 PLEASE CHECK PROTFILE

21205 Press <ENTER> after input

21206 NEW INPUT NOT ALLOWED

21207 PARAMETER ENTRY STORED

21208 To use the default value as new input: press <GET-DEF>

21209 Create a copy of the XPARAM file

21210 Repeat password for XPARAM file creation. Otherwise press <EXIT>

21211 Your OWN value exceeds the COMPUTED value ! Which one do you like ?

21212 Your OWN value is different from the COMPUTED value! What do you like?

21213 CHECK RUNDIRECTORY VALUE

21400 to 21405

23000 You cannot add more than X tables to a query design!

23001 No access to the ADABAS QueryPlus management table! Do you want to create it locally?

23002 Replace existing query?

23003 Replace existing SQL statement?

23004 Dialog was canceled.

23005 Terminate existing DDE communication?

23006 DDE channel busy!

23007 Unknown table:

23008 Empty command!

23009 No result!

23010 Replace existing MS-Word link?

23011 Replace existing MS-Excel link?

23012 Cannot quit QueryPlus at this time!

23013 No link data selected!

23014 QueryPlus is already running!

23015 Cannot find the language file

23016 Cannot fetch complete result!

23017 Cannot delete because you are not the owner!

23018 You cannot design because you have not the permission!

23019 No data transfer while fetching!

23020 Rows to fetch for the first page is too small!

23021 Rows to fetch for the next pages is too small!

23022 Cannot get all stored SQL statements!

23023 Cannot get all stored Queries!

23024 Cannot get all stored Word links!

23025 Cannot get all stored Excel links!

23026 Cannot get all users!

25000 Not Connected

25100 <ODBC Error Text>

25101 Unknown ODBC Error

25200 No corresponding control for variable '<name>'

25201 No Value Property for control '<name>'

25202 Unsupported Data Type

25203 Wrong Name for Session Control

25204 No parameters in statement

25205 No statement executed

25206 No controls to bind to

25299 You installed an earlier version of <name>.  Some features  of VBPlus will not work.

25300 DataSource not connected or RecordSource not set

25301 Property cannot be changed in this state of the form

25302 There must be at least two data controls for Master-Detail

25500 RecordSource too complicated: <statement>

25501 Wrong SelectData Property

25502 Not valid for this data type: <item>

25503 Datatype '<type>' of field '<name>' not supported for  automatic select

25504 'SelectData' or 'SelectField' property not set

25505 Invalid value for automatic select: field '<name>'

25900 Error in Event Procedure

25901 Error <no> loading <name>

25902 Fatal error in ODBC Driver <name>

25903 This version of Visual Basic is not supported by VBPlus

25904 This new version of Visual Basic is not yet supported by your version of VBPlus

25906 Not enough memory

25999 System Error <nr>

Messages and Error Codes

-1 DUPLICATE KEY IN INDEX

-8 EXECUTION FAILED, PARSE AGAIN

-20 DUPLICATE KEY

-25 DUPLICATE SECONDARY KEY

-30 INTEGRITY VIOLATION

-32 VIEW VIOLATION

-35 REFERENTIAL INTEGRITY VIOLATED

-36 FOREIGN KEY INTEGRITY VIOLATION

-40 LOCK COLLISION

-50 LOCK REQUEST TIMEOUT

-51 LOCK REQUEST TIMEOUT

-54 LOCK COLLISION

-60 WORK ROLLED BACK

-65 WORK ROLLED BACK

-70 SESSION INACTIVITY TIMEOUT (WORK ROLLED BACK)

-75 TOO MANY SQL STATEMENTS (WORK ROLLED BACK)

-101 SQL STATEMENT NOT AVAILABLE IN THIS DB MODE

-102 SQL STATEMENT CANCELLED

-106 TABLE UNLOADED OR CONTENT DELETED

-108 TABLE, INDEX DROPPED OR CONTENT DELETED

-109 SERVERDB IS READ ONLY

-110 LOG MUST BE SAVED

-111 INCOMPATIBLE INCREMENTAL BACKUP

-115 TABLE IS READ ONLY

-118 SERVERDB MUST BE ACTIVATED

-119 SERVERDB ALREADY ACTIVATED

-120 REQUEST DISCARDED

-121 SERVERDB MUST BE EMPTY

-122 HISTORY NOT FOUND

-502 INVALID STATEMENT IN DB PROCEDURE/TRIGGER

-503 INVALID STOP CODE IN DB PROCEDURE/TRIGGER

-504 DB FUNCTION FAILED

-505 TRIGGER FAILED

-506 DB PROCEDURE FAILED

-530 REFERENTIAL INTEGRITY VIOLATED

-602 SYSTEM ERROR

-701 MISSING DESCRIBE STATEMENT

-702 MISSING VARIABLE ADDRESS IN SQLDA

-703 DUPLICATE FETCH STATEMENT WITH MFETCH OPTION NOT ALLOWED

-705 TOO MANY FETCH STATEMENTS WITH MFETCH OPTION

-706 SQL STATEMENT TOO LONG (BUFFER OVERFLOW)

-707 CONNECT STATEMENT SYNTAX WRONG

-708 SERVERDB SYSTEM NOT YET AVAILABLE

-709 CONNECT FAILED, CHECK SERVERDB

-711 IMPLICIT CONNECT: MISSING USER OR SERVERDB

-712 TOO MANY PARAMETERS, SQLMAX TOO SMALL

-713 INVALID APPL NAME OR RESULT TABLENAME

-714 INVALID EXEC COMMAND

-715 MISSING USERNAME OR PASSWORD FOR CONNECT

-716 PARAMETER ONLY IN PARM ALLOWED

-717 INVALID PARAMETERSPEC

-718 FOR ATTR EXISTS NO FORM VAR CLAUSE

-719 UNKNOWN LOCALSYSUSER.SYSPROFILE TABLE

-720 SQLCODE  <no>   COMES FROM SYSPROFILE COMMAND

-721 MACRO NOT INITIATED, NO SQLCHECK : WARNING

-722 CMD REPORT LINE IS TOO LONG

-724 DUPLICATE SUBSTRUCTURE NAME

-725 INVALID FORM OPTION ATTR

-726 MACRO NOT ALLOWED IN THIS STATEMENT

-727 INVALID FRAME OPTIONS

-728 INVALID SQLPL OR FORM SYNTAX

-729 SOURCE CODE MAY BE TRUNCATED : WARNING

-730 NESTED COMMENT NOT CLOSED

-731 COMPONENT NAME TOO LONG

-732 INDEX OF COMPONENT OUT OF RANGE

-733 VARIABLE IS DECLARED AS A POINTER : WARNING

-734 POINTER VARIABLE NOT ALLOWED HERE

-735 NO SYNTAX CHECK FOR CONNECT COMMAND : WARNING

-736 MISSING ENDSIGN FOR CMD LINE

-737 BEGIN OR DO STATEMENT AT BLOCK LEVEL 0

-738 EXTRA BLOCK CLOSURE

-739 END LABEL CANNOT BE MATCHED

-740 ARRAY SIZE MISMATCH

-741 INPUT FILE IS LONGER THAN LINENO INPUT FILE : WARNING

-742 INVALID REPORT OR QUERY STATEMENT

-743 INPUT STRING TOO LONG -743 INPUT VARIABLE HAS BEEN TRUNCATED  (ANSI)

-745 CMD QUERY LINE IS TOO LONG

-746 MISSING CMD QUERY LINE

-747 VALUE BUFFER IS TOO SHORT

-748 TOO MANY FETCH STATEMENTS

-750 FFETCH OR ARRAY-FETCH AND FETCH MIX NOT ALLOWED

-751 NUMERIC INPUT PARAMETER OVERFLOW

-752 SESSION ALREADY CONNECTED

-753 OUTPUT PARAMETER WITH CONST TYPE

-754 TOO MANY VARIABLE NAMES DEFINITION

-755 TOO MANY PARAMETERS IN THIS STATEMENT

-756 DIFFERENT SQLMODES NOT ALLOWED

-757 XUSER FILE OPEN ERROR

-758 INCLUDE FILE EXISTS ON DISK : WARNING

-759 INCLUDE FILE PRODUCED BY USER   <user> : WARNING

-760 MEMORY ALLOCATION FAILED

-761 AREA SIZE IS TOO SMALL

-762 EXEC ORACLE COMMAND HAS BEEN DELETED

-763 VARIABLE NOT ALLOWED AS ARRAY

-764 INVALID VARS SPECIFICATION

-765 UNKNOWN ADABAS DATA TYPE (CHECK KERNEL; PRECOM VERS.)

-766 MISSING HOSTCOLSIZE IN SQLDA FOR ARRAY STATEMENT

-767 UNTERMINATED C STRING

-768 INVALID ESCAPE VALUE

-769 POINTER COMPONENT NOT ALLOWED

-770 MACRO IN FETCH SET MFETCH-OPTION TO ZERO

-771 LONG COLUMN EXISTS IN TABLE DEFINITION (WARNING)

-801 INPUT PARAMETER CANNOT BE NULL VALUE

-802 INVALID NUMERIC INPUT PARAMETER VALUE

-803 DUPLICATE SECONDARY KEY

-804 PARAMETER LIST TOO LONG

-805 PROGRAM MUST BE PRECOMPILED

-806 DB SESSION NUMBER NOT ALLOWED

-807 CONNECTION DOWN,  SESSION RELEASED

-808 NOT YET IMPLEMENTED

-809 MISSING INDICATOR VARIABLE, OUTPUT PARAMETER WITH NULL VALUE

-811 NUMERIC OUTPUT PARAMETER OVERFLOW

-812 PARAMETER LIST TOO SHORT

-813 SERVERDB MUST BE RESTARTED

-814 TRACE FILE CLOSE ERROR

-815 TRACE FILE OPEN ERROR

-816 TRACE FILE WRITE ERROR

-817 INCOMPATIBLE DATA TYPES

-818 MISSING MACRO PARAMETER INITIALIZATION

-819 PARAMETER IN SQL STATEMENT NOT ALLOWED

-820 INVALID DECLARE STATEMENT

-821 UNKNOWN COLUMNID

-822 INVALID CONSTANT DEFINITION

-823 INTEGER TOO LARGE, GREATER THAN 32767

-824 STATEMENT IN CONFLICT WITH COMPATIBLE OPTION

-825 DUPLICATE FIELD NAME IN RECORD

-826 DUPLICATE STATEMENT NAME

-827 DUPLICATE TYPE DEFINITION

-828 DUPLICATE VARIABLE NAME

-829 FILE CLOSE ERROR

-830 FILE OPEN ERROR

-831 FILE READ ERROR

-832 FILE WRITE ERROR

-833 ILLEGAL INCLUDE POSITION

-834 INCLUDES MUST NOT BE NESTED

-835 INCLUDE FILE OPEN ERROR

-836 INVALID C PREPROCESSOR COMMAND

-837 DATA DEFINITION NOT ALLOWED

-838 INVALID DECLARATOR

-839 INVALID MACRO VALUE

-840 INVALID NUMERIC MACRO VALUE

-841 INVALID PRECOMPILER OPTION

-842 PARAMETER AND INDICATOR STRUCTURES DO NOT MATCH

-843 INVALID PARAMETER NAME

-844 INVALID RECORD NAME

-845 INVALID SQL STATEMENT

-846 INVALID STATEMENT IN SECTION

-847 INVALID TYPE DEFINITION INVALID CLAUSE (COBOL)

-848 INVALID UNSIGNED INTEGER

-849 INVALID VARIABLE DEFINITION INVALID DATA DEFINITION

-850 STATEMENT TERMINATION EXPECTED

-851 MISSING INPUT FILE NAME

-852 MISSING PROGRAM FILE

-853 PRECOMPILER SYNTAX CHECK ONLY : WARNING

-854 PARAMETERS MUST BE QUESTION MARKS

-855 SQL VARIABLE MUST BE AN ARRAY

-856 INVALID LOOP PARAMETER VALUE

-857 MISSING SERVERDB

-858 STORAGE CLASS NOT ALLOWED

-859 NUMBER OF COLUMNS < NUMBER OF PARAMETERS : WARNING

-860 TOO MANY CONSTANTS DECLARED

-861 TOO MANY PARAMETERS FOR DESCRIPTOR

-862 TOO MANY SQL-PL STATEMENTS

-863 TOO MANY NAMES IN SQLPL STATEMENT

-864 TOO MANY OPTIONS IN SQLPL STATEMENT

-865 TOO MANY PARAMETERS IN SQL STATEMENTS

-866 TOO MANY PREPARE STATEMENTS

-867 TOO MANY PARAMETERS

-868 TOO MANY SQL STATEMENTS

-869 TOO MANY STRING CONSTANTS IN PREPARE OR EXECUTE STATEMENTS

-870 TOO MANY TYPE DEFINITIONS

-871 TOO MANY VARIABLE DEFINITIONS

-872 NUMBER OF COLUMNS > NUMBER OF PARAMETERS : WARNING

-873 UNKNOWN CONSTANT NAME

-874 UNKNOWN CURSOR NAME

-875 UNKNOWN INDICATOR NAME

-876 UNKNOWN MACRO NUMBER

-877 UNKNOWN PARAMETER NAME

-878 UNKNOWN RECORD NAME

-879 UNKNOWN PRECOMPILER STATEMENT

-880 UNKNOWN STATEMENT NAME

-881 UNKNOWN TYPE NAME

-882 MISSING USER NAME FOR CONNECT

-883 INVALID RUNTIME OPTIONS

-884 MISSING INDICATOR VARIABLE : WARNING

-885 VARIABLE MAY BE TRUNCATED : WARNING

-886 MISSING DECLARE SECTION BEGIN OR END

-887 WHENEVER ACTION TOO LONG

-888 MISSING INCLUDE SQLCA

-889 INPUT LINE LONGER THAN 512 CHARACTERS

-890 INPUT LINE LONGER THAN RIGHT MARGIN

-891 DUPLICATE CONSTANT NAME

-892 VARIABLE MAY OVERFLOW : Warning

-893 TOO MANY HOSTVARIABLES

-894 TRACE PARAMETER STRUCTURE NOT ALLOWED

-895 WHOLE TABLE MAY BE DELETED OR UPDATED : WARNING

-896 INVALID SQLPL OPTIONS

-897 INVALID ACCEPT KEYS

-898 INVALID PRINT OPTIONS

-900 DATA SPACE FULL (EMERGENCY SHUTDOWN)

-901 LOG FULL (EMERGENCY SHUTDOWN)

-902 I/O ERROR

-903 HOST FILE I/O ERROR

-904 SPACE FOR RESULT TABLES EXHAUSTED

-905 PERMLIMIT FOR THIS USER EXHAUSTED

-906 TEMPLIMIT FOR THIS USER EXHAUSTED

-907 SPACE FOR USER SESSION EXHAUSTED

-909 MIRRORED DEVSPACES IMPOSSIBLE

-910 COSTLIMIT FOR THIS USER EXHAUSTED

-911 WORK ROLLED BACK

-912 COMMUNICATION FAILURE

-913 LOCK REQUEST TIMEOUT

-914 NEW DEVSPACE NOT ACCESSIBLE

-915 NO MORE MEMORY

-916 SAVE/RESTORE READ PROCESS CRASH - I/O ERROR

-917 SAVE/RESTORE WRITE PROCESS CRASH - I/O ERROR

-918 STACK OVERFLOW

-919 SERVERDB DISCONNECTED

-942 UNKNOWN TABLE NAME

-955 DUPLICATE NAME

-1000 TOO MANY LOCK REQUESTS

-1001 TOO MANY LOCK OBJECTS SPECIFIED

-1002 TOO MANY COLUMNS

-1003 TOO MANY BUFFERS REQUESTED

-1004 TOO MANY CORRELATED COLUMNS

-1005 TOO MANY MONADIC OPERATORS

-1006 TOO MANY VARIABLES

-1007 TOO MANY NAMED INDEXES FOR THIS TABLE

-1010 TOO MANY DEVSPACES

-1011 TOO MANY CORRELATED TABLES

-1012 TOO MANY REFERENTIAL CONSTRAINT DEFINITIONS FOR THIS TABLE

-1013 TOO MANY ORDER COLUMNS

-1014 TOO MANY SOURCE TABLES

-1015 TOO MANY VALUES

-1017 TOO MANY JOINS

-1020 TOO MANY USERS WITH PERMLIMIT DEFINED

-1021 TOO MANY USERS CONNECTED

-1022 TOO MANY SERVERDBS

-1023 TOO MANY NESTED SUBTRANSACTIONS

-1024 TOO MANY TERMCHAR SETS

-1025 TOO MANY NET REQUESTS

-1026 TOO MANY DIFFERENCES BETWEEN OLD AND NEW VIEW DEFINITION

-1034 SERVERDB NOT ACCESSIBLE

-1101 TOO COMPLICATED SQL STATEMENT (BUFFER LIMIT)

-1102 TOO COMPLICATED SQL STATEMENT (TOO MANY SUBQUERIES)

-1103 TOO COMPLICATED SQL STATEMENT

-1200 TOO FEW VALUES

-1201 TOO FEW COLUMNS

-1402 INTEGRITY VIOLATION

-1406 OUTPUT VALUE TRUNCATED

-1556 DATA SPACE FULL (EMERGENCY SHUTDOWN)

-1754 A TABLE MAY CONTAIN ONLY ONE COLUMN OF TYPE LONG

-1755 SQL STATEMENT WILL DROP FURTHER OBJECTS ( USE CASCADE )

-2000 ROW IS TOO LONG

-2001 KEY IS TOO LONG

-2002 ONE OUTPUT COLUMN TOO LONG

-2003 OUTPUT COLUMNS ARE TOO LONG

-2004 NUMERIC CONSTANT TOO LONG

-2008 DEVSPACE SIZE IS TOO SMALL

-2009 JOIN COLUMNS ARE TOO LONG

-2010 ASSIGNMENT IMPOSSIBLE, CHAR VALUE TOO LONG

-2012 VIEW COLUMN LIST TOO LONG

-2013 SELECT COLUMN LIST TOO LONG

-2014 IDENTIFIER TOO LONG

-2020 DATA BUFFER TOO SMALL

-2025 INVALID NUMBER OF BACKUP DEVICES

-3000 INVALID HOST FILE CONTENT

-3002 INVALID DATATYPE

-3003 INVALID USER NAME

-3004 INVALID HOST FILE SEQUENCE

-3005 INVALID SQL STATEMENT

-3007 INVALID SEQUENCE OF DML AND DDL STATEMENTS

-3008 INVALID KEYWORD OR MISSING DELIMITER

-3009 INVALID TABLE NAME

-3010 INVALID CHARACTER VALUE

-3011 INVALID COLUMN NAME

-3014 INVALID END OF SQL STATEMENT

-3016 INVALID NUMERIC CONSTANT

-3017 INVALID UNSIGNED INTEGER

-3018 INVALID NUMERIC PARAMETER

-3019 INVALID EXPONENT

-3020 INVALID LENGTH FOR THIS DATA TYPE

-3021 INVALID MIXTURE OF FUNCTIONS AND COLUMNS

-3022 INVALID NUMBER OF TABLES FOR OUTER JOIN

-3024 INVALID NUMERIC EXPRESSION

-3025 INVALID DEFAULT CODE

-3027 INVALID LOCK TIMEOUT

-3028 INVALID LOG MODE

-3029 INVALID NUMBER OF LOG DEVSPACES

-3030 INVALID SESSION TIMEOUT

-3031 INVALID REQUEST TIMEOUT

-3034 INVALID LOG SEGMENT SIZE

-3035 INVALID DATE TIME FORMAT

-3036 INVALID NUMBER OF DATA DEVSPACES

-3037 INVALID DEVSPACE NAME

-3038 INVALID DEVSPACE SIZE

-3044 INVALID PERMLIMIT SIZE

-3046 INVALID CHAR POSITION IN STRING FUNCTION

-3048 INVALID DATE FORMAT

-3049 INVALID TIME FORMAT

-3050 INVALID TIMESTAMP FORMAT

-3051 INVALID CACHELIMIT VALUE

-3052 INVALID TERMCHAR SET

-3054 INVALID BLOCK SIZE

-3055 INVALID SERVERDB

-3056 INVALID SERVERNODE

-3059 INVALID DAY OF WEEK

-3060 INVALID ESCAPE SEQUENCE

-3061 INVALID ESCAPE VALUE

-3062 INVALID MONTH

-3063 INVALID FORMAT CODE

-3064 DATE INPUT VALUE OUT OF RANGE

-3065 INVALID DATE INPUT VALUE

-3066 DATE INPUT VALUE INCONSISTENT

-3067 INVALID TIMEZONE

-3102 INVALID SUBTRANS STRUCTURE

-3103 INVALID SEQUENCE DEFINITION

-3995 INVALID PATTERN

-3999 INVALID PARAMETER

-4000 UNKNOWN RESULT TABLE

-4002 UNKNOWN PASSWORD

-4003 UNKNOWN USER NAME

-4004 UNKNOWN TABLE NAME

-4005 UNKNOWN COLUMN NAME

-4006 UNKNOWN DOMAIN NAME

-4007 UNKNOWN SYNONYM NAME

-4008 UNKNOWN USER NAME/PASSWORD COMBINATION

-4009 UNKNOWN REFERENTIAL CONSTRAINT NAME

-4010 UNKNOWN MAPCHAR SET NAME

-4011 UNKNOWN INDEX NAME

-4013 UNKNOWN USERGROUP NAME

-4014 UNKNOWN SERVERDB NAME

-4015 UNKNOWN TERMCHAR SET NAME

-4016 UNKNOWN PROCEDURE NAME

-4017 UNKNOWN CONSTRAINT

-4018 UNKNOWN DEFAULT

-4019 UNKNOWN TRIGGER NAME

-4020 UNKNOWN SEQUENCE NAME

-4023 UNKNOWN FUNCTION NAME

-4024 UNKNOWN NAME

-5001 MISSING PRIVILEGE

-5003 MISSING KEY SPECIFICATION

-5004 MISSING CONSTANT

-5005 MISSING COLUMN, NULL VALUE NOT ALLOWED

-5006 MISSING IDENTIFIER

-5007 MISSING NUMERIC CONSTANT

-5008 MISSING STRING CONSTANT

-5009 MISSING INTEGER

-5010 MISSING VALUE SPECIFICATION

-5011 MISSING INDEX VALUE SPECIFICATION

-5012 MISSING DEFINITE TABLE NAME

-5013 MISSING UPDATE COLUMN

-5014 MISSING DEFINITE COLUMN NAME

-6000 DUPLICATE TABLE NAME

-6001 DUPLICATE COLUMN NAME

-6002 DUPLICATE PRIVILEGE

-6003 DUPLICATE RESULT TABLE NAME

-6006 DUPLICATE NAME

-6007 DUPLICATE ORDER COLUMN

-6008 DUPLICATE INDEX NAME

-6009 DUPLICATE REFERENCE NAME

-6010 DUPLICATE DEVSPACE NAME

-6011 DUPLICATE CONSTRAINT

-6012 DUPLICATE DEFAULT

-6013 DUPLICATE TRIGGER DEFINITION

-6014 DUPLICATE VALUE

-6016 DUPLICATE FORMAT CODE

-6017 DUPLICATE SNAPSHOT LOG

-7002 KEY NOT ALLOWED

-7003 NOT NULL NOT ALLOWED

-7004 DEFAULT NOT ALLOWED

-7005 LOWER BOUND GREATER THAN UPPER BOUND NOT ALLOWED

-7006 RESERVED IDENTIFIER NOT ALLOWED

-7007 KEY COLUMN NOT ALLOWED

-7008 UPDATES OF THIS TABLE NOT ALLOWED

-7009 NULL VALUE IN KEY COLUMN NOT ALLOWED

-7011 CORRELATED SUBQUERY NOT ALLOWED

-7012 MORE THAN ONE UPDATE ROW NOT ALLOWED

-7015 MORE THAN ONE RESULT ROW NOT ALLOWED

-7016 PARAMETER SPEC NOT ALLOWED IN THIS CONTEXT

-7017 USER NOT ALLOWED

-7018 VARIABLE NOT ALLOWED IN VIEW DEFINITION

-7019 FEATURE NOT ALLOWED IN VIEW DEFINITION

-7021 VIEW COLUMN DERIVED FROM FUNCTION NOT ALLOWED

-7022 COLUMNS OF MORE THAN ONE TABLE NOT ALLOWED

-7023 DROPPING OF ALL COLUMNS NOT ALLOWED

-7024 ALTER COLUMN NOT ALLOWED, CONSTRAINT VIOLATION

-7026 SQL STATEMENT NOT ALLOWED WITHOUT PREVIOUS FETCH

-7029 FUNCTION NOT ALLOWED FOR THIS DATA TYPE

-7030 PERMLIMIT LESS THAN PERM COUNT NOT ALLOWED

-7031 CONSTRAINT OR DEFAULT FOR DATA TYPE LONG NOT ALLOWED

-7032 SQL STATEMENT NOT ALLOWED FOR COLUMN OF DATA TYPE LONG

-7034 PERMLIMIT FOR STANDARD USER NOT ALLOWED

-7035 DEFAULT SPECIFICATION NOT ALLOWED FOR THIS COLUMN

-7036 ROWNO SPECIFICATION NOT ALLOWED IN THIS CONTEXT

-7037 NULL VALUE FOR NOT NULL COLUMN NOT ALLOWED

-7038 FOREIGN KEY COLUMN NOT ALLOWED

-7039 CYCLE IN REFERENTIAL CONSTRAINT DEFINITION NOT ALLOWED

-7040 REFERENTIAL CONSTRAINT NOT ALLOWED

-7041 RESULT TABLE NAME NOT ALLOWED

-7042 KEY UPDATE NOT ALLOWED

-7043 GROUP MEMBER NOT ALLOWED

-7044 CLEAR LOG NOT ALLOWED

-7045 PARAMETER SPEC NOT ALLOWED

-7048 DROP/ALTER USER NOT ALLOWED WHILE USER IS CONNECTED

-7050 FASTLOAD WITH INDEXED TABLE NOT ALLOWED

-7051 READ ONLY VIEW WITH CHECK OPTION NOT ALLOWED

-7052 SINGLE SELECT NOT ALLOWED

-7054 PARAMETER IN PARSING EXPLAIN NOT ALLOWED

-7055 COLUMN(S) ALREADY INDEXED

-7056 SUBQUERY NOT ALLOWED

-7057 VIEW DEFINITION CONTRADICTS NEW TABLE DEFINITION

-7058 CORRELATED SUBQUERY WITH SELECT IN FROM CLAUSE NOT ALLOWED

-7060 REMOTE TABLE LOAD/UNLOAD NOT ALLOWED

-7061 LOCK ROW FOR THIS TABLE NOT ALLOWED

-7063 TEMP TABLE NOT ALLOWED

-7064 FEATURE NOT ALLOWED IN TEMP TABLE DEFINITION

-7065 SUBTRANS COMMIT/ROLLBACK NOT ALLOWED WITHOUT SUBTRANS BEGIN

-7066 UNIQUE INDEX REFERENCED BY FOREIGN KEY NOT ALLOWED

-7067 UPDATE WITHOUT REPEATED READ NOT ALLOWED

-7068 OUTER JOIN NOT ALLOWED IN THIS CONTEXT

-7069 REMOTE WRITE ACCESS IN NOLOG SESSION NOT ALLOWED

-7070 SNAPSHOT TABLE BASED ON SNAPSHOT TABLE NOT ALLOWED

-7900 DIFFERENT BLOCK SIZES

-8000 SERVERDB MUST BE RESTARTED

-8001 USER MUST BE CONNECTED

-8002 USER ALREADY CONNECTED TO THIS USER TASK

-8003 LOG AND DATA MUST BE COMPATIBLE

-8004 CONSTANT MUST BE COMPATIBLE WITH COLUMN TYPE AND LENGTH

-8005 VALUE EXPRESSION MUST BE PARAMETER NAME

-8006 DATA TYPES MUST BE COMPATIBLE

-8007 COLUMN MUST BE KEY COLUMN

-8009 DEFAULT VALUE MUST BE IN CONSTRAINT SPECIFICATION

-8010 TABLE NAME MUST BE IN FROM LIST

-8013 ORDER COLUMN MUST BE OUTPUT COLUMN

-8014 RESULT TABLE MUST BE FOR REUSE

-8015 TABLE MUST BE A BASE TABLE

-8016 TABLE MUST BE A VIEW TABLE

-8017 COLUMN MUST BE GROUP COLUMN

-8018 INDEX NAME MUST BE UNIQUE

-8021 COLUMN MUST HAVE DEFAULT SPECIFICATION

-8022 USER ALREADY CONNECTED

-8023 COSTLIMIT MUST BE GREATER THAN COSTWARNING

-8025 TABLE MUST BE TEMP TABLE

-8026 FUNCTION PRESENTLY NOT EXECUTABLE

-8028 UNION COLUMNS MUST BE COMPATIBLE

-8029 NO SERVERS INSTALLED

-8030 COLUMN MUST BE INDEXED

-8031 OWNER MUST BE SPECIFIED

-8032 TABLE MUST BE A SNAPSHOT TABLE

-8033 INCOMPLETE LOG SEGMENT

-8034 ORDER COLUMN MUST BE NUMBER

-8035 FOREIGN KEY MUST EXIST

-8037 DB PROCEDURE MUST BE RECOMPILED

-8038 SERVERDB MUST BE AUTHORIZED

-8039 SNAPSHOT LOG DOES NOT EXIST

-8040 KEY DOES NOT EXIST

-8041 START OF ADABAS REQUIRED

-8042 ACKNOWLEDGEMENT NECESSARY

-8043 SOME SERVERDBS NOT ACCESSIBLE

-8888 SERVERDB NOT ACCESSIBLE

-9000 SYSTEM ERROR: NOT YET IMPLEMENTED

-9001 to -9799 SYSTEM ERROR:

-9801 INVALID COMMAND STATE

-9803 UNKNOWN DATA TYPE

-9804 ROLLBACK ERROR

-9805 OPTION CHECK   USAGE ON OR OFF ERROR

-9806 INVALID OUTPUT VALUE

-9807 TOO MANY USERS

-9808 SET FORMAT ERROR

-9809 OPTION CHECK   USAGE ADD  ERROR

-12002 Database is not accessible

-12101 Duplicate file name, file already open

-12102 Error opening file: <operating system message>

-12103 Error closing file: <operating system message>

-12104 Error reading file: <operating system message>

-12105 Error writing file: <operating system message>

-12106 Error erasing file: <operating system message>

-12107 Record length <number> too large

-12108 Input file contains no data

-12109 No command file accessed

-12110 End of command file

-12111 Printer not accessible

-12112 It is not possible to open another INCLUDE file

-12113 ORACLE file specifies invalid number of columns

-12201 INTEGER field : 1, 2 or 4 bytes long, (double if HEX)

-12202 REAL field : 4 or 8 bytes long (double if HEX)

-12203 DECIMAL field : 10 bytes, ZONED field : 20 bytes maximum (double if HEX)

-12204 Incorrect field length, necessary length : <number>

-12205 Fractional part too small, minimum length : <number>

-12206 Derived length of output line is too large

-12207 Position exceeds permitted row length

-12208 SQL statement is too long

-12209 File name is too long

-12210 String is too long

-12211 A constant input value must not be empty

-12212 Comparison value in condition has invalid length

-12213 At most 254 columns can be specified for one table

-12214 At most 20 tables can be loaded simultaneously

-12215 No further conditions allowed

-12216 Declare USAGE between 50% and 100%

-12217 Statement cannot be displayed completely

-12218 Memory space for LONG columns exhausted

-12301 Invalid input for date or time column

-12302 This value is not a valid number

-12303 Invalid position specification

-12304 Invalid FRACTION specification

-12305 Invalid SCALE specification

-12306 Incorrect format, valid are all patterns accepted in the SET menu

-12307 Incorrect comparison operator in condition

-12308 File content does not match table definition, reason code <consecutive number>

-12309 Input value does not match key order or range specification

-12310 This value is not a valid HEX constant

-12311 Invalid input for DBYTE column

-12312 CONSTRAINT condition violated

-12313 This specification is not allowed together with COMPRESS

-12314 Please specify the columns in left-to-right order  (positions ascending)

-12315 This specification is not allowed for ORACLE data

-12316 Invalid input for BOOLEAN column

-12401 End of selection criterion not recognized, semi-colon  missing

-12402 Delimiter missing

-12403 No opening parenthesis found

-12404 No closing parenthesis found

-12405 Table name missing

-12406 No columns specified for this table

-12407 Columns for key (KEY) or search condition missing

-12408 No (SET) columns to be changed specified

-12409 No column with this name or number contained in result table

-12410 No column number found (maybe it was interpreted as ZONED/DECIMAL fraction)

-12411 File specification missing or incorrect

-12412 No comparison value specified in condition

-12501 OTHERWISE condition not allowed here

-12502 This command requires a table with key columns

-12503 Column must not contain NULL values

-12504 ROUND or TRUNC specification not allowed for this column

-12505 Column data type and external data type are not compatible

-12506 Table contains column with unknown data type

-12507 Name denotes no TABLE, VIEW and UNLOADED are not allowed

-12508 This is a restricted statement, user must be SYSDBA

-12509 This statement can only be executed by the local SYSDBA

-12510 ORACLE column &1 has an incompatible datatype

-12511 The only way to load LONG columns is a one-table DATALOAD  statement

-12601 Unknown batch command

-12602 Unknown command

-12603 Input area contains no statement

-12604 Incomplete statement

-12605 Wrong keyword

-12606 Re-connected after timeout, statement must be started again

-12607 Execution rejected

-12608 Catalog lock request rejected, other users active

-12609 No rejected rows logged

-12610 Too many DEFAULT definitions for FASTLOAD loading

-12612 Not implemented

-12613 Parameter cannot be replaced, no actual argument passed

-12614 USER/USE connect with new username failed

-12615 Table has so many constraints that TABLELOAD would be impossible

-13501 Unknown QUERY command

-13502 Database command not allowed in QUERY

-13503 Name of stored command missing

-13504 Correct format : AUTOCOMMIT ON/OFF

-13505 Duplicate stored command name

-13506 Stored command not found

-13507 No further command found

-13508 Parameter list too short or missing

-13509 Enter new command name

-13510 First character of command name must be a letter

-13511 ENDLAYOUT missing

-13512 GRANT and REVOKE are not allowed for other users' commands

-13513 Command not executed

-13514 Wrong GO table definition

-13515 Table does not exist

-13516 Row not found

-13517 Invalid character in command name

-13518 No information available

-13519 Enter filename

-13520 Invalid command name

-13521 IMPORT command aborted

-13522 EXPORT command aborted

-13523 Invalid REPORT command

-13524 Enter new database name

-13525 Connection failed

-13526 Syntax: GO <table> or GO '<file>' or GO OFF

-13527 SQLEXEC error

-13528 Final quote missing

-13529 User does not exist

-13530 This command is too long to be stored, please divide it into two parts

-13531 Layout exceeds possible form size

-13532 The FOREIGN KEY condition cannot be resolved

-13533 Name of user missing

-13535 Unknown call option

-13536 EASY named request not found

-13537 Error in call privileges

-13538 Invalid SQLMODE

-13539 Syntax error in CROSS command

-13540 Create CROSS table failed

-13541 Table does not exist

-13542 Invalid column type in CROSS command

-13543 Row could not be inserted

-13544 Table contains no data

-14601 Unknown REPORT command

-14602 Maximum number of columns for this command reached

-14603 Enter new column name

-14604 Command only valid for CHAR columns

-14605 Unknown column identification

-14606 TAB rejected - column width less than display width

-14607 TAB rejected - column width less than value

-14608 Command only valid for numeric columns

-14609 First character of new column name must be a letter

-14610 Column width must be greater than zero

-14611 Value must be a number

-14612 Invalid column identification

-14613 Value must be ON or OFF

-14614 Only 8 rows for new name allowed

-14615 Printer error :

-14616 File error :

-14617 Enclose filename in quotes

-14618 Column width too large

-14619 Invalid LEVEL

-14620 Result table not available after timeout

-14621 REPORT buffer limit exceeded

-14622 Maximum number of digits = 18

-14623 Layout exceeds page width, print rejected

-14624 Label too long

-14625 Column is excluded

-14626 Printer not available

-14627 Missing position specification

-14628 Only conversion of byte strings possible

-14629 Double position or size specification

-14630 Invalid position or size specification

-14631 Mask missing or invalid

-14632 Command not possible after FORMAT

-14633 Application error :

-14634 Page length specification too small

-14635 Invalid arithmetic expression

-14637 Error with clipboard

-14638 ENDDETAIL missing

-14639 Command only valid for LONG columns

-14640 LONG column is empty

-14641 Error with zoom

-14642 Command only valid for CHAR LONG columns

-15000 Please enter table/view name

-15001 Invalid number entered

-15002 Output truncated

-15003 Key column must not be dropped

-15004 Invalid name

-15005 Example value missing

-15006 Example value is longer than specified length

-15007 Named request not found

-15008 Request already exists - will be overwritten by STORE

-15009 Undefined function

-15010 Function not unique

-15011 Request is not for this table

-15012 Printer not ready

-15013 No help texts loaded

-15014 Row already deleted

-15015 <language> language not available - <language> assumed

-15016 REPORT after DELETE/UPDATE/INSERT not allowed

-15017 Duplicate key definition

-15018 Input field too long

-15019 Form too wide

-15020 Invalid example value

-15021 No data field defined

-15022 Too many columns for TOTAL / SUBTOTAL / labels

-15023 too many REPORT commands

-15024 SUBTOTAL not allowed

-15025 Empty table menu

-15026 Invalid length

-15027 Wrong table column for FOREIGN KEY

-15028 Wrong cursor position

-15029 File open error

-15030 DELETE/UPDATE not allowed after INSERT

-15031 Too many base tables

-15032 Join assignment not unique

-15033 Form field too short

-15034 No EASY request

-15035 Request name missing

-15036 Batch processing not possible for XEASY

-15037 Too many changes

-15038 No named requests available

-15039 Wrong prefix command

-15040 No valid <operating system> command

-15041 Join assignment open

-15042 Wrong DBYTE value

-15044 No form marked

-15045 No user defined forms available

-15046 A form already exists for this table - confirm with IMPORT

-15047 No request marked

-15048 Request already exists

-15049 Wrong file format

-15050 No column numbers defined

-15051 Wrong column specification

-15052 Form and table definition not identical

-15053 FOREIGN KEY name missing

-15054 FOREIGN KEY not found

-15055 No detail rows found

-15056 Request attribute missing

-15057 Attribute request not found

-15058 Wrong cursor position

-15059 No user-defined request available

-15060 Restrained table menu

-15200 Warning: View becomes read only

-15201 Warning: Table changed by other user - see HELP

-15202 Warning: Database column will be dropped

-15203 Warning: Too many DD rows - row number lost

-16001 <module name> not found

-16002 Program not found

-16003 Module not found

-16020 Vector index must be between 1 and 255 (<module name>)

-16021 Repeat string length out of bounds (<module name>)

-16022 Too much data

-16023 No temporary space available

-16024 Endless loop supposed (<module name>)

-16025 Nested SQL calls not allowed (<module name>)

-16031 Call of stored command is too long (<module name>)

-16032 NULL value not allowed in stored command (<module name>)

-16033 Stored command not found (<module name>)

-16040 No terminal I/O in batch (<program name>)

-16041 Module <name> has to be stored again ( e.g. with MSTORE )

-16042 Invalid pattern in LIKE predicate

-16050 Not a PROC (<module name>)

-16051 Not a FUNCTION (<module name>)

-16052 Not a FORM (<module name>)

-16053 Not a HELPFORM (<module name>)

-16054 Not a MENU (<module name>)

-16080 End of file

-16081 File <name> already open

-16082 File <name> not writable

-16083 File <name> not readable

-16084 Too many files already opened

-16085 File <name> isn't open

-16086 Open error at file <name>

-16100 Stack overflow (<module name>)

-16101 There is no line for key labels (<module name>)

-16102 Out of memory (<module name>)

-16103 PULLDOWN label and COMMENT buffer overflow

-16104 Too many labels in menu

-16105 Too many PULLDOWNs in menu

-16106 Wrong terminal type

-16107 All labels are empty in menu (<module name>)

-16108 Actionbar out of window

-16201 '.' expected

-16202 '=' expected

-16203 ''' expected

-16204 ':=' expected

-16205 '(' expected

-16206 ')' expected

-16207 ':' expected

-16208 '<->' expected

-16211 PROC, DBPROC, FORM or FUNCTION expected

-16212 LAYOUT expected

-16213 AND expected

-16214 DO expected

-16215 END expected

-16216 THEN expected

-16217 UNTIL expected

-16218 WHEN expected

-16219 AS expected

-16220 CALL expected

-16221 OF expected

-16222 Print parameter expected

-16223 TO or DOWNTO expected

-16224 READ, WRITE or APPEND expected

-16225 IMMEDIATE expected

-16226 INTO expected

-16227 ROWS expected

-16228 F1 or F2 ... or F12 or HELP expected

-16229 Length (S, M, L, XL) expected

-16230 HIGH, LOW, INV, BLK, UNDERL or ATTR1..ATTR16 expected

-16231 BACKGROUND, NOHEADLINE, SETLOCAL or SETOFF expected

-16232 SUM, AVG, COUNT, MIN, MAX, VAL1, VAL2, VAL3 or VAL4 expected

-16233 IN, OUT or INOUT expected

-16241 New line expected

-16242 Parameter expected

-16243 Special character expected

-16244 Comparison operand expected

-16245 Expression expected

-16246 Statement expected

-16247 Any character expected

-16248 Variable list expected

-16249 Literal expected

-16250 Slice specification expected

-16251 Compiler option expected

-16252 FORM option expected

-16253 Numeric literal expected

-16254 Logic expression expected

-16256 Parameters for stored command expected

-16257 REPORT result specification expected

-16258 SQL data type expected

-16259 Call of a stored command expected

-16260 QUERY 'RUN' symbol expected

-16261 Name of a stored command expected.

-16262 'EXEC' symbol not allowed in REPORT call.

-16270 Constant is expected to be in hex notation

-16271 Because of vector slice in argument list a predicate is expected

-16280 Missing keyword

-16281 ENDLAYOUT expected

-16282 POS expected

-16284 VAR expected

-16285 CATCH expected

-16286 FROM expected

-16287 USING expected

-16288 PREPARE, EXECUTE or DESCRIBE expected

-16300 Obscure statement

-16301 Type declaration not allowed

-16302 Invalid layout specification

-16303 Invalid number

-16304 Invalid pattern

-16305 Invalid name

-16306 Invalid statement

-16307 Invalid boolean expression

-16308 Invalid slice specification

-16309 Invalid vector index

-16310 Variable is a vector

-16311 Variable is not a vector

-16312 Undeclared variable

-16320 CALL and SWITCH not allowed in FUNCTIONs

-16321 A vector component is not allowed as formal parameter

-16322 Empty layout not allowed

-16323 MESSAGE is not allowed here

-16324 Sign is not allowed here

-16325 CALL and SWITCH not allowed in HELPFORM screens

-16326 This SQL command is not allowed here

-16327 PAGE statement and explicit MESSAGE are not allowed

-16328 Only one field allowed in FIELD statement with DOMAIN specification

-16329 AUTOPAGE statement not allowed with ACTIONBAR definition

-16330 Only one INIT, SIZE and CHECK specification per FIELD statement allowed

-16331 This statement in CONTROL block is not allowed

-16332 Only one ACCEPT option allowed

-16333 Only one CONTROL option allowed

-16334 In HELPFORM screens only local variables are allowed

-16335 Only 20 attribute options on form call allowed

-16336 Only 20 INPUT/NOINPUT variable arguments on form call  allowed

-16337 This statement is only allowed in field-oriented forms

-16338 Only 20 DISPLAY formats per form allowed

-16340 Only ACTIONBAR in first line allowed

-16341 ACTIONBAR expected

-16342 PULLDOWN Menu not defined

-16343 Too many levels of PULLDOWN menus

-16344 Too many labels in menu

-16346 BUTTON in the layout expected

-16347 ACTIONBAR or BUTTON not defined

-16350 This statement is illegal in a DB procedure

-16351 This statement is illegal in field oriented forms

-16352 Global variables not allowed in functions

-16353 All or none of the fields have to belong to a group

-16354 Group name expected

-16355 Input variables may occur only in one FIELD statement

-16356 Global variables not allowed in DB procedures and triggers

-16360 Too many modules in this program

-16361 Too many variables

-16363 Too many field groups

-16364 Too many SQL variables

-16365 Too many parameters

-16370 Routine/Form too complex

-16400 This name is reserved

-16402 Duplicate definition

-16411 Up to 255 different fields may be used at runtime

-16412 Up to 9 different attribute definitions are possible

-16413 Up to 20 ignore definitions are possible

-16420 Number of parameters does not agree

-16430 This variable definition does not match the number of layout fields

-16431 There is no corresponding variable for this field number

-16432 Number of fields does not match the slice definition

-16433 All fields of a vector slice have to be input or output fields

-16434 Variable, vector or field number has to be defined  in the layout

-16435 This variable is already defined as input field

-16436 The value has to be greater than 0

-16440 This SQL command is too long or the closing parenthesis is missing

-16441 This QUERY/REPORT command is too long

-16442 Maximal length exceeded

-16460 Label not found

-16461 Too many labels

-16462 Duplicate label

-16490 DOMAIN definition syntactically incorrect

-16491 Unknown DOMAIN name

-16492 Unknown field or group in NEXTFIELD or NEXTGROUP statement

-16493 No label definition possible for this key

-16500 Not yet implemented

-16501 System error

-16502 Invalid system variable

-16503 Internal value error : <error number>

-16505 Internal database error : <error number>

-16506 Out of system memory

-16510 Syntax tree too complex

-16514 Bounds of vector slice parameter exceeded

-16515 Parameter must be a vector slice

-16519 System error while accessing a variable value

-16600 Precompiler and SQL-PL interpreter are incompatible

-16601 One of the variable values is too large

-16602 One of the output variables is not known in the form

-16604 Too many parameters

-16700 Database not accessible

-16704 Error during CONNECT on additional database

-16705 Too many databases

-16706 Unknown symbolic database name

-16730 Wrong SQL data type

-16731 Command not prepared

-16901  <name> not found

-16902 Program: <name> not found

-16903 Module <name> not found

-16904 Value <name> not found

-16905 User <name> does not exist

-16906 Module <name> is not a DB Procedure

-16907 Module <name> is not a trigger

-16908 Trigger <name> already exists

-16909 Invalid version <version>

-16910 Invalid command

-16911 No command in history

-16912 Invalid parameter

-16913 Invalid menu

-16914 Cursor not at prefix

-16922 Privilege cannot be granted

-16925 Program <name> cannot be dropped

-16926 Module <name> cannot be deleted

-16927 <Name> is in EDIT status

-16928 Modules in DB state cannot be modified

-16931 No export privilege

-16932 No grant privilege

-16933 No import privilege

-16934 No privilege on program <name>

-16935 Grant error

-16936 IMPORT error

-16937 REVOKE error

-16940 No literal defined

-16941 Set parameters not saved

-16942 SET info not found

-16951 First character must be a letter

-16952 Invalid program name

-16953 Invalid module name

-16954 '.' expected

-16955 Valid object type expected

-16956 Module <name> already exists

-16957 Too many procedures/forms

-16958 Module <name> is not a procedure

-16959 Name has more than 18 characters

-16962 Excluding of all columns not allowed

-16966 Table has more than <n> columns

-16970 Invalid table name

-16971 Table name must be specified

-16972 Program name must be specified

-16973 Filename must be specified

-16974 Position must be between 1 and 14

-16975 Size not between <n> and <m>

-16976 Prompt must be special character

-16977 Library name must be specified

-16978 Unknown reference name

-16979 Reference name must be specified

-16986 Open error at file <name>

-16987 Abort - TEST version exists for <program name>

-16999 Not implemented

-17001 Unknown prefix command - execution rejected

-17002 Pending <name> command

-17003 Multiple p/f targets specified - execution rejected

-17004 Edit form too small

-17005 Printer not available

-17006 Invalid option

-17007 Filename must be enclosed in single quotes

-17008 File error :

-17009 No line copied

-17010 PICK command rejected

-17011 Buffer is empty

-17012 No line(s) changed

-17013 Records truncated

-17014 Command buffer empty

-17015 Too many prefix commands

-17016 No WRAP, line is too long

-17017 WRAP is RED command

-17018 More than <couunt> edit lines

-20001 Database <name> does not exist

-20002 This username is already defined

-20004 CONTROL profile <Name> not found

-20005 Unknown <sysusertype> name/password combination

-20007 Different passwords, please reenter!

-20008 Alter <sysusertype> in WARM state only!

-20009 Alter CONTROL user in COLD/OFFLINE state only!

-20010 Tempfile <name> does not exist!

-20011 No termcharset defined

-20012 No mapcharset defined

-20018 Devspace path already defined

-20019 Data devspace size is too small! (min = 1500 pages)

-20020 Log segment size is too small (min = 300 pages)

-20022 Invalid value entered

-20025 Value <= 0 not allowed here!

-20026 Log mode DUAL was not defined!

-20027 No log segmentation, when log mode is DEMO!

-20028 Device does not exist

-20029 Transaction log size is too small (min = 300 pages)

-20030 Archive log size is too small (min = 1000 pages)

-20031 While restarting the SERVERDB, x_start failed!

-20032 While restarting the SERVERDB, x_clear failed!

-20033 Offline Shutdown failed due to x_stop

-20035 Remote SQL Server could not be started!

-20036 Kernel trace activation failed!

-20037 Kernel trace deactivation failed!

-20038 Kernel trace buffer flush failed!

-20040 Unkown transaction code in operating menu

-20044 Invalid numeric value

-20046 This medium already exists !

-20049 Cannot define more than 254 backup media

-20065 Missing SERVERDB argument for backup operation

-20068 Error when calling for x_param !

-20069 Error when calling for x_cons !

-20072 Error while generating tempfile <name>

-20073 Backup operation was aborted!

-20081 BREAK - Another CONTROL background process is already active

-20082 Error when opening CONTROL profile

-20094 Create of systemtables failed

-20100 Update of system tables failed

-20102 Invalid value for devspace size

-20103 The devspace name (special file name) has to be defined

-20105 No permission to create directory : <name>

-20106 No permission to create file : <name>

-20108 No remote server access - local CONTROL use only

-20113 Dual devspace is missing

-20114 DBROOT is missing

-20116 The DUAL LOG SIZE must be equal to the first LOG

-20117 Automatic backup is already running

-20118 Invalid SYSDBA

-20119 Device name too long!

-20121 Version not allowed for two devices

-20123 REQUEST TIMEOUT must be shorter than LOCK TIMEOUT

-20125 Start a backup generation by performing a complete database save first!

-20126 Medium does not exist!

-20128 Not allowed while AUTOSAVE LOG is running!

-20129 Medium does already exist!

-20130 Up to 4 backup devices allowed

-20131 Wrong save type

-20132 Cannot create a new version, because file already exists

-20133 Count of defined backup devices is too small  (ALTER KERNEL PARAMETER)

-20201 CRONTAB exists in unix environment only !

-20202 Error submitting CRONTAB <name>!

-21100 UNKNOWN CONTROLUSER/CONTROLPASSWORD

-21101 SERVERDB MISMATCH

-21102 MANDATORY VALUE MISSING

-21103 COPY FAILED

-21104 PRINT FAILED

-21105 XPARAM FILE EXISTS

-21106 NOT CORRESPONDING PARAM. DELETED

-21107 NOT CORRESPONDING PARAM. DETECTED

-21108 NO XPARAM CREATION FOR SUPERUSER

-21109 CONTROLUSER/SERVERDB NOT DIFFERENT

-21110 PASSWORD MISMATCH

-21111 RUNDIRECTORY PATH TOO LONG

-21112 TERMINAL INITIALISATION FAILED

-21300 INTEGER OVERFLOW

-21301 SUBTRACTION FAILED

-21302 DIVISION FAILED

-21303 PRIMARY PARAMETER NOT ACCESSIBLE

-21304 SECONDARY PARAM. NOT ACCESSIBLE

-21305 CALC failed

-21306 CONSTRAINT NOT SATISFIED

-21307 CANNOT COMPUTE CONDITION

-21308 CANNOT CHECK CONSTRAINT CONDITION

-21800 SYSTEM ERROR: INPUT LINE TOO LONG

-21801 SYSTEM ERROR: INVALID XHELPFILE

-21802 SYSTEM ERROR: DBNAMEFILE FAILED

-21803 SYSTEM ERROR: XHELPFILE FAILED

-21804 SYSTEM ERROR: PROTFILE FAILED

-21805 to -21919

-23000 Cannot show your tables!

-23001 Cannot select this session!

-23002 Cannot find the field:

-23003 The result of a SELECT is too big!

-23004 Database error occurred!

-23005 Unknown DDE EXECUTE command!

-23006 Database access failed!

-23007 Too many joins!

-23008 Cannot release the session!

-23010 Cannot get the SQL statement!

-23011 Cannot get the Query command!

-23012 Cannot save the SQL statement!

-23013 Cannot delete the query!

-23014 Cannot save the query!

-23015 Cannot read the query!

-23016 Cannot read the SQL statement!

-23017 Error while writing the MS-Excel file!

-23018 Unknown MS-Excel file type!

-23019 Cannot create the MS-Excel file!

-23020 Cannot execute DDE or no result!

-23021 Too many columns!

-23022 Syntax error:

-23023 Cannot add table:

-23024 Cannot read the link!

-23025 Cannot save the link!

-23026 Cannot share objects!

-23027 Cannot show your shared objects!

-23028 Cannot stop sharing of objects!


Manual Ordering

Manual Order Number:  ESD611-060WOU

This online help is applicable to ADABAS D Version 6.1.1 PE and to all subsequent releases, unless otherwise indicated in new editions or technical newsletters.

Specifications contained herein are subject to change and these changes will be reported in subsequent revisions or editions.

Readers' comments are welcomed. Comments may be addressed to the Documentation Department at the address on the back cover.

©    March 1995, SOFTWARE AG, Germany & SOFTWARE AG of North America, Inc.

All rights reserved

Printed in the Federal Republic of Germany

The SOFTWARE AG documentation often refers to numerous hardware and software products by their trade names. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by their respective companies.


Preface - Preface
Preface

This book contains the messages and codes of the ADABAS kernel, the tool components of ADABAS, and the ADABAS precompilers. Short explanations of the possible causes of the errors and instructions of how to correct them are included.

The second chapter lists the messages and return codes in ascending order (from 0 to 25999). They are status messages which are also output for a syntactically correct query or a faultlessly running program.

There is one exception: the VBPlus messages are actual error messages. The usage of a positive code is set down by Visual Basic.

The third chapter lists the error messages and error codes in descending order (from -1 to -25999). They show that an error occurred and what user action is recommended.


0 SUCCESS

Explanation:

The SQL statement was successfully executed.

The desired effect was produced.

User Action:

No user action is required.


100 ROW NOT FOUND

Explanation:

There is no (further) table row which meets the qualification.

User Action:

No user action is required.


200 DUPLICATE KEY

Explanation:

There is already a table row with the key to be inserted.

User Action:

Check whether the existing table row contains the desired values. If this is not the case, check whether values in the existing table row can be replaced with the desired values. If a new table row must be inserted, change the value of the key to be inserted in order to prevent key collisions.


250 DUPLICATE SECONDARY KEY

Explanation:

There is already a table row with the specified secondary key. UNIQUE was specified for the secondary key.

User Action:

Correct the value of the secondary key to be inserted in the SQL statement in order to avoid a key value collision.

The error message specifies the column or multiple-column index already containing the specified values.


300 INTEGRITY VIOLATION

Explanation:

Insertions or updates would violate integrity constraints specified in the base or view table definition.

User Action:

The error message specifies the column which would violate the integrity constraints.

Correct the input value for the corresponding column.


320 VIEW VIOLATION

Explanation:

An <insert statement> or <update statement> was issued for a view table. At least one of the rows specified in the SQL statement does not satisfy the <search condition>s of all underlying view tables defined 'WITH CHECK OPTION'.

User Action:

Display the definition of the view table using a <query statement> issued on the system table DOMAIN.VIEWDEFS. Correct the <insert statement> or <update statement> according to this definition.


350 REFERENTIAL INTEGRITY VIOLATED

Explanation:

There are three possible causes:

1.	An <insert statement> or <update statement> issued on a table that is the referencing table in a <referential constraint definition> produces a row that is not a matching row of the <referential constraint definition>.

2.	When deleting rows from a <referenced table> of a <referential constraint definition> with <action> RESTRICT in the <delete rule>, a matching row exists.

3.	When executing a <referential constraint definition>, the <referenced table> or referencing table contains rows which conflict with the <referential constraint definition> to be created.

User Action:

1.	Display the <referential constraint definition> using a <query statement> issued on the system table DOMAIN.COL_REFS_COL. Correct the <insert statement> or <update statement> according to this definition.

2.	Use an appropriate <query statement> to determine which row of the referencing table prevents the desired <referenced table> rows from being deleted.

3.	Use an appropriate <query statement> to determine which row of the <referenced table> or referencing table conflicts with the <referential constraint definition> to be created. Modify or delete the row concerned, or correct the <referential constraint definition> to be created.


360 FOREIGN KEY INTEGRITY VIOLATION

Explanation:

In case of an <insert statement> or <update statement> issued on a join view table, the column values functionally depending on the <referencing column>s of the referencing table conflict with the already existing column values.

User Action:

This conflict may be solved by changing either the column values specified in the <insert statement> or <update statement>, or the already existing values.


400 LOCK COLLISION

Explanation:

When the option '(NOWAIT)' is specified in the <lock statement> or in the <lock option>, this message signals that the lock request conflicts with the locks of other users.

User Action:

1.	In interactive mode, another job can be activated which does not require the desired lock.

2.	As an alternative, you can wait for the lock being released by specifying the same SQL statement without '(NOWAIT)' option.


450 LOCK COLLISION CAUSED BY PENDING LOCKS

Explanation:

The lock request made by the SQL statement conflicts with locks which presently cannot be resolved because they belong to a pending transaction. The pending transaction cannot be concluded because there is no connection to the releasing SERVERDB.

User Action:

The SQL statement should not be reissued until the pending transaction could be resolved; i.e., until it was possible to reconnect to the particular SERVERDB.


500 LOCK REQUEST TIMEOUT

Explanation:

1.	The lock request or an implicit lock conflicts with the locks of another user. The maximum waiting time for granting the lock has elapsed (installation parameter REQUEST TIMEOUT).

2.	The Operating / Shutdown / Normal menu function in the ADABAS component CONTROL could not be performed in a certain period of time (installation parameter LOCK TIMEOUT) because transactions with SQL statements for data modification are still open. The SERVERDB has not been shut down.

User Action:

1.	In some cases, the error message contains a more detailed description of the error. The lock request can be reissued. To avoid possible deadlock situations, it is advisable to roll back the transaction by using a <rollback statement>.

2.	Do without the SHUTDOWN or force a shutdown of the SERVERDB using Operating / Shutdown / Quick.


600 WORK ROLLED BACK

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>, because

1.	you failed to carry out any ADABAS operations within a certain period of time (installation parameter LOCK TIMEOUT) but held locks which other users were waiting for, or because

2.	the SERVERDB was in a deadlock situation. A deadlock situation is a situation in which two or more users hold locks and request further locks that are held by the respective other users. In the simplest case of two users, one user holds one lock and requests another lock. But this lock is held by another user who, on the other hand, waits for the lock held by the first user. This situation can only be resolved, if one of the users releases the lock already obtained.

User Action:

In some cases, the error message contains a more detailed description of the error.

In both cases, the lock requests must be checked and modified, if necessary. The last transaction must be repeated.

It may also be necessary to check and modify the value of the installation parameter LOCK TIMEOUT.


650 WORK ROLLED BACK

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>.

There is one of two possible causes.

1.	The log is full.

2.	In case of a distributed database, the connection to another SERVERDB is interrupted.

User Action:

The error message contains a more detailed description of the error.

1.	The log must be saved. For details, see the CONTROL online help.

2.	It should be ensured that the Operating / Restart / Warm menu function in the ADABAS component CONTROL is performed for the disconnected SERVERDB. Should this not be sufficient, reestablish the connection at operating system level.


700 SESSION INACTIVITY TIMEOUT (WORK ROLLED BACK)

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>. The ADABAS session was implicitly terminated, since you failed to carry out any ADABAS operations within a certain period of time (installation parameter SESSION TIMEOUT or TIMEOUT value specified with the <connect statement>).

User Action:

Repeat the <connect statement> and specify a larger TIMEOUT value, if necessary.

It may also be necessary to check and modify the value of the installation parameter SESSION TIMEOUT.


750 TOO MANY SQL STATEMENTS (WORK ROLLED BACK)

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>. The ADABAS session was implicitly terminated, since you had issued too many SQL statements or had performed too many transactions within a session.

User Action:

The transaction can be repeated after a new <connect statement>.


802 NUMERIC OPERATION EXCEPTION ERROR

Explanation:

In numeric operations on the database, an overflow or a division by 0 occurred, or the conversion of a value having an ADABAS data type into a programming language data type or vice versa failed.

User Action:

Check the definition and content of the column on which the operation should be performed. Modify the operation, the column definition, or the programming language data type.


12001 Message Number: <12...>         Parameter: <text or number>

Explanation:

This message is output when the actual message text is not loaded. If the actual text contains a parameter, the corresponding character string is set for <text or number>; otherwise, the message only consists of the first part. <12...> always is the number of the actual message.

User Action:

The displayed message number helps you to find the actual message. Continue reading there.


12003 <table>: inserted <number>, rejected <number> lines

Explanation:

This message is repeatedly output during a DATALOAD run only for informational purposes. For <table>, the table name is displayed; for <number>, the corresponding numeric values are shown.

User Action:

A user action is not required.


12004 <table>: <number> lines updated, <number> lines invalid

Explanation:

This message is repeatedly output during a DATAUPDATE run only for informational purposes. For <table>, the table name is displayed; for <number>, the corresponding numeric values are shown.

User Action:

A user action is not required.


12005 Sum of updates <number>, sum of invalid lines <number>

Explanation:

This message is output at the end of a DATAUPDATE run only for informational purposes. It is also written to the LOAD PROT file. For <number>, the corresponding numeric values are displayed.

User Action:

A user action is not required.


12006 Sum of inserted lines <number>, sum of rejected lines <number>

Explanation:

This message is output at the end of a DATALOAD run only for informational purposes. It is also written to the LOAD PROT file. For <number>, the corresponding numeric values are displayed.

User Action:

A user action is not required.


12007 Last transaction committed at input line <number>

Explanation:

For <number>, the number of the last line of file successfully processed is displayed.

User Action:

If the load run was cancelled for some reasons, it can be continued using RUN FROM <the number indicated in the message + 1>.


12008 Rows written : <number>

Explanation:

A DATAEXTRACT statement generated as many output lines as are indicated in the message.

User Action:

A user action is not required.


12010 Other errors

Explanation:

The errors occurred during a session are added up for each error number at the end of the protocol file. If too many different errors occurred, they are not shown individually but are summarized under this heading.

User Action:

A user action is not required.


12900 No syntax errors detected, execution begins...

Explanation:

This message occurs when the statement was started with RUN and the syntax check terminated successfully. In case of large intervals between the ends of transaction, it may take some time until the next message will appear.

User Action:

A user action is not required.


12901 <text> definitions are currently generated

Explanation:

This message is output with various parameters such as USER, TABLE, INDEX, etc., for example, while executing CATALOGEXTRACT to inform the user about what is happening.

User Action:

A user action is not required.


12902 SQL statement successfully executed

Explanation:

This message corresponds to the SQL return code 0.

User Action:

A user action is not required.


12903 SELECT or SHOW successful, LOAD does not display results

Explanation:

LOAD executed the SELECT or SHOW statement without detecting any error.

User Action:

Use QUERY/REPORT to display the results.


12904 The specified number of rows has been loaded

Explanation:

The load run was terminated, because the number of rows specified as RUN option had been loaded.

User Action:

A user action is not required.


12905 Execution terminated

Explanation:

This message occurs when a CATALOGEXTRACT or TABLEEXTRACT run was terminated without an error.

User Action:

A user action is not required.


12906 No syntax errors detected

Explanation:

The statement was started with RUN FROM 0 or RUN FOR 0; i.e., it should only be checked for syntactical correctness.

User Action:

A user action is not required.


12907 Now processing <text> data of table <table name>

Explanation:

This message is output with various parameters such as PRIMARY, RAW, LONG RAW, INDEX, etc., only for informational purposes, e.g., while executing TABLEEXTRACT.

User Action:

A user action is not required.


12908 LOAD statement successfully executed

Explanation:

A LOAD statemen, such as setting the SQLMODE, enabling or disabling AUTOCOMMIT, changing the database, was executed successfully.

User Action:

A user action is not required.


12910 HELP will display information concerning this error

Explanation:

When this message occurs, the HELP function of LOAD immediately shows the chapter where you may find the information possibly needed.

User Action:

If you are not sure why LOAD returned an error and how you could correct it, press the [image] key.


12920 If you want to leave, please press END again

Explanation:

You are prevented from leaving the tool components at once by inadvertently pressing the [image] key. Two strokes of the [image] key therefore correspond to the EXIT function.

User Action:

Press the [image] key again if you want to terminate LOAD.


12921 Costwarning: for execution enter RUN again

Explanation:

This message occurs when the parameter COSTWARNING is set and the DATAEXTRACT statement is about to perform a relatively costly SELECT.

User Action:

Your can decide by keystroke whether the command is to be executed or to be aborted. The corresponding key assignment is displayed.


12922 Attention, no CREATE TABLE statement (VIEW or no OWNER privilege)

Explanation:

A DATAEXTRACT FOR DATALOAD statement does not generate a CREATE TABLE statement, because the specified table is not your base tabl. The DATALOAD statement, however, is generated and the data is extracted.

User Action:

Press any key to acknowledge that you read the warning.


12923 Not all tables could be loaded

Explanation:

During a TABLELOAD USER or TABLELOAD ALL run, some tables of the input file could not be loaded, e.g., because no corresponding target table existed or because the definitions of source and target table were too different. The lines of the input file concerning these tables have been copied into the error file.

User Action:

Look into the LOAD prot file for more details.


12924 CLUSTER part has been ignored

Explanation:

A CREATE TABLE statement in an ORACLE export file contained a CLUSTER definition for which there is no equivalent in ADABAS.

User Action:

The LOAD protocol file contains the names of the tables concerned.


12930 Please mount next tape, then press function key to go on

Explanation:

The file option COUNT was specified for an unload statement. The number of data records specified thereafter was written.

User Action:

Change the tape and press the key [image] if the run is to be continued. Press the [image] key to cancel the run instead.


12931 Please mount tape no <number> (this is tape no <number>)

Explanation:

This message occurs for multi-volume processing (file option COUNT). The tapes must be mounted in the order they were written.

User Action:

Mount the tape the current number of which is output in the message.


12940 Difference fixed/variable length, take over the source table definition?

Explanation:

This message occurs during a TABLELOAD run when a column of the target table is defined in such a way that its values must be stored with a fixed length, but the corresponding columns in the source table only contain values of variable length.

User Action:

If you decide to continue the execution, the definition of the source table is taken over and neither the values taken over nor the values inserted later are stored as fixed-length values. Otherwise, the TABLELOAD run is continued with the next table.


12941 DROPPED COLUMNS, takeover of the source table definition acceptable?

Explanation:

This message occurs during a TABLELOAD run when source and target table look the same but differ internally, because the source table contains "invisible", dropped, columns which have not been created in the target table.

User Action:

If you decide by keystroke to continue the execution, the history of the source table concerning the dropped columns is taken over for the target table. But you may also abort the loading of the table. In this case, the TABLELOAD run is continued with the next table.


12942 Different constraints, take over the source table definition?

Explanation:

This message occurs during a TABLELOAD run when existing RANGE or CONSTRAINT conditions differ for the source and target table.

User Action:

If you decide to continue the execution, the respective definitions of the source table are transferred to the target table. CONSTRAINTS that possibly exist in the target table are deleted. Otherwise, the TABLELOAD run is continued with the next table.


12943 Default values differ - generate the same state as in the source file?

Explanation:

This message occurs during a TABLELOAD run when the existing defaults differ for the source and target table.

User Action:

If you decide to continue the execution, defaults like those extracted from the source table are defined for all columns of the target table. Otherwise, the TABLELOAD run is continued with the next table.


12944 INDEX definitions differ - generate the same state as in the source file?

Explanation:

This message occurs during a TABLELOAD run when different indexes were constructed across source and target table.

User Action:

If you decide to continue the execution, all INDEX definitions are dropped which do not have an equivalent in the source table. If index data is available in the source file without corresponding INDEX definitions in the target table, this data is created implicitly. Otherwise, the TABLELOAD run is continued with the next table.


12945 Data types differ - generate the same state as in the source file?

Explanation:

This message occurs during a TABLELOAD run when the source and target table differ from each other.

User Action:

If you decide to continue the execution, the complete description of the source table is taken over; i.e., after loading, the target table has the column names and column definitions as were used in the source table. Otherwise, the TABLELOAD run is continued with the next table.


12950 SQLMODE &1, AUTOCOMMIT OFF

Explanation:

The statement was executed in <sqlmode> mode. The transaction was not concluded thereafter, because AUTOCOMMIT OFF is valid.

User Action:

A user action is not possible.


12951 SQLMODE &1; AUTOCOMMIT

Explanation:

The statement was executed in <sqlmode> mode. The transaction was concluded with COMMIT WORK, because AUTOCOMMIT ON is valid.

User Action:

A user action is not possible.


12952 SQLMODE &1; NOLOG

Explanation:

The statement was executed in <sqlmode> mode. You are working in NOLOG mode.

User Action:

A user action is not possible.


12990 LOAD run aborted

Explanation:

The load run was aborted either because the number of rejected rows specified as RUN option was reached at least once and the [image] key was pressed during the interruption, or because an error occurred which did not allow the load run to be continued.

User Action:

A user action is not required.


12991 Overflow occurred, execution aborted

Explanation:

A numeric value cannot be represented in the desired INTEGER format.

User Action:

Select the format REAL or CHAR for the output.


12992 Execution of control file aborted (RETURN statement executed)

Explanation:

The control file just executed contains a RETURN that was recognized as a statement that must not be skipped. RETURN has the effect that the control file is closed but LOAD is not left.

User Action:

A user action is not required.


13001 SQL command successfully executed

Explanation:

An SQL statement was executed with return code 0.

User Action:

A user action is not required.


13002 Command successfully executed

Explanation:

An EXPORT, IMPORT, GRANT command, etc. executed in connection with a stored command was successful.

User Action:

A user action is not required.


13003 <number> row(s) updated

Explanation:

An SQL UPDATE statement updated the displayed number of rows.

User Action:

A user action is not required.


13004 <number> row(s) deleted

Explanation:

An SQL DELETE statement deleted the displayed number of rows.

User Action:

A user action is not required.


13005 To quit the QUERY session restrike END

Explanation:

For security reasons, QUERY is not left when the [image] key is pressed only once.

User Action:

Pressing the [image] key after this message has the same effect as the command EXIT. Pressing another key reestablishes the initial state in which the [image] key yields this message.


13006 Costwarning: for execution enter RUN again

Explanation:

This message corresponds to the SQL error message -4.

User Action:

You can execute the SQL statement in spite of the warning or cancel it.


13007 Command rejected - command buffer empty

Explanation:

RUN, SAVE, or STORE was executed for an empty input area.

User Action:

A user action is not required.


13008 No entries in command history

Explanation:

The command NEXT or PREV was issued, but no command had previously been entered into the command history.

User Action:

A user action is not required.


13009 Bottom of command history

Explanation:

The command NEXT was issued, but there are no more statements.

User Action:

A user action is not required.


13010 Top of command history

Explanation:

The command PREV was issued, but there is no previous statement.

User Action:

A user action is not required.


13011 Command name too long - truncated to 18 characters

Explanation:

Names of stored QUERY commands may have a maximum length of 18 characters.

User Action:

A user action is not required.


13012 Reconnected after timeout

Explanation:

A database TIMEOUT took place and the user has been reconnected to the database.

User Action:

A user action is not required.


13013 Result may be incomplete, some locations are not accessible

Explanation:

The database yields a warning if not all locations in a distributed system are accessible.

User Action:

A user action is not required.


13014 The result is the following command

Explanation:

If you press the key [image], you see the SQL statement resulting from a form.

User Action:

A user action is not required.


13015 Command not executed

Explanation:

The stored QUERY command started with RUN was not executed, because the layout form provided for the input of parameters had been left using the [image] key.

User Action:

Restart the command, if necessary.


13016 No commands found

Explanation:

No stored QUERY commands matching the search pattern were found using LIST or GRANT.

User Action:

A user action is not required.


13019 SQLMODE : ANSI

Explanation:

QUERY is working in ANSI mode.

User Action:

A user action is not required.


13020 SQLMODE : ORACLE

Explanation:

QUERY is working in ORACLE mode.

User Action:

A user action is not required.


13021 SQLMODE : DB2

Explanation:

QUERY is working in DB2 mode.

User Action:

A user action is not required.


13022 SQLMODE : ADABAS

Explanation:

QUERY is working in ADABAS mode.

User Action:

A user action is not required.


14101 Bottom reached

Explanation:

When scrolling through the result table, the bottom row was reached.

User Action:

A user action is not required.


14102 Top reached

Explanation:

When scrolling through the result table, the top row was reached.

User Action:

A user action is not required.


14103 Leftmost column reached

Explanation:

When scrolling through the result table, the leftmost column was reached.

User Action:

A user action is not required.


14104 Rightmost column reached

Explanation:

When scrolling through the result table, the rightmost column was reached.

User Action:

A user action is not required.


14105 Output on printer

Explanation:

The logical print file is closed and the order for actual printing was given.

User Action:

A user action is not required.


14106 Nothing to print

Explanation:

The logical print file is empty.

User Action:

A user action is not required.


14107 Result table printed -  for immediate output press PRINT again

Explanation:

The desired text was stored in the logical print file.

User Action:

If the printout is needed at once, press the [image] key again. Otherwise, all print orders are collected and performed at the session's end.


14108 PUT command executed

Explanation:

The desired text was stored in the specified file.

User Action:

A user action is not required.


14109 Warning: command history overflow

Explanation:

The last executed statement cannot be stored in the command history.

User Action:

A user action is not required.


14110 value too large, maximum value assumed

Explanation:

The maximum column width for alpha values is 80. Such values can extend across a maximum of eight lines.

User Action:

A user action is not required.


14111 Result table printed, for immediate output enter CLOSE

Explanation:

The desired text was stored in the logical print file.

User Action:

If the printout is needed at once, close the print file with CLOSE. Otherwise, all print orders are collected and performed at the session's end.


14112 No DETAIL rows found

Explanation:

No detail rows matching the current master row were found for the master-detail representation.

User Action:

A user action is not required.


21200 Repeat Password

Explanation:

The password must be entered twice. The entries must be identical.

User Action:

Enter the password a second time.


21201 To choose a parameter: place the cursor and press <ENTER>

Explanation:

A parameter can be explicitly selected in MENU or CHECK mode by placing the cursor on the parameter identifier and then pressing the [image] key. The user thus changes to the INSERT mode.

In MENU mode, the available XPARAM parameters are displayed. In CHECK mode, the error messages are displayed. If it is not possible to access the parameter in CHECK mode, the MENU mode is activated.

User Action:

Select a parameter to enter a value.


21203 CONDITIONS: NO ERRORS DETECTED

Explanation:

The consistency check terminated without having detected any errors.

User Action:

A user action is not required.


21204 PLEASE CHECK PROTFILE

Explanation:

When leaving XPARAM via [image], a consistency check of the parameters is implicitly performed. The errors thus detected are written to the XPARAM protocol file.

This message indicates that an error occurred during the final consistency check.

User Action:

Check the XPARAM protocol file. A consistent XPARAM file can only have been created when the XPARAM protocol file does not contain any error messages.

As result of the consistency check, error and status messages are stored in the XPARAM protocol file. Error messages are identified by their negative numbers.


21205 Press <ENTER> after input

Explanation:

The XPARAM program works directly on the XPARAM file. The parameters and their values which you see in MENU mode were directly read from the XPARAM file. In INSERT mode, a value is directly written to the XPARAM file. The [image] key must be pressed explicitly to confirm the entry.

User Action:

Press [image] to input the value.


21206 NEW INPUT NOT ALLOWED

Explanation:

This parameter cannot be modified by the user.

User Action:

A user action is not required.


21207 PARAMETER ENTRY STORED

Explanation:

The XPARAM program works directly on the XPARAM file. In INSERT mode, a value is directly written to the XPARAM file. This message confirms the input of a value.

User Action:

A user action is not required.


21208 To use the default value as new input: press <GET-DEF>

Explanation:

The displayed default value has not yet been accepted as parameter value. It will be entered into the XPARAM file by pressing the [image] key.

User Action:

The user either accepts the value - using the [image] key - or does not accept it (using any other key). Especially, if you press the [image] key, not the default value is entered into the XPARAM file but, as usual, the value specified by the user.


21209 Create a copy of the XPARAM file

Explanation:

After specifying a new SERVERDB name, a copy of the current XPARAM file is created. There must not be an XPARAM file with this name. The new copy contains almost the same parameters and values as the current XPARAM file. The only difference is that the SERVERDB gets the new name and that the values SYSDEVSPACE, LOGDEVSPACE, RUNDIRECTORY are not set to values in the copy of the XPARAM file.

User Action:

A copy can be created, the MENU mode be called, or the program be left.


21210 Repeat password for XPARAM file creation. Otherwise press <EXIT>

Explanation:

There is no XPARAM file available to the values entered in the login screen. Therefore, XPARAM tries to create a new XPARAM file.

The password must be entered twice. The entries must be identical.

After entering the password a second time, a new XPARAM file is created. The data of the login screen are entered into the XPARAM file as values. The 'USERNAME' is entered as COLDUSER, the 'PASSWORD' as COLDPASSWORD, and the 'DBNAME' as SERVERDB.

User Action:

To create the XPARAM file, enter the password a second time. To cancel the program, press the [image] key.


21211 Your OWN value exceeds the COMPUTED value ! Which one do you like ?

Explanation:

This message can occur with selected parameters. For these parameters, it can occur with all CALC statements, but not with other statements. This means, the value stored in the XPARAM file (called 'OWN' value) is greater than the value resulting from the CALC statement ('COMPUTED'). Both values are displayed at the screen.

User Action:

Use the key [image] or [image], respectively, to select the desired value.


21212 Your OWN value is different from the COMPUTED value! What do you like?

Explanation:

This message can occur with selected parameters. For these parameters, it can occur with all CALC statements, but not with other statements. This means, the value stored in the XPARAM file (called 'OWN' value) is different from the value resulting from the CALC statement ('COMPUTED'). Both values are displayed at the screen.

User Action:

Use the key [image] or [image], respectively, to select the desired value.


21213 CHECK RUNDIRECTORY VALUE

Explanation:

Within the XPARAM login screen, the SERVERDB name was modified. The value of the parameter 'RUNDIRECTORY' generally depends on the name of the SERVERDB. Therefore the RUNDIRECTORY value can be wrong now.

User Action:

Check the value of the RUNDIRECTORY and modify it, if necessary.


21400 to 21405

Explanation:

These messages inform about the internal execution of the consistency check.

User Action:

A user action is not required.


23000 You cannot add more than X tables to a query design!

Explanation:

No more tables can be added to the query design.

User Action:

It could be necessary to reduce the number of tables for the query design.


23001 No access to the ADABAS QueryPlus management table! Do you want to create it locally?

Explanation:

QueryPlus could not access its management tables in the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


23002 Replace existing query?

Explanation:

There is already a query with the specified name.

User Action:

If the existing query is to be overwritten, confirm the question with Yes. If the existing query is not to be overwritten, interrupt the saving procedure with No.


23003 Replace existing SQL statement?

Explanation:

There is already an SQL statement with the specified name.

User Action:

If the existing SQL statement is to be overwritten, confirm the question with Yes. If the existing SQL statement is not to be overwritten, interrupt the saving procedure with No.


23004 Dialog was canceled.

Explanation:

You interrupted the current process in a DDE communication.

User Action:

The further operation of this DDE communication should be canceled as well.


23005 Terminate existing DDE communication?

Explanation:

This case occurs frequently when QueryPlus was called out of another program and is to be terminated without ending the process that has been started within QueryPlus from the other program. If the answer to this question is Yes, i.e., if the DDE communication is interrupted explicitly, data may be lost.

User Action:

The process initiated by the DDE communication should be ended before terminating QueryPlus.


23006 DDE channel busy!

Explanation:

There can only be one DDE communication with QueryPlus at any one time.

User Action:

Wait until the active DDE communication has been terminated.


23007 Unknown table:

Explanation:

A query used within a table does not exist in the database.

User Action:

Modify the query or insert the table into the database.


23008 Empty command!

Explanation:

An empty query or SQL statement was saved. This means, the query does not contain any columns that could be displayed or the SQL statement does not contain any text.

User Action:

Either use another query or SQL statement or modify the query or SQL statement.


23009 No result!

Explanation:

The query does not produce any result set.

User Action:

Modify the query.


23010 Replace existing MS-Word link?

Explanation:

There is already an MS-Word link with the specified name.

User Action:

If the existing MS-Word link is to be overwritten, confirm the question with Yes. If the existing MS-Word link is not to be overwritten, interrupt the saving procedure with No.


23011 Replace existing MS-Excel link?

Explanation:

There is already an MS-Excel link with the specified name.

User Action:

If the existing MS-Excel link is to be overwritten, confirm the question with Yes. If the existing MS-Excel link is not to be overwritten, interrupt the saving procedure with No.


23012 Cannot quit QueryPlus at this time!

Explanation:

QueryPlus cannot be terminated at this point in time, because it is within a transaction which cannot be interrupted.

User Action:

Wait until the database transaction which cannot be interrupted has been terminated.


23013 No link data selected!

Explanation:

No query or SQL statement has been selected for opening or deletion.

User Action:

Select the query or SQL statement to be opened or deleted.


23014 QueryPlus is already running!

Explanation:

QueryPlus cannot be started several times because otherwise, it would be impossible to ensure a unique DDE communication.

User Action:

Use the started QueryPlus or terminate and restart it.


23015 Cannot find the language file

Explanation:

QueryPlus cannot find the file containing the messages for the specified language. In this case, QueryPlus attempts to load the file with the English messages. If QueryPlus cannot find this file either, the messages cannot be displayed correctly.

User Action:

Your adminsitrator must install the required file.


23016 Cannot fetch complete result!

Explanation:

QueryPlus could not load the whole query result.

User Action:

None


23017 Cannot delete because you are not the owner!

Explanation:

QueryPlus cannot delete the object. A user can only delete his own objects.

User Action:

Either define in QueryPlus that only your own objects are displayed; or the owner of the object to be deleted must end the sharing procedure.


23018 You cannot design because you have not the permission!

Explanation:

QueryPlus can only display objects to be modified if you have the corresponding privileges for them.

User Action:

The owner of the objects must grant the privileges for modification when sharing the objects.


23019 No data transfer while fetching!

Explanation:

While loading data from the database, QueryPlus is not able to copy data into the clipboard or into a file or to transfer data into an application via DDE.

User Action:

Wait until the data has been loaded.


23020 Rows to fetch for the first page is too small!

Explanation:

To display the result, QueryPlus attempts to load at least 10 rows for the first page.

User Action:

Set the value to at least 10.


23021 Rows to fetch for the next pages is too small!

Explanation:

To display the result, QueryPlus attempts to load at least 10 rows for the next page.

User Action:

Set the value to at least 10.


23022 Cannot get all stored SQL statements!

Explanation:

Not all SQL statements are available for sharing.

User Action:

A user action is not possible.


23023 Cannot get all stored Queries!

Explanation:

Not all queries are available for sharing.

User Action:

A user action is not possible.


23024 Cannot get all stored Word links!

Explanation:

Not all Word links are available for sharing.

User Action:

A user action is not possible.


23025 Cannot get all stored Excel links!

Explanation:

Not all Excel links are available for sharing.

User Action:

A user action is not possible.


23026 Cannot get all users!

Explanation:

Not all database users are available while sharing objects.

User Action:

A user action is not possible.


25000 Not Connected

Explanation:

The attempt was made to assign an SQL statement to the 'SQLStmt' property. But the current SQLControl was not yet connected to the database.

User Action:

The SQLControl must be first connected to a database, either by assigning a connect string to the 'Connect' property, or by joining to an existing session by assigning a Control name to it.

Or, you must use the Connect Box at design time to assign a session to the SQLControl.


25100 <ODBC Error Text>

Explanation:

An ODBC error occurred during a database access. The error text gives more information.

User Action:

Check the ODBC error text, and consult the ODBC documentation for more information.


25101 Unknown ODBC Error

Explanation:

An ODBC error occurred during a database access, but it was not possible to obtain further information. Maybe the memory is full.

User Action:

A user action is not required.


25200 No corresponding control for variable '<name>'

Explanation:

The SQL statement contains a parameter ':<name>', but no control <name> exists in the same form.

User Action:

Change the parameter's name, check the existing controls, or use question marks ('?') to specify parameters.


25201 No Value Property for control '<name>'

Explanation:

The SQL statement contains a parameter ':<name>', but this control contains no default value property. (Assignments <name> = <value> are not possible.)

User Action:

Use another control or question marks ('?') to specify parameters.


25202 Unsupported Data Type

Explanation:

The control specified by a parameter in the 'SQLStmt' property of the SQLControl has a data type not supported by SQLControl.

User Action:

Supported types are:

Strings,

Short integers,

Long integers,

Booleans (short integers),

Color values (long integers),

Enumerated types,

Real numbers.

If necessary, use question marks ('?') to specify parameters, and the 'ParameterList' property to access them.


25203 Wrong Name for Session Control

Explanation:

The attempt was made to connect an SQLControl to another session, but the control specified is not an SQLControl, or this control is not connected to a database.

User Action:

Specify an SQLControl connected via ODBC to a database as control.


25204 No parameters in statement

Explanation:

The attempt was made to access the 'DataTypes' or 'ParameterList' property array; but the 'SQLStmt' property contains no SQL statement with parameters.

User Action:

These property arrays must not be accessed when an SQL statement without parameters is the active statement.


25205 No statement executed

Explanation:

The attempt was made either to access a property of the SQLControl like e.g. 'ExecSQL', 'ColumnCount', 'ColumnList', or to press the SQLControl button, but there is no SQL statement currently assigned to the 'SQLStmt' property.

User Action:

These properties may only be accessed when an SQL statement is active.


25206 No controls to bind to

Explanation:

The attempt was made to open the Bind Columns dialog box, but there are no controls with a default value property in the current form except the SQL Form control itself.

User Action:

Controls must be defined to obtain Column Values from SQLForm, or the 'ColumnList' property array must be used instead.


25299 You installed an earlier version of <name>.  Some features  of VBPlus will not work.

Explanation:

The ADABAS ODBC Driver used is older than the version of VBPlus. The application will do, but some features will not work.

User Action:

A new version of the ADABAS ODBC Driver should be bought as soon as possible.


25300 DataSource not connected or RecordSource not set

Explanation:

The attempt was made to assign the name of a DataControl to the 'DataSource' property of SQLForm, but this control is not yet properly set up.

User Action:

First, assign a value either to the 'Connect' or to the 'Database' property, then to the 'RecordSource' property.


25301 Property cannot be changed in this state of the form

Explanation:

The attempt was made either to change the 'Visible' or 'DataSource' property when SQLForm had already generated Labels and DataBoxes, or to change the 'Active' property before the generation of the form.

User Action:

To change the 'Visible' or 'DataSource' property, all generated controls must be deleted first.

The change of the 'Active' property, however, is meaningless before a form has been generated.


25302 There must be at least two data controls for Master-Detail

Explanation:

The MasterDetail property was clicked for the master-detail box, but there is no second data control in the current form.

User Action:

At least two data controls are required to generate master-detail relations. Define a second data control. Set its 'Connect' or 'Database' property and its 'RecordSource' property.


25500 RecordSource too complicated: <statement>

Explanation:

The 'RecordSource' property of the Data Control specified by the 'SelectData' property of a DataBox contains an expression too complicated for the DataBox.

User Action:

Only plain table names or simple select statements (no ORDER BY etc.) are supported for Record Sources in 'SelectData' Controls.


25501 Wrong SelectData Property

Explanation:

The 'SelectData' property was assigned a value that is not the name of a DataControl.

User Action:

Check the assigned value, or use the property box for the correct assignment of this property.


25502 Not valid for this data type: <item>

Explanation:

The SelectOp property has been assigned a value not allowed for this data type. The 'like' and 'starts with' select operations are allowed only for character data.

User Action:

Use one of the other operations.


25503 Datatype '<type>' of field '<name>' not supported for  automatic select

Explanation:

The data type of the given field is not supported for automatic select.

User Action:

Supported types are: INTEGER, LONG and TEXT.


25504 'SelectData' or 'SelectField' property not set

Explanation:

The 'SelectOp' property may only be set when the 'SelectData' and 'SelectField' properties have been assigned a value.

User Action:

The 'SelectData' and 'SelectField' properties must first be set.


25505 Invalid value for automatic select: field '<name>'

Explanation:

An automatic select had been defined for a DataControl by the 'SelectData' and 'SelectField' properties. But the current content of this DataBox is not a valid value for the data type of this field.

User Action:

A value according to the data type must be used.


25900 Error in Event Procedure

Explanation:

An error occurred when calling an event procedure. Maybe the control has been destroyed during one of its event procedures.

User Action:

none


25901 Error <no> loading <name>

Explanation:

An error occurred when loading the ADABAS ODBC Driver. Maybe an older version of the ADABAS ODBC Driver is used, or one of the DLLs called by this driver is corrupt.

<no> may have the following values:

User Action:

Check all ADABAS DLLs and their paths. If necessary, a new installation should be made.


25902 Fatal error in ODBC Driver <name>

Explanation:

Because of a fatal error during load of the ADABAS ODBC Driver, VBPlus stopped loading.

User Action:

Check the error previously displayed.


25903 This version of Visual Basic is not supported by VBPlus

Explanation:

As Visual Basic Version 3.0 or higher is requested for VBPlus, this version of Visual Basic cannot be used.

User Action:

A new version of Visual Basic should be installed to work with VBPlus.


25904 This new version of Visual Basic is not yet supported by your version of VBPlus

Explanation:

The current version of Visual Basic is not yet supported by VBPlus, but it will be in the future. Maybe VBPlus will work anyway, but this is not sure.

User Action:

Check VBPlus and go on at your own risk. A new version will be shipped as soon as possible.


25906 Not enough memory

Explanation:

An internal memory operation was not successful.

User Action:

As probably too many Windows components are running, closing some of them will succeed.


25999 System Error <nr>

Explanation:

An unexpected error occurred during a VBPlus session.

User Action:

You should note the number specified in the error message and contact the ADABAS support.


-1 DUPLICATE KEY IN INDEX

Explanation:

There is already a table row with the specified secondary key. UNIQUE was specified for the secondary key.

User Action:

To avoid a key value collision, correct the value of the key to be inserted in the SQL statement.

The error message specifies the column or multiple-column index already containing the specified values.


-8 EXECUTION FAILED, PARSE AGAIN

Explanation:

The parse identification (parsid) became invalid by modifications made to the ADABAS catalog during parsing and executing a statement.

User Action:

Reparse the statement.


-20 DUPLICATE KEY

Explanation:

There is already a table row with the key to be inserted.

User Action:

Check whether the existing table row contains the desired values. If this is not the case, check whether values in the existing table row can be replaced with the desired values. If a new table row must be inserted, change the value of the key to be inserted in order to prevent key collisions.


-25 DUPLICATE SECONDARY KEY

Explanation:

There is already a table row with the specified secondary key. UNIQUE was specified for the secondary key.

User Action:

Correct the value of the secondary key to be inserted in the SQL statement in order to avoid a key value collision.

The error message specifies the column or multiple-column index already containing the specified values.


-30 INTEGRITY VIOLATION

Explanation:

Insertions or updates would violate integrity constraints specified in the base or view table definition.

User Action:

The error message specifies the column which would violate the integrity constraints.

Correct the input value for the corresponding column.


-32 VIEW VIOLATION

Explanation:

An <insert statement> or <update statement> was issued for a view table. At least one of the rows specified in the SQL statement does not satisfy the <search condition>s of all underlying view tables defined 'WITH CHECK OPTION'.

User Action:

Display the definition of the view table using a <query statement> issued on the system table DOMAIN.VIEWDEFS. Correct the <insert statement> or <update statement> according to this definition.


-35 REFERENTIAL INTEGRITY VIOLATED

Explanation:

There are three possible causes:

1.	An <insert statement> or <update statement> issued on a table that is the referencing table in a <referential constraint definition> produces a row that is not a matching row of the <referential constraint definition>.

2.	When deleting rows from a <referenced table> of a <referential constraint definition> with <action> RESTRICT in the <delete rule>, a matching row exists.

3.	When executing a <referential constraing definition>, the <referenced table> or referencing table contains rows which conflict with the definition of the <referential constraint definition> to be created.

User Action:

1.	Display the definition of the <referential constraint definition> using a <query statement> issued on the system table DOMAIN.COL_REFS_COL. Correct the <insert statement> or <update statement> according to this definition.

2.	Use an appropriate <query statement> to determine which row of the referencing table prevents the desired <referenced table> rows from being deleted.

3.	Use an appropriate <query statement> to determine which row of the <referenced table> or referencing table conflicts with the <referential constraint definition> to be created. Modify or delete the row concerned, or correct the <referential constraint definition> to be created.


-36 FOREIGN KEY INTEGRITY VIOLATION

Explanation:

In case of an <insert statement> or <update statement> issued on a join view table, the column values functionally depending on the <referencing column>s of the referencing table conflict with the already existing column values.

User Action:

This conflict may be solved by changing either the column values specified in the <insert statement> or <update statement>, or the already existing values.


-40 LOCK COLLISION

Explanation:

When the option '(NOWAIT)' is specified in the <lock statement> or in the <lock option>, this error message signals that the lock request conflicts with the locks of other users.

User Action:

1.	In interactive mode, another job can be activated which does not require the desired lock.

2.	As an alternative, you can wait for the lock being released by specifying the same SQL statement without '(NOWAIT)' option.


-50 LOCK REQUEST TIMEOUT

Explanation:

The lock request or an implicit lock conflicts with the locks of another user. The maximum waiting time for granting the lock has elapsed (installation parameter REQUEST TIMEOUT).

User Action:

In some cases, the error message contains a more detailed description of the error.

The lock request can be reissued. To avoid possible deadlock situations, it is advisable to roll back the transaction by using a <rollback statement>.


-51 LOCK REQUEST TIMEOUT

Explanation:

The lock request or an implicit lock conflicts with the locks of another user. The maximum waiting time for granting the lock has elapsed (installation parameter REQUEST TIMEOUT).

User Action:

In some cases, the error message contains a more detailed description of the error.

The lock request can be reissued. To avoid possible deadlock situations, it is advisable to roll back the transaction by using a <rollback statement>.


-54 LOCK COLLISION

Explanation:

When the option '(NOWAIT)' is specified in the <lock statement> or in the <lock option>, this error message signals that the lock request conflicts with the locks of other users.

User Action:

1.	In interactive mode, another job can be activated which does not require the desired lock.

2.	As an alternative, you can wait for the lock being released by specifying the same SQL statement without '(NOWAIT)' option.


-60 WORK ROLLED BACK

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>, because

1.	you failed to carry out any ADABAS operations within a certain period of time (installation parameter LOCK TIMEOUT) but held locks which other users were waiting for, or because

2.	the SERVERDB was in a deadlock situation. A deadlock situation is a situation in which two or more users hold locks and request further locks that are held by the respective other users. In the simplest case of two users, one user holds one lock at least and requests another lock. But this lock is held by another user who, on the other hand, waits for the lock held by the first user. This situation can only be resolved, if one of the users releases the lock already obtained.

User Action:

In some cases, the error message contains a more detailed description of the error.

In both cases, the lock requests must be checked and modified, if necessary. The last transaction must be repeated.

It may also be necessary to check and modify the value of the installation parameter LOCK TIMEOUT.


-65 WORK ROLLED BACK

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>.

There is one of two possible causes.

1.	The log is full.

2.	In case of a distributed database, the connection to another SERVERDB is interrupted.

User Action:

The error message contains a more detailed description of the error.

1.	Save the log. For details, see the CONTROL online help.

2.	It should be ensured that the Operating / Restart / Warm menu function in the ADABAS component CONTROL is performed for the disconnected SERVERDB. Should this not be sufficient, reestablish the connection at operating system level.


-70 SESSION INACTIVITY TIMEOUT (WORK ROLLED BACK)

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>. The ADABAS session was implicitly terminated, since you failed to carry out any ADABAS operations within a certain period of time (installation parameter SESSION TIMEOUT or TIMEOUT value specified with the <connect statement>).

User Action:

Repeat the <connect statement> and specify a larger TIMEOUT value, if necessary.

It may also be necessary to check and modify the value of the installation parameter SESSION TIMEOUT.


-75 TOO MANY SQL STATEMENTS (WORK ROLLED BACK)

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>. The ADABAS session was implicitly terminated, since you had issued too many SQL statements or had performed too many transactions within a session.

User Action:

The transaction can be repeated after a new <connect statement>.


-101 SQL STATEMENT NOT AVAILABLE IN THIS DB MODE

Explanation:

The issued SQL statement requires that the system is either in COLD or in WARM mode. This error message may occur, because

1.	either the Operating / Restart / Warm menu function or the Operating Shutdown menu function should be performed in the ADABAS component CONTROL, or

2.	an implicit SHUTDOWN was performed after the errors -900 DATA SPACE FULL (EMERGENCY SHUTDOWN), -901 LOG FULL (EMERGENCY SHUTDOWN), or after system errors.

User Action:

The system can be put into COLD mode using the Operating / Shutdown menu function in the ADABAS component CONTROL.

After error correction, if needed, the ADABAS system can be put into WARM mode using the Operating / Restart / Warm menu function in the ADABAS component CONTROL.


-102 SQL STATEMENT CANCELLED

Explanation:

The SQL statement currently executed was terminated by user or operator intervention or because the maximum usage level of the log was reached.

User Action:

1.	If the SQL statement was terminated by user or operator intervention, no user action is required in interactive mode. In an ADABAS application, a <rollback statement> should be issued to rollback the transaction.

2.	When the maximum usage level of the log is reached, the log must be saved using the ADABAS component CONTROL.


-106 TABLE UNLOADED OR CONTENT DELETED

Explanation:

The table cannot be accessed at the moment, because

1.	the table was extracted from the SERVERDB using the <tableextract statement> of the ADABAS component LOAD or because

2.	another user simultaneously performed a <delete statement> either for a great part of the table or for the whole table so that the specified table was not accessible for a short period of time. This error message can only occur if you work with ISOLATION LEVEL 0.

User Action:

The SQL statement can be executed as soon as

1.	the table has been reloaded into the SERVERDB using the <tableload statement> of the ADABAS component LOAD.

2.	the processing of the <delete statement> is completed.


-108 TABLE, INDEX DROPPED OR CONTENT DELETED

Explanation:

While an SQL statement was processed without any read locks, another ADABAS user dropped a table. The execution of the SQL statement was therefore cancelled.

User Action:

Clarify the organizational error in the user environment.


-109 SERVERDB IS READ ONLY

Explanation:

It is not possible to modify the database objects, because the Options / Database Access / Read-Only menu function in the ADABAS component CONTROL was performed.

User Action:

The SQL statement can be executed as soon as the Options / Database Access / Read/Write menu function in the ADABAS component CONTROL has been performed.


-110 LOG MUST BE SAVED

Explanation:

The Backup / Restore / Log menu function in the ADABAS component CONTROL can only be performed when the log has been saved.

User Action:

Save the log using the Backup / Save / Log menu function in the ADABAS component CONTROL. Then perform the Backup / Restore / Log menu function.


-111 INCOMPATIBLE INCREMENTAL BACKUP

Explanation:

The database version to be loaded for the Backup / Restore / Updated Pages menu function is not the follow-up version of the current database state.

User Action:

Use the correct database version.


-115 TABLE IS READ ONLY

Explanation:

The attempt was made to perform an <insert statement>, <update statement>, or <delete statement>. But the specified table only allows reading SQL statements, because it was previously loaded with the NOLOG option using the ADABAS component LOAD.

User Action:

The read-only mode can be implicitly cancelled using the Backup / Save / Database or Updated Pages menu function in the ADABAS component CONTROL. The same effect can be obtained by using the Options / Database Access / Nolog Off menu function in the ADABAS component CONTROL. However, the usage of the Nolog Off menu function is not recommended, because no data backup is performed so that the data cannot be restored if errors should occur.


-118 SERVERDB MUST BE ACTIVATED

Explanation:

This error message should not occur if the installation of the SERVERDB(s) was performed free of errors using the ADABAS component CONTROL.

User Action:

Check the installation protocol, and repeat the installation after correcting the error, if any.


-119 SERVERDB ALREADY ACTIVATED

Explanation:

This error message should not occur if the installation of the SERVERDB(s) was performed free of errors using the ADABAS component CONTROL.

User Action:

Check the installation protocol, and repeat the installation after correcting the error, if any.


-120 REQUEST DISCARDED

Explanation:

An SQL statement that requires a connection to another SERVERDB could not be processed correctly in a distributed database.

User Action:

This error cannot occur in normal database operation. Inform the ADABAS Support.


-121 SERVERDB MUST BE EMPTY

Explanation:

1.	A new SERVERDB can only be integrated just after its installation, or after performing the Configuration / Init Config menu function for this SERVERDB in the ADABAS component CONTROL.

2.	If the Operating / Restart / Restart Copy or Operating / Restart / Reconnect Copy menu function in the ADABAS component CONTROL was performed for the new SERVERDB and terminated abnormally, only the cancelled command can be repeated. Other commands are not possible.

User Action:

1.	Begin again at the SERVERDB to be integrated using the Configuration / Init Config menu function in the ADABAS component CONTROL. Afterwards, the SERVERDB can be integrated.

Data stored in the SERVERDB to be integrated is lost after issuing the Configuration / Init Config menu function. You should therefore use the ADABAS component LOAD to extract the data and reload it after integrating the SERVERDB.

2.	Repeat the Operating / Restart / Restart Copy or Operating / Restart / Reconnect Copy menu function.


-122 HISTORY NOT FOUND

Explanation:

A SERVERDB could not be reintegrated into the distributed database, because none of the integrated SERVERDBs disposes of the log entries needed for the update of all replicated objects on the SERVERDB to be integrated.

User Action:

It is possible to integrate the SERVERDB and update all replicated objects using the Operating / Restart / Reconnect Copy or Operating / Restart / Restart Copy menu function in the ADABAS component CONTROL.


-502 INVALID STATEMENT IN DB PROCEDURE/TRIGGER

Explanation:

A DB procedure contains a statement that is not allowed in DB procedures.

User Action:

Modify the routine in such a way that it contains only statements valid for DB procedures.


-503 INVALID STOP CODE IN DB PROCEDURE/TRIGGER

Explanation:

A DB procedure contains a stop code that is reserved for ADABAS.

User Action:

Modify the DB procedure in such a way that all STOP statements return valid stop codes.


-504 DB FUNCTION FAILED

Explanation:

The execution of a DB function was terminated using STOP without a stop code specification.

User Action:

According to the situation shown by STOP within the DB function, a user action is required or not.


-505 TRIGGER FAILED

Explanation:

The execution of a trigger was terminated using STOP without a stop code specification.

User Action:

According to the situation shown by STOP within the trigger, a user action is required or not.


-506 DB PROCEDURE FAILED

Explanation:

The execution of a DB procedure was terminated using STOP without a stop code specification.

User Action:

According to the situation shown by STOP within the DB procedure, a user action is required or not.


-530 REFERENTIAL INTEGRITY VIOLATED

Explanation:

There is one of two possible causes.

1.	An <insert statement> or <update statement> issued on a table that is the referencing table in a <referential constraint definition> produces a row that is not a matching row of the <referential constraint definition>.

2.	When deleting rows from a <referenced table> of a <referential constraint definition> with <action> RESTRICT in the <delete rule>, a matching row exists.

User Action:

1.	Display the <referential constraint definition> using a <query statement> issued on the system table DOMAIN.COL_REFS_COL. Correct the <insert statement> or <update statement> according to this definition.

2.	Use an appropriate <query statement> to find out which row of the referencing table prevents the desired <referenced table> rows from being deleted.


-602 SYSTEM ERROR

Explanation:

This error must not occur in normal operation of a consistent database.

In some cases, an implicit SHUTDOWN is performed.

User Action:

As a rule, the database should be shut down and the ADABAS Support informed. It is possible to create a trace of the last database activities. Write this trace to magnetic tape and send it to the ADABAS Support for error tracing and correction.


-701 MISSING DESCRIBE STATEMENT

Explanation:

An SQL statement with descriptor is used for which no DESCRIBE statement was issued.

User Action:

Check the program flow or insert a DESCRIBE statement.


-702 MISSING VARIABLE ADDRESS IN SQLDA

Explanation:

The HOSTVARADDR (address of the program variable) was not set in the SQLDA.

User Action:

Write the address into the SQLDA.


-703 DUPLICATE FETCH STATEMENT WITH MFETCH OPTION NOT ALLOWED

Explanation:

When the MFETCH option is set, only one FETCH statement specification is allowed for one result table.

The execution of such a FETCH statement can be repeated within a loop.

User Action:

Modify the application or run it without MFETCH option.


-705 TOO MANY FETCH STATEMENTS WITH MFETCH OPTION

Explanation:

A total of 18 buffers have been provided to allow processing of result tables by MFETCH. This means that up to 18 result tables can be opened. The attempt to open an additional result set (table) led to this error.

User Action:

At least one result table must be closed, before a new table can be opened.


-706 SQL STATEMENT TOO LONG (BUFFER OVERFLOW)

Explanation:

The SQL statement does not fit the buffer used for communication between the application program and ADABAS.

User Action:

Either change the application or break down the one SQL statement into two statements.


-707 CONNECT STATEMENT SYNTAX WRONG

Explanation:

There is an error in the CONNECT statement syntax.

User Action:

For the exact description of the syntax, refer to the Reference help. Correct the statement accordingly.


-708 SERVERDB SYSTEM NOT YET AVAILABLE

Explanation:

The database exists, but it is in the startup or shutdown phase, with the result that a connection cannot be established at the moment.

User Action:

Repeat the CONNECT at a later point in time.


-709 CONNECT FAILED, CHECK SERVERDB

Explanation:

An error was detected while processing the CONNECT statement.

User Action:

1.	Check the name of the database and correct it, if necessary.

2.	A check must be made as to whether the database is running. If need be, it must be restarted.

3.	Data communication with the database has been interrupted and must be reestablished.


-711 IMPLICIT CONNECT: MISSING USER OR SERVERDB

Explanation:

During execution of an implicit CONNECT, the user entries or the database name could not be found.

User Action:

Open an XUSER file, or enter the CONNECT parameters using runtime options.


-712 TOO MANY PARAMETERS, SQLMAX TOO SMALL

Explanation:

In an SQLDA, an SQLVAR entry was accessed which is no longer available (maximum number of SQLVAR entries < index of the SQLVAR entry).

User Action:

Update the maximum number of SQLVAR elements or correct the index.


-713 INVALID APPL NAME OR RESULT TABLENAME

Explanation:

The name specified for the application or result table is invalid.

User Action:

Correct the result tablename in the EXEC REPORT statement.


-714 INVALID EXEC COMMAND

Explanation:

The <mode> specification <SYNC, NEWSYNC, ASYNC> in an EXEC COMMAND does not correspond to the specified command.

User Action:

Correct the <mode> specification in the EXEC COMMAND.


-715 MISSING USERNAME OR PASSWORD FOR CONNECT

Explanation:

A username or password specification is missing in a CONNECT statement, or there is no XUSER file for an implicit CONNECT.

User Action:

Specify username and password for the CONNECT statement using options, or open an XUSER file.


-716 PARAMETER ONLY IN PARM ALLOWED

Explanation:

Parameters may only be specified after PARM.

The <form var clause> must be specified after OUTPUT, INPUT.

User Action:

Correct the statement EXEC SQLPL.


-717 INVALID PARAMETERSPEC

Explanation:

A <parameter-spec> was incorrectly specified.

User Action:

Correct the statement EXEC SQLPL.


-718 FOR ATTR EXISTS NO FORM VAR CLAUSE

Explanation:

No <form var clause> was specified for an ATTR option.

User Action:

Correct the statement EXEC SQLPL.


-719 UNKNOWN LOCALSYSUSER.SYSPROFILE TABLE

Explanation:

When enabling the PROFILE option, no SYSPROFILE table could be found.

User Action:

The LOCALSYSUSER must create this table, or the application program must be started without PROFILE option.


-720 SQLCODE  <no>   COMES FROM SYSPROFILE COMMAND

Explanation:

The ADABAS database error <no> occurred when writing SYSPROFILE.

User Action:

For error analysis and correction refer to the corresponding number in this online help and follow the instructions given there.

The application program may be started without PROFILE option.


-721 MACRO NOT INITIATED, NO SQLCHECK : WARNING

Explanation:

No SET MACRO was performed. Therefore the SQL statement cannot be checked.

User Action:

Ensure that SET MACRO is issued before the SQL statement within the program flow.


-722 CMD REPORT LINE IS TOO LONG

Explanation:

A REPORT statement is longer than 132 bytes.

User Action:

Break the statement EXEC REPORT down to several lines.


-724 DUPLICATE SUBSTRUCTURE NAME

Explanation:

The name specified for the search of an SQL variable is not unique, because it identifies a substructure.

User Action:

Specify the name of the complete structure with the SQL variable.


-725 INVALID FORM OPTION ATTR

Explanation:

The ATTR option was incorrectly specified.

User Action:

Correct the statement EXEC SQLPL.


-726 MACRO NOT ALLOWED IN THIS STATEMENT

Explanation:

Macro specifications are not allowed in EXEC SQLPL, EXEC QUERY, and EXEC REPORT statements.

User Action:

Remove the macro specifications from these statements.


-727 INVALID FRAME OPTIONS

Explanation:

The FRAME options were incorrectly specified.

User Action:

Correct the statement EXEC SQLPL.


-728 INVALID SQLPL OR FORM SYNTAX

Explanation:

The closing parenthesis is missing for PARM, or for input or output parameters.

User Action:

Insert the missing parenthesis into the EXEC SQLPL statement.


-729 SOURCE CODE MAY BE TRUNCATED : WARNING

Explanation:

The precompiler only recognizes text that is placed within the line delimiters. The line delimiters depend on the used programming language. The warning means that text outside the line delimiters was discovered. This text is ignored by the precompiler.

User Action:

If this effect is desired, the warning may be ignored. Otherwise, the text must be written to the next line or the line delimiters must be modified.


-730 NESTED COMMENT NOT CLOSED

Explanation:

Nested comments are not regularly closed in the source program.

User Action:

The number of opening commentary symbols must equal the number of closing commentary symbols.


-731 COMPONENT NAME TOO LONG

Explanation:

Structure names become longer than 18 bytes by expansion.

User Action:

Shorten the structure names in the table definition. If this is not possible, specify the column names separately.


-732 INDEX OF COMPONENT OUT OF RANGE

Explanation:

The specified index is not in the range of values of the array or of the COBOL table.

User Action:

Specify an index which is within the range of values.


-733 VARIABLE IS DECLARED AS A POINTER : WARNING

Explanation:

The SQL variable was defined as pointer in the DECLARE SECTION.

User Action:

As no fixed size is specified for a pointer, the name of the variable and COLLENGTH are indicated in the next error line. COLLENGTH is the maximum size of the SQL pointer variables. This size is needed for data conversion.


-734 POINTER VARIABLE NOT ALLOWED HERE

Explanation:

SQL variables defined as pointers are not allowed in ADABAS string columns, because the maximum length of these variables is not known.

User Action:

Specify the SQL variable as a CHARACTER ARRAY.


-735 NO SYNTAX CHECK FOR CONNECT COMMAND : WARNING

Explanation:

CONNECT statements that are not used to establish the connection for the check run are not checked for syntax errors during precompilation.

User Action:

Pay special attention to the correct spelling, when entering the statement.


-736 MISSING ENDSIGN FOR CMD LINE

Explanation:

Every QUERY and REPORT statement must end with a semicolon.

User Action:

Insert a semicolon into the statement EXEC QUERY or EXEC REPORT.


-737 BEGIN OR DO STATEMENT AT BLOCK LEVEL 0

Explanation:

A BEGIN or DO statement was specified on the outermost nesting level.

User Action:

Remove this statement.


-738 EXTRA BLOCK CLOSURE

Explanation:

There is an END specification one too many.

User Action:

Remove this END specification.


-739 END LABEL CANNOT BE MATCHED

Explanation:

An END label could not be found.

User Action:

Insert the missing END label.


-740 ARRAY SIZE MISMATCH

Explanation:

In case of mass statements, the parameters have different sizes.

User Action:

The smallest size of all the parameters is set. If this is not desired, set all the sizes to the same value.


-741 INPUT FILE IS LONGER THAN LINENO INPUT FILE : WARNING

Explanation:

XMS precompiler output for the listing is incomplete. As precompiler messages are provided with incorrect line numbers, it is no longer possible to make reference to the invalid source file line.

User Action:

Please inform the ADABAS specialists in the corresponding branch office.


-742 INVALID REPORT OR QUERY STATEMENT

Explanation:

The REPORT or QUERY statement is invalid or unknown.

User Action:

Correct the REPORT or QUERY statement (bracketing may be incorrect), or specify another statement.


-743 INPUT STRING TOO LONG -743 INPUT VARIABLE HAS BEEN TRUNCATED  (ANSI)

Explanation:

The contents of a character string is longer than the database is capable of storing.

In ANSI mode, the error message 'truncated' is output for floating point numbers which were truncated.

User Action:

Set the input variable to a string which corresponds to the length of the database variable or adapt the input variable to the format used in the database.

In ANSI mode, change either the variable values or the external data type.


-745 CMD QUERY LINE IS TOO LONG

Explanation:

A QUERY statement is longer than 132 bytes.

User Action:

Break the statement EXEC QUERY down to several lines.


-746 MISSING CMD QUERY LINE

Explanation:

The CMD specification is missing in a QUERY statement.

User Action:

Insert the CMD specification into the statement EXEC QUERY.


-747 VALUE BUFFER IS TOO SHORT

Explanation:

The value buffer specified in a Visual Basic statement is too small.

User Action:

Specify a greater buffer.


-748 TOO MANY FETCH STATEMENTS

Explanation:

The number of FETCH statements for a module is limited.

User Action:

Break the module down into several modules or reduce the number of FETCH statements.


-750 FFETCH OR ARRAY-FETCH AND FETCH MIX NOT ALLOWED

Explanation:

ARRAY-FETCH and FETCH statements cannot be issued on the same result set.

User Action:

All statements which refer to the same result set must be specified either as ARRAY-FETCH or FETCH.


-751 NUMERIC INPUT PARAMETER OVERFLOW

Explanation:

The numeric input value is too large for the database.

User Action:

Check the size of the input value and of the range of values valid for the database and modify them, if necessary.


-752 SESSION ALREADY CONNECTED

Explanation:

A database session has already been opened with this number.

User Action:

Either close the database session beforehand or remove the CONNECT from the application program.


-753 OUTPUT PARAMETER WITH CONST TYPE

Explanation:

An output parameter must not be declared as CONST type in C.

User Action:

Declare another parameter in the application program.


-754 TOO MANY VARIABLE NAMES DEFINITION

Explanation:

The number of SQL variable name definitions is too large.

User Action:

Distribute the SQL statements to various modules, or reduce the number of SQL variable name declarations. The maximum number is 1000.


-755 TOO MANY PARAMETERS IN THIS STATEMENT

Explanation:

The number of specified parameters for this SQL statement is too large.

User Action:

Reduce the number of parameters in the SQL statement. The maximum number is 1000. The size is only checked during precompilation.


-756 DIFFERENT SQLMODES NOT ALLOWED

Explanation:

An application program may only run in one SQLMODE.

User Action:

The CONNECT statement must be changed. Implicit CONNECTS only function in ADABAS mode. The specifications made in the XUSER file are not taken in this case.


-757 XUSER FILE OPEN ERROR

Explanation:

When initializing the precompiler or the application program, the XUSER file could not be opened.

User Action:

Check whether the XUSER file had been correctly created.


-758 INCLUDE FILE EXISTS ON DISK : WARNING

Explanation:

The DECLARE SECTION is not generated during the precompiler run. The file is already available.

User Action:

Check whether the used file is the current one.


-759 INCLUDE FILE PRODUCED BY USER   <user> : WARNING

Explanation:

During the precompiler run, the DECLARE SECTION is newly created by a CONNECT of the user <user>.

User Action:

Check whether the table of this user is the correct one.


-760 MEMORY ALLOCATION FAILED

Explanation:

The available main memory is too small or write-protected.

User Action:

Check the program for the possible programming error. The main memory must be enlarged or the support be informed.


-761 AREA SIZE IS TOO SMALL

Explanation:

An overflow of an internal variable occurred because of too many ADABAS statements.

User Action:

Decrease the number of ADABAS statements to be executed or inform the ADABAS support.


-762 EXEC ORACLE COMMAND HAS BEEN DELETED

Explanation:

The precompiler removes all statements that are preceded by EXEC ORACLE.

User Action:

This is a warning which may provide indications to possible compiler errors.


-763 VARIABLE NOT ALLOWED AS ARRAY

Explanation:

Scalar host variables are used in an ARRAY statement.

User Action:

Instead of scalar variables, use arrays only, or do without the ARRAY statement.


-764 INVALID VARS SPECIFICATION

Explanation:

The opening parenthesis for a parameter or variable specification is missing in the SQL-PL statement.

User Action:

Correct the syntax.


-765 UNKNOWN ADABAS DATA TYPE (CHECK KERNEL; PRECOM VERS.)

Explanation:

New column types introduced into Version 6.1.1 have been specified for a database of a previous version; i.e., the versions of the kernel and the application program (precompiler runtime system) do not match.

User Action:

Precompile and link the whole application.


-766 MISSING HOSTCOLSIZE IN SQLDA FOR ARRAY STATEMENT

Explanation:

For ARRAY statements, HOSTCOLSIZE of the SQLDA must be set to a value by the user.

User Action:

Assign a value to HOSTCOLSIZE of the SQLDA.


-767 UNTERMINATED C STRING

Explanation:

The zero byte delimiter is missing.

User Action:

Insert a zero byte.


-768 INVALID ESCAPE VALUE

Explanation:

The input host variable is longer than a byte.

User Action:

Use a correct host variable.


-769 POINTER COMPONENT NOT ALLOWED

Explanation:

Pointers are not allowed within structures.

User Action:

Do not specify components as pointers.


-770 MACRO IN FETCH SET MFETCH-OPTION TO ZERO

Explanation:

FETCH statements are executed as array statements, whenever possible. If macros are used in the FETCH statement, errors may occur and records be lost.

User Action:

When using macros within FETCH statements, set the runtime option MFETCH(0). This option prevents FETCH statements from being executed as array statements.


-771 LONG COLUMN EXISTS IN TABLE DEFINITION (WARNING)

Explanation:

The table from which the host variables are generated contains a LONG column.

User Action:

The user can change the host variable generated for this column.


-801 INPUT PARAMETER CANNOT BE NULL VALUE

Explanation:

The value of an input parameter must not be a null value, because null values are not permitted for the column.

User Action:

Modify the program or change the column definition in the CREATE TABLE statement.


-802 INVALID NUMERIC INPUT PARAMETER VALUE

Explanation:

The input value cannot be converted.

User Action:

Specify the value in a valid notation (see SQL variable types in the chapter 'General SQL Variable Conventions' of the Precompiler online help).


-803 DUPLICATE SECONDARY KEY

Explanation:

There is already a table row with the specified secondary key. UNIQUE was specified for the secondary key.

User Action:

To avoid a key value collision, correct the value of the secondary key to be inserted in the command.

The error message specifies the column or multiple-column index already containing the specified values.


-804 PARAMETER LIST TOO LONG

Explanation:

More parameters have been specified in a statement than are permitted in the pertinent EXECUTE statement.

User Action:

Modify the number of parameters in such a way that it corresponds to the specifications made in the column list.


-805 PROGRAM MUST BE PRECOMPILED

Explanation:

The common type definitions of the precompiler runtime system or of the include files do no longer correspond to the precompiler types.

User Action:

Check the release numbers of precompiler, precompiler runtime system, and include files and precompile again, if necessary.


-806 DB SESSION NUMBER NOT ALLOWED

Explanation:

The specified database session number is invalid.

User Action:

Insert a database session number between 1 and 8 into the application program.


-807 CONNECTION DOWN,  SESSION RELEASED

Explanation:

All database connections were closed with RELEASE.

User Action:

Establish a new connection using CONNECT.


-808 NOT YET IMPLEMENTED

Explanation:

The function has not yet been implemented.

User Action:

Wait for a following release.


-809 MISSING INDICATOR VARIABLE, OUTPUT PARAMETER WITH NULL VALUE

Explanation:

The indicator variable required for returning the NULL value to the SQL variable is missing.

User Action:

Specify an indicator variable with the parameter.


-811 NUMERIC OUTPUT PARAMETER OVERFLOW

Explanation:

An ADABAS database value is too large for the SQL variable or the parameter.

User Action:

Enlarge the value range for the SQL variable or parameter.


-812 PARAMETER LIST TOO SHORT

Explanation:

Less parameters have been specified in a statement than are needed in the pertinent EXECUTE statement.

User Action:

Modify the number of parameters in such a way that it corresponds to the specifications made in the column list.


-813 SERVERDB MUST BE RESTARTED

Explanation:

The ADABAS database is not running, or an invalid ADABAS database name was specified in the program.

User Action:

The DB administrator must start the database, or the user must modify the program or XUSER file.


-814 TRACE FILE CLOSE ERROR

Explanation:

The trace file could not be closed. The error was ignored in the program.

User Action:

Modify the file attributes (characteristics). For the exact error description, see the file 'appldiag'.


-815 TRACE FILE OPEN ERROR

Explanation:

The trace file could not be opened. Writing of the trace file was disabled. The statement in which the error occurred was not executed.

User Action:

Check the file attributes and change them, if necessary. For the exact error description, see the file 'appldiag'.


-816 TRACE FILE WRITE ERROR

Explanation:

An error occurred when writing into the trace file. Writing of the trace file was disabled. The statement in which the error occurred was not executed.

User Action:

Check the file attributes and change them, if necessary. For the exact error description, see the file 'appldiag'.


-817 INCOMPATIBLE DATA TYPES

Explanation:

The data type of the SQL variable or parameter is not compatible with the ADABAS data type.

User Action:

Change the data type of the SQL variable or parameter to match the ADABAS data type for the table column.

If this message is returned during precompilation and the data types do be compatible, precompile with NOCHECK option (see the chapter 'General Rules' of the Precompiler online help).


-818 MISSING MACRO PARAMETER INITIALIZATION

Explanation:

The macro was not initialized.

User Action:

Insert the SQL statement SET MACRO into the application program.


-819 PARAMETER IN SQL STATEMENT NOT ALLOWED

Explanation:

Only an SQL statement without parameter specifications is permitted. Either an SQL statement with parameters but without a USING part was passed with an EXECUTE, or an error occurred in the parameter list.

User Action:

Add a USING clause, or use an SQL statement without parameters, or correct the parameter list.


-820 INVALID DECLARE STATEMENT

Explanation:

The keyword FOR was not found in the DECLARE CURSOR statement.

User Action:

Insert the keyword FOR into the DECLARE CURSOR statement.


-821 UNKNOWN COLUMNID

Explanation:

For a QUERY or REPORT statement with result specifications, no result was set into the specified column.

User Action:

Check the QUERY or REPORT statement with the result <columnid> and change the statement accordingly.


-822 INVALID CONSTANT DEFINITION

Explanation:

The constant definition is invalid.

User Action:

Correct the constant definition within the DECLARE SECTION.


-823 INTEGER TOO LARGE, GREATER THAN 32767

Explanation:

The constant must not be larger than 32767 (2 bytes).

User Action:

Choose a smaller constant value.


-824 STATEMENT IN CONFLICT WITH COMPATIBLE OPTION

Explanation:

The option COMPATIBLE is set, and an SQL array statement was specified with the keyword FOR.

User Action:

The option COMPATIBLE can be used for all programs of Release 2.4. In Release 2.4, however, there were no SQL array statements yet. These are therefore incorrectly interpreted without COMPATIBLE option. New programs should be written in such a way that the option is no longer needed.


-825 DUPLICATE FIELD NAME IN RECORD

Explanation:

A name is used twice in an SQL record definition.

User Action:

Rename one of the record components.


-826 DUPLICATE STATEMENT NAME

Explanation:

The name was already specified for a statement.

User Action:

Rename the statement.


-827 DUPLICATE TYPE DEFINITION

Explanation:

The name was already specified for an SQL type definition.

User Action:

Rename the SQL type.


-828 DUPLICATE VARIABLE NAME

Explanation:

The name was already specified for an SQL variable.

User Action:

Rename the SQL variable.


-829 FILE CLOSE ERROR

Explanation:

An error occurred when closing a file. This is a device failure or system error.

User Action:

Retry to issue the command. For the exact error description, see the file 'appldiag'.


-830 FILE OPEN ERROR

Explanation:

A file could not be opened.

User Action:

Check whether the file is available or the spelling of the filename is correct. For the exact error description, see the file 'appldiag'.


-831 FILE READ ERROR

Explanation:

A file could not be read. This may be a device failure.

User Action:

Check whether the file is available or the spelling of the filename is correct. For the exact error description, see the file 'appldiag'.


-832 FILE WRITE ERROR

Explanation:

A file could not be written. This may be a device failure.

User Action:

Check whether the file is available or the spelling of the filename is correct. For the exact error description, see the file 'appldiag'.


-833 ILLEGAL INCLUDE POSITION

Explanation:

An INCLUDE statement is not at the correct position in the module.

User Action:

Place the INCLUDE statement in the correct position.


-834 INCLUDES MUST NOT BE NESTED

Explanation:

Another INCLUDE statement was found within an INCLUDE file.

User Action:

Remove the inner INCLUDE statement.


-835 INCLUDE FILE OPEN ERROR

Explanation:

The INCLUDE file could not be opened.

User Action:

Check whether the file is available or the spelling of the filename is correct. For the exact error description, see the file 'appldiag'.


-836 INVALID C PREPROCESSOR COMMAND

Explanation:

The C preprocessor command line is incorrect.

User Action:

Correct the command in accordance with the C rules.


-837 DATA DEFINITION NOT ALLOWED

Explanation:

The syntax of the SQL data type is incorrect or the SQL data type is invalid.

User Action:

Correct the data definition or construct a valid alternative.


-838 INVALID DECLARATOR

Explanation:

The declarator is invalid.

User Action:

Correct the declarator within the DECLARE SECTION.


-839 INVALID MACRO VALUE

Explanation:

An error occurred when substituting the macro.

User Action:

Specify the macro value in accordance with the syntax.


-840 INVALID NUMERIC MACRO VALUE

Explanation:

The macro number is invalid.

User Action:

Specify a number between 1 and 128 for the macro.


-841 INVALID PRECOMPILER OPTION

Explanation:

A precompiler option is invalid or unknown.

User Action:

For the exact error description, see the precompiler listing or the file SQLERROR. Check the options and specify them correctly.


-842 PARAMETER AND INDICATOR STRUCTURES DO NOT MATCH

Explanation:

Parameters and indicators are defined with different types (record, scalar). Valid combinations of SQL variables and indicator variables are record record, record integer array, and scalar scalar.

User Action:

Use indicator variables which have another type.


-843 INVALID PARAMETER NAME

Explanation:

The parameter name is not an identifier.

User Action:

Correct the name in accordance with the notation of identifiers.


-844 INVALID RECORD NAME

Explanation:

The record name is invalid or unknown.

User Action:

Declare a record or use another SQL variable.


-845 INVALID SQL STATEMENT

Explanation:

The SQL statement is invalid or unknown.

User Action:

Correct the SQL statement or use another SQL statement.


-846 INVALID STATEMENT IN SECTION

Explanation:

A statement in the section is invalid.

User Action:

Correct the statement or use another SQL statement.


-847 INVALID TYPE DEFINITION INVALID CLAUSE (COBOL)

Explanation:

The type definition or clause is invalid or not allowed.

User Action:

Correct the definition or clause, or remove it from the DECLARE SECTION.


-848 INVALID UNSIGNED INTEGER

Explanation:

An unsigned integer was expected but not found.

User Action:

Correct the SQL statement.


-849 INVALID VARIABLE DEFINITION INVALID DATA DEFINITION

Explanation:

The SQL variable or data definition is invalid or not allowed. The variable definition is not known as SQL variable.

User Action:

Declare the SQL variable name or the data in the DECLARE SECTION, or correct the name or data.


-850 STATEMENT TERMINATION EXPECTED

Explanation:

The termination symbol is missing in the preceding SQL statement. It is set by the precompiler.

User Action:

If there are no side effects, insert the termination symbol into the statement.


-851 MISSING INPUT FILE NAME

Explanation:

A name specified for an INCLUDE file is unknown.

User Action:

Check whether the file is available or the spelling of the filename is correct.


-852 MISSING PROGRAM FILE

Explanation:

The source file is unknown.

User Action:

Check whether the file is available or the spelling of the filename is correct.


-853 PRECOMPILER SYNTAX CHECK ONLY : WARNING

Explanation:

Although the option CHECK was specified, the syntax of this statement could only be checked for the precompiler run. No entries were made to the data dictionary of the database.

User Action:

To obtain information about possible errors, run the application with the TRACE option.


-854 PARAMETERS MUST BE QUESTION MARKS

Explanation:

In PREPARE statements, only question marks are allowed for parameter specifications.

User Action:

Replace the SQL variable with a question mark.


-855 SQL VARIABLE MUST BE AN ARRAY

Explanation:

SQL variables must be array structures in an SQL array statement.

User Action:

Define and specify the SQL variable correctly.


-856 INVALID LOOP PARAMETER VALUE

Explanation:

In an SQL array statement, the value of the <loop parameter> is set to <= 0.

User Action:

Set the <loop parameter> to a value > 0.


-857 MISSING SERVERDB

Explanation:

No SET SERVERDB statement was issued for the second or any following database connection.

User Action:

Specify SET SERVERDB before the CONNECT statement or in the XUSER file.


-858 STORAGE CLASS NOT ALLOWED

Explanation:

The C storage class is not allowed.

User Action:

Choose another storage class.


-859 NUMBER OF COLUMNS < NUMBER OF PARAMETERS : WARNING

Explanation:

More SQL variables are specified in the statement than columns are available in the table.

User Action:

If this is not desired, add columns to the table or reduce the number of SQL variables.


-860 TOO MANY CONSTANTS DECLARED

Explanation:

Too many SQL constants are declared.

User Action:

The database application should be modularized. The maximum number of constants is 100.


-861 TOO MANY PARAMETERS FOR DESCRIPTOR

Explanation:

Too many parameters are specified for the descriptor variable.

User Action:

Reduce the number of parameters in the SQL statement. The maximum number is 300.


-862 TOO MANY SQL-PL STATEMENTS

Explanation:

Too many SQL-PL statements are specified in the module.

User Action:

Distribute the statements to two modules. The maximum number is 100.


-863 TOO MANY NAMES IN SQLPL STATEMENT

Explanation:

Too many names are specified in SQL-PL statements.

User Action:

Distribute the statements to two modules. The maximum number is 1000.


-864 TOO MANY OPTIONS IN SQLPL STATEMENT

Explanation:

The total number of options specified in all SQL-PL statements of the module is too large.

User Action:

Distribute the statements to two modules. The maximum number is 100.


-865 TOO MANY PARAMETERS IN SQL STATEMENTS

Explanation:

The number of parameters specified in all SQL statements is too large.

User Action:

Distribute the statements to two modules. The maximum number is 1500.


-866 TOO MANY PREPARE STATEMENTS

Explanation:

The number of PREPARE statements is too large.

User Action:

Distribute the statements to two modules. The maximum number is 500.


-867 TOO MANY PARAMETERS

Explanation:

The number of parameters defined by the user in all SQL statements is too large.

User Action:

Distribute the statements to two modules. The maximum number is 1500.


-868 TOO MANY SQL STATEMENTS

Explanation:

Too many SQL statements are specified in the module.

User Action:

Distribute the statements to two modules. The maximum number is 500.


-869 TOO MANY STRING CONSTANTS IN PREPARE OR EXECUTE STATEMENTS

Explanation:

The number of character string literals of all PREPARE or EXECUTE statements of the module is too large.

User Action:

Distribute the statements to two modules, or reduce the number of character string literals. The maximum number is 1000.


-870 TOO MANY TYPE DEFINITIONS

Explanation:

The number of type definitions is too large.

User Action:

Distribute the SQL statements to several modules, or reduce the number of type definitions. The maximum number is 500.


-871 TOO MANY VARIABLE DEFINITIONS

Explanation:

The number of SQL variable definitions is too large.

User Action:

Distribute the SQL statements to several modules, or reduce the number of SQL variable declarations. The maximum number is 10000.


-872 NUMBER OF COLUMNS > NUMBER OF PARAMETERS : WARNING

Explanation:

Less SQL variables are specified in the statement than columns are available in the table.

User Action:

If this is not desired, add the missing SQL variables or reduce the number of columns in the table.


-873 UNKNOWN CONSTANT NAME

Explanation:

The constant name is unknown.

User Action:

Correct the name or declare one.


-874 UNKNOWN CURSOR NAME

Explanation:

The cursor name is unknown.

User Action:

Correct the name or define a cursor.


-875 UNKNOWN INDICATOR NAME

Explanation:

The indicator name is unknown.

User Action:

Correct the name or define an indicator.


-876 UNKNOWN MACRO NUMBER

Explanation:

The macro number is unknown. The SET MACRO statement was not performed for the specified macro number.

User Action:

Insert the correct number or define a corresponding macro.


-877 UNKNOWN PARAMETER NAME

Explanation:

The parameter name is unknown.

User Action:

Correct the name or declare an indicator.


-878 UNKNOWN RECORD NAME

Explanation:

The record name is unknown.

User Action:

Correct the name or declare a record.


-879 UNKNOWN PRECOMPILER STATEMENT

Explanation:

The precompiler statement is unknown or invalid.

User Action:

Issue the precompiler statement or correct it.


-880 UNKNOWN STATEMENT NAME

Explanation:

The statement name is unknown.

User Action:

Issue the PREPARE statement or correct it.


-881 UNKNOWN TYPE NAME

Explanation:

The type definition is unknown.

User Action:

Correct the type name or define a type.


-882 MISSING USER NAME FOR CONNECT

Explanation:

No user/password combination could be found for an implicit CONNECT enabled by the CHECK option.

User Action:

Write the CONNECT statement as first parameter into the program, or specify the option USER, or create an XUSER file for an implicit CONNECT.


-883 INVALID RUNTIME OPTIONS

Explanation:

Either the precompiler or runtime options are incorrect or the parameters specified with the SQL-PL call are not binary, 2-byte or 4-byte long integers.

User Action:

Correct the options or modify the SQL-PL call.


-884 MISSING INDICATOR VARIABLE : WARNING

Explanation:

The ADABAS database permits null values for the variable. It needs an indicator variable for them.

User Action:

Specify an indicator variable in addition to the SQL variable. This specification is not necessary when it is ensured that null values will not occur.


-885 VARIABLE MAY BE TRUNCATED : WARNING

Explanation:

The range of values of the database column is smaller than that of the SQL variable. When the value is inserted into the column or when values are compared, the value may be truncated and consequently be incorrect.

User Action:

If this is not desired, modify either the format of the column or the format of the SQL variable.


-886 MISSING DECLARE SECTION BEGIN OR END

Explanation:

The delimiter statement for the DECLARE SECTION is incorrect.

User Action:

Every DECLARE SECTION must be enclosed in BEGIN DECLARE SECTION and END DECLARE SECTION.


-887 WHENEVER ACTION TOO LONG

Explanation:

At most 50 bytes are available for the WHENEVER action definition.

User Action:

Reduce the number of characters, e.g., by shortening the names.


-888 MISSING INCLUDE SQLCA

Explanation:

The statement EXEC SQL INCLUDE SQLCA was not found when precompiling a module.

User Action:

Insert the statement EXEC SQL INCLUDE SQLCA into the program.


-889 INPUT LINE LONGER THAN 512 CHARACTERS

Explanation:

A line of a precompiler input file must not exceed 512 characters.

User Action:

Shorten the line concerned.


-890 INPUT LINE LONGER THAN RIGHT MARGIN

Explanation:

A line of the source file is longer than the right margin.

User Action:

If allowed, adjust the right margin using the option MARGINS. Otherwise, shorten the line.


-891 DUPLICATE CONSTANT NAME

Explanation:

A constant name is specified twice in the DECLARE SECTION.

User Action.

Rename one of the constants.


-892 VARIABLE MAY OVERFLOW : Warning

Explanation:

This warning is set, if a numeric value greater than allowed by the column definition can be transferred to a table. At runtime, the error -751 can be returned; i.e., the SQL statement then is not executed.

User Action:

To avoid the error -751, check the value for its size before transferring it into the table. The handling of this error must be programmed.


-893 TOO MANY HOSTVARIABLES

Explanation:

1.	Too many parameters are specified in an SQL statement with descriptor.

2.	In an SQLDA area, an SQLVAR entry was accessed which is no longer available (maximum number of SQLVAR entries < index of the SQLVAR entry).

User Action:

Reduce the number of parameters in the SQL statement to 300 or less.


-894 TRACE PARAMETER STRUCTURE NOT ALLOWED

Explanation:

There is a syntax error in SET TRACE LINE.

User Action:

Correct the SET TRACE LINE statement.


-895 WHOLE TABLE MAY BE DELETED OR UPDATED : WARNING

Explanation:

Precompiler warning that all entries of the table will be deleted or updated.

User Action:

Check whether this effect is desired. Otherwise, insert a WHERE clause into the statement.


-896 INVALID SQLPL OPTIONS

Explanation:

Options of the EXEC SQLPL statement are invalid.

User Action:

Correct the options in the EXEC SQLPL statement.


-897 INVALID ACCEPT KEYS

Explanation:

The ACCEPT option is incorrect.

User Action:

Correct the ACCEPT option of the EXEC SQLPL statement.


-898 INVALID PRINT OPTIONS

Explanation:

The PRINT options are incorrect.

User Action:

Correct the PRINT options of the EXEC SQLPL statement.


-900 DATA SPACE FULL (EMERGENCY SHUTDOWN)

Explanation:

The data devspace of the SERVERDB is full. The issued SQL statement fails. ADABAS implicitly performs a SHUTDOWN.

User Action:

The SERVERDB must be enlarged by assigning additional DEVSPACEs. Afterwards, the Operating / Restart / Warm menu function in the ADABAS component CONTROL must be executed in order to achieve data consistency for all transactions carried out.


-901 LOG FULL (EMERGENCY SHUTDOWN)

Explanation:

The log devspace is full. The issued SQL statement fails. ADABAS implicitly performs a SHUTDOWN.

User Action:

To clear parts of the log devspace, the Backup / Save / Log Segment menu function in the ADABAS component CONTROL must be performed to switch the SERVERDB into COLD mode; this must be followed by the Backup / Save / Log Segment menu function. Even if 0 was specified for log segment size during installation, these operations must be performed. Only if the SERVERDB is in COLD mode, CONTROL does not write any log entries.

If the LOG MODE is DEMO or if it is NORMAL and the temporary log area overflowed, the log can only be filled, because there is not enough space for the entire effects of one transaction. In this case, it is sufficient to execute the Operating / Restart / Warm menu function in the ADABAS component CONTROL to clear the log.


-902 I/O ERROR

Explanation:

An SQL statement for write or read operations on the ADABAS data devspace or log devspace had to be performed. This operation could not be executed successfully. There is one of two possible causes.

1.	A SHUTDOWN was performed in the meantime.

2.	A disk is defective.

User Action:

In some cases, the error message contains an additional description of the error which must be interpreted according to the used operating system.

1.	Perform the Operating / Restart / Warm menu function.

2.	Once the disk error has been corrected, the SERVERDB must be restored by means of backup copies and by redoing the log versions.


-903 HOST FILE I/O ERROR

Explanation:

An error occurred while operating a command file or host file or a backup device.

User Action:

The error message contains an additional description of the error which must be interpreted according to the used operating system.

To find out and remove the error cause, consult the documentation on the operating system.


-904 SPACE FOR RESULT TABLES EXHAUSTED

Explanation:

1.	The storage space available for result tables is too small or

2.	the ADABAS application generated too much temporary information.

In both cases, the execution of the SQL statement was terminated and the user was disconnected from ADABAS by an implicit <release statement> in the format ROLLBACK WORK RELEASE.

User Action:

1.	After a new <connect statement>, you can reissue the SQL statement hoping that other users are creating fewer result tables or less temporary information at this point in time.

2.	A larger disk space can be defined using the ADABAS component CONTROL.

3.	To make space, tables can be extracted using the <tableextract statement> of the ADABAS component LOAD.


-905 PERMLIMIT FOR THIS USER EXHAUSTED

Explanation:

The disk space defined in the <create user statement>, <create usergroup statement>, <alter user statement>, or <alter usergroup statement> for storing the user's private tables is full.

User Action:

1.	The user can regain disk space by dropping private tables or indexes or by deleting table rows.

2.	The SYSDBA or DBA who created the user or usergroup can expand the limit (PERMLIMIT) valid for the user or usergroup using the <alter user statement> or <alter usergroup statement>.


-906 TEMPLIMIT FOR THIS USER EXHAUSTED

Explanation:

The disk space defined in the <create user statement>, <create usergroup statement>, <alter user statement>, or <alter usergroup statement> for storing the user's result tables and the temporary information generated by the ADABAS application is full.

User Action:

1.	The user can regain disk space by dropping result tables.

2.	The SYSDBA or DBA who created the user or usergroup can expand the limit (TEMPLIMIT) valid for the user or usergroup using the <alter user statement> or <alter usergroup statement>.


-907 SPACE FOR USER SESSION EXHAUSTED

Explanation:

You have not been connected to ADABAS, because there is not sufficient free temporary disk space for the CONNECT of a normal ADABAS session.

User Action:

1.	You can connect to ADABAS as soon as another user has disconnected from ADABAS, or if there is sufficient free storage space available again, because other users deleted some result tables.

2.	You can connect to ADABAS using the ADABAS component CONTROL. The SERVERDB can be reconfigured using the ADABAS component CONTROL.


-909 MIRRORED DEVSPACES IMPOSSIBLE

Explanation:

The operating system does not support mirrored devspaces for ADABAS.

User Action:

Do without the installation of mirrored devspaces.


-910 COSTLIMIT FOR THIS USER EXHAUSTED

Explanation:

Execution of the SQL statement would exceed the permissible maximum limit for the processing of the SQL statement (COSTLIMIT value of the user) because of the necessary selection of rows. The COSTLIMIT value is defined in the <create user statement>, <create usergroup statement>, <alter user statement>, or <alter usergroup statement>.

User Action:

You should check whether the SQL statement is needed in the specified format. You should check whether, e.g., the set of data to be processed could be decreased by specifying more conditions in the <search condition>; thus decreasing the costs.

Should not be possible, try to obtain the effect of the SQL statement by several less costly SQL statements.

Display the definition of the COSTLIMIT value using a <query statement> issued on the system table DOMAIN.USERS.

The system DBA or the DBA who is owner of the usergroup or user may increase the COSTLIMIT value using an <alter user statement> or <alter usergroup statement>.


-911 WORK ROLLED BACK

Explanation:

Your transaction was implicitly cancelled and rolled back by an implicit <rollback statement>, because

1.	you failed to carry out any ADABAS operations within a certain period of time (installation parameter LOCK TIMEOUT) but held locks which other users were waiting for, or because

2.	the SERVERDB was in a deadlock situation. A deadlock situation is a situation in which two or more users hold locks and request further locks that are held by the respective other users. In the simplest case of two users, one user holds one lock and requests another lock. But this lock is held by another user who, on the other hand, waits for the lock held by the first user. This situation can only be resolved, if one of the users releases the lock already obtained.

User Action:

In some cases, the error message contains a more detailed description of the error.

In both cases, the lock requests must be checked and modified, if necessary. The last transaction must be repeated.

It may also be necessary to check and modify the value of the installation parameter LOCK TIMEOUT.


-912 COMMUNICATION FAILURE

Explanation:

The processing of the SQL statement requires access to another SERVERDB. This access failed.

User Action:

The error message contains the number of the SERVERDB that could not be accessed. Ensure that the connection between the SERVERDB to which you are connected and the other SERVERDB is in UP state again. Use a <query statement> issued on the system table DOMAIN.SERVERDBS to find out the name of the SERVERDB identified by the number.

It could suffice to perform the Operating / Restart / Warm menu function for the SERVERDB. Otherwise, the connection between the SERVERDBs must be reestablished at operating system level.


-913 LOCK REQUEST TIMEOUT

Explanation:

The lock request or an implicit lock conflicts with the locks of another user. The maximum waiting time for granting the lock has elapsed (installation parameter REQUEST TIMEOUT).

User Action:

In some cases, the error message contains a more detailed description of the error.

The lock request can be reissued. To avoid possible deadlock situations, it is advisable to roll back the transaction using the <rollback statement>.


-914 NEW DEVSPACE NOT ACCESSIBLE

Explanation:

The attempt was made to define an additional devspace for the ADABAS data using the Configuration / Add Devspace menu function in the ADABAS component CONTROL. This attempt failed because there is no disk with the specified name and size which could be accessed.

User Action:

The error message contains an additional description of the error which must be interpreted according to the used operating system.

Check the name and size of the disk as well as the installation of the disk.

The command can be repeated with changed specifications.


-915 NO MORE MEMORY

Explanation:

1.	The available main memory is not sufficient to open a user session. The available maximum main memory is determined by the parameter CATALOG_CACHE_PAGS when installing the SERVERDB.

2.	The available main memory is not sufficient to execute the desired DB procedure.

User Action:

1.	You can only open a session when at least one other user has terminated his session. A check should be made as to whether the value of the installation parameter CATALOG_CACHE_PAGS is large enough.

2.	Try to execute the DB procedure at a later point in time.

3.	Check whether the installation parameter PROC_DATA_PAGES can be increased.


-916 SAVE/RESTORE READ PROCESS CRASH - I/O ERROR

Explanation:

1.	An I/O error occurred while attempting to read a backup device for a restore statement.

2.	An I/O error occurred while attempting to read a devspace for a save statement.

The restore or save statement was cancelled.

User Action:

The error message contains an additional description of the error which must be interpreted according to the used operating system.

To find out and remove the error cause, consult the documentation on the operating system.


-917 SAVE/RESTORE WRITE PROCESS CRASH - I/O ERROR

Explanation:

1.	An I/O error occurred while attempting to write a backup device for a save statement.

2.	An I/O error occurred while attempting to write a devspace for a restore statement.

The save or restore statement was cancelled.

User Action:

The error message contains an additional description of the error which must be interpreted according to the used operating system.

To find out and remove the error cause, consult the documentation on the operating system.


-918 STACK OVERFLOW

Explanation:

Nested calls of DB procedures and triggers reached the maximum stack usage allowed for a task. Another nesting is not possible. The command was cancelled.

User Action:

Decrease the nesting levels of the calls by appropriate queries within the DB procedures and triggers.


-919 SERVERDB DISCONNECTED

Explanation:

An SQL statement was specified which requires that the current SERVERDB communicates with at least one SERVERDB in the distributed database. The SERVERDB where you opened your session had been previously removed from the network of SERVERDBs which can communicate with each other. Therefore, the statement cannot be executed.

User Action:

The SQL statement can only be executed when the current SERVERDB has been reintegrated in the network of SERVERDBs which can communicate with each other. Use the ADABAS component CONTROL for this purpose.


-942 UNKNOWN TABLE NAME

Explanation:

A table with the specified name is not known. It can be that such a table does not exist, or that the table exists but you have no privileges for it.

User Action:

Use a <query statement> issued on the system table DOMAIN.TABLES to find out the names of the tables for which you have privileges. Correct the table name; it may be sufficient to place the missing <owner> in front of it. Otherwise, create a table with this name or check why you do not have any privileges for the existing table.


-955 DUPLICATE NAME

Explanation:

There is already a data object with the specified name.

User Action:

Repeat the SQL statement with another name.


-1000 TOO MANY LOCK REQUESTS

Explanation:

There are too many locks or lock requests.

User Action:

You can try to reissue the SQL statement at a later point in time or cancel the transaction. Should this situation occur frequently, then the defined installation parameter LOCK_PAGES is too small and should be increased.


-1001 TOO MANY LOCK OBJECTS SPECIFIED

Explanation:

The <lock statement> or the option KEEP of a <commit statement> or <rollback statement> contains too many tables or table rows to be locked.

User Action:

The SQL statement must be formulated using two successive <lock statement>s.


-1002 TOO MANY COLUMNS

Explanation:

1.	The number of columns of a table that contains no (at least one) user-defined key column is limited to 254 (255).

2.	A named index can be created across a maximum of 16 columns of a table.

3.	In a <referential constraint definition>, more <referencing column>s than <referenced column>s were specified. The number of the specified referencing table columns must correspond to the number of the <referenced column>s of the <referenced table> specified implicitly or explicitly.

User Action:

1.	Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the current definition of the table. It is not possible to define more columns.

2.	Correct the number of columns in the index definition.

3.	Use <query statement>s issued on the system table DOMAIN.COLUMNS to find out the complete definition of the <referenced table> and of the key columns of the <referenced table>.


-1003 TOO MANY BUFFERS REQUESTED

Explanation:

The storage requirements of the buffers and areas defined by installation parameters are larger than the maximum virtual storage space available for ADABAS. The execution of the SQL statement was cancelled.

User Action:

Either decrease the configured size or number of buffers and areas (installation parameters) or increase the virtual storage space available to the ADABAS server. Then perform the Operating / Restart menu function in the ADABAS component CONTROL.


-1004 TOO MANY CORRELATED COLUMNS

Explanation:

The SQL statement contains at least one correlated subquery. The attempt was made to use more than 64 correlated columns. At most 64 correlated columns can be used. Every single usage of a correlated column is counted.

User Action:

Rearrange the SQL statement in such a way that 64 correlated columns suffice; or you can make the attempt to achieve the effect of this SQL statement with several SQL statements.


-1005 TOO MANY MONADIC OPERATORS

Explanation:

The issued SQL statement contains at least two monadic operators placed one after the other in an invalid manner.

User Action:

Correct the monadic operators in the SQL statement.


-1006 TOO MANY VARIABLES

Explanation:

A maximum of 300 variables may be specified per SQL statement.

User Action:

Decrease the number of variables in the SQL statement. Some variables must be replaced with constant values. If this is not possible, split the SQL statement into several SQL statements.


-1007 TOO MANY NAMED INDEXES FOR THIS TABLE

Explanation:

A maximum of 256 named indexes can be created per table.

User Action:

Check whether such a great number of indexes is actually needed. The overhead for maintaining the indexes in case of modifying operations as well as the storage space required for the indexes is very seldom in good proportion to their benefit.


-1010 TOO MANY DEVSPACES

Explanation:

During installation, the number of data DEVSPACEs is limited to 64.

User Action:

Specify a number <= 64 for the number of data DEVSPACEs.


-1011 TOO MANY CORRELATED TABLES

Explanation:

The number of correlated tables used within the correlated subqueries must not exceed 16.

User Action:

The attempt can be made to formulate the SQL statement in such a way that 16 correlated tables suffice. If this is not possible, the expected effect must be achieved in several intermediate steps, i.e., with several SQL statements.


-1012 TOO MANY REFERENTIAL CONSTRAINT DEFINITIONS FOR THIS TABLE

Explanation:

Using the <alter table statement>, the attempt was made to create more than 256 <referential constraint definition>s for a table that is the referencing table.

User Action:

Use a <query statement> issued on the system table DOMAIN.COL_REFS_COL to check the existing <referential constraint definition>s. The <alter table statement> can only be issued after dropping an existing <referential constraint definition>. Otherwise, do without the new <referential constraint definition>.


-1013 TOO MANY ORDER COLUMNS

Explanation:

There is one of three possible causes.

1.	More than 16 columns were specified as sort criterion or group columns.

2.	The total length of the order or group columns exceeds 250 characters.

3.	The length of the longest result data type of a <distinct function>, together with the lengths of the group columns, exceeds 254 characters. The result data type is the data type which is assigned to the result of an <expression>.

User Action:

Correct the SQL statement by removing one or more columns from the <order clause> or <group clause>.


-1014 TOO MANY SOURCE TABLES

Explanation:

The number of underlying tables of the <from clause> of the SQL statement exceeds 16. If a join view table was specified in the <from clause>, the number of base tables underlying the join view table is considered for the calculation.

User Action:

The SQL statement can be split into two successive SQL statements. It is also possible to bypass this restriction by using a <query expression> in the <from clause>.


-1015 TOO MANY VALUES

Explanation:

In case of an <insert statement> or <update statement>, the number of specified values exceeds the number of column names (possibly implicitly specified).

User Action:

Adapt the number of specified values in the SQL statement to the number of specified column names.

Use a <query statement> issued on the system table DOMAIN.COLUMNS for an <insert statement> without column name specification to find out the definition of the used table.


-1017 TOO MANY JOINS

Explanation:

The number of <join predicate>s in a <search condition> must not exceed 64.

User Action:

The expected result can be achieved by issuing several <query statements> and creating the respective result tables as temporary results. It is also possible to change the SQL statement in such a way that temporary results are implicitly created when a <query expression> is used in a <from clause>.


-1020 TOO MANY USERS WITH PERMLIMIT DEFINED

Explanation:

A maximum of 518 000 user areas can be defined with a PERMLIMIT specification for a SERVERDB. This number was exceeded when attempting to create a user or usergroup with PERMLIMIT specification.

The number of currently existing user areas with PERMLIMIT specification is thereby irrelevant.

User Action:

It is not possible to create another user area with PERMLIMIT specification.


-1021 TOO MANY USERS CONNECTED

Explanation:

The Configuration / Clear Serverdb menu function was performed in the ADABAS component CONTROL, although there is at least one more user connected to the SERVERDB.

User Action:

Clarify whether or not work shall be continued on this SERVERDB.


-1022 TOO MANY SERVERDBS

Explanation:

The attempt was made to add another SERVERDB to the distributed database using the ADABAS component CONTROL. A distributed database can have a maximum of 2048 SERVERDBs. This number was exceeded.

User Action:

Another SERVERDB can only be added to the distributed database after performing the Configuration / Clear Serverdb menu function in the ADABAS component CONTROL for one of the SERVERDBs belonging to the distributed database; i.e., after removing that SERVERDB from the distributed database.


-1023 TOO MANY NESTED SUBTRANSACTIONS

Explanation:

The maximum nesting level of subtransactions is 32767. This number was exceeded.

User Action:

Check which error in application programming generated such a nesting level of subtransactions. Correct the ADABAS application.


-1024 TOO MANY TERMCHAR SETS

Explanation:

A maximum of eight terminal character sets can be defined per SERVERDB. This number was exceeded.

User Action:

Check whether one of the available terminal character sets can be removed or whether you must do without the definition of a new terminal character set.


-1025 TOO MANY NET REQUESTS

Explanation:

There are too many SQL statements at one time issuing requests to other SERVERDBs.

User Action:

The SQL statement can be repeated at a later point in time.

If this error message occurs frequently, the installation parameter MAXSERVERTASKS should be increased.


-1026 TOO MANY DIFFERENCES BETWEEN OLD AND NEW VIEW DEFINITION

Explanation:

A <create view statement> was specified with <replace option>. There is already a view table with the specified name. The existing view definition differs so much from the specified view definition that the definitions depending on this view table can  no longer be maintained in a consistent state. Therefore, the <create view statement> fails.

User Action:

Do without modification of the specified view table or check which of the depending definitions, e.g., view tables, privileges, etc., do not match the new view definition. If there are some, delete them before reexecuting the <create view statement>, and recreate them afterwards in a format changed accordingly.


-1034 SERVERDB NOT ACCESSIBLE

Explanation:

The attempt was made to start a session using an ADABAS component. This is not possible, because

1.	the specified SERVERDB name is incorrect or

2.	the database server has not been started yet.

User Action:

1.	Check the specified SERVERDB name.

2.	Start the database server.


-1101 TOO COMPLICATED SQL STATEMENT (BUFFER LIMIT)

Explanation:

The system needs more than 8 KB for the internal representation of the SQL statement and the data.

User Action:

The SQL statement should be simplified or split into several SQL statements.


-1102 TOO COMPLICATED SQL STATEMENT (TOO MANY SUBQUERIES)

Explanation:

1.	The issued SQL statement contains too many subqueries. The number of permissible subqueries depends on the kind of SQL statement involved.

2.	Subqueries were specified in a <table expression> as well as in the <where clause> of an SQL statement containing at least one corresponding subquery. This is not allowed.

User Action:

The SQL statement should be simplified or split into several SQL statements.


-1103 TOO COMPLICATED SQL STATEMENT

Explanation:

The number of operations, functions, and conditions is too large.

User Action:

The SQL statement should be simplified or the attempt can be made to obtain the effect of the SQL statement with several SQL statements.


-1200 TOO FEW VALUES

Explanation:

In case of an <insert statement> or <update statement>, the number of specified values is less than the number of column names (possibly implicitly specified).

User Action:

Adapt the number of specified values in the SQL statement to the number of specified column names.

Use a <query statement> issued on the system table DOMAIN.COLUMNS for an <insert statement> without column name specification to determine the definition of the used table.


-1201 TOO FEW COLUMNS

Explanation:

For a <referential constraint definition>, less <referencing column>s than <referenced column>s were specified. The number of columns specified for the referencing table must correspond to the number of the <referenced column>s of the <referenced table> specified implicitly or explicitly.

User Action:

Use a <query statement> issued on the system table DOMAIN.COLUMNS to determine the definition of the key columns of the <referenced table>. Use a <query statement> issued on the system table DOMAIN.IND_USES_COL to find out the indexes of the <referenced table>. The specification of the referencing table columns must be adapted accordingly.


-1402 INTEGRITY VIOLATION

Explanation:

Insertions or updates would violate integrity constraints specified in the definition of the base or view table.

User Action:

The error message specifies the column which would violate the integrity constraints.

Correct the input value for the corresponding column.


-1406 OUTPUT VALUE TRUNCATED

Explanation:

The column's range of values is greater than that of the SQL variable. The value was truncated when being inserted into the SQL variable.

User Action:

Adapt the range of values of the SQL variable to that of the column.


-1556 DATA SPACE FULL (EMERGENCY SHUTDOWN)

Explanation:

The data devspace of the SERVERDB is full. The issued SQL statement fails. ADABAS implicitly performs a SHUTDOWN.

User Action:

The SERVERDB must be enlarged by assigning additional DEVSPACEs. Subsequently, the Operating / Restart / Warm menu function in the ADABAS component CONTROL must be executed to achieve data consistency for all the transactions carried out.


-1754 A TABLE MAY CONTAIN ONLY ONE COLUMN OF TYPE LONG

Explanation:

In SQLMODE ORACLE, only one column of data type LONG is permitted in a <create table statement>.

User Action:

1.	Use only one column of data type LONG.

2.	If you can do without ORACLE7 compatibility, generate the <create table statement> with modified data types, if required, and several LONG columns in SQLMODE ADABAS.


-1755 SQL STATEMENT WILL DROP FURTHER OBJECTS ( USE CASCADE )

Explanation:

A <drop user statement>, <drop table statement>, <drop view statement>, or <revoke statement> was specified for which the CASCADE option had not been specified neither implicitly nor explicitly. Other objects depend on the object to be deleted. These objects must be deleted as well. But this is only possible with an implicit or explicit specification of the CASCADE option.

User Action:

Before specifying the same SQL statement with CASCADE option, you should check which depending objects exist.


-2000 ROW IS TOO LONG

Explanation:

When (re-)defining a table, the length of a table row exceeds 4047 bytes.

User Action:

1.	One or more columns must be removed from a <create table statement> or their lengths must be reduced.

2.	One or more columns must be removed from an <alter table statement> or their lengths must be reduced.

Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the current definition of the table.


-2001 KEY IS TOO LONG

Explanation:

1.	For a <create table statement> or <alter table statement>, the sum of the key column lengths must not exceed 254 characters.

2.	When creating a named index, the sum of the column lengths for the index to be created must not exceed 254 characters.

User Action:

1.	Correct the definition of the lengths accordingly or try to use less key columns.

2.	Try to create the named index with less columns.


-2002 ONE OUTPUT COLUMN TOO LONG

Explanation:

The concatenation of values resulted in an excessively long alphanumeric value.

User Action:

You must do without this kind of output. If it can be assumed that all values in a column are shorter than the maximum length defined for this column, the attempt can be made to reduce the result to less characters by applying the SUBSTR function. In any case, the columns and expressions involved in a concatenation can be output separately.


-2003 OUTPUT COLUMNS ARE TOO LONG

Explanation:

There is one of three possible causes.

1.	The total length of the output columns exceeds 4048.

2.	The total length of the output columns, together with the columns specified in the <order clause> or <group clause>, exceeds 4048.

3.	The total length of the output columns, together with the correlated columns and columns of <predicate>s which contain a <subquery>, exceeds 4048 in an SQL statement with correlated subqueries.

User Action:

1.	The number of output columns must be reduced.

2.	The attempt should be made to do without sorting or grouping, or to perform the sorting or grouping across shorter or fewer columns.


-2004 NUMERIC CONSTANT TOO LONG

Explanation:

A number was entered which

1.	contains more than 18 digits or

2.	does not comply with the definition of the range of values.

User Action:

The number which was incorrectly entered may be determined from the position specification in the error message.

1.	The number must be reduced to 18 significant digits and be specified as <floating point literal>, if necessary.

2.	The definition of the range of values must be checked and the specification of the number must be corrected accordingly.


-2008 DEVSPACE SIZE IS TOO SMALL

Explanation:

The DEVSPACE size specified during installation is greater than the space available on the specified DEVSPACE.

User Action:

Repeat the command with a smaller DEVSPACE size.


-2009 JOIN COLUMNS ARE TOO LONG

Explanation:

The internal length of a table's join columns must not exceed 250 characters. Join columns are the columns that are contained in a <join predicate>.

An example is 'WHERE (S.A = T.V AND S.B < T.W)'. The join columns of the table S are the columns S.A and S.B. The internal length of the join columns of S is the internal length of the column S.A plus the internal length of the column S.B. The internal length of the join columns of S must not exceed 250.

User Action:

You can attempt to achieve the expected result by issuing several <query statement>s and creating tables as temporary results.


-2010 ASSIGNMENT IMPOSSIBLE, CHAR VALUE TOO LONG

Explanation:

In an <insert statement> with <query expression> or in an <update statement>, the attempt was made to assign a character string to a column of data type CHAR. This character string was too long. The error message is returned for the first occurring value with an exceeding length, not while analyzing the maximum column lengths.

User Action:

Use SELECT ... WHERE LENGTH (<column name>) > <unsigned integer> to find out the rows containing a value with an exceeding length.

The length of the corresponding column can be increased by an <alter table statement>.


-2012 VIEW COLUMN LIST TOO LONG

Explanation:

In a <create view statement>, the number of view columns to be created must be equal to the number of columns issued as <query expression> result. In the present case, the attempt was made to create more view table columns than columns are available in the <query expression> result.

User Action:

Reduce the number of view table columns specified in the SQL statement.


-2013 SELECT COLUMN LIST TOO LONG

Explanation:

There is one of three possible causes.

1.	In a <create view statement>, the number of view columns to be defined must be equal to the number of columns issued as <query expression> result. In the present case, there are more columns in the <query expression> result than view table columns defined.

2.	The number of <subquery> output columns specified in a <set update clause> must be precisely one. In some SQLMODEs, this restriction also applies to the <comparison predicate>s, <quantified predicate>s, and <in predicate>s. In the present case, the <subquery> produced more than one output column.

3.	An SQL statement for data retrieval was issued. The number of output columns must be less than or equal to 254. This number was exceeded.

User Action:

1.	The number of view table columns specified in the <create view statement> must be increased or the number of output columns of the <query expression> must be reduced.

2.	The number of output columns of the <subquery> must be limited to one.

3.	The data retrieval statement must be corrected by removing one or more output columns.


-2014 IDENTIFIER TOO LONG

Explanation:

The specified identifier is too long for the SQLMODE ANSI.

User Action:

Specify an identifier that does not exceed 18 characters.


-2020 DATA BUFFER TOO SMALL

Explanation:

There is no free data buffer space available at the time. The execution of the SQL statement was cancelled. ADABAS implicitly performs a SHUTDOWN.

User Action:

Perform a RESTART of the database with an expanded data buffer (installation parameter DATA_CACHE_PAGES).


-2025 INVALID NUMBER OF BACKUP DEVICES

Explanation:

The number of backup devices specified for a save or restore operation does not correspond to the installation parameter MAXBACKUPDEVS.

User Action:

Use the ADABAS component CONTROL to check and modify, if necessary, the parameter.


-3000 INVALID HOST FILE CONTENT

Explanation:

The host file or backup device used for the Backup / Restore menu function in the ADABAS component CONTROL has no contents that correspond to the command.

User Action:

Specify the host file or backup device that suits the Backup / Restore menu function.

In multivolume processing, all versions loaded by that time must be reloaded.


-3002 INVALID DATATYPE

Explanation:

The specified data type is unknown in the currently valid SQLMODE.

User Action:

The valid data types are described in the chapter <column definition> in the Reference online help. Use one of the data types specified there.


-3003 INVALID USER NAME

Explanation:

The specified user name does not comply with the syntax for <identifier>s.

User Action:

Correct the user name specified in the SQL statement.


-3004 INVALID HOST FILE SEQUENCE

Explanation:

The host file or backup device specified in multivolume processing to continue the Backup / Restore menu function in the ADABAS component CONTROL has no contents that correspond to the command executed by  that time.

User Action:

The error message contains an additional error description which must be interpreted according to the used operating system.

Specify the host file or backup device that is suitable for continuing the menu function.


-3005 INVALID SQL STATEMENT

Explanation:

The SQL statement either contains a typing error within the first two keywords, or is unknown in the current SQLMODE, or is not permitted in the current ADABAS version.

User Action:

Correct the typing errors, or specify another SQL statement.


-3007 INVALID SEQUENCE OF DML AND DDL STATEMENTS

Explanation:

Modifications were made to the catalog in the time between a <query statement> which does not generate a result table and the corresponding <fetch statement>s. These modifications concerned the underlying table of the <query statement>.

User Action:

Repeat the <query statement> and the <fetch statement>s.


-3008 INVALID KEYWORD OR MISSING DELIMITER

Explanation:

The SQL statement contains an incorrect keyword, or a keyword unknown in the currently valid SQLMODE, or a keyword or delimiter is missing.

User Action:

Correct the SQL statement according to the syntax description and the currently valid SQLMODE.


-3009 INVALID TABLE NAME

Explanation:

The specified table name does not comply with the syntax for <identifier>s.

User Action:

Correct the table name specified in the SQL statement.


-3010 INVALID CHARACTER VALUE

Explanation:

The attempt was made to assign a value that contains binary zeros to a column of data type CHAR with code attribute ASCII or EBCDIC.

User Action:

Modify the program in such a way that blanks replace the binary zeros.


-3011 INVALID COLUMN NAME

Explanation:

The specified column name does not comply with the syntax for <identifier>s.

User Action:

Correct the column name specified in the SQL statement.


-3014 INVALID END OF SQL STATEMENT

Explanation:

According to the syntax, the specified SQL statement is not allowed in the currently valid SQLMODE.

User Action:

The error position shows the location where the specified SQL statement deviates from the permitted syntax.


-3016 INVALID NUMERIC CONSTANT

Explanation:

1.	The specified number does not match the column data type.

2.	The specified length of the function's result, e.g., LPAD, CHR etc., is invalid. It must be between 1 and the maximum length valid for a CHAR-type column.

User Action:

1.	Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the data type of the column.

2.	Correct the specified length of the function's result.


-3017 INVALID UNSIGNED INTEGER

Explanation:

No valid number was specified.

User Action:

Correct the SQL statement.


-3018 INVALID NUMERIC PARAMETER

Explanation:

The specified value is not a valid number.

User Action:

Check the numeric value entered as parameter.


-3019 INVALID EXPONENT

Explanation:

There are two possible causes.

1.	A numeric final or temporary result is greater or less than the values which can be represented by a floating point number.

2.	A numeric value is greater or less than permitted by the data type of a specified column.

User Action:

1.	If a numeric intermediate result is too large or too small, the attempt can be made to prevent an overflow or underflow by rearranging the arithmetic operations.

2.	Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the data type of the column. The values must be corrected accordingly.


-3020 INVALID LENGTH FOR THIS DATA TYPE

Explanation:

The specified length is not permitted for the data type.

User Action:

1.	Choose a value between 1 and 254 (SQLMODE ANSI) or between 1 and 2000 (SQLMODE ORACLE) or between 1 and 4000 (SQLMODEs ADABAS and DB2) for the length attribute of a CHAR-type column.

2.	Choose a value between 1 and 18 for the precision of a FIXED- or FLOAT-type column.


-3021 INVALID MIXTURE OF FUNCTIONS AND COLUMNS

Explanation:

1.	When quantity functions (COUNT, MAX, MIN, SUM, AVG, VARIANCE, STDDEV) occur in a <select column>, non-group columns are not allowed in the <select column>s.

2.	It is not allowed to nest quantity functions, e.g., AVG(SUM...).

3.	A corresponding subquery S contained in the <where clause> of the <query spec> Q must not contain quantity functions for columns of tables specified in the <from clause> of the <query spec> Q.

User Action:

Correct the SQL statement.

Instead of nesting the quantity functions, you can attempt to achieve the desired effect by several <query statement>s, each containing only one quantity function.

To achieve the effect within a <query statement>, specify a <query expression> in the <from clause>.


-3022 INVALID NUMBER OF TABLES FOR OUTER JOIN

Explanation:

If an <outer join indicator> was specified in at least one <join predicate> of the <query spec>, the number of the underlying tables of the <query spec> <from clause> must be precisely two or the following must apply:

a)	<outer join indicator>s are only specified for one of the tables specified in the <from clause>.

b)	All <join predicate>s of this table related to just one other table contain the <outer join indicator>.

c)	All the other <join predicate>s do not contain an <outer join indicator>.

User Action:

The attempt should be made to add the missing <outer join indicator>s, if necessary, or to split the SQL statement into several SQL statements, or to achieve the desired effect by <query expression>s in the <from clause>.


-3024 INVALID NUMERIC EXPRESSION

Explanation:

It was intended to perform a division by 0.

1.	The currently valid SQLMODE is ORACLE or ANSI or

2.	this division does not belong to a <select column> of the outermost <query spec>.

User Action:

Check whether this error can be prevented by using appropriate <predicate>s.


-3025 INVALID DEFAULT CODE

Explanation:

The DEFAULT CODE specified during installation is invalid.

User Action:

Specify ASCII, EBCDIC, or INTERNAL for the DEFAULT CODE in the command.


-3027 INVALID LOCK TIMEOUT

Explanation:

An invalid value was specified for the LOCK TIMEOUT during installation.

User Action:

Choose a value between 30 and 86400 seconds for the LOCK TIMEOUT.


-3028 INVALID LOG MODE

Explanation:

The LOG MODE specified during installation is invalid or the specifications made for ARCHLOG do not match the LOG MODE. No ARCHLOG specification can be made for the LOG MODEs DEMO and SINGLE.

User Action:

Specify NORMAL, DUAL, SINGLE, or DEMO for the LOG MODE in the command. The specifications for the LOG DEVSPACEs must be adapted.


-3029 INVALID NUMBER OF LOG DEVSPACES

Explanation:

The number of archive LOG DEVSPACEs specified during installation is invalid. For the LOG MODE DEMO or SINGLE, the value must lie between 0 and 7; otherwise, it must lie between 1 and 7.

User Action:

Correct the specifications in the command.


-3030 INVALID SESSION TIMEOUT

Explanation:

1.	The value specified for the SESSION TIMEOUT during installation is invalid.

2.	If the CONNECT statement is specified with a TIMEOUT value, this value must be less than or equal to the maximum TIMEOUT value possible for the user concerned.

User Action:

1.	Choose a value between 30 and 32400 seconds for the SESSION TIMEOUT.

2.	If no user-specific TIMEOUT value was defined in the <create user statement> or <create usergroup statement> for the current user, this maximum value is equal to the installation parameter SESSION TIMEOUT.

If a user-specific TIMEOUT value was defined in the <create user statement> or <create usergroup statement>, this is the maximum value.

3.	If 0 is specified for the TIMEOUT value in the CONNECT statement, periods of inactivity during a session are not checked.


-3031 INVALID REQUEST TIMEOUT

Explanation:

The REQUEST TIMEOUT specified during installation is invalid.

User Action:

Choose a value between 30 and 86400 seconds for the installation parameter REQUEST TIMEOUT.


-3034 INVALID LOG SEGMENT SIZE

Explanation:

An invalid value was specified for LOG SEGMENT SIZE during installation.

User Action:

Choose a value for the installation parameter LOG SEGMENT SIZE which does not exceed the log size.


-3035 INVALID DATE TIME FORMAT

Explanation:

The DATE TIME FORMAT specified during installation is invalid.

User Action:

Specify EUR, INTERNAL, ISO, JIS, or USA for the date and time format.


-3036 INVALID NUMBER OF DATA DEVSPACES

Explanation:

An invalid value was specified for the number of data DEVSPACEs during installation.

User Action:

Choose a value between 1 and 64 for the number of data DEVSPACEs.


-3037 INVALID DEVSPACE NAME

Explanation:

The DEVSPACE name specified during installation is invalid. This name depends on the environment in which ADABAS is running. Usually, it is a host file name.

User Action:

The error message contains the incorrect DEVSPACE name.

The name must meet the conventions of the environment in which ADABAS is running.


-3038 INVALID DEVSPACE SIZE

Explanation:

The value for DEVSPACE SIZE specified during installation is not a valid number.

User Action:

Specify a valid number for DEVSPACE SIZE.


-3044 INVALID PERMLIMIT SIZE

Explanation:

No positive integer was specified for the PERMLIMIT or TEMPLIMIT size in a <create user statement>, <create usergroup statement>, <alter user statement>, or <alter usergroup statement>.

User Action:

Specify a valid number.


-3046 INVALID CHAR POSITION IN STRING FUNCTION

Explanation:

An invalid value was specified for a position in a <string function>.

User Action:

In the SQL statement, a value must be specified for a position which is greater than 0 and less than or equal to the defined column width.


-3048 INVALID DATE FORMAT

Explanation:

The specified value is not a valid date value or does not correspond to the date and time format chosen during installation or the current session.

User Action:

Correct the date value.


-3049 INVALID TIME FORMAT

Explanation:

The specified value is not a valid time value or does not correspond to the date and time format chosen during installation or the current session.

User Action:

Correct the time value.


-3050 INVALID TIMESTAMP FORMAT

Explanation:

The specified value is not a valid timestamp value or does not correspond to the date and time format chosen during installation or the current session.

User Action:

Correct the timestamp value.


-3051 INVALID CACHELIMIT VALUE

Explanation:

If a CACHELIMIT value is specified for the CONNECT statement, this value must be less than or equal to the maximum CACHELIMIT value possible for this user.

User Action:

If a CACHELIMIT value was defined for this user with the <create user statement> or <create usergroup statement>, then this is the maximum value. Otherwise, the maximum value is determined with the installation parameter MAX_TEMP_CACHE.


-3052 INVALID TERMCHAR SET

Explanation:

If a terminal character set is specified for a CONNECT statement, the code type of this character set (ASCII or EBCDIC) must correspond to the code type of the terminal.

User Action:

Use another terminal character set.


-3054 INVALID BLOCK SIZE

Explanation:

An invalid value was specified for the I/O blocking size for the Backup / Save / Data Quick menu function in the ADABAS component CONTROL.

User Action:

Specify a value between 1 and 16 in the command. This value indicates the number of 4KB units which form an I/O operation.


-3055 INVALID SERVERDB

Explanation:

1.	The specified combination of SERVERDB and SERVERNODE is unknown.

2.	During installation of a SERVERDB that is to become part of a distributed database, it is not allowed to specify the local SERVERDB as REMOTE SERVERDB.

User Action:

Specify a valid combination of SERVERDB and SERVERNODE in the command.


-3056 INVALID SERVERNODE

Explanation:

During installation of a SERVERDB that is to become part of a distributed database, it is not allowed to specify a SERVERNODE which only differs from any existing SERVERNODE by its upper/lowercase characters.

User Action:

Choose another SERVERNODE or use the notation of the existing SERVERNODE.


-3059 INVALID DAY OF WEEK

Explanation:

For a date specification, an invalid day of week was specified in the chosen language or format. For the format element DAY, the days of week must be written in full length; for DY, they must be specified with their three-letter abbreviation.

User Action:

Check the chosen language and format and repeat the SQL statement with a correct day of week specification.


-3060 INVALID ESCAPE SEQUENCE

Explanation:

The escape character may only be placed before a <match char> which is identical to the escape character, before a <match string>, or before a <match set> which is not a <match char>.

User Action:

Remove the exceeding escape character.


-3061 INVALID ESCAPE VALUE

Explanation:

Exactly one character is valid for an escape value.

User Action:

Reduce the escape value to one character.


-3062 INVALID MONTH

Explanation:

For a date specification, an invalid month was specified in the chosen language or format. For the format element MONTH, the months must be written in full length; for MON, they must be specified with their three-letter abbreviation.

User Action:

Check the chosen language and format, and repeat the SQL statement with a correct month specification.


-3063 INVALID FORMAT CODE

Explanation:

The format specification in a function for date or number conversion contains an invalid format element.

User Action:

Remove the invalid format element.


-3064 DATE INPUT VALUE OUT OF RANGE

Explanation:

An invalid value was specified for a format element in a function that converts a value into a date value. The following limits are valid for these format elements: year (YYYY): 1 to 4713; day of month (DD): 1 to 28/29/30/31; day of year (DDD): 1 to 365/366; day of week (D): 1 to 7; hours (HH,HH12): 1 to 12; hours (HH24): 0 to 23; minutes (MI), and seconds (SS): 0 to 59; seconds of day (SSSSS): 0 to 86399;

Julian day (J): 1 to 3442447.

User Action:

Correct the value.


-3065 INVALID DATE INPUT VALUE

Explanation:

The value to be converted into a date value contains an invalid element, or too many or too few elements.

User Action:

Correct the value according to the format.


-3066 DATE INPUT VALUE INCONSISTENT

Explanation:

Data of two format elements was converted. The values of the data are contradictory. Perhaps a Julian day was specified which does not lie within the specified year or month, or denotes another day of month; or the seconds of day were specified but do not correspond to the specified hours or minutes or seconds of minute.

User Action:

1.	One of the format elements the values of which contradict each other should be omitted.

2.	The values of the two format elements should be adapted.


-3067 INVALID TIMEZONE

Explanation:

An invalid value for timezone was specified in the function NEW_TIME.

User Action:

Repeat the SQL statement with a valid timezone.


-3102 INVALID SUBTRANS STRUCTURE

Explanation:

In a DB procedure, more or less subtransactions were dynamically opened than closed. The subtransactions opened but not closed until the end of the DB procedure were rolled back.

User Action:

Check which error in the DB procedure generated such nesting of subtransactions. Correct the DB procedure.


-3103 INVALID SEQUENCE DEFINITION

Explanation:

There are three possible causes.

1.	In the <create sequence statement>, the value 0 was specified for the interval between two numbers to be created by the sequence. This is not allowed.

2.	In the <create sequence statement>, a starting value was specified which is not within the range defined by the minimum and maximum value; or a minimum value was specified that is greater than the maximum value.

3.	The attempt was made to generate the 9th sequence on this SERVERDB. This is not yet possible.

User Action:

1.	Repeat the command with a positive or negative integer.

2.	Change the starting value and/or the minimum and maximum values and repeat the command.

3.	Do without this sequence, or check whether you can do without another sequence on this SERVERDB.


-3995 INVALID PATTERN

Explanation:

The value specified in a <like predicate> does not comply with the syntax of <like expression>s.

User Action:

The value must be corrected according to the syntax rules of a <like expression> in a <like predicate>.


-3999 INVALID PARAMETER

Explanation:

1.	An invalid installation parameter was specified.

2.	An invalid parameter was specified in the sequence of parameters of a <create trigger statement>. The usage of OLD is invalid in an INSERT trigger, the usage of NEW is invalid in a DELETE trigger.

User Action:

1.	The error message contains a more detailed description of the error. The parameter values must be corrected accordingly.

2.	Correct the parameters accordingly.


-4000 UNKNOWN RESULT TABLE

Explanation:

There is no result table (any more) with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.TABLES to find out the names of the existing result tables. Correct the name of the result table or check why the result table with the specified name was deleted.

A <commit statement> issued in the SQLMODEs ANSI and DB2 implicitly closes all result tables. This behavior can be prevented in the SQLMODE DB2 by specifying 'WITH HOLD'.

Except for the SQLMODE ORACLE, a <rollback statement> implicitly closes all result tables generated within this transaction.


-4002 UNKNOWN PASSWORD

Explanation:

The specified password is unknown.

User Action:

Repeat the <alter password statement> using the correct password.


-4003 UNKNOWN USER NAME

Explanation:

There is no user with this name.

User Action:

A DBA or the SYSDBA can use a <query statement> issued on the system table DOMAIN.USERS to find out the known user names. Other users can use a <query statement> issued on the system table DOMAIN.USERS to find out the users which belong to the same DBA as they do. Repeat the SQL statement with a known user name.


-4004 UNKNOWN TABLE NAME

Explanation:

A table with the specified name is not known to you. This table may not exist; or this table exists but you have no privileges for it.

User Action:

Use a <query statement> issued on the system table DOMAIN.TABLES to find out the names of the tables for which you have privileges. Then correct the table name. It may be sufficient to place the missing <owner> in front of it. Otherwise, create a table with the desired name or check why you have no privileges for the existing table.


-4005 UNKNOWN COLUMN NAME

Explanation:

There is no column with the specified name in any of the specified tables.

User Action:

Use <query statement>s issued on the system table DOMAIN.COLUMNS to find out the names of the columns existing in the tables. Correct the column name.


-4006 UNKNOWN DOMAIN NAME

Explanation:

There is no domain with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.DOMAINS to see a list of the known domains. Correct the domain name in the SQL statement accordingly. It may be sufficient to place the missing <owner> in front of the statement.

A user with DBA status can create a domain with the desired name and features.


-4007 UNKNOWN SYNONYM NAME

Explanation:

There is no synonym with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.SYN_REFS_TAB to see a list of the existing synonym names. Correct the synonym name in the SQL statement accordingly.


-4008 UNKNOWN USER NAME/PASSWORD COMBINATION

Explanation:

The specified combination of user name and password is unknown. ADABAS can only be accessed by a combination that is known to the database.

User Action:

Change the user or password specification in the SQL statement.


-4009 UNKNOWN REFERENTIAL CONSTRAINT NAME

Explanation:

There is no <referential constraint definition> with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.COL_REFS_COL to see a list of the existing <referential constraint definition>s. Change the <referential constraint name> in the SQL statement accordingly.


-4010 UNKNOWN MAPCHAR SET NAME

Explanation:

There is no MAPCHAR SET with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.MAPCHARSETS to see a list of the available MAPCHAR SETs. Change the name in the SQL statement accordingly.


-4011 UNKNOWN INDEX NAME

Explanation:

There is no named index with the specified name for the used table.

User Action:

Use a <query statement> issued on the system table DOMAIN.IND_USES_COL to see a list of the existing indexes. Change the index name in the SQL statement accordingly.


-4013 UNKNOWN USERGROUP NAME

Explanation:

There is no usergroup with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.USERS to see a list of the existing usergroup names. Change the group name in the SQL statement accordingly.


-4014 UNKNOWN SERVERDB NAME

Explanation:

There is no SERVERDB with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.SERVERDBS to see a list of the existing SERVERDB names. Change the SERVERDB name in the SQL statement accordingly.


-4015 UNKNOWN TERMCHAR SET NAME

Explanation:

There is no character set with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.TERMCHARSETS to see a list of the existing character set names. Change the character set name in the SQL statement changed accordingly.


-4016 UNKNOWN PROCEDURE NAME

Explanation:

There is no DB procedure with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.DBPROCEDURES to see a list of the existing DB procedures. Change the procedure name in the SQL statement accordingly.


-4017 UNKNOWN CONSTRAINT

Explanation:

There is no <constraint definition> for the specified column.

User Action:

It is not necessary to drop the <constraint definition>. An update of a <constraint definition> must be replaced with an add operation.


-4018 UNKNOWN DEFAULT

Explanation:

There is no default specification for the specified column.

User Action:

It is not necessary to drop the default specification. An update of a default specification must be replaced with an add operation.


-4019 UNKNOWN TRIGGER NAME

Explanation:

There is no trigger with the specified name.

User Action:

Use the <show trigger statement> to see a list of the existing triggers.


-4020 UNKNOWN SEQUENCE NAME

Explanation:

There is no sequence with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.SEQUENCES to see a list of the existing sequences.


-4023 UNKNOWN FUNCTION NAME

Explanation:

1.	There is no function with the specified name.

2.	The attempt was made to use a <named query expression> that is not valid at this place instead of a <query expression>.

User Action:

Replace the <named query expression> with a <query expression>. If the error message occurs although there is no <named query expression> in the SQL statement, check whether the specified function is only not offered in

the used SQLMODE.

1.	Do without the specified function.

2.	Open a session using the SQLMODE in which the function is available.

3.	A DB function with the specified name and the desired functionality is generated.


-4024 UNKNOWN NAME

Explanation:

There is no database object with the specified name.

User Action:

Use <query statement>s issued on system tables to find out which objects you are authorized to see.


-5001 MISSING PRIVILEGE

Explanation:

You are not authorized to execute the SQL statement.

User Action:

Use a <query statement> issued on the system table DOMAIN.USR_USES_COL to find out the privileges you have for the specified table or its columns. It is not possible to execute the desired SQL statement.


-5003 MISSING KEY SPECIFICATION

Explanation:

The SQL statement requires a primary key specification. The primary key was omitted or is incomplete.

User Action:

Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the key columns of the table. Correct the key specified in the SQL statement, or insert a key specification into the SQL statement.


-5004 MISSING CONSTANT

Explanation:

A constant is missing in the SQL statement.

User Action:

Insert a constant into the SQL statement.


-5005 MISSING COLUMN, NULL VALUE NOT ALLOWED

Explanation:

The <insert statement> or <update statement> must contain non-NULL values for all mandatory columns. If <key spec>s are specified, non-NULL values must be specified for all key columns.

User Action:

Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the table's mandatory and key columns.


-5006 MISSING IDENTIFIER

Explanation:

An <identifier> is missing.

User Action:

The error position indicates the location of the missing <identifier>. Insert an <identifier> into the SQL statement.


-5007 MISSING NUMERIC CONSTANT

Explanation:

A number is missing.

User Action:

The error position indicates the location of the missing number. Insert a number into the SQL statement.


-5008 MISSING STRING CONSTANT

Explanation:

A string constant is missing in the issued SQL statement.

User Action:

Insert a <string literal> into the SQL statement.


-5009 MISSING INTEGER

Explanation:

An integer is missing.

User Action:

Insert an integer into the SQL statement.


-5010 MISSING VALUE SPECIFICATION

Explanation:

A value is missing, or the specified value is not allowed.

User Action:

Correct the value specified in the SQL statement, or insert a value into the SQL statement.


-5011 MISSING INDEX VALUE SPECIFICATION

Explanation:

If an <index pos spec> is specified after a <dir2 spec> in a <select ordered statement>, a value must be specified for each column of the index.

User Action:

Use a <query statement> issued on the system table DOMAIN.IND_USES_COL to find out the columns that form the specified index. Repeat the SQL statement with all required column value specifications.


-5012 MISSING DEFINITE TABLE NAME

Explanation:

If a table name in a <from clause> is used several times with different <owner>s, then the table name must always be specified with the desired <owner> within this SQL statement.

User Action:

Add the <owner>s to the table names.


-5013 MISSING UPDATE COLUMN

Explanation:

The attempt was made to update at least one column value of an updatable join view table column using an <update statement>. This column value can only be updated together with other column values. At least one of the required column values is missing in the <update statement>.

User Action:

Insert the missing column values into the <update statement> or execute <update statement>s for the underlying table(s) of the updatable join view table.


-5014 MISSING DEFINITE COLUMN NAME

Explanation:

The number of tables specified in a <from clause> of the SQL statement is greater than 1. A <column name> without preceding <table name> was used, and this <column name> occurs in more than one of the tables specified in the <from clause>.

User Action:

To ensure the <column name>'s uniqueness, place the desired <table name> in front of the <column name>.


-6000 DUPLICATE TABLE NAME

Explanation:

There is already a table with the specified name.

User Action:

Use another name for the table to be created.


-6001 DUPLICATE COLUMN NAME

Explanation:

1.	The column names of a table must differ from each other. Base tables without user-defined key columns and named result tables contain the implicitly created column 'SYSKEY'.

2.	Named result tables with columns which have not been explicitly named and which do not inherit a column name of the underlying base table, implicitly get the column name 'EXPRESSION_'. '_' stands thereby for a positive integer.

3.	A column must not be specified more than once in an <insert statement> or <update statement> or in <key spec>s.

User Action:

1.	Use different column names.

2.	In a <create view statement> or <query statement>, uniqueness of the column names can be achieved by <reference name> specifications in the <select column>s. In a <create view statement>, uniqueness can also be obtained by <alias name> specifications.

3.	Correct the repeated specification of the same column.


-6002 DUPLICATE PRIVILEGE

Explanation:

A privilege to be granted was listed twice in the SQL statement.

User Action:

Remove one of these privileges from the SQL statement.


-6003 DUPLICATE RESULT TABLE NAME

Explanation:

The SQLMODEs ANSI and DB2 require that a result table generated by DECLARE CURSOR is closed using a <close statement>, before the result table name can be used to open a new result table within the same transaction.

User Action:

Insert a <close statement> into the ADABAS application.


-6006 DUPLICATE NAME

Explanation:

There is already a data object with the specified name.

User Action:

Repeat the SQL statement using another name.


-6007 DUPLICATE ORDER COLUMN

Explanation:

The <order clause> of a <query statement> lists the same column name or column number twice.

User Action:

Decide which of the duplicate column names or numbers in the sort criteria order shall be kept. One of the names or numbers must be removed.


-6008 DUPLICATE INDEX NAME

Explanation:

There is already an index with the specified name.

User Action:

Repeat the command using another index name, or drop the existing index.


-6009 DUPLICATE REFERENCE NAME

Explanation:

The <from clause> of a <query spec> lists the same reference name twice. This violates the requirement that each table must have a unique reference name.

User Action:

Change one of the reference names.


-6010 DUPLICATE DEVSPACE NAME

Explanation:

For a menu function in the ADABAS component CONTROL, a DEVSPACE name was used more than once or an already used name was specified again to define an additional DEVSPACE.

User Action:

Repeat the command using different DEVSPACE names.


-6011 DUPLICATE CONSTRAINT

Explanation:

There is already a <constraint definition> for the specified column.

User Action:

Do without a <constraint definition> specification, or attempt to obtain the desired effect by changing the existing <constraint definition>. Use a <query statement> issued on the system table DOMAIN.CONSTRAINTS to find out the existing <constraint definition>.


-6012 DUPLICATE DEFAULT

Explanation:

There is already a default specification for the specified column.

User Action:

Do without a default specification, or attempt to obtain the desired effect by changing the existing default. Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the definition of the existing default.


-6013 DUPLICATE TRIGGER DEFINITION

Explanation:

There is already a trigger with the specified name.

User Action:

Use a <query statement> issued on the system table DOMAIN.TRIGGERS to find out the trigger names already used. Specify another name.

Use a <query statement> issued on the system table DOMAIN.TRIGGERS to find out whether the existing trigger has the desired definition and you therefore need not define another trigger.


-6014 DUPLICATE VALUE

Explanation:

1.	When defining a TERMCHAR SET, an internal or external value was specified more than once. There must be a 1:1 relation between the internal and external values.

2.	When defining a MAPCHAR SET, an internal value was specified more than once.

User Action:

1.	Change the definition of the TERMCHAR SET in such a way that the 1:1 relation is not violated.

2.	Change the definition of the MAPCHAR SET in such a way that it is not necessary to specify several mappings for an internal value.


-6016 DUPLICATE FORMAT CODE

Explanation:

1.	A format element was specified several times in the function TO_DATE.

2.	In the format specification of the TO_DATE function, format elements were specified which must not occur together. For example, day of year (DDD) and the Julian day must not occur together. There must not be several specifications denoting the year, e.g., YYYY and IY, or the month, e.g., MM and MONTH.

User Action:

1.	Remove the format elements specified too often.

2.	Remove one of the format elements that cannot occur together.


-6017 DUPLICATE SNAPSHOT LOG

Explanation:

The attempt was made to generate a snapshot log for a table for which a snapshot log is already available.

User Action:

A user action is not required.


-7002 KEY NOT ALLOWED

Explanation:

1.	The <create table statement> must list the key columns first, if they are defined by a KEY specification in a <key or not null spec>.

2.	In a <create table statement>, it is not allowed to specify KEY in a <key or not null spec> and a <key definition>.

3.	It is not possible to change the key columns with a later <alter table statement>.

User Action:

Specify the key columns correctly in the SQL statement.


-7003 NOT NULL NOT ALLOWED

Explanation:

Columns with NOT NULL specification cannot be added to a table with the <alter table statement>.

User Action:

Repeat the SQL statement after removing the specification NOT NULL.


-7004 DEFAULT NOT ALLOWED

Explanation:

1.	Columns with DEFAULT specification cannot be added to a table with the <alter table statement>.

2.	The specification of NOT NULL DEFAULT NULL is not allowed.

User Action:

1.	To add a column with an <alter table statement>, specify it DEFAULT. Then define the DEFAULT in another <alter table statement>. The added column then implicitly obtains the DEFAULT value in all table rows.

2.	Repeat the SQL statement after removing the DEFAULT specification.


-7005 LOWER BOUND GREATER THAN UPPER BOUND NOT ALLOWED

Explanation:

In case of an upper and lower limit specification for a range of values, the lower limit is greater than the upper limit.

User Action:

Correct the values for the upper and lower limit in the SQL statement.


-7006 RESERVED IDENTIFIER NOT ALLOWED

Explanation:

In the current SQLMODE, the specified name is a reserved keyword and must not be used to identify database objects.

User Action:

Correct the SQL statement using another <identifier>.


-7007 KEY COLUMN NOT ALLOWED

Explanation:

A key column specification is not allowed here.

User Action:

Remove the key column specification from the SQL statement.


-7008 UPDATES OF THIS TABLE NOT ALLOWED

Explanation:

The specified table cannot be updated, because

1.	the table specified in an SQL statement with CURRENT OF <result table name> specification is not the table indicated in the <from clause> of the <query statement> which generated the result table <result table name> specified after CURRENT OF.

2.	the SQL statement contains a correlated subquery which uses the table to be updated.

3.	the <query expression> was specified with FOR UPDATE, but the <query expression> contains statement parts which cannot be used together with a FOR UPDATE specification (DISTINCT, <group clause>, UNION, INTERSECT, EXCEPT, <subquery>).

4.	in SQLMODE DB2 the <query expression> pertinent to an SQL statement with CURRENT OF <result table name> specification contains a FOR FETCH ONLY specification.

User Action:

1.	Replace the table name with the name used in the <from clause> of the <query statement>, or issue a new <query statement> that uses the required table name.

2.	In case of the correlated subquery, the desired effect can be obtained by generating a named result table which is then used in the <subquery>.

3.	In case of FOR UPDATE, remove the FOR UPDATE or DISTINCT specification, or the like.

4.	In case of FOR FETCH ONLY, repeat the <query expression> without this specification, or remove the specification of CURRENT OF <result table name> from the SQL statement.


-7009 NULL VALUE IN KEY COLUMN NOT ALLOWED

Explanation:

Key columns must not be set to the NULL value.

User Action:

Use non-NULL values for key columns.


-7011 CORRELATED SUBQUERY NOT ALLOWED

Explanation:

A correlated subquery was used in a <query expression> containing at least a UNION, INTERSECT, or EXCEPT. Presently, this is not allowed.

User Action:

The desired effect can be achieved by splitting the <query statement> into several successive SQL statements.


-7012 MORE THAN ONE UPDATE ROW NOT ALLOWED

Explanation:

The attempt was made to modify several rows with an <update statement>, specifying a new value for a LONG column. This is not allowed.

User Action:

Modify the <update statement> in such a way that only one row is updated or do without the value modification for the LONG column.


-7015 MORE THAN ONE RESULT ROW NOT ALLOWED

Explanation:

1.	This error may occur when a <single select statement> is executed and more than one row complies with the <search condition>.

2.	This error can also occur when a < subquery> specified in a <comparison predicate> or a <set update clause> of an <update statement> is executed and more than one row complies with the <search condition>.

User Action:

1.	The <single select statement> can be replaced with a <query statement> and a sequence of <fetch statement>s; or it can be ensured that at most one row complies with the conditions by expanding the <search condition>.

2.	The <comparison predicate> can be replaced with a <quantified predicate>. The attempt can be made to change the <subquery> in such a way that the <subquery> contains at most one row as the result by specifying DISTINCT or by expanding the <search condition>.


-7016 PARAMETER SPEC NOT ALLOWED IN THIS CONTEXT

Explanation:

1.	The attempt was made to specify a parameter in a <select column>.

2.	The error message can also be returned if a <comparison predicate> of the format '<parameter spec> <comp op> <parameter spec>' occurs within the <search condition>.

3.	The error message can also occur, if a <comparison predicate>, <in predicate>, or <quantified predicate> specifies a comparison between a parameter and a <subquery>.

User Action:

1.	Replace the parameter with a constant.

2.	It is useful to check such a condition within the ADABAS application, not in ADABAS. If this is not possible, replace one of the two parameters with a constant, a column name, or an <expression> which does not only contain parameters.

3.	Replace the parameter with a constant or integrate it into a function (e.g., SUBSTR) so that the data type of the parameter becomes unique.


-7017 USER NOT ALLOWED

Explanation:

1.	You cannot grant privileges to yourself.

2.	The specified names must not be equal in a <grant user statement>.

User Action:

Correct the user name.


-7018 VARIABLE NOT ALLOWED IN VIEW DEFINITION

Explanation:

Parameters must not be specified in the <create view statement>.

User Action:

Use constants instead of variables.


-7019 FEATURE NOT ALLOWED IN VIEW DEFINITION

Explanation:

ROWNO specifications are not allowed in a view definition.

User Action:

Remove the ROWNO specification from the SQL statement.


-7021 VIEW COLUMN DERIVED FROM FUNCTION NOT ALLOWED

Explanation:

A view table column was specified which was the result of an arithmetic expression or of a set function. In the present case, it is not allowed to specify such a column.

User Action:

The attempt can be made to achieve the desired effect with one or more other SQL statements.


-7022 COLUMNS OF MORE THAN ONE TABLE NOT ALLOWED

Explanation:

In certain cases, it is not allowed to address columns of more than one table within an <expression>.

User Action:

Consider whether issuing other SQL statements could give the desired result.


-7023 DROPPING OF ALL COLUMNS NOT ALLOWED

Explanation:

The attempt was made to drop all columns of a table.

User Action:

This can only be done by using the <drop table statement>. The <drop table statement> implicitly drops all view tables, privileges, indexes, <referential constraint definition>s, etc. which depend on this table. Afterwards, a new table with the same name can be created with the <create table statement>.


-7024 ALTER COLUMN NOT ALLOWED, CONSTRAINT VIOLATION

Explanation:

The attempt was made to redefine a <constraint definition> for a particular column. The SQL statement fails when the table contains rows which do not meet the <constraint definition>.

User Action:

1.	Use another <constraint definition> or do not change the <constraint definition>.

2.	Use a <query statement> to find out the rows which do not meet the <constraint definition>. These rows can then be updated or deleted.


-7026 SQL STATEMENT NOT ALLOWED WITHOUT PREVIOUS FETCH

Explanation:

The attempt was made to issue an SQL statement with CURRENT OF <result table name>, without having previously issued a successful <fetch statement> on the specified result table.

User Action:

Repeat the SQL statement, once you have issued a successful <fetch statement> for the result table.


-7029 FUNCTION NOT ALLOWED FOR THIS DATA TYPE

Explanation:

1.	The attempt was made to use one of the functions DATE, TIME, TIMESTAMP, USER, USERGROUP, STAMP, or TRUE or FALSE for a default specification of a column having a data type not comptaible with such a specification.

2.	The attempt was made to call a <function spec> for a value which does not allow this function be applied.

3.	The attempt was made to form a <datetime expression> or <labeled duration> with a value having a data type which is invalid for this purpose.

User Action:

1.	In case of a default specification, another default must be chosen, or the default specification must be removed from the SQL statement.

1.	Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the data types of the specified columns. A check can be made as to whether the desired effect can be achieved by a function converting numbers into character strings or vice versa.

2.	In case of a default specification, another default must be chosen, or the default specification must be removed from the SQL statement.


-7030 PERMLIMIT LESS THAN PERM COUNT NOT ALLOWED

Explanation:

In an <alter user statement> or <alter usergroup statement>, the attempt was made to define a value for PERMLIMIT which was less than the number of 4 KB blocks currently used by the user or usergroup to store private tables.

User Action:

A <show statistics statement> with a USER specification can be used to find out the currently used number of 4 KB blocks. A greater value must be specified for PERMLIMIT or it must be ensured that the user drops tables or deletes rows from tables before the SQL statement can be reissued.


-7031 CONSTRAINT OR DEFAULT FOR DATA TYPE LONG NOT ALLOWED

Explanation:

A LONG column was specified in a <create table statement> together with a <constraint definition> or <default definition>. A <constraint definition> or <default definition> is not allowed for LONG columns.

User Action:

Remove the <constraint definition> or <default definition> from the SQL statement.


-7032 SQL STATEMENT NOT ALLOWED FOR COLUMN OF DATA TYPE LONG

Explanation:

The command cannot be applied to LONG columns.

User Action:

The operations allowed for the data type LONG are described in the Reference online help.


-7034 PERMLIMIT FOR STANDARD USER NOT ALLOWED

Explanation:

The attempt was made to install a STANDARD user with a PERMLIMIT specification. Since STANDARD users are not allowed to create permanent tables, no permanent storage area is available to them.

User Action:

Repeat the SQL statement without PERMLIMIT specification.


-7035 DEFAULT SPECIFICATION NOT ALLOWED FOR THIS COLUMN

Explanation:

An <insert statement> or <update statement> or a <default predicate> was issued with a DEFAULT specification for a column for which no <default value spec> had been defined neither in the <create table statement> nor in a subsequent <alter table statement>.

User Action:

Specify the desired value instead of DEFAULT.


-7036 ROWNO SPECIFICATION NOT ALLOWED IN THIS CONTEXT

Explanation:

One of the following conditions was violated:

1.	The specification ROWNO may only be used in <query statement>s. The <query statement> must not contain a UNION, EXCEPT, or INTERSECT specification.

2.	The <rowno predicate> can be used within the <search condition> in the form 'ROWNO < <rowno spec>' or 'ROWNO <= <rowno spec>'; i.e., ROWNO is placed on the left of the operator.

3.	The <rowno predicate> may occur only once in a <search condition>. It must be connected with other predicates by logical AND.

User Action:

1.	In case of UNION, EXCEPT, or INTERSECT, the effect can be achieved by two successive <query statement>s.

2.	Correct the <search condition> in the SQL statement accordingly.


-7037 NULL VALUE FOR NOT NULL COLUMN NOT ALLOWED

Explanation:

The error message is returned for a <referential constraint definition> with ON DELETE SET NULL specification, if a column of the <referencing column> does not allow the NULL value.

User Action:

Choose another <action> in the <delete rule> or admit the NULL value for the corresponding column(s) in the referencing table.


-7038 FOREIGN KEY COLUMN NOT ALLOWED

Explanation:

A foreign key column is a column which was specified in the <referencing column> of a <referential constraint definition>.

1.	The attempt was made to drop a table column which was specified in a <referencing column> of a <referential constraint definition>.

2.	The attempt was made to delete the key of a table. The columns of the key were specified implicitly or explicitly as <referencing column>s of a <referential constraint definition>.

User Action:

To be able to drop the column or to delete the key, the <referential constraint definition> must be dropped first.


-7039 CYCLE IN REFERENTIAL CONSTRAINT DEFINITION NOT ALLOWED

Explanation:

The attempt was made to create a <referential constraint efinition> which would produce an invalid reference cycle.

The <referential constraint definition> would result in basically contesting situations. ADABAS therefore rejects this definition.

User Action:

This problem needs rethinking and should be solved by another solution.


-7040 REFERENTIAL CONSTRAINT NOT ALLOWED

Explanation:

There is already a <referential constraint definition> with the specified referencing table. Moreover, CASCADE dependency arises. Under these conditions, all <referential constraint definition>s with the indicated referencing table must specify either CASCADE or RESTRICT.

User Action:

Rethink the wanted effect, because it would result in basically contesting situations.

The user may see information about the existing <referential constraint definition>s using a <query statement> issued on the system table DOMAIN.COL_REFS_COL.


-7041 RESULT TABLE NAME NOT ALLOWED

Explanation:

In a <create view statement>, a named result table was specified in a <from clause> of the <query expression>. But only base or view tables may be specified.

User Action:

Specify a base or view table in the SQL statement and add those conditions to the <search condition> which were used for the generation of the result table.


-7042 KEY UPDATE NOT ALLOWED

Explanation:

The attempt was made to change a value of a key column in a temporary table to a new value. This is not possible. Key columns can only be changed in permanent tables.

User Action:

If another key value is wanted, delete the row with the old key value and insert a row with the new key value.


-7043 GROUP MEMBER NOT ALLOWED

Explanation:

There is one of two possible causes.

1.	The attempt was made to grant privileges to a user of a usergroup.

2.	The attempt was made to alter the characteristics of a user who is member of a usergroup using an <alter user statement>.

User characteristics and privileges cannot be altered for members of a usergroup, only for the complete usergroup.

User Action:

A DBA or the SYSDBA can use a <query statement> issued on the system table DOMAIN.USERS to find out the usergroup to which the respective user belongs. Other users only see the users and usergroups which belong to the same DBA as they do.

1.	Grant the privileges to the usergroup to which the user belongs.

2.	Replace the <alter user statement> with an <alter usergroup statement>.


-7044 CLEAR LOG NOT ALLOWED

Explanation:

1.	The Backup / Restore / Clear Log menu function in the ADABAS component CONTROL cannot be executed for a SERVERDB which belongs to a distributed database.

2.	The Backup / Restore / Clear Log menu function in the ADABAS component CONTROL cannot be executed, because the SERVERDB is not in a consistent state.

User Action:

1.	A user action is not possible.

2.	Perform the Backup / Restore / Database menu function before executing this function.


-7045 PARAMETER SPEC NOT ALLOWED

Explanation:

A parameter was specified, although this ADABAS component or this kind of application programming only allows the usage of constants.

User Action:

Replace the parameter with a constant.


-7048 DROP/ALTER USER NOT ALLOWED WHILE USER IS CONNECTED

Explanation:

The attempt was made to drop a user or to alter the characteristics of a user who was connected to ADABAS. This is only permitted for a user who is not connected to ADABAS.

User Action:

Repeat the SQL statement when the user to be dropped or altered is not connected to ADABAS.


-7050 FASTLOAD WITH INDEXED TABLE NOT ALLOWED

Explanation:

An index is created on the table to be loaded. In this case, a fast load is not possible.

User Action:

Drop the index or do without the fast load.


-7051 READ ONLY VIEW WITH CHECK OPTION NOT ALLOWED

Explanation:

The view table to be created is not updatable. The specification WITH CHECK OPTION is not allowed for non-updatable view tables.

User Action:

Repeat the SQL statement without WITH CHECK OPTION.


-7052 SINGLE SELECT NOT ALLOWED

Explanation:

In a <single select statement>, at least a UNION, EXCEPT, or INTERSECT was specified. This is not allowed.

User Action:

Replace the <single select statement> with a <query statement> and a subsequent <fetch statement>.


-7054 PARAMETER IN PARSING EXPLAIN NOT ALLOWED

Explanation:

In an <explain statement>, the specification of parameters is only allowed in the sequence of <parameter spec>s of the <single select statement>.

User Action:

The SQL statement can be repeated, but the parameters must be replaced with constants.


-7055 COLUMN(S) ALREADY INDEXED

Explanation:

There is already an index for the specified column(s).

User Action:

Use a <query statement> issued on the system table DOMAIN.IND_USES_COL to check whether the index values are stored in ascending or descending order. A user action is not required.


-7056 SUBQUERY NOT ALLOWED

Explanation:

A <subquery> specification in a <constraint definition> is not allowed.

User Action:

1.	The attempt can be made to formulate the <search condition> in such a way that the <subquery> is not necessary.

2.	The attempt can be made to achieve the desired effect by defining a trigger that checks the condition.


-7057 VIEW DEFINITION CONTRADICTS NEW TABLE DEFINITION

Explanation:

1.	The attempt was made to add a column to a table or to drop a column from a table. When creating the specified view table, SELECT * was used and new names were assigned to the view table columns. After table modification, the number of names would no longer coincide with the number of table columns.

2.	The attempt was made to drop a <referential constraint definition> which is prerequisite for an updatable join view table.

User Action:

1.	Drop and recreate the view table. Each of the desired columns should be specified in the <select column>s of the <query expression>.

2.	The <referential constraint definition> can only be dropped if the updatable view table was dropped before.


-7058 CORRELATED SUBQUERY WITH SELECT IN FROM CLAUSE NOT ALLOWED

Explanation:

A <query expression> specification in the <from clause> of a correlated subquery is not allowed.

User Action:

The attempt can be made to formulate the correlated subquery in such a way that the <query expression> is no longer needed. If this is not possible, split the SQL statement into at least two SQL statements and generatee a named result table that can be used in the <from clause>.


-7060 REMOTE TABLE LOAD/UNLOAD NOT ALLOWED

Explanation:

DATALOAD with NOLOG option or UNLOAD cannot be performed for a table stored on a SERVERDB other than that to which you are connected.

User Action:

The SQL statement can be repeated if the NOLOG option is not specified or if you connect to the SERVERDB where the table is stored.


-7061 LOCK ROW FOR THIS TABLE NOT ALLOWED

Explanation:

A <lock statement> with <row lock spec> specification can only be performed for an updatable join view table.

But not even updatable join view tables allow a <row lock spec> with OPTIMISTIC specification.

User Action:

The effect can be achieved by several <row lock spec>s issued on the underlying base tables.


-7063 TEMP TABLE NOT ALLOWED

Explanation:

Only a subset of data definition statements is allowed for temporary tables; among them, the SQL statements for creating and dropping tables and for making the existence check.

User Action:

Decide whether the data definition statement can be removed or whether a permanent table is to be created instead of the temporary table.


-7064 FEATURE NOT ALLOWED IN TEMP TABLE DEFINITION

Explanation:

It is not possible to specify a <referential constraint definition> for a temporary table or to create this table WITH REPLICATION.

User Action:

Repeat the SQL statement without the invalid specification, or create a permanent table instead of the temporary table.


-7065 SUBTRANS COMMIT/ROLLBACK NOT ALLOWED WITHOUT SUBTRANS BEGIN

Explanation:

The corresponding SQL statement SUBTRANS BEGIN must have been called for each subtransaction to be closed.

User Action:

Check the ADABAS application for the dynamic behavior of the <subtrans statement>s.


-7066 UNIQUE INDEX REFERENCED BY FOREIGN KEY NOT ALLOWED

Explanation:

The specified index cannot be dropped, because the columns contained in it were specified as referenced columns of the <referenced table> in a <referential constraint definition>.

User Action:

The index can only be dropped after dropping the corresponding <referential constraint definition>. Use a <query statement> issued on the system table DOMAIN.COL_REFS_COL to find out which <referential constraint definition>s are defined.


-7067 UPDATE WITHOUT REPEATED READ NOT ALLOWED

Explanation:

An optimistic lock was set to at least one table row by a previous SQL statement. Afterward, another database user updated one of these rows. The database user who set the optimistic lock can make new changes to this row only after reading it with a (optimistic) lock.

User Action:

The row to be updated must be read again with a (optimistic) lock.


-7068 OUTER JOIN NOT ALLOWED IN THIS CONTEXT

Explanation:

An <outer join indicator> was used in a <comparison predicate> in which no table column was specified in one of the two <expression>s. An <outer join indicator> is only allowed in a <join predicate>.

User Action:

The SQL statement can be repeated without the <outer join indicator>.


-7069 REMOTE WRITE ACCESS IN NOLOG SESSION NOT ALLOWED

Explanation:

The attempt was made to execute an SQL statement for data manipulation. This SQL statement would have to make modifications to the data of a SERVERDB other than that on which the session was opened. This is not allowed for a session which was opened with NOLOG specification in the <connect statement>.

User Action:

You must do without the SQL statement in this session.

1.	You can repeat the SQL statement in a session opened without NOLOG specification.

2.	You can open a new session or more sessions with or without NOLOG specification on the SERVERDB keeping the data to be modified. The SQL statement can be repeated there.


-7070 SNAPSHOT TABLE BASED ON SNAPSHOT TABLE NOT ALLOWED

Explanation:

In a <create snapshot statement>, a snapshot table or a view table was specified as underlying table. The snapshot table or the view table also has an underlying snapshot table. This is not allowed.

User Action:

Do without the definition of the snapshot table, or try to replace the specification of the underlying snapshot table or view table with the specification of the base table(s) or view table(s) underlying that table and the relating conditions.


-7900 DIFFERENT BLOCK SIZES

Explanation:

The block sizes specified for the restore and save differ from each other. The restore cannot be terminated successfully.

User Action:

The block size specified for the corresponding save must be used for the restore operation.


-8000 SERVERDB MUST BE RESTARTED

Explanation:

It is not possible to work on the SERVERDB because it was shut down.

User Action:

The SERVERDB must be started with the Operating / Restart / Warm menu function in the ADABAS component CONTROL.


-8001 USER MUST BE CONNECTED

Explanation:

An ADABAS session can only be opened with a <connect statement>.

User Action:

Specify a <connect statement>.


-8002 USER ALREADY CONNECTED TO THIS USER TASK

Explanation:

A user already connected to the database entered another <connect statement>.

User Action:

If the user wants to continue working under another user name, he must specify first the <release statement> and then a <connect statement>.


-8003 LOG AND DATA MUST BE COMPATIBLE

Explanation:

1.	The data devspace of the SERVERDB and the current log have a different status for the Operating / Restart / Warm menu function in the ADABAS component CONTROL.

2.	The sequence of log versions is incorrect for the Backup / Restore / Log menu function in the ADABAS component CONTROL.

User Action:

1.	Perform the Backup / Restore / Database menu function in the ADABAS component CONTROL with the correct backup version.

2.	The Backup / Restore / Log menu function in the ADABAS component CONTROL must be repeated with all required log versions in the correct order.

Afterwards, it is possible to perform the Operating / Restart / Warm menu function in the ADABAS component CONTROL.


-8004 CONSTANT MUST BE COMPATIBLE WITH COLUMN TYPE AND LENGTH

Explanation:

The specified constant does not match the data type for this column.

User Action:

Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the definition of the affected column. Specify a constant with the correct data type.


-8005 VALUE EXPRESSION MUST BE PARAMETER NAME

Explanation:

When calling a DB procedure, not a parameter but a constant value was specified for an OUT or IN/OUT parameter.

User Action:

Replace the constant specification with a parameter.


-8006 DATA TYPES MUST BE COMPATIBLE

Explanation:

1.	A <function> was applied to a non-permitted argument.

2.	A two-digit operation was applied to non-comparable values.

3.	A <predicate> contains non-comparable data types.

Each data type can be compared to itself. CHAR columns with the different code attributes ASCII and EBCDIC can be compared to each other; they are implicitly adapted. CHAR columns of the code attributes ASCII and EBCDIC can be compared to date, time, and timestamp specifications.

All numbers can be compared to each other.

User Action:

Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the definition of the columns involved. If necessary, the attempt can be made to achieve comparability by applying a <conversion function>.


-8007 COLUMN MUST BE KEY COLUMN

Explanation:

The specification of a non-key column is not allowed here.

User Action:

Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the columns which belong to the table key. Only these columns can be specified at this position within the SQL statement.


-8009 DEFAULT VALUE MUST BE IN CONSTRAINT SPECIFICATION

Explanation:

The specified DEFAULT value would violate the <constraint definition>.

User Action:

1.	The definition of the corresponding <constraint definition> must be reconsidered and modified, if necessary.

2.	Use another DEFAULT value, or do not specify a default value at all.


-8010 TABLE NAME MUST BE IN FROM LIST

Explanation:

A table name which was not listed in the <from clause> was specified in a <select column> or <search condition> or <order clause>.

User Action:

1.	If a reference name was specified for a table name, use this reference name in the SQL statement.

2.	If the <from clause> contains the specification of a table which does not belong to the current user, to this user's user class or DBA, and which is not a system table, the <owner> must be specified for the table throughout the SQL statement.


-8013 ORDER COLUMN MUST BE OUTPUT COLUMN

Explanation:

1.	Only column names which are also specified as <select column> can be specified in the <order clause> of a <query statement> with DISTINCT specification.

2.	If column numbers are specified, it must be ensured that this number is not greater than the number of specified output columns.

3.	The number of output columns may have decreased in case of a SELECT * as a result of an <alter table statement> with <drop definition>.

User Action:

1.	Do not use the DISTINCT specification or specify the column of the <order clause> in a <select column>.

2.	Correct the number in the <order clause> accordingly.


-8014 RESULT TABLE MUST BE FOR REUSE

Explanation:

A named result table which was not created with FOR REUSE was used in the <from clause> of a <query statement>.

User Action:

Create the named result table with FOR REUSE and reissue the SQL statement.


-8015 TABLE MUST BE A BASE TABLE

Explanation:

The specification of a base table is expected. This specification is missing or the specified table is not a base table.

User Action:

Use a <query statement> issued on the system table DOMAIN.TABLES to find out whether the specified table is a view table or result table. In case of a view table, use a <query statement> issued on the system table DOMAIN.VIEWDEFS  to find out the pertinent base table. The desired SQL statement can then be issued for the base table, if you have the corresponding privileges.


-8016 TABLE MUST BE A VIEW TABLE

Explanation:

In a <rename view statement> or <drop view statement>, a table was specified which is not a view table.

User Action:

Specify a view table in the SQL statement or replace the SQL statement with a <rename table statement> or <drop table statement>.


-8017 COLUMN MUST BE GROUP COLUMN

Explanation:

A column which is not a group column, i.e., which is not contained in the <group clause> was specified in a <select column> or in the <having clause>. Columns which are not group columns may only occur in arguments of the functions COUNT, SUM, AVG, MAX, MIN, STDDEV, and VARIANCE.

User Action:

Insert the specified column into the <group clause> as further group column or remove it from the <select column> or <having clause>.


-8018 INDEX NAME MUST BE UNIQUE

Explanation:

1.	This error message can occur, when a <drop index statement> is executed. Indexes with identical names were created for separate tables. Therefore the name of the index to be dropped is not unique.

2.	There is only a named single-column index for this column. The attempt was made to drop the index for this column without specifying its name.

User Action:

1.	Specify the name of the table to which the index to be dropped refers in the <drop index statement>.

2.	Drop the index with the name specification.


-8021 COLUMN MUST HAVE DEFAULT SPECIFICATION

Explanation:

The attempt was made to specify the <action> SET DEFAULT as <delete rule> in a <referential constraint>, although there was no DEFAULT value defined for at least one column of the <referencing column>.

User Action:

1.	If the error occurred during the execution of a <create table statement>, either define a DEFAULT value for the column(s) or choose another <action>.

2.	If the error occurred during the execution of an <alter table statement>, issue another <alter table statement> to assign a DEFAULT value to all columns of the <referencing column>s without a DEFAULT value and then repeat the previous <alter table statement>. Alternatively, you could choose another <action>.


-8022 USER ALREADY CONNECTED

Explanation:

A user attempts to connect to ADABAS under a user name which was defined with EXCLUSIVE in a <create user statement>, <create usergroup statement>, <alter user statement>, or <alter usergroup statement>. Another user has connected to ADABAS using this name.

User Action:

The user must wait until the other user has disconnected from ADABAS using a <release statement>.

To enable a user to have various simultaneous connects, the owner of the user or usergroup must specify NOT EXCLUSIVE for this user using the <alter user statement> or <alter usergroup statement>.


-8023 COSTLIMIT MUST BE GREATER THAN COSTWARNING

Explanation:

A COSTLIMIT value was specified which was less than or equal to the specified COSTWARNING value. The COSTLIMIT value, however, must be greater than the COSTWARNING value.

User Action:

Use a <query statement> issued on the system table DOMAIN.USERS to find out the COSTWARNING value for existing users.


-8025 TABLE MUST BE TEMP TABLE

Explanation:

In a <create table statement>, the option IGNORE ROLLBACK was specified for a permanent table. This is not allowed.

User Action:

The SQL statement can be repeated, if the IGNORE ROLLBACK option is not specified or if a temporary table is created by specifying TEMP as <owner> of the table to be generated.


-8026 FUNCTION PRESENTLY NOT EXECUTABLE

Explanation:

Some of the menu functions provided in the ADABAS component CONTROL can only be executed when the current menu function or another menu function of this group is not executed simultaneously. The attempt was made to execute two of these menu functions simultaneously.

User Action:

After a certain waiting time, another attempt should be made to execute the desired menu function.


-8028 UNION COLUMNS MUST BE COMPATIBLE

Explanation:

In a <query expression> with at least a UNION, INTERSECT or EXCEPT specification, all sequences of <select column>s must designate the same number of columns. The data types of the corresponding columns must thereby comply with the conditions valid for comparability.

Each data type can be compared to itself. Columns of data type CHAR with the different code attributes ASCII and EBCDIC can be compared to each other; they are implicitly adapted. Columns with the code attribute ASCII and EBCDIC can be compared to date, time, and timestamp specifications.

All numbers can be compared to each other.

In SQLMODE ANSI, it is not sufficient that the data types and lengths of the specified columns are compatible; they must be equal. Moreover, only <column spec>s or '*' may be specified in the <select column>s of the <query spec>s connected by UNION. The specification of <literal>s is not allowed.

User Action:

Use a <query statement> issued on the system table DOMAIN.COLUMNS to find out the definition of the columns concerned. If need be, the attempt can be made to achieve comparability by applying a <conversion function>.

This request cannot be made in SQLMODE ANSI.


-8029 NO SERVERS INSTALLED

Explanation:

It is not possible to operate this SERVERDB as part of a distributed database. There are two possible causes.

1.	The installation parameter MAXSERVERDB was specified 1.

2.	The installation parameter MAXSERVERTASKS was specified 0.

User Action:

Correct the values of MAXSERVERDB and MAXSERVERTASKS.


-8030 COLUMN MUST BE INDEXED

Explanation:

1.	No index was created on the specified column.

2.	In a <referential constraint definition>, the <column list> of the <referenced table> must either designate the key of the table or columns which form an index defined with UNIQUE.

User Action:

Use a <query statement> issued on the system table DOMAIN.IND_USES_COL to find out the existing indexes. Create the desired index, or do without the index.


-8031 OWNER MUST BE SPECIFIED

Explanation:

In a DB procedure, the <owner> must be specified for each <table name>.

User Action:

Correct the DB procedure accordingly.


-8032 TABLE MUST BE A SNAPSHOT TABLE

Explanation:

A <drop snapshot statement> or <refresh statement> was specified. The specified name does not denote a snapshot table.

User Action:

Use a <query statement> issued on the system table DOMAIN.TABLES to find out the existing snapshot tables.


-8033 INCOMPLETE LOG SEGMENT

Explanation:

The attempt was made to save a log segment using the Backup / Save / Log Segment menu function in the ADABAS component CONTROL. The log segment is not yet filled sufficiently.

User Action:

It is not yet necessary to save more log segments, because all log segments completely filled have already been saved.


-8034 ORDER COLUMN MUST BE NUMBER

Explanation:

In a <query statement> which contains at least a UNION, INTERSECT, or EXCEPT specification in its outermost <query expression>, the <order clause> must not contain any <column spec>s.

User Action:

Replace the <column spec>s with the corresponding numbers of the output columns.


-8035 FOREIGN KEY MUST EXIST

Explanation:

An <update statement> was performed for an updatable join view table. This <update statement> leads to an internal insert into one of the underlying base tables. The specifications made in the <update statement> are not sufficient to form all mandatory columns which are needed for the implicit <insert statement>.

User Action:

Issue an <insert statement> on the underlying base table. This can prevent the necessity of inserting when performing the <update statement> on the join view table.


-8037 DB PROCEDURE MUST BE RECOMPILED

Explanation:

SQL statements for data definition were performed which concern tables used in the DB procedure. Check by compilation whether the DB procedure is still executable.

User Action:

This check can only be made by the owner of the DB procedure by restoring the DB procedure.


-8038 SERVERDB MUST BE AUTHORIZED

Explanation:

An error occurred during installation of a SERVERDB that is to become part of a distributed database. Consequently, the (distributed) database existing so far does not know the name of the local SERVERDB the installation of which cannot be terminated.

User Action:

Check the protocol to find out which previous error caused the current error. After removing the error cause, e.g. power failure, you can try again to install the SERVERDB.


-8039 SNAPSHOT LOG DOES NOT EXIST

Explanation:

The attempt was made to delete the snapshot log for the specified table. The specified table has no shapshot log.

User Action:

The SQL statement is not needed because there is already the desired result.


-8040 KEY DOES NOT EXIST

Explanation:

The attempt was made to delete the key for the specified table. The specified table has no user-defined key. The key implicitly generated with the column 'SYSKEY' cannot be deleted.

User Action:

The SQL statement is not needed because there is already the desired table definition.


-8041 START OF ADABAS REQUIRED

Explanation:

In a few cases of incorrect execution of menu functions in the ADABAS component CONTROL, it is necessary to shut down the database server using the Operating / Exit menu function and to begin with the Operating / Restart / Cold menu function.

User Action:

Stop the database server using the Operating / Exit menu function and restart it using the Operating / Restart / Cold menu function.


-8042 ACKNOWLEDGEMENT NECESSARY

Explanation:

The start of a restore operation requires a confirmation.

User Action:

The restore operation must be confirmed to be started, or it can be easily cancelled at this point in time.


-8043 SOME SERVERDBS NOT ACCESSIBLE

Explanation:

The specified table could not be found. The connection is down to at least one SERVERDB that could keep the meta data of the specified table. It is therefore not possible to tell whether the table does not exist, or whether it is only not visible because the communication to another SERVERDB is missing.

User Action:

1.	It can be sufficient to place <owner> in front of the table name.

2.	The attempt should be made to reestablish the communication between the SERVERDBs within the network.

3.	The attempt can be made to open a session with the SERVERDB at which the meta data and the data of the specified table are kept.


-8888 SERVERDB NOT ACCESSIBLE

Explanation:

The attempt was made to start a session using an ADABAS component. This is not possible, because

1.	the SERVERDB name was incorrectly specified or

2.	the database server was not started.

User Action:

1.	Check the specified SERVERDB name.

2.	Start the database server.


-9000 SYSTEM ERROR: NOT YET IMPLEMENTED

Explanation:

This SQL statement is not yet implemented. It will be available in future releases.

User Action:

The attempt can be made to achieve the desired effect by one or more other SQL statements.


-9001 to -9799 SYSTEM ERROR:

Explanation:

These error messages should not occur during normal operation on a consistent database.

With some errors, an implicit SHUTDOWN is issued.

User Action:

As a rule, the database should be shut down and the ADABAS Support be informed. It is possible to create a trace of the last database activities. Write this trace to magnetic tape and send it to the ADABAS Support for error tracing and correction.


-9801 INVALID COMMAND STATE

Explanation:

The command state is invalid.

This is a runtime error of the precompiler.

User Action:

Please inform the ADABAS specialist in the corresponding branch office.


-9803 UNKNOWN DATA TYPE

Explanation:

The data type is not known in the database.

User Action:

Please inform the ADABAS specialist in the corresponding branch office.


-9804 ROLLBACK ERROR

Explanation:

When the option CHECK is specified, every ADABAS statement completely executed is rolled back at the end of a precompiler run. An error occurred in such a case.

User Action:

For error analysis and correction, pay attention to the ADABAS error messages output during the precompiler run. Look up the corresponding number in this online help and follow the instructions given there.


-9805 OPTION CHECK   USAGE ON OR OFF ERROR

Explanation:

When the option CHECK is specified, the SYSUSAGE entries are maintained at the end of a precompiler run. An error occurred in such a case.

User Action:

For error analysis and correction, pay attention to the ADABAS error messages output during the precompiler run. Look up the corresponding number in this online help and follow the instructions given there.


-9806 INVALID OUTPUT VALUE

Explanation:

The define byte in the command buffer is set to an invalid value.

User Action:

Check whether the kernel and the precompiler used for translating the application have the same version number. If the versions are the same, inform your database administrator and the supplier.

If the error occurs during the execution of a SELECT DIRECT statement, it might be remedied by setting the runtime option NO SELECT DIRECT FAST. If the error occurs inspite of this option, inform your database administrator and the supplier.


-9807 TOO MANY USERS

Explanation:

All sessions of the ADABAS database are occupied.

User Action:

Wait until a session is released. If this problem arises frequently, the configuration of the ADABAS database must be checked and modified by the DBA.


-9808 SET FORMAT ERROR

Explanation:

An implicit SET FORMAT is issued to the database after every CONNECT. SET FORMAT indicates which date/time format is used by the current user. If an error occurs hereby, the ADABAS format is taken as default.

User Action:

Restart the program and intercept the error. Should the error occur repeatedly, inform the database administrator and the supplier.


-9809 OPTION CHECK   USAGE ADD  ERROR

Explanation:

When the option CHECK is specified, the SYSUSAGE entries for SQL-PL, FORM, REPORT, PROC, QUERY, COMMAND, and PREPARE are maintained at the end of a precompiler run. An error occurred in such a case.

User Action:

For error analysis and correction, pay attention to the ADABAS error messages output during the precompiler run. Look up the corresponding number in this online help and follow the instructions given there.


-12002 Database is not accessible

Explanation:

Communication between user process and database is interrupted and cannot be resumed regularly. The reasons for it can be that the database does no longer work or that, after a timeout, no free user process is available.

User Action:

Every keystroke has the same effect as the EXIT command. The contents of the current edit form may be found in the LOAD prot file. You may inform yourself about the database state and recall LOAD, if necessary.


-12101 Duplicate file name, file already open

Explanation:

After INFILE or OUTFILE, the name of a file was specified that is already open either as LOAD prot file or as command file. This error is also returned when DATAEXTRACT is to generate two output files and the same name has been specified for them.

User Action:

Specify another filename.


-12102 Error opening file: <operating system message>

Explanation:

A text depending on the operating system is inserted for <operating system message>, indicating the error occurred. Reasons for the error may be that there is no file of this name, or that the specified disk is write-protected, etc.

User Action:

Specify another filename or correct the error (branching to the operating system).


-12103 Error closing file: <operating system message>

Explanation:

A text depending on the operating system is inserted for <operating system message>, indicating the error occurred.

User Action:

A user action is not required.


-12104 Error reading file: <operating system message>

Explanation:

A text depending on the operating system is inserted for <operating system message>, indicating the error occurred.

User Action:

A user action is not required.


-12105 Error writing file: <operating system message>

Explanation:

A text depending on the operating system is inserted for <operating system message>, indicating the error occurred.

User Action:

A user action is not required.


-12106 Error erasing file: <operating system message>

Explanation:

A text depending on the operating system is inserted for <operating system message>, indicating the error occurred.

User Action:

A user action is not required.


-12107 Record length <number> too large

Explanation:

The attempt was made to open the file with the record length indicated in the message, but this is not possible.

User Action:

If a DATAEXTRACT output file is concerned, you can shorten the output lines by decreasing the number of selected columns or by changing the line positions. The possible line length depends, among other factors, upon the kind of data and cannot be greater than 4096.


-12108 Input file contains no data

Explanation:

The external file is empty, or the statement specifies INFILE * and the separated input data has already been read from the command file.

User Action:

The easiest you can do in case of INFILE * is to recall the command file with PROMPT option, to scroll to the desired statement, to correct it, if necessary, and then to start it.


-12109 No command file accessed

Explanation:

The NEXT command was issued, but no open command file is available.

User Action:

A user action is not required.


-12110 End of command file

Explanation:

This message occurs when a command file was called with the option NOPROMPT and the last statement of this file was executed without any errors to be returned.

User Action:

A user action is not required.


-12111 Printer not accessible

Explanation:

The name of a non-accessible printer was used as filename of the LOAD prot file or of an OUTFILE.

User Action:

Specify another name.


-12112 It is not possible to open another INCLUDE file

Explanation:

A command file contains an INCLUDE statement that exceeds the valid nesting level. Execution of the command file is continued with the next following statement.

User Action:

It is possible to prevent the command file from being executed further by checking $RC after the INCLUDE statement and performing RETURN, if necessary.


-12113 ORACLE file specifies invalid number of columns

Explanation:

LOAD expects an ORACLE export file. The current input file has not the required format.

User Action:

Use the file option INTEGER LOHI to ensure a correct interpretation of the binary numbers stored in the file.


-12201 INTEGER field : 1, 2 or 4 bytes long, (double if HEX)

Explanation:

An explicit column description contains a file field of type INTEGER, the length of which does not correspond to the length mentioned here.

User Action:

Correct the position specification.


-12202 REAL field : 4 or 8 bytes long (double if HEX)

Explanation:

An explicit column description contains a file field of type REAL, the length of which does not correspond to the length mentioned here.

User Action:

Correct the position specification.


-12203 DECIMAL field : 10 bytes, ZONED field : 20 bytes maximum (double if HEX)

Explanation:

An explicit column description contains a file field of type DECIMAL or ZONED, the length of which does not correspond to the length mentioned here.

User Action:

Correct the position specification.


-12204 Incorrect field length, necessary length : <number>

Explanation:

An explicit column description of a DATAEXTRACT statement contains a file field, the length of which is less than the minimum length mentioned here. The minimum output length of database values of type CHAR is their definition length, the length of numeric database values is determined by their definition and the chosen number representation. In DATALOAD statements, the definition length of CHAR columns is the maximum input length allowed.

User Action:

Correct the position specification.


-12205 Fractional part too small, minimum length : <number>

Explanation:

The number of fractional digits that can optionally be specified after DECIMAL or ZONED must not be less than the number of fractional digits of the database column.

User Action:

Correct the position specification.


-12206 Derived length of output line is too large

Explanation:

Usually, the valid maximum record length is 4096, but for binary files of variable record length, it is only 4086. Files are assumed to be binary when they contain BYTE-column values or when one of the data types INTEGER, REAL, etc. was explicitly chosen. LONG files are binary as well.

User Action:

If this message occurs during a EXTRACT LONG run, the column contents are not in order. Otherwise, reduce the length of the output row. Sometimes, it is sufficient to change the separator from STANDARD (three characters) to a shorter string. If not, you can modify the SELECT statement that underlies the DATAEXTRACT statement or specify the positions of all columns explicitly.


-12207 Position exceeds permitted row length

Explanation:

An explicit column description contains a position specification that is larger than 4096 in case of being output to a file and larger than the screen width in case of being output to the screen (OUTFILE *).

User Action:

Correct the position specification.


-12208 SQL statement is too long

Explanation:

The SQL statement is so long that it does not fit into the buffer used for communication between LOAD and database kernel.

User Action:

Remove the leading blanks from every row and, if this is not sufficient, delete those blanks from the actual text which are not required syntactically.


-12209 File name is too long

Explanation:

The maximum length of a filename is 64 characters.

User Action:

Change the directory to be able to use a shorter path name, or rename the file.


-12210 String is too long

Explanation:

Reason 1: a mask for a file option is longer than permitted.

Reason 2: a character string of the input file is too long for the target column (can only occur with COMPRESS).

User Action:

If the error is returned during the syntax check (file options), you can specify a correct mask. The second case only occurs at runtime; the corresponding row will not be loaded. Characters may be deleted from the rejected rows. These can then be loaded.


-12211 A constant input value must not be empty

Explanation:

The cursor designates the error position.

User Action:

At least one (blank) character must be specified between the single quotes.


-12212 Comparison value in condition has invalid length

Explanation:

If a condition compares two character strings, these must be exactly of the same length; i.e., the position specification must indicate as many characters as are specified between the single quotes.

User Action:

Modify the position specification or the character string within the condition.


-12213 At most 254 columns can be specified for one table

Explanation:

This restriction corresponds to the current ADABAS restriction.

User Action:

Correct the statement.


-12214 At most 20 tables can be loaded simultaneously

Explanation:

To our opinion, 20 tables per DATALOAD statement are sufficient.

User Action:

Correct the statement. If this number of tables should not suffice, contact the ADABAS support.


-12215 No further conditions allowed

Explanation:

There is a pool of conditions which can be defined as table or column conditions, as you like. The maximum number is already reached.

User Action:

If the statement consists of several DATALOAD parts for one input file and if the error does not occur in the first part, every DATALOAD part can be transformed into a statement. Otherwise, it might be possible to manage with a part of these conditions for each run, specifying ranges of rows after RUN.


-12216 Declare USAGE between 50% and 100%

Explanation:

none

User Action:

Specify a number between 50 and 100 before the percent sign.


-12217 Statement cannot be displayed completely

Explanation:

The edit form is not large enough to accomodate all rows that are contained in the command file up to the next separator line. Mostly the separator line between a DATALOAD statement and the pertinent data was forgotten or the data was fetched to the edit form using the NEXT command.

User Action:

Start the command file again (after inserting a separator line, if necessary). Then go to the DATALOAD statement which had not been performed and continue execution there. The data is read directly from the command file.


-12218 Memory space for LONG columns exhausted

Explanation:

The main memory limitations do not allow for simultaneous loading or unloading all LONG columns defined in the table.

User Action:

Use a combination of DATALOAD and DATAUPDATE to load all LONG columns. Formulate an extensive select list for the DATAEXTRACT statement and extract the LONG columns in two runs.


-12301 Invalid input for date or time column

Explanation:

The attempt was made to convert a character string into a date or time format accepted by the database, according to the set mask; but no characters could be found that correspond to this mask.

User Action:

Specify a matching mask (file options DATE and TIME) or check it, and correct the position specification.


-12302 This value is not a valid number

Explanation:

The attempt was made to convert a character string into a numeric format accepted by the database, according to the set mask; but no characters could be found that correspond to this mask. This error is also returned if the number is not within the range of values valid for the column.

User Action:

Specify a matching mask (file option DEC) or check it, and correct the position specification.


-12303 Invalid position specification

Explanation:

Position specifications must comply with the following conditions: if the initial and end positions are specified, they must be joined by a hyphen, and the end position must not be less than the initial position. For hexadecimal values, the position distance must be even-numbered. Numeric strings can only have a length of up to 28 characters.

User Action:

Correct the statement.


-12304 Invalid FRACTION specification

Explanation:

A number (enclosed in parentheses, if necessary) was expected after ROUND, TRUNC, or in connection with DECIMAL or ZONED.

User Action:

Check and correct the statement.


-12305 Invalid SCALE specification

Explanation:

A SCALE number may have a sign and be enclosed in parentheses; more syntax elements are not allowed. The value of a SCALE number must be between -63 and +63.

User Action:

Correct the statement.


-12306 Incorrect format, valid are all patterns accepted in the SET menu

Explanation:

Masks must be specified for the file options DATE, TIME, DEC, etc. The valid layout of these masks must correspond to that actually accepted in the SET menu.

User Action:

The valid formats may be looked up in the syntax description of the LOAD manual. Correct the statement accordingly.


-12307 Incorrect comparison operator in condition

Explanation:

Comparison operators are < (less), <= (less-equal), > (greater), >= (greater-equal), <> (not equal), and = (equal).

User Action:

Correct the statement.


-12308 File content does not match table definition, reason code <consecutive number>

Explanation:

The following reasons can lead to an abortion of a TABLELOAD run:

 1.	The header block expected in a TABLELOAD file (byte 6 = 0) is not available.

 2.	The integer swap form (1 for normal, 2 for full swapping, 3 for partial swapping) in byte 8 of the header block was not found.

 3.	The description of the table stored in the file has an invalid length (e.g., too many rows with byte 6 = 1).

 4.	The description of the table stored in the file is not complete.

 5.	The file does not contain all constraint rows belonging to the table.

 6.	The file does not contain all default rows belonging to the table.

 7.	There are no data records for the table stored in the file.

 8.	The columns of the source table and of the target table differ in their definitions to such an extent that the file cannot be used for the loading of the target table.

 9.	The source table and the target table have different numbers of columns.

User Action:

Check whether the specified file was actually intended for the loading of this table and had been regularly generated with TABLEEXTRACT.


-12309 Input value does not match key order or range specification

Explanation:

For FASTLOAD loading, the stream of input data must be arranged  in ascending order according to the table key. This is also valid with regard to the table rows already available.

User Action:

The rejected rows can be loaded later with a normal DATALOAD statement.


-12310 This value is not a valid HEX constant

Explanation:

If HEX is specified for input fields, these must only consist of the characters '0' to '9' and 'A' to 'F' (or 'a' to 'f').

User Action:

Check the input values and the position specification.


-12311 Invalid input for DBYTE column

Explanation:

Double-byte values must have an even-numbered length and be enclosed by certain shift characters.

User Action:

Check the input values and the position specification.


-12312 CONSTRAINT condition violated

Explanation:

While loading with FASTLOAD, there were rows which did not comply with all CONSTRAINT conditions.

User Action:

Check the input values.


-12313 This specification is not allowed together with COMPRESS

Explanation:

Only plaintext data can be loaded with COMPRESS. Column conditions are not allowed. The position specification indicates the consecutive number of the value to be loaded into this column. The column description does not comply with these conventions.

User Action:

Omit the data type specification and HEX. Specify only a number as position specification and delete the NULL-IF-POS condition.


-12314 Please specify the columns in left-to-right order  (positions ascending)

Explanation:

With COMPRESS, the fields are written to the output line in the order in which the columns are specified in the DATAEXTRACT statement.

User Action:

Specify the columns in the desired order.


-12315 This specification is not allowed for ORACLE data

Explanation:

ORACLE export files contain data in a fixed format known to LOAD. The specification of an external data type and a fixed position, HEX and other conversion specifications are not correct and are rejected. NULL conditions cannot be evaluated either.

User Action:

Omit the data type specification and HEX. Specify only a number as position specification and delete the NULL-IF-POS condition.


-12316 Invalid input for BOOLEAN column

Explanation:

A value to be inserted into a BOOLEAN-type column does not comply with the representation defined for TRUE or FALSE.

User Action:

Use the file option BOOLEAN to specify the representation used in the data or change the corresponding SET parameter.


-12401 End of selection criterion not recognized, semi-colon  missing

Explanation:

Variable parts of a statement which are not interpreted by LOAD, but by the database kernel, must be concluded with a semicolon. An example is the DATAEXTRACT statement. Its first part is sent as SELECT statement to the database. Its second part contains the column descriptions of the output file which were analyzed by LOAD.

User Action:

The position where the semicolon is missing may be looked up in the syntax description of the LOAD manual. Correct the statement accordingly.


-12402 Delimiter missing

Explanation:

This message is output during the syntax check, when the end of a character string enclosed in single quotes was not found in the same line.

User Action:

Correct the statement by writing the character string in one line.


-12403 No opening parenthesis found

Explanation:

The statement contains only a closing parenthesis.

User Action:

Correct the statement in such a way that all parentheses are paired.


-12404 No closing parenthesis found

Explanation:

The statement contains only an opening parenthesis.

User Action:

Correct the statement in such a way that all parentheses are paired.


-12405 Table name missing

Explanation:

A table name must begin with a letter. Names equal to keywords or containing special characters must be enclosed in double quotes.

User Action:

Correct the statement.


-12406 No columns specified for this table

Explanation:

A column name must begin with a letter. Names equal to keywords or containing special characters must be enclosed in double quotes.

User Action:

Correct the statement.


-12407 Columns for key (KEY) or search condition missing

Explanation:

A DATAUPDATE statement must contain at least one column description either preceded by KEY when a <keyed update> is allowed, or without a keyword when a WHERE condition of the form <column name> = <value> is to be generated.

User Action:

Specify a qualifiying column.


-12408 No (SET) columns to be changed specified

Explanation:

A DATAUPDATE statement must contain at least one column description preceded by SET. SET columns are modified by the SQL statement UPDATE.

User Action:

Specify a column to be updated.


-12409 No column with this name or number contained in result table

Explanation:

The DATAEXTRACT statement generated a result table to be output according to explicit column descriptions. The column marked by the cursor does not exist in this table.

User Action:

Check whether a position specification was mistaken for the next column identifier.


-12410 No column number found (maybe it was interpreted as ZONED/DECIMAL fraction)

Explanation:

The DATAEXTRACT statement generated a result table to be output according to explicit column descriptions. A column of this table has the external format DECIMAL or ZONED in case of which the specification of the number of assumed fractional digits is optional. This specification cannot be distiguished from a number indicated as identifier of the next column.

User Action:

At least those columns following a DECIMAL- or ZONED-type column must be identified by their names instead of their consecutive numbers.


-12411 File specification missing or incorrect

Explanation:

Either the syntactical element INFILE, OUTFILE, or the like was not found, or the filename is missing, or file options were not recognized. The cursor position allows a more detailed determination of the error.

User Action:

Correct the statement.


-12412 No comparison value specified in condition

Explanation:

A condition in a command file must specify a numeric comparison value. The return code of the last executed statement must be compared against this value.

User Action:

Also check whether the comparison operator was correctly specified.


-12501 OTHERWISE condition not allowed here

Explanation:

The OTHERWISE condition can only be used for the last table specified in a statement that consists of several DATALOAD or DATAUPDATE parts. The OTHERWISE condition excludes all the other conditions for the same table.

User Action:

Change the order of the statement parts accordingly.


-12502 This command requires a table with key columns

Explanation:

The statement DATAEXTRACT FOR DATAUPDATE is only executed, if the specified table has a user-defined row key. SHOW TABLEDEF can be used to check the availability of this key.

User Action:

Create a new table, if necessary, or perform DATAEXTRACT FOR DATALOAD instead of FOR DATAUPDATE. Make sure you own a table with this name.


-12503 Column must not contain NULL values

Explanation:

NULL-IF-POS conditions are not accepted for mandatory columns and for key columns.

User Action:

Remove the objected condition from the statement.


-12504 ROUND or TRUNC specification not allowed for this column

Explanation:

ROUND and TRUNC can only be specified for numeric columns (e.g., FIXED, FLOAT, SMALLINT, INTEGER).

User Action:

Remove the objected part of statement.


-12505 Column data type and external data type are not compatible

Explanation:

The external data types INTEGER, REAL, DECIMAL, and ZONED are only compatible with the numeric SQL data types FIXED, FLOAT, etc. In addition, INTEGER values cannot be generated from FLOAT columns. CHAR input and output is possible for every SQL data type.

User Action:

Choose another data type for output. Check the assignment of file position to table column for input.


-12506 Table contains column with unknown data type

Explanation:

The database kernel allows data type definitions which in the current LOAD version are not yet or no longer permitted.

User Action:

Ensure that the software versions match.


-12507 Name denotes no TABLE, VIEW and UNLOADED are not allowed

Explanation:

In TABLELOAD and related statements, the table name must denote a base table belonging to the current user. A table of the specified name and the attribute TABLE was not contained in the SHOW TABLE result.

User Action:

Specify the name of a base table of your own.


-12508 This is a restricted statement, user must be SYSDBA

Explanation:

CATALOGEXTRACT ALL and CATALOGLOAD ALL are statements which concern the complete database catalog and can therefore only be executed by a system administrator.

User Action:

Call LOAD with the corresponding user identification.


-12509 This statement can only be executed by the local SYSDBA

Explanation:

TABLEEXTRACT ALL and TABLELOAD ALL are statements which concern the complete local data set and can therefore only be executed by the system administrator. REMOTE execution is not allowed, because much data is to be transported.

User Action:

Call LOAD with the corresponding user identification.


-12510 ORACLE column &1 has an incompatible datatype

Explanation:

In a DATALOAD statement for a single ORACLE table, a column of the target table was combined with a column of the ORACLE export file which cannot be converted into the required data type. It may also be that the data type is unknown to LOAD.

User Action:

Ensure that the ORACLE version used for generating the export file can be operated with the current LOAD version. Numeric data types are compatible with each other, CHAR data types are compatible with each other, ORACLE DATE columns can be used to load ADABAS DATE, TIME, or TIMESTAMP columns. LONG columns are only compatible with ADABAS LONGs.


-12511 The only way to load LONG columns is a one-table DATALOAD  statement

Explanation:

If a table contains LONG columns, other tables cannot be loaded simultaneously from the same input file. In this case, it is not possible to use FASTLOAD.

User Action:

Specify only one DATALOAD statement per input file.


-12601 Unknown batch command

Explanation:

LOAD cannot address the screen. Only command files can be executed in this mode.

User Action:

Call LOAD with a correct BATCH or RUN command.


-12602 Unknown command

Explanation:

The character string was not identified as a LOAD command.

User Action:

Correct the command.


-12603 Input area contains no statement

Explanation:

The RUN command was executed (by keystroke), but the edit form is empty.

User Action:

Fetch the next statement, if any, with NEXT.


-12604 Incomplete statement

Explanation:

The edit form contains no data any more, but syntactical elements are still expected for the statement being analyzed.

User Action:

Correct the statement.


-12605 Wrong keyword

Explanation:

During the syntax check, a keyword was found that is not allowed at this position.

User Action:

Correct the statement.


-12606 Re-connected after timeout, statement must be started again

Explanation:

No statement was executed for a long while. Therefor, the database timeout process interrupted the connection. LOAD reestablished this connection instead of executing the statement.

User Action:

Repeat the RUN command.


-12607 Execution rejected

Explanation:

There are some database commands, such as CONNECT, which are intercepted by the tool components.

User Action:

Do without the execution of this command.


-12608 Catalog lock request rejected, other users active

Explanation:

The database catalog should be locked for the execution of CATALOGEXTRACT ALL in order that the created file reflects a consistent state.

User Action:

Ensure that only the SYSDBA is connected to the database.


-12609 No rejected rows logged

Explanation:

The PROT command was executed, but the online PROT is empty.

User Action:

The result of previous load runs can only be looked up in the PROT file.


-12610 Too many DEFAULT definitions for FASTLOAD loading

Explanation:

While loading with FASTLOAD, LOAD generates the definite data records. If a NULL condition is met and a default is defined for the column, LOAD inserts this value as input value. The default values of all columns are therefore kept in a buffer the length of which is not sufficient in the present case.

User Action:

Use a normal DATALOAD statement to load the data.


-12612 Not implemented

Explanation:

A key was pressed that should be bound to an editor function.

User Action:

This should never be the case. Please inform the ADABAS support.


-12613 Parameter cannot be replaced, no actual argument passed

Explanation:

A statement of the command file just executed contains one of the character strings &1 to &9. Formal parameters to be replaced with current parameters are noted in this way. If no current parameters are specified, LOAD assumes that a correct execution of the command file is not possible and therefore aborts its execution.

User Action:

Specify the required number of parameters with the RUN command.


-12614 USER/USE connect with new username failed

Explanation:

The exact error cause is specified in the PROT file.

User Action:

You can decide now whether to continue with the execution of the command file or to leave it. Typing errors in username/password can be corrected interactively.


-12615 Table has so many constraints that TABLELOAD would be impossible

Explanation:

A table must be extracted with TABLEEXTRACT or TABLEUNLOAD. This table, however, contains so many constraints that their internal representation exceeds the storage capacity of LOAD.

User Action:

Remove some of the constraint definitions or extract the table using DATAEXTRACT FOR DATALOAD.


-13501 Unknown QUERY command

Explanation:

QUERY does not know a command with this name.

User Action:

Consult the manual or HELP function of QUERY.


-13502 Database command not allowed in QUERY

Explanation:

Some SQL statements are intercepted by QUERY, because their execution is not permitted.

User Action:

A user action is not required.


-13503 Name of stored command missing

Explanation:

The name of a stored QUERY command was not specified, e.g., for STORE.

User Action:

Consult the manual or HELP function of QUERY.


-13504 Correct format : AUTOCOMMIT ON/OFF

Explanation:

none

User Action:

Enter AUTOCOMMIT ON or AUTOCOMMIT OFF.


-13505 Duplicate stored command name

Explanation:

none

User Action:

Use the option REPLACE, if necessary.


-13506 Stored command not found

Explanation:

none

User Action:

Use the LIST menu to find out the names of the stored QUERY commands.


-13507 No further command found

Explanation:

The TUTOR function provides no more examples.

User Action:

A user action is not required.


-13508 Parameter list too short or missing

Explanation:

A stored QUERY command contains more position indicators than current parameters have been specified.

User Action:

Edit the command to find out the missing parameters.


-13509 Enter new command name

Explanation:

COPY needs two names of stored QUERY commands. The first name designates the existing command, the second name the copy to be generated.

User Action:

Consult the manual or HELP function of QUERY.


-13510 First character of command name must be a letter

Explanation:

none

User Action:

Consult the manual or HELP function of QUERY.


-13511 ENDLAYOUT missing

Explanation:

none

User Action:

Consult the manual or HELP function of QUERY.


-13512 GRANT and REVOKE are not allowed for other users' commands

Explanation:

You are not allowed to grant privileges for stored QUERY commands to other users.

User Action:

A user action is not required.


-13513 Command not executed

Explanation:

The QUERY command was not executed.

User Action:

Restart the command, if necessary.


-13514 Wrong GO table definition

Explanation:

The table addressed by the command GO <table> must belong to the SYSDBA and consist of the columns

          NO1 FIXED (4) KEY,

          NO2 FIXED (4) KEY,

          ROW CHAR (132))

User Action:

Contact your administrator.


-13515 Table does not exist

Explanation:

The addressed GO table does not exist.

User Action:

Specify the name of an existing table.


-13516 Row not found

Explanation:

A report should be displayed, but the SELECT statement produced the return code 100.

User Action:

A user action is not required.


-13517 Invalid character in command name

Explanation:

The special characters point, asterisk, interrogation mark, underscore, and percent sign are not allowed in names of stored QUERY commands. A point separates the owner name from the command name and the other special characters are used as WILDCARD arguments for SQL statements.

User Action:

Specify a command name without any of these characters.


-13518 No information available

Explanation:

The desired HELP information is not loaded.

User Action:

A user action is not required.


-13519 Enter filename

Explanation:

The commands EXPORT and IMPORT need a file.

User Action:

Consult the manual or HELP function of QUERY to find out the correct syntax.


-13520 Invalid command name

Explanation:

An IMPORT file must contain a line before each new QUERY command, specifying the name under which the command is to be stored.

User Action:

Consult the QUERY manual or generate a small example file using EXPORT to find out the correct syntax.


-13521 IMPORT command aborted

Explanation:

The tables required for the storage of QUERY commands are not correctly installed.

User Action:

Contact your system administrator.


-13522 EXPORT command aborted

Explanation:

The tables used for the storage of QUERY commands are incorrect or do not match the current QUERY version.

User Action:

Contact your system administrator.


-13523 Invalid REPORT command

Explanation:

A stored QUERY command executed in batch mode contains an incorrect REPORT command. Execution was interrupted at this position.

User Action:

Execute the command interactively to find out the incorrect statement, then correct it and save it (e.g., using STORE =).


-13524 Enter new database name

Explanation:

The USE command requires the specification of the database with which you want to work from now on.

User Action:

Complete the command.


-13525 Connection failed

Explanation:

It is not possible to establish a connection between user process and database because of the specified combination of connect parameters.

User Action:

Specify other parameters or continue working with the existing connection.


-13526 Syntax: GO <table> or GO '<file>' or GO OFF

Explanation:

The GO command needs a table or file to read the statements from it.

User Action:

Complete the GO command.


-13527 SQLEXEC error

Explanation:

Execution of an operating system command was not successful.

User Action:

A user action is not required.


-13528 Final quote missing

Explanation:

A character string contains an odd number of single quotes.

User Action:

Correct the command.


-13529 User does not exist

Explanation:

The user addressed in a GRANT command is not known in the database.

User Action:

Correct the name.


-13530 This command is too long to be stored, please divide it into two parts

Explanation:

A stored QUERY command must not exceed 8 kilo bytes.

User Action:

Divide the command and store the parts separately.


-13531 Layout exceeds possible form size

Explanation:

A form provided for the input of parameters for stored QUERY commands may have a maximum length of 18 lines.

User Action:

Delete some lines between LAYOUT and ENDLAYOUT.


-13532 The FOREIGN KEY condition cannot be resolved

Explanation:

There is no FOREIGN KEY with this name.

User Action:

Consult the QUERY manual to find out the correct syntax.


-13533 Name of user missing

Explanation:

No user name was specified in the GRANT or REVOKE command.

User Action:

Specify a name.


-13535 Unknown call option

Explanation:

QUERY was called with an option that is not valid for QUERY (e.g., RUN <file>).

User Action:

A user action is not required.


-13536 EASY named request not found

Explanation:

It is not possible to display a menu with EASY named requests, because there is no named request that matches the search pattern.

User Action:

A user action is not required.


-13537 Error in call privileges

Explanation:

When importing commands from a file, an error occurred while granting the privileges.

User Action:

Check the GRANT command in the import file.


-13538 Invalid SQLMODE

Explanation:

An invalid SQLMODE was specified.

User Action:

Consult the QUERY manual to find out the valid SQLMODEs.


-13539 Syntax error in CROSS command

Explanation:

none

User Action:

Consult the QUERY manual to find out the correct syntax.


-13540 Create CROSS table failed

Explanation:

The result table for the CROSS command could not be created.

User Action:

Check the table name for validity.


-13541 Table does not exist

Explanation:

The starting table for the CROSS command could not be read.

User Action:

Correct the name of the starting table.


-13542 Invalid column type in CROSS command

Explanation:

none

User Action:

Consult the QUERY manual to find out the valid column types.


-13543 Row could not be inserted

Explanation:

While executing the CROSS command, a row from the starting table could not be inserted into the result table.

User Action:

Consult the QUERY manual.


-13544 Table contains no data

Explanation:

The starting table for the CROSS command contains no data rows.

User Action:

Check the starting table.


-14601 Unknown REPORT command

Explanation:

REPORT does not know a command with that name.

User Action:

Consult the QUERY manual or the REPORT HELP function.


-14602 Maximum number of columns for this command reached

Explanation:

none

User Action:

Consult the QUERY manual or the REPORT HELP function.


-14603 Enter new column name

Explanation:

The NAME command expects two column names: the name used so far and the desired new name. If the new name shall consist of blank characters, specify BLANK for it.

User Action:

Correct the command.


-14604 Command only valid for CHAR columns

Explanation:

none

User Action:

none


-14605 Unknown column identification

Explanation:

REPORT does not know a column with this number or name.

User Action:

Check whether the syntax of the specified command is correct. Use the displayed column headings to find out the correct column identification.


-14606 TAB rejected - column width less than display width

Explanation:

The TAB command can only be used for columns which exceed the display width.

User Action:

A user action is not required.


-14607 TAB rejected - column width less than value

Explanation:

The TAB value must denote a position within the long column.

User Action:

Specify a smaller number.


-14608 Command only valid for numeric columns

Explanation:

none

User Action:

none


-14609 First character of new column name must be a letter

Explanation:

none

User Action:

Correct the command.


-14610 Column width must be greater than zero

Explanation:

none

User Action:

Correct the command.


-14611 Value must be a number

Explanation:

The command syntax requires a number.

User Action:

Consult the QUERY manual or the REPORT HELP function.


-14612 Invalid column identification

Explanation:

The PSUBTOTAL command was applied to a column for which no SUBTOTAL was defined.

User Action:

Define a SUBTOTAL computation for the desired column.


-14613 Value must be ON or OFF

Explanation:

The NUMBER command has the format NUMBER ON or NUMBER OFF.

User Action:

Correct the input.


-14614 Only 8 rows for new name allowed

Explanation:

The new name of a column contains more than seven split characters.

User Action:

Correct the input.


-14615 Printer error :

Explanation:

An additional operating system message is output giving a more detailed explanation of the error.

User Action:

A user action is not required.


-14616 File error :

Explanation:

An additional operating system message is output giving a more detailed explanation of the error.

User Action:

A user action is not required.


-14617 Enclose filename in quotes

Explanation:

none

User Action:

Correct the statement.


-14618 Column width too large

Explanation:

The application of MIN and MAX in (SUB)TOTAL commands only yields correct results if the table column is not longer than 40 characters.

User Action:

Use the function SUBSTR in the SELECT statement.


-14619 Invalid LEVEL

Explanation:

A number between 1 and 16 must be specified after the keyword LEVEL.

User Action:

Correct the statement.


-14620 Result table not available after timeout

Explanation:

The SELECT or SHOW result is no longer available after a timeout.

User Action:

Execute the SQL statement again.


-14621 REPORT buffer limit exceeded

Explanation:

The command cannot be executed because there is no space any more in the corresponding REPORT buffer (e.g., for column names or for function labels).

User Action:

A user action is not required.


-14622 Maximum number of digits = 18

Explanation:

The DECIMAL command specifies so many fractional digits that a total of more than 18 digits is the result.

User Action:

Specify less digits.


-14623 Layout exceeds page width, print rejected

Explanation:

The width of a print page can be defined using SET. The current REPORT has a width larger than specified there.

User Action:

Narrow the report using WIDTH and EXCLUDE.


-14624 Label too long

Explanation:

The label of a function in a TOTAL or SUBTOTAL command is too long.

User Action:

Conclude the comment with a single quote after a maximum of 40 characters.


-14625 Column is excluded

Explanation:

A POS command is to display a column at the left side of the report, but this column is excluded.

User Action:

Use INCLUDE first to redisplay the column, then POS.


-14626 Printer not available

Explanation:

The printer is not available the name of which was either specified in the command or taken from the SET parameters.

User Action:

Specify another printer, if any.


-14627 Missing position specification

Explanation:

The WINDOW command expects a position specification in the form POS <line> <column>.

User Action:

Correct the statement.


-14628 Only conversion of byte strings possible

Explanation:

The commands ASCII, EBCDIC, and HEXADECIMAL can only be used for BYTE columns.

User Action:

A user action is not required.


-14629 Double position or size specification

Explanation:

No more parameters are allowed at this position of the WINDOW command.

User Action:

Consult the QUERY manual or the REPORT HELP function.


-14630 Invalid position or size specification

Explanation:

It is not possible to open a window at the desired position and/or of the desired size.

User Action:

Specify different numbers after POS or SIZE.


-14631 Mask missing or invalid

Explanation:

In a FORMAT mask, the characters point, comma, minus, plus, asterisk, and greater have a special function and cannot be used for building any numeric pattern (e.g., hyphen in a telephone number).

User Action:

Consult the QUERY manual or the REPORT HELP function.


-14632 Command not possible after FORMAT

Explanation:

The commands LEAD, TRAIL, PROTECT, and CRDB are only implemented for standard numeric formats. The masks generated by the specified built-in functions can also be built by a FORMAT mask extended accordingly.

User Action:

Either set FORMAT to OFF (for this column) or extend the format mask.


-14633 Application error :

Explanation:

The (PC) application called from REPORT could not be started or executed successfully.

User Action:

Check the error message to find out the reason for the unsuccessful execution.


-14634 Page length specification too small

Explanation:

The logical print page has so few lines that, after printing the top titles and column headings, no space is available for the actual data.

User Action:

Change the SET parameter 'page_length'.


-14635 Invalid arithmetic expression

Explanation:

The formula used in a (SUB)TOTAL command must be built according to the normal rules of arithmetic expressions. It can contain parentheses, signs, and the operators +, -, *, and /. Operands can be numeric constants or column names.

User Action:

Consult the QUERY manual or the Reference online help.


-14637 Error with clipboard

Explanation:

The clipboard (PC application) cannot be addressed.

User Action:

A user action is not required.


-14638 ENDDETAIL missing

Explanation:

The closing keyword is missing in the DETAIL command.

User Action:

Insert an ENDDETAIL at the end of the DETAIL command.


-14639 Command only valid for LONG columns

Explanation:

none

User Action:

none


-14640 LONG column is empty

Explanation:

It is not possible to zoom into the LONG column.

User Action:

A user action is not possible.


-14641 Error with zoom

Explanation:

It is not possible to zoom into the LONG column.

User Action:

A user action is not possible.


-14642 Command only valid for CHAR LONG columns

Explanation:

none

User Action:

none


-15000 Please enter table/view name

Explanation:

The specification of a table or view name is missing.

User Action:

Specify the name or the current number of the table/view you want to use or place the cursor on the corresponding name in the menu and then press the [image] key.


-15001 Invalid number entered

Explanation:

No or a wrong numeric value was specified in the input field.

User Action:

Replace the contents of the field with a numeric value that is valid for this field.


-15002 Output truncated

Explanation:

EASY works with internal storage areas. It stores the names and values of the table columns there. Since this storage area is limited, it may not be sufficient in case of large tables.

User Action:

Limit the result set by an appropriate request.


-15003 Key column must not be dropped

Explanation:

Key columns may only be renamed, not dropped. The user's request to remove the key column was ignored.

User Action:

A user action is not possible.


-15004 Invalid name

Explanation:

A name in EASY may contain all characters, except double quotes. The double quotes may only be placed at the beginning and end of a name. They tell EASY that the name has to be accepted in the way it was entered; i.e., lowercase characters are not converted into uppercase characters.

User Action:

Correct the name.


-15005 Example value missing

Explanation:

No example value was specified for a database column to be created. This example value determines the data type of the column and must not be omitted!

User Action:

Specify the example value in the form field provided for this purpose.


-15006 Example value is longer than specified length

Explanation:

EASY determines the data type from the example value and the length specification. The example value may be shorter but in no case longer than specified in the length field.

User Action:

Modify the length specification or adapt the example value to it.


-15007 Named request not found

Explanation:

There is no named request with the specified name for this table.

User Action:

Enter an asterik "*" into the field "Named request: ................." to obtain a list of the available requests.


-15008 Request already exists - will be overwritten by STORE

Explanation:

The attempt was made to store the current request under a name that is already used for another request.

User Action:

Specify another, unused name or press the [image] key a second time to overwrite the old request with the new one.


-15009 Undefined function

Explanation:

A function was specified which is unknown to EASY.

User Action:

In the field "Function: .........", you can only specify functions that are displayed in the function menu. Only the function EXIT is always provided in addition; it can be used to leave EASY immediately.


-15010 Function not unique

Explanation:

The name of a function was abbreviated to such an extent that it can be confused with one or more other functions.

User Action:

Specify the complete name or use an abbreviation which cannot be confounded with other functions.


-15011 Request is not for this table

Explanation:

The called request does no longer fit the table. Probably the table definition was changed in the meanwhile.

User Action:

Redefine the request.


-15012 Printer not ready

Explanation:

EASY is not able to send the print job to the printer.

User Action:

Check whether the printer is ready to receive data.


-15013 No help texts loaded

Explanation:

The help texts have not been loaded.

User Action:

Ask the database administrator to check whether the database was installed correctly.


-15014 Row already deleted

Explanation:

One of the keys [image] or [image] was pressed. But the entry was already deleted by the current or another user.

User Action:

Press the [image] key, if you want to reinsert the values which in case of an UPDATE are displayed on the screen.


-15015 <language> language not available - <language> assumed

Explanation:

No help texts are loaded in the language currently set.

User Action:

Contact the database administrator.


-15016 REPORT after DELETE/UPDATE/INSERT not allowed

Explanation:

The attempt was made to call the REPORT function, but an entry had been modified since the last RESULT. Since the REPORT function exactly displays the result of the last request, the modifications would not be taken into account. The REPORT function is therefore inhibited.

User Action:

First press [image], then call [image] again.


-15017 Duplicate key definition

Explanation:

One or more column numbers were repeated in the input fields used for the specification of the key fields.

User Action:

Remove the repeated column numbers.


-15018 Input field too long

Explanation:

An input field used for creating a request or inserting a value can have a maximum length of 255 characters. This limit should not be exceeded.

User Action:

Shorten the entry.


-15019 Form too wide

Explanation:

The attempt was made to define fields in the request form longer than the right screen margin.

User Action:

Modify the field definition.


-15020 Invalid example value

Explanation:

Possibly, one of the following mistakes was made:

-	The attempt was made to modify the number of integral digits.

-	The attempt was made to place a text longer than 40 characters before or after the example value.

-	The attempt was made to append so many fractional digits that the total number of represented digits became greater than 18.

-	Several characters were used for separating the thousands groups.

User Action:

Modify the incorrect example value.


-15021 No data field defined

Explanation:

The attempt was made to create a request form without any input field definition.

User Action:

Define at least one input field in the request form.


-15022 Too many columns for TOTAL / SUBTOTAL / labels

Explanation:

The total and subtotal function as well as text before or after the numeric output were defined for more than eight database columns.

User Action:

Reduce these specifications to eight database columns at the most.


-15023 too many REPORT commands

Explanation:

The possible maximum number of formattings was exceeded. The formattings which could not be taken into account were not transferred to the formatting form.

User Action:

Confine yourself to the most essential formattings.


-15024 SUBTOTAL not allowed

Explanation:

The SUBTOTAL function can only be called if the results of at least one database column has been grouped.

User Action:

Group at least one of the database columns and select the SUBTOTAL function again.


-15025 Empty table menu

Explanation:

The user only wanted to see a subset of the tables available to him. A pattern was specified for this purpose for which there are no matching tables.

User Action:

Specify another pattern.


-15026 Invalid length

Explanation:

The attempt was made to define a column as a character string, decimal number, or floating point number. The specified value is too large for the length or precision.

User Action:

Limit the specification to the valid maximum value.


-15027 Wrong table column for FOREIGN KEY

Explanation:

EASY could not find an input field of the named request in the request form.

The reason may be that, in the meanwhile, the pertinent database column was dropped from the table or the order of input fields was changed in the request form.

User Action:

Redefine the request.


-15028 Wrong cursor position

Explanation:

When attempting to select the total or subtotal formatting option, the cursor was placed on an incorrect row.

User Action:

Place the cursor on a row with a table column name and press the desired function key.


-15029 File open error

Explanation:

The file the name of which was specified could not be opened.

There may be different reasons for it. Perhaps the filename was not correct.

User Action:

Use another, correct filename.


-15030 DELETE/UPDATE not allowed after INSERT

Explanation:

After inserting a new value into the database, the results retrieved with the last request can no longer be updated or deleted.

User Action:

Make another request and update the respective values.


-15031 Too many base tables

Explanation:

The attempt was made to create a new view on more than two tables.

User Action:

If views are to be created on more tables, first define one view on two of the base tables, then use this new view as base of a second view etc.


-15032 Join assignment not unique

Explanation:

The attempt was made to define a new view on two tables. Thereby one column was assigned to more columns of the other table. But there may only be a 1 : 1 relation between the columns of the two tables.

User Action:

Remove the repeated column assignments.


-15033 Form field too short

Explanation:

The input fields of the request form must be large enough to accomodate the longest value of the database column.

Numeric columns must also have sufficient space for the sign, the fractional digits, and the separators of thousand groupings, if any.

User Action:

Enlarge the input field(s) adequately.


-15034 No EASY request

Explanation:

The attempt was made to process the named request. This attempt failed.

Perhaps the table had been altered in the meanwhile, or the request had been modified outside EASY.

User Action:

Define a new request, if necessary, which fits the table.


-15035 Request name missing

Explanation:

The name of the named request to be processed has been omitted.

User Action:

Enter the name or current number of the request you want to process or place the cursor on the corresponding request name in the menu.

 produces the result of the request in file card format, [image] in REPORT format. Press the [image] key or [image] to display the request which may still be changed, if necessary.


-15036 Batch processing not possible for XEASY

Explanation:

The attempt was made to work with EASY in batch mode. This is not possible for EASY.

User Action:

A user action is not possible.


-15037 Too many changes

Explanation:

EASY works with internal storage areas where it stores the modifications made in report mode. Since these storage areas are limited, they may not be sufficient for a great number of modifications.

User Action:

Make less modifications. Store these in the database with the [image] key. Then return to the report mode to make the next changes.


-15038 No named requests available

Explanation:

No named request has been created for this table.

User Action:

A user action is not required.


-15039 Wrong prefix command

Explanation:

An unknown prefix command was used in report mode. Only the commands 'C', 'D', 'R', and " or the block commands 'CC', 'DD', 'RR', and "" are valid.

User Action:

Use only one of the above-mentioned commands in the prefix area.


-15040 No valid <operating system> command

Explanation:

An unknown operating system command was specified.

User Action:

Enter a valid operating system command.


-15041 Join assignment open

Explanation:

The attempt was made to define a new view based on two tables, but the assignment was not concluded for at least one column.

User Action:

Remove the column assignments still open.


-15042 Wrong DBYTE value

Explanation:

An invalid DBYTE value was specified.

User Action:

Correct the input.


-15044 No form marked

Explanation:

The attempt was made to start the export of forms without having marked a form.

User Action:

Use the [image] key to mark the names of the forms to be exported.


-15045 No user defined forms available

Explanation:

There is no user-defined request form for the current search pattern.

User Action:

Specify another search pattern, if you did not use the default pattern '*'.


-15046 A form already exists for this table - confirm with IMPORT

Explanation:

The form to be imported already exists.

User Action:

 overwrites the old form definition. The form may be skipped by using the [image] key. (EASY then continues import with the next form.) The import run may be interrupted with [image]. You are then returned to the export/import menu.


-15047 No request marked

Explanation:

The attempt was made to start the export of requests without having marked a request.

User Action:

Use the [image] key to mark the names of the requests to be exported.


-15048 Request already exists

Explanation:

The request to be imported already exists.

User Action:

 overwrites the old request definition. The request may be skipped by using the [image] key. (EASY then continues import with the next request.) The import run may be interrupted with [image]. You are then returned to the export/import menu.


-15049 Wrong file format

Explanation:

The format of the import file does not correspond to the file format required by EASY.

User Action:

Check whether the correct filename was specified.


-15050 No column numbers defined

Explanation:

When defining the request form, the columns or input fields were not numbered. Such a numbering is needed for referring to a column by '%'.

User Action:

Modify the request form by numbering the input fields.


-15051 Wrong column specification

Explanation:

An unknown column number was specified in the named request when referring to another column by '%'.

User Action:

Modify the incorrect column number.


-15052 Form and table definition not identical

Explanation:

The table definition was changed during export and import of the form. The form therefore does no longer fit the table, e.g., because a column was dropped and enlarged.

User Action:

When such an error occurs, EASY interrupts the import run and displays the form definition. Remove the error by adapting the displayed form definition to the new table definition.


-15053 FOREIGN KEY name missing

Explanation:

The specification of a FOREIGN KEY name is missing.

User Action:

Specify the name or the current number of the FOREIGN KEY to be used or place the cursor on the corresponding name in the menu and then press the [image] key.


-15054 FOREIGN KEY not found

Explanation:

There is no FOREIGN KEY between the current and another table.

User Action:

A user action is not possible.


-15055 No detail rows found

Explanation:

There are no detail records available for a selected master record.

User Action:

A user action is not possible.


-15056 Request attribute missing

Explanation:

The specification of an attribute is missing.

User Action:

Specify a name or the sequence number of an attribute or place the cursor on the corresponding name in the menu. Then press the [image] key.


-15057 Attribute request not found

Explanation:

The name or the number of an attribute specified in the field

Attribute: ............ does not exist.

User Action:

Correct the name or the number.


-15058 Wrong cursor position

Explanation:

The attempt was made to assign an attribute to a field. But the cursor was not correctly positioned, so that EASY does not know which field is meant.

User Action:

Place the cursor on or before the corresponding field. Then repeat [image].


-15059 No user-defined request available

Explanation:

There is no user-defined request available for the current search pattern.

User Action:

Specify another search pattern, if not the default pattern '*' was used.


-15060 Restrained table menu

Explanation:

EASY was called with a limited table menu. You can therefore only work with the tables that were displayed after the start of EASY.

User Action:

If you want to reduce the table menu to a greater extent or to create a new table, the pattern or the table name must correspond to the search argument used for the call.


-15200 Warning: View becomes read only

Explanation:

The defined view does not allow you to make any update or insert operations to the data of the base tables underlying the view.

User Action:

A user action is not possible.


-15201 Warning: Table changed by other user - see HELP

Explanation:

The result to be deleted or updated was modified by another user. The new value is displayed now.

User Action:

A user action is not possible.


-15202 Warning: Database column will be dropped

Explanation:

At least one input field was removed from the form. In consequence, a column will be removed from the pertinent database table, and the data stored there will be lost.

User Action:

If this modification is desired, press [image] twice.


-15203 Warning: Too many DD rows - row number lost

Explanation:

In report mode, too many entries were marked as ready for deletion. EASY can only delete a limited number of entries with one order.

User Action:

Make less deletions. Execute them in the database using the [image] key. Then return to the report mode to make the next deletions.


-16001 <module name> not found

Explanation:

When executing a program, the specified routine or form is called in a CALL, SWITCH, or SWITCHCALL statement. This routine or form does not exist.

User Action:

Create the corresponding module or correct the typing error, if any.


-16002 Program not found

Explanation:

There is no program with the specified name for which you have access privileges.

User Action:

The workbench command 'PLIST' displays all programs. Use this command to find out the correct name.


-16003 Module not found

Explanation:

The module specified for the start of a program does not exist.

User Action:

The workbench command 'LIST' displays all existing modules. Use this command to find out the correct name.


-16020 Vector index must be between 1 and 255 (<module name>)

Explanation:

When executing the program, a vector index occurs in the routine specified in parentheses. This vector index is either undefined (NULL) or not within the specified interval.

User Action:

Find out the index variable using either test outputs or the debugger, and set the routine to correct values.


-16021 Repeat string length out of bounds (<module name>)

Explanation:

When executing the program, a length occurs in the routine specified in parentheses. This length is either undefined (NULL) or not within the valid interval. The interval is 0-4069 for use in DB procedures or otherwise, 0-12276.

User Action:

Find out the corresponding length specification using either test outputs or the debugger, and set the routine to a correct value.


-16022 Too much data

Explanation:

The contents of a variable does no longer fit into the value area.

User Action:

Enlarge the value area by modifying the SET parameter Value area.


-16023 No temporary space available

Explanation:

A temporary result does no longer fit into the value area.

User Action:

Enlarge the value area by modifying the SET parameter Value area.


-16024 Endless loop supposed (<module name>)

Explanation:

The number of iterations in the specified routine reached the maximum number defined in the LOOPCONTROL option.

User Action:

Check whether all loops function correctly in the specified routine. Use the debugger or the values output (VALUES) after a test run for this purpose.


-16025 Nested SQL calls not allowed (<module name>)

Explanation:

When constructing an SQL statement, a function is called which contains an SQL statement, too.

User Action:

The corresponding function must be processed before the SQL statement.


-16031 Call of stored command is too long (<module name>)

Explanation:

A call of a stored command issued within the routine specified in parentheses exceeds the maximum length permitted.

User Action:

Check the call of the stored command and reduce it accordingly.


-16032 NULL value not allowed in stored command (<module name>)

Explanation:

A call of a stored command issued within the routine specified in parentheses passes a parameter that has not a defined value but the NULL value; or not all required parameters have been specified.

User Action:

Find out the corresponding parameter using test outputs or the debugger, and set the routine to a correct value.


-16033 Stored command not found (<module name>)

Explanation:

A stored command is called in the routine specified in parentheses. This stored command does not exist.

User Action:

Check the name and the access right of the stored command, correct typing errors, if any, or create the corresponding command in QUERY.


-16040 No terminal I/O in batch (<program name>)

Explanation:

The program that was executed in batch mode makes input and output to the terminal.

User Action:

The program cannot be executed in batch mode. If this is desired, remove each input and output made to the terminal.


-16041 Module <name> has to be stored again ( e.g. with MSTORE )

Explanation:

The specified routine or form was translated with another SQL-PL version than the current one.

User Action:

The routine or form must be retranslated with the current SQL-PL version.


-16042 Invalid pattern in LIKE predicate

Explanation:

The pattern specified in a LIKE predicate does not meet the syntactical requirements.

User Action:

Check the pattern and correct it, if necessary.


-16050 Not a PROC (<module name>)

Explanation:

During the execution of a CALL PROC statement, the system determines that the module to be called is not defined as PROC. The program is aborted.

User Action:

Correct the call or the module header.


-16051 Not a FUNCTION (<module name>)

Explanation:

During the execution of a function call, the system determines that the module to be called is not defined as FUNCTION. The program is aborted.

User Action:

Correct the call or the module header.


-16052 Not a FORM (<module name>)

Explanation:

During the execution of a CALL FORM statement, the system determines that the module to be called is not defined as FORM. The program is aborted.

User Action:

Correct the call or the module header.


-16053 Not a HELPFORM (<module name>)

Explanation:

During the execution of a HELP FORM statement, the system determines that the module to be called is not defined as HELPFORM. The program is aborted.

User Action:

Correct the call or the module header.


-16054 Not a MENU (<module name>)

Explanation:

During the execution of an INCLUDE MENU statement, the system determines that the module to be called is not defined as MENU. The program is aborted.

User Action:

Correct the call or the module header.


-16080 End of file

Explanation:

The end of file was reached while reading.

User Action:

A user action is not required.


-16081 File <name> already open

Explanation:

The attempt was made to open a file the internal file identifier of which is already used.

User Action:

Either choose another internal file identifier or close the open file beforehand.


-16082 File <name> not writable

Explanation:

The attempt was made to write a file which was opened for reading only.

User Action:

Open the corresponding file for writing.


-16083 File <name> not readable

Explanation:

The attempt was made to read a file which was opened for writing only.

User Action:

Open the corresponding file for reading.


-16084 Too many files already opened

Explanation:

The maximum number of files which may be processed at the same time is reached.

User Action:

One of the open files must be closed first.


-16085 File <name> isn't open

Explanation:

The attempt was made to access an internal file identifier for which no OPEN was performed.

User Action:

The corresponding file must be opened first.


-16086 Open error at file <name>

Explanation:

The name of the file to be opened is incorrect (e.g., NULL), or the operating system yields an error when opening the file.

User Action:

Correct the OPEN statement.


-16100 Stack overflow (<module name>)

Explanation:

More space as available in the internal SQL-PL stack is needed for processing a program.

User Action:

Inform the ADABAS support.


-16101 There is no line for key labels (<module name>)

Explanation:

According to the terminal type, a key label line is required above the explicit message line. Such a line is missing here.

User Action:

Reserve a key label line above the explicit message line in the form layout.


-16102 Out of memory (<module name>)

Explanation:

The indicated program requires a greater value area than is currently set.

User Action:

The maximum size of the value area can be set using the SET parameters of SQL-PL. The maximum size depends on the used hardware.


-16103 PULLDOWN label and COMMENT buffer overflow

Explanation:

The maximum size of the storage area for labels and comments in the menu (10 KB) has been exceeded.

User Action:

Reduce the storage requirements by using shorter comments and labels.


-16104 Too many labels in menu

Explanation:

The maximum number of labels in the menu (160) has been exceeded.

User Action:

Distribute the menu to several menus and forms.


-16105 Too many PULLDOWNs in menu

Explanation:

The maximum number of pulldown menus (40) has been exceeded.

User Action:

Distribute the menu to several menus and forms.


-16106 Wrong terminal type

Explanation:

From this type of terminal, SQL-PL does not receive the local cursor keys. The result is that the menus and field-oriented forms cannot be executed.

User Action:

Only block-oriented forms can be executed on this terminal type.


-16107 All labels are empty in menu (<module name>)

Explanation:

The labels of the ACTIONBAR or BUTTONBAR are not set; the program stops.

User Action:

Ensure that at least one label of the ACTIONBAR or BUTTONBAR is set when the form is called with the ACTIONBAR or BUTTONBAR definition.


-16108 Actionbar out of window

Explanation:

The ACTIONBAR or BUTTONBAR is not contained in the visible section of the form.

User Action:

Choose such a section of the form that the ACTIONBAR or BUTTONBAR is visible.


-16201 '.' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16202 '=' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16203 ''' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16204 ':=' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16205 '(' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16206 ')' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16207 ':' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16208 '<->' expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16211 PROC, DBPROC, FORM or FUNCTION expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16212 LAYOUT expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16213 AND expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16214 DO expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16215 END expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16216 THEN expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16217 UNTIL expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16218 WHEN expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16219 AS expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16220 CALL expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16221 OF expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16222 Print parameter expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16223 TO or DOWNTO expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16224 READ, WRITE or APPEND expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16225 IMMEDIATE expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16226 INTO expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16227 ROWS expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16228 F1 or F2 ... or F12 or HELP expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16229 Length (S, M, L, XL) expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16230 HIGH, LOW, INV, BLK, UNDERL or ATTR1..ATTR16 expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16231 BACKGROUND, NOHEADLINE, SETLOCAL or SETOFF expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16232 SUM, AVG, COUNT, MIN, MAX, VAL1, VAL2, VAL3 or VAL4 expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16233 IN, OUT or INOUT expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16241 New line expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16242 Parameter expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16243 Special character expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16244 Comparison operand expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16245 Expression expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16246 Statement expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16247 Any character expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16248 Variable list expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16249 Literal expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16250 Slice specification expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16251 Compiler option expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16252 FORM option expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16253 Numeric literal expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16254 Logic expression expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16256 Parameters for stored command expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16257 REPORT result specification expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16258 SQL data type expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16259 Call of a stored command expected

Explanation:

A syntax check of the QUERY call was performed and no static or dynamic call of a stored command was detected.

User Action:

Correct the source code accordingly.


-16260 QUERY 'RUN' symbol expected

Explanation:

A syntax check of the QUERY call was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16261 Name of a stored command expected.

Explanation:

A syntax check of the QUERY call was performed and no name of a stored command was detected.

User Action:

Correct the source code accordingly.


-16262 'EXEC' symbol not allowed in REPORT call.

Explanation:

An 'EXEC' symbol was detected in a REPORT call. REPORT does not allow dynamic calls of a command.

User Action:

Correct the source code accordingly.


-16270 Constant is expected to be in hex notation

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16271 Because of vector slice in argument list a predicate is expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16280 Missing keyword

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16281 ENDLAYOUT expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16282 POS expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16284 VAR expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16285 CATCH expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16286 FROM expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16287 USING expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16288 PREPARE, EXECUTE or DESCRIBE expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Corrrect the source code accordingly.


-16300 Obscure statement

Explanation:

No SQL-PL statement can be recognized; perhaps, there is only a semicolon missing before the objected statement, or a keyword contains a typing error.

User Action:

Check the statement and correct it.


-16301 Type declaration not allowed

Explanation:

A parameter specification contains variables with and without type declarations.

User Action:

Remove the type declaration or declare all parameters with the same variable type.


-16302 Invalid layout specification

Explanation:

No correct name follows the input or output character of the field.

User Action:

A name or field number must be specified after the first character of the field (control character).


-16303 Invalid number

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16304 Invalid pattern

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16305 Invalid name

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16306 Invalid statement

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16307 Invalid boolean expression

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16308 Invalid slice specification

Explanation:

Vector slices in forms must be specified in ascending order.

User Action:

Correct the boundaries of the vector slices.


-16309 Invalid vector index

Explanation:

The specified vector index is less than 0, greater than 255, or no numeric expression.

User Action:

Correct the vector index.


-16310 Variable is a vector

Explanation:

The specified variable is used as scalar, although it was defined as vector.

User Action:

Correct the variable name; or specify another name for the variable, if necessary.


-16311 Variable is not a vector

Explanation:

The specified variable is used as vector, although it was defined as scalar.

User Action:

Correct the variable name; or specify another name for the variable, if necessary.


-16312 Undeclared variable

Explanation:

The specified variable is unknown. This error can only occur, if the compiler option 'Implicit Declaration' is disabled.

User Action:

Declare the variable. If you want to work without declarations, change the compiler option.


-16320 CALL and SWITCH not allowed in FUNCTIONs

Explanation:

A CALL or SWITCH statement was recognized, and the module is defined as FUNCTION.

User Action:

Define the CALL or SWITCH statement in a PROC module.


-16321 A vector component is not allowed as formal parameter

Explanation:

Only local-dynamic variables or local-dynamic vector slices without slice specification are permitted as formal parameters.

User Action:

If a single vector component is to be passed as current parameter, the formal parameter must be defined as local-dynamic variable. If a vector slice is to be passed as current parameter, the formal parameter must be defined as vector slice without slice specification.


-16322 Empty layout not allowed

Explanation:

The layout of the form does not contain any field.

User Action:

Insert at least one field into the form layout.


-16323 MESSAGE is not allowed here

Explanation:

If the MESSAGE variable shall be used explicitly within the form layout, it can be specified only once as output variable.

User Action:

Correct the MESSAGE field definition.


-16324 Sign is not allowed here

Explanation:

The number of single quotes is not correct in a string constant.

User Action:

Correct the string constant.


-16325 CALL and SWITCH not allowed in HELPFORM screens

Explanation:

The checked module is of the type HELPFORM, and a CALL or SWITCH statement was recognized.

User Action:

Use normal FORM modules in case of HELPFORMS having a more complicated structure.


-16326 This SQL command is not allowed here

Explanation:

The following SQL statements are not allowed in SQL-PL:

- CONNECT

- DECLARE

- MFETCH

- OPEN CURSOR

- COMMIT WORK RELEASE

- COMMIT RELEASE

User Action:

These commands cannot be used in an SQL-PL program.


-16327 PAGE statement and explicit MESSAGE are not allowed

Explanation:

An explicit MESSAGE field and the PAGE statement were defined in this form. The PAGE statement is only allowed in forms without explicit MESSAGE field.

User Action:

The explicit MESSAGE field can be omitted, because FORM creates such a field automatically.


-16328 Only one field allowed in FIELD statement with DOMAIN specification

Explanation:

A DOMAIN definition was specified for a list of fields in the FIELD statement. This is not allowed.

User Action:

If a DOMAIN definition shall be valid for several fields, specify a FIELD statement with a corresponding definition for each field.


-16329 AUTOPAGE statement not allowed with ACTIONBAR definition

Explanation:

AUTOPAGE is not allowed in a FORM using an ACTIONBAR.

User Action:

Correct the source code.


-16330 Only one INIT, SIZE and CHECK specification per FIELD statement allowed

Explanation:

More than one INIT, SIZE, or CHECK specification was recognized in one of the FIELD statements.

User Action:

Correct the FIELD statement.


-16331 This statement in CONTROL block is not allowed

Explanation:

This statement is not allowed in the CONTROL block. The statements allowed in the CONTROL block of FORM screens are:

- CALL

- SWITCHCALL

- SWITCH

- RETURN

- STOP

- PICK

- PUT

In HELPFORMs, CALL, SWITCHCALL, and SWITCH are not allowed either.

User Action:

Call an SQL-PL routine in the CONTROL statement using CALL. This routine can be used to process all SQL-PL statements.


-16332 Only one ACCEPT option allowed

Explanation:

The restriction specified in the error message was violated.

User Action:

Correct the source code.


-16333 Only one CONTROL option allowed

Explanation:

The restriction specified in the error message was violated.

User Action:

Correct the source code.


-16334 In HELPFORM screens only local variables are allowed

Explanation:

A global variable was recognized in the checked HELPFORM.

User Action:

Correct the HELPFORM.


-16335 Only 20 attribute options on form call allowed

Explanation:

The restriction specified in the error message was violated.

User Action:

Correct the source code.


-16336 Only 20 INPUT/NOINPUT variable arguments on form call  allowed

Explanation:

The restriction specified in the error message was violated.

User Action:

Correct the source code.


-16337 This statement is only allowed in field-oriented forms

Explanation:

A statement was recognized which is only valid in field-oriented forms.

User Action:

Either omit this statement or define the form as a field-oriented form.


-16338 Only 20 DISPLAY formats per form allowed

Explanation:

The restriction specified in the error message was violated.

User Action:

Correct the source code.


-16340 Only ACTIONBAR in first line allowed

Explanation:

If the keyword ACTIONBAR is specified in the first line of the form layout, no other form field may be defined there.

User Action:

Correct the source code.


-16341 ACTIONBAR expected

Explanation:

The ACTIONBAR can only be used in the processing part of the form when it is defined in the form layout.

User Action:

Correct the source code.


-16342 PULLDOWN Menu not defined

Explanation:

The name of a pulldown menu was recognized. But no definition is available for this menu.

User Action:

Correct the typing error or define the missing pulldown menu.


-16343 Too many levels of PULLDOWN menus

Explanation:

A maximum of four nesting levels is allowed for pulldown menus.

User Action:

Correct the source code.


-16344 Too many labels in menu

Explanation:

The ACTIONBAR contains more than 11 actions or the pulldown menu contains more than 16 functions.

User Action:

Correct the definition of the menu.


-16346 BUTTON in the layout expected

Explanation:

The BUTTON definition in the form layout is missing for the BUTTON specification in the processing part of the form.

User Action:

The position of the BUTTONBAR must be determined by the keyword BUTTON in the layout part of the form.


-16347 ACTIONBAR or BUTTON not defined

Explanation:

The ACTIONBAR or BUTTONBAR defined in the form layout are not specified in the processing part of the form.

User Action:

Define the ACTIONBAR or BUTTON statement in the processing part of the form.


-16350 This statement is illegal in a DB procedure

Explanation:

A statement was recognized which is not allowed in a DB procedure.

User Action:

Correct the source code.


-16351 This statement is illegal in field oriented forms

Explanation:

A READ or WRITE statement was determined in a field-oriented form. Such a statement is not permitted there, because it is implicitly executed in field-oriented forms.

User Action:

Remove the READ or WRITE statement from the field-oriented form.


-16352 Global variables not allowed in functions

Explanation:

A global variable was determined in the function. But only local variables are allowed in functions.

User Action:

Correct the source code.


-16353 All or none of the fields have to belong to a group

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16354 Group name expected

Explanation:

A syntax check was performed and the error returned was detected at the cursor position.

User Action:

Correct the source code accordingly.


-16355 Input variables may occur only in one FIELD statement

Explanation:

The syntax check detected an input field that occurs in more than one FIELD statement. The cursor is positioned on that input field.

User Action:

Correct the source code accordingly.


-16356 Global variables not allowed in DB procedures and triggers

Explanation:

A global variable was determined in the DB procedure or trigger. But only local variables are allowed in DB procedures or triggers.

User Action:

Correct the source code.


-16360 Too many modules in this program

Explanation:

The maximum number of routines and forms of a program is 63.

User Action:

The program must be redesigned. Either put routines or forms together or build a second program to which a branch can be made using SWITCHCALL.


-16361 Too many variables

Explanation:

512 global variables are allowed per program.

User Action:

Check whether global variables can be transformed into local ones.


-16363 Too many field groups

Explanation:

Ten field groups are allowed per form.

User Action:

Correct the specifications.


-16364 Too many SQL variables

Explanation:

300 SQL variables are allowed per SQL statement.

User Action:

Correct the specifications.


-16365 Too many parameters

Explanation:

255 parameters are allowed per module.

User Action:

Reduce the parameter list.


-16370 Routine/Form too complex

Explanation:

A routine can be split up by calls of other routines or functions.

User Action:

It may be sufficient to reduce the constants. But bear in mind that in forms, each text and in routines, each SQL statement belongs to the constants.


-16400 This name is reserved

Explanation:

The attempt was made to specify a keyword as identifier, or there are so many mistakes in a statement that it cannot be recognized.

User Action:

Choose another identifier or correct the statement.


-16402 Duplicate definition

Explanation:

A syntactical element was specified several times for a REPORT or QUERY statement.

User Action:

Correct the statement.


-16411 Up to 255 different fields may be used at runtime

Explanation:

A form may contain more than 255 fields within the layout. But only 255 of these fields may be represented on the screen at runtime.

User Action:

Call the form in a smaller screen section (option SCREENSIZE).


-16412 Up to 9 different attribute definitions are possible

Explanation:

More than nine different definitions were recognized for attributes.

User Action:

Correct the source code in such a way that no more than nine different definitions are available.


-16413 Up to 20 ignore definitions are possible

Explanation:

More than 20 IGNORE statements were recognized.

User Action:

Correct the source code in such a way that no more than 20 IGNORE statements are used.


-16420 Number of parameters does not agree

Explanation:

Not all parameters expected for this built-in function are specified, or they are not separated by a comma.

User Action:

Correct the specifications.


-16430 This variable definition does not match the number of layout fields

Explanation:

The definition of the vector slice does not correspond to the number of fields of the assigned field number.

User Action:

Specify exactly the number of fields placed one below the other that results from the definition of the assigned vector slice.


-16431 There is no corresponding variable for this field number

Explanation:

No variable is assigned to the field number.

User Action:

In a FIELD statement, a variable must be assigned to the field number.


-16432 Number of fields does not match the slice definition

Explanation:

The definition of the vector slice does not correspond to the number of specified fields.

User Action:

Specify exactly the number of fields placed one below the other that results from the definition of the vector slice.


-16433 All fields of a vector slice have to be input or output fields

Explanation:

When a vector slice was used in a form layout, not all fields were of the same type.

User Action:

Correct the special characters for the input or output field.


-16434 Variable, vector or field number has to be defined  in the layout

Explanation:

The variables, vectors, or field numbers specified in the processing statements after the form layout must occur in the layout.

User Action:

Check the name or number of the corresponding field.


-16435 This variable is already defined as input field

Explanation:

In a form, a variable was defined as input field more than once.

User Action:

Each variable may only be assigned to one field of the form.


-16436 The value has to be greater than 0

Explanation:

The numeric constant in the FIELD/SIZE statement is <= 0.

User Action:

Correct the constant.


-16440 This SQL command is too long or the closing parenthesis is missing

Explanation:

The specified SQL statement exceeds the valid length, perhaps because the closing parenthesis is missing.

User Action:

Add the closing parenthesis or reduce the SQL statement.


-16441 This QUERY/REPORT command is too long

Explanation:

The specified QUERY/REPORT command exceeds the valid length, perhaps because the closing parenthesis is missing.

User Action:

Add the closing parenthesis or reduce the QUERY/REPORT command.


-16442 Maximal length exceeded

Explanation:

A number, a string, a format screen, or the like, is too long.

User Action:

Find out the length restriction of the object, the compiler considered to be too long (cursor position) and modify its length.


-16460 Label not found

Explanation:

The skip label specified in the SKIP statement is not defined.

User Action:

Define the skip label.


-16461 Too many labels

Explanation:

20 skip labels are allowed per routine.

User Action:

Correct the specifications.


-16462 Duplicate label

Explanation:

There are several skip labels with the same name in the routine.

User Action:

Give unique names to the skip labels.


-16490 DOMAIN definition syntactically incorrect

Explanation:

A syntax error was detected in the FIELD/DOMAIN statement.

User Action:

Correct the FIELD/DOMAIN statement.


-16491 Unknown DOMAIN name

Explanation:

No definition is available for the specified DOMAIN name.

User Action:

Define the DOMAIN.


-16492 Unknown field or group in NEXTFIELD or NEXTGROUP statement

Explanation:

The field/group name specified in the NEXTFIELD/NEXTGROUP statement must already be used in a FIELD/GROUP statement. Such a statement is missing, or a typing error was made.

User Action:

Insert the FIELD/GROUP statement or correct the typing error.


-16493 No label definition possible for this key

Explanation:

Labels can only be specified for the following keys:

F1, SK1, PF1, ..., F12, SK9, PF9, HELP, UP, DOWN.

User Action:

A user action is not possible.


-16500 Not yet implemented

Explanation:

The specified statement is intended but not yet integrated into the current version.

User Action:

A user action is not possible.


-16501 System error

Explanation:

This is an internal SQL-PL error.

User Action:

Inform the ADABAS support.


-16502 Invalid system variable

Explanation:

An internal SQL-PL order is incorrect.

User Action:

Inform the ADABAS support.


-16503 Internal value error : <error number>

Explanation:

A system error with the displayed error number occurred while administering variable values.

User Action:

Inform the ADABAS support.


-16505 Internal database error : <error number>

Explanation:

A database error occurred when an SQL statement was executed. Either the database state or an internal SQL-PL order is incorrect. The displayed number relates to the error message of the database.

User Action:

Inform the ADABAS support.


-16506 Out of system memory

Explanation:

Variable values require more space during the processing of the application than is provided by the system memory.

User Action:

Use variable values sparingly. Memory is released, when

-	variables are set to NULL.

-	SWITCH is used to change to another program.

-	a procedure with parameters and local variables is left.


-16510 Syntax tree too complex

Explanation:

The routine or form cannot be translated, because there is no sufficient internal storage space available.

User Action:

Reduce the routine/form.


-16514 Bounds of vector slice parameter exceeded

Explanation:

The bounds of the current vector slice parameter are exceeded in the called routine or form.

User Action:

Check the size of the vector slice and adapt it accordingly.


-16515 Parameter must be a vector slice

Explanation:

The formal parameter declaration needs a vector slice whereas the current parameter is not a vector slice.

User Action:

The sequence and type of the parameters specified for the call of the routine or form must be checked and corrected.


-16519 System error while accessing a variable value

Explanation:

SQL-PL is not able to access a variable's value.

User Action:

Inform the ADABAS support.


-16600 Precompiler and SQL-PL interpreter are incompatible

Explanation:

The precompiler version does not correspond to that of the SQL-PL interpreter.

User Action:

Use a precompiler and an SQL-PL interpreter of the same version and retranslate the program.


-16601 One of the variable values is too large

Explanation:

The total length of all parameter and variable values which the SQL-PL routine or form returns to the program is restricted to 4K.

User Action:

The SQL-PL routine or form must be written in such a way that the total length of all values returned to the program does not exceed the maximum length.


-16602 One of the output variables is not known in the form

Explanation:

A field specified in the OUTPUT clause is not known in the form, or a typing error was made.

User Action:

Compare the fields defined in the form against those used in the OUTPUT clause.


-16604 Too many parameters

Explanation:

The number of current parameters transferred with the call of an SQL-PL routine/form is greater than that of the parameters defined formally.

User Action:

Change the call.


-16700 Database not accessible

Explanation:

The component SQL-PL is no longer connected to the database. There may be different causes for it.

User Action:

Check the state of the network and database.


-16704 Error during CONNECT on additional database

Explanation:

A system error occurred in multi-db mode.

User Action:

Inform the ADABAS support.


-16705 Too many databases

Explanation:

In multi-db mode eight simultaneous database connections can be established.

User Action:

Use unused database connections.


-16706 Unknown symbolic database name

Explanation:

No CONNECT was performed for a symbolic database name used in an SQL statement.

User Action:

First, perform a CONNECT for the symbolic database name in the program. Perhaps, a typing error was made. Check therefore whether the symbolic database name in the CONNECT statement differs from that in the SQL statements.


-16730 Wrong SQL data type

Explanation:

The usage of the SQL-PL variables does not correspond to the definition in the SQL statement.

User Action:

Check why the value of one of the variables in the SQL statement is not of the required type. This possibility must be prevented by corresponding checks.


-16731 Command not prepared

Explanation:

While performing the EXECUTE statement, the system determines that the PREPARE statement has not been executed.

User Action:

The PREPARE statement must be included or it must be ensured that it is executed.


-16901  <name> not found

Explanation:

The search string specified for the module or variable name in the XREF menu was not found.

User Action:

A user action is not required.


-16902 Program: <name> not found

Explanation:

There is no program of the specified name for which the user has access privileges.

User Action:

The workbench command 'PLIST' displays all programs for which you have access privilegesr.


-16903 Module <name> not found

Explanation:

There is no module with the specified name for which you have access privileges.

User Action:

The workbench command 'MLIST' displays all modules for which you have access privileges.


-16904 Value <name> not found

Explanation:

The variable name specified in the VALUE menu was not found.

User Action:

A user action is not required.


-16905 User <name> does not exist

Explanation:

This message occurs in case of GRANT, IMPORT, EXPORT, or REVOKE, if no user with the specified name exists.

User Action:

The SQL statement 'SHOW USER' displays all database users in the system.


-16906 Module <name> is not a DB Procedure

Explanation:

No module with the specified name was found as DB procedure for PDROP.

User Action:

The workbench command 'PSHOW' displays all DB procedures.


-16907 Module <name> is not a trigger

Explanation:

No module with the specified name was found as trigger for TDROP.

User Action:

The workbench command 'TSHOW' displays all triggers.


-16908 Trigger <name> already exists

Explanation:

For TCREATE, an already existing trigger name was specified.

User Action:

Choose another trigger name or remove the existing trigger using TDROP <name>.


-16909 Invalid version <version>

Explanation:

The version (TEST, PROD, or HIST) specified during the creation of the module list does not exist for this module name.

User Action:

The version specification 'ALL' can be used to find out which versions exist for the modules wanted.


-16910 Invalid command

Explanation:

There is no workbench command with the specified name.

User Action:

Check the command syntax.


-16911 No command in history

Explanation:

No command was issued in the command line which could be redisplayed.

User Action:

A user action is not required.


-16912 Invalid parameter

Explanation:

An invalid search string was specified as parameter for the PLIST, MLIST, EXPORT, PRINT, or STORE command.

User Action:

Check the command syntax.


-16913 Invalid menu

Explanation:

A prefix command was issued from an invalid menu.

User Action:

Issue the command from the command line.


-16914 Cursor not at prefix

Explanation:

LIST or EDIT was called using a softkey, but the cursor was not placed in the prefix area.

User Action:

Place the cursor on a prefix line and press the softkey again.


-16922 Privilege cannot be granted

Explanation:

An error occurred when granting a privilege.

User Action:

Reissue the command. Inform the ADABAS support in case of repeated failures.


-16925 Program <name> cannot be dropped

Explanation:

An error occurred when dropping a program.

User Action:

Reissue the command. Inform the ADABAS support in case of repeated failures.


-16926 Module <name> cannot be deleted

Explanation:

An error occurred when deleting a module.

User Action:

Reissue the command. Inform the ADABAS support in case of repeated failures.


-16927 <Name> is in EDIT status

Explanation:

When starting (RUN) a module, the system recognized that the module was in EDIT status. Therefore it could not be executed.

User Action:

STORE the module. Then start it with RUN.


-16928 Modules in DB state cannot be modified

Explanation:

The attempt was made to modify a DB procedure stored in the kernel (DROP, DELETE, EDIT).

User Action:

Before DB procedures can be modified, they must have been removed from the kernel using PDROP.


-16931 No export privilege

Explanation:

No export privileges were granted to other users.

User Action:

A user action is not required.


-16932 No grant privilege

Explanation:

No GRANT was issued for other users.

User Action:

A user action is not required.


-16933 No import privilege

Explanation:

No import privileges are available for programs of other users.

User Action:

A user action is not possible.


-16934 No privilege on program <name>

Explanation:

Neither import nor call privileges were granted to other users.

User Action:

A user action is not required.


-16935 Grant error

Explanation:

An error occurred when granting the call privilege.

User Action:

Reissue the command. Inform the ADABAS support in case of repeated failures.


-16936 IMPORT error

Explanation:

A syntax error occurred when importing a module.

User Action:

The command LIST with the parameter SAVE shows all modules where syntax errors occurred. Store these modules out of the editor to display the syntax errors which can then be corrected.


-16937 REVOKE error

Explanation:

An error occurred when revoking a privilege.

User Action:

Reissue the command. Inform the ADABAS support in case of repeated failures.


-16940 No literal defined

Explanation:

The LANG command provided for the selection of the translation language only makes sense when entries are available in the literal table.

User Action:

Literals can be defined using DOMAIN. Recall the LANG command to display all languages for which literals are defined in a selection menu.


-16941 Set parameters not saved

Explanation:

The set menu was modified and then left with INTERRUPT.

User Action:

A user action is not required.


-16942 SET info not found

Explanation:

It is not possible to read the SET information.

User Action:

A user action is not possible.


-16951 First character must be a letter

Explanation:

An invalid program or module name was chosen when creating a new SQL-PL module. The name must begin with a letter.

User Action:

Change the name and restore the module.


-16952 Invalid program name

Explanation:

An invalid program name was chosen when creating a new SQL-PL module. The name must not contain special characters, except the underscore '_'.

User Action:

Change the name and restore the module.


-16953 Invalid module name

Explanation:

An invalid module name was chosen when creating a new SQL-PL module. The name must not contain special characters, except the underscore '_'.

User Action:

Change the name and restore the module.


-16954 '.' expected

Explanation:

When a new SQL-PL module is created, program and module names separated by a dot are expected after the keyword PROC, FORM, FUNCTION, DBPROC, DBFUNC, TRIGGER, or HELPFORM. The dot between program and module names is missing.

User Action:

Correct the line and restore the module.


-16955 Valid object type expected

Explanation:

When a new SQL-PL module is created, the keyword PROC, FORM, FUNCTION, DBPROC, DBFUNC, TRIGGER, or HELPFORM is expected to be the first word in the edit form.

User Action:

Correct the line and restore the module.


-16956 Module <name> already exists

Explanation:

When storing the SQL-PL module, the system recognized that the name of the module was changed and that there was already a module with this new name.

User Action:

Either change the name and restore the module or press the [image] key again to overwrite the existing module.


-16957 Too many procedures/forms

Explanation:

The maximum number of procedures and forms of a program which contain global variables is 63.

User Action:

The program must be redesigned. Either put procedures or forms together or build a second program to which a branch can be made using SWITCHCALL.


-16958 Module <name> is not a procedure

Explanation:

When generating a DB procedure, the system recognized that the called module is not a procedure.

User Action:

For the generation of a DB procedure, only modules can be utilized which in the module list are identified by the type PROC or FUNC.


-16959 Name has more than 18 characters

Explanation:

A name longer than 18 characters was chosen in the edit form when creating a new SQL-PL module.

User Action:

Shorten the name and restore the module.


-16962 Excluding of all columns not allowed

Explanation:

When generating a program with EXPRESS, not all columns of the table can be exported.

User Action:

Check the contents of the table columns.


-16966 Table has more than <n> columns

Explanation:

When generating a program with EXPRESS, not all columns of the table can be exported.

User Action:

Check the contents of the table columns.


-16970 Invalid table name

Explanation:

An invalid table name was specified when filling in an EXPRESS form.

User Action:

Correct the table name and confirm it with [image].


-16971 Table name must be specified

Explanation:

No table name was specified when filling in an EXPRESS form.

User Action:

Correct the table name and confirm it with [image].


-16972 Program name must be specified

Explanation:

No program name was specified when filling in an EXPRESS form.

User Action:

Enter a program name and confirm it with [image].


-16973 Filename must be specified

Explanation:

No filename was specified when filling in an EXPRESS form.

User Action:

Enter a filename and confirm it with [image].


-16974 Position must be between 1 and 14

Explanation:

An incorrect screen position was specified when filling in an EXPRESS form.

User Action:

Enter a value between 1 and 14 for the position specification and confirm it with [image].


-16975 Size not between <n> and <m>

Explanation:

An incorrect screen size was specified when filling in an EXPRESS form.

User Action:

Set the size to a value within the range of values and confirm it with [image].


-16976 Prompt must be special character

Explanation:

An invalid prompt character was specified when filling in an EXPRESS form.

User Action:

Change the prompt character to a special character and confirm it with [image].


-16977 Library name must be specified

Explanation:

No library name was specified when filling in an EXPRESS form.

User Action:

Specify a library name and confirm it with [image].


-16978 Unknown reference name

Explanation:

An invalid reference name was specified when filling in an EXPRESS form.

User Action:

Change the reference name and confirm it with [image].


-16979 Reference name must be specified

Explanation:

No reference name was specified when filling in an EXPRESS form.

User Action:

Specify a reference name and confirm it with [image].


-16986 Open error at file <name>

Explanation:

When importing an operating system file, the specified filename was not found.

User Action:

Check the filename and correct it, if necessary.


-16987 Abort - TEST version exists for <program name>

Explanation:

While importing a program as productive version, the system determines that the program, or parts of it, already exist(s) as test version. Therefore, the operation fails.

User Action:

The test version must be deleted; save it, if necessary.


-16999 Not implemented

Explanation:

A command has been called which is not yet implemented in the current version of the workbench.

User Action:

A user action is not possible.


-17001 Unknown prefix command - execution rejected

Explanation:

The commands allowed in the prefix area are I, D, C, M, /, >, ", X, S. The command S is only allowed in the prefix area of excluded columns.

User Action:

Delete the unknown prefix command or replace it with one that is known.


-17002 Pending <name> command

Explanation:

The second mark of the corresponding block command (or the P/F mark) cannot be found.

User Action:

Specify or delete the second mark of the command (or the P/F mark).


-17003 Multiple p/f targets specified - execution rejected

Explanation:

More P/F marks are specified than COPY or MOVE commands (M, C).

User Action:

Just one P/F mark must be specified for each COPY or MOVE command. Delete the supernumerary P/F marks.


-17004 Edit form too small

Explanation:

The maximum size of the edit form (12K) was exceeded during the execution of the last command.

User Action:

The text may be split and processed in several edit forms.


-17005 Printer not available

Explanation:

The text was not logged, because the printer is not available.

User Action:

Check the printer.


-17006 Invalid option

Explanation:

The specified option is not allowed, or the command syntax is not correct.

User Action:

Specify another option, or check the command syntax and correct it, if necessary.


-17007 Filename must be enclosed in single quotes

Explanation:

none

User Action:

The filename specified with the PUT and GET command must be enclosed in single quotes (e.g. PUT 'filename').


-17008 File error :

Explanation:

The error occurred when a file was opened or closed.

User Action:

A user action is not required.


-17009 No line copied

Explanation:

The specified input area to be copied is empty.

User Action:

A user action is not required.


-17010 PICK command rejected

Explanation:

The specified area to be copied into the pick buffer is empty or exceeds the maximum size of the pick buffer (2K).

User Action:

Copy the area in several parts that do not exceed the pick buffer size into the pick buffer.


-17011 Buffer is empty

Explanation:

The PICK buffer is empty.

User Action:

Use the PUT command to fill the PICK buffer.


-17012 No line(s) changed

Explanation:

The CHANGE command was not executed, because the specified string did not occur in the input area, or the specification of the command syntax was not correct, or the edit area (12K) was exceeded by the CHANGE command.

User Action:

Check the command for syntactical correctness and, if necessary, use the '/' command to search for the string to find out whether the string occurs in the input area.


-17013 Records truncated

Explanation:

At least one line of the text is longer than the maximum line length of the editor (132 characters). The lines longer than 132 characters were truncated.

User Action:

Adapt the line length of the text to that of the editor.


-17014 Command buffer empty

Explanation:

The command cannot be executed, because the input area is empty.

User Action:

A user action is not required.


-17015 Too many prefix commands

Explanation:

The maximum number of prefix commands (20) was exceeded. A prefix command area is used for every excluded block of lines.

User Action:

Perform the prefix commands one after the other or redisplay the excluded blocks of lines by specifying an 'S' in the prefix area.


-17016 No WRAP, line is too long

Explanation:

The WRAP function can only be enabled when the editor lines are not longer than the editor window.

User Action:

Use SPLIT to adapt the lines that are longer than the editor window.


-17017 WRAP is RED command

Explanation:

The WRAP function can only be enabled in the RAND editor.

User Action:

Use the RED command to activate the RAND editor.


-17018 More than <couunt> edit lines

Explanation:

You may only edit the specified number of lines.

User Action:

The supernumerary lines must be deleted.


-20001 Database <name> does not exist

Explanation:

A non-defined database name was passed as parameter for an external call of the backup function.

User Action:

Check the specified database name.


-20002 This username is already defined

Explanation:

An already existing user name was specified for the user definition.

User Action:

Choose another user name.


-20004 CONTROL profile <Name> not found

Explanation:

No CONTROL profile with the specified name could be read.

User Action:

Check the access rights on the directory of the specified file.


-20005 Unknown <sysusertype> name/password combination

Explanation:

An unknown name and password combination was specified when connecting to CONTROL or when changing the system user configuration. Depending on the action, CONTROL-DBA, SYSDBA, COLDUSER, OPERATOR, or DOMAIN is displayed as <sysusertype>.

User Action:

Correct the input.


-20007 Different passwords, please reenter!

Explanation:

For the user definition, the second password entry differs from the first entry. It must be a typing error.

User Action:

Enter the password again and repeat it for security reasons.


-20008 Alter <sysusertype> in WARM state only!

Explanation:

In COLD database state, the attempt was made to change the SYSDBA or DOMAIN password using Configuration / Alter Parameters / Systemuser. These actions are only allowed in WARM database state. 'SYSDBA' or 'DOMAIN User' can be displayed as <sysusertype>.

User Action:

Start the SERVERDB and repeat the selection.


-20009 Alter CONTROL user in COLD/OFFLINE state only!

Explanation:

The attempt was made to redefine the CONTROL user using Configuration / Alter Parameters / Systemuser. This action is not possible in WARM database state.

User Action:

Shut the SERVERDB down and repeat the selection.


-20010 Tempfile <name> does not exist!

Explanation:

The temporary file <name> could not be created during the execution of a CONTROL function.

User Action:

Check the access rights on the directory of the specified file.


-20011 No termcharset defined

Explanation:

The attempt was made to display a list of the loaded termchar sets using Configuration / Alter Parameters / Termchar Set. But no termchar set could be found.

User Action:

Use Load Systables to load the default termchar set.


-20012 No mapcharset defined

Explanation:

The attempt was made to display a list of the defined mapchar sets using Configuration / Alter Parameters / Mapchar Set. But no mapchar set could be found.

User Action:

Inform the ADABAS support.


-20018 Devspace path already defined

Explanation:

During installation, a name was entered twice in the list of the devspace paths.

User Action:

Specify another path for the marked devspace.


-20019 Data devspace size is too small! (min = 1500 pages)

Explanation:

The size of the data devspace defined during installation is too small. The minimum size is 1500 pages.

User Action:

Increase the value for the data devspace size.


-20020 Log segment size is too small (min = 300 pages)

Explanation:

The specified LOG SEGMENT SIZE is too small. The minimum size must not be less than 300 pages (1.2 MB).

User Action:

Increase the LOG SEGMENT SIZE specification.


-20022 Invalid value entered

Explanation:

An invalid value was entered.

User Action:

Correct the input.


-20025 Value <= 0 not allowed here!

Explanation:

A value that is not a positive number was entered into a field.

User Action:

Correct the input.


-20026 Log mode DUAL was not defined!

Explanation:

During installation, a second LOG SIZE was entered which determines the size of the DUAL LOG. But the LOG MODE is SINGLE or DEMO.

User Action:

Either change the LOG MODE or set the second LOG SIZE to '-'.


-20027 No log segmentation, when log mode is DEMO!

Explanation:

During installation, a value greater than 0 was specified in the field LOG SEGMENT SIZE and the LOG MODE was set to DEMO. It is not possible to segment the log in DEMO mode.

User Action:

Either change the LOG MODE or set the LOG SEGMENT SIZE to '0'.


-20028 Device does not exist

Explanation:

A non-existent raw device was specified during installation.

User Action:

Define the raw device and repeat the installation.


-20029 Transaction log size is too small (min = 300 pages)

Explanation:

The size specified for TRANSACTION LOG DEVSPACES is too small. The minimum size must not be less than 300 pages (1.2 MB).

User Action:

Increase the TRANSACTION LOG SIZE specification.


-20030 Archive log size is too small (min = 1000 pages)

Explanation:

The size specified for ARCHIVE LOG DEVSPACES is too small. The minimum size must not be less than 1000 pages (1.2 MB).

User Action:

Increase the ARCHIVE LOG SIZE specification.


-20031 While restarting the SERVERDB, x_start failed!

Explanation:

An error occurred in the utility program x_start while starting the SERVERDB into COLD mode.

User Action:

For more information, select Diagnose/OpMessages.


-20032 While restarting the SERVERDB, x_clear failed!

Explanation:

An error occurred in the utility program x_clear while starting the SERVERDB into COLD mode.

User Action:

For more information, select Diagnose/OpMessages.


-20033 Offline Shutdown failed due to x_stop

Explanation:

An error occurred in the utility program x_stop while shutting down the SERVERDB into COLD mode.

User Action:

For more information, select Diagnose/OpMessages.


-20035 Remote SQL Server could not be started!

Explanation:

The server for remote operation of the SERVERDB cannot be started.

User Action:

Inform the ADABAS support.


-20036 Kernel trace activation failed!

Explanation:

The kernel trace cannot be activated.

User Action:

Inform the ADABAS support.


-20037 Kernel trace deactivation failed!

Explanation:

The kernel trace is already deactivated after a shutdown/restart.

User Action:

A user action is not required.


-20038 Kernel trace buffer flush failed!

Explanation:

The kernel trace buffer cannot be written.

User Action:

A user action is not required.


-20040 Unkown transaction code in operating menu

Explanation:

An invalid operation was selected within CONTROL.

User Action:

A user action is not required.


-20044 Invalid numeric value

Explanation:

An invalid value was entered.

User Action:

Correct the input.


-20046 This medium already exists !

Explanation:

A duplicate Media ID was specified.

User Action:

Enter another name for the Media ID.


-20049 Cannot define more than 254 backup media

Explanation:

There are already 254 backup media defined.

User Action:

Delete a backup medium to be able to define a new backup medium.


-20065 Missing SERVERDB argument for backup operation

Explanation:

No database name was passed for an external call of the backup function.

User Action:

Correct the backup call.


-20068 Error when calling for x_param !

Explanation:

An error occurred while executing the utility program x_param.

User Action:

Inform the ADABAS support.


-20069 Error when calling for x_cons !

Explanation:

An error occurred while executing the utility program x_cons.

User Action:

Inform the ADABAS support.


-20072 Error while generating tempfile <name>

Explanation:

The specified temporary file could not be created while executing a CONTROL function.

User Action:

Check the access rights on the directory of the specified file.


-20073 Backup operation was aborted!

Explanation:

An error occurred during the backup operation.

User Action:

For more information, select Backup / Show / Protocol.


-20081 BREAK - Another CONTROL background process is already active

Explanation:

The attempt was made to start a long-running process displayed in the BACKGROUND field of the main screen for other CONTROL sessions. At calling time, however, there is another process active. In the BACKGROUND field, the following actions are displayed as BACKGROUND process:

UPDATE STATISTICS, VERIFY DEVSPACES, LOAD SYSTABLES, SAVE and RESTORE operations.

User Action:

Repeat the call at a later time. The BACKGROUND field should contain NONE.


-20082 Error when opening CONTROL profile

Explanation:

The specified profile file could not be found when calling CONTROL.

User Action:

Check the access rights on the directory of the specified file.


-20094 Create of systemtables failed

Explanation:

After starting the SERVERDB, the attempt was made to create the system tables SYSBU$MEDIA, SYSBU$REPORT, and SYSBU$HISTORY. An error occurred hereby. (The system tables are only relevant as R/3 interface.)

User Action:

Inform the ADABAS support, if necessary.


-20100 Update of system tables failed

Explanation:

After a backup operation, the attempt was made to update the system tables

SYSBU$MEDIA, SYSBU$REPORT, and SYSBU$HISTORY. An error occurred hereby. (The system tables are only relevant as R/3 interface.)

User Action:

Check whether the system tables belong to the SYSDBA and can be read and written by all users. Inform the ADABAS support, if necessary.


-20102 Invalid value for devspace size

Explanation:

During installation, no positive number was specified as DEVSPACE size.

User Action:

Enter the size under SYS SIZE and/or LOG SIZE.


-20103 The devspace name (special file name) has to be defined

Explanation:

No devspace name was specified for the Add Devspace function.

User Action:

Enter the devspace name.


-20105 No permission to create directory : <name>

Explanation:

The specified directory could not be created.

User Action:

Check the access rights on the specified directory.


-20106 No permission to create file : <name>

Explanation:

The specified file could not be created.

User Action:

Check the access rights on the directory of the specified file.


-20108 No remote server access - local CONTROL use only

Explanation:

CONTROL was called for another node.

User Action:

CONTROL can only be used in local operation.


-20113 Dual devspace is missing

Explanation:

During installation, the log mode DUAL or NORMAL was defined, but no second DEVSPACE was specified as DUAL LOG.

User Action:

Make a LOG SIZE entry for another DEVSPACE.


-20114 DBROOT is missing

Explanation:

The system variable DBROOT has not been set. This variable must contain the root directory for the database.

User Action:

Set the variable DBROOT before calling CONTROL.


-20116 The DUAL LOG SIZE must be equal to the first LOG

Explanation:

The size specification of the DUAL LOG differs from that of the first log devspace.

User Action:

Enter the size specified for the first LOG also for the second LOG.


-20117 Automatic backup is already running

Explanation:

The attempt was made to start an automatic backup, but there is already an active automatic backup.

User Action:

Wait for the end of the first backup; then restart the automatic backup.


-20118 Invalid SYSDBA

Explanation:

An invalid SYSDBA was specified.

User Action:

Correct the input.


-20119 Device name too long!

Explanation:

Device names may be 64 characters in length. When combining commands for an automatic backup, the command string can internally become longer than 132 characters.

User Action:

Use operating system means to link the device name to a shorter name which can then be specified in CONTROL.


-20121 Version not allowed for two devices

Explanation:

During a database backup, 'V' was specified for Overwrite in order to keep different versions. This is only possible for a backup made to one device. If you specify a second device to obtain a copy of the backup, you are not allowed to keep different versions.

User Action:

Correct the input.


-20123 REQUEST TIMEOUT must be shorter than LOCK TIMEOUT

Explanation:

The parameter for REQUEST TIMEOUT specified during installation is too  large in relation to the LOCK TIMEOUT.

User Action:

Either decrease the REQUEST TIMEOUT or increase the LOCK TIMEOUT.


-20125 Start a backup generation by performing a complete database save first!

Explanation:

The attempt was made to save the log or the updated pages without having performed a save of the complete database. An incremental save is always based on a save of the whole database.

User Action:

First, perform a complete save.


-20126 Medium does not exist!

Explanation:

A backup operation was started without defining a backup medium.

User Action:

Fill in the displayed form. If an identifier is entered in the field 'Medium', all specifications are stored and can be used for the next backup operation.


-20128 Not allowed while AUTOSAVE LOG is running!

Explanations:

A backup action was started, and CONTROL determined that Autosave Log is enabled.

User Action:

Disable Autosave Log or do without the backup action.


-20129 Medium does already exist!

Explanations:

The attempt was made to enter a new medium, but the specified identifier already exists.

User Action:

Enter another media identification.


-20130 Up to 4 backup devices allowed

Explanations:

For parallel backup, more than four media were selected from the media list.

User Action:

Select up to four media.


-20131 Wrong save type

Explanations:

A non-existing save type was specified for the batch call.

User Action:

Correct the save type.


-20132 Cannot create a new version, because file already exists

Explanations:

A file cannot be renamed for the automatic administration of backup versions, because the target file already exists.

User Action:

Rename the target file or delete it.


-20133 Count of defined backup devices is too small  (ALTER KERNEL PARAMETER)

Explanations:

The number of defined backup devices is too small.

User Action:

Increase the corresponding parameter.


-20201 CRONTAB exists in unix environment only !

Explanation:

The Schedule Manager can presently only be activated on a UNIX platform.

User Action:

A user action is not required.


-20202 Error submitting CRONTAB <name>!

Explanation:

The Schedule Manager was activated (Schedule ON), deactivated (Schedule OFF), or actions were confirmed. An error occurred thereby while reading the temporary file <name> into crontab [crontab <name>].

User Action:

Check and modify, if necessary,  the access rights on cron (e.g.: in the file /usr/lib/cron/cron.allow or /usr/lib/cron/cron.deny) and on the directories in the path of <name>. The file <name> contains the changed cron entries; it can be deleted.


-21100 UNKNOWN CONTROLUSER/CONTROLPASSWORD

Explanation:

The specifications for the parameters CONTROLUSER and/or CONTROLPASSWORD made in the login screen or command line are not identical with the XPARAM file specifications.

User Action:

Either change the CONTROLUSER and/or CONTROLPASSWORD specification for the XPARAM login or change the XPARAM file.


-21101 SERVERDB MISMATCH

Explanation:

The specification for the parameter SERVERDB made in the login screen or command line is not identical with the specification in the XPARAM file.

This error can only occur, when the XPARAM fils was manipulated.

User Action:

Delete the XPARAM file where the error occurred using the command 'x_param -CLEAR <dbname>'. Afterwards, a new XPARAM file with the desired <dbname> can be created.


-21102 MANDATORY VALUE MISSING

Explanation:

Some parameters must be set to values. The corresponding parameter has not yet received a value.

User Action:

Assign a value to the parameter.


-21103 COPY FAILED

Explanation:

It was not possible to create a new XPARAM file. Perhaps, access privileges on the operating system level are not correct.

User Action:

Check the corresponding access rights.


-21104 PRINT FAILED

Explanation:

It was not possible to print the XPARAM file. The operating system rejects the execution of this print job. Perhaps, the printer installation is not correct.

User Action:

The system administrator must check the operating system print commands as well as the installation of the printer.


-21105 XPARAM FILE EXISTS

Explanation:

The attempt was made to write to an existing XPARAM file.

An XPARAM file can only be copied with a new file name.

User Action:

Modify the XPARAM filename.


-21106 NOT CORRESPONDING PARAM. DELETED

Explanation:

This message appears at the CHECK screen or in the protocol file, along with the corresponding parameter.

The parameter was deleted from the XPARAM file to restore consistency with the XPARAM help file.

User Action:

In principle, no user action is required. But consider the explanation of the message -21107.


-21107 NOT CORRESPONDING PARAM. DETECTED

Explanation:

An inconsistency between the XPARAM file and the XPARAM help file was detected. The differing parameters were deleted from the XPARAM file. The deleted parameters are recorded in the protocol file.

This error can only occur, when

1.	a new ADABAS version was installed or

2.	invalid manipulations were made to the XPARAM help file.

User Action:

Install the original XPARAM help file, if no new ADABAS version was installed.

If this XPARAM session is the first session after an ADABAS installation, then no user action is required.


-21108 NO XPARAM CREATION FOR SUPERUSER

Explanation:

The attempt was made to call the program with the XPARAM superuser identification. It is not possible to create an XPARAM file with the CONTROLUSER name 'superuser'.

User Action:

Modify the CONTROLUSER name.


-21109 CONTROLUSER/SERVERDB NOT DIFFERENT

Explanation:

CONTROLUSER name and SERVERDB name must differ from each other.

User Action:

Modify the CONTROLUSER name and/or the SERVERDB name.


-21110 PASSWORD MISMATCH

Explanation:

The two entries for the password are not identical.

User Action:

Repeat the password entry.


-21111 RUNDIRECTORY PATH TOO LONG

Explanation:

The program was started with the call argument '-r <rundir-path>'. It was not possible to create the directory path for the parameter RUNDIRECTORY, because the maximum length of 56 characters was exceeded.

Remember that the argument <rundir-path> must only consist of the path without SERVERDB identification.

User Action:

Specify a correct directory path.


-21112 TERMINAL INITIALISATION FAILED

Explanation:

Right after the program start, the compatibility of the operating system with the terminal is checked. This check was negative. It was not possible to initialize the terminal. The reason may be:

1.	Incorrect setting of operating system variables (DBTERM and DBHIF),

2.	Missing directories, especially under 'terminfo',

3.	Missing or incorrect terminal description files (see 'terminfo').

User Action:

Install the terminal environment correctly.


-21300 INTEGER OVERFLOW

Explanation:

This message appears in CHECK mode, along with the corresponding parameter.

The CALC computation result for the parameter exceeds the size of the integer data type.

User Action:

Modify the values of the arguments of the CALC computation accordingly.


-21301 SUBTRACTION FAILED

Explanation:

This message appears at the CHECK screen, along with the corresponding parameter.

The value of the parameter became negative during the execution of a CALC computation. Negative values are not allowed.

User Action:

Modify the values of the arguments of the CALC computation accordingly.


-21302 DIVISION FAILED

Explanation:

This message appears at the CHECK screen, along with the corresponding parameter.

The value of the divisor became zero or negative within a CALC computation.

User Action:

Modify the values of the arguments of the CALC computation accordingly.


-21303 PRIMARY PARAMETER NOT ACCESSIBLE

Explanation:

This message appears at the CHECK screen, along with the corresponding parameter.

It was not possible to read the primary parameter from the XPARAM file to compare it with the result of the internal computation.

User Action:

Enter a value for the primary parameter. It is possible to change to the INSERT mode by positioning the cursor to the parameter and pressing [image].


-21304 SECONDARY PARAM. NOT ACCESSIBLE

Explanation:

This message appears at the CHECK screen, along with the corresponding parameter.

It was not possible to read the secondary parameter from the XPARAM file to compare it with the result of the internal computation. The parameter on the left of the screen is the secondary parameter.

User Action:

Enter a value for the primary parameter. It is possible to change to the INSERT mode by positioning the cursor to the parameter and pressing [image].


-21305 CALC failed

Explanation:

This message appears at the CHECK screen and in the protocol file, along with the corresponding parameter.

A CALC computation could not be performed. The circumstances can be explained in more detail by more messages which are then output BEFORE this message. Usually, valid ranges of values were exceeded.

There may be various CALC computations for a parameter.

User Action:

The user action depends on the other messages. All secondary parameters should be checked.


-21306 CONSTRAINT NOT SATISFIED

Explanation:

This message appears at the CHECK screen and in the protocol file, along with the corresponding parameter.

The CONSTRAINT condition was not satisfied. This is the case when the comparison of the CONSTRAINT computation with the value of the primary parameter was negative.

There may be various CONSTRAINT computations for one parameter.

User Action:

There are two possibilities: adapt either the values of the primary parameter or the arguments of the CONSTRAINT condition.


-21307 CANNOT COMPUTE CONDITION

Explanation:

This message appears at the CHECK screen and in the protocol file, along with the corresponding parameter.

This computation could not be performed, because the values of the secondary parameters could not be accessed. The parameter on the left of the screen is the primary parameter.

Generally, there is at least one other message output with this message to specify the error more exactly.

User Action:

Ensure that all secondary parameters are provided with valid values before computing the conditions of the primary parameter.

It is possible that no data was input for a parameter. The parameter on the left of the screen is the secondary parameter.

It is also possible that the computation of the conditions for a parameter stated BEFORE this parameter was incomplete.


-21308 CANNOT CHECK CONSTRAINT CONDITION

Explanation:

After entering a new value, an implicit check of a CONSTRAINT condition was performed.

It was not possible to compute the CONSTRAINT, because necessary arguments, such as secondary parameters, were missing.

The new value was entered in the XPARAM file; but without a check.

User Action:

Ensure that all arguments of the CONSTRAINT are satisfied. Generally, this is the case when all parameters at the screen (MENU mode) are set to values. Then start the consistency check.


-21800 SYSTEM ERROR: INPUT LINE TOO LONG

Explanation:

The installation of XPARAM is incorrect.

The reason for this error can be an incorrect file to be read by XPARAM. Perhaps the help file was created in another operating system.

User Action:

Install a new XPARAM version with special consideration of the environment of the file.


-21801 SYSTEM ERROR: INVALID XHELPFILE

Explanation:

The installation of XPARAM is incorrect.

The version identification of the help file is different from that of the XPARAM program.

User Action:

Install a new XPARAM version.


-21802 SYSTEM ERROR: DBNAMEFILE FAILED

Explanation:

It was not possible to open and/or write the DBNAMEFILE.

User Action:

Perhaps, the user is not authorized to access the directory '/tmp'.


-21803 SYSTEM ERROR: XHELPFILE FAILED

Explanation:

It was not possible to open the help file.

User Action:

Perhaps, the user is not authorized to access the directory '$DBROOT/env'.


-21804 SYSTEM ERROR: PROTFILE FAILED

Explanation:

It was not possible to open the protocol file.

User Action:

Perhaps, the user is not authorized to access the directory where XPARAM was started. Another reason can be that the access authorization of an existing protocol file does not correspond to that of the current user.


-21805 to -21919

When these messages occur, contact the ADABAS Support.


-23000 Cannot show your tables!

Explanation:

The database tables for which you have a privilege cannot be determined.

Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23001 Cannot select this session!

Explanation:

Probably, there is no longer a connection to the database.

User Action:

Inform the database administrator.


-23002 Cannot find the field:

Explanation:

A table column specified in a query design does not exist in any of the tables selected for the query.

User Action:

Correct the column name or add the table containing the corresponding column to the query.


-23003 The result of a SELECT is too big!

Explanation:

Several result sets linked to the object were requested at the same time for an SQLFetchLink.

User Action:

Check the link description. Ensure that only one result set is requested for each SQLFetchLink statement.


-23004 Database error occurred!

Explanation:

An error occurred while accessing the database.

User Action:

QueryPlus should be started with the start parameter /D (see OfficePlus online help) in order to obtain a more detailed description of the database error.


-23005 Unknown DDE EXECUTE command!

Explanation:

An unknown DDE EXECUTE command was sent to QueryPlus, or its syntax is not correct.

User Action:

Correct the DDE EXECUTE command.


-23006 Database access failed!

Explanation:

An error occurred while accessing the database.

User Action:

QueryPlus should be called with the start parameter /D (see OfficePlus online help) in order to obtain a more detailed description of the database error.


-23007 Too many joins!

Explanation:

Too many joins have been specified in a query definition. Up to 500 joins are allowed.

User Action:

Reduce the number of joins.


-23008 Cannot release the session!

Explanation:

The existing database connection cannot be terminated regularly. Probably, there is no longer a connection to the database.

User Action:

This message can be ignored if no other connect is to be performed. Otherwise, the database administrator must be informed.


-23010 Cannot get the SQL statement!

Explanation:

The system could not find an SQL statement stored with the specified name.

User Action:

Check the name for the stored SQL statement or correct it.


-23011 Cannot get the Query command!

Explanation:

The system could not find a QUERY command stored with the specified name.

User Action:

Correct the name.


-23012 Cannot save the SQL statement!

Explanation:

The SQL statement you formulated could not be stored in the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23013 Cannot delete the query!

Explanation:

The query you specified could not be deleted from the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23014 Cannot save the query!

Explanation:

The query you formulated could not be stored in the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23015 Cannot read the query!

Explanation:

The query to be modified could not be retrieved from the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23016 Cannot read the SQL statement!

Explanation:

The SQL statement to be modified could not be retrieved from the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23017 Error while writing the MS-Excel file!

Explanation:

An error occurred while writing an MS-Excel file.

User Action:

Check the specified path and the storage capacity and correct them, if necessary.


-23018 Unknown MS-Excel file type!

Explanation:

The MS-Excel file type you selected is not known.

User Action:

Select a known MS-Excel file type.


-23019 Cannot create the MS-Excel file!

Explanation:

The MS-Excel file you specified could not be created.

User Action:

Check the specified path and the storage capacity and correct them, if necessary.


-23020 Cannot execute DDE or no result!

Explanation:

An error occurred in a database query performed via DDE, or the query did not produce any result.

User Action:

Check the database query. QueryPlus should be started with the start parameter /D (see OfficePlus online help) in order to obtain a more detailed description of a possible database error.


-23021 Too many columns!

Explanation:

Too many columns have been specified for a query design.

User Action:

Reduce the number of specified columns.


-23022 Syntax error:

Explanation:

A criterion in the query design contains a syntax error.

User Action:

Check the syntax of all criteria in the query design and correct them, if necessary.


-23023 Cannot add table:

Explanation:

An error occurred while adding a table to a query design.

User Action:

Inform the database administrator.


-23024 Cannot read the link!

Explanation:

The specified link could not be retrieved from the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23025 Cannot save the link!

Explanation:

An error occurred while storing a link in the database. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23026 Cannot share objects!

Explanation:

An error occurred while sharing objects. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23027 Cannot show your shared objects!

Explanation:

An error occurred while displaying shared objects. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.


-23028 Cannot stop sharing of objects!

Explanation:

An error occurred while terminating a sharing procedure for an object. Probably, there is no longer a connection to the database.

User Action:

A check must be made as to whether there is still a connection to the database. If this is not the case, another connection can be established by selecting the Database/Connect menu or by connecting directly to the database. Should this not be possible, inform the database administrator.