RLS Access Rules

The following table illustrates RLS access rules, showing the possible scenarios for opening data sets with and without RLS. In Table 1, OPEN1 represents an initial successful open and OPEN2 represents the options for a subsequent open of the same data set, with or without RLS.

Table 1. RLS open rules, for recoverable or non-recoverable data sets
OPEN1 Did—> OPEN2 Wants:	RLS	Non-RLS Input with SHR(2 x)	Non-RLS Output, or Input without SHR(2 x)
RLS	See note below	OK	NO
Non-RLS Input with SHR(2 x)	OK	OK	SHAREOPTIONS rules
Non-RLS Output, or Input without SHR(2 x)	NO	SHAREOPTIONS rules	SHAREOPTIONS rules

Note: For non-recoverable data sets, either transactional (CICS or DFSMStvs) RLS or non-transactional (non-CICS and non-DFSMStvs) RLS is acceptable. For recoverable data sets:

Transactional RLS can share with: any transactional RLS accesses, and input-only non-transactional RLS accesses (non-transactional RLS cannot update recoverable data sets)
Non-transactional RLS can share with any non-transactional RLS as long as they do not update the recoverable data sets.

For example, if OPEN1 already successfully opened the data set to be accessed with RLS, the subsequent OPEN2 attempting to open it for non-RLS output would fail, regardless of whether or not the data set is recoverable. With the same OPEN1, if the data set is recoverable, OPEN2 can open it for non-transactional (that is, non-commit protocol) RLS input-only access.