HP 3000 Manuals HP 3000 Manuals
$CONTROL
The $CONTROL command allows you to specify options in relation to
processing the schema.
Syntax
$CONTROL [LIST ] [,ERRORS=nnn] [,LINES=nnnnn] [,ROOT ]
[NOLIST] [,NOROOT]
[REV BEG]
[,BLOCKMAX=nnnn] [,TABLE ] [,JUMBO ]
[,NOTABLE] [,NOJUMBO]
[REV END]
Parameters
LIST causes each source record of the schema to be printed on
the list file.
NOLIST specifies that only source records with errors be
printed on the list file. An error message is printed
after these records.
ERRORS=nnn sets the maximum number of errors to nnn. If more than
nnn errors are detected, the Schema Processor
terminates. nnn can have a value between 0 and 999,
inclusive. The default value is 100.
LINES=nnnnn sets the number of lines per page on the list file to
nnnnn which can be between 4 and 32767, inclusive. The
default value is 60 if the list file is a line printer
and 32767 if it is not.
ROOT causes the Schema Processor to create a root file if no
errors are detected in the schema. This is the default.
NOROOT prevents the Schema Processor from creating a root file.
BLOCKMAX=nnnn sets the maximum physical block length (in halfwords)
for any data set in the database. nnnn can have a value
between 128 and 2560, inclusive. The default value is
512. This is an important parameter and is discussed in
detail in the section "Selecting the Block Size."
TABLE causes the Schema Processor to write a table of summary
information about the data sets to the list file device
if no errors are detected. This is the default.
NOTABLE suppresses the TABLE option.[REV BEG]
JUMBO allows a data set, defined following this option whose
capacity is greater than 4 GB, to automatically become a
jumbo data set.
NOJUMBO disallows data sets, defined following this option, to
be jumbo data sets.[REV END]
Description[REV BEG]
The default parameters are LIST, ROOT, TABLE, and NOJUMBO.[REV END] If no
$CONTROL command is used, the results are the same as if the following
$CONTROL command is used:
$CONTROL LIST,ERRORS=100,LINES=60,ROOT,BLOCKMAX=512,TABLE
The parameters can be placed in any order but must be separated by
commas.
[REV BEG]
To specify a jumbo data set, the JUMBO option must be included in the
schema before defining any jumbo data sets. Then any data set whose
capacity is greater than 4 GB automatically becomes a Jumbo data set. If
the JUMBO option is not specified, an error is generated for the data
sets exceeding the 4 GB limit. Use the NOJUMBO option to turn off the
jumbo feature.
DBSTORE does not store jumbo data sets; instead use TurboSTORE/iX 7x24
True-Online Backup using ONLINE=START or ONLINE=END option.
NOTE Use only third-party utilities and diagnostic tools that are
enhanced to handle Jumbo data sets.
[REV END]
Selecting the Block Size
The data set records are transferred from the disk to memory in 4096-byte
pages in TurboIMAGE/XL blocks. The block format is described in chapter
10. When you specify a maximum block size with the $CONTROL command, you
should consider:
* Efficient disk space utilization.
* Localizing the block's bit map to the actual data entries within a
4096-byte page.
The Schema Processor determines the number of data records that fit in a
block. Note that DBSCHEMA chooses a block size (less than or equal to
the maximum block size) that makes the best use of disk space, and which
can be substantially less than the maximum block size specified by
$CONTROL BLOCKMAX (or the default of 512 halfwords). If the record size
is greater than 512 halfwords, BLOCKMAX must be set greater than or equal
to the record size. A certain amount of tuning may be necessary to
determine the best block size. In general, the default block size of 512
halfwords yields reasonable performance on TurboIMAGE/XL and should be
changed only when needed.