Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (P)
Guardian Procedure Calls Reference Manual—522629-013
12-150
PROCESS_LAUNCH_ Procedure
propagated; otherwise, the =_DEFAULTS DEFINE in the caller’s context is
propagated.
Buffer space for DEFINEs being propagated to a new process is limited to 256 KB
whether the process is local or remote. However, the caller can propagate only as
many DEFINEs as the child’s PFS can accommodate in the buffer space for the
DEFINEs themselves and in the operational buffer space needed to do the
propagation. The maximum number of DEFINEs that can be propagated varies
depending upon the size of the DEFINEs being passed.
•
When a process is created, its DEFINE working set is initialized with the default
attributes of CLASS MAP.
•
The Z^PROGRAM^NAME, Z^LIBRARY^NAME, Z^SWAPFILE^NAME, or
Z^EXTSWAPFILE^NAME fields can be DEFINE names; PROCESS_LAUNCH_
uses the disk volume or file given in the DEFINE. If Z^PROGRAM^NAME is a
DEFINE name but no such DEFINE exists, an error is returned. If any of the other
names is a DEFINE name but no such DEFINE exists, the procedure behaves as if
no name were specified. This feature of accepting names of nonexistent DEFINEs
as input gives the programmer a convenient mechanism that allows, but does not
require, user specification of the location of the library file, the swap file, or the
extended swap file.
•
For each process, a count is kept of the changes to that process’s DEFINEs. This
count is always 0 for newly-created processes. The count is incremented each
time the procedures DEFINEADD, DEFINEDELETE, DEFINESETMODE, and
DEFINEDELETEALL are invoked and a consequent change to the process context
occurs. In the case of DEFINEDELETE and DEFINEDELETEALL, the count is
incremented by one even if more than one DEFINE is deleted. The count is also
incremented if the DEFINE mode of the process is changed. If a call to
CHECKDEFINE causes a DEFINE in the backup to be altered, deleted, or added,
then the count for the backup process is incremented.
Batch Processing Considerations
•
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.
Refer to the
Guardian Procedure Errors and Messages Manual for the format of
the job process creation message.
•
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
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.