Guardian Procedure Calls Reference Manual

Batch Processing Considerations
NOTE: The job ancestor facility is intended for use by the NetBatch product. Other applications
that use this facility might be incompatible with the NetBatch product.
• When the process being created is part of a batch job, PROCESS_LAUNCH_ sends a job
process creation message to the job ancestor of the batch job. (See the discussion of job
ancestor in the Guardian Programmer's Guide.) The message identifies the new process and
contains the job ID as originally assigned by the job ancestor. This enables the job ancestor
to keep track of all the processes belonging to a given job.
For the format of the job process creation message, see the Guardian Procedure Errors and
Messages Manual.
• PROCESS_LAUNCH_ can create a new process and establish that process as a member of
the caller's batch job. In that case the caller's job ID is propagated to the new process. If the
caller is part of a batch job, to start a new process that is part of the caller's batch job, set
Z^JOBID to -1.
• PROCESS_LAUNCH_ 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 Z^JOBID.
• PROCESS_LAUNCH_ 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 Z^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_LAUNCH_ is to become a job ancestor, it must
conform to this requirement.
• When Z^JOBID is 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_LAUNCH_ procedure.
PROCESS_LAUNCH_ returns error 12 if you try. Use the PROCESS_SPAWN_ procedure or
OSS functions to create an OSS process.
• You can call PROCESS_LAUNCH_ 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
1076 Guardian Procedure Calls (P)