Using HP-UX Workload Manager: A quick reference

10. Note what messages a WLM shutdown produces:

Run the tail command again:

# tail -f /var/opt/wlm/msglog

You will see messages similar to the following:

08/29/06 09:06:55 [I] (p6128) wlmd 6128 shutting down

08/29/06 09:06:55 [I] (p7235) wlmd terminated (by request)

11. Stop the loop.pl, loop2.pl, and loop3.pl perl programs.

Where is HP-UX Workload Manager installed?

The following table shows where WLM and some of its components are installed.

Item Installation path

WLM /opt/wlm/

WLM Toolkits /opt/wlm/toolkits/

Manpages for WLM and its toolkits /opt/wlm/share/man/

If you are using WLM configurations that are based on the Process Resource Manager (PRM) product,

you must install PRM.

Can I see how HP-UX Workload Manager will perform

without actually affecting my system?

WLM provides a passive mode that enables you to see approximately how WLM will respond to a

given configuration—without putting WLM in charge of your system resources. Using this mode,

enabled with the -p option to wlmd, you can gain a better understanding of how various WLM

features work. In addition, you can verify that your configuration behaves as expected—with minimal

effect on the system. For example, with passive mode, you can answer the following questions:

• How does a cpushares statement work?

• How do goals work? Is my goal set up correctly?

• How might a particular cntl_convergence_rate value or the values of other tunables affect

allocation change?

• How does a usage goal work?

• Is my global configuration file set up as I wanted? If I used global arbitration on my production

system, what might happen to the CPU layouts?

• Is a user’s default workload set up as I expected?

• Can a user access a particular workload?

• When an application is run, which workload does it run in?

• Can I run an application in a particular workload?

• Are the alternate names for an application set up correctly?

For more information on how to use the passive mode of WLM, as well as explanations of how

passive mode does not always represent actual WLM operations, see the “PASSIVE MODE VERSUS

ACTUAL WLM MANAGEMENT” section in the wlm(5) manpage.