Locking for SYSEVENTs

All issuers of enabled, branch-entry SYSEVENTs must hold the local lock when the SYSEVENT is issued. The following SYSEVENTs are serialized by the CPU lock:

SRM obtains the SRM lock on all SYSEVENT entries except the following:

The issuer of any of these SYSEVENTs, with the exception of HOLD, NOHOLD, and DIRECTPO, must be disabled when issuing the SYSEVENT because SRM uses processor-related save areas while processing the SYSEVENTs. The issuer of HOLD, NOHOLD, and DIRECTPO must also be in key 0. Issuers of SYSEVENTs not in the preceding list must not hold the SRM lock or any global lock when they issue the SYSEVENT.

Table 1 lists all SYSEVENTs in alphabetical order with their associated codes.