Subsystem Control Point (SCP) Management Programming Manual

SPI Programming Considerations for SCP
Subsystem Control Point (SCP) Management Programming Manual—520619-001
3-2
Communication Alternatives
Communication Alternatives
If the SCP to which the command is directed is already opened by your management
process, you can send the command directly to it, as Figure 3-1 shows.
If your management process needs to direct a command to an SCP process other than the
one it is currently using to route commands, it can route the command message through
the open SCP process to the target SCP process, as Figure 3-2
shows.
Also see the discussion of interprocess communications restrictions in D-Series Changes
on page 3-7.
Identifying the Target Process
To direct a command to an SCP process (rather than through the SCP process to another
subsystem), assign the name of the SCP process to ZCOM-TKN-OBJNAME and the
native object type ZCOM-OBJ-PROC to the object type token ZSPI-TKN-OBJTYPE.
(For more information on the native object type, see the SPI Common Extensions
Manual.)
Figure 3-1. Managing an SCP Process Directly
Figure 3-2. Managing an SCP Process Indirectly
Management
Process
SCP
Process
SCP1
SPI Command
for SCP1
SPI Response
from SCP1
VST002.vsd
Management
Process
SCP
Process
SCP1
SPI Command
for SCP2
SPI Response
from SCP2
VST003.vsd
SCP
Process
SCP2
SPI Command
for SCP2
Response
from SCP2