Date: 2005/04/13 
Revision: 1.85 


      wlmd - activate the HP-UX Workload Manager (WLM)


      wlmd -h
      wlmd -V
      wlmd -C
      wlmd [-p] [-s] [-t] [-W] [-i] -A [-l logopt[=n][,...]]
      wlmd [-p] [-s] [-t] [-W] [-i] -a configfile [-l logopt[=n][,...]]
      wlmd [-W] -c configfile
      wlmd -k


      wlmd can activate the HP-UX WLM configuration (using either the
      specified configfile or the most recent configuration) or check the
      syntax of configfile without activating the configuration.  When a
      configuration is activated, the HP-UX WLM daemon is started and a copy
      of the configuration is made. The daemon then starts all the data
      collectors specified in the configuration file. Every interval, as
      defined in the configuration file, the HP-UX WLM daemon checks for
      data from the data collectors and automatically adjusts CPU
      allocations, if needed, to better achieve the specified SLOs.

      In addition to the WLM management within systems and partitions
      provided by wlmd, WLM can manage workloads across nPartitions and
      virtual partitions (vPars) using its global arbiter wlmpard.  This
      arbiter takes input from the WLM instances on the partitions, then
      moves CPUs between partitions, if needed, to better achieve the SLOs
      specified in the WLM configuration files that are active in the
      partitions.  These partitions can be nested--and even contain FSS
      workload groups.	wlmpard also provides management of Temporary
      Instant Capacity and Pay Per Use resources. For more information, see
      the wlmpard(1M) man page.

      To start wlmd automatically at system boot, edit the file


      -h   Displays usage information and exits.  This option overrides all
	   other options.

      -V   Displays version information and exits.  This option overrides
	   all options other than -h.

      -C   Displays the most recent WLM configuration, appending two
	   commented lines that indicate the origin of the configuration.

      -i   Initializes workload group assignments, ensuring a new
	   configuration's user records and application records are used
	   when the same workload groups exist in the active and new WLM
	   Use this option when the following conditions are met:

	   +  You have workload groups that are in both the active WLM
	      configuration and the new configuration that you want to

	   +  You are going to activate the new configuration without first
	      stopping the WLM daemon

	   Without -i, if a currently running process is in a workload group
	   that also exists in the new configuration, the process stays in
	   that group regardless of application records or user records in
	   the new configuration.

	   The -i option is only valid with the -a or -A options.

      -p   Causes WLM to run in passive mode. In this mode, you can see how
	   WLM will approximately respond to a configuration--without the
	   configuration actually taking control of your system. Using this
	   mode allows you to analyze various items in your configuration.
	   For more information on this mode, including its limitations, see
	   the wlm(5) man page.

	   To see how the configuration would affect your workloads, use the
	   WLM utility wlminfo.

	   NOTE: Do not rely on prmlist or prmmonitor to observe changes
	   when using passive mode. These utilities will display a
	   configuration WLM uses to create the passive mode. However, you
	   can use prmmonitor to gather CPU usage data.

	   The -p option must be used with either the -a or -A options.

      -s   Causes WLM to run in secure mode--assuming you have distributed
	   security certificates to the systems in question. For more
	   information on using security certificates, see the wlmcert(1M)
	   man page.

	   You can start wlmd in secure mode at boot time by editing the
	   file /etc/rc.config.d/wlm.

      -t   Generates comma-separated audit data files. These files are
	   placed in the directory /var/opt/wlm/audit/ and are named
	   wlmd.monyyyy, with monyyyy representing the month and year the
	   data was gathered. You can access these files directly or through
	   the wlmaudit command.  (wlmaudit has audit data to display only
	   when you use the -t option.) For information on wlmaudit or on
	   the format of the data files, see the wlmaudit(1M) man page.

	   NOTE: Be sure to set wlm_interval in your WLM configuration file
	   as indicated in the wlmconf(4) man page when you use the -t

      -A   Activates a copy of the most recent WLM configuration.

      -W   Prints warning messages found when parsing the configuration file
	   as error messages. The -W option is only valid with the -A, -a,
	   and -c options.

      -a configfile
	   Activates the configuration specified in the file configfile.  If
	   configfile is not valid, an error message is displayed, and wlmd

      -c configfile
	   Checks the configuration specified in the file configfile for
	   syntax errors. The current configuration is not affected.

      -l logopt
	   Causes wlmd to log statistics to the file /var/opt/wlm/wlmdstats.
	   Use this data for tuning your WLM configuration. Acceptable
	   values for logopt are:

	   all	     Logs statistics for every group, host, metric, and SLO
		     every WLM interval

	   all=n     Logs statistics for every group, host, metric, and SLO
		     every n WLM intervals

	   group     Logs group statistics every WLM interval

	   group=n   Logs group statistics every n WLM intervals

	   host	     Logs host statistics every WLM interval

	   host=n    Logs host statistics every n WLM intervals

	   metric    Logs metric statistics every WLM interval

	   metric=n  Logs metric statistics every n WLM intervals

	   slo	     Logs SLO statistics every WLM interval

	   slo=n     Logs SLO statistics every n WLM intervals

	   The -l option is ignored unless used with the -a or -A option.
	   When the same logopt is specified multiple times, the last one
	   specified takes precedence.

	   Combine multiple values separating them with a comma. The
	   following combination requests all the statistics--with the
	   exception of the host statistics, which have been turned off:
	   -l all,host=0

	   NOTE: In the wlmdstats file, the cpuuse value represents the
	   amount of CPU the group used in the last WLM interval. However,
	   the group's cpuent value (CPU entitlement or allocation) is from
	   the current WLM interval. As a result, comparisons of the numbers
	   could lead mistakenly to the conclusion that the usage exceeds
	   the entitlement.

	   You can use the wlminfo command to review statistics from
	   /var/opt/wlm/wlmdstats. For example, to view SLO data, enter:

	   % wlminfo slo -o

	   In place of slo, you can also use group, host, or metric.  For
	   more information on wlminfo, see the wlminfo(1M) man page.

	   You can enable automatic trimming of the wlmdstats file by using
	   the wlmdstats_size_limit tunable in your WLM configuration. For
	   more information, see the wlmconf(4) man page.

      -k   Kills any running instance of wlmd.	Use this option to shutdown
	   HP-UX Workload Manager.


      wlmd -c returns exit status 0 if no errors occur, or 1 if there are

      wlmd -A and wlmd -a return exit status 0 if no errors occur or nonzero
      if the configuration file is invalid or there were errors while
      activating the configuration.

      wlmd -k returns exit status 0 if no errors occur or nonzero if the
      running wlmd could not be confirmed as killed.


      Check the configuration file for syntax errors:

	   wlmd -c configfile

      Activate the specified configuration file and move all currently
      running configured applications and user processes to their assigned

	   wlmd -i -a configfile

      Activate the specified configuration file, leave all currently running
      application and user processes in their current groups, and collect
      logging statistics every fifth WLM interval:

	   wlmd -a configfile -l slo=5


      Do not use prmconfig -r while wlmd is active.


      HP-UX WLM depends on PRM--see the release notes
      (/opt/wlm/share/doc/Rel_Notes) for version requirements. HP-UX WLM
      uses the PRM API to dynamically adjust the CPU allocations of the PRM
      groups (known as PSET workload groups and FSS workload groups in the
      context of HP-UX WLM) to which managed workloads are assigned. HP-UX
      WLM does this to achieve the specified service-level objectives

      HP-UX WLM also uses the PRM API to set memory and disk bandwidth
      allocations, if defined. Furthermore, the PRM API is used when
      dynamically adjusting memory allocations (if defined) to compensate
      for inactive workload groups (workload groups with no active SLOs).


      wlmd was developed by HP.


      If you would like to comment on the current HP-UX WLM functionality or
      make suggestions for future releases, please send email to:


      /etc/rc.config.d/wlm	      system initialization directives

      /var/opt/wlm/msglog	      default message log

      /var/opt/wlm/wlmdstats	      optional statistics log

      /var/opt/wlm/.wlmd.LCK	      process mutual exclusion lock file

      /var/opt/wlm/.wlmd.cfg.CKP      copy of most recent configuration file


      wlmaudit(1M), wlmemsmon(1M), wlminfo(1M), wlmpard(1M), libwlm(3),
      wlmconf(4), wlm(5)

      HP-UX Workload Manager User's Guide (/opt/wlm/share/doc/WLMug.pdf)

      HP-UX Workload Manager homepage (