Previous Topic: Access Rules for Shared File System FilesNext Topic: Writing Access Rules for SFS Directories


SFS File Identifiers

Each SFS file server manages a collection of SFS files called a filepool. There is only one filepool for each SFS server machine. Every user must know the name of the filepool where any files reside that they might need access to. The filepool name is an integral part of the file identifier (we will go into more detail about this later).

Every SFS file in a filepool resides in a root directory of the same name as the owning user ID so it is associated with its owner. Like MS‑DOS, there can also be hierarchical subdirectories under each root directory that also contain SFS files. SFS supports up to eight levels of subdirectories. Each subdirectory name can be up to 16 characters long.

Let's take a look at how all these components fit together to form the file identifier for an SFS file. As an example, consider a CMS file called MY DATA that user ID TLCAMS owns in the filepool APPLDATA. This file resides in TLCAMS' root directory. The complete file identifier for this file would be:

APPLDATA:TLCAMS.MY.DATA

It is very important that a colon (:) always follow the filepool name and the owner ID always follow the colon.

Now, let's consider a more complex example where the file resides three levels deep under subdirectories. The first level is a directory called UNITEDSTATES. The second level is called ILLINOIS. The third level is called CHICAGO. The full file identifier is:

APPLDATA:TLCAMS.UNITEDSTATES.ILLINOIS.CHICAGO.MY.DATA

It is important to note that the last two elements of the file identifier are always the filename and filetype of the CMS file.

A few CMS commands let the user refer to an SFS file using the full file identifier, however, this is usually awkward. Most users instead prefer to access the directory where the file resides at a CMS filemode exactly as they would for a minidisk.

Let's assume that you want to access the directory in our most recent example as the E disk. You would enter the following:

ACCESS APPLDATA:TLCAMS.UNITEDSTATES.ILLINOIS.CHICAGO E

After completing this step, all the files in that subdirectory are accessible as if they resided on a minidisk at mode E. In this example, you would refer to MY DATA E.

Because you will normally want to access files that reside entirely in a single filepool, there is a way to declare a filepool so that you do not have to enter the filepool name again. An example of this syntax follows:

SET FILEPOOL APPLDATA:

After you enter the SET FILEPOOL command, use the following command syntax to access the directory:

ACCESS TLCAMS.UNITEDSTATES.ILLINOIS.CHICAGO E

You can also refer to your own root directory with a period (.) instead of entering its name. For example, to access this directory, TLCAMS enters:

ACCESS .UNITEDSTATES.ILLINOIS.CHICAGO E