SCF Reference Manual for J-Series and H-Series RVUs

SCF Commands
SCF Reference Manual for J-Series and H-Series RVUs—529649-003
5-3
SCF Object Lists
object-type
is a subsystem-specific keyword identifying the type of object being referred to. If it
is omitted, the subsystem process may or may not attempt to determine the object
type. If an attempt to determine the object type fails, an error message is
displayed.
The variable object-type designates the type of the object or objects to be
acted on by the command. You can omit object-type if it has been assumed
using the ASSUME command or if the subsystem in use can derive the type of the
object from the object name.
An exception is the null object type, which has no name. The null object type is
reserved for use with the AGGREGATE, NAMES, and VERSION commands, that
is, in cases where the object type is irrelevant or not known.
object-name
is either the name of a single object or (if it includes a wild-card character) the
name of a group of objects (also known as an object-name template). The syntax
of object-name is
[ \ system .[$ device ]][. subdevice ]
[." subdevice " ]
[.# gpname ]
\ system
is the name of a network node. It consists of an alphabetic character followed
by zero through seven alphanumeric characters with no embedded blanks.
$ device
is the name of a logical device (for example, a communications line) controlled
by a subsystem. It has this form:
{ $ name | $ ldev | $ template }
For a list of names that must not be used for $ device , see Reserved Names
on page 5-5
.
$ name
consists of an alphabetic character followed by zero through six
alphanumeric characters with no embedded blanks.
$ ldev
is an existing logical-device number, as shown by the SCF LISTDEV
command.