IBM Support

PI60881: INVALID CPSM WLM WORKLOAD FROZEN STATUS OR TOR/AOR OPTIMIZATION STATUS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Various errors can occur when a CMAS imports a CPSM WLM workload
    while the workload is frozen.
    
    -  Other CMASes that were managing the workload before it became
       frozen may defrost the workload pre-maturely.
    
       This will allow updates to be improperly made to the workload
       while it is frozen if they are initiated through these
       CMASes.
    
    -  The CMAS that imported the workload while it was frozen may
       not defrost the workload properly when appropriate.
    
       This will result in:
    
       -  failures when routing transactions that require the
          building of affinities of lifetime ACTIVITY, PERMANENT,
          PROCESS or SYSTEM in routing regions connected to this
          CMAS.  Terminal users will receive message EYUWR0301W.
    
       -  no updates being allowed to the workload if they are
          initiated through this CMAS.
    
    -  The CMAS that imported the workload may set an invalid
       optimization status for routing or target regions that were
       in a LOSTCON state when it imported the workload, after the
       regions become ACTIVE.
    
       This can result in invalid routing decisions being made by
       routing regions connected to the CMAS.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Various errors can occur when a CMAS    *
    *                      imports a CPSM WLM workload while the   *
    *                      workload is frozen.                     *
    *                                                              *
    *                      -  Other CMASes that were managing the  *
    *                         workload before it became frozen may *
    *                         defrost the workload pre-maturely.   *
    *                                                              *
    *                         This will allow updates to be        *
    *                         improperly made to the workload      *
    *                         while it is frozen if they are       *
    *                         initiated through these CMASes.      *
    *                                                              *
    *                      -  The CMAS that imported the workload  *
    *                         while it was frozen may not defrost  *
    *                         the workload properly when           *
    *                         appropriate.                         *
    *                                                              *
    *                         This will result in:                 *
    *                                                              *
    *                         -  failures when routing             *
    *                            transactions that require the     *
    *                            building of affinities of         *
    *                            lifetime ACTIVITY, PERMANENT,     *
    *                            PROCESS or SYSTEM in routing      *
    *                            regions connected to this CMAS.   *
    *                            Terminal users will receive       *
    *                            message EYUWR0301W.               *
    *                                                              *
    *                         -  no updates being allowed to the   *
    *                            workload if they are initiated    *
    *                            through this CMAS.                *
    *                                                              *
    *                      -  The CMAS that imported the workload  *
    *                         may set an invalid optimization      *
    *                         status for routing or target regions *
    *                         that were in a lostcon state when it *
    *                         imported the workload, after the     *
    *                         regions become active.               *
    *                                                              *
    *                         This can result in invalid routing   *
    *                         decisions being made by routing      *
    *                         regions connected to the CMAS.       *
    *                                                              *
    *                      -  Invalid lostcon status for routing   *
    *                         or target regions in the WLMAWTOR    *
    *                         or WLMAWAOR views.                   *
    ****************************************************************
    * RECOMMENDATION: This fix is being provided across all        *
    *                 supported releases of CPSM as follows:       *
    *                                                              *
    *                  -  CPSM V4R1M0  -  APAR PI60881             *
    *                  -  CPSM V4R2M0  -  APAR PI60881             *
    *                  -  CPSM V5R1M0  -  APAR PI60885             *
    *                  -  CPSM V5R2M0  -  APAR PI60885             *
    *                  -  CPSM V5R3M0  -  APAR PI60887             *
    *                                                              *
    *                 After applying the PTF that resolves this    *
    *                 APAR for the appropriate releases, all       *
    *                 CMASes must be restarted.  Note that the     *
    *                 restarts do not need to occur at the same    *
    *                 time, but until all CMASes in the network    *
    *                 are restarted with the fix, the issues       *
    *                 described in the problem description above   *
    *                 may continue to occur.  Also note that the   *
    *                 order in which CMASes are restarted with the *
    *                 fix is not dependent upon the maintenance    *
    *                 point (MP) status of the CMASes.             *
    ****************************************************************
    When a CMAS which manages a CPSM workload terminates while the
    target and routing regions connected to it are still active,
    the workload is marked as frozen and the target and routing
    regions are marked as lostcon.  This is done to ensure the
    integrity of the workload.  As the target and routing regions
    either re-enter the network, or are confirmed as terminated,
    their status is set as active or inactive, and when all lostcon
    regions are set as active or inactive, then the workload
    defrosts.
    
    When a CMAS enters the CMAS network after a workload has become
    frozen, and imports the workload while it is still frozen,
    a number of logic errors can lead to the problems documented
    in the problem description above.
    
    -  Method EYU0WMAA (WMAA), which is called to activate a target
       region for a workload, may not set CPSM WLM optimization
       settings correctly when a target region that was in lostcon
       state does re-enter the network.
    
    -  Method EYU0WMTJ (WMTJ), which is called to activate a routing
       region in a workload, calls method EYU0WSFW (WSFW) to defrost
       a frozen workload, without verifying that the routing region
       it was called for was marked as lostcon to the workload.
    
       Additionally, if a routing region is lostcon at the time a
       CMAS imports a workload, that information is not retained by
       the CMAS.
    
       Finally, WMTJ may not set CPSM WLM optimization
       settings correctly when a routing region that was in lostcon
       state does re-enter the network.
    
    -  When a CMAS that has a workload installed, is called to
       export that workload to another CMAS, method EYU0WMQW (WMQW)
       does not pass the name of the CMAS to which a target region
       is connected to the importing CMAS.  This may result in the
       importing CMAS not being able to defrost the workload if a
       target region which is in a lostcon state is terminated
       before its CMAS becomes active again.
    
    -  When a CMAS imports a workload, it does not update the
       Topology CICS system descriptor block (CSDB) with the name of
       the CMAS that routing and target regions were connected to
       and the information that the region is in lostcon state.
       This may result in the importing CMAS not being able to
       defrost the workload if a routing or target region which is
       in a lostcon state is terminated before its CMAS becomes
       active again.
    

