BINILOAD

DUPLICATE KEYS OR DB-KEYS FOUND / REC REF‘S OR RSQ’S OUT OF RANGE

SEE PRINTER OUTPUT

Meaning
All duplicated key values or database keys, any illegal database keys and RSQs found in the input records are also output under the header
“LIST OF DUPLICATE KEYS OR DBKEYS / LIST OF REC REF‘S OR RSQ’S OUT OF RANGE”.
Database keys are only output if the user has declared them externally.

The following cases can be distinguished:

1.	The duplicated key values which are found are output to SYSLST in decimal or hexadecimal format, preceded by “DUPL KEY: ”. This is the case with CALC keys or set keys for which DUPLICATES NOT has been defined in the DDL. For set keys this clause applies only within each individual set occurrence. Key values which already exist in the database are also covered by the check. Response for case 1 Take the following steps to determine which input records correspond to the duplicate keys found. Determine the CALC keys or set keys in question. If the BINILOAD run has been started from a terminal with option MSG = FH, SYSLST printouts are logically incorporated into the BINILOAD runtime log; if the routine has been started as an ENTER job, the messages on SYSLST as a whole follow those on SYSOUT, in which case assignment is more difficult. The first key can be determined from the WARNING on SYSOUT and further keys from the DUPLICATES NOT clauses and the key lengths. Combine the key from the individual key items and determine their individual positions in the DB record (RECORD-DISPL, LENGTH) using the key information in the SSI (BPSIA log). Determine, using the RECORD-DISPL statements for this BINILOAD run, how these key items have been filled with the strings (DISPL,LENGTH) of the input record. Locate the input record belonging to a duplicated output key value by means of the EDT (if an input record belonging to a duplicated key value has been found, all input records of the same set occurrence can be found via the key for OWNER selection). After determining the respective input records, correct input file and reset the database (if required), then repeat BINILOAD.
2.	The database key or the RSQ has been declared externally by the user in the input record. For clarification, a further distinction must be made:
2.1.	If an invalid key has been marked as “DUPL KEY: ” on SYSLST, one of the two cases 2.1.1. or 2.1.2. applies, otherwise 2.2.
2.1.1.	The listed key value is a duplicated CALC key or set key for which DUPLICATES NOT has been defined in the DDL: 1. applies.
2.1.2.	The listed key value is a duplicated database key or RSQ. The indicated database key or RSQ had already been assigned within the database or declared for one of the input records. Using the listed key values, the user must determine whether case 2.1.1 or 2.1.2 applies. The database keys and RSQs shown in hexadecimal form must have been defined in at least one of the input records. The hexadecimal database key begins with the REC-REF number of the record to be stored (see BPSIA log). The record to which the duplicated database key has been assigned in the input file can be determined via the field defined for the database key entry in the input record. Response for case 2.1 After determining the input record concerned, correct the input file in accordance with the meaning of the duplicated database key or RSQ, reset the database if required, and restart BINILOAD.
2.2.	If an illegal key listed on SYSLST is marked by the header “REC REF OR RSQ OUT OF RANGE”, the REC-REF or record sequence number of the database key or RSQ that was declared for the input record is not in the permissible value range. The permitted ranges are determined by the database type (2-Kbyte or 4/8-Kbyte) and by the DBTT size of the existing database. After 1000 occurrences of header “REC REF OR RSQ OUT OF RANGE” in SYSLST the following message is listed: “FOR ALL OTHER RECORDS RSQ OUT OF RANGE OCCURED”. Response for case 2.2 Reset the database if required, select values suitable for the database type (2-Kbyte or 4/8-Kbyte), increase the DBTT with BREORG to allow for the highest record sequence number defined in the input records, and restart BINILOAD.

NO USER-HASH-ROUTINES LOADED

Meaning

The module library dbname. HASHLIB either does not exist at all or does not contain all user-own hash routines defined in the DDL, including the connection module UDSHASH (from BGSIA). The names of the missing modules are output. If no user-own hash routines are required within the specific load run, BINILOAD continues the load run normally. If, however, a private hash routine is required, BINILOAD terminates, the database is not yet destroyed. In other words if no private hash routine is required then they do not have to be available; if, however, only one routine is required, then all the routines must be available.

Response
In the event the BINILOAD run is aborted, enter the missing hash routines in the module library
dbname. HASHLIB, then restart BINILOAD.

Note
If the module library dbname. HASHLIB contains a connection module UDSHASH which does not originate from the BGSIA run for setting up this database, but was copied from another HASHLIB, it cannot be taken for granted that all user-own hash routines defined in the DDL are really loaded, even if the above message fails to appear. In such a case the calling of a non-existent user-own hash routine would result in an uncontrolled abortion of the BINILOAD run with paging error.

0607

NO IS BEFORE INT. OR CHAR. CONSTANT

Meaning
Instead of IS or integer the statement contains an incorrect keyword in this place.

Response
None.
(It can be expected that a further error message will be given with regard to the same statement).

0609

EXPECTED RESERVED WORD IS NOT keyword
DEFAULT VALUE IS ASSUMED

Relevant statement:

EXECUTION { WITH | WITHOUT } CHECK
or
RUN { WITH | WITHOUT } EFFICIENT IO

Meaning
The mandatory keyword keyword was expected here.
The keyword may contain the following values:
CHECK
EFFICIENT
IO
WITH
WITHOUT

Response
WITH is the default value. If the default value is not desired, the statement must be corrected.
In the interactive mode, the statement can be immediately corrected by reentering the complete statement, after which the BINILOAD run is continued normally.
If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0611

SORTCORE INTEGER VALUE IS INVALID
DEFAULT VALUE = 150 IS ASSUMED

Relevant statement:
SORTCORE IS integer

Meaning
The number specified was outside the permissible range of values.

Response
If the default value of 150 is not desired, the statement must be corrected.
In the interactive mode, the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally.
If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0612

LENGTH FIELD IS INVALID IN LINE line-number


Meaning
Length field of variable-length item has incorrect value in the line line-number and the line will be skipped.

Response
None.

0613

LENGTH FIELD IS INVALID IN LINE line-number, FIELD NAME: field-name, VALUE: value


Meaning
Length field of variable-length item in the CSV input file has incorrect value in the line line-number and the line will be skipped.

Response
None.

0614

ITEM item-name OF UNKNOWN ITEM TYPE IN RECORD record-name

Meaning
Warning:
Self-explanatory

0615

INCORRECT VALUE. LINE NUMBER line-number, FIELD-NAME: field-name. ERROR TYPE: error-type

Meaning

Warning:

Value for the specified item isn't correct. Value will be modified (truncated) according to the data type of the field.

