TS/MP 2.5 System Management Manual

Guardian File Names
Each disk file in the Guardian file-system is identified by a unique, symbolic file name, described
in these paragraphs.
File Name Format
The name, and therefore the location, of a Guardian disk file is determined in four parts:
• \node—Identifies a specific system within a network
• $volume—Identifies a physical disk pack mounted on a disk unit
• subvolume—Identifies a disk file as a member of a related set of files as defined by the user
• file–identifier—Identifies a particular file within the subvolume
File names of disk files are represented to HP subsystem programs by these four parts concatenated
into a contiguous string. Each part is separated from the other by a period as follows:
\node.$volume.subvolume.file–identifier
When you supply only a partial file name as a command parameter, the internal representation
of the file name is expanded into the full four-part file name. As a minimum, a partial file name
must consist of the file identifier.
Each process and each device, such as a tape drive or printer, is identified the same way a disk
file is identified. For example:
\TSB.$TAPE1
specifies a particular tape drive on the system named \TSB. If a Pathway environment is running
on this system, only $TAPE1 is required for the file name.
File Name Expansion
File name expansion is accomplished through the use of default names. If you omit the node,
volume, or subvolume name in a command parameter, PATHCOM uses system defaults to expand
the file name before passing the name to the PATHMON process.
To get the default for the node name, PATHCOM first determines whether the SET PATHWAY
NODEINDEPENDENT attribute is set to ON. If NODEINDEPENDENT is ON, the default node
name is \* , a generic name representing the node where the PATHMON process is currently
running. For information on configuring for the node independence, see “Specifying Node
Independence” (page 54) and “SET PATHWAY Command” (page 159).
If the SET PATHWAY NODEINDEPENDENT attribute is set to OFF, PATHCOM uses the node name
you supply in the CMDVOL command. PATHCOM also uses the default volume and subvolume
names specified in the CMDVOL command. For information on the CMDVOL command, see “CMDVOL
Command” (page 138).
Although the PATHMON process uses system names, it does not store server process names (nor
Pathway/iTS TCP names) in fully qualified network form. All other file names are kept in the form:
\node.$volume.subvolume.file–identifier
OSS Pathnames
An OSS pathname in the OSS attributes PROGRAM, STDIN, STDERR, and STDOUT can be an
absolute pathname or a relative pathname. Case is significant.
When specifying an OSS pathname longer than one line, use the PATHCOM continuation character
(&) at the end of the line to indicate continuous input. If the pathname includes an ampersand (&)
as part of the name and the ampersand occurs at the end of an input line, enter two ampersands.
An ampersand occurring in the middle of an input line, embedded in a pathname, need not be
doubled. To embed blanks, quotes, commas, and semicolons, use the same rules as for PATHCOM,
and enclose the entire pathname in quotes.
Guardian File Names 131