IBM Support

PM83877: ECB NOT CLEARED WHEN API RECEIVE RETURNS NODATA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an EXEC CPSM RECEIVE request receives a NODATA response,
    the ECB does not get cleared to 0.  For an application program
    this may result in an abend occurring and the task eventually
    hitting the runaway value.
    .
    The receive program does not do anything to the sentinel if it
    determines there is NODATA on the RECEIVE request.  It only
    decrements the sentinel if it is returning a record to the
    caller.  We then check the value of the sentinel and if it is
    negative, we then clear the ECB.
    
    
    Additional Symptom(s) Search Keyword(s): KIXREVNDB
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an EXEC CPSM RECEIVE command       *
    *                      issued from a API program running in a  *
    *                      MAS receives a NODATA response, the     *
    *                      SENTINEL for the API thread is not set  *
    *                      to 0, and as a result, the ECB for the  *
    *                      API thread is not cleared.              *
    *                                                              *
    *                      Depending upon how the API program is   *
    *                      written, this could result in the task  *
    *                      eventually reaching the runaway value.  *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all MASes must be restarted.  Note     *
    *                 that the restarts do not need to occur at    *
    *                 the same time.                               *
    ****************************************************************
    When a EXEC CPSM RECEIVE command is issued by an API program
    ruuning in a MAS, method EYU0XDY6 (XDY6) is called to retrieve
    the next asynchronous result.  If XDY6 finds a result available,
    it decrements the value of the SENTINEL, and then returns to
    method EYU0XDE5 (XDE5).  On exit, XDE5 checks the value of the
    SENTINEL, and if it is 0, clears the ECB.
    
    If XDY6 determines that there is no result to return, it sets a
    response of NODATA and then exits, without modifying the
    SENTINEL.  This can result in the SENTINEL never being set to 0,
    which means that XDE5 will not clear the ECB.
    

Problem conclusion

  • XDY6 has been updated to set the SENTINEL to 0 and to clear the
    ECB if it is going to return a response of NODATA when running
    in a MAS.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM83877

  • 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

    2013-02-28

  • Closed date

    2013-04-16

  • Last modified date

    2013-05-03

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

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

    PM84042 PM84043 UK93508

Modules/Macros

  •    EYU0XDY6
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK93508

       UP13/04/20 P F304

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:
03 May 2013