HP Tru64 UNIX Technical Updates for the Version 5.1B and Higher Operating System and Patches (February 2010)

reserved component names. The following table lists the reserved component names used by
EVM:
CommentsFollowing ValueComponent Name
The name of the processor set
managed category that was created or
removed.
Processor set category_catname
The system host name, referred to by
the event, which may not be the
posting host.
System host name_hostname
The name of the hardware component
that has undergone a state change.
Hardware component_hwcomponent
Identifies events referring to hardware
device IDs.
Hardware ID_hwid
The address of a physical memory
location experiencing a problem.
Memory address_physical_address
The proccess ID involved in a process
set manager operation.
Process ID_pid
The name of a process that was started
or terminated.
Process name_process
sysman_menu(8) Correction (Nov. 2002)
The following notes apply to the sysman_menu(8) reference page:
• The host option is not supported.
• The menu flag cannot be used with the list flag (/usr/sbin/sysman [menu] list).
• Examples 5 and 6 are not valid.
• Example 4 does not specify a cluster member for the focus option.
Corrections to Manuals
Tuning Guide Table Lists Tools in Error (Sept. 2005)
Table 5.1 of the System Configuration and Tuning guide lists two tools to aid in detecting poor NFS
performance that should have been removed from the table. Attempting to use these tools causes
no harm, but does result in error messages being generated. Those tools and the error messages
they generate are as follows:
(dbx) p nfs_sv_active_hist
"nfs_sv_active_hist" is not defined or not active
(dbx) p nchstats
can't evaluate a Block
Information on Default Private Region Size Is Incorrect in LSM Manual (March 2005)
The second paragraph of Section 1.1.2 of the Logical Storage Manager manual (September 2002
version), incorrectly states that the default private region size guarantees space for a configuration
database that tracks 8192 objects (LSM disks, subdisks, plexes, and volumes). The statement
assumes that the private region contains only the configuration database and does not account
for the kernel change log and other LSM metadata.
To determine the size of the configuration database it is necessary to issue the voldg list
diskgroupname command. For example:
# voldg list rootdg
Group: rootdg
dgid: 1105649937.1026.hero
Documentation Corrections 43