IBM Support

PI49200: AICA ABEND IN CPSM METHOD EYU0MOXT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Your CMAS suffers an AICA abend in method MOXT. The messages in
    your CMAS job look like the following:
    .
    EYUXL0900I   Starting Environment Recovery
    EYUXL0905E cmasname AICA IN MOXT, OFFSET 0000018C
        PSW=078D6000 9E47516C
    EYUXL0905E INTC=0002 ILC=2 TXCP=0933E800 SCODE=S????
        TRAN=XLNX TASK=0012345
    EYUXL0905E Methods=MOXT,XQGQ,XLNX,XLOP
    .
    In the resulting SVC dump, the MVS SYSTRACE leading up to the
    'SVC D' for the dump will show PSW addresses out of CPSM method
    MOXT from offset +x'124' (corresponding to label XXBS_LOOP_0009
    in the code) through +x'196'.
    .
    Formatting the CPSM-written trace entries in IPCS using
    .
      VERBX EYU9D### 'TRC,JOB=cmasname'
    .
    You can see that the abending task called method MOXT for
    function TRANSFORM_TABLE:
    .
    .
         Keyword             Data Queue Req Data     Data
         Value               Type Dir   Opt Address  Value
    In: *FUNCTION            FUN         .  1E3D1FB4 TRANSFORM_TABLE
        *DEBUG               CHR         .  1E3D1FB8 XQGQMOXT
        *SOURCE_RESTYPE      RES         .  1E3D1FC0 09E7
        *SOURCE_VERSION      BIN         .  1E3D1FC2 0A01
         TARGET_VERSION      BIN         .
        *SOURCE              EBK         .  1E3D1FC8 A=01FF0024
                                                     O=0001105C
                                                     L=00000044
        *TARGET              BUF         .  1E3D1FD4 A=1E3D575C
                                                     L=00000000
                                                     M=00006FFC
                                                     T=00000000
        *SOURCE_BLOCKING     ENM         .  1E3D1FE4 UNBLOCKED
         TARGET_CPSM_RELEASE CHR         .
         OLD_VMOD            PTR         .
         MAL_VMOD            PTR         .
    .
    .
    The problem in this case is that MOXT depends upon the CPSM MOS
    component being fully initialized, but MOS initialization
    failed during startup. The CPSM joblog shows this shortly
    before the AICA:
    .
    EYUXD0020E cmasname Enhanced MOS initialization failed.
    .
    In the case that originated this APAR, the reason for the MOS
    initialization failure was due to storage constraints, and the
    job log shows the following:
    .
    IEW4000I FETCH FOR MODULE EYUTMOSD FROM DDNAME STEPLIB FAILED
             BECAUSE INSUFFICIENT STORAGE WAS AVAILABLE.
    CSV031I LIBRARY ACCESS FAILED FOR MODULE EYUTMOSD, RETURN
            CODE 14, REASON CODE 26110021, DDNAME STEPLIB
    .
    .
    There could however be other reasons for MOS initialization
    failures. The key here is that MOXT is assuming that MOS is
    available, but it is not.
    .
    .
    Additional Symptom(s) Search Keyword(s): KIXREVSVR
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Your CMAS issues message: IEW4000I      *
    *                      FETCH FOR MODULE EYUTMOSD FROM DDNAME   *
    *                      STEPLIB  FAILED BECAUSE INSUFFICIENT    *
    *                      STORAGE WAS AVAILABLE.                  *
    *                                                              *
    *                      Subsequent to this message the CMAS     *
    *                      reports an abend in module MOXT and     *
    *                      takes a system dump as part of its      *
    *                      shutdown process. The reported CICS     *
    *                      dump code is an AICA - which means      *
    *                      that the CMAS had entered a runaway     *
    *                      task condition. Other abends may        *
    *                      also be reported - all concerned        *
    *                      with illegal storage addressing.        *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes must be recycled to pick    *
    *                 up the new code.  Note that regions do not   *
    *                 need to be brought down and restarted at     *
    *                 the same time.                               *
    ****************************************************************
    The abend in MOXT is symptom of the root problem, which is that
    insufficient storage was available to load the CPSM Managed
    Object Services (MOS) Directory control table EYUTMOSD. When
    that failure occurred then the CMAS effectively entered shutdown
    mode. However, parallel CMAS initialisation services were
    executing at the same time, which are dependent on MOS being
    fully initialised. One of these tasks requested MOS
    transformation services, which attempted to scan the MOS
    Directory without checking beforehand that MOS was successfully
    initialised. This caused a lookup into uninitialised CICS
    storage, which resulted in the AICA abend in the reported
    situation, but could easily have generated an alternate CICS
    abend (i.e. ASRA, ASRB) instead.
    

Problem conclusion

  • Module EYU0MOXT has now been updated to verify that MOS is
    successfully initialised before continuing with a transformation
    request. If the MOS_STATUS flag in the DAT MOEB is not set with
    the BIND value, then the current request is rejected with a
    Response/Reason code of EXCEPTION/INCOMPLETE_ENVIRONMENT.
    
    When that response code is returned to EYU0XQGQ, it is
    transposed into a CANNOT_CONVERT_TABLE status back to
    its caller.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

  • ž**** PE15/10/30 FIX IN ERROR. SEE APAR PI51625  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI49200

  • 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

  • Submitted date

    2015-09-22

  • Closed date

    2015-10-23

  • Last modified date

    2015-11-20

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

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

    PI49653 UI32339

Modules/Macros

  • EYU0MOXT EYU0UQGQ EYU0XQGQ EYU9XDPU EYU9XDP3 EYU9XDP4 EYU9XDP6
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R70M PSY UI32339

       UP15/10/27 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":"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:
20 November 2015