When an LDS-backed VTS is configured with TSRACCESS=RF, it is designed to support VTSManager alias switching operations. To enable this, a RACF profile must be defined for the VTS before it is started. Any user who needs to start the VTS, or who requires full access including both read and write operations, must be explicitly granted CONTROL-level access in the associated RACF profile.
Regarding RACF profile definitions for true names and alias names: both the true VTS name and any alias names associated with a given VTS-TSR resource must have consistent RACF definitions, meaning that end users generally need READ access to both.
From an operational standpoint, VTSManager SWITCH and RESET commands remain subject to the standard rules governing VTS Manager. When issuing tableBASE commands against such a VTS, the issuing user must hold READ or WRITE RACF privileges appropriate to the type of command. Failure to satisfy these requirements results in errors 1072-3 or 1072-4, respectively.
Despite allowing RACF WRITE privilege assignments, a VTS running under TSRACCESS=RF is treated as effectively read-only. The only permitted update-type operation is the RF (Refresh) command, which reloads tables into the VTS. Any other update commands — such as IK or RK — will fail with error 13-6 regardless of the user’s RACF WRITE privilege level. As noted above, the VV command from VTS Gate is also not compatible with this mode.