Guardian Procedure Calls Reference Manual

library” is the set of implicit DLLs. At load time, symbols are bound to the first definition found
in the search list of the program.
If no library specification is provided (priority bit 1 is zero, or library-file is blank), the
process runs with whatever library file, if any, is specified in the program file. The
library-file parameter can specify either a file name, or that no library should be used.
If this specification differs from what is recorded in the program file, the process must have
write access to the program file. For a TNS or non-PIC native process, a different library
specification used in a successful NEWPROCESS[NOWAIT] invocation replaces the one in
the program file; if an instance of the program is already running that replacement cannot
occur and a library conflict error is reported. For a PIC process, the library specification in
the program file is not replaced, so multiple processes can be running the same program with
different libraries simultaneously.
The association of a library with a program file can be recorded in the program file by the
Binder or linker.
For more information about building TNS user libraries, see the Binder Manual. For more
information about building non-PIC TNS/R SRLs, see the nld Manual and the noft Manual. For
more information about building PIC TNS/R DLLs, see the ld Manual. For more information
about building PIC TNS/E DLLs, see the eld Manual and the enoft Manual. For more information
about loading PIC programs and DLLs, see the rld Manual.
• Library conflict—NEWPROCESS[NOWAIT] error
The library file for a process can be shared by any number of processes. However, when a
TNS or non-PIC native program file 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. An error 9 ("library conflict") occurs
when a copy of the running program runs with a different library configuration than was
specified in the call to NEWPROCESS[NOWAIT].
• Startup messages and NEWPROCESS[NOWAIT]
The caller of NEWPROCESS[NOWAIT] has the responsibility to format and send a startup
message to the new process, if one is required. For more information on the startup message,
see the Guardian Procedure Errors and Messages Manual.
• Device subtypes for named processes
Process device subtype is an object file attribute that can be set when compiling or linking a
program. FILEINFO, DEVICEINFO, and other information procedures return the device type
and subtype of a named process. A process with a device subtype other than zero must be
named.
There are 63 device subtypes available (0 is the default subtype):
are for general use. Any user may create a named process with a process subtype in this range.48- 63
are reserved for definition by HP. Currently, 1 is a CMI process, 2 is a security monitor process, 30 is
a device simulation process, and 31 is a spooler collector process. Additionally, for subtypes 1 - 15, if
1 - 47
the caller of NEWPROCESS[NOWAIT] does not have a creator access ID of the Super ID, the object
file is not LICENSED, or the object file is not PROGIDed to the Super ID, NEWPROCESS[NOWAIT]
rejects the request with an error.
• HP 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)
NEWPROCESS[NOWAIT] Procedures (Superseded by PROCESS_LAUNCH_ Procedure) 859