Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (P)
Guardian Procedure Calls Reference Manual—522629-013
12-48
PROCESS_CREATE_ Procedure
(Superseded by PROCESS_LAUNCH_ Procedure )
appropriate attribute of the DEFINE, the resolved name will include the caller’s
node.
See below for details on resolution of specific file-name parameters.
•
For TNS and accelerated processes on RVUs preceding the D42.00 RVU, if
swap-file or ext-swap-file:
•
is specified and a file with that name exists, that file is used for memory
swapping of the user data stack (
swap-file) or the default extended data
segment (
ext-swap-file) during execution of the process; if no file of that
name exists, then a file of that name and of the necessary size is created and
used for swapping. If the file name is partially qualified, the system uses the
=_DEFAULTS DEFINE to resolve it.
•
Specifies the name of a temporary file that is already in use, an error is
returned.
•
Specifies only the disk volume name, then a temporary file is created on the
specified disk device.
•
Is not specified or length is 0, then the SWAP volume name in the
=_DEFAULTS DEFINE is used if available. Otherwise, the system chooses
where to place the file.
•
Creation of the backup of a named process pair
If the backup of a named process pair is created, the backup process becomes the
creator or mom of the primary (that is, of the caller to PROCESS_CREATE_) and
the primary becomes the mom of the newly created backup process. Refer to the
discussions of “mom process” and “ancestor process” in the
Guardian
Programmer’s Guide.
•
Program file and user library file differences
A user library is an program file containing one or more procedures. The
difference between a program file and a library file is that the library file cannot
contain a MAIN procedure; a program file must contain a MAIN procedure.
Undefined external references in a program file are resolved from the user library,
if any, or the system library. Unresolved references in a library are resolved only
from the system library.
•
Library conflict—PROCESS_CREATE_ error
The library file for a process can be shared by any number of processes.
However, when a program is shared by two or more processes, all processes must
have the same user library configuration; that is, all processes sharing the program
either have the same user library, or they have no user library. A library conflict
error occurs when there is already a copy of the program running with a library
configuration different from that specified in the call to PROCESS_CREATE_.