• if value is of BINARY15 / 31 / 63 and contains a decimal point, the part after the decimal point will be truncated;
• if value is of decimal/unpacked numeric data type and contains too many fractional digits, value will be truncated according to the datatype of the field.
• if value is of alphanumeric data type and bigger then maximum length, value will be truncated to the maximum length defined for the field.

Response
None.

0701

NON-EXISTING SCHEMA SPECIFIED

Relevant statement:
SCHEMA schemaname

Meaning
The statement was syntactically correct, but an invalid schema name was entered.

Response
BINILOAD terminates abnormally immediately thereafter. The database remains unchanged.
Restart BINILOAD and then enter correct statement.

0702

NO SUBSCHEMA SPECIFIED

Relevant statement:
SUBSCHEMA subschemaname

Meaning
The statement was either not entered at all or its syntax was incorrect.

Response
BINILOAD terminates abnormally immediately thereafter. The database remains unchanged.
Restart BINILOAD and then enter correct statement.

0703

NON-EXISTING SUBSCHEMA SPECIFIED

Relevant statement:
SUBSCHEMA subschemaname

Meaning
The statement was entered with the correct syntax but an invalid subschema name was given.

Response
BINILOAD terminates abnormally immediately thereafter. The database remains unchanged.
Restart BINILOAD and then enter correct statement.

0705

AREA realmname INVOLVED IN UTILITYLOCK

Meaning
A previous BMEND run involving this realm was interrupted.

Response
Ensure that the realm is in the correct closed state and then restart BINILOAD.

0706

AREA realmname INVOLVED IN SYSTEMBREAK

Meaning
In the indicated user realm, the system break bit was already set prior to this BINILOAD run (while the system break bit was not set in the database directory).
The affected database is inconsistent.

Response
Determine reason for inconsistency with the aid of logs taken during previous processing.
Make state of database consistent; then restart BINILOAD.

0707

DATABASE INCONSISTENT;
AREA: realmname

Meaning
In the indicated user realm, the backup data or the version number does not match the associated entry in the database directory, or the indicated user realm is not compatible with the allocated database directory, or AK0 and AKN differ.

Response
Determine reason for inconsistency of database with the aid of logs taken during previous processing.
Make state of database consistent; then restart BINILOAD.

0711

NOT ENOUGH SPACE ON PUBLIC VOLUMES
FOR FILE LINK = SORTWK

Meaning
No sort file with LINK-NAME=SORTWK was opened; there was not enough space on public disk for the sort file to be set up internally by BINILOAD with SPACE = (120,120).

Response
Either create space by deleting other files or set up the sort file on private disk; then restart BINILOAD (the database is still undestroyed).

0712

NOT ENOUGH SPACE ON PUBLIC VOLUMES FOR
FILE LINK = SCRTCH1

Meaning
No scratch file with LINK-NAME=SCRTCH1 was opened. There was not enough space on the public disk for the scratch file to be set up internally by BINILOAD with SPACE = (9,9) or SPACE = (135,135) when using high-efficiency I/O.

Response
Either create space by deleting other files or set up the sort file on private disk; then restart BINILOAD (the database is still unchanged).

0715

INPUT FILE NAME EXPECTED AS LITERAL

Relevant statement:
INPUT FILE ’input-filename’

Meaning
The input file name must be enclosed in apostrophes. If this name contains one or more periods, message 0809 is output as a continuation error.

Response
In the interactive mode the statement can be immediately corrected by reentering the complete statement, after which the BINILOAD run is continued normally.
If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0716

INPUT-FILENAME NOT GIVEN

Relevant statement:
INPUT FILE ’input-filename’

Meaning
The statement was either not entered at all or its syntax was incorrect.

Response
BINILOAD terminates abnormally immediately thereafter. The database remains unchanged.
Restart BINILOAD and then enter correct statement.

0717

OPEN OF INPUT-FILE IMPOSSIBLE WITH DMS-CODE dmscode FOR FILE input-filename

Relevant statements:
INPUT FILE ’input-filename’
USER FILE RECORD LENGTH IS integer

Meaning
The specified input file cannot be opened; the file name and the specific DMS code are output.

Response
Look up DMS code or request it using the /HELP-MSG command; eliminate error; then restart BINILOAD (the database remains unchanged).

0718

USER-INPUT-RECORD CANNOT BE READ, DMS-CODE = dmscode

Relevant statements:
INPUT FILE ’input-filename’
USER FILE RECORD LENGTH IS integer

Meaning
When reading a record from the input file an error occurred; the specific DMS code is output.

Response
If the error has not occurred during the check run, the database is destroyed and must be reset; after correction of the input file restart BINILOAD.

0720

FSTAT-ERROR AT filename
ERR-CODE: errcode ERRBYTE: errbyte

Meaning
FSTAT error. The cause of the error can be obtained from the indicated error code and error byte. BINILOAD is terminated abnormally.

Response
Restart BINILOAD using correct input file.

0721

EMPTY INPUT FILE filename

Meaning
Self-explanatory.

Response
BINILOAD terminates abnormally. The database is unaffected. Restart BINILOAD using correct input file.

0722

line-name LINE IS NOT FOUND IN CSV FILE

Meaning
Header line or content lines is not found in CSV file.

Response
Check and correct the CSV file and rerun BINILOAD.

0723

ERROR DURING READ OF CSV LINE: line-number , ERROR: error-type

Meaning

CSV line has incorrect syntax.

Possible error types:

• DOUBLE QUOTE CHARACTER IS NOT DUPLICATED

Response

Check and correct the value in the line where error occurred, delete all records of the specified record

types from the database using BOUTLOAD (REMOVE-RECORD statement) and rerun BINILOAD.

0724

CSV INPUT FILE WITH FIXED-LENGTH RECORDS IS NOT SUPPORTED. CSV FILE NAME file-name

Meaning

CSV input file should variable-length file with maximal length of 32752 bytes

Response

Check and correct the input CSV file format

0801

FILLING INTEGER INVALID

Relevant statement:
FILLING IS integer

Meaning
For integer a 0 or a value > 100 was specified. If the default value of 100 is not desired, the statement must be corrected.

Response
In interactive mode, the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0804

NO NAME SPECIFIED

Meaning
This statement contains a syntactical error; the name to be specified cannot be interpreted.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0805

NO RESERVED WORD SPECIFIED AFTER keyword

Meaning
A further keyword was expected after the input of keyword.

Response
In the interactive mode, the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

keyword may contain the following values:

,

Meaning
A keyword is expected after the comma.

INSERT

Relevant statement:
INSERT INTO SET setname

Meaning 
SET is a mandatory keyword in the statement, but no keyword was specified after INSERT.

