IBM Support

PK89461: SYSPLEX OPTIMIZED WORKLADS REMAIN FROZEND AFTER CMAS OUTAGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using a Sysplex Optimized workload, a CMAS may remain frozen
    in the workload if it is restarted.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: -  When a workload becomes frozen       *
    *                         because a CMAS terminates while CPSM *
    *                         WLM routing and target regions       *
    *                         connected to it are active, if at    *
    *                         least one target region is still     *
    *                         active when the CMAS is restarted,   *
    *                         the workload may not be unfrozen.    *
    *                                                              *
    *                      -  When WLMAWTOR records are requested  *
    *                         through the API or WUI, the OWSTATE  *
    *                         attribute may display as INACTIVE    *
    *                         for a routing region even though     *
    *                         Sysplex optimization is active for   *
    *                         the region, if the region is         *
    *                         connected to a CMAS other than the   *
    *                         CMAS to which the API program or WUI *
    *                         server connected.                    *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes and MASes must be           *
    *                 restarted.  Note that the restarts do not    *
    *                 need to occur at the same time.              *
    ****************************************************************
    -  When a CMAS termination causes a workload to become frozen,
       all target regions connected to the CMAS at the time of its
       termination have a flag turned on in their EYURWAOR control
       block to indicate that they were lost due to their CMAS being
       terminated.  When the CMAS is restarted, and the still active
       target regions re-connect to the CMAS, the flag is used to
       unfreeze the workload.  A logic error in module EYU0WMWD
       (WMWD) causes the flag to be reset before it can be used to
       unfreeze the workload, resulting in the workload remaining
       frozen.
    
    -  A CMAS considers a routing region to be either local
       (connected to the CMAS) or remote (connected to another
       CMAS).  For local routing regions, method EYU0WMTJ (WMTJ) is
       called to perform Workload Join of the routing region after
       the region is Topology Connected to the CMAS.
    
       For remote routing regions, WMTJ is called either when the
       CMAS imports the workload, or if the region is not active at
       that time, when the region is Topology Joined to the CMAS.
    
       If a CMAS is importing the workload at the same time it is
       performing Topology Join for one of the routing regions
       associated with the workload, it is possible that WMTJ may be
       called for workload import before Toplogy Join completes for
       the region.  When that occurs, the region's CICS version will
       not be set in the CICS system descriptor block (CSDB) for the
       region.  As a result, WMTJ will treat the region as a
       pre-CICS V6R6M0 region, and will not set the OWSTATE
       attribute to ACTIVE.
    

Problem conclusion

  • -  WMWD has been updated to not clear the EYURWAOR lost contact
       flag before it can be interrogated when a CMAS connects to a
       target region.
    
    -  WMTJ has been updated to not perform Workload Join for a
       remote routing system until after Topology Join has occurred.
       This will ensure that the region's CICS version will be set
       in the CSDB before WMTJ runs.
    

Temporary fix

  • *********
                * HIPER *
                *********
    FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK89461

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    60M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-22

  • Closed date

    2009-08-18

  • Last modified date

    2009-09-02

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

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

    UK49315

Modules/Macros

  • EYU0WMAA EYU0WMAT EYU0WMEV EYU0WMTJ EYU0WMWD
    EYU0WNHD EYU0WNRS EYU0XLES
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UK49315

       UP09/08/20 P F908

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 September 2009