6. DATA SOURCES › 6.12 Multisystem Enclaves Overview › 6.12.3 Accounting for Multisystem Enclaves

Previous Topic: 6.12.2 Enabling Multisystem Enclaves

Next Topic: 6.13 CA MICS and CA SMF Director Interface

6.12.3 Accounting for Multisystem Enclaves


 Resource accounting for enclaves depends on whether it is an
 independent, dependent, or foreign enclave.

 CPU time consumed by an independent enclave is recorded
 in the SMF type 30 record of the owning address space in
 field SMF30ESU.  The CA MICS representation is:

 PGMENCTM - Step Enclave CPU Time

 A dependent enclave is a logical continuation of an active
 transaction in an address space.  Its performance goal is
 derived from the owning address space.  CPU service
 consumed by the enclave is accumulated in the SMF type 30
 record of the owning address space in field SMF30DET.  The
 CA MICS representation is:

 PGMDENTM - Step Dependent Enclave CPU Time

 A foreign or multisystem enclave is recorded as either an
 dependent or independent foreign enclave in the SMF type 30
 record of the owning address space on the originating
 system.  It is reported separately from local CPU time.  The
 CA MICS representation is:

 RENCPDTM - Multisystem Dep Enclave CPU Time
 RENCPITM - Multisystem Ind Enclave CPU Time