Guardian Procedure Calls Reference Manual

Considerations
When ACTIVATEPROCESS is called on a Guardian process, the caller must be the super ID
(255,255), the group manager (n,255) of the process access ID, or a process with the same
process access ID as the process or process pair being activated. For more information about
the process access ID, see the PROCESSACCESSID procedure Considerations (page 1131) and
the Guardian Programmer's Guide.
When ACTIVATEPROCESS is called on an OSS process, the security rules that apply are the
same as those that apply when calling the OSS kill() function. For details, see the kill(2)
function reference page either online or in the Open System Services System Calls Reference
Manual.
ACTIVATEPROCESS cannot be used on a high-PIN unnamed process. However, it can be
used on a high-PIN named process or process pair; process-id[3] must contain either -1
or two blanks.
To activate a high-PIN unnamed process, use the PROCESS_ACTIVATE_ procedure. See the
Guardian Programmer's Guide.
OSS Considerations
When used on an OSS process, ACTIVATEPROCESS has the same effect as calling the OSS
kill() function with the input parameters as follows:
The signal parameter set to SIGCONT
The pid parameter set to the OSS process ID of the process identified by process-id in
the ACTIVATEPROCESS call
The SIGCONT signal is delivered to the target process.
46 Guardian Procedure Calls (A-B)