IBM Support

PK54688: ABEND ASRA/S0C4 OCCUR IN A CMAS IN METHOD EYU0BMLE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abend ASRA/S0C4 will occur in a CMAS in method EYU0BMLE when
    an EUI or API request is made specifying a BAS logical scope
    that represents 200 or more CICS systems.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend ASRA/S0C4 may occur in a CMAS in  *
    *                      method EYU0BMLE (BMLE) when an API or   *
    *                      WUI request specifies a BAS logical     *
    *                      scope.                                  *
    *                                                              *
    *                      The error is more likely to occur when  *
    *                      the scope represents 200 or more MASes. *
    *                                                              *
    *                      In addition, the requestor will not     *
    *                      receive an indication that an error has *
    *                      occurred.                               *
    ****************************************************************
    * 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 an API or WUI request specifies a BAS logical scope, method
    EYU0XLSI (XLSI) calls method EYU0TMLE (TMLE) to build the
    namelist that would be required to retrieve the specified data
    for the scope.  TMLE calls method EYU0BMLE (BMLE) to build a
    queue which contains one element for each MAS and resource
    associated with the logical scope.  To do this, BMLE must build
    a list that contains the name of each local MAS that is part of
    the logical scope.  BMLE builds this list in its working
    storage, and limits the list size to 199 MASes.  If more than
    199 MASes exist, then BMLE getmains a secondary area.  A logic
    error in BMLE causes the secondary area to be corrupted.  In
    most situations, this will result in a S0C4 abend in BMLE as it
    attempts to add additional elements to the list.
    
    When the abend occurs, or when any other error causes a failure
    in BMLE, TMLE is returned a failure indication.  TMLE will issue
    an exception trace and propagate the failure back to XLSI.  XLSI
    will also issue an exception trace, but it does not return a
    failure indication to its caller.  As a result, the requestor
    does not know that a failure occurred, and may re-execute the
    request, resulting in additional failures.
    

Problem conclusion

  • BMLE has been updated to correct the logic errors that cause it
    to corrupt secondary MAS lists.  Additional errors in the
    handling of these lists have also been resolved.
    
    XLSI has been updated so that if it receives a failure
    indication from TMLE, it will set a non-OK status.  The
    requestor will receive the following:
    
    -  API requestors will receive:
    
    
         RESPONSE = 1028 (INVALIDPARM)
         REASON   = 1294 (SCOPE)
    
    
    -  WUI requestors will receive:
    
         EYUVC1283W  The specified Scope (<scope>) is not available
                     for this Context (<cicsplex>).
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK54688

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-10-16

  • Closed date

    2007-10-19

  • Last modified date

    2007-11-02

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

    PK54731

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

    UK30437

Modules/Macros

  •    EYU0BMLE EYU0XLSI
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK30437

       UP07/10/23 P F710

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

Document Information

Modified date:
02 November 2007