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-3
OSS Pathnames
Each pathname for an OSS regular file has an underlying Guardian filename. The OSS
name servers map such pathnames onto corresponding Guardian filenames. This
mapping, known as name resolution, is necessary because OSS pathnames are
different from Guardian filenames.
Each OSS file therefore has two names:
•
An OSS pathname, such as /usr/henry/workfile
•
A Guardian filename, such as $VOL2.ZYQ00001.Z0000034
The parts of a Guardian filename and an OSS pathname for an OSS file are:
Directory files, terminal device files, AF_UNIX sockets, and FIFOs (named pipes) do
not have underlying Guardian files or Guardian filenames. These OSS special files are
managed entirely by OSS server processes. Such files do not require any configuration
action by the system manager; their operation cannot be controlled through SCF
FILESET commands.
Guardian files also exist in the OSS environment. All accessible Guardian files on the
local node are located in the /G directory of the OSS file system.
From a programmer’s or end user’s perspective, the /G directory is its own fileset in
the OSS file system; each disk volume within the Guardian file system and each
terminal process also are separate filesets. An OSS administrator does not need to
Figure 3-2. Guardian Files and Disk Volumes
Environment Volume Fileset Inode
Guardian $VOL2 ZYQ00001 .Z0000034
OSS -- /usr /henry/workfile
Legend
HP NonStop server node
Disk volumes
Subvolumes
Files
1
2
4
\MYNODE
1
\MYNODE.$OURVOL.MYSUBVOL.MYFILE1
\MYNODE.$OURVOL.YRSUBVOL.YRFILE1
$OTHVOL
SUBVOL1
SUBVOL2
AFILE1
AFILE2
BFILE1
BFILE2
2
3
3
4
4
VST003.VSD
$OURVOL
MYSUBVOL
YRSUBVOL
MYFILE1
MYFILE2
YRFILE1
YRFILE2
2
3
3
4
4
3