z/OS MVS Programming: Workload Management Services
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Deleting an Enclave

z/OS MVS Programming: Workload Management Services
SC34-2663-00

Deleting an Enclave

A caller can delete an enclave using the IWM4EDEL macro. If the enclave is registered, it is only logically deleted. That is, it remains available until it is no longer registered by any subsystem.

When the enclave is deleted, the following occurs for each remaining dispatchable unit:

  • SRBs:

    Each SRB belonging to the enclave is changed to a preemptable SRB and run at the dispatching priority of the current home address space (the address space into which the SRB was scheduled). The subsystem can purge SRBs using the PURGEDQ macro when the enclave still exists in the system. In most cases, this prevents the SRB from existing beyond the life of the enclave. For information on how to use PURGEDQ, see z/OS MVS Programming: Authorized Assembler Services Guide.

  • Tasks: If an enclave ends with tasks still joined to the enclave, the tasks revert back to ordinary non-enclave tasks.

A foreign enclave is deleted using the IWMUIMPT macro. Work-dependent enclaves are implicitly deleted when the owning independent enclaves get deleted.

For information about the IWM4EDEL macro, see IWM4EDEL – Deleting an Enclave.

Example

To delete an enclave, specify the following:

IWM4EDEL ETOKEN=etoken,
         RETCODE=retcode,
         RSNCODE=rsncode

where the calling program has defined the following:

etoken    DS    FL4          Enclave token
retcode   DS    CL4          Return code
rsncode   DS    CL4          Reason code

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014