NIO CommKit Host Interface Installation and System Administration Manual

3-13
Control Tables (from AT&T 255-110-127)
srvtab
Mapping lines in the srvtab table consist of six tab-separated fields:
system service flags user program initial parms
NOTE: Delimit fields by tabs only. Do not use blanks.
These fields are described below.
System Field
The system field (originating group) contains a pattern against which origi-
nating groups are matched. The format of the pattern is area/exchange/
group[!][.user], where the suffixes ! and .user are optional.
The area/exchange/group pattern may be specified in one of the following
ways:
• completely specified as in 1c/sporty/hotrod
• consisting of a single askerisk (wild card) as in *
• consisting of a partially specified originating group with embedded wild card
characters (each asterisk matches any set of zero or more characters and each
question mark matches any single character).
Under these rules, originating group fields 1*?/sp?rty/h*rod*,??/*/hotrod,
and 1c/spor???h* all match the originating group 1c/sporty/hotrod. Origi-
nating group fields 1??/sp?rty/h*rod,* ??/*x/hotrod, and 1c/spor??h* do
not match the originating group 1c/sporty/hotrod. Note that the originating
group fields *,*/*, and */*/* are equivalent and match any originating group.
The originating group suffix ! may be specified for originating group pat-
terns that end with an asterisk (*) wild card. The exclamation point (!) pre-
vents the asterisk wild card from matching the local dkserver name. For
example, if the local server name is camaro, the pattern 1c/sporty/*! will
match all originating groups in area/exchange, 1c/sporty except 1c/sporty/
camaro. This feature prevents users from calling themselves on the same
host. The local server name and the group name of the host in the data
switch control computer database must be the same for the ! feature to work.
The originating group suffix .user may be used to match specific users from
either specific groups or from classes of groups. The user must be specified
as a decimal integer user ID to match the format provided in the call request
information. The group pattern *.0 would match the user root from any