PI78476: PERFORMANCE ISSUES WHEN ERASEING A QUERY OR PROC

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• performance issues when ERASEing a query or proc
  

Local fix

• DROP the Q.OBJECT_OBJDATAX index and create a new one adding
  TYPE.
  Use the following example:
  
  CREATE TYPE 2 UNIQUE INDEX
  Q.OBJECT_OBJDATAX
  ON Q.OBJECT_DATA
  ("OWNER" ASC, "NAME" ASC, "TYPE" ASC, "SEQ" ASC)
  USING STOGROUP DSQSGCTL
  PRIQTY XXX
  SECQTY YYY
  NOT PADDED
  CLUSTER
  CLOSE NO;
  
  This should give index access during ERASE QUERY in the
  offending SQL statement from DSQIFLDR.
  
  Remember to run RUNSTATS and rebind the QMF packages again after
  creating the new index as recommended in the "DB2 for z/OS
  11.0.0 Managing DB2 performance Maintaining data organization
  and statistics" Knowledge Center topic online at the following
  URL:
  
  https://ibm.biz/BdicuM
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All QMF for TSO/CICS V11.2 and V12.1 users   *
  *                 who have completed installation or migration *
  *                 into a DB2 for z/OS database.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Users may experience DB2 performance    *
  *                      problems using theERASE or RENAME       *
  *                      commands due to tablespace access       *
  *                      scanduring underlying SQL from program  *
  *                      DSQIFLDR.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  QMF catalog index, Q.OBJECT_OBJDATAX, needs to be modified
  to add one additional column, TYPE. The QMF installation
  process has been modified to create Q.OBJECT_OBJDATAX with
  the additional column.
  *
  Users who have already completed migration to QMF 11.2 or
  QMF 12.1 without this APAR are advised to
  DROP INDEX Q.OBJECT_OBJDATAX and rerun QMFvrm.SDSQSAPE(DSQ1BLNI)
  to recreate the index in the proper manner. Or, rather than
  rerunning DSQ1BLNI, after dropping the
  index the users could run the following sample DDL:
  CREATE TYPE 2 UNIQUE INDEX
  Q.OBJECT_OBJDATAX
  ON Q.OBJECT_DATA
  ("OWNER" ASC, "NAME" ASC, "TYPE" ASC, "SEQ" ASC)
  USING STOGROUP DSQSGCTL
  PRIQTY XXX
  SECQTY YYY
  NOT PADDED
  CLUSTER
  CLOSE NO;
  In either case, after recreating the index, job
  QMFvrm.SDSQSAPE(DSQ1BPKG) should be rerun to bind QMF packages.
  

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

  UI46041 UI46042

Modules/Macros

•    DSQ1BLNX
  

Fix information

• Fixed component name

  QMF-QUERY MGMT

• Fixed component ID

  566872101

Applicable component levels

• RB20 PSY UI46041

     UP17/04/01 P F703

• RC10 PSY UI46042

     UP17/04/01 P F703

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.