I don¡¯t think we ever implied that modes 1 and 2 on the ¡°S¡± and ¡°Y¡± disk were anything other than for convenience. However, for Mode 0 the CMS user guide for VM/370 says
?
???? ¡°a filemode number of 0 assigned to a file makes it private. No other user can access it unless they have read/write access to the disk¡±
?
So the manual implies it¡¯s a security lock, and those who are not familiar with VM/CMS such as those asking here, might take that at its face value, when we know its not true.
The ability to make only certain filemode number files visible, like filemode 2 files on the S and Y disks,
was not a security mechanism. It was a way to save storage by making only necessary files visible.
Maintenance files were not needed during ordinary use. It was convenient to place them on the system
disk.?
?
VM data security was based on the architecture?that made one user's disks completely unavailable to
another user who does not have the disk read or write passwords.
?
?
On Wed, Feb 12, 2020 at 1:33 AM adriansutherland67 <adrian@...> wrote:
On Tue, Feb 11, 2020 at 11:16 PM, Peter Coghlan wrote:
Then I used DDR to copy the original disk which I only had read access to onto the temporary disk. Because I had read/write access to the temporary disk, the standard ACCESS command let me see all the files on it.
Those were more innocent times, well in terms of IT security at least ...