When the Data Collector was tried to run after the latest PTFs were applied to CA Insight Database Performance Monitor for DB for z/OS R19.0, the Data Collector was failed with RC=52. The following messages appeared in the joblog.
DBG99001E DSNS 10:04:46 ERROR IN COMMAND STREAM, PROCESSING ENDED
..
DBG04004I DSNS 10:04:45 REQUEST DSQTHD FROM STARTUP
..
DBG01014E DSNS 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LEN
DBG02018E DSNS 10:04:45 INVALID FIELD SPECIFICATION
4112 PACKAGE-ID-LONG (PF=A128)
DBG01014E DSNS 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LONG
Release : 19.0
Component : CA Insight Database Performance Monitor for DB for z/OS
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 Prefix.CDBATREQ library.
*---------------------------------------------------------------------
* 08/27/18 KIETH01 IDB2#2302
* - 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 Prefix.CDBATREQ.
However, the following error messages appeared in the Data Collector joblog though the DSQTHD member in the Prefix.CDBATREQ had been already updated with PACKAGE-PGM-xxxxxx literal.
DBG01014E DSNS 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LEN
and
DBG01014E DSNS 10:04:45 MISSPELLED RESERVED WORD OR LITERAL PACKAGE-ID-LONG
After reviewed the Prefix.REQUESTS library, it was found that their old DSQTHD member existed in their Prefix.REQUESTS library.
To resolve this problem, do one of the the following.
1. Delete the old DSQTHD member in the Prefix.REQUESTS library.
or,
2. Copy the new DSQTHD member to the Prefix.REQUESTS library from the Prefix.CDBATREQ library.