Special Considerations

For access level of BROWSE, only the records the user is allowed are returned. (Any records the user is not allowed are automatically bypassed). No violations or logging occurs for records not allowed by the RLP selection process.
Even if XFCT=YES, and RLP=YES, the FCT in question MUST be owned and permitted to the user with the SELECT clause, before RLP will have any affect. For example:
```
TSS PERMIT(userid) FCT(FILEA)
                   ACCESS(READ)
                   SELECT(ISFILEA)
```
For access level of DELETE to function under the RLP selection criteria, you must have the FCT defined (to CICS) with a journalling option or recovery enabled. For example, under CICS CEDA transaction:
```
CEDA def File(FILEB)
            .
            .
        RECOVERY PARAMETERS
        Recovery   : ALL
        Fwdrecovlog: 01
```
Regardless of the FCT having journalling or not, normal access checks will still occur for DELETE access.

If you are using the MASK feature of RLP, be aware that although masking is limited to READ and BROWSE file operations, the application should not WRITE(CREATE) a record from the data buffer that might contain the masking values.
Make certain that the data types specified in the MASKDATA or RECDATA definitions match the data types of those contained on the actual file record.
When RLP=YES, NOTAUTH conditions might have EIBRESP2=0000 instead of the expected EIBRESP2=101.