Subsystem Control Point (SCP) Management Programming Manual

Communicating With an SCP Process
Subsystem Control Point (SCP) Management Programming Manual—520619-001
2-2
Starting an SCP Process
Starting an SCP Process
This subsection describes two methods for starting an SCP process:
•
Issuing a RUN command to a command interpreter
•
Calling the Guardian PROCESS_CREATE_ procedure
You declare SCP process run options and startup parameters in the RUN command or in
the PROCESS_CREATE_ procedure call and subsequent startup message. For a
description of these parameters, see Starting an SCP Process Using the RUN Command
.
The SCP Object File
The SCP program object file is initially installed in the subvolume $SYSTEM.SYSnn
although system management might move it.
The SCP program object file must be properly secured:
•
Owned by the super ID
•
PROGID set to the super ID
•
LICENSE set
•
Process access xxNx for network access or xxAx for local system access
The $ZNET SCP Process
The Subsystem Control Facility (SCF) is an interactive subsystem management
application that converts typed commands into SPI command messages and routes them
through an SCP process to the target subsystem. Unless otherwise directed, SCF uses an
SCP process named $ZNET, which can be found running on most nodes as a result of
SCF activity. Management applications other than SCF can route commands through the
$ZNET process to avoid starting other SCP processes.
Starting an SCP Process Using the RUN Command
To start an SCP process from a command interpreter like Compaq Tandem Advanced
Command Language (TACL), issue a RUN command. Specify run options between the
slashes and startup parameters after the run options: