Ignite-UX Reference (March 2010, B3921-90005)
instl_adm(4) instl_adm(4)
value. For example:
Swap size in bytes: +${_hp_pri_swap+0}.
Variables that the UI does not recognize as special are represented in the Additional button available in the
UI on the Basic tab. From the Additional dialog, you may modify the values of any visible variables.
Variables do not need to be declared as their type (integer or string) is determined the first time they are
assigned and cannot be assigned a different type later. Variables may be assigned using two different con-
structs:
init _variable=value
Preceding the assignment with the init keyword means the variable is to be initialized
to the given value, but the UI is allowed to alter the value later.
_variable=value
When the init keyword is not used, the variable cannot be changed by the UI. This
type of assignment is not recommended for "visible" variables.
Variables may be assigned a list of potential values the UI may choose from in generating a selection list
for the user. This is done with the following syntax:
_variable={value1,value2,...}
Sets the list of potential values of the variable to those given and is for use by the UI only. There
is no error checking to ensure the resulting value is in the given list.
_variable+={value2,value3,...}
Using the += operator adds the given values to any existing values specified for that variable.
_variable={number..number}
Specifies a numeric range of potential values using two numbers (or integer variables/keywords)
separated by two dots.
_variable={disk[*], disk[*=X]}
Creates a list of potential values made of the hardware paths of all the disks in the first case, and
the first "X" number of disks in the second case. This is useful when you need to choose from the
list of available disks on the system.
Variable values that should be restricted to one of the list of potential values may be specified as an enumer-
ation variable using the enum keyword as follows:
enum _variable
Variables that should not be displayed in the UI should be set to invisible using the syntax:
_variable visible_if false
The help_text keyword may be used to specify a longer, more descriptive name for the variable that the
UI may use in the Additional dialog. The syntax is:
_variable help_text string
Special Variables
These are variables that are treated specially by the UI or other parts of Ignite-UX and are described as fol-
lows:
_hp_addnl_fs_free_pct
Integer variable used to control the amount of additional free space (or "breathing room") allocated
to volumes beyond the space required to load the software. If this variable is not set, it defaults to
10 (10%). See the definition for the file system size keyword attribute for more details.
_hp_cfg_detail_level
Internal string variable fundamental in the configuration file management done by Ignite-UX. It is
used primarily in the client-specific configuration files. It contains a list of option characters that
represent which aspects of the configuration file have been modified by the UI. This represents the
areas of information the configuration file written by the UI contains.
4