IBM Support

PH08179: INCORRECT CPSM TRANSACTION ROUTING BETWEEN MASES ON TWO LPARS, WLM HEALTH REPORTED AS ZERO.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • We have installed the LNQUEUE Algorithm with the
    TRANGRP-Definition.
    Regardless of where the transactions were started, we expect
    that the workload will be like "equal" on LPAR1 and LPAR3. E.G.
    Transactions in a ratio something 2:3 per LPAR but instead we
    get a ratio of 1:25
    From the WUI view :
    "Complete active target region details" view.
    The Route Selection (edited) shows   :
    Target    Reporting Owning   z/OS WLM    Route
    region    CMAS      CMAS     Health   Completes
    CICS1111  CMAS1111  CMAS3333   100        449
    CICS2222  CMAS1111  CMAS3333   100        503
    CICS3333  CMAS1111  CMAS1111   100      29941
    CICS4444  CMAS1111  CMAS1111   100      28040
    CICS1111  CMAS3333  CMAS3333   100    1186854
    CICS2222  CMAS3333  CMAS3333   100    1232481
    CICS3333  CMAS3333  CMAS1111     0          0
    CICS4444  CMAS3333  CMAS1111     0          0
    .
    The incorrect routing appears to be linked to the fact that the
    z/OS WLM Health value is not correctly shared between each CMAS
    and shows as zero when viewed from one of the CMASes.
    Additional Symptoms and Keywords: ACRD ABENDACRD WSVE_WLMHLTH
    WAOW_SEL_IND  WAOW_SEL_NOT
    .
    

Local fix

  • The problem seems to be cured either by closing and opening
    WLMHEALTH, or restarting the affected MAS regions, or cycling
    the MAS agent with COSH then COLM. This allows any CMAS which
    is up and connected to the network to see the WLHHEALTH as 100%.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V5R4M0 and V5R5M0 users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Tasks cannot be dynamically routed      *
    *                      from certain routing regions to target  *
    *                      regions connected to a different CMAS.  *
    *                      This occurs when sysplex optimised      *
    *                      workload routing is not in effect.      *
    *                      The issue occurs because data held by   *
    *                      the CMAS where the routing region is    *
    *                      connected indicates that the target     *
    *                      region (connected to a different CMAS)  *
    *                      has a WLMHEALTH value of zero.          *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF which resolves        *
    *                 PH08179, all CMAS regions must be restart    *
    *                 to activate the fix.                         *
    *                 The restarts do not need to occur at the     *
    *                 same time.                                   *
    ****************************************************************
    A MAS region, which acts as a target region in a dynamic
    workload, connects to its CMAS and begins to open WLMHEALTH.
    Message DFHMN0115I is issued one or more times, eventually
    indicating
      +DFHMN0115I applid CICS Server z/OS WLM Health
                  percentage is now 100.
    .
    After this time, another CMAS starts and connects to the first.
    It imports the MAS directory elements known to the first CMAS.
    The MAS directory element has not been updated with the
    WLMHEALTH values, so this second CMAS builds a representation of
    this MAS assuming it has a WLMHEALTH value of zero.
    This state will not be updated further, unless the MAS closes
    and reopens WLMHEALTH, thereby broadcasting new EWHEALTH
    notifications.
    .
    Routing regions connected to this second CMAS will see the
    WLMHEALTH value of zero, and mark the target region as not
    selectable.
    The WLMATARG view of the CICSPlex SM WUI server will also
    indicate a "z/OS WLM health" value of zero, with a
    "WLM routing weight for region" of 2,147,483,647.
    

Problem conclusion

  • EYU0TIST has been updated so that the MAS directory element
    is updated with the new WLMHEALTH value when EWHEALTH events
    are processed. This ensures that other CMAS regions which
    import this data will build their representation of a MAS
    region using its last known WLMHEALTH value.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08179

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-05

  • Closed date

    2019-03-05

  • Last modified date

    2020-05-26

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI61664 UI61665

Modules/Macros

  • EYU0TIST
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R10M PSY UI61664

       UP19/03/07 P F903

  • R20M PSY UI61665

       UP19/03/07 P F903

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
27 May 2020