IBM Support

PI48170: EYUXL0905E ASRA S0C4 IN CPSM METHOD EYU0WMGL, TRANSACTION WMWC

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You recently upgraded to CPSM 5.2. Your CMAS starts
    successfully, but when you begin CONNECTing MASes to it, and
    CPSM goes to install workloads, you see an ASRA S0C4 abend in
    the CMAS. Messages may look similar to the following:
    .
    EYUXL0900I   Starting Environment Recovery
    EYUXL0905E CMASABCD   ASRA IN WMGL, OFFSET 000009DA
                          PSW=07856000 A668A0D2
    EYUXL0905E INTC=0010 ILC=4 TXCP=0017E801 SCODE=S00C4 TRAN=WMWC
               TASK=0012345
    EYUXL0905E Methods=WMGL,WMBA,WMBP,WMBS,WMWB,WMWC,XLOP
    EYUXL0905E BEAR=2668A2B8, OFFSET=00000BC0
    EYUXL0906I Registers at ABEND
    EYUXL0907I GPR0-GPR1  00000000_00000058  00000000_0017E300
    EYUXL0907I GPR2-GPR3  00000000_00000080  00000000_26689738
    EYUXL0907I GPR4-GPR5  00000000_FFFFFF00  00000000_FFFFFF80
    EYUXL0907I GPR6-GPR7  00000000_00002EB8  00000000_00002D00
    EYUXL0907I GPR8-GPR9  00000000_0017E000  00000000_00A9A500
    EYUXL0907I GPRA-GPRB  00000000_2668A738  00000000_26A524F0
    EYUXL0907I GPRC-GPRD  00000000_26159C90  00000000_2615A110
    EYUXL0907I GPRE-GPRF  00000000_A668A08A  00000000_00000000
    .
    EYUXL0907I ARR0-ARR3  00000000  01010069  01010069  00000000
    EYUXL0907I ARR4-ARR7  00000000  00000000  00000000  01010069
    EYUXL0907I ARR8-ARRB  0101006A  01010069  00000000  00000000
    EYUXL0907I ARRC-ARRF  00000000  00000000  00000000  00000000
    .
    In the dump, the CMAS trace table shows an exception trace
    entry for the following:
    .
    Task  Mtd  Prev Tran Obj Level Pt-ID  Debug  UOW   Local TOD
    12345 WMGL      WMWC     Abend       *Abend*     hh:mm:ss.ttttt
    .
    Bits 16-17 of the PSW are x'01', so we were in AR mode at the
    time.
    .
    The instructions in WMGL at +x'9DA' that we were in at the time
    show us at label ACQSYS_INCR. The problem is that AR8 is not
    pointing to the correct ALET for the WLM dataspace it needs to
    use. The instruction being executed at the time uses AR7 and
    AR8. The alet in AR8 is not for the correct WLM dataspace
    extent.
    .
    .
    Additional Symptom(s) Search Keyword(s): KIXREVSVR
    

Local fix

  • Recycling the CMAS may correct this, but the problem may
    reoccur on a subsequent run as well.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V5R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend ASRA/S0C4 can occur in a CMAS in  *
    *                      method EYU0WMGL (WMGL) around offset    *
    *                      x'9DA', or an overlay of the WLM data   *
    *                      cache can occur, when a CPSM WLM        *
    *                      workload is installed, or a WLMDEF is   *
    *                      installed into an existing workload.    *
    *                                                              *
    *                      If the overlay occurs, it will most     *
    *                      likely result in CPSM WLM performing    *
    *                      incorrect routing decisions.  However,  *
    *                      other unpredictable results may occur.  *
    ****************************************************************
    * 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 workload is installed, or a WLMDEF is installed into an
    existing workload, method EYU0WMGL (WMGL) is called to build
    EYURWSGA data structures in the WLM data cache for each
    AORSCOPE.  It then anchors the pointer to the EYURWSGA in the
    EYURWSGV data structure in the WLM data space and increments a
    AORSCOPE counter in the EYURWSGV header.  When it addresses the
    EYURWSGV header, it does so with the ALET of the EYURWSGA,
    instead of the ALET for the EYURWSGV.  If these structures
    reside in different data spaces, then the errors described above
    will occur.
    

Problem conclusion

  • WMGL has been updated to correctly use the ALET for the EYURWSGV
    when updating the AORSCOPE counter.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI48170

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    90M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-09-03

  • Closed date

    2015-09-30

  • Last modified date

    2015-11-03

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

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

    UI31626

Modules/Macros

  • EYU0WMGL
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R90M PSY UI31626

       UP15/10/02 P F510 ½

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:
03 November 2015