IBM Support

PI64558: ABEND0C4 ON STARTUP OF CMAS IN MODULE EYU0MOCS AND ERROR MESSAGES EYUCP0002E EYUCL0107E

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Running CICS 5.2, you experience an abend in the startup of the
    maintenance point CMAS. Here are the messages:
    .
    EYUXL0905E CMASxxxx ASRA IN MOCS, OFFSET 00000E5A
               PSW=07855000 A85380BA INTC=0010 ILC=4
               TXCP=62C60801 SCODE=S00C4 TRAN=LPLT TASK=0000050
               Methods=MOCS,CPZI,CPTI,CPLT,XLOP
               BEAR=28538240, OFFSET=00000FE0
    .
    EYUXL0910I EYU9XLRV  Dump,CMASxxxx,CMASxxxx, MVSX,CMAS, LPLT,
               0000050, ASRA,EYU0MOCS,
    EYUCP0002E CMASxxxx NetTop Import Failure for Connecting CMAS
               CMASyyyy Failure occured in CPZI
    .
    EYUCL0107E CMASxxxx ESSS ICT attach to <nodename> failed,
               add capability failed.
    .
    The program check occurred at offset x'E5A' in module EYU0MOCS
    at ptf level UI24867, due to referencing the incorrect
    dataspace. In other releases, the offset and PTF level may be
    different.
    .
    Looking at the task having the problem with
      VERBX EYU9Dxxx 'TASKS'
    the stack will look like:
    .
    Task Meth Load-Pt  OPB      OSSB     Stack    Mal      MODB
      50 XLOP 000A8128 28B93C30 28B93DB8 28B93DE0 00000000 27586CF0
      50 CPLT 2861AEE0 28B93C30 28B93DB8 28B93F28 275F47FC 2758E3F0
      50 CPTI 2868C418 28B93C30 28B93DB8 28B94CE8 28B94148 2758E3F0
      50 CPZI 28692C38 28B93C30 28B93DB8 28B956F0 28B951B0 2758E3F0
      50 MOCS 28537260 28B93C30 28B93DB8 28B95BE8 28B95970 2758C1F0
    .
    Additional Symptom(s) Search Keyword(s): KIXREVGJT
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V5R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend ASRA/S0C4 may occur in a CMAS in  *
    *                      method EYU0MOCS (MOCS) when the CMAS    *
    *                      connects directly or indirectly to      *
    *                      another CMAS.                           *
    ****************************************************************
    * 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 CMAS connects directly or indirectly to another CMAS,
    both CMASes need to build a resource table capability matrix for
    the partner CMAS, so that when CPSM resource tables are shipped
    between the two CMASes, table translation can occur if the
    CMASes support different versions of the tables.
    
    To build a capability matrix, method EYU0MOCS (MOCS) is called.
    MOCS will search through the existing capability matrixes that
    the CMAS has already built, to see if one is a match for the new
    partner CMAS.  If so, it will assign the existing matrix to the
    new partner.  If not, it will build a new matrix and assign it
    to the new partner.
    
    The capability matrixes are stored in the DAT component data
    cache, and are chained to each other.  MOCS starts with the last
    built matrix, and chains from it to the first built matrix.
    Since the DAT data cache consists of two data spaces, DAT1 and
    DAT2, the matrixes can be allocated in either data space,
    depending upon available storage at the time of allocation.
    When this occurs, a logic error in MOCS will cause it to address
    invalid data when a matrix in one data space chains to a matrix
    in the other data space.  This will most likely result in MOCS
    abending ASRA/S0C4.
    

Problem conclusion

  • MOCS has been updated to address the next compatibility matrix
    properly, when it is allocated in a different data space than
    the previous matrix.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI64558

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    90M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-06-20

  • Closed date

    2016-06-28

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

    PI64770 UI38985

Modules/Macros

  • EYU0MOCS
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R90M PSY UI38985

       UP16/06/30 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":"5.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":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 July 2016