6. DATA SOURCES › 6.4 CPU Time Measurements › 6.4.2 Analyzer Files with CPU Time Measurements › 6.4.2.3 CPU Time for Remote Enclaves

6.4.2.3 CPU Time for Remote Enclaves

The CA MICS Batch and Operations Analyzer creates remote
enclave activity file observations from the Multisystem
Enclave Remote System Data Section(s) of the SMF type 30
Common Address Space Work step and interval records (subtypes
2, 3, and 4).

The following CA MICS file contains remote enclave activity:

  File    File Label
  ------  ------------------------------------
  BATREN  Multisystem Enclave Activity File

At the DETAIL time-span, BATREN file may contain several
observations representing multisystem enclave activity for a
single step or interval.

The BATREN file is the only CA MICS file where multisystem
remote enclave CPU time is recorded at the address space
level.  It is important to include the BATREN file in any
address space level CPU time usage analysis or accounting and
chargeback algorithm.

Multisystem enclave CPU time is not included in the step and
job level files because it may not be appropriate to
aggregate the CPU time recorded in each data section.

By definition, the CPU time for a multisystem remote enclave
was consumed on a system other than where the using address
space executed.  These other systems must be part of a
SYSPLEX, but do not have to be on the same CEC.

Example: SYSPLEXA

         z900 - SYSA, SYSB, and SYSC
         z990 - SYS1, SYS2, SYS3, and SYS4

If all seven systems are part of the same sysplex, a job
running on SYSA may register, in its SMF type 30 address
space step or interval record, remote system enclave activity
from any or all of the other six systems.  The SMF type 30
record will contain a separate data section for each system
where remote enclaves performed work on behalf of the job.

Because a CPU second on a z900 does not represent the same
amount of work as a CPU second on a z990, it is not
appropriate to add the CPU times across the separate remote
system enclave data sections.

CA MICS creates a separate observation in the BATREN file for
each remote system enclave data section found in an SMF type
30 step or interval record.  The data elements required to
exactly associate the BATREN observations with the associated
step or interval file record are included in the BATREN file.

The following CPU time data elements represent the CPU time
used by remote enclaves during a step or interval.

o RENCPDTM - Multisystem Dep Enclave CPU Time

  RENCPDTM contains the contents of SMF type 30 field
  SMF30MRD.

  It is the dependent enclave CPU time used on the remote
  system on behalf of the using program.
o RENCPITM - Multisystem Ind Enclave CPU Time

  RENCPITM contains the contents of SMF type 30 field
  SMF30MRI.

  It is the independent enclave CPU time used on the remote
  system on behalf of the using program.

The BATREN file SYSID data element represents the SYSID where
the multisystem enclave executed, while data element Using
Address Space SYSID (RENLSYID) represents the SYSID where the
using address space executed.