IBM Support

PI40266: CPSM EYU0MOXT MAY INCORRECTLY CONVERT A QUEUE RECORD. UNPREDICTABLE RESULTS, INCLUDING ABENDS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CPSM EYU0MOXT may incorrectly convert a queue record in some
    circumstances. Base table records are converted to a version
    compatible with the capabilities of the CMAS. If the version of
    a record has changed, MOXT may overlay some of the record being
    processed. Unpredictable results may occur.
    .
    This issue may be exposed and cause a problem if a PTF has been
    applied that causes a version change in a table record, but the
    modules affected by the PTF are not completely rolled into the
    CMAS's load libraries.
    .
    For example, if a PTF affects modules in both SEYUAUTH and
    SEYULOAD, but only the SEYUAUTH dataset changes are rolled into
    the running CMAS's loadlibs (or vice versa,) it might cause an
    abend (SOC1 or ASRA) in another CMAS. That is because when two
    CMASes exchange capabilities at startup, they indicate to each
    other what version of each base record type they are using.
    That information comes from modules in SEYUAUTH. However, when
    those base records actually get built and sent around during
    the running of the CMAS, the modules in SEYULOAD perform that
    function. If the CMAS is indicating to other CMASes through
    SEYUAUTH members that it uses version '1234' of a given record,
    but it builds version '5678' though SEYULOAD members, then
    other CMASes processing those records may encounter
    unpredictable results, including abends. One specific abend
    encountered so far was an intentional ASRA S0C1 out of EYU0TSCJ
    method.
    .
    .
    Additional Symptom(s) Search Keyword(s): KIXREVSVR
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 and V4R2M0 Users      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend ASRA/S0C1 may occur in method     *
    *                      EYU0TSCJ (TSCJ) if a topology resource  *
    *                      map (CRESxxxx resource table) is passed *
    *                      between two CPSM CMASes which are at    *
    *                      different maintenance levels for the    *
    *                      CRESxxxx resource table.                *
    *                                                              *
    *                      The problem can also occur when a CPSM  *
    *                      CMAS manages a CICSplex whose           *
    *                      maintenance point (MP) CMAS is running  *
    *                      a higher release of CPSM.               *
    *                                                              *
    *                      In addition to the ASRA/S0C1 abend in   *
    *                      TSCJ, other symptoms include Topology   *
    *                      join failures, and missing records in   *
    *                      get requests issued through the WUI or  *
    *                      a CPSM API program.  When either of     *
    *                      these problems occur, the following     *
    *                      exception trace records may be issued   *
    *                      by CMASes exhibiting these symptoms:    *
    *                                                              *
    *                           Method  TPID  Debug text           *
    *                           ------  ----  ----------           *
    *                           MOXT     106  TAB_VER              *
    *                           XQGQ       1  GETQXCP              *
    *                           TSCJ       8  TSCJXQGQ             *
    ****************************************************************
    * 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 CICS resource that CPSM manages through Topology resource
    maps is added or removed in a MAS, a CRESxxxx record is built in
    the CMAS to which the MAS is connected (for example a CRESPRGM
    record for PROGRAM resources).  The local CMAS uses the record
    to change the resource maps for the MAS, and then ships the
    record to other CMASes in the network in a CPSM queue structure,
    where the record is used to update the MAS's resource maps in
    the receiving CMASes.  The processing of the records in the
    remote CMASes is performed by TSCJ.  These resource maps are
    used by CPSM's single system image (SSI) processing to determine
    where to direct EUI, WUI, API and RTA requests.  If the maps are
    incorrect, then requests may not be directed correctly.
    
    If the CRESxxxx record is at a different version in the two
    CMASes, then method EYU0MOXS (MOXS) is called in the CMAS that
    has the later version of the resource table, to convert the
    record to the proper version. When TSCJ runs in the remote CMAS
    to process the record, it calls method EYU0XQGQ (XQGQ) to read
    the record from the queue.  XQGQ will validate the version of
    the record.  If it is not at the correct version, XQGQ will call
    method EYU0MOXT (MOXT) to convert the record properly.  A logic
    error in MOXT will cause the the record to not be converted
    properly. This will lead to either the ASRA/S0C1 in TSCJ, or the
    Topology failure or missing records in get requests.
    

Problem conclusion

  • Methods EYU0MOXT (MOXT), EYU0XQGQ (XQGQ) and EYU0XQTQ (XQTQ)
    have been updated to make sure that records with leading data
    are converted correctly.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI40266

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    70M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-01

  • Closed date

    2016-06-08

  • Last modified date

    2016-07-04

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

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

    PI40794 PI40795 PI40797 PI62811 UI38495 UI38496

Modules/Macros

  • EYU0MOXT EYU0UQGQ EYU0XQGQ EYU0XQTQ EYU9XDPU EYU9XDP3 EYU9XDP4
    EYU9XDP6
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UI38495

       UP16/06/10 P F606

  • R70M PSY UI38496

       UP16/06/10 P F606

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

Document Information

Modified date:
04 July 2016