IBM Support

PH20459: CPSM INCORRECT WORKLOAD OWNER WHILE INSTALLING WLMDEF

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the CICSPlexSM WUI, the Install of a newly created WLMDEF
    fails because, when the associated workload specification in
    selected, the "workload owner" field is incorrectly filled with
    a CMAS SYSID that is not the one owning the workload.
    

Local fix

  • would enhance the list to present both possible workloads
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM Users.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using the CICSPlex SM Web User     *
    *                      Interface (WUI) server to install a     *
    *                      WLM definition or WLM group into an     *
    *                      active workload, a picklist is          *
    *                      available which displays the active     *
    *                      workloads where this WLMDEF or WLMGROUP *
    *                      could be installed.                     *
    *                      This picklist may contain incorrect or  *
    *                      incomplete data.                        *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF which solves PH20459, *
    *                 all CMASes and WUI servers must be restarted *
    *                 to activate the fix.                         *
    *                 The restarts need not be performed at the    *
    *                 same time, however if systems are not        *
    *                 restarted at the same time, the following    *
    *                 rules apply:                                 *
    *                                                            . *
    *                 - Maintenance Point (MP) CMASes must be      *
    *                   restarted on the updated code before       *
    *                   non-MP CMASes.                             *
    *                                                            . *
    *                 - If you have more than one MP CMAS and any  *
    *                   of those MP CMASes are connected directly  *
    *                   or indirectly, then those MP CMASes        *
    *                   must be restarted at the same time.        *
    *                                                            . *
    *                 - Before a MAS, regardless of whether it is  *
    *                   running as a WUI server, is restarted      *
    *                   with the updated code, the CMAS to which   *
    *                   the MAS connects must be running with the  *
    *                   updated code.                              *
    *                                                            . *
    *                 - This fix is being provided across the      *
    *                   following releases of CICSPlex SM:         *
    *                                                            . *
    *                   -  CPSM V5R4M0 - APAR PH20459              *
    *                   -  CPSM V5R5M0 - APAR PH20459              *
    *                                                            . *
    *                   Before a CMAS running with the PTF that    *
    *                   resolves this APAR for its release         *
    *                   connects directly or indirectly to a CMAS  *
    *                   running a higher release of CPSM, the      *
    *                   higher release CMAS must be restarted so   *
    *                   that it is running with the appropriate    *
    *                   PTF for its release.                       *
    ****************************************************************
    The CICSPlex SM Web User Interface (WUI) can be used to install
    WLM definitions and WLM groups into an active workload.
    The EYUSTARTWLMDEF.INSTALL and EYUSTARTWLMGROUP.INSTALL views
    both provide a picklist to assist the user in selecting the
    target workload where the WLMDEF or WLMGROUP should be
    installed. The resource table used to build this view uses the
    workload name as a key, which means that only one workload with
    a given name can be represented.
    The selection offered may be incomplete if duplicate workloads
    exist within the CICSplex.
    A duplicate workload occurs when two separate CMAS regions each
    build the workload. The resulting workloads can be distinguished
    using the Owning System ID (WRKLOWNER).
    Furthermore the "Resource status" (either Active or Inactive)
    was not being set correctly on elements in these picklists,
    meaning that workloads which were known to the CICSplex but
    not currently active (i.e. there is no active CMAS currently
    managing the workload, even though at least one routing region
    is active) were not filtered out.
    
    In the reported problem, the only option displayed in this
    picklist was an inactive workload. That is, the "Owner name"
    displayed was for a CMAS which was not the workload owner of an
    active workload.
    
    Attempting to install a WLM definition into the only workload
    presented in the picklist resulted in the following error:
    EYUVC1231E     'Install' (INSTALL) request failed. Request
                    complete for 1 records. (Notavailable, Workload)
    

Problem conclusion

  • CICSplex SM has been update to extend the key for the
    internal TOPOBJ resource table to include the owner field.
    This allows TOPOBJ representations of WLMAWORK resources
    using the same workload name but a different workload owner
    to be represented within a single result set.
    Method TSQO (EYU0TSQO) has also been updated to ensure that
    the Active/Inactive state is filled in in these resources.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH20459

  • 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-12-18

  • Closed date

    2020-01-22

  • Last modified date

    2020-02-04

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

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

    UI67499 UI67500

Modules/Macros

  • EYU0TSQO EYUE2540 EYUT2540 EYUY2540
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R10M PSY UI67499

       UP20/01/24 P F001

  • R20M PSY UI67500

       UP20/01/24 P F001

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":"5.4","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":"5.4","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 February 2020