IBM Support

PI67645: RECURSIVE DFHSM0001 AND DFHTF0001 0C4/AKEA, X'141C' IN DFHSMGF AND X'26BA' IN DFHTFIQ 16/10/05 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS starts dumping recursively with SM0001 and TF0001
    abends.  You'll see mostly the following messages.
    .
    DFHSM0001  An abend (code 0C4/AKEA) has occurred at offset
    X'141C' in module DFHSMGF.
    .
    DFHTF0001 An abend (code 0C4/AKEA) has occurred at offset
    X'26BA' in module DFHTFIQ.
    .
    The 0C4 occurs in DFHTFIQ in the FREEMAIN_PROTECTED_FIELD_DATA
    proc because the address/length of the storage being freed is
    invalid.  It is proc ERASE_PROTECTED_FIELDS in DFHTFIQ that
    sets up the FREEMAIN address. The problem is that TCTTETEA, the
    address of the BMS extension, is zeroes so the FREEMAIN
    address/length get set up using data from low core.
    .
    It appears a mirror task abended AZVE during task
    initialization.  This has meant that the TCTTE was completely
    setup as it would be for a normal task.  After DFHXMAB has run
    to abend the task, DFHPGPG calls DFHTFIQ function CHECK_BMS to
    free the terminal storage used for BMS field checking.  DFHTFIQ
    assumes that if it has a valid TCTTE it must have a BMS
    extension so continues without checking that address.  The BMS
    extension was never created so the address is 0.  A bad address
    gets picked up from low core to be freemained.  DFHTFIQ then
    attempts to set the address to 0 which will cause the 0C4.
    .
    Need to ensure that in this error situation DFHTFIQ will make
    sure that a BMS extension exists before trying to access fields
    within it.
    Additional Symptom(s) Search Keyword(s): KIXREVrer
    DFHSM0102 SM0102 Storage violations
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users  with PI50363 applied.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: An abend 0C4 or a severe error (code    *
    *                      X'0305') in module DFHSMGF, and an      *
    *                      abend 0C4 in module DFHTFIQ.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There is an abend 0C4 in module DFHTFIQ due to an attempted
    invalid freemain with messages DFHSM0001 or DFHSM0002 and
    message DFHTF0001.
    
        DFHSM0001 applid An abend (code 0C4/AKEA) has occurred at
        offset X'nnnn' in module DFHSMGF.
    
        DFHSM0002 applid A severe error (code X'0305') has occurred
        in module DFHSMGF.
    
        DFHTF0001 applid An abend (code 0C4/AKEA) has occurred at
        offset X'nnnn' in module DFHTFIQ.
    
    This may occur if a TCTTE does not have a BMS extension in which
    case the TCTTETEA BMS extension address is zero. The TCTTETEA is
    addressing low core with TCTTEBFL at offset x'34' in low core.
    
    If TCTTEBFL is zero no freemain is attempted and consequently
    there is no error.  However, if TCTTEBFL is non-zero it is
    assumed to point to a valid BMS Checking table, and its length
    is obtained from that area which might give an S0C4 abend, but
    if that succeeds a freemain routine is called with the invalid
    address and invalid length which results in a freemain error and
    an S0C4 abend in module DFHTFIQ.
    
    Additional keywords:
    DFHSM0102 SM0102 Storage violations
    

Problem conclusion

  • UI38910 UI38914
    DFHTFIQ is updated to add a check which ensures the TCTTETEA is
    non-zero and therefore has a valid TCTTEBFL pointer to the BMS
    Checking table before any freemain is attempted.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI67645

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-16

  • Closed date

    2016-10-17

  • Last modified date

    2016-11-02

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

    PI65435

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

    UI41890 UI41891

Modules/Macros

  • DFHTFIQ
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R600 PSY UI41890

       UP16/10/29 P F610 {

  • R700 PSY UI41891

       UP16/10/29 P F610 {

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:
02 November 2016