HP-UX Workload Manager Toolkits User's Guide

HP-UX WLM Duration Management Toolkit and HP-UX WLM Toolkit for Base SAS Software
How do I use DMTK / SASTK?
Chapter 6 115
Many applications’ discovery commands can be simple shell scripts.
Example discovery commands are included with DMTK and SASTK.
NOTE If your target application is started by a script, be sure that your
discovery command looks for the executable rather than the script that
starts it.
When first setting up a discovery command, just focus on getting the
target application’s PID to standard out. For now, you can enter a value
of 0 (zero) for both the profile value and for the desired duration:
$PID 0 0
wlmdurdc will display the profile value for the application in syslog
(/var/adm/syslog/syslog.log). You can then have your discovery command
report the target application’s actual profile value and your desired
duration for the application.
For an example discovery command showing one way to get the PID, see
the “Example discovery command” on page 123. For example discovery
commands that are specific to SAS, see:
/opt/wlm/toolkits/sas/examples/
Step 2. Define WLM workload groups in which to place your target applications
In a WLM configuration file, say configfile, define a WLM workload
group for each target application.
NOTE For optimal duration management, place each application for which
you’ll be managing its duration in its own workload group. This ensures
that the resources being allocated by WLM for the application’s
management are used only by that application.
For example, if we have two groups GroupA and GroupB for our target
applications app1 and app2, the group definitions would be:
prm {
groups = GroupA : 1, GroupB : 2;
}