AM3270 and TR3271 Configuration and Management Manual

SCF Interface to AM3270 and TR3271
AM3270 and TR3271 Configuration and Management Manual—529993-001
4-3
Sensitive and Nonsensitive Commands
Several commands are available for displaying and changing SCF session parameters.
For example, the SYSTEM and VOLUME commands control the default system,
volume, and subvolume names used for expanding file names. The OBEY and OUT
commands control the files used for command input and display output. The ASSUME
command defines a default object to be used when the object is omitted from an SCF
command.
The TRACE command traces the operation of an object. While being traced, the object
continues normal operation, but it passes all message traffic to a trace procedure.
When the trace procedure recognizes a message that meets its selection criteria, it
stores the message in a trace file. You can then use the PTrace program to examine
the file.
The HELP command can be used in several different ways. In its basic form, it displays
a list of the available SCF commands. You can request additional specific information,
such as command syntax, for each command. For most subsystems, you can also
request subsystem-specific information for commands.
The HELP key is also available to display command syntax. (It is used in the same way
in the TACL command interpreter.)
The RUN command allows you to run another program during an SCF session.
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 with the security features of the NonStop OS, SCF
provides effective access control for sensitive commands. Commands that request
information or status but that 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. In the AM3270
and TR3271 subsystems, a PROCESS object always has the same name as the line it
controls.
Subdevices cannot be defined during system generation for the AM3270 and TR3271
subsystems and must be added to the subsystem by using the SCF ADD command.