TS/MP 2.5 System Management Manual

command. But PATHCOM uses values defined with the CMDCWD command to resolve relative
pathnames when it processes ADD or ALTER commands.
If a default absolute pathname /abc is defined with the CMDCWD command (assuming no value
is set for the CWD attribute), all OSS relative path names in ADD or ALTER commands are
resolved with the /abc absolute pathname. The resolved path names are sent to the
PROCESS_SPAWN_ procedure. However, the default OSS directory name and other relative
OSS path names are stored separately in the PATHMON configuration file.
If you issue the CMDCWD command again to assign the pathname /xyz (and there is still no
value defined by the SET SERVER CWD command), all relative path names sent thereafter
to PROCESS_SPAWN_ procedure are now resolved with the /xyz pathname.
CMDVOL Command
Use the CMDVOL command to set the default node, volume, or subvolume for the expansion of any
Guardian file names associated with objects supported under NonStop TS/MP or Pathway/iTS,
except command file names used with the OBEY command. Guardian file names specified in SET
commands are expanded with the current value defined by the CMDVOL command.
CMDVOL { [ \node. | \*.] $volume.subvolume }
{ [ \node. | \*.] $volume }
{ [ \node. | \*.] subvolume }
{ \node | \* }
\node
specifies the node name to be used for file expansion.
\*
specifies that the node where the PATHMON process is running at any given time be used as the
node name for file name expansion. \* is a generic node name designating PATHMON’s current
node. This is the default specification when the Pathway NODEINDEPENDENT attribute is set to
ON.
$volume
specifies the volume to be used for file expansion.
subvolume
specifies the subvolume to be used for file expansion.
Considerations
If you omit the CMDVOL command, the default setting in effect is the node, volume, and
subvolume of the user who started PATHCOM.
The first time the CMDVOL command is run, any parameters not specified default to the settings
of the user who started PATHCOM. For subsequent CMDVOL commands, parameters not
specified default to the value established by the previous CMDVOL command.
As an example, assume that the first time the CMDVOL command is issued, the volume is not
specified. The volume defaults to $CHICAGO, the volume of the user who started PATHCOM.
A second CMDVOL command is issued, this time explicitly setting the volume as $PROVO. If
a third CMDVOL command is issued without a specified volume, the value for the volume
defaults to $PROVO.
After a CMDVOL command is run, it remains in effect until either another CMDVOL command
is run or the PATHCOM session ends. Thus, if the node \MARS is defined with the CMDVOL
138 PATHCOM Operation Commands