TCP/IP Configuration and Management Manual

SCF Reference
TCP/IP Configuration and Management Manual—427132-004
4-6
Naming Convention Summary
Naming Convention Summary
Table 4-3 summarizes the reserved names for each object type and the naming
convention rules.
Wildcard Support
Normally, an SCF command line must include an object specifier composed of the
object type and an object name. For many commands, the NonStop TCP/IP subsystem
accepts object-name templates. With an object-name template, one object name can
be used to indicate that multiple objects of a given object type are to be affected by the
command.
Object-name templates allow you to specify multiple objects by entering either a single
wildcard character, or text and one or more wildcard characters. With the NonStop
TCP/IP subsystem, you can use the following wildcard characters:
Table 4-3. Object Naming Convention Summary and Reserved Names
Object Type
Reserve
d Names
Starting
Symbol
(Required)
First
Character
Requirement
First Character
Recommendation
Character
Limit
ADDRMAP #ZADR # Letter None 7
ENTRY None # Letter None 7
null N/A N/A N/A N/A N/A
PROCESS None $ Letter ZTCx where x is a
letter or a numeric
digit.
7
ROUTE #RTn
and
DRTn
# Letter None 7
SERVER None # Letter None 7
SUBNET #LOOP0 # Letter SN followed by a
SUBNET number
7
* Use an asterisk (*) to represent a character string of undefined length. The
following example deletes all SUBNETs and routes subordinate to $ZTC0:
-> DELETE SUBNET $ZTC0.*
The following example deletes all SUBNETs subordinate to $ZTC0 that have
names that start with #SN:
-> DELETE SUBNET $ZTC0.#SN*