HP PRM Version C.03.06 release notes - (March 2012)

No PSET PRM group data from GlancePlus
Issue GlancePlus has not been enhanced to recognize processor sets. If you have
defined PRM groups based on processor sets in your PRM configuration,
GlancePlus returns no information for these PRM groups.
Workaround For configurations with processor sets defined, use the prmmonitor command
instead of GlancePlus.
Colons in alternate names
Issue You get a message similar to:
Cannot parse configuration record at line 3 -- contains
too many fields. Remove some fields or remove record.
(PRM-2249) PRM is not configured.
This may be due to using colons (:) in extended regular expressions. Starting with
PRM C.03.02, you can use extended regular expressions in the alternate names
field of application records. However, you cannot use colons (:) in these extended
regular expressions, as they are used as field separators by PRM.
Workaround Remove colons from these extended regular expressions.
Spaces when using the SMH interface
Issue When using PRM’s interface in SMH, spaces may be collapsed to a single space
or removed. For example, consecutive spaces in alternate names that use extended
regular expressions are reduced to single spaces. Spaces at the ends of
configuration file names are removed, preventing the files from appearing in the
SMH listing of files. Spaces used in names of users or volume groups may also
be affected.
Workaround Use WBEM Services A.02.05 or later.
Alternatively, remove trailing spaces in filenames for configuration files you want
to use in SMH. For alternate names, use “[ ]*” to handle zero or more spaces;
use “[ ]+” to handle one or more spaces. Be careful of spaces used elsewhere.
Alternate names have limit on length
Issue Due to a kernel limitation:
• On HP-UX 11i v1 (B.11.11), the PRM application manager cannot identify
alternate names that are greater than 64 characters in length, or scripts
where the combination of the alternate name and command name is greater
than 64 characters.
• On HP-UX 11i v2 (B.11.23), the PRM application manager cannot identify
alternate names that are greater than 128 characters in length, or scripts
where the combination of the alternate name and command name is greater
than 128 characters.
Workaround Be sure these names do not exceed 64 characters on HP-UX 11i v1 or
128 characters on HP-UX 11i v2.
High CPU load may reduce CPU entitlements of PRM groups with few
processes
Issue
NOTE: With Hyper-Threading disabled, each core is seen as a CPU. With
Hyper-Threading enabled, each core can be seen as multiple, logical CPUs.
16 Known problems and workarounds