HP-UX Virtual Partitions Administrator's Guide (includes A.05.01) (previously titled Installing and Managing HP-UX Virtual Partitions)

CPU, Memory, and I/O Resources (A.05.xx)
Memory: Setting the Granularity Values (Integrity)
Chapter 6
209
Memory: Setting the Granularity Values (Integrity)
Syntax
The syntax for setting granularity unit size is:
-g ILM|CLM: unit [:y|n]
where:
g is granularity
ILM|CLM specifies whether the unit size is applied to ILM or CLM
unit is the granularity unit size in MBs
This value must be an integral power of 2 (in other words, 2^X) and be greater than or
equal to 64.
y|n specifies whether granularity unit size should be written to firmware. The default is n.
[vparcreate only; Integrity only]
The procedure to configure granularity unit sizes is described under “Configuring Granule Size” on page 211.
Commands
There are two commands that can set the granularity values: vparenv and vparcreate. Both are available
at the HP-UX shell level and use the -g option:
1. vparenv -g ...
writes the granularity values to the firmware only. Note that vparenv is applicable only on Integrity.
2. vparcreate -g ...
writes the granularity values to the vPars database and also can (using the update firmware option [:y])
write these values to firmware.
vparenv
# vparenv -g ILM|CLM: unit
writes the unit granularity value to firmware. This takes effect for the nPartition on the next nPartition
boot. For example, to set the granularity unit size in firmware for ILM to 512 MB and for CLM to 256 MB:
# vparenv -g ILM:512 -g CLM:256
Note that this does not set the granularity value in the vPars database. Only vparcreate sets the granularity
value in the vPars database. Typically, you would change the granularity with vparenv rather than
vparcreate if you have more than one database with differing granularities, and wish to switch to a database
with different granularity during the next vPar Monitor boot.
CAUTION The granularity values in firmware must match those in the vPars database used during the
next boot of the vPars Monitor. If the granularity values in firmware do not match those in the
vPars database, the virtual partitions of that database will not boot.
vparcreate
# vparcreate -p vpar1_name [-g ILM: unit [:y] ] [-g CLM: unit [:y] ]