Enclave Resource Accounting

The accounting for resources consumed by an enclave depends on whether it is an independent, work-dependent, dependent, or a foreign enclave.

A dependent enclave is a logical continuation of the transaction already active in a client's address space. Therefore, CPU and MSO service for a dependent enclave is included in the SMF 30 record of the owning address space, and in the SMF 72 record for the address space's transaction. MSO service for the enclave is calculated based on the frame count of the owning address space, not on frame usage in the address space(s) where the enclave is executing.

For an independent enclave and for work-dependent enclaves, CPU service is included in the SMF 30 record of the owning address space, and in the SMF 72 record for the enclave's service class or performance group period. MSO service is not calculated for either kind of enclave.

For dependent, work-dependent and independent enclaves, IOC service is included in the SMF 30 and 72 records associated with the address space where the enclave work is executing. SRB service for enclaves is always zero.

For a foreign enclave, CPU time is included in the SMF 30 record of the owning address space on the originating system. It is reported separately from local CPU time. CPU service is also included in the SMF 72 record on each system where the enclave executed.

Because CPU time used by foreign enclaves is included in the owner's SMF 30 record, it is not included in the SMF 30 records on the other systems where it actually executed. In order for those other systems to have some record of the CPU time used by foreign enclaves, an SMF 97 record is written for each SMF global recording interval. This SMF 97 record identifies the CPU time used by foreign enclaves during that interval, broken down by originating system. The installation can review the originating system's SMF 30 records to identify the specific jobs that consumed the CPU time in the foreign enclaves. Note that because data is collected asynchronously for the SMF 30 records, and because SMF intervals can vary from system to system, it may not be possible to exactly match SMF 30 times with SMF 97 times from one global interval to another.

Table 12 compares control characteristics and resource accounting for independent, work-dependent, dependent and foreign enclaves.

Table 12. Enclave characteristics and resource accounting (a.s. = address space)

Independent enclave

Dependent enclave

Foreign enclave

Work-dependent enclave

Dispatchable unit type

SRBs and/or tasks

New transaction?

Yes

Owner

Home space at the time IWM4ECRE is issued

Depends on the TYPE parameter passed to IWM4ECRE:

If TYPE=DEPENDENT, the home a.s. at the time the service was issued.
If TYPE=WORKDEPENDENT, the creating (dependent) enclave's home a.s.
If TYPE=MONENV, the a.s. associated with the monitoring environment - see Note 1

Owner of the original enclave

Owner a.s. of the creating independent enclave

Server

a.s. where enclave work is dispatched

Service class/report class

Assigned based on attributes passed to IWM4ECRE (see Note 2)

Same as owner.

Same service & report class as original enclave.

Same as owning independent enclave's

CPU time

Owner's SMF30Cpt (total) owner's SMF30Enc (independent and work-dependent enclaves only)

Owner's SMF30Cpt (total) owner's SMF30Det (dependent enclave only)

Owner's SMF30MRI (for foreign ind. enclave) owner's SMF30MRD (for foreign dependent enclave)

Owner's SMF30Cpt (total) owner's SMF30Enc (independent and work-dependent only)

CPU service by a.s.

Owner's SMF30Csu (total) owner's SMF30Esu (independent and work-dependent enclaves only)

Owner's SMF30Csu (total)

CPU time/SMF30MRA/256 * CPU coefficient (CPU coefficient can be obtained from SMF 72 record)

Owner's SMF30Csu (total) owner's SMF30Esu (independent and work-dependent only)

CPU service by period

Enclave's R723Ccpu

Owner's R723Ccpu

Enclave's R723Ccpu

Enclave’s R723Ccpu

DASD I/O connect time by a.s. (see Note 3)

Owner's SMF30Eic (independent and work-dependent enclaves only)

Owner's SMF30Aic (dependent enclave + a.s.)

n/a

Owner's SMF30Eic (independent and work-dependent only)

DASD I/O connect time by period (see Note 3)

Enclave's R723Cict

Owner's R723Cict

Enclave's R723Cict

DASD I/O counts by a.s.

Owner's SMF30Eis (independent and work-dependent enclaves only)

n/a

Owner's SMF30Eis (independent and work-dependent only)

DASD I/O counts by period

Enclave's R723Circ

Owner's R723Circ

Enclave's R723Circ

Page delay samples, with storage mgt. (see Note 4)

Enclave's R723Cspv

Owner's R723Cspv

Enclave's R723Cspv

Page delay samples, without storage mgt. (see Note 4)

Enclave's R723Caxm

Owner's R723Caxm

Enclave's R723Caxm

IOC service

Server's SMF 30 and 72 records

SRB service

n/a

MSO service

n/a

Owner's SMF30Mso, based on owner's frame count

n/a

Notes:

The address space associated with the monitoring environment is one of the following:
- The address space related to the monitoring environment via the IWMMRELA service
- If there is no related space, the home space at the time IWM4MINI was issued
The attributes passed to IWM4ECRE are used with the classification rules in the active service policy to assign a service class and/or report class to the enclave.
Connect time is used as an example here. Other measures associated with I/O in the SMF records are:
- DASD I/O disconnect time in fields SMF30EID, SMF30AID, R723CIDT, and SMF72IDT.
- DASD I/O wait time in fields SMF30EIW, SMF30AIW, R723CIWT, and SMF72IWT.
Storage management is in effect for an enclave if either of the following is true:
- The enclave includes one or more tasks.
- The enclave includes at least one SRB which has issued the SYSEVENT ENCASSOC to associate itself with an address space.