INTO

Relevant statement:
INSERT INTO SET setname

Meaning 
SET is a mandatory keyword in the statement, but no keyword was specified after INTO.

ORDER

Relevant statement:
SET ORDER ...

Meaning 
USING or VIA is expected here.

RECORD-DBKEY

Relevant statement:
RECORD-DBKEY IS DISPL IS integer

Meaning 
IS or DISPL is expected after RECORD-DBKEY.

RECORD-RSQ

Relevant statement:
RECORD-RSQ IS DISPL IS integer

Meaning 
IS or DISPL is expected after RECORD-RSQ.

STORE

Relevant statement:
STORE RECORD recordname

Meaning 
No keyword was entered after STORE.

0807

EXPECTED RESERVED WORD IS NOT keyword

Meaning
Input of the mandatory keyword keyword is expected here.

Response
In the interactive mode, the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

keyword may contain the following values:

AREA

Relevant statement:
OWNER CALCKEY ..., AREA realmname

Meaning 
Only the mandatory keyword AREA is permitted here.

CALCKEY, DBKEY, RSQ, SEARCHKEY OR KEY

Meaning 
An invalid keyword was entered for the type of OWNER selection.

COLUMN-NR OR ORDER-NR

Relevant statement:
OWNER SEARCHKEY ...

Meaning 
The input of either COLUMN-NR or ORDER-NR is expected here.

DISPL OR VALUE

Meaning 
The input of either DISPL or VALUE is expected here.

DISPL

Relevant statements:
SET ORDER USING DISPL IS integer, LENGTH IS integer
OWNER KEY DISPL IS integer, LENGTH IS 1

Meaning 
Only the mandatory keyword DISPL is permitted here.

FILE OR RECORDNUMBER

Relevant statements:
INPUT FILE ’input-filename’
INPUT RECORDNUMBER IS integer

Meaning 
Only the keywords FILE or RECORDNUMBER are permitted after the initial keyword INPUT.

FILE

Relevant statement:
SET ORDER VIA USER FILE SEQUENCE

Meaning 
Only the mandatory keyword FILE is permitted here.

LENGTH

Meaning 
Input of the mandatory keyword LENGTH is expected here.

ORDER

Relevant statement:
SET ORDER ...

Meaning 
Only the keyword ORDER is permitted after the initial keyword SET.

RECORD

Relevant statement:
STORE RECORD recordname

Meaning 
RECORD is a mandatory keyword in the statement, but no keyword was specified after STORE.

SEQUENCE

Relevant statement:
SET ORDER VIA USER FILE SEQUENCE

Meaning 
Only the mandatory keyword SEQUENCE is permitted here.

SET

Relevant statement:
INSERT INTO SET setname

Meaning
SET is a mandatory keyword in the statement, but no keyword was specified after INSERT or INTO.

USER

Relevant statement:
SET ORDER VIA USER FILE SEQUENCE

Meaning 
Only the mandatory keyword USER is permitted here.

VIA OR USING

Relevant statement:
SET ORDER ...

Meaning 
Input of either VIA or USING is expected here.

VIA, COLUMN-NR OR ORDER-NR

Relevant statement:
OWNER SEARCHKEY ...

Meaning
If the set for the OWNER selection is an explicit singular set, the mandatory keyword VIA is required here. If the set is an implicit set, either the mandatory keyword COLUMN-NR or ORDER-NR is required, since the VIA SET... specification is not allowed in this case.

0809

MAJOR KEYWORD NOT DETECTED

Meaning
At this point the entry of a new statement beginning with a begin keyword is expected. This message can under certain circumstances result from a continuation error originating in a previous incorrect statement (cf. 0715, for example).

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run continues normally. If the error occurs in batch mode, BINILOAD must be restarted using the correct statement.

0810

NO IS BEFORE INTEGER OR CHAR. CONSTANT

Meaning
After the keyword VALUE, an identifier was specified which is, however, not equal to the only option possible at this point, namely the keyword IS; possibly the apostrophes required for the specification of the literal have been omitted.

Response
In the interactive mode the statement can be immediately corrected by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0811

DELIMITER EXPECTED

Meaning
Input of a delimiter (comma or colon) must be entered here.

Response
In the interactive mode the statement can be immediately corrected by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0812

THE EXPECTED DELIMITER IS NOT A COMMA

Meaning
Input of a comma was expected as a delimiter here.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0816

NO LITERAL AFTER VALUE SPECIFIED

Relevant statement:
RECORD-DISPL integer, VALUE literal

Meaning
After the mandatory keyword VALUE, input of a literal (character constant or hexadecimal constant) was expected.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0817

NO TYPE AFTER OWNER SPECIFIED

Meaning
After the keyword OWNER a further keyword for the type of OWNER selection was expected (CALCKEY, SEARCHKEY, DBKEY, KEY).

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0819

NO RESERVED WORD AFTER OWNER TYPE

Meaning
After the correct specification of the type of owner selection, a further mandatory keyword is expected (DISPL or VALUE).

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0821

NO INTEGER OR CHAR. CONSTANT SPECIFIED

Meaning
At this point a figure is expected.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0830

RECORD-DBKEY LENGTH IS INVALID

Relevant statement:
RECORD-DBKEY IS DISPL IS integer,[LENGTH IS 4].

Meaning
The specified DB key length is incorrect.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run continues normally. If the error occurs in batch mode, BINILOAD must be restarted using the correct statement.

0833

COLUMN-NR integer INVALID (< 1 OR > 255)

Relevant statement:
OWNER SEARCHKEY ..., COLUMN-NR integer

Meaning
The DBTT-COLUMN-NR specified for the sort key/search key table for owner selection is outside its normal range of values.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0834

SPEC. LENGTH OR LITER LENGTH IS INVALID

Relevant statement:
Statement with specification
DISPL integer, LENTH integer
or
VALUE ’literal ’

Meaning
The length specified for the item from the input record is invalid, or the literal has the length 0.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued.
If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0835

INCORRECT RECORD REFERENCE NUMBER

Relevant statement:
OWNER DBKEY VALUE recref:page-number

Meaning
The recref specified for dbkey is either

1. syntactically incorrect (< 1 or > number of records of the SIA) or

2. not the REC-REF of the OWNER record type of the set to be inserted.

Response

1. In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

2. BINILOAD aborts immediately thereafter. The database remains unchanged. Restart BINILOAD, then enter correct statement.

0836

THE EXPECTED DELIMITER IS NOT :

Relevant statement:
OWNER DBKEY VALUE recref:page-number

Meaning
At this point a colon is expected as a delimiter between recref and page-number (RSQ) in dbkey.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0837

