Table of Contents
Advertisement
When you create directories and files, their access capabilities are "public" (available to
any user on the SRM). You may subsequently protect a directory or file against certain
types of access by other SRM workstations, provided all of the following are true:
• You possess MANAGER access capability on the file or directory (MANAGER
access to the file is public or you know the password protecting the capability).
• You possess READ access capability on the directory immediately superior to the
file or directory you wish to protect.
• You protect the file or directory either while "in" its superior directory or by
specifying the valid directory path to its superior directory.
For example, using the directory structure established for other examples in this section
(see illustration) and assuming no passwords have been assigned to the files, you could:
(root)
BDRT 1
1. Assign the password passme to protect the MANAGER and WRITE access capa-
bilities on the directory CHARLIE with the sequence:
MSI "/PROJECTS/Project_one"
PROTECT "CHARLIE". ("passme":MANAGER.WRITE)
which executes the PROTECT statement after moving to the directory Proj ect_one
(immediately superior to CHARLIE). As a result of this PROTECT statement, the
READ access capability on CHARLIE is still public, but any operations that require
MANAGER or WRITE capabilities must include the password.
U sing Directories and Files
5-29
Advertisement
Table of Contents