Problem conclusion

  • To resolve these issues, the following changes have been made:
    
    -  WMAA has been updated to set the CPSM WLM optimization values
       for a target region properly when a lostcon target region
       re-enters the network.
    
    -  WMTJ has been updated to only call WSFW to defrost a workload
       if the routing region it was called to process is
       transitioning from lostcon to active or inactive state.
    
       WMTJ has been updated to ensure that its caller, method
       EYU0WMQU (WMQU), can set the lostcon status for a routing
       region if appropriate when a workload is imported.
    
       WMTJ has been updated to set the CPSM WLM optimization values
       for a target region properly when a lostcon routing region
       re-enters the network.
    
    -  WMQW has been updated to include the connected CMAS name in
       the target region information it passes to the importing
       CMAS.
    
    -  Method EYU0WMQU (WMQU), which is called during workload
       import to call WMAA for target regions and WMTJ for routing
       regions, has been updated to call method EYU0TSNC (TSNC) if
       the region is in a lostcon state.
    
       TSNC and its parameter list, EYUZTSNC, have been updated such
       that when called by WMQU for a lostcon region, TSNC will
       update the CSDB of the region to include the connected CMAS
       name and turn on the flag that indicates it is in lostcon
       state.
    

Temporary fix

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

Comments

  • ×**** PE16/11/01 FIX IN ERROR. SEE APAR PI71597  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI60881

  • 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 / Xsystem

  • Submitted date

    2016-04-15

  • Closed date

    2016-07-05

  • Last modified date

    2016-11-04

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

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

    PI60885 PI60887 UI39171 UI39172

Modules/Macros

  • EYU0TIST EYU0TSNC EYU0WMAA EYU0WMQU EYU0WMQW EYU0WMTJ EYU9TSRU
    EYU9TSR3 EYU9TSR4
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UI39171

       UP16/07/07 P F607 ¢

  • R70M PSY UI39172

       UP16/07/07 P F607 ¢

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:
04 November 2016