SPI Programming Manual (G06.24+, H06.03+, J06.03+)

Introduction to SPI
SPI Programming Manual—427506-006
1-12
Converting Management Applications
Interprocess Communications Restrictions
These restrictions apply to communication among processes on a node running a
D-series RVU or among processes in a mixed network of C-series and D-series RVUs
and are relevant to all instances of SPI requester-server communications:
•
No process on a node running a C-series RVU can be opened by a high-PIN
process on a node running a D-series RVU. For example, a management
application running at a high PIN cannot open an SCP process on a node running
a C-series RVU, nor can an SCP running at a high PIN open a subsystem
manager process on a node running a C-series RVU.
•
A high-PIN process on a node running a D-series RVU can open an unconverted
low-PIN process on a node running a D-series RVU if the low-PIN process has
been recompiled to set the HIGHREQUESTERS object-file attribute.
For more information about these restrictions and how to overcome them, see the
Guardian Application Conversion Guide .
Converting Management Applications
Existing management applications do not need to be converted in order to run on a
system running a D-series RVU or in a mixed network of C-series and D-series RVUs if
all related processes run at low PINs. (Related processes include the management
application, the managed subsystem processes, and any intermediate process such as
SCP.)
However, if you decide to convert a management application in order to take
advantage of the new features of the operating system for D-series RVUs:
1. Consult the Guardian Application Conversion Guide for an overview of conversion
and its benefits. This guide provides help with the details of the conversion
process.
2. Modify your management application to use any new tokens for D-series RVUs
described in the management programming manual for the managed subsystem.
3. Convert the sections of your application that process event messages. (See the
EMS Manual. )