SCF Reference Manual for G-Series RVUs (G06.27+)

SCF Commands
SCF Reference Manual for G-Series RVUs—520413-005
5-6
Effect of the ASSUME Command on Subdevice
Specification
subdevices could be configured on a single line. In this case, an object
specification of the form $line-name (as in INFO WS $LINE1.*) can be used to
refer to all subdevices on that line. For example, the command:
-> ASSUME LINE $LINE1; INFO WS *
displays information about all workstations attached to line $LINE1.
•
The following ASSUME command assigns a workstation as the assumed object.
The subsequent INFO command uses the assumed object type (WS) and the
$device part of the object name ($L1), but overrides the #subdevice part of the
assumed object name.
-> ASSUME WS $L1.#TERM1
-> INFO #TERM2
•
If you enter the following ASSUME command after the ASSUME command from
the preceding example, the INFO command that follows it replaces the
#subdevice part of the assumed object name and displays information about the
new assumed object, $L1.#TERM3.
-> ASSUME #TERM3
-> INFO
Other subsystems use the SUB parameter of some SCF commands to refer to all
subordinate objects. Refer to SCF Subdevices on page 3-5 for information about
subordinate objects.
Effect of the ASSUME Command on Subdevice Specification
A fully qualified subsystem name would be specified as
$ABC.XYZ.W
Using the ASSUME command to establish an object type and object name allows you
to specify partially qualified subsystem names. For example, the command:
-> ASSUME LINE $ABC
defines an assumed LINE object type named $ABC. You can then issue partially
qualified subsystem names, as shown in the following INFO command examples:
Suppose you issue the command:
-> ASSUME SU $ABC.#DEF
-> INFO translates to -> INFO LINE $ABC
-> INFO SU translates to -> INFO SU $ABC
-> INFO $LMN translates to -> INFO LINE $LMN
-> INFO #XYZ translates to -> INFO LINE $ABC.#XYZ