Protection exceptions referencing the UDSA and EUDSA
In a system running with transaction isolation enabled, protection exceptions can occur in programs with EXECKEY(USER).
Such an exception is caused by one transaction using a user key
program to read or write to the user-key task-lifetime storage of
another transaction. This situation might highlight a program error
or an interdependency between two transactions. The IBM CICS Interdependency
Analyzer for z/OS® tool can help to identify potential transaction
interdependencies. Examples of transaction interdependencies are:
- A transaction might use EXEC CICS GETMAIN or GETMAIN64 to obtain 24-bit or 31-bit storage, and pass the address of the storage to other transactions. Access to this storage by one of these other transactions causes a protection exception if transaction isolation is enabled, unless both affected transactions are defined with ISOLATE(NO). Storage to be shared in this manner should be acquired by a GETMAIN with the SHARED option. This is preferable to defining the transactions with ISOLATE(NO).
- A transaction might attempt to post an ECB that exists in another transaction’s task-lifetime storage. ECBs should be acquired by a GETMAIN from shared storage. Alternatively, the affected transactions should be defined with ISOLATE(NO).
Transaction isolation does not apply to 64-bit storage, so protection exceptions caused in this way do not reference the GUDSA.