IBM Support

PM59329: CICS TS VER.4.2 JVM HIGH STORAGE USAGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer is suffering ABEND 878-10 in his CICS TS Ver.4.2
    region, and it is provoked because LSQA is growing below the
    line. The problem is located with ESTAE processing, that is
    allocating a lot of storage pieces of x'500' bytes (aroung 2700
    requests of 1280 bytes). But CICS doesn't shows enough errors to
    justify these requests.
    
    The ESTAEX 0 is used, that the SCB would be deleted on return.
    But if somehow that was not used, then the SCBs would be left
    for the life of the task.
    Also other abends may be seen including 0c4 abend0c4 abends0c4.
    Keywords: CEEPLDLL XPLINK
    

Local fix

  • No Local fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND878 due to excessive LSQA subpool  *
    *                      255 storage usage.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A CICS Java application is using JDBC calls to access DB2.  At
    some point in its processing the application uses the JCICS API
    to issue a syncpoint command.
    
    The syncpoint command is first handled by DFHEIP which is
    managing the CICS-application boundary.  It detects that the
    request has come from an open environment and adds the CICS
    ESTAE to establish the CICS recovery environment.
    
    SYNCPOINT is a threadsafe command so control stays on the J8/9
    TCB that the Java application was using.  As part of the
    syncpoint process a DFHRMCAL TYPE=SYNCPT call is made.  This
    also gets handled by DFHEIP.  DFHEIP incorrectly makes the
    decision that the request is crossing the boundary and adds the
    CICS ESTAE a second time.
    
    When DFHERM has finished processing the DFHRMCAL call it
    determines that the request was not from the application and
    does not remove this second ESTAE that was added by DFHEIP.
    
    When the entire syncpoint command completes DFHEIP removes the
    latest ESTAE and returns to the Java application.
    
    During this process the CICS ESTAE was added twice and only
    removed once.
    
    ESTAEs are represented by SCB control blocks anchored off the
    owning TCB.  These SCB blocks are acquired in LSQA subpool 255
    below the line.  1 SCB block will be orphaned every time a
    JCICS syncpoint command is issued.  Eventually the region will
    run out of below the line storage.
    
    This may lead to an 878 abend or other system abends dependant
    on which service was attempting to obtain more storage.
    
    An additional problem was also identified in DFHKERN where it
    was not addressing the current stack correctly when checking
    KERNACR.  This could lead to the CICS recovery environment not
    being added when it should be.
    

Problem conclusion

  • DFHEIP has been changed to not add the CICS ESTAE for DFHRMCAL
    TYPE=SYNCPT calls.
    
    DFHKERN has been modified to correctly check KERNACR when
    deciding whether to add CICS recovery.
    

Temporary fix

  •             *********
                * HIPER *
                *********
    FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM59329

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-29

  • Closed date

    2012-04-17

  • Last modified date

    2013-03-12

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

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

    PM59876 UK78038 UK78039

Modules/Macros

  •    DFHABAB  DFHAPLI1 DFHAPLI2 DFHAPLI3 DFHAPLJ1
    DFHAPLX1 DFHAPPIS DFHCDKRN DFHCDK64 DFHCPI   DFHDLIDP DFHD2CC
    DFHD2STP DFHD2STR DFHEIP   DFHERM   DFHFCFR  DFHKERN  DFHLONGN
    DFHMQIG  DFHMSGIF DFHMSG64 DFHPGEX  DFHPGLD  DFHPGLE  DFHPGLK
    DFHPGLU  DFHSJAS  DFHSJCS  DFHTRCIF DFHTRC64 DFHUEH   DFHXSEV
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R700 PSY UK78038

       UP12/04/27 P F204

  • R703 PSY UK78039

       UP12/04/27 P F204

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:
12 March 2013