IBM Support

PK73340: NO AICA FOR TASK IN NON-YIELDING LOOP ON L8/L9 TCB UNTIL ICVR TIMES 10 HAS BEEN REACHED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A task in a non-yielding loop on a L8/L9 TCB will not get
    AICA'd until ICVR times 10 has been reached.
    If ICVR is set to 3000 ms, the task will be timed out by CICS
    if 30000 ms is reached.
    The expectation is that the timeout will occur after
    3000 ms as is the case with loops on the QR TCB.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Tasks running under L9 TCBs take over   *
    *                      ten times longer to be abended AICA     *
    *                      than they should do.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DFHKETIX has logic to multiply by 10 the runaway timeout value
    for those tasks running under non-essential TCBs. This
    adjustment to task runaway timeout was intended to avoid
    Java programs running under J8 TCBs from being invalidly AICA-
    abended while performing CPU-intensive work. However, it means
    that if a threadsafe program (running under an L9 TCB) enters
    into a non-yielding loop, the runaway timeout abend will take
    approximately 10 times longer to occur than is expected.
                                                                   .
    KEYWORDS: Abend AbendAICA AICAs AbendAICAs OTE open transaction
              environment ketix userkey
    

Problem conclusion

  • DFHKETIX has been modified to handle tasks running under L9 TCBs
    in the same manner as essential TCB tasks, and not scale up
    their runaway interval by a factor of ten.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK73340

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-07

  • Closed date

    2009-01-21

  • Last modified date

    2009-02-02

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

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

    UK43344

Modules/Macros

  •    DFHKETIX
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R500 PSY UK43344

       UP09/01/23 P F901

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

Document Information

Modified date:
02 February 2009