IBM Support

PH01185: SCANNING OF TSQS DOES NOT HAPPEN CONSISTENTLY; NEED DIAGNOSTIC MESSAGE TO DETERMINE WHY.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are running with a number of TSQ models, and a number of
    active queues were created with the specifications of those
    models.  You expect periodic scans of the TSQs to determine
    which require deletion, on an interval based on 10% of your
    model's expiry time.  There are gaps in the scan intervals that
    are far longer, based on the times of the message:
    DFHTS1605 Scan of local temporary storage queues completed.
    XXXX local temporary storage queues were scanned and YYYY were
    deleted.
    .
    Occasionally, the buildup of undeleted TSQs results in message
    DFHTS1315 The temporary storage data set has exceeded the
    maximum number of control intervals supported.
    .
    There are some legitimate reasons NOT to run a scan:
    * A scan is already running
    * There are no TSMODEL resources with non-zero expiry times.
    * It's not yet time to perform a scan, based on the previous
       run.
    .
    These conditions do not appear to apply
    .
    There is no message that indicates that CICS has opted not to
    scan the TSQs, nor any indication of how many times the scan
    has been bypassed.  You would like additional CICS messaging to
    indicate when a scan is not performed for an interval, and a
    count of the consecutive intervals for which this occurred.
    .
    Additional Symptom(s) Search Keyword(s): KIXREVEAA
    

Local fix

  • Manual deletion of TSQs may control the buildup of those
    requiring deletion.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: No message issued when the TS           *
    *                      clean up task detects an earlier        *
    *                      instance is still running.              *
    ****************************************************************
    The CICS temporary storage clean up task (DFHTSCL)
    is invoked as a timer callback gate for the TS domain.
    It should be called every 1 minute from the time
    TS domain initialises. If it detects that a previous instance
    of the clean up task is still active then it terminates but no
    message is issued to indicate this unusual condition has
    occurred.
    

Problem conclusion

  • DFHTSCL has been enhanced to detect whether a previous instance
    of the clean up task is still active, and issue new message
    DFHTS1609 if that is the case.
    The CICS Transaction Server 5.2, 5.3 and 5.4 Messages and
    Codes Volume 2 manual will be updated to include new message
    DFHTS1609:
    .
    DFHTS1609 date time applid terminal
    The TS queue clean up task could not start because it was
    already running.
    Explanation: An attempt to run the TS clean up task failed
    because a previous instance of the task is still running.
    It is unusual for the TS clean up task to take a long
    time to run.
    This might happen if locks are being held on queues.
    System action: Automatic deletion of TS queues is not
    performed.
    The clean up task that is already running needs
    to complete first.
    User response: Check whether there are any signs of problems
    with your TS queues.
    Refer to the section, "Automatic deletion of temporary
    storage queues" in the CICS Knowledge Center.
    Module: DFHTSCL
    Message inserts:
    1. date
    2. time
    3. applid
    Destination: CSMT
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH01185

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-01

  • Closed date

    2018-09-11

  • Last modified date

    2018-10-02

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

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

    UI58422 UI58423 UI58424

Modules/Macros

  • DFHEIQTS DFHEITS  DFHMETSC DFHMETSE DFHMETSK DFHMIRS  DFHTSAD
    DFHTSAM  DFHTSBR  DFHTSCL  DFHTSDM  DFHTSDQ  DFHTSDUC DFHTSDUF
    DFHTSDUS DFHTSITR DFHTSMB  DFHTSP   DFHTSPT  DFHTSQR  DFHTSRM
    DFHTSSH  DFHTSSQ  DFHTSSR  DFHTSST  DFHTSWQ
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI58424

       UP18/09/14 P F809

  • R100 PSY UI58423

       UP18/09/13 P F809

  • R900 PSY UI58422

       UP18/09/13 P F809

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

Document Information

Modified date:
02 October 2018