Guardian Procedure Calls Reference Manual

Table 35 Summary of Process Creation Errors (continued)
Descriptionerror
On a TNS/E system, unresolved procedure references in a TNS program are
bound to an illegal label, so an attempt to invoke an unresolved procedure
generates an Illegal Instruction trap at the call site. The default handling is process
termination, but if the process has armed a trap handler, that handler will be
invoked.
(Note that there are no non-PIC programs on a TNS/E system; all native programs
are PIC.)
• For a PIC native program, the handling of unresolved external procedure references
is controlled by the rld_ignore attribute in the loadable object file containing
the unresolved reference—the program or any DLL loaded with it. The linker can
set the rld_ignore attribute to error, warn, or ignore. The default is error:
an unresolved reference causes the process creation to fail with error 74. If the
attribute is warn, the warning is issued every time the file is loaded. If the attribute
is ignore, loading proceeds without any warning
Unresolved procedure references in PIC objects are bound to a procedure named
UNRESOLVED_PROCEDURE_CALLED_. Unless the programmer has provided a
procedure of that name, the process calls that procedure in the native system
library. When invoked, that procedure causes a fault, generating a SIGILL
signal. The default handling of that signal is process termination, but other actions
are possible. If the process has installed a signal handler for the SIGILL signal,
that handler will be invoked.
For more information about handling a trap or signal, see the debugging, trap
handling and signal handling section in the Guardian Programmer’s Guide.
No process control block available, or no PIN less than 255 is available.15
Unable to allocate virtual address space.16
Unlicensed privileged program or library.17
Library conflict. (See General Considerations (page 1073).)18
Program file and library file specified are same file.19
Program file has an invalid process device subtype. (See General Considerations
(page 1073).)
20
Process device subtype specified in backup process is not the same as that in the
primary process.
21
Backup creation was specified, but caller is unnamed.22
DEFINE error; error-detail contains either a file-system error number, a DEFINE
error number, or this error subcode.
1
24
An excessive number of DEFINEs were to be propagated. See the
PROCESS_CREATE_ procedure DEFINE Considerations (page 995).
2
Dynamic IOP error. (This error is returned only to privileged callers or to unprivileged
callers attempting to use certain privileged features. On D-series RVUs, it can be
26
returned when an I/O process is incorrectly configured. On G-series RVUs, it can be
returned by an attempt to create a D-series I/O process.)
PFS size in program file is invalid (this error is not generated in G06.12 and later
RVUs).
27
An unrecognized error number was returned from a remote system (probably running
another level of software); error-detail contains the error number.
28
Unable to allocate a priv stack for the process.29
Unable to lock the priv stack for the process.30
Unable to allocate a main stack for the process.31
PROCESS_LAUNCH_ Procedure 1063