Subsystem Control Point (SCP) Management Programming Manual

Communicating With an SCP Process
Subsystem Control Point (SCP) Management Programming Manual—520619-001
2-7
Starting an SCP Process Using the
PROCESS_CREATE_ Procedure
SWAPVOL volname
specifies the volume on the local node to which extended memory is swapped. If
you omit this parameter, the SCP process uses the volume to which the data area is
swapped. See the SWAP process option on page 2-4.
Starting an SCP Process Using the PROCESS_CREATE_ Procedure
An application can create an SCP process by calling the Guardian
PROCESS_CREATE_ procedure, in which case the sequence of events is:
1. The application starts the SCP process by calling the PROCESS_CREATE_
procedure.
2. The application uses the FILE_OPEN_ procedure to open the SCP process in order
to send a startup message.
3. The application sends a startup message to the SCP process, specifying the desired
startup parameters.
4. The application closes the SCP process, which is then ready to be opened for SPI
communications by management applications.
Specify run options as arguments to the procedure itself, and specify startup parameters
in the subsequent startup message. For more information on PROCESS_CREATE_ and
other procedures, see the Guardian Procedure Calls Reference Manual and the
Guardian Programmer’s Guide.
Note. Applications are not required to use the PROCESS_CREATE_ procedure to create an
SCP process. An existing management application that starts an SCP process should run
without modification on newer node if the management, SCP, and managed subsystem
processes run at low PINs. See Implications for Management Applications
on page 3-7.