Description
Example
Naming Convention
1
Type of Object
First Listener process for
the system
LSN0
$LSN number
Listener process
None
None
Automatically created by
WANMGR
TFTP process
None
None
Automatically created by
WANMGR
WANBOOT process
Tenth SWAN/SWAN 2
concentrator in the system
S10
S
number
SWAN/SWAN 2
concentrators
3
1
For more information about CLIM processes that use the CIP subsystem and the naming conventions for these
processes, refer to the
Cluster I/O Protocols (CIP) Configuration and Management Manual
.
2
ESS is only supported on the NS2100 commercial system.
3
Swan and SWAN 2 concentrators are only supported on the NS2100 commercial system.
On new NonStop systems, only one of each of these processes and names is configured:
•
TCP6SAM - $ZTC0
•
Telserv - $ZTCN0
•
Listener - $LSN0
No TFTP or WANBOOT process is configured for new NonStop systems.
NOTE:
Naming conventions or configurations for the dedicated service LAN TCP/IP are the
same as the TCP/IP conventions used with G-series and H-series RVUs. The names are $ZTCP0
and $ZTCP1. Hewlett Packard Enterprise does not support changing the names of these
processes.
OSM Service Connection provides the location of the resource by adding an identifying suffix to
the names of all the system resources. Other interfaces, such as SCF, also provide means to
locate named resources.
110
Default Startup Characteristics and Naming Conventions
