In a TPX Generic Resource environment, one of the TPX images is experiencing high CPU usage.
Release : 5.4
Component : CA-TPX for Z/OS
This is symptomatic of a TPX VSAM database (ADMIN!, ADMIN2....etc) not being reorged in a very long time.
One of the most common reason among many, can be that a user record is locked or corrupted, causing the TPX 'monitor' queue backing up, resulting in wait time for processing.
The Ci/CA splits in the VSAM database need to be attended to in order to avoid unpredictable results. A Reorg will eliminate the condition.
Review the recommended procedure's in the Additional information section below, for keeping the TPX VSAM database healthy.