Best Practices for Deploying HP-UX Secure Resource Partitions (SRP) for SAP Whitepaper

9
Figure 2. Display issue in ST06
If the status overview in ST06 is mandatory in the user environment, then consider enabling the
execution rights for saposcol in the respective SRP compartment rule file.
Note
Please note that in this case, saposcol can be stopped for the whole system
from just one SAP system.
Even if the execution access is allowed, the status display is not correct. In figure 2, the line item
Collector in the status overview shows “not running (process ID not found).” The reason why is
because SAP gets the process ID (pid) of saposcol out of the shared memory and checks on the OS to
see if the pid still exists. Since saposcol is running in a separate compartment, the pid cannot be
detected and this error message appears.