Define WLM service classes


BMC AMI Ops Automation for Batch ThruPut assigns WLM Service Classes at job selection, solely to reflect the amount of execution resources to be assigned to each batch workload.

We suggest you start with the current WLM batch Service Classes and create two parallel sets for use within BMC AMI Ops Automation for Batch ThruPut, one for General Services and one for Production Services. Modify or add to them as follows:

  • Considering each set of Service Classes, use names that are different from any of the current ones.
  • These WLM Service Classes must be dedicated to BMC AMI Ops Automation for Batch ThruPut. You must not assign these new WLM Service Classes using the classification rules in the WLM Policy. You simply define them in WLM.
  • As a best practice, we suggest you define five WLM Service Classes for each queue. (You will map these Services Classes to the BMC AMI Ops Automation for Batch ThruPut importance levels).
  • You should use velocity goals; if discretionary goals are specified, use them only for the Service Classes with the lowest BMC AMI Ops Automation for Batch ThruPut importance levels. Your velocity goals should not take queue time into account, since BMC AMI Ops Automation for Batch ThruPut uses JES2 initiators.
  • You should favor a single performance period, as this allows for more accurate prediction by BMC AMI Ops Automation for Batch ThruPut of the effect on adding more work in a given Service Class.
Warning

Important

Using multiple periods requires BMC AMI Ops Automation for Batch ThruPut to take a "blended" view of the Service Class performance. If multiple periods must be used, try to select a first period duration such that more than 95% of jobs using that Service Class complete in the first period

Together with your WLM specialist, you determine the values right for your installation. As a best practice, the Service Classes for the example start their names with 'TM' in the hopes they would not conflict with the names of other WLM Service Classes in use now or in the future.

Keep in mind that any velocity <=30 can result in cycles stolen for discretionary work.

BMC AMI Ops Automation for Batch ThruPut Importance

Workload

WLM Service Class

WLM Veolocity

WLM Importance

Production Services Queue

Premium

For highest importance workload when it becomes critical

TMPS0

60

3

1

For highest importance workload

TMPS1

50

3

2

For high importance workloads.

TMPS2

40

3

3

For medium importance workloads

TMPS3

30

3

4

For lower importance workloads.

TMPS4

30

4

5

For lowest importance workloads

TMPS5

25

4

General Services Queue

1

For highest importance workload

TMGS1

40

3

2

For high importance workloads.

TMGS2

30

3

3

For medium importance workloads

TMGS3

30

4

4

For lower importance workloads.

TMGS4

25

4

5

For lowest importance workloads.

TMGS5

15

5

Remember to activate your new WLM Policy.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation for Batch ThruPut 22.4