IBM Support

PH64002: CICS REGION HANG UP WHEN THE QR TCB WENT IN MVS WAIT WITHOUT AN ACTIVE STIMER SET 24/11/11 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When there are no tasks to be dispatched CICS QR TCB goes into
    MVS Wait with a STIMERM set to wakeup QR TCB in a near future.
    During this process CICS may fail to set an active STIMERM which
    causes QR TCB enter into MVS WAIT leaving no active STIMERM set
    thus CICS will be waiting indefinitely until any interrupt
    occurs.
    Additional Symptoms and Keywords:
    KIXREVLHCF CICS hangup hangs
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users with UI96194 applied.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS appears to stall and not process   *
    *                      any work. The region was not short on   *
    *                      storage or at maxtask.                  *
    ****************************************************************
    PH60353 changed DFHDSDS3 and exposed this base code problem
    whereby an STIMER_ARRAY entry can contain a bad 5th byte instead
    of being rounded to the next tick boundary of 00, 40, 80 or
    C0 - i.e. quarter second boundaries, and the rest of the 2nd
    word zero.
    
    For example, the following STIMERM time in the STIMERM array is
    invalid because the 5th byte is D2 -
    
    DFEAA086 D2000000
    
    This means that the QR TCB can return to MVS with no active
    STIMERM to reawaken it. As this customer had no external work
    to post CICS back into life (no VTAM or MRO activity) and had
    ICV set to 5000, there was no cause for QR to wake up again.
    CICS entered a state where it appeared to be hung, with interval
    work waiting for interval control suspends that were not being
    honoured when they had expired.
    

Problem conclusion

  • UI96194
    DFHDSDS3 has been changed to ensure that the STIMERM array
    contains a valid 5th byte in its time field i.e. 00, 40, 80 or
    C0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH64002

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-11-05

  • Closed date

    2024-12-06

  • Last modified date

    2025-01-02

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

    PH63982

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

    UI99317

Modules/Macros

  • DFHDSDS3
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R300 PSY UI99317

       UP24/12/10 P F412 {

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":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.6","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
02 January 2025