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

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series

100

SCF Commands

SCF Reference Manual for J-Series and H-Series RVUs—529649-003

5-5

Effect of the ASSUME Command on Object-Name

Specification

except that

gpname

must be preceded by a pound symbol (#) and cannot be

enclosed in quotation marks.

For more information about generic processes, refer to the

SCF Reference

Manual for the Kernel Subsystem

Reserved Names

These names are reserved names and must not be used as logical device or process

names during system configuration:

In this list,

is any two-digit decimal number, and

aaa

is any combination of one, two,

or three letters or decimal numbers.

Effect of the ASSUME Command on Object-Name Specification

If an ASSUME command has been used to establish a default object type and fully

qualified object name, and if the object type and object name together refer to a valid

object, you can omit

object-spec

from a command. In this case, the command is

applied to the object known as the assumed object, the object designated using the

ASSUME command (described on page 5-36). The form of the object name depends

on the type of object. Usually, the name has the form of an operating-system device

name, subdevice name, or process name. Some examples follow:

•

All or part of the object name can be omitted if an ASSUME command has been

used to establish an appropriate object name. For example, if the command

-> ASSUME WS $L1.#TERM1

has been entered, subsequent entry of the INFO command by itself displays

information about the workstation called $L1.#TERM1.

•

Many SCF commands accept a list of object names in place of a single object

name. If so, object names must appear within a pair of parentheses and must be

separated by commas. The command is then applied to all the objects in the list.

For example, the command:

-> ASSUME $L1; INFO WS (#WS1, #WS2)

displays information about the $L1.#WS1 and $L1.#WS2 workstations.

•

Some subsystems are structured hierarchically, with a group of objects of one type

logically subordinate to an object of another type. For example, a number of

$AOPR $IPB $OSP $SYSTEM $TSCH

$C9341 $KEYS $PM $T $X

aaa

$CMON $MLOCK $S $TICS $Y

aaa

$CMP $MLOK $SPLS $TMP $Z

aaa

$DM

$NCP $SPLP $TRPM $0

$IMON $NULL $SSCP $TRMS