ASAP 2.8 Server Manual

ASAP Conversational Interface Commands
HP NonStop ASAP Server Manual—522303-007
6-107
SET Command
{ entity | DEFAULT } { part-num | ALL } part-opt RESET
resets a specific partitioning attribute for the specified entity and partition
number. To reset the default setting of the specific attribute, use DEFAULT.
To reset all partitions of the specified entity, use ALL.
FORMAT2 { ON | OFF }
enables or disables support of Format 2 files. Format 2 support lets ASAP
retain much more data by allowing the creation of much larger files and
partitions.
Notes
•
You cannot specify a KEY, SYSNO, or VOLUME for a base partition (that is,
partition number 0). The latter is done by the SET DB command.
•
You cannot specify KEY, SYSNO, and VOLUME values if the partition number
is ALL.
•
You must provide a KEY or SYSNO value, or both, and a VOLUME for all
secondary partitions. If you do not, the partition description is marked Invalid in
the output of the SET PARTITION command, and the Collector does not create
the partition.
•
You must define partitioning keys (made up of a combination of the SYSNO
and KEY values) in ascending order for each partition. That is, the partitioning
key for partition 2 must be greater than the partitioning key for partition 1, the
key for partition 3 must be greater than the key for partition 2, and so on.
•
If Format 2 is on, you cannot specify MAXEXTENTS for a secondary partition.
The collector ignores any such values, and the secondary partitions are
created with the MAXEXTENTS value specified for the base partition.
•
The PRIEXT, SECEXT, and MAXEXTENTS values specified for partitions of
the DEFAULT entity are used when creating partitions for all other entities,
unless you supply specific values when you define the new partitions. For
example, partition 1 of the DEFAULT entity is defined with PRIEXT = 100. This
value is used when creating partition 1 of the CPU entity unless the definition
of partition 1 of the CPU entity overrides the DEFAULT setting.
•
The Collector automatically adjusts the length of the partitioning keys specified
for the partitions of a given entity to ensure that all partition key lengths are the
same for that entity. This is accomplished by null-filling partition keys for the
maximum partition key length specified.
For example, if the KEY for partition 1 of the APP entity is defined as FT, the
KEY for partition 2 is SWIFT, and the key for partition 3 is TXN, the maximum
partitioning key length is 5 bytes (from partition 2, for SWIFT). Therefore, the
Collector appends null bytes to the partitioning keys for partitions 1 and 3, so
their lengths are also 5 bytes. The partitioning key for partition 1 becomes [FT,
0, 0, 0], and the partitioning key for partition 3 becomes [TXN, 0, 0]. This