HP-UX Workload Manager User's Guide

Example configuration files
twice_weekly_boost.wlm
Chapter 9 327
# Purpose:
# Demonstrate a conditional allocation with a moderately complex
# condition.
# A baseball park’s server runs a number of different workloads
# for two groups: the front office and the scouting staff. The
# basic allocations are 30 shares for front_office, 30 shares for
# scouting, and the remainder (40 in this case) for OTHERS.
#
# The front office staff has one important, long running job,
# “analyze_ticket_sales”, which is usually run every Tuesday and
# Thursday. During these days, the front_office group receives a
# ‘boost’, and its allocation is 60 shares.
#
# For these regularly scheduled runs, the system administrator relies
# on HP-UX WLM to automatically re-allocate CPU resources.
#
# In addition to those regular runs, occasionally a special events
# ticket sale is held. For these sales, the job is run at an
# unscheduled time, with an allocation of 70 shares.
#
# To manually enable the front office boost for special events,
# the system administrator executes this command:
#
# % wlmsend front_office.boost_enable 1
#
# To manually disable after the special event, the system
# administrator executes this command:
#
# % wlmsend front_office.boost_enable 0
#
# The scouting staff has one particularly important, long running
# job, /opt/baseball/scouting/bin/batting_averages, which is
# usually run every Monday and Wednesday, when it receives 60
# shares.
#
# In addition to those regular runs, occasionally farm league
# makeup games are held, and the job must be run at an unscheduled
# time. During these times, the scouting group receives a manual
# ‘boost’ to 70 shares.
#
# To manually enable the scouting boost for special events,
# the system administrator executes this command:
#
# % wlmsend scouting.boost_enable 1
#
# To manually disable after the special event, the system