BGSSIA

2016	NO SPACE FOUND FOR SIA/SSIA Meaning The SIA/SSIA is too large and cannot be internally stored. Response Reduce length of subschema, repeat definition.
2301	INVALID SYNTAX IN SOURCE STATEMENT Meaning The keyword SUBSCHEMA is followed by a string which cannot be interpreted as a name. The next valid begin keyword is searched for. Response Enter correct statement.
2302	STATEMENT BEGINNING WITHOUT CORRECT PRIMARY KEYWORD Meaning A statement does not begin with a permissible begin keyword. The next valid keyword is searched for. Response Enter correct statement.
2303	NO VALID STATEMENT INPUT Meaning No statement which can be interpreted has been input. BGSSIA terminates. Response Restart BGSSIA using correct statement.
2304	DATABASE COULD NOT BE OPENED. DB-STATUS = NNNNN Meaning Error when entering the READY statements to the linked-in DBH. If OPENED is followed by a (2), then the error occurred during the second READY for entering the name table and the item table. Response According to the DB status.
2305	SCHEMA-NAME MISSING, NAME OF USERSCHEMA IS ASSUMED Meaning No schema name follows the keyword OF. The name of the user schema is used. Response None.
2306	KEYWORD OF MISSING, NAME OF USERSCHEMA IS ASSUMED Meaning The subschema names are followed by the mandatory keyword OF. The name of the user schema is used as the schema name. Response None.
2310	DISPLAY CLAUSE WITHOUT GENERATE CLAUSE Meaning The DISPLAY statement can only be executed in conjunction with the GENERATE statement. BGSSIA terminates after having performed a DELETE statement. Response Restart with either BPSIA or BGSSIA using correct statements.
2311	DIFFERENT NAME IN THE DISPLAY AND GENERATE CLAUSE Meaning The subschema names in the DISPLAY and GENERATE statements do not match. The entire DISPLAY statement is ignored and the next valid begin keyword is searched for. Response Enter DISPLAY statement without subschema names etc.
2312	THE SCHEMANAME MUST BE THE SAME AS IN THE GENERATE CLAUSE Meaning The schema name specified in the DISPLAY or DELETE statement does not match that of the GENERATE statement. The entire DISPLAY or DELETE statement is ignored and the next valid begin keyword is searched. Response Specify correct schema name or omit.
2315	NO MEDIA SPACE AVAILABLE ON DBDIR Meaning DBDIR overflow when storing the generated SSIA or creating the NAME and ITEM records. Response Use BREORG to increase size of DBDIR. If there is no space available for the NAME and ITEM records, it will BE necessary to use BGSSIA to delete the generated SSIA from the DBDIR. Rerun BGSSIA.
2316	NO DBKEY FOR NAME-/ITEM-RECORD AVAILABLE Meaning The DBTT for the specified record type in the PRIVACY-AND-IQF-SCHEMA is too small. Response Use BREORG to increase the size of the DBTT. Use BGSSIA to delete the generated SSIA from the DBDIR.
2320	NO CORRECT OUTPUT OF THE SCHEMA-COMPILATION Meaning No user schema definition exists in the compiler database. Response Repeat database definition.
2321	THE SCHEMA-NAME IS DIFFERENT FROM THE COMPILED SCHEMA Meaning The specified schema name does not match that in the DDL schema compilation. Response None, or specify correct schema name and repeat BGSSIA.
2330	SUBSCHEMA subschemaname NOT FOUND Meaning There is no subschema definition with the indicated name in the compiler database. Response Specify correct subschema name or first compile subschema with DDL, then repeat BGSSIA.
2331	SSIA OF SUBSCHEMA subschemaname NOT FOUND Meaning The SSIA of the indicated subschema which is to be deleted does not exist. Response None.
2332	SSIA OF SUBSCHEMA subschemaname EXISTS ALREADY Meaning An SSIA for the indicated subschema exists already. Response Use REGENERATE or DELETE statement.
2334	NO AREAS IN SUBSCHEMA Meaning Error when reading the first realm definition, belonging to the subschema, from the compiler database. Response Correct subschema, repeat DDL and BGSSIA; if the error is reproducible, compile diagnostic documentation and write error report.
2335	NO RECORDS IN SUBSCHEMA FOUND Meaning Error when reading the first record type definition, belonging to the subschema, from the compiler database. Response Correct subschema, repeat DDL and BGSSIA; if the error is reproducible, compile diagnostic documentation and write error report.
2336	REC NAME HAS NOT WITHIN-DESCRIPTORS Meaning For the AREA-WITHIN-LIST in the SSIA there are no entries within the compiler database. Response Correct subschema, repeat DDL and BGSSIA; if the error is reproducible, compile diagnostic documentation and write error report.
2337	REC recordname HAS INCORR. NR. CALC-ITEMS Meaning In the compiler database, the number of CALC key item definitions for the indicated record type on subschema level deviates from that on schema level. (CALC key items omitted in the subschema must still be defined in the compiler database for the subschema). Response Correct subschema, repeat DDL and BGSSIA; if the error is reproducible, compile diagnostic documentation and write error report.
2338	NO ITEM-TABLE, NAME-TABLE INCOMPLETE GENERATED Meaning When reading from the scratch file, end of file was reported prematurely. Response Repeat BGSSIA using the REGENERATE statement.
2339	I/O ERROR DURING HANDLING OF SCRATCH-FILE NO ITEM-TABLE OR NAME-TABLE IS STORED Meaning When writing or reading in the scratch file, an I/O error occurred. The scratch file is required for buffer storage when generating the name and item tables. The generated SSIA is retained. Response Repeat BGSSIA using the REGENERATE statement.