HP Integrity NonStop H-Series - Manual (Page 67)

Objects in DSNM Commands
Object Specifications
098571 Tandem Computers Incorporated 3–3
You can supply additional qualifiers to make the name resolvable by issuing the
following command:
STATUS SERVER SERVER-X UNDER $PM2
The subsystem can be omitted because DSNM can determine it from the manager. The
object type is required because DSNM assumes it is TERM, if it is not specified.
Now suppose the DNS database contains the names of two Pathway servers with the
name SERVER-X, with one under $PM1 and one under $PM2. The object type can be
omitted from the object specification, because the DNS database can supply that
information. However, the manager name must be supplied because SERVER-X is
otherwise ambiguous. Given this example, the following command enables DSNM to
resolve the name and carry out the command:
STATUS SERVER-X
However, there is no way to predict whether the affected object is SERVERX under
$PM1 or SERVERX under $PM2. If you intend to find out the status of SERVERX
under $PM2, you can make the command unambiguous as follows:
STATUS SERVER-X UNDER $PM2
Finally, suppose that the DNS database contains SERVER-X1 as an alias for the
Pathway server named SERVER-X under $PM1, and SERVER-X2 as an alias for the
Pathway server named SERVER-X under $PM2. The following command is
unambiguous:
STATUS SERVER-X1
Caution If you specify an ambiguous name in a command, the command is executed and a subsystem object that
matches your object specification is affected, but not necessarily the subsystem object you intended. If
you are not certain whether or not an object specification is ambiguous, issue an informational command
such as STATUS to see how the name is resolved before you issue a control command against it.
Groups and Composites
Group and composite names refer to several subsystem objects. The names are DNS
entities, which can only be defined in DNS. All subsystem objects in a group or
composite are fully qualified, so DSNM does not need to determine any missing
qualifiers for the constituent objects. When used with groups and composites,
qualifiers act as selectors, picking out of the group or composite only those objects that
match the qualifiers.
For example, suppose the group COMM-LINES contains all data communications
lines on the local node. The following command starts all the lines on the node:
START COMM-LINES
However, the following command starts only the SNAX lines:
START SNAX COMM-LINES