DUPLICATE KEYS FOUND
|
| SEE PRINTER OUTPUT
Meaning
Any illegal (duplicated) key values found are also listed on SYSLST in decimal and hexadecimal format under the heading ’FOR OWNER DBKEY: dbkey‘ or the heading
’DUPLICATE KEY LIST FOR CALC’, with up to the first 60 bytes of the key shown in character representation and up to the first 30 bytes of the key in hexadecimal form. If BALTER recognizes that illegal (duplicate) key values may exist, it informs the user of this fact in the report phase (with REPORT IS YES).
If BALTER actually finds illegal key values during restructuring (EXECUTION IS YES), it reports them as described above, but it executes the requested update regardless of the warning. Note
Illegal key values are not reported by BALTER for any records which need not be accessed in the BALTER run, even if DUPLICATES ARE NOT ALLOWED has been newly specified. Response
Make appropriate corrections. |
DBKEY VALUES WILL BE CUT
|
| SEE PRINTER OUTPUT
Meaning
The following lines are output to SYSLST with hexadecimal values:
FOR RECORD DBKEY: dbkey
DBKEY TO BE CUT: item-contents
If data is lost for a record type on converting a TYPE IS DATABASE-KEY-LONG item to a
TYPE IS DATABASE-KEY item due to the necessary truncation of the REC-REF item from 2 bytes to 1 byte or the necessary truncation of the RSQ item from 4 to 3 bytes, this data loss is reported. FOR RECORD DBKEY indicates the database key of the record in which the data loss occurred. DBKEY TO BE CUT indicates the values of an item to be truncated. |
1001
| UNKNOWN STATEMENT
|
| Meaning
A statement which has been input to BALTER does not begin with EXECUTION|REPORT|RUN|SORT|CORE|FILLING|END.
Response
Enter correct statement. |
1002
| EXECUTION STATEMENT INCORRECT
|
| Meaning
The statement EXECUTION IS { YES | NO }
was entered incorrectly. |
| Response
Enter correct statement. |
1003
| REPORT STATEMENT INCORRECT
|
| Meaning
The statement REPORT IS { YES | NO }
was entered incorrectly. Response
Enter correct statement. |
1004
| INCORRECT STATEMENT
|
| Meaning
The statement contains illegal keywords. Response
Correct statement; restart cycle. |
1005
| RENAMING SUCCESSFULLY INITIATED
|
| Meaning
A renaming cycle has been initiated. Response
None |
1006
| RESTRUCTURING SUCCESSFULLY INITIATED
|
| Meaning
A restructuring cycle has been initiated. Response
None |
1007
| STATEMENT NOT ALLOWED FOR RENAMING
|
| Meaning
The statement is not permitted in the renaming cycle. Response
Correct statement; restart BALTER. |
1008
| AFTER-IMAGE-LOGGING HAS BEEN SPECIFIED
|
| Meaning
Writing of after-images has been specified for the database.
When restructuring or renaming a database, however, no after-images are written. |
| Response
Restore the database from a backup copy, and terminate the writing of after-images
(BMEND Statement STOP-LOG). |
1009
| BPRIVACY-SIGN IS MISSING
|
| Meaning
The BCHANGE utility routine reports that the indicator that a BPRIVACY run is to be performed after a BALTER run is missing (e.g. because of an incorrect BALTER or BPRIVACY run). Response
Generate diagnostic documentation. |
1010
| SCHEMA CHANGES HAVE BEEN SPECIFIED WHICH ARE NOT ALLOWED
SET: setname
IF RECORDS OF MEMBER TYPE ARE PRESENT THE RESTRUCTURING PROCESS WILL END ABNORMALLY.
|
| Meaning
This message is output only if the indicated set has been specified in the new schema using one of the following set order specifications:
NOT SORTED:= FIRST|LAST|NEXT|PRIOR|IMMATERIAL If member records exist, this is only permitted if the structure for this set (chain, array, list) does not have to be newly set up. 1. | This warning appears when an existing set is updated, | 1.1 | if the set mode was altered, | 1.2 | when no change is made to the set mode for
CHAIN -> CHAIN, if the owner and/or member SCD’s increase in size POINTER ARRAY -> POINTER ARRAY, in the case of SET-ORDER SORTED INDEX in the old schema, LIST -> LIST, in the case of SET-ORDER SORTED INDEXED in the old schema,
or LIST RECORD increases in size or LIST table is transferred to another realm (in the case of SET-ORDER SORTED INDEXED in the new schema, lists may also not be stored in another realm). See “Creation and Restructuring“ manual. | 2. | This warning is output when a set is added, in case the set
(with SET-ORDER NOT SORTED) is singular and was specified as
MANDATORY AUTOMATIC. |
|
| Response
The BSTATUS utility routine can be used to determine whether member records are present in the database, to do so, however, the database must be restored from a backup copy
(see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring. |
1010
| SCHEMA CHANGES HAVE BEEN SPECIFIED WHICH ARE NOT ALLOWED
RECORD: recordname
|
| Meaning
BALTER was started by entering EXECUTION IS YES.
This message is output only if the set in which the indicated record is a member has been specified in the new schema using one of the following set order specifications: SET-ORDER NOT SORTED:= FIRST|LAST|NEXT|PRIOR|IMMATERIAL
If member records exist, this is permitted only if the structure for this set (chain, array, list) does not have to be newly set up. Set occurrences for the record type in question do exist. Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring. |
1011
| BCHANGE ALREADY EXECUTED
|
| Meaning
BCHANGE has already been executed for restructuring. Response
Continuation of restructuring with DDL (compilation of the new schema). |
1012
| BFORMAT NOT EXECUTED
|
| Meaning
When setting up the original database, BFORMAT was either not executed at all or not executed for all the user realms. Response
In case BFORMAT was not executed at all, newly create the database using the correct schema instead of restructuring it; otherwise format the unformatted realms with BFORMAT prior to restructuring. |
1013
| NO EXECUTION STATEMENT SUPPLIED
|
| Meaning
The statement EXECUTION IS { YES | NO }
was not input. BALTER immediately terminates abnormally. Response
Restart BALTER and enter statement correctly. |
1014
| NO REPORT STATEMENT SUPPLIED
|
| Meaning
The statement REPORT IS { YES | NO }
was not input. BALTER immediately terminates abnormally. |
| Response
Restart BALTER and enter statement correctly. |
1015
| FILE IN USE OR ACCESS IS READ realmname
|
| Meaning
The indicated realm is currently locked and therefore cannot be opened. Response
Find reason for the lock, if necessary postpone restructuring or renaming to a later point in time. |
1016
| PASSWORD NOT GIVEN realmname
|
| Meaning
The specified realm has been assigned a password; since this was not specified, this file cannot be opened. Response
Enter password. |
1017
| FILE DOES NOT EXIST realmname
|
| Meaning
The specified realm does not exist, it is possible that an incorrect dbname.CATALOG is being used for restructuring the database. Response
Check configuration for the existing database. |
1018
| FILE NOT SHARABLE realmname
|
| Meaning
The indicated realm is not shareable. This message can only occur if processing does not take place under the user ID under which the database is cataloged.
This is, however, not permitted for restructuring or renaming. Response
Start BALTER/BCHANGE under the user ID under which the database is cataloged. |
1019
| FILE IS EMPTY realmname
|
| Meaning
The indicated realm is empty. |
| Response
Check configuration for the existing database and if it is found to be a dbname.CATALOG file, an incorrect database name has been specified. First open the database using
/SET-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=dbname.DBDIR
and then restart BCHANGE or BALTER. |
1020
| programname HAS NOT BEEN EXECUTED
|
| Meaning
Execution of the programname utility was omitted when preparing the BALTER run. Response
Incorporate the appropriate utility routine in the preparation for restructuring or renaming. |
1022
| NO DATABASE DECLARED OR CATALOG-FILE NOT CORRECT
|
| Meaning
When starting BCHANGE or when (separately) starting BALTER, no dbname.CATALOG file of a database had been created with LINK-NAME=DATABASE. Response
First specify the database using
/SET-FILE-LINK LINK-NAME=DATABASE,FILE-NAME=dbname.DBDIR
and then restart BCHANGE or BALTER. |
1023
| DATABASE IS LOCKED WITH RESPECT TO WANTED ACCESS RIGHT
|
| Meaning
The dbname.DBDIR file belonging to the database is locked and can thus not be opened.
The probable reason is that the DBH or another utility routine (which is not required to start under the user ID under which the database is cataloged) is processing the database. Response
Find reason for locked state. Postpone restructuring or renaming if necessary. |
1025
| DATABASE ALREADY IN USE
|
| Meaning
The database is locked against access. Response
Find reason for locked state. Postpone restructuring or renaming if necessary. |
1026
| FILL STATEMENT INCORRECT
|
| Meaning
FILL statement was specified incorrectly Response
Check and correct FILL statement and rerun BALTER |
1029
| NO FILE FOR REALM realmname
|
| Meaning
No file has been set up on operating system level for the realm. Response
In the event that the realm is a user realm to be added, the database must be reset to the state existing before restructuring or renaming was begun. The new files have to be created; then repeat restructuring or renaming. |
1030
| FILE CONTAINS NO OR ONLY ONE PAGE realmname
|
| Meaning
The indicated realm does not contain a page or contains only one page, error probably occurred during creation. |
| Response
If the realm is a user realm to be added, the database must be reset to the state existing before restructuring, the new files have to be created and restructuring repeated. |
1031
| AREA NOT OPENED realmname
|
| Meaning
The indicated realm could not be opened. Response
Check whether the realm has already been opened, if necessary use VERIFY. |
1032
| AREA NOT FORMATED
REALM-NAME: realmname
|
| Meaning
The indicated realm of the old schema is temporary and/or not formatted. Response
In the event that BFORMAT has not been performed at all, recreate the database using the correct schema instead of restructuring;
otherwise format the unformatted realms using BFORMAT prior to restructuring. |
1033
| A CHANGE OF THE TEMPORARY SITUATION HAS BEEN SPECIFIED
|
| Meaning
Specification of the indicated realm was changed from permanent to temporary, or vice versa; such an alteration of the schema is, however, not permitted. Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual) and repeat restructuring using the corrected schema. |
1034
| UNKNOWN ITEM TYPE IN OLD/NEW SCHEMA. RECORD NAME: recname. ITEM NAME: itemname
|
| Meaning
BALTER cannot process the data type of the specified item which was generated by the DDL compiler in the old or new DBCOM. Response
Use the BALTER of the UDS/SQL version which matches the database. |
1035
| SAME SET HAS GOT ANOTHER OWNER OR MEMBER setname
|
| Meaning
A different owner or member record was defined for the indicated set whose name was not changed; this is, however, not permitted. |
| Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual) and repeat restructuring using the corrected schema. |
1036
| A CHANGE OF THE DYNAMIC SITUATION HAS BEEN SPECIFIED
|
| Meaning
Specification of the indicated set was changed from normal to DYNAMIC or vice versa;
such an alteration of the schema is, however, not permitted. |
| Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual) and repeat restructuring using the corrected schema. |
1037
| WRONG DBCOM (OLD)
|
| Meaning
The original database to be restructured contains an invalid compiler realm (backup data, version no.).l The database is inconsistent. Response
Find reason for inconsistency.
In the event that this message is not output until the BALTER run, copy the old DBCOM to DBCOM.O, if necessary using a backup copy, and restart BALTER. |
1039
| REALM NOT CONSISTENT realmname
|
| Meaning
In the indicated realm the system break bit is set, the database is inconsistent. Response
Find reason for inconsistency.
Either restore the database from a backup copy or retry SSL. |
1040
| REALM FULL realmname
|
| Meaning
Not enough free blocks in indicated realm. Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual).
Enlarge the size of the realm by the number of pages required using the utility routine BREORG, repeat restructuring. |
1041
| RECORD PRESENT IN AREA (DELETED FROM RECORD-WITHIN-CLAUSE)
|
| Meaning
For the indicated record type the WITHIN clause (DDL) of the new schema is at least one realm short as compared to the old schema. The omitted realms must not contain any records. |
| Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring. |
1042
| CYCLIC SET RELATION BETWEEN RECORDS LIST OF RECORD TYPES
|
| Meaning
A cyclic set structure exists for which the intended updates cannot be performed (see “Creation and Restructuring“ manual). Response
If necessary carry out restructuring in several steps. |
1044
| NON PARTICIPATING MEMBERS FOR A SET WITH MODE IS LIST
|
| Meaning
For a set defined with MODE IS LIST (and thus MANDATORY AUTOMATIC) in the new schema, member records exist in the database which are not assigned to an owner. Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring.
Instead of removing existing member records without owner, the records can also be inserted into the set occurrences. Note
BALTER aborts with this message only if the set setname must be processed for another reason, otherwise BALTER terminates normally with the database in an inconsistent state. |
1045
| NON PARTICIPATING MEMBERS FOR A MATCHING AUTOMATIC SET
|
| Meaning
In the database there are member records without assignment to an owner and belonging to a set defined as MANDATORY AUTOMATIC in the new schema. Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring.
Instead of removing existing member records without owner, these records can be inserted into the set occurrences. Note
BALTER aborts with this message only if the set setname must be processed for another reason, otherwise BALTER terminates normally with the database in an inconsistent state. |
1046
| NEW AUTOMATIC NON-SINGULAR SET: MEMBER INSERTION IMPOSSIBLE
RECORD: recordname
IF RECORDS OF MEMBER TYPE ARE PRESENT THE RESTRUCTURING PROCESS WILL END ABNORMALLY.
|
| Meaning
In the new schema, the indicated record type is a member record type of a new non-singular set defined as MANDATORY AUTOMATIC. If member records exist, they cannot be inserted, since selection of the owner is not possible. |
| Response
The utility routine BSTATUS can be used to detect whether member records exist in the database, to do so, however, the database must be restored from a backup copy
(see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring. |
1048
| COMPRESSED INFORMATION OR VARIABLE LENGTH FOR RECNAME: recordname
|
| Meaning
The indicated record type was defined using the SSL clause COMPRESSION FOR ALL ITEMS in the old schema or contains a variable item in the old and/or new DDL. If existing records include COMPRESS information in the user section, they cannot be processed by BALTER. In the case of COMPRESSION this applies for records which are actually compressed
(CALL DML), and it always applies for records with a variable item. Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring. |
1050
| BFORMAT EXECUTED WHILE RESTRUCTURING
|
| Meaning
The utility routine BFORMAT was used during restructuring; this is, however, not permitted;
BALTER should be used instead. Response
Restore the database from a backup copy (DBDIR, DBCOM, COSSD, HASHLIB) and correctly execute restructuring. |
1051
| SORTCORE STATEMENT INCORRECT
|
| Meaning
The statement SORTCORE IS nnn was entered incorrectly. Response
If neither the default value nnn = 150 nor the last setting specified is desired, enter a correct statement. |
1052
| INCORRECT VALUE FOR SORTCORE
|
| Meaning
The specified value for nnn is outside the range of permitted values, which is 24 ... 255. Response
Enter correct value. |
1053
| RUN STATEMENT INCORRECT
|
| Meaning
The statement RUN { WITH | WITHOUT } EFFICIENT IO
was entered incorrectly. |
| Response
If neither the default value WITH nor the last setting specified is desired, enter a correct statement. |
1055
| FILLING STATEMENT INCORRECT
|
| Meaning
The FILLING statement was entered incorrectly. Response
If neither the default value for the occupancy level nor the last setting specified is desired, enter a correct statement. |
1056
| INCORRECT VALUE FOR FILLING
|
| Meaning
The value specified for nnn is outside the permitted range of values, which is 1 ... 100 Response
Enter an acceptable value. |
1057
| WRONG NAME SET : setname
|
| Meaning
There is no such set name in the new SIA. Response
Enter the FILLING statement with the set name corrected. Correctly specified set names will then be processed. In batch mode the entire statement has to be repeated. |
1059
| BRENAME ALREADY EXECUTED
|
| Meaning
A renaming cycle has already been initiated. Renewed initiation is only possible if the previous save status is restored. |
1060
| DECLARATION CONFLICT OF MEMBER AREAS IN DDL AND SSL
|
| Meaning
The owner’s realm is determined for a LIST set by the DETACHED statement without a WITHIN clause. However, this realm is missing in the DDL declaration of the member record types. Response
Specify the realm explicitly in the DETACHED statement or add the realm to the declaration of the member record types in DDL or SSL; repeat cycle. |
1058
| FILLING STATEMENT FOR THIS CHAIN IS IGNORED
SET : setname
|
| Meaning
There are no tables for the set specified. |
1061
| MODULE NAME: modulename; DBTT_ADMIN MISSING FOR RECORD recordname
|
| Meaning
A runtime error occurred during the processing of the DBTT tables. |
| Response
Create the diagnostic documents and submit error report. |
1062
| MODULE NAME: modulename; DBTT_BASE_PTR MISSING
|
| Meaning
A runtime error occurred during the processing of the DBTT tables. Response
Create the diagnostic documents and submit error report. |
1063
| MODULE NAME: modulname; PAGE pagenr IS NO DBTT PAGE
|
| Meaning
A further DBTT page should be read in the procedure, but the page actually read is of a different type. Response
Create diagnostic documentation and write error message. |
1064
| MODULE NAME: modulname; SELECTED DBTT EXTENT DOES NOT EXIST
|
| Meaning
Too high a value was calculated for the DBTT EXTENT INDEX when the DBTT was processed to supply PHYSICAL LINKs. Response
Create diagnostic documentation and write error message. |
1075
| RECORD WITH RSQ rsq EXISTING
RESTRUCTURING NOT POSSIBLE
|
| Meaning
An occupied DBTT entry rsq that is not permitted in owner record types was found during the modification of a pure member record type to an owner record type in a database in 2-Kbyte page format. Response
Delete or change the storage location of records with an excessively large rsq or convert the database to 4-Kbyte or 8-Kbyte page format. |
1076
| COPY WITH ERROR
FILE : COSSD
ERRORCODE: dmscode
|
| Meaning When copying COSSD to COSSD.O an error occurred. The DMS code is output. Response
The copy dbname.COSSD.O is not required for the actual restructuring procedure, it is, however, required for the transfer of the compatible subschemas subsequent to restructuring. If BCHANGE was started separately, copying can be repeated directly following it (that is prior to compilation of the new DDL schema), otherwise (i.e. after restructuring has been completed) only a backup copy of the COSSD can be used prior to restructuring. If the error occurred because the COSSD did not exist at all, a COSSD must be created prior to compilation of the new DDL schema. |
1076
| COPY WITH ERROR, FILE: DBCOM
|
| Meaning
When copying DBCOM to DBCOM.O an error occurred. The DMS code is output. Response
Restart after resetting the DBDIR BCHANGE. |
1077
| REALM NOT CLOSED
FILE : realmname
DMS-CODE : dmscode
|
| Meaning
When terminating restructuring, the realm realmname could not be closed. Response
Check output DMS code. |
1079
| “COMPRESSION FOR ALL ITEMS” SPECIFIED FOR RECORD: recordname
IF COMPRESSED INFORMATION WILL BE FOUND OR VARIABLE LENGTH MUST BE TREATED THE RESTRUCTURING PROCESS WILL END ABNORMALLY. |
| Meaning
The indicated record type was defined using the SSL clause COMPRESSION FOR ALL ITEMS in the old schema or contains a variable item in the old and/or new DDL. If existing records contain COMPRESS information in the user section, they cannot be processed by BALTER. This applies in the case of COMPRESSION for records which have actually been compressed (CALL DML), and always applies for records with a variable item. BALTER cannot change records with a fixed length into records with a variable length. Response
The utility routine BSTATUS can be used to detect whether member records exist in the database, to do so, however, the database must be restored from a backup copy
(see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring. |
1080
| MANDATORY AUTOMATIC HAS BEEN SPECIFIED
SET: setname
IF NON PARTICIPATING MEMBERS ARE PRESENT THE DATABASE WILL BE INCONSISTENT AFTER RESTRUCTURING.
|
| Meaning
The given set has been specified as MANDATORY AUTOMATIC in the new schema, however, but was not specified at all in the old schema. If existing records have not been inserted, this cannot be done at a later date by BALTER. This also applies to singular sets. |
| Response
The utility routine BSTATUS can be used to detect whether member records exist in the database, to do so, however, the database must be restored from a backup copy
(see “Creation and Restructuring“ manual), member records that are not included in the given set must be removed prior to restructuring. Instead of removing member sets without owner, these records can also be inserted in set occurrences. Note
If BALTER was started with EXECUTION IS YES, one of the following three cases occurs: |
1. “MANDATORY AUTOMATIC” HAS BEEN SPECIFIED
|
| SET: setname
PARTITION-CHECK HAS BEEN DONE.
Meaning
MANDATORY AUTOMATIC has been newly entered in the specified set; BALTER has run a positive set membership check. |
2. “MANDATORY AUTOMATIC” HAS BEEN SPECIFIED
|
| SET: setname
NO PARTITION-CHECK HAS BEEN DONE.
Meaning
MANDATORY AUTOMATIC has been newly entered in the specified set and BALTER has not run a set membership check. If the specified set contains member records that have not been inserted, the database is inconsistent. |
3. 1044/1045
|
| Meaning
BALTER aborts with message 1044 or 1045 if the specified set that has just been made MANDATORY AUTOMATIC has to be processed for another reason and records that have not been inserted exist. The database is then inconsistent. |
1081
| AREAS DELETED FROM RECORD-WITHIN-CLAUSE RECORD: recordname
IF RECORD OCCURRENCES ARE PRESENT IN AREAS WHICH ARE DELETED FROM RECORD-WITHIN-CLAUSE THE RESTRUCTURING PROCESS WILL END ABNORMALLY.
|
| Meaning
For the indicated record type, the WITHIN clause (DDL) of the new schema is at least one record short as compared to the old schema. The omitted realms must not contain any records. |
| Response
Restore the database from a backup copy (see “Creation and Restructuring“ manual), existing member records must be removed prior to restructuring. |
1083
| MODULE module: DATABASE IS INCONSISTENT
|
| Meaning
The system break bit is located in an AK0 of the open realm (DBDIR or user area). The database is inconsistent. |
| Response
Roll back database. Check with BCHECK. |
1084
| BALTER-SIGN IS MISSING. NAME OF MODULE: module
|
| Meaning
The BCHANGE utility routine reports that the indicator that a BPRIVACY run is to be performed after a BALTER run is missing (e.g. because of an incorrect BALTER or BPRIVACY run). Response
Generate diagnostic documentation. |
1085
| RECORD OF VARIABLE LENGTH: AN INTERNAL ERROR OCCURRED
RECORD:recordname
|
| Meaning
An internal error occurred while restructuring a variable length record type. BALTER will terminate abnormally. Response
Check database backups with BCHECK. They are possibly already inconsistent. Restore the database from a consistent backup copy. |
1091
| number CHANGE(S) OF FIELD TYPE
|
| Meaning
The item type has been changed in the number of items specified. Response
You must check very carefully that the data stored in these items in the database is compatible with the type change and use in the application programs. |
1092
| number CHANGE(S) OF REPEATING GROUP
|
| Meaning
The number of repeating groups specified is affected by the change. Response
You must check very carefully that the data stored in these items in the database is compatible with the change and use of the repeating groups in the application programs. |
1093
| number CHANGE(S) OF DATABASE KEY FIELD
|
| Meaning
The number of items of the type database key specified is involved in changes. Response
You must check very carefully that the data stored in these items in the database is compatible with the type change and use in the application programs. |
1094
| number CHANGE(S) OF INDEX IN VECTOR OR REPEATING GROUP
|
| Meaning
The number of indexes of vectors and repeating groups specified has been changed. |
| Response
You must check very carefully that the data stored in these items in the database is compatible with the change and use in the application programs. |
1095
| number CHANGE(S) WITH CONCATENATION OF FIELDS
|
| Meaning
The number of items specified has been formed by concatenation of existing items. Response
You must check very carefully that the data stored in these items in the database is compatible with the grouping and use in the application programs. |
1096
| number CHANGE(S) WITH SPLIT OF FIELDS
|
| Meaning
The number of items specified has been split. Response
You must check very carefully that the data stored in these items in the database is compatible with the splitting and use in the application programs. |
1097
| UNKNOWN ITEM IN NEW SCHEMA. RECORD NAME: recordname. ITEM NAME: itemname
|
| Meaning Item or record, entered in FILL statement, wasn’t found in schema. Response
You must check very carefully that the data you entered compatible with DB schema. |
1098
| INCORRECT FILL VALUE FOR ITEM: itemname. ERROR TYPE : errortype
|
| Meaning Value of item itemname can’t be stored in DB, because of errortype. Response
Analyze errortype, if “TOO BIG FRACTIONAL PART” error occurred, it means, that value, you tried to store, has too many digits in fractional part (second number in decimal items declarations), try to increase that amount or change entered value.
If “TOO BIG INTEGER PART” error occurred, it means that you entered too many digits before comma. Try to increase overage length of item in DB schema or enter smaller value.
If “SIZE EXCEED” error occurred, it means that you entered too long character or hexadecimal value, try to increase item in DB schema or enter shorter value.
If “ILLEGAL COMMA IN BINARY TYPE” error occurred, it means that you entered comma in binary type, enter value without comma.
If “TOO MANY SIGNIFICANT DIGITS” error occurred, it means that numeric value contains more significant digits than allowed by data type.
If “CANNOT CONVERT DBKEY” error occurred, it means that specified value in FILL statement is not in hexadecimal representation.
If “VALUE CANNOT BE CONVERTED TO UTF16. XHCS RETURN CODE: return-code” error occurred, check XHCS return error code, by entering /HELP-MSG in system mode or see the XHCS manual. |
1099
| STRING IS TOO LONG
|
| Meaning Too long character sequence was entered as a new default value. Response
You must enter character sequence not more than 255 bytes. |
1100 | ITEM ALREADY EXISTS IN OLD SCHEMA. RECORD NAME: recordname. ITEM NAME: itemname. FILL STATEMENT WILL BE IGNORED.
|
| Meaning
Item of record, entered in FILL statement, exists in old DB schema. Response
You must check the data you entered in FILL statement; it must not contain items from old DB schema. |
1101
| NATIONAL VALUE IS SPECIFIED IN UNSUPPORTED FORMAT
|
| Meaning
BALTER supports three formats for specifying value for national type in FILL statement: C-string, X-string and unpacked numeric. Response
Please verify the value and correct the statement |
1102
| USER CODED CHARACTER SET CANNOT BE DETERMINED: SRMUINFI RETURN CODE: return-code
|
| Meaning
Self-explanatory. |
1103
| THERE ARE NO RECORDS FOR RECORD TYPE. FILL STATEMENTS WILL BE IGNORED
|
| Meaning
Warning
The record type is empty, all FILL statements for this record type are ignored |
1104 | WRONG FIELD NAME IS SPECIFIED IN statementname STATEMENT. RECORD NAME: recordname.ITEM NAME: itemname.
|
| Meaning
recordname or itemname is wrong. Response
In case of FILL statement, you should check that you didn't specify a field with repetition factor. |
1105
| BUFFER OVERFLOW buffertype DURING GENERATION OF MOVE ROUTINE.
|
| Meaning
Buffer overflow in internal routine.
Analyze buffertype:
If buffertype is “FOR VARIABLES OF FILL STATEMENTS”, too many FILL statements are specified. BALTER allows only 62 FILL statements.
If buffertype is empty, buffer overflow for binary values or space occurred. Response
Split the restructuring in several runs. |
2100
| realmname IS TOO SMALL
|
| Meaning
The realm cannot be formatted as it has been configured too small and is not extensible.
This has no influence on the formatting of other realms. Response
Enlarge realmname at least to the size specified by BGSIA-ESTIMATE-REPORT or permit extension by defining a secondary allocation > 0 and start restructuring again. |
2113
| realmname IS NOT PRESENT
|
| Meaning
Specified realm does not exist or cannot be processed. Response
Make the realm available and start restructuring again. |
4120
| SPECIFIED PAGE SIZE FOR DATABASE REALMS IS NOT ALLOWED
|
| Meaning
The DB page size specified is not permissible. Response
Specify permissible page size (DATABASE-PAGE-LENGTH) or generate diagnostic documentation and write error report. |
6001-6098
| RETURNCODE:retcode
DMS-CODE :dmscode/’ ’
FUNCTION :operation
<DECLARATION>/’ ’
IN MODULE :module
|
| Meaning
Self-explanatory. Response
Check return code and DMS code; if necessary compile diagnostic documentation and write error report. |
6005
| INCONSISTENCE IN DBTT
DATABASE KEY : key
ACTUAL KEY : key
DBTT COLUMN NUMBER : number
MODULE : module
|
| Meaning
The logical record type belonging to a DBTT entry cannot be found during program runtime. Response
Restore the database from a backup copy, then check the consistency of the database with the aid of the utility routine BCHECK. If the database is consistent, a system error has occurred. |
6005
| INCONSISTENCE IN TABLE
DATABASE KEY : key
ACTUAL KEY : key
LAST ACTUAL KEY : key O. page-number
DBTT COLUMN NUMBER : number
MODULE : module
|
| Meaning
A table record belonging to a table occurrence cannot be found during program runtime. Response
Restore the database from a backup copy, then check the consistency of the database with the aid of the utility routine BCHECK. If the database is consistent, a system error has occurred. The following system error messages are possibly the result of user errors: |
6090
| FUNCTION: SORTCRT RETURN CODE: 00060013 DMS-CODE: 054D
|
| Meaning
The sort file with LINK-NAME=SORTWK has not been set up by the user, public volume was not sufficient when setting up the sort file by means of BALTER with SPACE = (120, 120). Response
Create enough space on public volume or set up the sort file on private volume, then restart BALTER. |
6091-6093
| FUNCTION: SORTPEN/SORT_OUT/SORT_IN RETURN CODE: 0106srt
|
| Meaning
An error was detected by the SORT. srt is the return code of the SORT Response
See the manual “SORT (BS2000)“. |
6091
| FUNCTION: SORTPEN RETURN CODE: 0106001E
|
| Meaning
The sort file with LINK-NAME=SORTWK has been set up by the user, the primary allocation is however insufficient with regard to the SORTCORE parameter selected. Response
Restore the database from a backup copy, recreate sort file, then repeat restructuring. |
6092
| FUNCTION: SORT_IN RETURN CODE: 0106000D
|
| Meaning
The sort file is correctly dimensioned with regard to the SORTCORE parameter, proves, however, to be too small and can no longer be expanded. (This error usually occurs when sorting existing records of a record type which must be relocated). Response
Calculate size of data volume for sort file, restore the database from a backup copy, recreate sort file, then repeat restructuring. |
6093
| FUNCTION: SORTOUT RETURN CODE: 0106000D
|
| Meaning
The sort file is correctly dimensioned with regard to the SORTCORE parameter, proves, however, to be too small and can no longer be expanded. (This error usually occurs when sorting existing records of a record type which must be relocated). Response
Calculate size of data volume for sort file, restore the database from a backup copy, recreate sort file, then repeat restructuring. |
6095
| FUNCTION: FILECRT RETURN CODE: 0002000D
|
| Meaning
The scratch file with LINK-NAME=SCRTCH1 has not been previously set up by the user, but storage space was not sufficient for creating the scratch file by means of BALTER with
SPACE = (9,9) or (135,135) with high-efficiency input/output. Response
Create enough space on public volume or set up scratch file on private volume, then restart BALTER. |
6098
| FUNCTION: WRITILE RETURN CODE: 0002000B
|
| Meaning
The scratch file with LINK-NAME=SCRTCH1 has been set up by the user, the primary or secondary ALLOCATION is not a multiple of 9 or 135 in the case of high-efficiency I/O. Response
Recreate scratch file and restore the database from a backup copy, then repeat restructuring. |
6098
| FUNCTION: WRITILE RETURN CODE: 0002000D
|
| Meaning
The scratch file with LINK-NAME=SCRTCH1 proves to be too small and is no longer expandable. Response
Calculate size of data volume for sort file, recreate sort file and restore the database from a backup copy, then repeat restructuring. |
9112
| FSTAT-ERROR
DMS-CODE = dmscode
ERRORBYTE = errbyte
FILE = filename
|
| Meaning
A runtime error occurred with respect to the specified file when a SHOW-FILE-ATTRIBUTES command was executed. The message is followed by a dump of the SHOW-FILE-ATTRIBUTES command’s parameter block for diagnostic purposes. Response
Write down error message and add it, plus documents related to the file concerned, to the runtime log. |
