PH12193: ERRONEOUS -905 RECORDED IN NEGATIVE SQL CODES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Erroneous -905 recorded in Negative SQL Codes
  Query Monitor showing erroneous -905 recorded in Negative SQL
  Codes
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM Db2 Query Monitor z/OS                   *
  *                 users of component                           *
  *                 - ISPF Client                                *
  *                 - SQL Codes                                  *
  *                 - CQM Data Offload and Batch Reporting       *
  *                 - Compatibility                              *
  *                 - TCz                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. Erroneous -905 recorded in Negative  *
  *                      SQL Codes                               *
  *                      2. CQM1153E message may be written in   *
  *                      file with Query Monitor data for        *
  *                      loading into history tables. In such    *
  *                      case Load job fails with                *
  *                      ABEND=S04E U0000 REASON=00E40347.       *
  *                      3. CQM Offload SAMPLIB member CQM@LDB2  *
  *                      has references to DDs TEXTDATA,         *
  *                      EXCPTEXT, SQLCTEXT which are not used.  *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  1. In some cases, Query Monitor may report -905 code, which
  corresponds to Resource limit exceeding, for threads which are
  not controlled by RLF.
  
  2.1 Error message CQM1153E was written in output file, intended
  for uploading into history table, overlaying data for Load
  utility.
  2.2 The structure of the error file was not clear.
  2.3 In statistical part of offload joblog the information about
  output datasets for LOB tables was missed.
  2.4 If the step for preparation of output file for LOAD utility
  had some errors with data, it still finished with return code 0
  which causes DSNUTIL be called and failed on the loading
  incorrect data.
  2.5 The length shown in CQM7014I message was incorrect. It
  showed the length of first record instead of summary of all
  records' lengths.
  
  3. In Query Monitor 3.3 Offload job for non-IDAA tables use the
  DD names TEXTCLOB, EXCPCLOB, SQLCCLOB instead of TEXTDATA,
  EXCPTEXT, SQLCTEXT. This caused confusion because both lists of
  DDs are required and set in Offload job for non-IDAA.
  

Problem conclusion

• 1. The detecting the SQL code was corrected.
  
  2.1 Logic was changed to create the correct output file intended
  for uploading into history table and to put error messages only
  into error file.
  2.2 The structure of error file records was updated
  to make it more readable.
  2.3 Information about output datasets for
  LOB tables was added in offload joblog.
  2.4 Now if there are any corruption of data, the step for
  preparation finishes with return code 4, which prevents from
  calling DSNUTIL. If it is a field translation error, the
  resulting dataset contains "N/A" value for the field with
  problem. Customer should review the resulting dataset manually
  based on created error file and decide whether the data is
  acceptable for load into Query Monitor history tables.
  If it is acceptable data, customer can restart offload job from
  the step for DSNUTILB.
  2.5 The length in CQM7014I message was corrected. Message
  CQM7014I was also enhanced to include the number of errors
  happened during processing of the interval datasets.
  
  3. Offload job for IDAA tables use only the DD names TEXTDATA,
  EXCPTEXT, SQLCTEXT. Offload job for non-IDAA tables use the DD
  names TEXTCLOB, EXCPCLOB, SQLCCLOB and does not check any more
  for existence of TEXTDATA, EXCPTEXT, SQLCTEXT DD names.
  Samples are updated to reflect this change.
  
  
  Search Keywords:
  -905 SQL CODE FOR NON RLF THREAD
  OFFLOAD ABEND S04E REASON 00E40347
  NON IDAA DD NAME TEXTDATA, EXCPTEXT, SQLCTEXT CQM@LDB2 CQM@LIDA
  

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:

  UI64671

Modules/Macros

• CQM#ARCX CQM#CTLF CQM#LOAX CQM#QAPI CQM#QAPX CQM#QSQL CQM#UINX
  CQM$ACTV CQM$BUFP CQM$CALL CQM$CPRF CQM$DB2C CQM$DDB2 CQM$DELY
  CQM$ERRP CQM$HSTV CQM$INTD CQM$INTV CQM$LOCK CQM$OBJS CQM$PROF
  CQM$QRPT CQM$SM01 CQM$SQC2 CQM$SQC3 CQM$SQCI CQM$SQCM CQM@LDB2
  CQM@LIDA CQM@WDB2 CQMMEACX CQMMEAPX CQMMEARX CQMMEASX CQMMEBCX
  CQMMEBPX CQMMEBRX CQMMEBSX CQMMECCX CQMMECPX CQMMECRX CQMMECSX
  CQMMQAPX
  

Fix information

• Fixed component name

  DB2 QUERY MONIT

• Fixed component ID

  5655E6701

Applicable component levels

• R330 PSY UI64671

     UP19/08/14 P F908

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.