The following table describes the codes (error codes, return codes, information return codes) that can occur in connection with database handling. These codes occur in BSA messages, in the logs and reports of the BSA database utilities, etc.
Note: IRCs >= 1000 are product-specific codes. Most of these codes occur in connection with database operations. Product-specific codes are described in the Messages and Codes of the corresponding product.
The Comp. column indicates the originating component of the code, which is included for informational purposes.
BQL
BQL component
GBL
Global Index Server
VSAM
VSAM component
OBJ
Object Server
SPS
Spool Service
FMT
Format component
BSAM
BSAM component
BOF
Base Output Facility component
BAF
Base Archive Facility component
VSV
VSAM Server
Code |
Comp. |
Description |
---|---|---|
1 |
BQL |
Keyword error. The BQL statement contains an undefined keyword; check the keywords in the statement for spelling mistakes etc. |
2 |
BQL |
Table is not defined in the definition file. |
3 |
BQL |
Table set in error. See 'STARTUP Errors' and SYSLOG messages. |
4 |
BQL |
Field is not defined in the definition file. |
5 |
BQL |
Wrong value count; the UPDATE or INSERT statement contains fewer or more values than fields. |
6 |
BQL |
Value conversion error; the specified value could not be converted to the internal format of the field. |
7 |
BQL |
Comparison operator invalid or missing. |
8 |
BQL |
Boolean operator invalid or missing. |
9 |
BQL |
Value invalid. Length error. |
10 |
BQL |
Field parameter missing in INSERT, SELECT or UPDATE statement. |
11 |
BQL |
WHERE clause missing in UPDATE or DELETE statement. |
12 |
BQL |
Value parameter missing in UPDATE or INSERT statement. |
13 |
BQL |
Statement incomplete. |
14 |
BQL |
Value exceeds range of field. |
15 |
BQL |
Invalid key in ORDER clause. Key not available in database. |
16 |
BQL |
Definition file not updated, specified file not found. |
17 |
BQL |
Keyword missing. |
18 |
BQL |
Definition file not updated: no product specified for deleting, inserting or updating. This applies only to the file definition. |
19 |
BQL |
Definition file not updated: File ID invalid. |
20 |
BQL |
Definition file not updated: File type invalid. |
21 |
BQL |
Only the internal or external field format can be entered. |
22 |
BQL |
A table or key cannot be found. This occurs only while a database is being loaded. |
23 |
BQL |
The database mask used for the date is invalid. |
25 |
BQL |
The WHERE command used in the BQL command is too long. |
30 |
BQL |
Definition file not updated: duplicate dataset name. |
31 |
BQL |
Definition file not updated: status of dataset not model. |
32 |
BQL |
Wrong CSI; CSI has to be a multiple of 4096. |
33 |
BQL |
File was not deleted: File not empty. |
34 |
BQL |
Keyword missing. |
35 |
BQL |
The generation file is missing. |
36 |
BQL |
Duplicate keyword in BQL statement. |
37 |
BQL |
The file is not available because it has already been closed. |
38 |
BQL |
The VSAM file could not be found. |
39 |
BQL |
The desired function is unavailable while the database is running because the database is shared. If databases are shared, you must stop all database access to be able to delete spool files, insert generation files, etc. |
40 |
BQL |
An error has occurred during the file opening. |
41 |
BQL |
The spool file, cache file, or index file cannot be deleted. The database is still used by another STC or batch job. |
42 |
BQL |
BST05DBL was called to load data into a GEN file, but the GENFILE(nn) parameter has not been coded. GENFILE(nn) is required if the file to be loaded is a GEN file. |
43 |
BQL |
Generation file not deleted: File not empty. |
44 |
BQL |
BST05DBL encountered an error during writing of the UNLOAD file. |
45 |
BQL |
Inconsistent length; the length specified in the table definition of the definition file differs from the length specified in the sequential file. This occurs only while a database is being loaded. |
46 |
BQL |
Sequential file could not be allocated. |
47 |
BQL |
Sequential file could not be opened. |
48 |
BQL |
While loading a database, an error (GET) has occurred in module BST05DBL. |
49 |
BQL |
The file exit could not be found. |
50 |
BQL |
Communication error between slave and master. |
55 |
BQL |
A requested resource was locked beforehand (Enqueue), for example: LOCK NAME(xxx) TEST This code also occurs, for example, if a user requests to browse or print from an archive tape volume that is already in use by another user. |
61 |
BQL |
The field could not be found in table BSAUBP. |
62 |
BQL |
The table BSAUBP could not be found. |
63 |
BQL |
It is not allowed to update or delete table BSAUBP. |
70 |
BQL |
A reload request has been made for a data set that is not open. |
75 |
BQL |
A select was made on a dataset record, but the dataset could not be found. |
76 |
BQL |
Dataset is invalid. |
77 |
BQL |
The transferred pointer is invalid. |
78 |
BQL |
The print control length is invalid; check the accompanying messages to determine the cause of the print error. |
79 |
SPS |
An error occurred on the spool page. |
80 |
SPS |
List is already open in the current transaction. |
81 |
SPS |
Report was not opened because list is not open. The list must be opened before you can open a report. |
83 |
SPS |
Command failed because list and/or report not open. |
86 |
BAF |
The archive dataset contains unexpected data (OSH). |
87 |
BAF |
The archive dataset contains unexpected data. |
88 |
BAF |
Read error (Page); SPS (spool service) cannot read in the spool. Check the accompanying messages to determine the cause of the read error. |
89 |
BAF |
A list is to be browsed or printed from an archive tape, but the maximum number or tapes that can be allocated has already been reached. This number is controlled by the LST parameter B08_ARCHIVE_TAPE = n. |
90 |
BAF |
Archive pool not found |
91 |
BAF |
File allocation error |
92 |
BAF |
File open error |
93 |
BAF |
Write error; check the accompanying messages to determine the cause of the write error. |
95 |
BAF |
Block record for reload not found |
96 |
BAF |
Archive type not defined |
97 |
BAF |
Archive version not defined |
98 |
BAF |
Page not found (This occurs during tape view.) |
99 |
BAF |
Read error; check the accompanying messages to determine the cause of the read error. |
102 |
VSAM |
VSAM error: file not found. |
103 |
VSAM |
VSAM error: undefined command/request. |
105 |
VSAM |
General VSAM error. |
106 |
VSAM |
The contents of the block used do not correspond with those in SMR/SIR. |
111 |
BQL |
Block allocation error: the database is full. |
120 |
BQL |
Record not deleted: inconsistency between record and key. |
121 |
BQL |
Record not updated: inconsistency between record and key. |
122 |
BQL |
Record not read: inconsistency between record and key. |
130 |
BQL |
Duplicate table. |
131 |
BQL |
Table is not allocated in the file. |
135 |
BQL |
The LOG file is too small. |
140 |
BQL |
Key not found: inconsistency between record and key. |
141 |
BQL |
Record not updated: inconsistent key length. |
142 |
BQL |
Duplicate key: key must be unique. |
143 |
BQL |
Record not read: inconsistent key length in a SELECT command. |
144 |
BQL |
Record not deleted: inconsistent key length in a DELETE command. |
145 |
BQL |
Invalid key block. |
146 |
BQL |
Invalid table block. |
150 |
BQL |
While comparing the database record with the old one, inconsistencies have been found (REC is not equal to OLDREC). |
151 |
BQL |
An invalid command occurred during a log sequence. |
160 |
BQL |
Shutdown was carried out before the lock database is unlocked. |
161 |
BQL |
Two lock databases have been executed. |
212 |
SPS |
Inconsistent timestamp between product pointer, spool index or page block. |
213 |
SPS |
Spool page number invalid. |
216 |
SPS |
Error in spool index: file ID = 0. |
217 |
SPS |
Error in spool index: rba = 0. |
218 |
SPS |
Error in spool index: slot = 0. |
219 |
SPS |
Error in spool index: slot invalid. |
221 |
SPS |
Error in spool index: CI size = 0. |
224 |
SPS |
Page number invalid. |
226 |
SPS |
The page note defined for this specific list page was not found. |
227 |
SPS |
Referenced print control page not found. |
230 |
SPS |
When pages exceed the size of 32K, the page number will become invalid. |
250 |
SPS |
Reload request for an expired list. |
255 |
SPS |
A list is to be browsed or printed from an archive tape, but LST parameter B08_ARCHIVE_TAPE = 0 has been specified, which forbids this. Contact your system administrator if you have to browse or print from archive tapes. |
301 |
FMT |
Work file for formatter could not be allocated. |
302 |
FMT |
IDCAMS error; refer to the IDCAMS protocol (SYSPRINT) to determine the cause of this error. |
303 |
FMT |
VSAM file could not be allocated. |
304 |
FMT |
VSAM file could not be opened. |
305 |
FMT |
VSAM file could not be initialized. |
306 |
FMT |
VSAM file could not be closed. |
307 |
FMT |
Work file for formatter could not be deallocated. |
310 |
FMT |
Error in the master control block (SMR) of the VSAM file. |
312 |
FMT |
VSAM file is already formatted. |
320 |
FMT |
VSAM file could not be opened. |
350 |
BSAM |
End of volume: file is full. |
400 |
BOF |
Output allocation error |
401 |
BOF |
Allocation error |
402 |
BOF |
QSAM open error |
403 |
BOF |
User authorization error |
404 |
BOF |
An error occurred while loading one of the product exits. |
405 |
BOF |
STC authorization error |
406 |
BOF |
An error occurred while decompressing a page. |
450 |
BOF |
Invalid page control block (PAB) |
701 |
OBJ |
Serialization error |
702 |
OBJ |
Initialization error |
705 |
OBJ |
File ID has been switched during deallocation |
711 |
OBJ |
File not found |
712 |
OBJ |
File not found |
715 |
OBJ |
VSAM control block (SIR) is reserved |
721 |
OBJ |
Allocation error. Medium (tape, disk etc.) error |
722 |
OBJ |
Allocation error |
723 |
OBJ |
BSAM open error |
724 |
OBJ |
BSAM point error |
725 |
OBJ |
BSAM read error |
726 |
OBJ |
BSAM write error |
727 |
OBJ |
BSAM block number |
728 |
OBJ |
LFDNR out of range |
731 |
OBJ |
A select was made for a dataset record, however, the dataset was not found. |
732 |
OBJ |
AOR record not found |
735 |
OBJ |
Invalid page length |
736 |
OBJ |
Invalid page |
737 |
OBJ |
No data page |
738 |
OBJ |
Loop next page |
740 |
OBJ |
INDEXPTR not found |
741 |
OBJ |
SPOOL pointer not found |
742 |
OBJ |
PAGE not found |
743 |
OBJ |
Print control not found |
744 |
OBJ |
Timestamp of a block in error |
745 |
OBJ |
Block level error |
746 |
OBJ |
An invalid insert type has been used |
747 |
OBJ |
An error has occurred during decompression |
748 |
OBJ |
Max IO exceeded |
749 |
OBJ |
Invalid page number |
750 |
OBJ |
No devices have been allowed in the LST member |
751 |
OBJ |
Asynchronous archive access is requested |
801 |
GBL |
GLP not found |
802 |
GBL |
IAR not found |
811 |
GBL |
GBL DIFF INS/DEL |
812 |
GBL |
IDX DIFF INS/SEL |
819 |
GBL |
GLP TIME TYPE |
821 |
GBL |
GLOBAL PTR = ZERO |
822 |
GBL |
INDEX PTR = ZERO |
851 |
VSV |
Invalid server INIT phase |
852 |
VSV |
Invalid server call |
853 |
VSV |
Invalid server structure (VSV) |
854 |
VSV |
Invalid access (INS/SEL/DEL) |
855 |
VSV |
Invalid remote access (SELECT) |
856 |
VSV |
Request (BRW/PRT/ARC/RDR/CLN) |
857 |
VSV |
OPEN ==> (LIST/RSRCE/REPORT) |
858 |
VSV |
Report/list not open |
859 |
VSV |
Invalid page |
860 |
VSV |
Page structure has no data |
861 |
VSV |
Page number outside this document |
862 |
VSV |
Invalid page extension |
863 |
VSV |
Invalid page decompression |
864 |
VSV |
Database definition file (DD BnnDEFI) not available |
865 |
VSV |
List/report is not closed |
871 |
VSV |
Unique document token = zero |
872 |
VSV |
List/report pointer = zero |
873 |
VSV |
Pointer is invalid |
874 |
VSV |
Invalid product (Beta 93/97) |
881 |
VSV |
Document is not expired (REQ=DEL) |
901 |
BQL |
Product not found. See SYSLOG. |
902 |
BQL |
Subsystem ID not found. See SYSLOG. |
903 |
BQL |
DD card (product DEFI) not found. See SYSLOG. |
904 |
BQL |
Definition file in error. See SYSLOG. |
905 |
BQL |
Synchronization file in error. See SYSLOG. |
906 |
BQL |
Inconsistent timestamp in the database. See SYSLOG. |
907 |
BQL |
Synchronization file already in use. |
Note: IRCs >= 1000 are product-specific codes. Most of these codes occur in connection with database operations. Product-specific codes are described in the Messages and Codes of the corresponding product.