Guardian Procedure Calls Reference Manual

• Reserved process names
The operating system reserved process name space includes these names: $Xname, $Yname,
and $Zname, where name is from 1 through 4 alphanumeric characters. You must not use
names of this form in any application. System-generated process names (from
PROCESS_LAUNCH_, PROCESS_SPAWN_, PROCESS_CREATE_, NEWPROCESS[NOWAIT],
PROCESSNAME_CREATE_, CREATEPROCESSNAME and CREATEREMOTENAME procedures)
are selected from this set of names. For more information about reserved process names. see
Appendix B: Reserved Process Names.
• Creator access ID (CAID) and process access ID (PAID)
The creator access ID of the new process is always the same as the process access ID of the
creator process. The process access ID of the new process is the same as that of the creator
process unless the program file has the PROGID attribute set; in that case the process access
ID of the new process is the same as the user ID of the program file's owner and the new
process is always local.
• I/O error to the home terminal
An I/O error to the home terminal can occur if there are undefined externals in the program
file and PROCESS_CREATE_ is unable to open or write to the home terminal to display the
undefined externals messages. The error-detail parameter contains the file-system error
number that resulted from the open or write that failed.
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, see the Guardian Programmer's Guide and the
Guardian Application Conversion Guide.
994 Guardian Procedure Calls (P)