PK72434: QUERY MONITOR ABENDS AFTER UPGRADING FROM V8 TO V9, OR FALLING BACK FROM V9 TO V8, WHILE CQM IS MONITORING DB2.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Query Monitor and DB2 may ABEND after upgrading DB2 from V8 to
  V9, or falling back from V9 to V8, while CQM is monitoring the
  DB2 undergoing the version change. Additional symptoms may
  include ABEND0C1 DSNJW001+001C, resulting in abnormal
  termination of DB2.
  

Local fix

• A workaround is provided by running a utility to remove hooks
  installed for the version of the monitored DB2, and allow
  monitoring to continue at the new DB2 version.
  1. Create and customize the utility job using this sample JCL,
  following the instructions included in the JCL:
  //jobcard your jobcard
  //**************************************************************
  //*
  //* Licensed Materials - Property of IBM
  //* 5697-I03
  //* (c) Copyright IBM Corp. 1999, 2005 All Rights Reserved.
  //* (c) Copyright Rocket Software, Inc. 1999, 2005 All Rights
  //* US Government Users Restricted Rights - Use, duplication, or
  //* disclosure restricted by GSA ADP Schedule Contract with IBM
  //*
  //* INSTRUCTIONS:
  //*
  //* ISSUE CHANGE COMMANDS:
  //*
  //*  REPLACE JOBCARD WITH JOBCARD SUITABLE TO YOUR INSTALLATION
  //*
  //*  C #QM#     TO THE CQM THAT IS MONITORING THE DB2 THAT HAS
  //*             VERSIONS
  //*
  //*  C #DB#     TO THE DB2 THAT HAS CHANGED VERSIONS
  //*
  //*  C #USRHI#  TO A HIGH LEVEL QUALIFIER FOR THE OUTPUT DATASET
  //*             DD CARD CQMYDATA
  //*
  //*  C #CQMHI#  TO THE HIGH LEVEL QUALIFIER FOR THE CQM
  //*             EXECUTABLE CODE
  //*
  //*  C #FECHI#  TO THE HIGH LEVEL QUALIFIER FOR THE FEC
  //*             EXECUTABLE CODE
  //*
  //**************************************************************
  //IDCAMS  EXEC PGM=IDCAMS
  //SYSPRINT DD SYSOUT=*
  //SYSIN    DD *
   DELETE #USRHI#.CQMYDATA
   SET MAXCC = 0
  //STEP1   EXEC PGM=CQM#YDAT,REGION=6M
  //STEPLIB  DD DSN=#CQMHI#.SCQMLOAD,DISP=SHR
  //         DD DSN=#FECHI#.SFECLOAD,DISP=SHR
  //SYSPRINT DD   SYSOUT=*
  //UTPRINT  DD   SYSOUT=*
  //SYSUT1   DD   UNIT=SYSALLDA,SPACE=(CYL,(10,10))
  //SORTOUT  DD   UNIT=SYSALLDA,SPACE=(CYL,(10,10))
  //CQMYDATA DD DSN=#USRHI#.CQMYDATA,DISP=(,CATLG),
  //  UNIT=SYSALLDA,SPACE=(CYL,(1,1),RLSE),
  //  DCB=(LRECL=32756,BLKSIZE=0,RECFM=VB)
  //CQMLOADP DD *
     CQM_SUBSYSTEM(#QM#)
     CLEAR_AREA(SQLHS,#DB#,58,C0)
  /*
  2. Ensure that CQM is monitoring the DB2 to be upgraded or
  fallen back.
  3. Stop the DB2 subsystem.
  4. Afer CQM issues the CQM3003I DB2 shutdown detected message,
  run the customized job and verify a return code of 0.
  customized job and verify a return code of 0.
  5. Upgrade or fall back the DB2 version and restart the DB2
  subsystem.
  6. When CQM detects the startup, the new hooks will be installed
  for the correct version of DB2.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM DB@ Query Monitor           *
  ****************************************************************
  * PROBLEM DESCRIPTION: Query Monitor ABENDs after upgrading    *
  *                      from V8 to V9, or falling back from V9  *
  *                      to V8, while CQM is monitoring the DB2  *
  *                      undergoing the version change.LOCAL     *
  *                      FIX:A workaround is provided by running *
  *                      a utility to remove hooks installed for *
  *                      the version of the monitored DB2, and   *
  *                      allow monitoring to continue at the new *
  *                      DB2 version.  1.  Create and customize  *
  *                      the utility job using this sample JCL,  *
  *                      following the instructions included in  *
  *                      the JCL://jobcard your jobcard          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Code changes have been made to address these issues.
  

Problem conclusion

• Apply the PTF.
  

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:

  UK41562

Modules/Macros

•    CQM#EXCP CQM#SSMN CQM@CCAF CQMMINDX CQMMINST
  CQMOINST
  

Fix information

• Fixed component name

  DB2 QUERY MONIT

• Fixed component ID

  5655E6701

Applicable component levels

• R230 PSY UK41562

     UP08/11/19 P F811

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.