HP PRM Version C.03.02.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

PRM Release Notes
Known problems and workarounds
Chapter 1 21
Workaround
On HP-UX 11i v3 (B.11.31), be sure to use WBEM Services A.02.05 or later.
For HP-UX 11i v1 (B.11.11) and HP-UX 11i v2 (B.11.23), WBEM Services
A.02.05 is scheduled for a December 2006 release.
Until then, 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.
prm3d consumes excessive resources
Issue
Because of a pthread issue triggered by Java, prm3d can occasionally become
a runaway process, consuming excessive CPU resources.
Workaround
If you notice this condition, a short-term solution is to stop prm3d:
# /opt/prm/bin/prm3d -stop
prm3d is used only by the PRM GUI, xprm. If you do not plan on using xprm,
leave prm3d stopped. If you will be using xprm, restart prm3d:
# /opt/prm/bin/prm3d
The long-term solution to this problem is to patch the pthread library. Also,
Java 1.4.1 itself had an issue with its use of pthreads that has been
addressed in newer versions. (HP-UX with Java 1.4.2.)
Using Java requires certain patches. For the most up-to-date information on
patches needed for Java, visit http://www.hp.com/go/java. Look for patches
that are required for or recommended for Java JRE 1.4.2.
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.