Table of Contents
Advertisement
The current access capabilities for a file are shown in a catalog listing:
PROJECTS/Project_one:REMOTE 21, 0
LABEL:
Disc1
FORMAT:
SDF
AVAILABLE SPACE:
FILE NAME
ASCII_1
BDAT_1
MEMOS
4354096
SYS
FILE
LEV TYPE TYPE
ASCII
1 98X6 BOAT
1
DIR
NUMBER
RECORDS
========
0
0
0
RECORD
MODIFIED
PUB
LENGTH DATE
TIME ACC
========
===============
256
2-Dec-84 13:20
256
2-Dec-84 13:20 R
24
2-Dec-84 13:20 RW
OPEN
STAT
In the above example, the file ASCII_1 has no public access capabilities; that is, all access
must include the appropriate password. The file BDAT_1 has the READ capability public,
which means that anyone on the SRM system can read the file. The directory MEMOS has
READ and WRITE capabilities still open to the public; anyone can create and purge
files in the directory, as well as "search" through the directory (with statements like MASS
STORAGE IS "MEMOS/SUB_DIR").
Capabilities are protected with the PROTECT statement, which associates a password
with one or more access capabilities.
Each file or directory can have several pass-
word/capability pairs assigned to it.
Once assigned. the password protecting an access capability must be included with the
file or directory specifier to execute statements requiring that access. If you don
It
specify
the correct password when it is required, the system will report an error and deny access
to the file or directory.
5-28
Using Directories and Files
Advertisement
Table of Contents
