6. DATA SOURCES › 6.12 Multisystem Enclaves Overview › 6.12.1 Independent vs Dependent Enclaves
6.12.1 Independent vs Dependent Enclaves
A multisystem enclave can begin as either an independent or
dependent enclave on a single system.
INDEPENDENT ENCLAVES
An independent enclave represents a new transaction, which
is classified into a new service class or performance group
when it is created. The home address space is the owner of
the independent enclave.
Independent enclaves can be used in either goal mode or
compatibility mode.
Goal Mode
---------
In goal mode, a service class and a goal is defined for work
being processed by the subsystem using independent enclaves.
Resource controls are dynamically managed by workload
management based on the goal.
Compatibility Mode
------------------
In compatibility mode, performance group characteristics are
defined in the IEAIPSxx parmlib member. The independent
enclave is then managed according to the performance group
definitions.
For a multisystem enclave, each system's enclave performance
group assignment, and dispatching priority is based on the
local IEAICSxx and IEAIPSxx parmlib members.
DEPENDENT ENCLAVES
A dependent enclave is a logical continuation of an active
transaction in an address space. It's performance goal is
derived from the owning address space.
Dependent enclaves can be used in either goal mode or
compatibility mode.
Goal Mode
---------
Because dependent enclaves are managed to the performance
goal of the owning address space, it is not necessary to
classify dependent enclaves, or to define separate service
classes or performance groups.
Compatibility Mode
------------------
Because dependent enclaves are managed to the dispatching
priority of the owning address space, it is not necessary to
classify dependent enclaves, or to define separate groups
for them.
For a dependent multisystem enclave, each system's enclave
performance group assignment, and dispatching priority is
based on the local IEAICSxx and IEAIPSxx parmlib members.
