Subset CPU Time Data Elements

The subset data elements listed below represent CPU time measurements that are subsets of the CPU times listed above as standalone CPU time data elements.
rm
In general, these subset measurements are useful for analysis, but not for chargeback because their values are already accounted for in the standalone measurements. An exception might be made if you wanted to charge differently for a particular subset of a standalone CPU time measurement.
PGMPRETM - Step Preemptable/Client CPU TimeSUBSET of PGMTCBTM - Step TCB Time
PGMPRETM contains the contents of SMF type 30 field SMF30ASR.
Preemptable SRBs are comparable to Task Control Blocks (TCBs) in scheduling and accounting, but maintain the low overhead advantages of SRBs. Using the IEAMSCHD macro, the preemptable SRB type is determined by the PRIORITY parameter. When either PRIORITY=PREEMPT or PRIORITY=CLIENT is specified, the SRB is preemptable.
The primary difference between preemptable and client SRBs is the priority that they inherit.
When PRIORITY=PREEMPT is specified, the preemptable SRB inherits the major priority of the target home address space.
When PRIORITY=CLIENT SRB is specified, the preemptable SRB inherits the major priority of the address space named by the CLIENTSTOKEN parameter specified in the IEAMSCHD macro. This named address space accumulates the CPU time used by the client SRB during execution.
PGMENCTM - Step Enclave CPU Time SUBSET of PGMTCBTM - Step TCB Time
PGMENCTM contains the contents of SMF type 30 field SMF30ENC.
It represents the portion of TCB CPU time used by independent enclaves, executing on the same system (LPAR) as the address space, while performing work on behalf of the address space.
Independent enclaves are managed by Workload Manager (WLM) goals specific to the enclave, and not those of the "using" address space.
PGMDENTM - Step Dependent Enclave CPU Time SUBSET of PGMTCBTM - Step TCB Time
PGMDENTM contains the contents of SMF type 30 field SMF30DET.
It represents the portion of TCB CPU time used by dependent enclaves, executing on the same system (LPAR) as the address space, while performing work on behalf of the address space. Dependent enclaves inherit the Workload Manager (WLM) goals of the "using" address space.
PGMZACTM - zAAP Eligible CPU Time on CP
SUBSET of PGMTCBTM - Step TCB Time
PGMZECTM - zAAP IND Enclave CPU Time on CP
SUBSET of PGMZACTM - zAAP Eligible CPU Time on CP
PGMZDCTM - zAAP DEP Enclave CPU Time on CP
SUBSET of PGMZACTM - zAAP Eligible CPU Time on CP
PGMZACTM contains the contents of SMF type 30 field SMF30_TIME_IFA_ON_CP.
PGMZECTM contains the contents of SMF type 30 field SMF30_ENCLAVE_TIME_IFA_ON_CP.
PGMZDCTM contains the contents of SMF type 30 field SMF30_DEP_ENCLAVE_TIME_IFA_ON_CP.
PGMZACTM represents the portion of TCB CPU time that was eligible to execute on a zAAP processor, but actually executed on a standard processor.
PGMZECTM is the portion of zAAP Eligible CPU Time on CP (PGMZACTM) attributable to independent enclaves.
PGMZDCTM is the portion of zAAP Eligible CPU Time on CP (PGMZACTM) attributable to dependent enclaves.
In a zIIP only configuration (no zAAP engines present) and SYS1.PARMLIB(IEASYSxx) option ZAAPZIIP=YES, all zAAP related CPU measurements will be zero (0). Any zAAP CPU time will be included in all zIIP related CPU measurements.
Analysis of zAAP eligible CPU time can help determine if it would be cost effective to purchase zAAP processors to offload JAVA workloads from standard processors to the lower cost zAAP processors.
PGMSUCTM - zIIP Eligible CPU Time on CP
SUBSET of PGMTCBTM - Step TCB Time
PGMSECTM - zIIP IND Enclave CPU Time on CP
SUBSET of PGMSUCTM -
zIIP Eligible CPU Time on CP
PGMSDCTM - zIIP DEP Enclave CPU Time on CP
SUBSET of PGMSUCTM - zIIP Eligible CPU Time on CP
PGMSUCTM contains the contents of SMF type 30 field SMF30_TIME_SUP_ON_CP.
PGMSECTM contains the contents of SMF type 30 field SMF30_ENCLAVE_TIME_SUP_ON_CP.
PGMSDCTM contains the contents of SMF type 30 field SMF30_DEP_ENCLAVE_TIME_SUP_ON_CP.
PGMSUCTM represents the portion of TCB CPU time that was eligible to execute on a zIIP processor, but actually executed on a standard processor.
PGMSECTM is the portion of zIIP Eligible CPU Time on CP (PGMSUCTM) attributable to independent enclaves.
PGMSDCTM is the portion of zIIP Eligible CPU Time on CP (PGMSUCTM) attributable to dependent enclaves.
In a zIIP only configuration (no zAAP engines present) and SYS1.PARMLIB(IEASYSxx) option ZAAPZIIP=YES, zIIP related CPU measurements include both JAVA and enclave SRB activity. There is no way to separate what part was 'zAAP' versus the part that was 'zIIP'.
Analysis of zIIP eligible CPU time can help determine if it would be cost effective to purchase zIIP processors to offload database serving workloads such as DB2, from standard processors to the lower cost zIIP processors.
PGMEQPTM - Step Enqueue Promotion CPU Time SUBSET of PGMTCBTM/PGMSRBTM - Step TCB Time and SRB Time
PGMEQPTM contains the contents of SMF type 30 field SMF30CEPI.
It represents the portion of TCB CPU time and SRB CPU time used by the step while "enqueue promoted." Enqueue promotion is used to speed the completion of address spaces that hold a reserve on resources needed by other workloads.
While in the "enqueue promotion" status, all TCB and SRB time recorded for the address space is also added to field SMF30CEPI.
PGMCRPTM - Promoted Due to Chronic Contention Time SUBSET of PGMTCBTM/PGMSRBTM - Step TCB Time and SRB Time
PGMCRPTM contains the contents of SMF type 30 field SMF30CRP.
It represents the portion of TCB CPU time and SRB CPU time used by the step while promoted due to resource contention. A higher temporary dispatching priority is given to speed the completion of address spaces causing resource contention.
While in the "chronic resource contention" status, all TCB and SRB time recorded for the address space is also added to field SMF30CRP.
PGMUSSTM - Step USS CPU Time
PGMUSSTM contains the contents of SMF type 30 field SMF30OST.
It represents the portion of TCB CPU time and SRB CPU time used by the process under measurement for USS.
PGMTSITM - Step Initiator TCB Time at Step Init
PGMTSITM contains the contents of SMF type 30 field SMF30ICU_Step_Init.
It is the Task Control Block (TCB) CPU time that is spent executing initiator code during job step initialization. It is only recorded in the SMF type 30 subtype 4 step end record. For sites using interval records, the value of SMF30ICU_Step_Init is captured from each subtype 4 step end record and recorded in the observation representing the last interval record for that step.
It represents the portion of TCB CPU time that is spent executing initiator code in preparation for a step.
PGMTSTTM - Step Initiator TCB Time at Step Term
PGMTSTTM contains the contents of SMF type 30 field SMF30ICU_Step_Term
It is the Task Control Block (TCB) CPU time that is spent executing initiator code during job step termination. It is only recorded in the SMF type 30 subtype 4 step end record. For sites using interval records, the value of SMF30ICU_Step_Term is captured from each subtype 4 step end record and recorded in the observation representing the last interval record for that step.
It represents the portion of TCB CPU time that is spent executing initiator code at step termination of the previous step in preparation for the next step.
PGMSSITM - Step Initiator SRB Time at Step Init
PGMTSITM contains the contents of SMF type 30 field SMF30ISB_Step_Init.
It is the System Resource Block (SRB) CPU time that is spent executing initiator code during job step initialization. It is only recorded in the SMF type 30 subtype 4 step end record. For sites using interval records, the value of SMF30ISB_Step_Init is captured from each subtype 4 step end record and recorded in the observation representing the last interval record for that step.
It represents the portion of SRB CPU time that is spent executing initiator code in preparation for a step.
PGMSSTTM - Step Initiator SRB Time at Step Term
PGMTSTTM contains the contents of SMF type 30 field SMF30ISB_Step_Term
It is the System Resource Block (SRB) CPU time that is spent executing initiator code during job step termination. It is only recorded in the SMF type 30 subtype 4 step end record. For sites using interval records, the value of SMF30ISB_Step_Term is captured from each subtype 4 step end record and recorded in the observation representing the last interval record for that step.
It represents the portion of SRB CPU time that is spent executing initiator code at step termination of the previous step in preparation for the next step.