IBM Support

PI62546: CICS CAN GO INTO A WAIT IF A TASK IS CANCELLED WITH AUXTRACE ACTIVE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If AuxTrace is active and a transaction is purged there is a
    small window when CICS can go in wait.
    DFHTRSU issues message DFHTR0116 because of an AKEH abend.
    If the task is running on open TCB, have auxtrace active and to
    have just come out of an ECB WAIT for the I/O for the aux
    buffer when the transaction is purged.
    In this case the tracing of the return from DB2 was being issued
    from DFHD2D2 (on an L8 TCB), DFHTRPT issued the TRACE PUT call,
    and had acquired the trace lock. The bit indicating that the
    trace lock was held had been set and a call to DFHTRSU
    WRITE_AUX_BUFFER had been issued.
    This issues a DFHTRATM CHECK call which drives DFHTRAO and its
    DFHTRAO which issue the ECB wait.
    If at this point the transaction is purged then DFHTRSU's
    recovery routine is driven, which issues the DFHTR0116 message
    and sets the aux trace to paused, but it does not percolate
    back to DFHTRPT's recovery routine, which is where the trace
    lock would have been freed.
    The transaction should be protected from being purged whilst in
    the trace modules.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Following a purge of a CICS             *
    *                      transaction, CICS region may enter      *
    *                      wait.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Following a purge of a CICS transaction, the CICS region may go
    into a wait. This problem can occur when AUXTRACE is active and
    the CICS transaction has done a call to DB2. Should the purge of
    the CICS transaction happen to occur in the CICS code writing
    out the trace record then the CICS region will enter a wait and
    need to be restarted.
    

Problem conclusion

  • DFHD2D2 has been changed to protect the writing of trace records
    from being purgeable.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI62546

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-17

  • Closed date

    2016-07-21

  • Last modified date

    2016-08-02

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

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

    PI64045 UI39582 UI39583

Modules/Macros

  • DFHD2D2
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R800 PSY UI39582

       UP16/07/30 P F607 ¢

  • R900 PSY UI39583

       UP16/07/30 P F607 ¢

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