Defining the started tasks to z/OS Workload Manager (WLM)
This is part of the larger task of customizing your z/OS® environment.
About this task
With z/OS workload management (WLM), you define performance goals and assign a business importance to each goal. You define the goals for work in business terms, and the system decides how much resource, such as CPU and storage, should be given to it to meet the goal. Workload Manager constantly monitors the system, and adapts processing to meet the goals.
IBM® Integration Bus automatically defines the JOBACCT token for each integration server started, so that the integration node systems administrator can use WLM classification to map the JOBACCT token to specific Service and Report classes.
Each integration server can be assigned to a different Service and Report class. Whenever an integration server address space is started, the STEPNAME is assigned to the JOBACCT token.
an integration server address space is started on z/OS, the STEPNAME is derived from
the integration server label; the STEPNAME is defined as the last
eight characters. Any characters that are not valid for a STEPNAME
are replaced with the
example, an integration server address space with the label
has a STEPNAME of
IONGROUP and assigns this same
value to the JOBACCT.
The STEPNAME/JOBACCT is not guaranteed to be unique across multiple integration server address spaces on the same LPAR. If you require a unique STEPNAME/JOBACCT across multiple integration servers, you must use a suitable integration server naming standard.