instl_adm.4 (2012 03)

i
instl_adm(4) instl_adm(4)
An integer may be a hexadecimal value specified using the prefix
0x followed by a value using the
hexadecimal digits
0 through 9, a
through f, and A through F.
An integer may be a decimal value and may have a
KiB, MiB, GiB or suffix multiple. For compa-
tibility with prior Ignite-UX releases a
KB,
MB, GB or suffix multiple may be used instead. These
multiples are
KiB or KB for 2ˆ10, MiB
or MB for 2ˆ20, GiB or GB for 2ˆ30, and TiB or TB for
2ˆ40. According to International System of Units (SI) notation the preferred multiples are
KiB,
MiB, GiB, and Note that Ignite-UX does not support 10ˆ3, 10ˆ6, 10ˆ9, and 10ˆ12 decimal multiples.
Further information about binary multiples is available from Commission Electrotechnique Interna-
tionale (IEC) and National Institute of Standards and Technology (NIST).
String:
A string is text surrounded by double-quote (") characters. If a double quote is needed inside the
string, it must preceded with the backslash (\) character. No other characters, including newlines,
need to be preceded with a backslash character.
Most keywords also allow for complex strings (cplx_string ). Complex strings may be regular quoted
strings or may be a combination of multiple strings, variable names, mathematical expressions, or
system-attribute keywords enclosed with ${} combined using the "+" operator. For example: "The
system contains " + ${num_disks} + " disk drives".
A complex string may also have a format string associated with it to allow specific formatting to be
performed when converting the value into a string. The format string is passed directly to
sprintf. The syntax to specify a format string is as follows:
mod_kernel += "maxdsiz " + ${"0X%X" _maxdsize_var}
where "0X%X" is the format string and causes the value of the variable to be converted to an upper-
case hexadecimal value.
Boolean:
The boolean constants are: true/TRUE and false/FALSE.
I/O Constant:
Ignite-UX provides supports use of several different types of special constants related to I/O for use
in conditional expressions and setting variables. A hardware path is a common example of one of
these I/O types. More detailed information about these types is provided in the section on I/O
Configuration.
Variables
The Ignite-UX configuration files support string and integer variables. Variable names must begin with
an underscore (
_) character followed by one or more characters from the set a-z, A-Z, 0-9, or underscore.
Integer variables and numeric values are stored internally in KB units when possible. This allows for
larger than 4GB values to be operated on and still use a 32-bit value internally. However, the parser con-
verts a value to regular units when addition or subtraction is performed using a non-KB value. The
parser does not allow a combination of KB and non-KB values to be listed as potential values for a vari-
able. When using a variable as part of cplx_string , you may need to add 0 (zero) to the value to force
conversion to a non-KB 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
constructs:
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:
HP-UX 11i Version 3: March 2012 − 3 − Hewlett-Packard Company 3