pTAL Reference Manual (G06.24+, H06.09+, J06.03+)

and run the compiler again, it looks for newfiles.myutil.
If you omit the node or volume, the HP TACL product uses the current default node or volume. If
you omit the subvolume, the compiler ignores the command. HP TACL DEFINE names are not
allowed.
The ASSIGN SSV command also lets you specify the order in which subvolumes are searched.
You can specify ASSIGN SSV commands in any order. If the same SSV value appears more than
once, the HP TACL product stores only the last command having that value.
For example, if you issue the following commands, the HP TACL product stores only two of the
messages:
StoredAssign SSV Command
YesASSIGN SSV28, $a.b
NoASSIGN SSV7, $c.d
NoASSIGN SSV7, $e.f
YesASSIGN SSV07, $g.h
The compiler stores ASSIGN SSV messages in its SSV table in ascending order.
For each file name the compiler processes, the compiler scans the SSVs in ascending order from
SSV0 until it finds a subvolume that holds the file.
For example, if you issue the following ASSIGN commands before running the compiler:
ASSIGN SSV7, $aa.b3
ASSIGN SSV10, $aa.grplip
ASSIGN SSV8, mylib
ASSIGN SSV20, $cc.divlib
ASSIGN trig, $sp.math.xtrig
and the compiler encounters the following SOURCE directive:
?SOURCE unpack
the compiler first looks for an ASSIGN message having the logical name unpack. If there is none,
the compiler looks for the file in subvolumes in the following order:
$aa.b3.unpack (SSV7)
$default-volume.mylib.unpack (SSV8)
$aa.grplib.unpack (SSV10)
$cc.divlib.unpack (SSV20)
$default-volume.default-subvolume.unpack
The compiler uses the first file it finds. If it finds none named unpack, it issues an error message.
When the compiler encounters this directive:
?SOURCE trig
it tries only $sp.math.xtrig; if it does not find that exact file, it issues an error message.
524 Disk File Names and HP TACL Commands