NO INTEGER HAS BEEN SPECIFIED AFTER :

Relevant statement:
OWNER DBKEY VALUE recref:page-number

Meaning
No number was entered for page-number (RSQ) after the colon.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0838

NO PREVIOUS INSERT STATEMENT SPECIFIED

Relevant statements:
SET ORDER ...
OWNER ...

Meaning
No INSERT statement for the associated set was entered prior to the indicated statement.

Response
Enter INSERT statement first, followed by indicated statements.

0839

AREA IN WHICH RECORD MUST BE STORED NOT SPEC.

Relevant statement:
RECORD -AREA realmname

Meaning
The WITHIN clause (DDL) for the record type to be stored contains more than one realm name.
However no RECORD-AREA statement has been entered.

Response
BINILOAD terminates abnormally immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement.

0840

OWNER SEARCHKEY NOT IN SINGULAR SET
SING SET: setname

Relevant statements:
INSERT SET setname
OWNER SEARCHKEY ..., VIA SET setname

Meaning
The set specified for owner selection in the VIA clause is not singular. The specified set name is output.

Response
BINILOAD terminates abnormally directly thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement.

0841

OWNER CALCKEY NOT FOUND
KEY: key

Relevant statement:
OWNER CALCKEY ...

Meaning
The item specified as the owner CALC key in a record of the input file or in the VALUE clause contains a CALC KEY which is not found in the database. The erroneous CALC KEY is output.
The message appears only once for every incorrect key value, even if it recurs in the input file for owner selection.
The name of the associated set to be inserted is output in the BINILOAD runtime log immediately before this.
If the check run is selected, all incorrect owner keys are detected and the run is aborted, the database remaining unchanged.
If the check run was not selected, the run is cancelled right after the first incorrect owner key and the database is destroyed.

Response
The column area for the item in the input record is taken from the owner statement.
If this area has been defined correctly, the corresponding input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).
The input file or the literal in the VALUE clause must be corrected.
If the check run is not selected, the database must be reset to a consistent state existing prior to this BINILOAD run.

0842

OWNER SEARCHKEY NOT FOUND
KEY: key

Relevant statement:
OWNER SEARCHKEY ...

Meaning
The item specified as the owner search key in a record of the input file or in the VALUE clause contains a search key which is not found in the database. The erroneous search key is output.
The message appears only once for every incorrect key value, even if it recurs in the input file.
The name of the associated set to be inserted is output in the BINILOAD runtime log immediately before this.
If the check run is selected, all incorrect owner keys are detected and the run is aborted, the database remaining unchanged.
If the check run was not selected, the run is cancelled right after the first incorrect owner key and the database is destroyed.

Response
The column area for the item in the input record is taken from the owner statement.
If this area has been defined correctly, the corresponding input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).
The input file or the literal in the VALUE clause must be corrected.
If the check run is not selected, the database must be reset to a consistent state prior to this BINILOAD run.

0843

TOO MANY USER RECORDS (DBTT FULL)

Meaning
The existing DBTT is too small for the number of input records.
This message appears only if the check run has not been selected; BINILOAD aborts immediately thereafter and the database is destroyed.

Response
The database must be reset, after which the still existing empty DBTT entries can be determined with the aid of the utility routine BSTATUS. The DBTT is then enlarged using BREORG, according to the number of input records; then restart BINILOAD.

0845

NO STORE RECORD STATEMENT INCLUDED

Relevant statement:
STORE RECORD recordname

Meaning
The statement was either not entered at all or its syntax is incorrect.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0846

RECORD NAME DOES NOT EXIST IN SCHEMA
RECORD NAME: recordname

Relevant statement:
STORE RECORD recordname

Meaning
The specified record name is not found in the schema of the database.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0847

SET NAME DOES NOT EXIST IN SCHEMA
SET NAME: setname

Relevant statements:
INSERT INTO SET setname
OWNER SEARCHKEY ...,
VIA SET setname, ...

Meaning
The specified set name is not found in the schema of the database.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0848

AREA NAME DOES NOT EXIST IN SCHEMA
AREA NAME: realmname

Relevant statements:
RECORD-AREA realmname
OWNER CALKEY ..., AREA realmname

Meaning
The specified realm name is not found in the schema of the database.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0849

SET DOES NOT EXIST IN SUBSCHEMA
SET NAME: setname

Relevant statements:
INSERT INTO SET setname
OWNER SEARCHKEY ...,
VIA SET setname, ...

Meaning
The specified set name is not found in the specified subschema.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0850

INPUT RECORD LENGTH NOT EQUAL DATABASE RECORD LENGTH PERHAPS: RECORD-DISPL STATEMENT MISSING

Relevant statements:
USER FILE RECORD LENGTH integer
RECORD-DISPL integer, DISPL integer, LENGTH integer

Meaning
No RECORD-DISPL statement was given. BINILOAD assumes that the length of the input record and the length of the user part of the database record are the same - this is, however, not the case.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0851

RECORD DOES NOT EXIST WITHIN SPECIFIED AREA

Relevant statements:
STORE RECORD recordname
RECORD AREA realmname

Meaning
The specified realm is not contained in the WITHIN clause (DDL) for the record type to be stored.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0852

RECORD NOT MEMBER OF SPECIFIED SET

Relevant statements:
STORE RECORD recordname
INSERT SET setname

Meaning
The record type to be stored is not a member of the specified set to be inserted.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0853

DATABASE IS INCONSISTENT

Meaning
The specified database is inconsistent.

Response
Determine reason for the inconsistency using the logs taken during previous processing.
Make state of database consistent; then restart BINILOAD.

0854

INVALID DISPL OR LENGTH FIELD IN RECORD-DISPL STATEMENT
RECORD-DISPL NR. displ-number

Relevant statements:
USER FILE RECORD LENGTH integer
RECORD-DISPL integer, DISPL integer, LENGTH integer

Meaning
The receive item (RECORD-DISPL, LENGTH) does not fit into the DB record or the send item (DISPL, LENGTH) does not fit into the input record.
The displ-number output indicates the specific RECORD-DISPL statement.

Response
BINILOAD aborts immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement.

0855

OWNER DBKEY INVALID
SET NAME: setname

Relevant statement:
OWNER DBKEY IS VALUE dbkey

Meaning
The RSQ specified in dbkey is too high (i.e. not contained in the existing DBTT).

Response
Correct indicated database key.

0855

OWNER DBKEY INVALID
OWNER DATABASE KEY: dbkey

Relevant statement:
OWNER DBKEY ...

