Open topic with navigation

ibi™ Open Data Hub for Mainframe Connectors 1.0.8

# Workload Manager

Although the server may run in a specific performance group, transactions submitted by server agents may perform differently than the server by adding the following keyword to edaserve.cfg:

    wlm_enclave_trname = WLM_transaction_name

where:

WLM_transaction_name

Can be up to 8 characters.

This is a service-level keyword.

Using this setting, the task will join a Workload Manager (WLM) enclave when a request starts, and leave the enclave when the request finishes. This gives WLM control of the dispatching priority of the task. The transaction rules defined on WLM will determine the default service class assigned to this transaction, and that service class will determine how the request runs.

This feature helps to balance a workload so that a long request will not affect a short request. This can be achieved through WLM rules designed to lower the priority of a long request after a certain period of time. Without this feature, all requests share the region priority.

The transaction name passed in this keyword must match one defined in the WLM Classification Rules for the Job Entry Subsystem (JES). A corresponding WLM Service Class pointed to by this rule will then be associated with this service.

The classification rules for JES must be used even if the server is started as a started task. The subtasks are always run under JES.

For example, you would include the following in edaserve.cfg:

    SERVICE = DEFAULT

    BEGIN

    wlm_enclave_trname = IWAYFAST

    .

    .

    .

    END

The WLM definition is:

    Subsystem Type JES - Batch Jobs

    Classification:

    Default service class is PRDBATLO

    There is no default report class.

      Qualifier  Qualifier      Starting       Service   Report

    # type       name           position       Class     Class

    - ---------- -------------- ---------      --------- --------

    1 TN         IWAYFAST                      EDAQRYHI

WLM subrules (levels 2 and above) are supported. For a server request to join an enclave in a particular service class, the names of all rule qualifiers below our transaction name are checked.

For example, consider the following WLM definition:

    Subsystem Type JES - Batch Jobs

    Classification:

    Default service class is PRDBATLO

    There is no default report class.

      Qualifier Qualifier     Starting Service  Report

    # type      name          position Class    Class

    - --------- ------------- -------- -------- --------

    1 SSC       PRDMVS                 PRDDFLT

    2 . TN      . IWAYFAST             EDAQRYHI

In this particular case, the qualifier 1 type is SSC (Subsystem Collection), and a server request will only join the enclave IWAYFAST if it is running on a particular LPAR in the SYSPLEX. This qualifier (PRDMVS) must match the XCF group definition: issue $DMASDEF (for JES2) and check the value of XCFGRPNM field.

You can handle WLM scheduling environments by defining them to WLM and then adding the JOB statement parameter SCHENV=xxxxx to the ISTART JCL.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

ibi™ Open Data Hub for Mainframe Connectors

Copyright © 2021-2025. Cloud Software Group, Inc. All Rights Reserved.