 |
» |
|
|
|
Using Workload Manger, you can create an essentially unlimited
number of user-defined workgroups for your system. When you create a
workgroup, you specify three kinds of information: the workgroup name,
membership criteria, and scheduling characteristics. You can use the NEWWG command to add a new workgroup to the current
configuration or to replace the entire workgroup configuration with a new one.
For instructions to replace the workgroup configuration, read “
Creating a New Workgroup Configuration” later in this chapter. To create a new workgroup | |
To add a workgroup to the existing configuration, use the NEWWG command
to specify the name, one or more membership criteria, and the scheduling
characteristics. The syntax of the NEWWG command is:
NEWWG [WORKGROUP=]workgrp
{ [;MEMB_LOGON=]logon
[;MEMB_PROGRAM=]program_file
[;MEMB_QUEUE=]queue_attribute }
[;BASE=]base [;LIMIT=]limit
[[;MINQUANT=]min] [[;MAXQUANT=]max]
[[;BOOST=] {DECAY
OSCILLATE}]
[[;TIMESLICE=]tslice]
[[;MINCPUPCT=]minpercent] [[;MAXCPUPCT=]maxpercent]
[[;POSITION=]existingwg]
|
For more detailed information on this command, refer to Chapter 5,
“Commands Reference”. | | | |  | NOTE:
To replace the existing workgroup configuration by specifying an
indirect file on the NEWWG command line, you use a different
syntax. For information, see “Creating a New Workgroup
Configuration”
in this chapter.
| | | | |
For example, to create a new user-defined workgroup named
Program_Development whose base and limit priorities are 160 and 170
(respectively) and with a boost property of OSCILLATE, enter:
:NEWWG Program_Development; memb_program= (editor.pub.sys,&
qedit.@.@, hpedit.@.@);memb_logon=("nm@,@.mytest"); base=&
160; limit= 170; boost= oscillate
|
Or, using positional parameters instead of keywords, you would enter:
:NEWWG Program_Development, "nm@,@.mytest", (editor.&
pub.sys,qedit.@.@,hpedit.@.@),,160,170,,,oscillate
|
The membership criteria must appear in the order MEMB_LOGON,
MEMB_PROGRAM and MEMB_QUEUE when the keywords
are not specified and, in this case, since MEMB_QUEUE isn't specified,
a comma is used as a placeholder.
The ampersand character (&) appears at the end of the command lines
in the examples above to indicate continuation. If you type the command on
one single line (so that it wraps), omit the ampersand. For a process to become a natural member of the Program_Development
workgroup (that is, one that naturally meets the membership criteria), both
of the following conditions must be true: The user (or job) must log onto any user name in the account mytest,
with a job or session name that begins with nm. For example,
a user logging on as nmbuild1,pat.mytest qualifies.
Or, a job identified as nmbeta,doug.mytest qualifies. The user or job logging on must run one of three editing
programs editor.pub.sys, qedit.@.@, or hpedit.@.@.
To place the workgroup in the ordered list | |
The workgroups on your system are maintained in an ordered list.
When the Workload Manager assigns a process to a workgroup, it searches
the list of workgroups on your system and places the process into the
first workgroup in which it fits. Since workgroup
membership dictates how a process is scheduled, which workgroup it
falls into is critical. When you create new workgroups, you can use the POSITION
parameter to determine where the workgroup is positioned in the
ordered list. You should order workgroups so that those with the
most specific membership criteria appear first and those with more
general membership criteria follow. For example, to create a
workgroup named Payroll_online for online users of the Payroll
account that appears ahead of the Program_Development
workgroup (created in the preceding example), enter:
:NEWWG Payroll_online; memb_logon= (@.Payroll); &
base= 170; limit= 190; position= Program_Development
|
Or, to use positional parameters, you enter the command this way:
:NEWWG Payroll_online, @.Payroll,,,170,190,,,,,,,&
Program_Development
|
Note that you must use the comma as a placeholder for the membership criteria
you are not specifying. The ampersand character (&) appears at the
end of the command lines in the examples above to indicate continuation. For a process to become a natural member of the Payroll_online workgroup,
the user must logon to the Payroll account with any user name.
(The user can also
choose a session name. Since it isn't specified in the membership criteria, any
session name is considered a match.) The Payroll_online workgroup has a
base priority of 170, a limit of 190, the default
minimum and maximum quantum of 1 and 2000 milliseconds, the default
boost property (DECAY), and the default timeslice of 200 milliseconds. For more conceptual information and an example of determining workgroup
membership, read “To understand the importance of workgroup
order” and “How workgroup membership is determined: an
example”, in Chapter 2. To display the workgroup | |
To display information about all workgroups on the system, you use
the SHOWWG command. You can choose to display information in any
of the formats available: SUMMARY, DETAIL, PROCS, or
WGFILE. If you do not specify a format (as shown below), the
SHOWWG command defaults to the SUMMARY format. For example, assuming that you had just
created the two workgroups shown in the previous examples, entering
the SHOWWG command would produce this information:
:SHOWWG
-----QUANTUM----- TIME CPU %
WORKGROUP BASE LIMIT MIN MAX ACTUAL BOOST SLICE PROCS MIN MAX
------------------- ---- ----- ----- ----- ------ ----- ----- ----- --- ---
Payroll_online 170 190 1 2000 0 DECAY 200 0 0 100
Program_Development160 170 1 2000 0 OSC 200 0 0 100
AS_Default 30 99 N/A N/A N/A N/A 1000 14 N/A N/A
BS_Default 100 150 N/A N/A N/A N/A 1000 30 N/A N/A
CS_Default 152 200 1 2000 4 DECAY 200 21 N/A N/A
DS_Default 202 238 2000 2000 0 DECAY 200 0 N/A N/A
ES_Default 240 253 2000 2000 0 DECAY 200 0 N/A N/A
|
|
