21.02.2013 Views

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

AIX 5L Problem Determination - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

This manual assignment can be done either by a WLM command, which<br />

could be invoked directly or through SMIT or Web-based System Manager, or<br />

by an application, using a function of the WLM Application Programming<br />

Interface. Manual assignment overrides automatic assignment.<br />

10.5.2 Automatic assignment<br />

The automatic assignment of processes to classes uses a set of class<br />

assignment rules specified by a WLM administrator. There are two levels of<br />

assignment rules:<br />

► A set of assignment rules at the WLM configuration level used to determine<br />

which superclass a given process should be assigned to.<br />

► A set of assignment rules at the superclass level used to determine which<br />

subclass of the superclass the process should be assigned to.<br />

The assignment rules at both levels have exactly the same format.<br />

When a process is created by fork, it remains in the same class as its parent.<br />

Usually, reclassification happens when the new process calls the system call<br />

exec. In order to classify the process, WLM starts by examining the top level<br />

rules list for the active configuration to find out which superclass the process<br />

should belong to. For this purpose, WLM takes the rules one at a time, in the<br />

order they appear in the file, and checks the current values for the process<br />

attributes against the values and lists of values specified in the rule. When a<br />

match is found, the process will be assigned to the superclass named in the first<br />

field of the rule. Then the rules list for the superclass is examined in the same<br />

way to determine which subclass of the superclass the process should be<br />

assigned to. For a process to match one of the rules, each of its attributes must<br />

match the corresponding field in the rule. The rules to determine whether the<br />

value of a process attribute matches the values in the field of the rules list are as<br />

follows:<br />

► If the field in the rule has a value of hyphen (-), any value of the corresponding<br />

process attribute is a match.<br />

► If the value of the process attribute (for all the attributes except type) matches<br />

one of the values in the list in a rule, and it is not excluded (prefaced by an<br />

exclamation point (!)), it is considered a match.<br />

► When one of the values for the type attribute in the rule is comprised of two or<br />

more values separated by a plus sign (+), a process will be a match for this<br />

value only if its characteristics match all the values mentioned above.<br />

As previously mentioned, at both superclass and subclass levels, WLM goes<br />

through the rules in the order in which they appear in the rules list, and classifies<br />

the process in the class corresponding to the first rule for which the process is a<br />

284 <strong>IBM</strong> ^ Certification Study Guide - <strong>AIX</strong> <strong>5L</strong> <strong>Problem</strong> <strong>Determination</strong> Tools and Techniques

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!