IBM Support

OA49277: WAIT0A2 RSN40 XCFAS DATASPACE IXCDSCBE EXHAUSTED WITH REAMS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WAIT0A2-40 occurred as XCF Dataspace routine detected storage
    was exhausted as a result of a build-up of REAMS control blocks
    in dataspace IXCDSCBE. There is a defect in IXCSEND service
    code which allows storage in an XCFAS dataspace to remain
    allocated after an exploiter terminates. This only occurs when
    the exploiter also has an error which causes it to terminate
    before it receives all messages pending in delivery. The
    exposure may occur running with any applications that exploits
    the XCF Client/Server IXCSEND service. In the case the apar was
    opened for, the exploiter was MXI by Rocket Software.
    
     EXTERNAL SYMPTOMS:
     WAIT0A2-040 when XCF Client/Server related processing which
     causes the build up of REAMs in IXCDSCBE dataspace. Subsequence
     request of IXCSEND triggers the need to obtain one more REAM
     from ISCDSCBE but IXCDSCBE reached 2G limit.
     KNOWN IMPACT:
     Loss of LPAR
     VERIFICATION STEPS:
     1) Checking the SYSTEM TRACE from all general CPs. Locate
     any processing with primary in asid(6),
     2) Checking the last few SYSTEM TRACE entries under these
     logical CPs and determine if any PC 00B37 (IXCSEND request) was
     in progress
     3) SUMM FORMAT for the home address space from the systrace
     entry, then locate the associated TCB. use the linkage stack
     below the PC 00B37 to check out the save area and determine
     which dataspace was the target.
     4) IPCS COUPLE STORAGE report to check out the usage of that
     dataspace.
    

Local fix

  • BYPASS/CIRCUMVENTION:
     No local fix available
     RECOVERY ACTION:
     re-IPL the LPAR and try not to start the application using the
     IXCSEND until fix becomes available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Cross System Coupling Services      *
    *                 (XCF) client/server communications           *
    *                 on z/OS V1R13 (HBB7780) and above.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: XCF client/server IXCSEND macro         *
    *                      requests that fail to successfully      *
    *                      initiate a send request due to bad      *
    *                      application supplied parameters may     *
    *                      leave resources allocated in the XCF    *
    *                      IXCDSCBE data space causing the data    *
    *                      space to fill up and run out of         *
    *                      eligible storage causing a WAIT0A2-40   *
    *                      wait state of the system.               *
    *                                                              *
    *                      SYSPLEXDS                               *
    ****************************************************************
    * RECOMMENDATION: Install PTF on each system in the sysplex    *
    *                 via rolling IPL.                             *
    ****************************************************************
    When an XCF client/server IXCSEND macro request fails due to bad
    application parameter input, RC8 with one of the following RSN
    codes may be returned:
    
    - RSN0001000C
    - RSN00060004
    - RSN00060008
    - RSN000800EE
    - RSN000B0004
    - RSN000B0008
    - RSN000C0004
    - RSN000C0008
    - RSN0017000C
    
    When one of the above mentioned RSN codes is returned, the
    IXCSEND service routine does not free all storage resources.
    Resources are left allocated in the XCF owned IXCDSCBE data
    space which eventually runs out of available storage and results
    in a WAIT0A2-40 wait state of the system.
    

Problem conclusion

  • Change the IXCSEND service routine to free all resources.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA49277

  • Reported component name

    XCF

  • Reported component ID

    5752SCXCF

  • Reported release

    790

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-11-05

  • Closed date

    2015-11-18

  • Last modified date

    2016-01-04

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

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

    UA79840 UA79841 UA79842

Modules/Macros

  • IXCS1SND
    

Fix information

  • Fixed component name

    XCF

  • Fixed component ID

    5752SCXCF

Applicable component levels

  • R7A0 PSY UA79840

       UP15/12/02 P F512

  • R780 PSY UA79841

       UP15/12/02 P F512

  • R790 PSY UA79842

       UP15/12/02 P F512

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 January 2016