Table of Contents
Advertisement
Purging SRM Files and Directories
The PURGE statement can be used for rf'moving SRM files and directorif's. PUReE
works only with closed files and directories. Directories must also be empty (not contain
any files or directories).
When specifying the SRM file to be purged. you must include a write password for the
file and read/write passwords for its parent directory. For example. to purge the file
BDAT_l
from the directory
CHARLIE
(see previous examples). you could type:
PURGE 1.<passme>/BDAT_l<write>"
In this example,
CHARLIE
is the current working directory. as denoted in the directory
path by " . ". (Refer to the syntax for directory path in the BASIC Language Reference
manual).
To purge a file, you must have the vVRITE access capability on that file and READ and
WRITE access capabilities on the file's superior directory. Because
passme
protects the
WRITE capability on
CHARLIE
and
write
protects the WRITE capability on
BDAT_l,
both
passwords must be included in the file specifier in the PURGE statement.
Although you do not normally need to specify the working directory in a directory path,
you must include the password for the PURGE operation. The READ capability on
CHARLIE
is not password-protected.
To purge
CHARLIE,
you would first need to purge the remaining files and directory in
CHARLIE.
Because the .MSI statement "opens" a directory (making it the current working
directory), you must also "close"
CHARLIE.
For example, if no files or directories remained in
CHARLIE,
you could purge
CHARLIE
hy
executing these two commands:
MSI ":REMOTE"
PURGE "PROJECTS/Project_one/CHARLIE<passme>
The first statement closes
CHARLIE
and establishes the root directory as the current
working directory. Note that. because
passme
protects the WRITE access capability
on
CHARLIE.
you must include that password in the PURGE statement.
5-38
Using Directories and Files
Advertisement
Table of Contents
