IBM Support

PM78215: QMF FOR CICS IDENTIFIED BY DB2 AS A LONG RUNNING READER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Starting QMF as a CICS transaction and remaining in the start
    panel without further actions causes DSNB260I messages.
    QMF for TSO doesn't have this behaviour.
    
    For example:
    The following msgs from DB2 master address space output:
    
    DSNB260I  -DBSP DSNB1PCK WARNING - A READER HAS BEEN
    RUNNING FOR 130 MINUTES
               CORRELATION NAME=POOLQMFE0001
               CONNECTION ID=TCICS82
               LUWID=llllllll.LUTSDBSP.CA8249F1FB32=79
               PLAN NAME=QMF10
               AUTHID=T06931A
               END USER ID=*
               TRANSACTION NAME=POOLQMFE
               WORKSTATION NAME=*
    
    -DISPLAY DB CLAIMERS shows the thread is holding (CS,C) claims
    on some catalog tablespaces and one QMF tablespace, OBJECTRD.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All QMF for CICS V10.1 users.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Users running QMF for CICS may notice   *
    *                      held claimers on QMF catalog            *
    *                      tablespaces and index spaces after      *
    *                      entering QMF under CICS and just being  *
    *                      on the QMF home panel. Tablespaces      *
    *                      DSQTSCT1, DSQTSCT3 and index spaces     *
    *                      OBJECTRO and OBJECTRD may be involved.  *
    *                      Users may see this same situation       *
    *                      when using the DISPLAY, RUN, PRINT      *
    *                      and EXPORT commands that involve        *
    *                      QMF objects.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running under CICS, QMF was neglecting to issue the COMMIT
    statement under certain circumstances involving the DISPLAY,
    RUN, PRINT and EXPORT commands involving QMF objects (QUERIES,
    PROCS and FORMS).  Additionally, QMF was not issuing a COMMIT
    during Q.SYSTEM_INI processing during initialization. When
    running under TSO, QMF does issue the proper COMMIT
    statements in these circumstances.
    

Problem conclusion

  • Module DSQDCKRT has been modified to issue COMMIT statements
    under CICS as it does under TSO.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM78215

  • Reported component name

    QMF-QUERY MGMT

  • Reported component ID

    566872101

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-30

  • Closed date

    2012-12-12

  • Last modified date

    2013-03-22

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

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

    UK90273

Modules/Macros

  • DSQDCKRT
    

Fix information

  • Fixed component name

    QMF-QUERY MGMT

  • Fixed component ID

    566872101

Applicable component levels

  • RA10 PSY UK90273

       UP12/12/14 P F212

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCWRCK","label":"QMF for TSO\/CICS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
22 March 2013