IBM Support

PH08005: DFHDS0004 LOOP IN DFHDSAT WITH MVS GETMAINS & FREEMAINS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During the attach of a new task, DFHDSAT issues message
    .
    DFHDS0004 A possible loop has been detected at offset X'FFFF'
     in module DFHDSAT.
    .
    Kernel error data shows abend 999/AKEC for the task indicating
    a loop was detected in DFHDSAT +x'900'. MVS system trace shows
    a loop of MVS GETMAINs/FREEMAINs from DFHDSAT, acquiring and
    freeing the same storage address.
    .
    Kernel stacks show processing is in the GET_TASK_PAGE routine
    in DFHDSAT. Dispatcher maintains its own page for quick-celled
    DTAs in a PAM (Page Allocation Map). The problem causing the
    loop of MVS GETMAINs/FREEMAINs from DFHDSAT is that the number
    of tasks in the region has grown until there is no more room
    left in the PAM to save the newly GETMAINed page. However,
    DFHDSAT should put out an error instead of loop.
    .
    Additional Symptom(s) Search Keyword(s): KIXREVxxx
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHDSAT loop of getmains and freemains. *
    ****************************************************************
    The loop in DFHDSAT is the result of another problem which
    created a build up of DTAs due to the attach of system
    tasks which were unable to run.
    The upper limit of 5120 DTAs was eventually reached.
    The next attach of a system task tried to acquire a new DTA.
    Dispatcher domain set a bad return pointer because it could not
    allocate a new DTA.
    This return pointer was wrongly interpreted and dispatcher
    tried to acquire a DTA again, which resulted in a loop.
    Keywords: DFHXM0213 msgDFHXM0213
    

Problem conclusion

  • Dispatcher domain has been changed to set the return pointer
    correctly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08005

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-31

  • Closed date

    2019-05-07

  • Last modified date

    2019-06-03

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

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

    UI62862 UI62863 UI62864

Modules/Macros

  • DFHDSAT  DFHDSDS2 DFHDSSR
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI62862

       UP19/05/08 P F905

  • R100 PSY UI62864

       UP19/05/08 P F905

  • R200 PSY UI62863

       UP19/05/08 P F905

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

Document Information

Modified date:
03 June 2019