APLMGR SCF Reference Manual

Introduction to SCF for Tandem FTAM

OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001

1-9

Running SCF

You can start SCF by using the TACL command interpreter RUN command. This

command can be used interactively, included in a command (OBEY) file, or included in

a TACL macro or routine. Section 3, SCF Commands for Tandem FTAM

, describes the

SCF commands for OSI/FTAM and OSI/APLMGR.

SCF can accept input from a terminal or a disk file. You can change the input source

dynamically by using the OBEY command.

To start SCF, use the TACL RUN command described in the TACL Reference Manual.

Subsystem Control Facility (SCF) Commands

SCF commands are your means of controlling Tandem FTAM; Tandem FTAM is

managed through the SCF interface to the APLMGR process and to the initiator and

responder processes. You use the SCF command interface to configure each subsystem,

to monitor and evaluate its performance, and to make alterations when necessary.

General Command Format

An SCF command begins with a keyword identifying the command (such as, ADD,

START, or TRACE). If the command pertains to an object, it is followed immediately

by the object type and the object name. If additional information is required, the object

name is followed by a comma and the attributes required to further specify the object-

type or the action to be taken. For example, the following command modifies the

common name of an initiator process:

ALTER PROCESS \MARS.$AMGR.#FTAMI.FTI1, COMNAME "FTM1F"

Sensitive and Nonsensitive Commands

Some SCF commands cause changes in the operation of the subsystem to which they are

sent; for instance, they change the state or configuration of objects, start or stop tracing,

or reset the values of statistics counters. To protect the integrity of the subsystem, the

SCP process allows only certain users to perform such commands. Commands on which

SCP performs security checking and screening are called sensitive commands. SCP

limits the use of sensitive commands to the following Guardian user IDs:

•

Members of the super ID (group ID 255)

•

Members of the user group that owns the process to which the command is sent: that

is, members of the user group that owns either the APLMGR process (if the

$appl-mgr-name or indirect-process-name syntax is used) or the

initiator or responder process (if the $process-name syntax is used).

Note. The ownership of a responder process can change whenever an association is made

through the responder. Therefore, when issuing a TRACE, an ABORT SU, or a STATS (with

RESET option) command to a responder process, you might need to use a super ID to ensure

access to the command.