Meaning
The item specified as the owner DB key in a record of the input file or in the VALUE clause contains a DB key which is not found in the database. The erroneous DB KEY is output.
The message appears only once for every incorrect key value for owner selection, even if it recurs in several records of the input file.
The name of the associated set to be inserted is output in the BINILOAD runtime log immediately before this.
If the check run is selected, all incorrect owner keys are detected and the run is aborted, the database remaining unchanged.
If the check run is not selected, the run is aborted following the first incorrect owner key and the database is destroyed.

Response
The column area for the item in the input record is taken from the owner statement.
If this area has been defined correctly, the corresponding input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).
The input file or the literal in the VALUE clause must be corrected.
If the check run is not selected, the database must be reset to a consistent state existing prior to this BINILOAD run.

0856

FILLING PERCENTAGE TOO SMALL

Relevant statement:
FILLING IS integer PERCENT

Meaning
If integer < 100, even pages for which LIST RECORDS has been defined are only partially filled (as level-0 pages of a table); the indicated value of integer is so low that even a single LIST RECORD no longer fits in a page.

Response
BINILOAD aborts immediately thereafter. The database remains unchanged. Restart BINILOAD, then enter the correct statement.

0857

OWNER OF INSERT SET NOT MEMBER OF SPEC. SINGULAR SET
SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER SEARCHKEY ..., VIA SET setname

Meaning
The owner record of the set to be inserted is not a member record of the singular set specified for owner selection.

Response
BINILOAD aborts immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement.

0858

COLUMN-NR NOT PRESENT IN SCHEMA
SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER SEARCHKEY ..., VIA SET setname

Meaning
The specified DBTT-COLUMN-NR belonging to the sort key/search key table in the specified singular set is not found in the schema.

Response
BINILOAD aborts immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement.

0859

OWNER SEARCHKEY LENGTH INVALID

Relevant statements:
INSERT SET setname
OWNER SEARCHKEY ..., VIA SET setname

Meaning
The specified length of the item to be used for owner selection does not match the length of the key as defined in the schema.

Response
BINILOAD aborts immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement.

0861

AUTOMATIC SET NOT PRESENT
SET NAME: setname

Relevant statement:
INSERT SET setname

Meaning
No INSERT statement was specified for the AUTOMATIC set which was output.

Response
BINILOAD aborts immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter the correct statement.

0862

SET ORDER STATEMENT SPECIFIED FOR A SORTED SET
SET NAME: setname

Relevant statements:
INSERT SET setname
SET ORDER ...

Meaning
The SET ORDER statement is only permitted for the set to be inserted together with the ORDER clause (DDL): ORDER IS FIRST/LAST/NEXT/PRIOR/IMMATERIAL BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0863

OWNER SYMBOLIC OUTSIDE BOUNDS OF USER RECORD
SET NAME: setname

Relevant statements:
OWNER { CALCKEY | SEARCHKEY | DBKEY | KEY } DISPL integer, LENGTH integer, ...

Meaning
The specified item (DISPL, LENGTH) to be used for owner selection is outside of the input record.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0864

OWNER SYMBOLIC SPECIFIED FOR A SINGULAR SET
SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER { CALCKEY | SEARCHKEY | DBKEY }...

Meaning
Owner selection in this way is only useful in the case of non-singular sets, the specified set to be inserted, is, however, singular.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0865

OWNER CALCKEY SPEC., BUT OWNER NOT LOCATED BY CALC

Relevant statements:
INSERT SET setname
OWNER CALCKEY ...

Meaning
The owner record type of the set to be inserted does not have the LOCATION MODE IS CALC clause in the DDL, for that reason owner selection via a CALC key is not possible, only the specification DBKEY or SEARCHKEY can be used, the latter only if the owner
record type is a member in a singular set. BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0866

OWNER CALCKEY NOT WITHIN SPECIFIED AREA
SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER CALCKEY ..., AREA realmname

Meaning
The specified realm does not contain any CALC blocks, i.e. the realm is not referred in the POPULATION clause (SSL) and not in the WITHIN clause (DDL) for the owner record type.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0867

AREA NAME IN OWNER CALCKEY STATEMENT NOT SPECIFIED
SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER CALCKEY ..., AREA realmname

Meaning
For the statement OWNER CALCKEY...,AREA realmname the realm entry is missing and the CALC blocks for the owner record type are spread over more than one realm. For this reason one of these realms must be specified in this case.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0868

OWNER CALCKEY ITEM LENGTH INVALID
SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER CALCKEY ..., AREA realmname

Meaning
The specified length of the item to be used for owner selection does not match the length of the key as defined in the schema.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0869

SET ORDER ITEM OUTSIDE BOUNDS OF USER RECORD
SET NAME: setname

Relevant statements:
USER FILE RECORD LENGTH integer
INSERT SET setname
SET ORDER USING DISPL integer, LENGTH integer

Meaning
The item defined as the sort criterion (DISPL, LENGTH) is located outside of the input record.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0870

OWNER KEY SPECIFICATION NOT ALLOWED FOR AUTOMATIC SING.
SET SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER KEY DISPL integer, LENGTH 1

Meaning
The owner statement with the KEY specification is only permitted for a singular MANUAL set or an OPTIONAL set and in that case sets a flag byte in the input record for inserting or not inserting the associated DB record. A singular MANDATORY AUTOMATIC set is specified using an INSERT statement without subsequent owner statement.
BINILOAD aborts immediately afterwards. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0871

OWNER OF SET IS NOT SYSTEM
SET NAME: setname

Relevant statements:
INSERT SET setname
OWNER { CALCKEY | SEARCHKEY | DBKEY }...

Meaning
The set to be inserted is not singular, however no statement for owner selection was specified.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0872

USER FILE RECORD LENGTH NOT SPECIFIED

Relevant statement:
USER FILE RECORD LENGTH integer

Meaning
This statement was either not entered at all or its syntax is incorrect.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0873

USER FILE BUFFER LENGTH NOT SPECIFIED

Relevant statement:
USER FILE BUFFER LENGTH integer

Meaning
This statement was either not entered at all or its syntax is incorrect.

Note
The specified buffer length is not evaluated in BS2000; the statement is nevertheless mandatory (compatibility with BS1000).
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0874

USER FILE BUFFER LENGTH IS NOT A MULTIPLE OF RECORD LENGTH

Relevant statements:
USER FILE RECORD LENGTH integer
USER FILE BUFFER LENGTH integer

Meaning
In BS1000 the buffer length must be a multiple of the length of the input record, a check on this is also performed in BS2000.

Note
The specified buffer length is not evaluated in BS2000; the statement is nevertheless mandatory (compatibility to BS1000).
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0876

RECORD DOES NOT EXIST IN SUBSCHEMA
RECORD NAME: recordname

