Open System Services Management and Operations Guide (G06.29+, H06.07+)

Understanding the OSS File System
Open System Services Management and Operations Guide—527191-005
3-5
Using Pathnames for Remote Files
Using Pathnames for Remote Files
The rules described in the preceding subsection can be extended to the files
accessible through the /E directory. A file on a remote node that is connected to your
node through the Expand network appears in /E when all of the following are true:
•
The remote Expand node has a TOSVERSION of D40 or later.
•
The remote node has an OSS name server running with a device subtype of 5.
•
The file is either:
°
A Guardian disk file
°
An OSS file in a started fileset with a catalog that uses a format newer than a
D3x version
Remote Guardian files appear in the /G directory of the remote node. For example, if
the remote node is named NODE1, the Guardian files on its $SYSTEM disk in
subvolume ZOSSUTL would appear to your system as files in
/E/node1/G/system/zossutl/.
Remote OSS files can be found from the root (/) directory of the remote node. For
example, the files in /usr/share/man on the remote node named NODE1 would
appear to your system as /E/node1/usr/share/man.
Files visible through /E on the remote node are not visible to your system. That is, if
you are on NODE0, you cannot access files on NODE0 by looking in
/E/node1/E/node0.
Your local node also has an entry in its own /E directory. That entry consists of a
symbolic link to its own root directory; for example, /E/node0 is a symbolic link to the
/ directory if your local node is NODE0.
Some software permits you to specify files on your local node by prefixing the OSS
pathname with /E and the local node name (for example, on NODE0 you can enter
/E/node0/usr/share/man/cat5/filename.5 or
/E/node0/G/system/zossutl/T8620MAN). This form of pathname is intended for
programming use; it is not a good practice when using the OSS shell and should be
avoided.
Using the Local Root Directory as a Pathname
Because /G and /E both appear in your local root directory, you should be very careful
when using OSS shell commands on or from the root directory. OSS shell commands
that perform recursive actions make no distinction between Guardian and OSS files or
between local and remote files.
For example, a simple search with the find command that is intended to look for an
OSS file also searches all Guardian files on your local node and all files on all
connected Expand nodes if you enter just:
find / -name log*