IBM Support

PH17586: CPSM: MIGRATION RESULTS IN AP SPEC SECONDARY CMAS ASSOCIATION CORRUPTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In the plex environment, all the AP Specifications were
    associated with a Primary and Secondary CMAS. When the CMASes
    were upgraded from 5.4 to 5.5, the association between the
    APSpec and the secondary CMAS were missing. In the WUI, none of
    the APSpecs showed there was an association with a Secondary
    CMAS. And when trying to add the Secondary CMAS, an error
    stating there was an duplicate associate occurred, which
    indicates that the original association is there in the plex.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CPSM users for V5R2M0, V5R3M0, V5R4M0,   *
    *                 and V5R5M0.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Analysis Point Specification CMAS links *
    *                      are lost from the MP Data Repository    *
    *                      when upgrading a non-MP CMAS.           *
    ****************************************************************
    * RECOMMENDATION: All Maintenance Point CMAS regions should    *
    *                 be restarted to activate the fix.            *
    ****************************************************************
    Analysis Point Specification CMAS links are lost from the
    Maintenance Point (MP) Data Repository when upgrading a non-MP
    CMAS. This occurs when the non-MP CMAS is defined as a Primary
    or Secondary CMAS on an RTA Analysis Point Specification in a
    CICSplex assigned to the non-MP CMAS.
    When a non-MP data repository is upgraded using the EYU9XDUT
    utility, all CICSplex context records are removed from the
    repository. When that CMAS next reconnects to the maintenance
    point for a CICSplex it manages, the upgraded version of these
    CICSplex context records will be restored. To achieve this, the
    MP CMAS will temporarily remove the non-MP CMAS from the
    CICSplex, then assign it back again. When the CMASCPLX record is
    deleted during the unassign operation, associated CMDMPAPS and
    CMDMSAPS (primary/secondary APSPEC relationships) will also be
    deleted from the MP data repository due to referential integrity
    processing. These records are not restored when the CICSplex is
    assigned back to the non-MP CMAS.
    This issue only affects Primary (CMDMPAPS) and Secondary
    (CMDMSAPS) CMAS relationships for RTA Analysis Point
    Specifications (APSPEC).
    The same loss of CMDMPAPS or CMDMSAPS records may occur for
    other scenarios involving an automation delete and re-add of a
    CICSplex to a non-MP CMAS by CPSM method CPLT.
    

Problem conclusion

  • CICSplex SM has been updated to ensure that Primary and
    Secondary CMAS relationships for an RTA Analysis Point
    Specification are retained across an automatic unassign and
    reassign of a CICSplex by method CPLT. CPSM methods CPLT, CCAP,
    CCDP and PSLT were all updated. Affected records will be stored
    temporarily in a queue, allowing them to be restored after the
    CICSplex assign operation completes.
    
    The CICSPlex SM Messages and Codes manual, version V5.2
    (GC34-7310-00), V5.3 (GC34-7445-00), V5.4 and V5.5 will all be
    updated with new message EYUCP0208:
    EYUCP0208E <applid> Delete and re-add of CICSplex <plexname>
        from CMAS <cmasname> failed. The <primary|secondary> CMAS
        association to APSPEC <apspec> may have been lost.
    This message will be issued to the EYULOG of the maintenance
    point CMAS, only if CPSM is not able to fully restore the
    CMDMPAPS or CMDMSAPS records. This will be accompanied by
    message EYUCP0023E, indicating a failure during data
    repository synchronisation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH17586

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    20M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-01

  • Closed date

    2020-01-27

  • 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:

    UI67565 UI67566 UI67567 UI67568

Modules/Macros

  • EYU0CCAP EYU0CCDP EYU0CPLT EYU0PSLT EYU9CMP3 EYU9CMP4 EYU9CMPU
    EYU9CMR3 EYU9CMR4 EYU9CMRU EYUMCCPC EYUMCCPE EYUMCCPK
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R00M PSY UI67566

       UP20/01/30 P F001 ¢

  • R10M PSY UI67567

       UP20/01/31 P F001 ¢

  • R20M PSY UI67568

       UP20/01/29 P F001 ¢

  • R90M PSY UI67565

       UP20/01/29 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.5","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.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 February 2020