HP Large Objects System Management Manual

HP Large Objects System Management Manual – 543599.001
Appendix B – Parms
The parameter or parm table contains the values that determine how the Large Object
scheme performs. Values of the parms must not be changed once the BuddyGroup
they relate to is active. The BuddyGroup is active once the first BuddySet is created
for that group. Parm values should only be changed using SetBuddyGroupParm.
The metaData.sh script establishes a set of default parameters to cover an entire
installation of the Large Object system. The list below show which parameters can be
overridden at BuddyGroup level.
System Wide Parms
These parameters apply to an entire Large Object installation:
Token
Num
Name & Description Default Value
110 OBJECT_STORE_NUM
The name of this Large Object
instance. Multiple instances may
exist on a node for testing purposes.
Must be 4 characters or fewer. First
character must be alpha.
No Default.
170 TMF_BULK_LOCK_LIMIT
The number of locks allowed in a
single TMF transaction. This applies
only to BuddyReload.
100
Buddy Group Parms
These parms can be set for each individual BuddyGroup created on the system, and
thereby override the default value established for the installation.
Token
Num
Name & Description Default Value
101 FSM_BLOCK_SIZE
The block size for FSM files, for
lower powers the default is set to the
Segment size.
2048
102 BSP_BLOCK_SIZE
The block size for all BuddySpaces.
4096
103 BSP_FILE_SIZE
The size in kilobytes of all
BuddySpace files whatever their
power. Must be an exact multiple of
both the largest segment size
(multiple of 56k) and 32k so that an
exact number of segments fits into the
file for each power of two.
Greatly affects the amount of disk
2,097,152 (approximately 2MB)
Page 34 of 37