Relevant statements:
SUBSCHEMA subschemaname
STORE RECORD recordname

Meaning
The record type to be stored is not found in the specified subschema, the record name or the subschema name must be corrected.
BINILOAD aborts immediately thereafter. The database remains unchanged.

Response
Restart BINILOAD, then enter correct statement.

0877

WRONG RECORD REFERENCE NUMBER
RECORD-DBKEY:dbkey

Relevant statement:
RECORD-DBKEY ...

Meaning
The item specified for the RECORD-DBKEY in a record of the input file contains a DB key with an incorrect REC-REF. The incorrect DB key is output.

Response
Correct the input file. If no test run has been specified, the database must be reset to its consistent state prior to the BINILOAD run.

0879

DBTT TOO SMALL. REORGANIZE DATABASE. MODIFY-RECORD-POPULATION recordname,
DIFFERENCE = n

Meaning
The existing DBTT is too small for the number of input records; n indicates the number of required empty DBTT entries. This message is output only if the check run was selected.

Response
After the check run the database is still unchanged. The size of the DBTT can be increased immediately using the utility routine BREORG.

0880

AREA TOO SMALL. REORGANIZE DATABASE. MODIFY-REALM-SIZE realmname, DIFFERENCE = n

Meaning
In the realm realmname, n more empty pages are required for accommodating the records and/or tables. This message is output only if the check run was selected.

Response
If SECONDARY_ALLOCATION = 0 is set for the realm concerned, the BINILOAD run is aborted with an unchanged database after the test run has been completed. Realm extension can be performed immediately with the BREORG utility routine.
(Note: If the DBTT also needs to be extended, the associated realm must also be extended by the pages required for this purpose.)
If SECONDARY_ALLOCATION > 0 is set for the realm concerned, the BINILOAD run is not aborted after the test run owing to a lack of free space required for this urpose.
Instead, the free space required is obtained automatically by means of automatic realm extension as the procedure continues.

0881

LIST TABLE NOT EMPTY
OWNER KEY : key (IF PRESENT)
OWNER DATABASE KEY : dbkey
OWNER ACTUAL KEY : actkey

Relevant statements:
INSERT SET setname
OWNER ..

Meaning 
The set to be inserted is a LIST set and the set occurrence, selected via the owner for inserting the new DB record(s) is not empty. However, to LIST sets only completely new set occurrences can be added with BINILOAD. If new DB records are to be inserted into an existing set occurrence which is not empty, this must be performed by way of an application program with the DBH.
The message appears only once for every incorrect key value for owner selection even if it recurs in several records of the input file.
The name of the associated set to be inserted is output in the BINILOAD runtime log immediately before this.
If the check run is selected, all incorrect owner keys are determined and the run is aborted, the database remaining unchanged.
If the check run is not selected, the run is aborted following the first incorrect owner key and the database is destroyed.

Response 
The column area for the item in the input record is taken from the owner statement.
If this area has been defined correctly, the corresponding input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).
The input file or the literal in the VALUE clause must be corrected.
If the check run is not selected, the database must be reset to a consistent state existing prior to this BINILOAD run.
Note
This error can also occur in the case of a singular LIST set.

0882

A KEY-ITEM IS NOT DECLARED IN SUBSCHEMA

Meaning
A key item of the combined record key has not been declared in the subschema.

Response
Declare key item in the subschema; restart BINILOAD.

0884

^{DBKEY / RSQ FOR OWNER ISN'T SPECIFIED IN CSV FILE, SET_NAME: set-name}

Meaning
DBKEY or  RSQ for Owner is missed in CSV file

Response
Correct CSV file and rerun BINILOAD.

0890

SPECIFIED AREA IS TEMPORARY

Relevant statements:
RECORD-AREA realmname
OWNER CALCKEY ..., AREA realmname

Meaning
The realm specified is temporary.

Response
BINILOAD terminates abnormally immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement.

0891

MORE THAN 5 RECORD-DISPL STATEMENTS WITH VALUE SPECIFIED

Relevant statement:
RECORD-DISPL integer, VALUE literal

Meaning
While BINILOAD can process any number of RECORD-DISPL statements with the specification (DISPL, LENGTH), it can only process up to 5 statements with the specification VALUE.

Response
BINILOAD aborts immediately thereafter. The database remains unchanged.
Restart BINILOAD, then enter correct statement, trying to reduce the number of statements affected by combining them.

0892

OWNER RECORD HAS NO SEARCHKEY
RECORD NAME: recordname

Relevant statements:
INSERT setname
OWNER SEARCHKEY ...

Meaning
The OWNER SEARCHKEY statement has been entered without specifying an explicitly singular set VIA SET setname ; in this case BINILOAD assumes that owner selection is to be via an implicit set (search key of owner record); no search key has been defined on record level for the owner record type in the DDL however.

Response
Repeat OWNER SEARCHKEY statement using the entry VIA SET...

0893

ORDER-NR integer INVALID (< 1 or > 255)

Relevant statement:
OWNER SEARCHKEY ..., ORDER-NR integer

Meaning
The ORDER NR. specified for the sort key/search key table to be used for owner selection is not within the permitted range of values.

Response
In the interactive mode the statement can be corrected immediately by reentering the complete statement, after which the BINILOAD run is continued normally. If the error occurred in batch mode, BINILOAD must be restarted using the correct statement.

0894

ORDER-NR IS NOT POSSIBLE FOR SET
SET NAME setname

Relevant statement:
OWNER SEARCHKEY ..., ORDER-NR integer

Meaning
The ORDER-NR. for a set counts all keys in this set definition (DDL), inclusive of the CALC keys. Too large an ORDER-NR was entered in the specified singular set to be used for owner selection.

Response
Correct the ORDER-NR.

0895

OWNER KEY NOT LOW-VALUE OR HIGH-VALUE
KEY: key

Relevant statements:
INSERT SET setname
OWNER KEY DISPL integer, LENGTH 1

Meaning
The specified flag byte contains neither X’00’ (LOW-VALUE for insertion) nor X’FF’ (HIGH-VALUE for non-insertion); the contents of the flag byte are output.

Response
The column area for the item in the input record is taken from the OWNER statement.
If the column area was defined correctly, the concerned input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).
The input file or the literal in the VALUE clause must be corrected.
If the check run was not selected, the database must be reset to a consistent state existing prior to the BINILOAD run.

0896

OWNER CALC SEARCH KEY NOT FOUND

Relevant statement:
OWNER SEARCHKEY ...

