Guardian Procedure Calls Reference Manual

Process Descriptors
A process descriptor is a form of process file name that always includes the node and seq-no
sections of the name; when identifying a named process, it never includes the optional qualifiers
qual-1 or qual-2. Guardian 90 procedures always return a process descriptor as the
external-form representation of a process or process pair.
Examples
These are examples of process descriptors:
ode5.$zproc:1622091078
\east.$:5:131:436612
File-Name Patterns
A file-name pattern resembles a file name but designates a set of entities (that is, a set of disk files,
devices, processes, or systems) through the use of pattern-matching characters. The pattern-matching
characters are:
• An asterisk (*) matches zero or more letters, digits, dollar signs, pound signs, or a combination
of these.
• A question mark (?) matches exactly one letter, digit, dollar sign, or pound sign.
The syntax for a file-name pattern is:
\pattern
or
[\pattern.]$pattern[.pattern[.pattern]]
or
[\pattern.][[pattern.]pattern.]pattern
pattern
consists of one or more characters. Allowable characters are letters, digits, pound signs (#),
asterisks (*), and question marks (?). The maximum length of a pattern is twice that of the
corresponding portion of a file name. (For example, 16 characters is allowed for a pattern
that corresponds to a subvolume portion. This allows you to interleave multiple asterisks with
a set of fixed characters.)
The all-numeric portions of a file name (that is, the seq-no, cpu, and pin portions of process
file names) cannot be represented by pattern.
This syntax allows combinations of characters that are not permitted in file names, such as the use
of pound signs anywhere in any portion. However, using such a combination of characters means
that the pattern cannot designate any entity.
Note that the dollar sign is allowed only in the second form of the file-name pattern, as shown in
the diagram above. The presence or absence of the dollar sign determines whether the system
interprets the file-name pattern according to the rules of the second or third form. As a result, the
file-name pattern "$*.*" cannot match a permanent disk file name, but "*.*" can match a permanent
disk file name (in the form subvol.file-id).
Examples
These are examples of file-name patterns:
matches all files in the current subvolume that have names (file IDs) containing the letter "z."
*z*
matches all devices on the current node that have 7-character names starting with “$TERM,” such as
“$TERM12.”
$TERM??
matches all disk files on the current volume that are in subvolumes whose names begin with the letter “P.”
P*.*
Syntax 1539