IBM Support

PM01527: POSSIBLE ASRA/S0C4 IN 3.2 CMAS WHEN RTAACTV GET ISSUED FROM 4.1 CMAS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A failure may occur when an API or WUI request for RTAACTV
    records that specifies a criteria is sent from a CPSM 4.1 CMAS
    to a CPSM 3.2 CMAS.  The API program or WUI user will receive a
    RESPONSE/REASON of FAILED/EXCEPTION.
    
    Examination of the joblog of the 3.2 CMAS will show an abend in
    method EYU0PGRS (PGRS).  The abending offset will most likely be
    ????????, and the abend will most likely be an ASRA/S0C4.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: A failure may occur when an API or WUI  *
    *                      request for RTAACTV records that        *
    *                      specifies a criteria is sent from a     *
    *                      CPSM 4.1 CMAS to a CPSM 3.2 CMAS.  The  *
    *                      API program or WUI user will receive a  *
    *                      RESPONSE/REASON of FAILED/EXCEPTION.    *
    *                                                              *
    *                      Examination of the joblog of the 3.2    *
    *                      CMAS will show an abend in method       *
    *                      EYU0PGRS (PGRS).  The abending offset   *
    *                      will most likely be ????????, and the   *
    *                      abend will most likely be an ASRA/S0C4. *
    ****************************************************************
    * 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 to retrieve table records is shipped from one
    CMAS to another CMAS, if the CMASes have different versions of
    the table, then method EYU0MOXS (MOXS) is called in the CMAS
    which has the higher version of the table to perform conversion
    for the request.  If criteria or a view mod is associated with
    the request, then MOXS calls method EYU0XDOX (XDOX) to convert
    the criteria and/or view mod to the proper level.  If XDOX
    determines that the table or the table version is unknown to the
    target CMAS, it returns an UNKNOWN_TABLE status to MOXS.  MOXS
    will then clear the criteria and/or view mod pointer and length
    in the parameter list (message argument list - MAL), but does
    not clear the existence bit for the criteria or view mod.  If
    the processing method only checks the existence bit to determine
    if it has a criteria or view mod, then it may attempt to access
    data at location x'00000000', which will most likely lead to an
    abend.
    
    For an RTAACTV request, the processing method, EYU0PGRS (PGRS),
    does only check the existence bit, so if MOXS removes the
    criteria or view mod from the MAL, then it will most likely
    abend.  However, the call to XDOX for an RTAACTV request should
    not produce an UNKNOWN_TABLE status, since the RTAACTV table and
    version is known to 3.2 CMAS.  Because of a definition error in
    the PGRS MAL (EYUZPGRS), XDOX does return an UNKNOWN_TABLE
    status in this situation.
    

Problem conclusion

  • MOXS has been updated to turn off the existence bit in the MAL
    when removing a criteria or view mod from the MAL prior to
    execution, and to turn the existence bit back on when restoring
    the criteria or view mod after execution.
    
    EYUZPGRS has been updated to resolve the definitional error that
    results in XDOX returning a status of UNKNOWN_TABLE when called
    to ship an RTAACTV request that contains a criteria or view mod
    to a 3.2 CMAS.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM01527

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    60M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-18

  • Closed date

    2010-01-15

  • Last modified date

    2010-02-01

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

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

    UK53541

Modules/Macros

  • DYU0MOCS DYU0MOIT DYU0MOXS DYU0MOX2 EYUBMOMR
    EYUCPGRS EYUQPGRS EYURPGRS EYUTRRTA EYUYPGRS EYUZPGRS EYU0MOCS
    EYU0MOIT EYU0MOXS EYU0MOX2 EYU9PSPU EYU9PSP3 EYU9PSP4
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UK53541

       UP10/01/19 P F001

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

Document Information

Modified date:
01 February 2010