Managing Serviceguard Nineteenth Edition, Reprinted June 2011

See “Parameters for Configuring EMS Resources” (page 128) for more information and example.
resource_polling_interval
How often, in seconds, the resource identified by resource_name (page 233) is to be monitored.
Default is 60 seconds. The minimum value is 1. (There is no practical maximum.)
resource_start
Specifies when Serviceguard will begin monitoring the resource identified by resource_name.
Valid values are automatic and deferred.
automatic means Serviceguard will begin monitoring the resource as soon as the node joins the
cluster.deferred means Serviceguard will begin monitoring the resource when the package starts.
resource_up_value
Defines a criterion used to determine whether the resource identified by resource_name is up.
Requires an operator and a value. Values can be string or numeric. The legal operators are =,
!=, >, <, >=, or<=, depending on the type of value. If the type is string, then only = and != are
valid. If the string contains white space, it must be enclosed in quotes. String values are
case-sensitive.
The maximum length of the entire resource_up_value string is 1024 characters.
You can configure a total of 15 resource_up_values per package. For example, if there is
only one resource (resource_name) in the package, then a maximum of 15
resource_up_values can be defined. If two resource_names are defined and one of them
has 10 resource_up_values, then the other resource_name can have only 5
resource_up_values.
concurrent_vgchange_operations
Specifies the number of concurrent volume group activations or deactivations allowed during
package startup or shutdown.
Legal value is any number greater than zero. The default is 1.
If a package activates a large number of volume groups, you can improve the package’s start-up
and shutdown performance by carefully tuning this parameter. Tune performance by increasing
the number a little at a time and monitoring the effect on performance at each step; stop increasing
it, or reset it to a lower level, as soon as performance starts to level off or decline. Factors you
need to take into account include the number of CPUs, the amount of available memory, the HP-UX
kernel settings for nfile and nproc, and the number and characteristics of other packages that
will be running on the node.
NOTE: If you set concurrent_vgchange_operations to a value greater than 1, you may
see messages such as this in the package log file:
Cannot lock “/etc/lvmconf//lvm_lock” still trying...”
This is an informational message that can be safely ignored.
enable_threaded_vgchange
Indicates whether multi-threaded activation of volume groups (vgchange -T)is enabled. New
for modular packages. Available on HP-UX 11i v3 only.
Legal values are zero (disabled) or 1 (enabled). The default is zero.
Set enable_threaded_vgchange to 1 to enable vgchange -T for all of a package’s volume
groups. This means that when each volume group is activated, physical volumes (disks or LUNs)
are attached to the volume group in parallel, and mirror copies of logical volumes are synchronized
234 Configuring Packages and Their Services