Meaning
The item specified as the owner search key in a record of the input file or in the VALUE clause contains a search key which is not found in the database. The erroneous search key is output.
The message appears only once for every incorrect key value for owner selection even if it recurs in several records of the input file.
The name of the associated set to be inserted is output in the BINILOAD runtime log immediately before this.
If the check run is selected, all incorrect owner keys are detected and the run is aborted, the database remaining unchanged.
If the check run is not selected, the run is aborted following the first incorrect owner key and the database is destroyed.

Response

The column area for the item in the input record is taken from the owner statement.

If this area has been defined correctly, the corresponding input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).

The input file or the literal in the VALUE clause must be corrected.

If the check run is not selected, the database must be reset to a consistent state existing prior to this BINILOAD run.

0897

OWNER OF LIST SET NOT IN RECORD-AREA
OWNER KEY           : key             (IF PRESENT)
OWNER DATABASE KEY  : dbkey
OWNER ACTUAL KEY    : actkey

Relevant statements:
RECORD-AREA realmname
INSERT SET setname
OWNER ...

Meaning 
The INSERT set is a LIST set which was specified differently in the SSL than with DETACHED WITHIN realmname. The AREA lists for the owner and member record types in the DDL (the two must then be identical) contain more than one realm. In this case all owner occurrences which have been selected must also be in the specified record area of the specific BINILOAD run.

Response 
The column area for the item in the input record is taken from the OWNER statement.
If the column area has been defined correctly, the concerned input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).
The input file or the literal in the VALUE clause must be corrected.
If the check run was not selected, the database must be reset to a consistent state existing prior to this BINILOAD run.

0898

OWNER OF PLOP SET NOT IN RECORD-AREA
OWNER KEY           : key                (IF PRESENT)
OWNER DATABASE KEY  : dbkey
OWNER ACTUAL KEY    : actkey

Relevant statements:
RECORD-AREA realmname l
INSERT SET setname

Meaning 
For a set with PLACEMENT OPTIMIZATION, the same applies as for 0897.

Response 
The column area for the item in the input record is taken from the OWNER statement.
If the column area has been defined correctly, the concerned input records can be determined with the aid of the incorrect key value which is output (the easiest way to do this is by using EDT, if possible).
The input file or the literal in the VALUE clause must be corrected.
If the check run was not selected, the database must be reset to a consistent state existing prior to this BINILOAD run.

0899

OWNER KEY HIGH VALUE FOR A MANDATORY AUTOMATIC SET

Relevant statements:
INSERT SET setname
OWNER { CALCKEY | SEARCHKEY | DBKEY }...

Meaning
The indicated set is a non-singular MANDATORY AUTOMATIC set and the item in the input record to be used for owner selection contains X’FF...FF’ (HIGH-VALUE for non-insertion);
this is, however, only possible in the case of a MANUAL or an OPTIONAL set.
The name of the associated set to be inserted is output in the BINILOAD runtime log immediately before this.
If the check run is selected, the run is aborted with the database unchanged.
If the check run is not selected, the run is aborted and the database destroyed.

Response
The column area for the item in the input record is taken from the owner statement.
If this area has been defined correctly, the corresponding input records can be determined with the aid of the owner selection item which is output (the easiest way to do this is by using EDT, if possible).
The input file must be corrected.
If the check run is not selected, the database must then be reset to a consistent state existing prior to this BINILOAD run.

0900

OWNER DBKEY POSSIBLY INVALID, SIA NOT UP TO DATE
OSET NAME : setname

Relevant statements:
OWNER DBKEY IS VALUE dbkey

Meaning
The RSQ specified in dbkey is too large (i.e. not present in the available DBTT). However, since the SIA used for validation may be out-of-date, the problem may very occasionally be due to the fact that a completed online DBTT extension has not yet been recorded in the SIA.

Response
Correct the input or make sure the SIA is updated (connect the DB in an update DBH session).

0901

LISTREALM OF A DISTRIBUTABLE LISTSET NOT SPECIFIED
RECORD NAME: recordname

Meaning
The record type recordname is a member of a distributable LIST set.
Not all list realms are defined in the specified subschema.
BINILOAD terminates abnormally and the database is unchanged.

Response
Correct the subschema and rerun BINILOAD.

0902

OWNER RECORD NOT SPECIFIED
RECORD NAME: recordname

Meaning
The record type to be loaded must be inserted in a set (INSERT statement). The associated owner record type is not defined in the specified subschema. BINILOAD terminates abnormally and the database is unchanged.

Response
Correct the subschema and rerun BINILOAD.

0903

SPECIFIED REALM UNEQUAL TO TABLE AREA OF A DISTRUBUTABLE LISTSET

Statements affected:
RECORD-AREA realmname

Meaning
The record type to be loaded is the member record type of a distributable list. The realm specified is not the table realm. BINILOAD terminates abnormally and the database is unchanged.

Response
Specify the table realm of the distributable LIST set in the RECORD-AREA statement.

0904

WRONG AREA IN OWNER CALCKEY STATEMENT

Statements affected:
INSERT SET setname
OWNER CALCKEY ...

Meaning
The record type to be loaded is inserted in a set whose owner is selected by means of a CALC key. The owner record type is the member record type of a distributable list. In the OWNER CALCKEY statement the table realm is not specified under AREA NAME.
BINILOAD terminates abnormally and the database is unchanged.

Response
Correct the OWNER CALCKEY statement and rerun BINILOAD.

0905

DISTRIBUTABLE LISTSET MISSING

Meaning
The record type to be loaded belongs to a distributable list. However, no appropriate set is specified for the record type. The associated INSERT statement is missing. BINILOAD terminates abnormally and the database is unchanged.

Response
Add the INSERT statement and rerun BINILOAD.

0906

STATEMENT statement-name IS NOT ALLOWED WHEN FORMAT CSV IS SPECIFIED

Meaning
Statements RECORD-DISPL, RECORD-DBKEY, RECORD-RSQ, USER BUFFER LENGTH, USER FILE RECORD LENGTH, OWNER KEY, OWNER SEARCHKEY, OWNER CALCKEY, OWNER DBKEY and OWNER RSQ are not allowed if FORMAT IS CSV is specified.
BINILOAD terminates abnormally and the database is unchanged.

Response
Check and correct the statements and rerun BINILOAD.

0907

OPTION <DISPL IS n, LENGTH IS m> IN STATEMENT statement-name IS NOT ALLOWED WHEN FORMAT CSV IS SPECIFIED

Meaning
OPTION <DISPL IS n, LENGTH IS m> is not allowed in statement SET ORDER if FORMAT IS CSV is specified.
BINILOAD terminates abnormally and the database is unchanged.

Response
Check and correct the statements and rerun BINILOAD.

0908

