Sysview for Db2 data collector failed with RC=52 and DBG01014E after applying latest PTFs to release r19

Products

• SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

When the Sysview Performance Management Option for Db2 for z/OS (IDB2) data collector was started after the latest PTFs
were applied to the r19 release, the IDB2 data collector failed with RC=52.  The following messages appeared in the job log:

DBG99001E ssid 10:04:46 ERROR IN COMMAND STREAM, PROCESSING ENDED 
..
DBG04004I ssid 10:04:45 REQUEST DSQTHD   FROM STARTUP
..
DBG01014E ssid 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LEN     

DBG02018E ssid 10:04:45 INVALID FIELD SPECIFICATION                                                                                                   
          4112    PACKAGE-ID-LONG                          (PF=A128)   

DBG01014E ssid 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LONG

Resolution

From the DBG error messages such as the DBG01014E, it seems that the following words were misspelled.

PACKAGE-ID-LEN and PACKAGE-ID-LONG

 

The PACKAGE-ID-xxxxxx fields were changed to PACKAGE-PGM-xxxxxxx by the applied solution. The following comments
were added the DSQTHD member in the hlq.CDBATREQ library.

*---------------------------------------------------------------------
* - changed field package-id to package-pgm.
*---------------------------------------------------------------------

Therefore, the PACKAGE-PGM-LEN and PACKAGE-PGM-LONG are correct. And those fields were reflected in the DSQTHD member in the hlq.CDBATREQ.

However, the following error messages appeared in the IDB2 data collector job log though the DSQTHD member in the hlq.CDBATREQ had been already
updated with PACKAGE-PGM-xxxxxx literal.

DBG01014E ssid 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LEN

and

DBG01014E ssid 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LONG

 

After reviewed of the hlq.REQUESTS library, it was found that an old DSQTHD member existed in the hlq.REQUESTS library.

To resolve this problem, do one of the the following:
1. Delete the old DSQTHD member in the hlq.REQUESTS library
or
2. Copy the new DSQTHD member to the hlq.REQUESTS library from the hlq.CDBATREQ library