High CPU consumption in the Data Collector after a Release upgrade

Products

• SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

For some reason, for example after an upgrade to a new Release of the Data Collector or after maintenance has been applied, a high increase of the CPU consumption is suddenly reported in the Data Collector started task.

You have to research the cause of the CPU consumption increase and try to find a circumvention to avoid the high CPU consumption until a permanent solution is published. 

Environment

Release : 20.0

Component : CA SYSVIEW Performance Management Option for DB2 for z/OS

Resolution

You can run the following steps for debugging and find any task that can be the cause of the high increase of CPU consumption.   
  
- In CA SYSVIEW for DB2 main menu select the options.
1  System Statistics
6 More...
1 MVS Address Space Displays
Update JOB . . IDB2DC  ASID . . xxxx  <-- Check the current ASID
IDB2DC is the CA SYSVIEW for DB2 started task.
 
4 Tasks <-- This option will display how Tasks are utilizing the CPU. 
Scroll down to all the panels and check column 'CPU Time', it should be a task with a high CPU consumption. 
Sometimes the task can be disabled with any of the Data Collector parameters.
  
- Go to the CA SYSVIEW for DB2 main menu and in 'Tools' select 1 COMMANDS.
Select 3 CA SYSVIEW for DB2 Commands.
In 'CA SYSVIEW for DB2 Console Command ===>' issue the IFI command.
Review this screen shot to check if any of the IFCID's is called a lot of times.

Contact Broadcom Support with all these results to be analyzed and research the solution.