Telserv Manual

Subsystem Control Facility (SCF) for Telserv

Telserv Manual—427174-009

4-2

Subsystem Control Point (SCP)

The Subsystem Control Point (SCP) is a network-management process for receiving

and redistributing the messages that SCF sends to certain data communications

subsystems like Telserv.

SCP lies between SCF and Telserv. SCP provides security (by restricting access to

sensitive commands), version control, and tracing support for subsystems, as well as

providing support for application processes. Like SCF, DSM applications depend on

SCP to communicate with the different subsystems. DSM applications provide the

additional capability of automating many of the management tasks that can be useful in

a complex computing environment. Event messages are sent directly from the

subsystem to the EMS event collector ($0). You can filter the types of event messages

to be displayed, printed, or stored. For no-wait state, the default maximum limit is set to

15 for the concurrent event messages that can be sent from the subsystem to the EMS

event ($0). For more information about no-wait depth, see the Guardian Procedure

Calls Reference Manual.

SCF automatically opens and closes SCP. In most cases, the default SCP is the only

one you will ever need. If you should need to establish an SCF session through a

specific SCP other than the default SCP, you can start additional SCPs by using either

the SCF RUN command or the TACL RUN command. For more information about

SCP, see the SCF Reference Manual for SCP.

SCP can be used in two ways: interactively and programmatically. The interactive

interface is provided so you can choose either to let a person perform an action or to

automate the action.

The programmatic interface is based on the Subsystem Programmatic Interface (SPI),

which provides procedures that build and retrieve information from command,

Figure 4-1. SCF Overview

002VST .VSD

Command

(Obey)

SCF

SCP

($ZNET)

Telserv