| Messages 0102-0132 are self-explanatory. |
0102
| AREA NOT OPENED: realmname
|
0105-0108
| explanation
|
0118
| STATEMENT WITH SYNTAX/SEMANTIC ERRORS DETECTED
|
0119
| EXECUTION OF STATEMENTS TERMINATED
|
0122
| TESTMODE IS ON
|
0124
| SOME PAGES TO BE REDUCED ARE OCCUPIED
|
0128
| NO DYNAMIC BREORG CALL ALLOWED
|
0130
| SCHEMA NAME IS NOT PRIVACY-AND-IQF-SCHEMA
|
0131
| SCHEMA NAME IS NOT COMPILER-SCHEMA
|
0132
| NO SCHEMA SPECIFIED
|
0133
| NO SUBSCHEMA HAS BEEN READ
|
| Meaning At least two SPECIFY-SUBSCHEMA statements have been specified, and the last SPECIFY-SUBSCHEMA was cancelled with UNDO. An error occurred when the penultimate subschema was read in again. Response Terminate BREORG with an END statement and then restart it. |
0134
| SUBSCHEMA STATEMENT IGNORED
Meaning The last SPECIFY-SUBSCHEMA statement is ignored because an error occurred when this subschema was read in. Response Repeat the SPECIFY-SUBSCHEMA statement; restart BREORG if necessary. |
0135
| SUBSCHEMA STATEMENT NOT ALLOWED
Meaning An error occurred while BREORG was being initialized. No further SPECIFY-SUBSCHEMA statement can be accepted. Response Restart BREORG if subschema is required. |
0140
| THE OPEN MODE OF AREA realmname IS NOT WRITE
Meaning The realm realmname could not be opened for writing during reorganization. Response Restart BREORG if the indicated realm is to be made available again exclusively. |
0356
| NON-EXISTING SCHEMA SPECIFIED
Meaning An unknown schema name was specified. Response Enter the correct schema name. |
0357
| NON-EXISTING SUBSCHEMA SPECIFIED
Meaning An unknown subschema name was specified. Response Enter the correct subschema name. |
0364
| BFORMAT NOT YET EXECUTED
Meaning BFORMAT has not run yet. Response A BFORMAT run is necessary before starting processing with BREORG. |
0370
| THE AREA IS NOT IN THE REFERENCED SCHEMA AREA-NAME: realmname
Meaning In the preceding statement a realm name was specified which does not exist in the schema. Response Enter the correct realm name. |
0373
| NO SUBSCHEMA SPECIFIED
Meaning No subschema has been specified for the REORGANIZE SET function. A set for which MODE IS LIST SORTED INDEXED has been defined requires a subschema. Response Specify subschema name in a SPECIFY-SUBSCHEMA statement. |
0374
| THE SET NAME IS NOT IN THE REFERENCED (SUB)SCHEMA
Meaning In the preceding statement a set name was specified which does not exist in the (sub)schema. Response Enter the correct set name. |
0375
|
|
0376
| UNEXPECTED PPPS DETECTED IN SET setname
Meaning During processing, BREORG discovered a PPP in an incorrect place. It may not be there because the record to which it refers is not relocatable, for instance. Response Execute a PPP update for the specified set again using REORGANIZE SET. |
0380
| TEMPORARY AREA WILL NOT BE ENLARGED/REDUCED
Meaning Self-explanatory. Response None. |
0389
| REQUIRED SIZE OF DBTT POSSIBLY OUT OF RANGE, SIA NOT UP TO DATE
Relevant statement:
MODIFY-RECORD-POPULATION Meaning The check reveals that the DBTT size obtained from the statement is outside the permitted range. 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). |
0390
| REQUIRED SIZE OF {FPA | DBTT | CALC} OUT OF RANGE
AREA-NAME: realmname , POPULATION: population-value or
KEY-REF: keyref , POPULATION: population-value
Meaning The required size of the specified area is outside the range possible under UDS/SQL. An additional message is only displayed if the REORGANIZE-CALC statement is entered incorrectly. Response Specify another size (Values between 1 and 16777216 are permitted as the number of FPA entries. The permitted number of DBTT entries varies: In the 2KB owner scenario, values between 1 and 16711679 are permitted. In the 2KB non-owner scenario, values between 1 and 16777215 are permitted. In the 4KB/8KB scenario, values between 1 and 2147483647 are permitted. For CALC: the maximum number of CALC pages calculated from the POPULATION specification is 16760797). |
0421
| THE DECREASE-VALUE IS SMALLER THAN NUMBER OF ENTRIES
Meaning The intended reduction in the number of entries in the DBTT of the referenced record type results in a number smaller than the highest number of reserved entries. Response Restart BREORG and enter a feasible number of occurrences in the MODIFY-RECORD-POPULATION statement. The DBTT information in the SIA-PRINT-REPORT can be useful as a source of information. |
0451
| REDUCE BY DMS NOT POSSIBLE FOR FILE filename
Meaning An error occurred during execution of the /MODIFY-FILE-ATTRIBUTES command to reduce the file filename for a realm, with the result that the realm can only be reduced logically (i.e. the FPA). Meaning The message always occurs in conjunction with the general utility message 0097 which describes the error in more detail. After BREORG has been terminated and the cause of the error removed, the user must reduce the file him- or herself using a MODIFY-FILE-ATTRIBUTES command. |
0452
| ENLARGE NOT POSSIBLE FOR FILE filename
Meaning The realm specified in the MODIFY-REALM-SIZE statement in the file filename cannot be enlarged. The error message is always followed by a general utility message. Response Analyze error codes and remove error; restart BREORG. |
0464
| NO POPULATION GIVEN FOR DIRECT CALC RECORDS
Meaning The record type of the CALC key records to be reorganized is of the type DIRECT-CALC. Specification of a POPULATION is necessary, which was, however omitted. No reorganization was performed. Response Restart BREORG with a POPULATION specification other than UNCHANGED in the CALC-RECORD operand. |
0501-0513
| explanation
Meaning Self-explanatory error message issued during the syntax analysis of the REORGANIZE-CALC and REORGANIZE-SET functions. |
0505
|
Response Correct the input or make sure the SIA is updated (connect the DB in an update DBH session). |
0517
| RECORD DOES NOT EXIST IN SPECIFIED AREA
Meaning In the REORGANIZE-CALC statement a record type was specified whose occurrences are not found in the realm specified at the same time. Response Enter the correct realm in the REORGANIZE-CALC statement. |
0518
| REORGANIZE-FUNCTION RESULTS IN NO PROCESSING
Meaning No reorganization was performed because NONE was specified for both the CALC-RECORD and CALC-SEARCHKEY operands in the REORGANIZE-CALC statement. Response None. |
0519
| NO REORGANISATION CALC SEARCH KEY TABLE
Meaning No CALC-SEARCH-KEY table was reorganized since the physical location of the record is fixed, and therefore there are no PPPs. Response None. |
0520
| NO CALC RECORD TYPE EXISTS IN SCHEMA
Meaning The specified record has not been defined in the REORGANIZE-CALC statement with LOCATION MODE IS CALC. The CALC-RECORD operand is ignored. Response None. |
0521
| NO CALC SEARCH KEY EXISTS IN SCHEMA
Meaning No CALC SEARCHKEY has been defined for the specified record in the REORGANIZE-CALC statement. The CALC-SEARCHKEY operand is ignored. Response None. |
0522
| DBDIR OR DBCOM NOT ALLOWED FOR FUNCTION REORGANIZE-POINTERS
Meaning DBDIR or DBCOM was specified in the REORGANIZE-POINTERS statement as the realm name. Response Specify a user realm or delete the statement. |
0523
| ONLY THE USER-SCHEMA IS ALLOWED FOR FUNCTION REORGANIZE-POINTERS
Meaning A schema name that is not the same as the user schema name was specified with the REORGANIZE-POINTERS statement in the SPECIFY-SCHEMA statement. Response Specify a user schema name or delete the REORGANIZE-POINTERS statement. |
0524
| THE DATABASE IS INCONSISTENT IN ANCHOR-TABLE / SCD-LENGTH/OWNER / SCD-LENGTH/MEMBER
Meaning An inconsistency in the specified size was detected while updating all PPPs in a specified realm. Response Restore a backup of the database and execute BCHECK. |
0530-0538
| explanation
Meaning Self-explanatory error message issued during processing of the REORGANIZE function. Response Check to see if the database saved before the BREORG run is consistent. |