Open System Services Management and Operations Guide (G06.27+, H06.04+)
Managing OSS Files
Open System Services Management and Operations Guide—527191-003
6-2
Interpreting Guardian Filenames for OSS Files
The OSS shell gname and pname utilities allow you to provide a Guardian filename 
and obtain the OSS pathname for a specific file and vice versa. See the following 
subsections for more information:
•
Using the OSS gname Command on page 6-2
•
Using the OSS pname Command on page 6-3
You can also use the Guardian VPROC utility or the OSS shell vproc command to 
determine the product-version information for an OSS file supplied by HP. The 
procedure to use either VPROC or vproc is described under Gathering Version 
Information About OSS Files on page 11-1.
Interpreting Guardian Filenames for OSS Files
OSS files have a distinctive form of Guardian filename in the Guardian environment. In 
addition to the usual node name and volume name information, the Guardian filename 
for an OSS file has the following form:
•
Subvolume names begin with ZYQ. These subvolume names correspond to OSS 
filesets.
The digits that follow ZYQ are the device identifier for the fileset within the 
ZOSSFSET database file used by the node. See The ZOSSFSET File on page 4-8 
for more information about OSS device identifiers.
•
File identifiers begin with Z0. These file identifiers correspond to OSS file system 
inodes.
The rightmost digits in the file identifier correspond to the OSS inode number for 
the file. (You can also have files other than OSS files whose file identifiers begin 
with Z0.) See Inconsistencies Checked by FSCK on page 5-29 for more 
information on the use of inode numbers.
Using the OSS gname Command
To display the Guardian equivalent of an OSS pathname, enter the following command 
from the OSS shell: 
gname [-s] filename
where the optional -s flag displays only the Guardian filename and filename is an 
OSS pathname. You can use shell wildcard characters in the OSS pathname; however, 
you should not use wildcard characters in the node-name portion of a pathname that 
includes the /E directory because of the potentially large number of files involved.
Figure 6-1 shows examples of using gname.










