IBM Support

PM80518: DFHXCTRP RECEIVED AN ABEND S0C4 AT OFFSET X'000494'

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You migrate to CICS TS v4.2 and start receiving an 0C4 abend in
    DFHXCTRP at offset x'000494'. The EXCI RESP and REASON data is:
    RESP = x'00000010', (decimal '16') = SYSTEM_ERROR
    REASON = x'0000026F' , (decimal '623')  = ESTAE_INVOKED
    SUBRSN1 = x'000C4000'
    SUBRSN2 = x'00000000'
    
    The failing instruction is a MVC:  D207 8018 5078
    The problem is because the high order word for the 64 bit
    address at x'58' into the DFHTRANCHOR is dirty. The address is
    00000010 23209000 and is the TRA_ENDTAB_PTR.
    
    Additional Symptom(s) Search Keyword(s): KIXREVGJT
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHXCTRP 0C4 abend when DFHXCTRP tries  *
    *                      to create a trace entry in internal     *
    *                      trace table.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A batch job is executed in z/OS to issue the EXCI calls to
    CICS region. The EXCI internal trace table is allocated. GETMAIN
    is called in DFHXCTRI to obtain storage for the trace table
    with R1 contains the start trace table address and bottom half
    of R0 contains the length. TRA_ENDTAB_PTR is used to contain
    the end address of trace table which is calculated by adding R0
    and R1. Since the top half of R0 is not handled when it is used
    to calculate the TRA_ENDTAB_PTR, the value of TRA_ENDTAB_PTR
    will be incorrect if the top half of R0 contains the dirty data.
    
    When writing a new trace record into the trace table,
    TRA_ENDTAB_PTR is used to check if the trace table is full. If
    the TRA_ENDTAB_PTR contains an incorrect value, the end of the
    trace table can not be detected successfully which will cause
    an 0C4 abend when DFHXCTRP attempts to write a new trace record
    beyond the end of the trace table.
    
    Keywords : abend0C4  abendS0C4
    

Problem conclusion

  • DFHXCTRI has been changed so that the TRA_ENDTAB_PTR can be
    calculated correctly.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM80518

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-13

  • Closed date

    2013-01-25

  • Last modified date

    2015-03-04

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

    PM77040

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

    UK91179

Modules/Macros

  • DFHXCTRI
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R800 PSY UK91179

       UP13/02/02 P F302

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

Document Information

Modified date:
04 March 2015