A non-LDS-backed VTS can be configured with TSRACCESS=RO, and the same RACF rules that govern LDS-backed TSRACCESS=RO configurations apply here as well — covering profile definitions, CONTROL-level access, consistent naming definitions, VTSManager command boundaries, and tableBASE privilege enforcement.
Beyond these standard rules, this configuration unlocks the primary operational advantage of using VTS Gate in this context. Using the VV command, a designated batch job can swap the VTS from RO to RW, perform necessary table preparation or updates, and then swap it back to RO. While the VTS-TSR is in RO mode, VTSManager’s alias switch can be performed normally. This combination of VTS Gate access swapping and VTSManager alias switching provides a flexible and controlled mechanism for managing table content while preserving the read-only production state.