ZOS CPU Utilization

Use the ZOS CPU Utilization attributes to determine how much of your processor is used by DB2.

Note: Parameter ZOSMETRICS must be set to YES for enabling DB2 to retrieve data from the RMF interface. If ZOSMETRICS is not set to YES, you might see negative Operating System CPU data. ZPARM ZOSMETRICS in DSN6SPRM.

CPU Utilization DB2 The percentage of the processor used by the DB2 subsystem; if parameter ZOSMETRICS is not set to YES for enabling DB2 to retrieve data from the RMF interface, you might see negative Operating System CPU data.

CPU Utilization DB2 DBM1 The percentage of the processor used by the DB2 DBM1 address space; if parameter ZOSMETRICS is not set to YES for enabling DB2 to retrieve data from the RMF interface, you might see negative Operating System CPU data.

CPU Utilization DB2 MSTR The percentage of the processor used by the DB2 MSTR address space; if parameter ZOSMETRICS is not set to YES for enabling DB2 to retrieve data from the RMF interface, you might see negative Operating System CPU data.

CPU Utilization LPAR The average processor usage per LPAR; if parameter ZOSMETRICS is not set to YES for enabling DB2 to retrieve data from the RMF interface, you might see negative Operating System CPU data.

DB2ID The name of a DB2 subsystem.

DB2 Version The version of DB2.

Interval Start The date and time, as set on the monitored system, indicating the instance when the agent collects information.

Number of CPU on LPAR The number of processors on the LPAR; if parameter ZOSMETRICS is not set to YES for enabling DB2 to retrieve data from the RMF interface, you might see negative Operating System CPU data.

Originating System ID Identifies the originating Tivoli Enterprise Monitoring Server. Valid format is alphanumeric, with a maximum of 32 characters; for example, DB2.USCACO01.D412.