Safeguard Administrator's Manual (G06.29+, H06.08+, J06.03+)

Installation and Management
Safeguard Administrator’s Manual—523317-029
10-3
Process Considerations for the SMP and SAFECOM
°
Supplementary group list
°
Group count
A separate SHP process runs in every processor in a protected system. Each SHP
updates the process attributes of every process in its own processor running with the
user identity whose above-mentioned user attributes are changed. The SMP ensures
that all SHPs are operational.
Process Considerations for the SMP and
SAFECOM
The system uses a process identification number (PIN) to identify a process. When the
system creates a new process, it assigns a PIN to the process. Processes on a system
running D-series or G-series RVUs can have either a high or a low PIN as:
•
A low PIN ranges from 0 through 254.
•
A high PIN ranges from 256 through the maximum number supported by the
processor.
PIN 255 is used only for a synthetic process ID, which is described in the Guardian
Application Conversion Guide.
By default, SAFECOM runs at low PINs. The SMONs and SMP run at high PINs. If you
have a single system running D-series or G-series RVUs or a network that consists
only of systems running D-series and G-series RVUs, you can optionally allow
SAFECOM to run at high PINs by using the SET HIGHPIN option of Binder.
However, if you have a network of mixed systems running C-series and D-series or G-
series RVUs, recompile the low PIN processes on systems running C-series RVUs
using the HIGHREQUESTORS option to communicate with high PIN SMP.
Swap Space Migration Considerations
The SMON processes now require additional swap space on each processor. The
space is needed for an allocated flat data segment used for cache (for temporary
storage of pattern protection records) This cache improves performance considerably.
The SMONs require as much as an additional 64MB of virtual memory. System
administrators must ensure that enough swap space is available on each processor for
this new feature.
Note. SHP is supported on systems running on J06.10 and later J-series RVUs and H06.21
and later H-series RVUs.
Note. Even if CHECK-DISKFILE-PATTERN is OFF, the additional swap space is still required.