Registering an Enclave

Enclave transactions do not only exist within a subsystem, but also across subsystems. Enclaves can be deleted by any subsystem at any time. So, it might happen that a subsystem deletes an enclave that is still used by another subsystem. To avoid premature deletion, you can register an enclave. The registration indicates to the system that an enclave must not be deleted until the registering subsystem deregisters it.

The new service, IWMEREG, allows an enclave to be registered in order to prevent it from premature deletion until the enclave is deregistered. The new service, IWMEDREG, allows the registration for an enclave to be undone and deleted

The registration is owned by the job step task of the home address space at the time IWMEREG is invoked. If the job step task or the address space terminates, the system implicitly deregisters the enclave.

Only subsystems which utilize enclaves created by other subsystems need to register interest in an enclave while using it. If a subsystem only uses enclaves that it created itself, there is no need to register interest in the enclave.