Telserv Manual

Subsystem Control Facility (SCF) for Telserv
Telserv Manual427174-009
4-4
Sensitive and Nonsensitive Commands
Sensitive and Nonsensitive Commands
Because some commands can have detrimental effects if improperly used, special
qualification is required to use them. These commands are called sensitive commands.
A sensitive command is one that can be issued only by a user with super-group
access, the owner of the subsystem, or a member of the same group as the owner of
the subsystem. When used in conjunction with the security features of the NonStop
Kernel operating system, SCF provides effective access control for sensitive
commands. Commands that request information or status but do not affect operation
are called nonsensitive commands. Nonsensitive commands are available to all users.
Objects
SCF controls a wide variety of data communications subsystems whose individual
components are called objects. Each object has an object type and an object name.
The object type describes the type of the object, such as LINE, SU (subdevice), or
PROCESS. The object name uniquely identifies an object within the system.
Object names usually follow a consistent set of naming conventions. Objects defined
during system generation are usually referred to by their device names, which consist
of a dollar sign ($) followed by a letter and from zero through six alphanumeric
characters. A LINE object, for example, might have the name $LIN32. A PROCESS
object sometimes has the same name as the line it controls.
Subdevices are often not defined during system generation and must be added to the
subsystem by using the SCF ADD command. The object name for an SU object
usually has two parts: the name of the line to which the SU has been added and the
unique name of the subdevice itself. The subdevice part of the name begins with a
pound sign (#) and includes up to seven alphanumeric characters. For example, an SU
object might have the name $LIN32.#PC, where $LIN32 is the name of the line.
There are many other object types and object names used in SCF. The objects
relevant to Telserv are described later in this section.
Subordinate Objects
Some subsystems are structured hierarchically, with a group of objects of one type
logically subordinate to objects of another type. For example, a number of subdevices
could be configured on a single line. In this case, an object specification (object-
spec) of the form line-name* (as in $LINE*) can be used to refer to all subdevices
on that line. Some SCF commands include a SUB parameter that refers to all
subordinate objects.
The SUB parameter has the following form:
SUB [ subtype ]
This parameter selects the subordinate objects affected by the command. subtype
can be a subordinate object type or one of the keywords ONLY or ALL. If a subordinate
object type is named, only objects of that type are affected. ONLY specifies that only