Guardian Procedure Calls Reference Manual

PROCESS_CREATE_ can create a new process separate from any batch job, even if the caller
is a process that belongs to a batch job. In that case the job ID of the new process is 0. To
start a new process that is not part of a batch job, specify 0 for jobid.
PROCESS_CREATE_ can create a new batch job and establish the new process as a member
of the newly created batch job. In that case, the caller becomes the job ancestor of the new
job; the job ID supplied by the caller becomes the job ID of the new process. To start a new
batch job, specify a nonzero value (other than -1) for jobid.
A job ancestor must not have a process name that is greater than four characters (not counting
the dollar sign). When the caller of PROCESS_CREATE_ is to become a job ancestor, it must
conform to this requirement.
When jobid is omitted or set to -1:
If the caller is not part of a batch job, neither is the newly created process; its job ID is
0.
If the caller is part of a batch job, the newly created process is part of the same job
because its job ID is propagated to the new process.
Once a process belongs to a batch job, it remains part of the job.
Safeguard Considerations
For information on processes protected by Safeguard, see the Safeguard Reference Manual.
OSS Considerations
You cannot create an OSS process using the PROCESS_CREATE_ procedure.
PROCESS_CREATE_ returns error 12 if you try. Use the PROCESS_SPAWN_ procedure or
OSS functions to create an OSS process.
You can call PROCESS_CREATE_ from an OSS process to create a Guardian process.
Every Guardian process has these security-related attributes for accessing OSS objects. These
attributes are passed, unchanged, from the caller to the new process, whether the caller is an
OSS process or a Guardian process:
Real, effective, and saved user ID
Real, effective, and saved group ID
Group list
Login name
Current working directory (cwd)
Maximum file size
No other OSS process attribute is inherited by the new process.
OSS file opens in the calling process are not propagated to the new process.
File Privileges Considerations
On systems running J06.11 or later J-series RVUs or H06.22 or later H-series RVUs, files have an
additional file privilege attribute that specifies special privileges, if any, a file has when accessing
files in a restricted-access fileset. For example, the executable files for the Backup and Restore 2
product can be given the PRIVSOARFOPEN file privilege to a locally-authenticated member of the
Safeguard SOA group to back up and restore files that are in a restricted-access fileset.
996 Guardian Procedure Calls (P)