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

SNAX/XF
Subsystems
5–14 098571 Tandem Computers Incorporated
SNAX/XF If you use DSNM to control the SNAX/XF subsystem, you will find the following
information helpful. While it covers what you need to know about SNAX/XF from
the viewpoint of operating DSNM, it is not exhaustive. For more details on the SNAX
subsystem, refer to the SNAX/XF Configuration and Control Manual.
The DSNM keyword for SNAX/XF is SNAX.
Object Types The SNAX/XF subsystem contains three object types, LINE, PU, and LU, which
correspond to lines, physical units, and logical units. If you issue a command for this
subsystem without specifying the object type, the object type defaults to LU if the
object is in the form $line.#lu; otherwise, it defaults to LINE. The hierarchical
relationships among lines, physical units, and logical units is shown in Figure 5-6.
Figure 5-6. Subsystem Object Hierarchy in the SNAX/XF Subsystem
LU LU
PU
006
PU
LINE
Note To monitor the status of SNAX LUs in NetStatus, you must make sure that the LUOPMSG attribute of
each SNAX line is ON. The LUOPMSG attribute can be set during system generation, or later through
SCF. For more information on SCF, refer to the Subsystem Control Facility (SCF) Reference Manual.
If LUOPMSG is OFF, state information on LU objects as reported by the DSNM INQUIRE command, can
be incorrect, because the SNAX subsystem does not log state change messages for LU objects when
LUOPMSG is OFF.