PM49113: QMF FOR TSO USING DEFAULT FORM CAN REPORT SOME BIGINT NUMBERS AS ASTERISKS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In QMF V9 running in DB2 V9 ENFM and lower, user runs this
  query:
  SELECT -999999999999999  FROM SYSIBM.SYSDUMMY1
  and receives a report back that looks like:
                COL1
  ------------------
    -999999999999999
  The default form for the report shows and EDIT CODE of 'L' and
  a WIDTH of 18.
  *
  The user runs the same exact query in QMF V9 with a DB2 V9 NFM
  database (and higher) and receives this report:
         COL1
  -----------
  ***********
  The default form shows an EDIT CODE of L and a WIDTH of 11.
  *
  

Local fix

• Increase the WIDTH of the column on the default form to see
  the complete data value.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All QMF for TSO/CICS users running queries   *
  *                 containing BIGINT columns.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Users running queries that select       *
  *                      BIGINT columns may see '*******'        *
  *                      (asterisks) indicating the numeric      *
  *                      overflow condition. This can happen for *
  *                      a BIGINT data value that is in the      *
  *                      valid range of -9223372036854775808 to  *
  *                      9223372036854775807 but only happens    *
  *                      for numbers less than -9999999999 and   *
  *                      greater than 9999999999.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the query SELECT -999999999999999  FROM SYSIBM.SYSDUMMY1 is
  run from QMF V9 or QMF V10 in DB2 for z/OS V9 ENFM or earlier,
  DB2 returns a data type of 484 (packed decimal) with a precision
  of 15 and a scale of 0. On a default QMF form, QMF formats that
  number based on QMF's design for decimal numbers which is a 'L'
  edit code with the width of 18. When the same query is run from
  QMF V9 or QMF V10 in DB2 for z/OS V9 NFM and higher database,
  DB2 returns a data type of 492 (BIGINT) which when formatted on
  the QMF default form gets a edit code of 'L' with a default
  width of 11. As 11 places is not enough to hold the largest
  BIGINT number, the user will see asterisks ('*****') on the
  default QMF report that appears when the query is run.
  

Problem conclusion

• QMF will increase the default width on the default QMF form for
  the BIGINT data type from 11 to 20 to accommodate the largest
  BIGINT number along with sign.
  

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:

  UK72728 UK72729

Modules/Macros

• DSQFSCOL
  

Fix information

• Fixed component name

  QMF-QUERY MGMT

• Fixed component ID

  566872101

Applicable component levels

• RA10 PSY UK72728

     UP11/10/08 P F110

• R910 PSY UK72729

     UP11/10/08 P F110

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.