DISPLAY [IN CSV [csv-filename]] RECORD STATISTICS FOR {record-name-1,... | ALL}
IN CSV
BSTATUS also outputs the data in CSV format.
csv-filename
Name of the file to which the data is to be output in CSV format. The specification of csv-filename is mandatory in the first IN CSV statement of a BSTATUS run (e.g. DISPLAY IN CSV 'BSTATUS.CSV' ...).
For a detailed description of CSV format output, see the manual “Database Operation”, section “Outputting database information in a neutral format”.
record-name
Name of a record type contained in the specified subschema for which record type statistics are to be printed out
ALL
BSTATUS prints the record type statistics on all record types contained in the specified subschema
Example
DISPLAY RECORD STATISTICS FOR ALL
*----------------------------------------------------------------------------------------------------------------------------------* | | D B T T | | |---------------------------------------------------------------------------------------|---------| | | NR OF | HIGHEST | HIGHEST | FILLING | EXTENDIBLE| NR OF | HIGHEST |NR ENTR. | | R E C O R D S | ENTRIES | RSQ | RSQ | | | DBTT | USED |PER DBTT | | | USED | USED | POSSIBLE | RATIO % | | EXTENTS | EXTENT |EXTENSION| |--------------------------------|------------|------------|------------|----------|-----------|------------|------------|---------| | | | | | | | | | | | CUSTOMER | 0 | 0 | 331 | 0,0 | SCAN | 0 | 0 | 21184| | | | | | | | | | | | CST-ORDERS | 0 | 0 | 497 | 0,0 | SCAN | 0 | 0 | 31808| | | | | | | | | | | | ORD-ITEM | 0 | 0 | 1990 | 0,0 | SCAN | 0 | 0 | 63680| | | | | | | | | | | | INSTALMENT | 0 | 0 | 995 | 0,0 | SCAN | 0 | 0 | 63680| | | | | | | | | | | | ART-TYPE | 4 | 4 | 497 | 0,8 | SCAN | 0 | 0 | 31808| | | | | | | | | | | | ART-SELECTION | 5 | 5 | 497 | 1,0 | SCAN | 0 | 0 | 31808| | | | | | | | | | | | ART-DESCR | 13 | 13 | 497 | 2,6 | SCAN | 0 | 0 | 31808| | | | | | | | | | | | ARTICLE | 63 | 63 | 995 | 6,3 | SCAN | 0 | 0 | 63680| | | | | | | | | | | | SUBSET | 0 | 0 | 995 | 0,0 | SCAN | 0 | 0 | 63680| | | | | | | | | | | | COLORS | 25 | 25 | 995 | 2,5 | SCAN | 0 | 0 | 63680| | | | | | | | | | | | MATERIALS | 10 | 10 | 995 | 1,0 | SCAN | 0 | 0 | 63680| | | | | | | | | | | | SUPPLIER | 1 | 1 | 662 | 0,1 | SCAN | 0 | 0 | 21184| | | | | | | | | | | | PURCHASE-ORDER | 0 | 0 | 497 | 0,0 | SCAN | 0 | 0 | 31808| | | | | | | | | | | | P-ORD-ITEM | 0 | 0 | 995 | 0,0 | SCAN | 0 | 0 | 63680| | | | | | | | | | | *----------------------------------------------------------------------------------------------------------------------------------* | | | | | | | | | | | T O T A L | 121 | | | | | | | | | | | | | | | | | | *----------------------------------------------------------------------------------------------------------------------------------*
RECORDS
Names of record types
DBTT
For each record type BSTATUS prints out the most important DBTT information
NR OF ENTRIES USED
The number of DBTT entries used is equivalent to the number of currently stored records of the record type
HIGHEST RSQ USED
Highest record sequence number assigned; if records have been erased, this number may be higher than the number of records currently stored
HIGHEST RSQ POSSIBLE
Highest record sequence number possible, i.e. greatest number of records of this record type which can be stored in the current DBTT
FILLING RATIO %
DBTT occupancy level, expressed as a percentage of the allocated DBTT entries
EXTENDIBLE:
Specifies whether or not the record type can be extended:
NO
cannot be extended
SCAN
can be extended with parameter SCAN=YES
NOSCAN
can be extended with parameter SCAN=NO
NR OF DBTT EXTENTS:
Number of DBTT extents currently present
HIGHEST USED EXTENT:
Number of DBTT extents currently present minus the number of consecutive completely empty extents at the end of the DBTT. This information can be of use in the case of a DBTT reduction using BREORG.
NR ENTR. PER DBTT EXTENSION:
Number of entries required for a DBTT extension
TOTAL
Outputs the total number of DBTT entries used.
The DBTT entries which are locked in the case of the BMODTT statement KEEP are not counted in any specifications; only those for which records have been stored are regarded as “occupied”.