Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (A-B)
Guardian Procedure Calls Reference Manual—522629-013
2-10
ACTIVATEPROCESS Procedure
(Superseded by PROCESS_ACTIVATE_
.<8:15> PIN assigned by the operating system to identify the process in the
processor
If
process-id [0:2] references a process pair and process-id [3] is specified as
-1, then both members of the process pair are activated.
Condition Code Settings
< (CCL) indicates that either ACTIVATEPROCESS failed or no process designated
as
process-id exists.
= (CCE) indicates that the process is activated.
> (CCG) is not returned from ACTIVATEPROCESS.
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. Refer to “Considerations” for the PROCESSACCESSID procedure and
the
Guardian User’s Guide for information about the process access ID.
•
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.
See the
kill(2) function reference page either online or in the Open System
Services System Calls Reference Manual for details.
•
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. Refer to 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.