ERROR DURING VALUE CONVERSION. LINE NUMBER:  line-number, FIELD NAME:  field-name, ERROR TYPE:  error-type

Meaning
Value can't be converted to database item type.
The specified line was skipped when storing to the database.

Possible error types:

• INVALID SYMBOL (X)
• MORE SIGNIFICANT DIGITS THAN ALLOWED
• INCORRECT FORMAT OF DECIMAL NUMBER
• INCORRECT VALUE
• VALUE IS BIGGER THAN ALLOWED
• VALUE CANNOT BE CONVERTED TO UTF16. XHCS RETURN CODE: return-code
  return-code -  XHCS error code. For more detailed information about the XHCS error code enter /HELP-MSG in system mode or see the XHCS manual.
• ALPHANUMERIC VALUE IS NOT IN DOUBLE QUOTES

Response
Check and correct the value in the field where error occurred, delete all records of the specified record types from the database using BOUTLOAD (REMOVE-RECORD statement)  and rerun BINILOAD.

0909

ERROR DURING FIELDS NAMES PARSING. LINE NUMBER:  line-number, FIELD NAME:  field-name, ERROR TYPE:   error-type

Meaning
Name of the field doesn't correspond to any field name in the database.

Possible error types:

• NO FIELD WITH RSQ FOUND
• INVALID FIELD NAME

Response
Check and correct the name in the field for which error occurred and rerun BINILOAD.

0910

SOME VALUES ARE MISSED IN CSV LINE: line-number

Meaning
Number of values in the specified CSV line doesn't correspond to number of field names in the header line.

Response
Check and correct the values in the line for which error occurred.

0911

OPTION <USING FIELD NAME IS> IN <SET ORDER> STATEMENT IS ALLOWED ONLY WHEN FORMAT CSV IS SPECIFIED

Meaning
OPTION <USING FIELD NAME IS> is allowed in statement SET ORDER statement only if FORMAT IS CSV is specified.
BINILOAD terminates abnormally and the database is unchanged.

Response
Check and correct the statements and rerun BINILOAD

0912

FIELD NAME SPECIFIED IN <SET ORDER> IS NOT CORRECT

Meaning
Field name specified in SET ORDER USING FIELD NAME IS statement is not correct.
BINILOAD terminates abnormally and the database is unchanged.

Response
Check and correct the statement and rerun BINILOAD

5889

DATABASE INCONSISTENCE: WRONG FORMAT OF TABLE RECORD

Meaning
BINILOAD has discovered a table node in ACT-KEY format in the database although none may exist in ACT-KEY format with respect to the table. BINILOAD terminates abnormally.

Meaning
Check the database with BCHECK.

5890

ERROR IN SIA ACCORDING TO A DISTRIBUTABLE LISTSET
RECORD NAME: recordname  oder
SET NAME: setname

Meaning 
An inconsistency exists in the SIA with respect to distributable LIST sets, for instance the distribution attribute with respect to the record and set do not match or only one realm is specified for the record type. The name of the object concerned is displayed.

Response 
Check the consistency of the database before the BINILOAD run. If no inconsistency is detected, a system error exists.

5891

DATABASE INCONSISTENCE: TABLE RECORD NOT FOUND
DBKEY: dbkey
COLUMN NR: column-number

Meaning 
In the course of the internal program run (owner selection, erasing tables) a table occurrence, which should already have been in the database prior to the BINILOAD run, cannot be found.

Response 
If the message was not output during the check run, the database must now be reset. The consistency of the database prior to the BINILOAD run must be checked. If the database proves to be consistent prior to the BINILOAD run, a system error has occurred.

5892

DATABASE INCONSISTENCE: RECORD NOT FOUND
DBKEY: dbkey

Meaning
In the course of the internal program run (owner selection, erasing tables) a record occurrence, which should already have been in the database prior to the BINILOAD run, cannot be found.

Response
If the message was not output during the check run, the database must now be reset. The consistency of the database prior to the BINILOAD run must be checked. If the database proves to be consistent prior to the BINILOAD run, a system error has occurred.

5894

DB_KEY IN SCD OF CHAIN INVALID
OWNER DB_KEY: owner dbkey
DB_KEY: member dbkey

Meaning 
BINILOAD is processing the specified owner. BINILOAD fetches the specified member DB key (of the first or last member in the chain) from the owner’s SCD.
BINILOAD searches for act-key for this member DB key via the member DBTT. However, none was found.

Response 
If the message was not output during the check run, the database must now be reset. The consistency of the database prior to the BINILOAD run must be checked. If the database proves to be consistent prior to the BINILOAD run, a system error has occurred.

5895

USER CODED CHARACTER SET CANNOT BE DETERMINED: SRMUINFI RETURN CODE: returncode

Meaning
User coded character set can't be determined by SRMUINFI macro (see the return code) and loading data from the file in CSV format is not possible now. BINILOAD terminates abnormally.

Response
Data can be loaded from the input file not in CSV format.

5899

IN MODULE: module
AT OPERATION: operation
RETCODE: retcode

Meaning 
In some cases the buffer for the database page last read or last written to SYSLST is printed in addition to the above message.

Response 
Generate diagnostic documentation and write error report.
If the system error does not occur during the check run, the database has been destroyed and must be reset.

5899

OPERATION = WRITIL1/WRITIL2/WRITIL3
RETCODE = X’0002000B’

Meaning
An attempt is made to write to the scratch file with LINK-NAME=SCRTCH1, the return code corresponds to the DMS code: 0922
The scratch file was set up with SPACE = (primary, secondary), which were not multiples of 9 or 135 (in the case of high-efficiency I/O).

Response
Set up new scratch file.

5899

OPERATION = WRITIL1/WRITIL2/WRITIL3
RETCODE = X’0002000D’

Meaning
At attempt was made to write to the scratch file with LINK-NAME:SCRTCH1, the return code corresponds to the DMS-CODE: 054D
The scratch file is too small and cannot be expanded any further.

Response
Calculate data quantity to be stored in the scratch file (see “Creation and Restructuring“ manual) and set up new scratch file.

5899

OPERATION = SORTPEN
RETCODE = X’0106001E’

Meaning
The primary allocation for the sort file with LINK-NAME=SORTWK is too low in respect to the SORTCORE parameter which has been selected.

Response
Set up new scratch file.

5899

OPERATION = SORT-IN/SORTOUT
RETCODE = X’0106000D’

Meaning
In respect to the SORTCORE parameter the sort file is correctly dimensioned, proves, however, to be too small and cannot be expanded any further. (This error usually occurs when sorting the records in the STORE phase).

Response
Calculate data quantity for the sort file (see “Creation and Restructuring“ manual) and set up new sort file.