IBM Support

PI66814: CICS SM DEFINITIONS VIEW OPENS THE WRONG RESOURCE NAME FOR EDITING

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS Explorer 5.3
    CICS SM perspective
    In "File Definitions" view I've double-clicked on a resource to
    edit the file attributes.
    
    
    Explorer opens the wrong resource for editing  - it appears to
    always open the FIRST resource in the same CSD group
    as the one selected.
    The same incorrect behaviour occurs for TRANSACTION defs also.
    .
    This problem occurs only with configuration:
    It requires a CICS 5.3 CMAS and a CICS 4.2 CMAS which are
    connected. The 4.2 MAS region is connected to the 4.2 CMAS and
    belongs to the same CICSplex as the 5.3 MAS regions connected to
    
    the 5.3 CMAS.
    If you click on a file definition in the 4.2 CSD then it opens
    another file in the same csd group.
    The problem does not happen for a 5.3 FILE so the issue
    seems to happen when a resource request is for CPSM 4.2.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V5R1M0 and V5R2M0 Users      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a GET request is issued for BAS or *
    *                      CSD CICS resource definitions with      *
    *                      criteria associated with the request,   *
    *                      the definitions returned may not match  *
    *                      the criteria.                           *
    *                                                              *
    *                      This is more likely to occur when the   *
    *                      request originates in a CMAS but needs  *
    *                      to be shipped to another CMAS (BAS) or  *
    *                      MAS (CSD), that is running a different  *
    *                      CPSM version, or has a different        *
    *                      maintenance level.                      *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be restarted.  Note    *
    *                 that the restarts do not need to occur at    *
    *                 the same time.                               *
    ****************************************************************
    When a request is made to GET BAS or CSD CICS resource
    definitions, method EYU0BAGQ (BAGQ) is called to retrieve the
    records.  If the request is for BAS records and the originating
    CMAS is the maintenance point (MP) CMAS for the CICSplex the
    records are associated with, then BAGQ executes locally.
    Otherwise, the BAGQ request is shipped to either the MP CMAS of
    the CICSplex (BAS) or to a MAS (CSD) to execute.
    
    When a request that includes criteria is shipped from a CMAS to
    another CMAS or MAS and the target CMAS or MAS is running a
    different CMAS version or a different maintenance level than
    the originating CMAS, then method EYU0MOXS (MOXS) calls method
    EYU0XDOX (XDOX) to convert the criteria to the proper level for
    the target.  MOXS determines the resource type being processed
    from the definition for the method being called to retrieve the
    records, determines the record version required for the target
    the request is going to, and passes the version requested to
    XDOX.
    
    While BAGQ is called to process many different record types, its
    definition indicates that it is called to process PROGDEF
    records.  As a result, regardless of the record type being
    processed, MOXS always tells XDOX to convert the criteria based
    upon the required version for the PROGDEF record.  If that
    version is different from the version of the record it was
    called to process, or invalid, then the criteria may not be
    properly honored for the request.
    

Problem conclusion

  • The definition for BAGQ, EYUZBAGQ, has been updated to instruct
    MOXS to retrieve the record type from the BAGQ parameter list,
    instead of using PROGDEF as the record type.
    

Temporary fix

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

Comments

  • ×**** PE17/05/08 FIX IN ERROR. SEE APAR PI79774  FOR DESCRIPTION
    ×**** PE17/06/20 FIX IN ERROR. SEE APAR PI79774  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI66814

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    80M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-01

  • Closed date

    2016-08-30

  • Last modified date

    2017-06-20

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

    PI66792

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

    UI40462 UI40463

Modules/Macros

  • EYU0XDOX EYU9BAPU EYU9BAP3 EYU9BAP4 EYU9BAP6
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R80M PSY UI40462

       UP16/09/01 P F608 ¢

  • R90M PSY UI40463

       UP16/09/01 P F608 ¢

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

Document Information

Modified date:
20 June 2017