IPX/SPX Configuration and Management Manual

Managing NonStop™ IPX/SPX With the Subsystem
Control Facility (SCF)
IPX/SPX Configuration and Management Manual—425731-001
3-3
Objects
Objects
To configure the NonStop™ IPX/SPX environment, you must understand the structure
and hierarchy of the objects in the NonStop™ IPX/SPX subsystem. Each object has an
object type, an object name, attributes, and operational (summary) states associated with
it. NonStop™ IPX/SPX also supports object-name templates, which allow you to specify
commands by using wildcards. (See Object-Name Templates and Wildcards
on
page 3-6.)
Object Types
Figure 3-2 shows the hierarchy of the NonStop™ IPX/SPX object types.
Object Names
An object name is actually the name of the process that the object controls. When you
define NonStop™ IPX/SPX processes, you must specify object names that conform to
the naming conventions for NonStop™ Kernel objects.
SUBSYS Object
The SUBSYS object controls the IPXMGR process. One IPXMGR process exists for
each NonStop™ Himalaya S-series server and manages one or more IPXPROTO
processes on the system. The IPXMGR process name is $ZMGR. You start the
IPXMGR process using a generic process or with a TACL RUN command. (For an
example of how to start IPXMGR, see Task 2: Install and Configure NonStop™
IPX/SPX on page 1-4.)
PROCESS Object
The PROCESS object controls the IPXPROTO process. The IPXPROTO process name
must conform to the NonStop™ Kernel conventions for process names. The
recommended form for IPXPROTO process names is $ZNVn, where n is an
alphanumeric character (0 through 9 or A through Z). This convention allows
applications to use a simple screening algorithm to locate NonStop™ IPX/SPX
processes in a system. If the IPXPROTO process name is longer than four characters,
remote systems will be unable to access it.
Figure 3-2. NonStop™ IPX/SPX Object Types
015CDT .CDD
SUBSYS
PROCESS
SERVER