IBM Support

PK09295: AFTER QMF/TSO V8 UPGRADE (COMPATIBILITY), EXPERIENCING A 20% INCREASE IN CPU TIMES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After installing QMF/TSO V8 upgrade (Compatibility), user did
    experienced a 20% increase in CPU times
    *
    This performance degradation may be noticed when running QMF V8
    compatibility mode in either a DB2 UDB for z/OS V8 database
    running in compatibility mode or a DB2 UDB for z/OS V7 database.
    *
    To alleviate the performance problem, the following workaround
    may be immediately implemented. Using SPUFI or QMF, create 3 new
    indexes using the following DDL:
    CREATE TYPE 2 UNIQUE INDEX
            Q.OBJECT_REMNAMEX
            ON Q.OBJECT_REMARKS
            ("NAME ASC, "OWNER" ASC)
              USING STOGROUP DSQSGCTL
              PRIQTY 200
              SECQTY 20
              CLOSE NO;
    CREATE TYPE 2 UNIQUE INDEX
            Q.OBJECT_OBJDATANAMX
         ON Q.OBJECT_DATA
           ( "NAME" ASC, "SEQ" ASC,"OWNER" ASC)
            USING STOGROUP DSQSGCTL
            PRIQTY 200
            SECQTY 20
            CLOSE NO;
    CREATE TYPE 2 UNIQUE INDEX
             Q.OBJECT_DIRECTNAMEX
          ON Q.OBJECT_DIRECTORY
         ("NAME" ASC, "OWNER" ASC)
           USING STOGROUP DSQSGCTL
           PRIQTY 200
           SECQTY 20
           CLOSE NO;
    and rebind the QMF V8 runtime packages using the bind job,
    QMF810.SDSQSAPE(DSQ1BPKG).
    *
    DB2 for z/OS V8 compatibility mode users should also apply DB2
    APAR PK12389/PK17117.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All QMF for TSO/CICS V8.1 users running in a *
    *                 DB2 UDB for z/OS V7 or DB2 UDB for z/OS V8   *
    *                 compatibility mode database.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Users running QMF in a DB2 UDB for z/OS *
    *                      V7 or V8 compatibility mode database    *
    *                      experience poor performance due to      *
    *                      processing involving nonmatching index  *
    *                      scans on the QMF control tables.        *
    *                      Performance problems will probably be   *
    *                      detected in databases that contain      *
    *                      large numbers of QMF objects (queries,  *
    *                      forms, and procs).                      *
    ****************************************************************
    * RECOMMENDATION: Apply this fix and rerun the QMF bind        *
    *                 package job, QMF810.SDSQSAPE(DSQ1BPKG).      *
    ****************************************************************
    The performance problem occurred because DB2 was not
    using the QMF indexes to access data from the QMF control
    tables.  The QMF control tables are accessed by internal QMF SQL
    (static SQL) bound in QMF runtime packages.  For QMF 8.1, QMF
    internal SQL processing was changed to define host variables
    that will accomodate 128 character authorization and name
    processing.  When QMF 8.1 ran in a DB2 UDB for z/OS V7 or V8
    compatibility mode database that has 8 character
    authorization id and 18 character name limitations, a datatype
    mismatch was detected by DB2 and the index search was nullified.
    QMF commands that experience the performance problems:
    SET PROFILE, DISPLAY, SAVE, CONNECT, ERASE.
    Unqualified QMF object names experience the worst
    performance. QMF 8.1 New Function Mode processing is not
    affected by this change nor will QMF 8.1 New Function Mode
    experience the same (original) performance problem.
    

Problem conclusion

  • QMF has modified internal SQL processing to properly match host
    variable declarations with the underlying QMF control table DDL
    definitions.  This change will allow for index usage in the
    above mentioned databases.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK09295

  • Reported component name

    QMF-QUERY MGMT

  • Reported component ID

    566872101

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-07-21

  • Closed date

    2005-08-25

  • Last modified date

    2007-08-20

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

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

Modules/Macros

  • DSQEBOR  DSQECSQL DSQEICVS DSQELD   DSQEPR
    DSQESV   DSQEUPRF DSQIBOR  DSQICSQL DSQIICVS DSQILD   DSQIPR
    DSQISV   DSQIUPRF
    

Fix information

  • Fixed component name

    QMF-QUERY MGMT

  • Fixed component ID

    566872101

Applicable component levels

  • R810 PSY UK06649

       UP05/09/01 P F508

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":"8.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
20 August 2007