HP Insight Global Workload Manager 6.0 Software: User Guide

the placement rules, which are explained in the online help topic "pset / fss group tips" in the
section "Precedence of placement techniques."
If you use the psrset command to place processes in psets, gWLM is likely to move the processes
to the default pset.
Workaround To maintain the placement of a process, use gWLM's application records or user
records when creating or editing your workload definitions in gWLM. If using records is not
practical, use the gwlmplace command. However, you will have to use gwlmplace after each
redeploy of an SRD to put the processes back in the desired workloads.
iCAP compliance warning
gWLM might give the following warning:
Warning: gwlmagent cimserver error, icapd down, or icap out of
compliance. First restart cimserver. Make sure icapd is running. If
this error happens again, consult gwlmagent man page for steps to return
to compliance.
Workaround Verify that no partition changes (parmodify) are pending. If partition changes
are pending, please restart the system. Then, either consult iCAP documentation or contact HP
to return the iCAP system back to compliance.
Major issues
The following are major issues for Global Workload Manager.
gWLM fails to start with certain time zone settings
gwlmcmsd and gwlmagent can fail to start with certain time zone settings. The following message
is displayed in the gwlmagent.log.0 file or the gwlmcmsd.log.0 file when you attempt to invoke
either daemon:
Unable to call method, 'main', with signature,
'([Ljava/lang/String;)V', in class, 'com/hp/gwlm/node/Node'.
Exception in thread "main"
Workaround Use Java 1.5.0.12 or later.
gWLM commands core dump
Attempts to run gwlm commands result in core dumps when /var is full.
Workaround Make space available in /var.
Multiple time changes on CMS might render gWLM unusable
If the time on the CMS is changed to a point in the future, changes to the gWLM configuration
are made and time on the CMS is moved back to the present; gWLM will not recognize any new
changes as the latest configuration.
Workaround Backup the CMS before performing any changes to time on the CMS system.
PHKL_39587 patch required on HP-UX 11i v3 Integrity VM hosts
The HP-UX 11i v3 (B.11.31) PHKL_39587 patch is required on an HP Integrity Virtual Machines
host that is to be managed by gWLM. If the patch is not installed, communication between gWLM
and the Integrity VM host might hang for one to many hours, in which event operating virtual
machines might not be allocated the CPU resources they need.
Workaround Install the HP-UX 11i v3 (B.11.31) PHKL_39587 patch on all HP Integrity Virtual
Machines hosts.
Major issues 61