Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (P)
Guardian Procedure Calls Reference Manual—522629-013
12-50
PROCESS_CREATE_ Procedure
(Superseded by PROCESS_LAUNCH_ Procedure )
Nowait Considerations
•
If you call this procedure in a nowait manner, the results are returned in the nowait
PROCESS_LAUNCH_ or PROCESS_CREATE_ completion message (-102), not
the output parameters of the procedure. The format of this completion message is
described in the
Guardian Procedure Errors and Messages Manual. If error is
not 0, no completion message is sent to $RECEIVE. Errors can be reported either
on return from the procedure, in which case
error and error-detail might be
meaningful, or through the completion message sent to $RECEIVE.
Compatibility Considerations
•
If the new process is to be accessible to a process with a low PIN, then it must be
forced into a low PIN (below 255). You can force the process into a low PIN either
by specifying
create-options.<15> = 1 (requires a low PIN), or by making sure
that the program-file high-PIN flag is off.
•
If you want the new process to be forced into a low PIN only if the calling process
was forced into a low PIN, specify
create-options.<10> = 0 (requires a low PIN
if the caller has the inherited force-low attribute set) and
create-options.<15> =
0 (can have any PIN).
•
If you want explicit control over each child process with respect to running with a
high or low PIN, specify
create-options.<10> = 1 (ignore the caller’s inherited
force-low attribute) and
create-options.<15> = either 1 (requires a low PIN) or
0 (can be assigned any PIN) as appropriate.
•
If the new process is unnamed, it must be forced into a low PIN if it is to be
accessible to processes that do not know about high PINs.
•
If the new process has a high PIN and has a name with five or fewer characters
(not counting the $), it is accessible to any high PIN process running on any node
in the network.
•
For further information on compatibility, refer to the Guardian Programmer’s Guide
and the
Guardian Application Conversion Guide.
DEFINE Considerations
•
DEFINEs are propagated to the new process from the process context of the
caller, from a caller-supplied buffer containing DEFINEs collected by calls to
DEFINESAVE, or from both of these. DEFINEs are propagated to the new process
according to the DEFINE mode of the new process and the propagation option
specified in
create-options. If both sets of DEFINEs are propagated and both
sets contain a DEFINE with the same name, the DEFINE in the caller-supplied
buffer is used. When a caller is creating its backup, the caller’s DEFINEs are
always propagated, regardless of the options chosen.
The =_DEFAULTS DEFINE is always propagated, regardless of the options
chosen. If the DEFINE buffer contains a =_DEFAULTS DEFINE, that one is