Guardian Procedure Calls Reference Manual

Table 35 Summary of Process Creation Errors (continued)
Descriptionerror
Parameter error; from PROCESS_LAUNCH_ and PROCESS_SPAWN_,
error-detail contains the literal for the first parameter to be found in error. See
2
Table 36 (page 1069) for possible values. From PROCESS_CREATE_, error-detail
contains the number of first parameter found to be in error, where 1 designates the
leftmost parameter.
NOTE: The PROCESS_CREATE_ parameters are counted as in TAL (see the
PROCESS_CREATE_ procedure Syntax for TAL Programmers (page 987)) rather than
C. Thus, program-file:length is parameter 1, library-file:length is
parameter 2, and so on; priority is reported as parameter 5 although it is the 9th
parameter in the C calling sequence.
Bounds error; from PROCESS_LAUNCH_ and PROCESS_SPAWN_, error-detail
contains the literal for the first parameter to be found in error. See Table 36 (page 1069)
3
for possible values. From PROCESS_CREATE_, error-detail contains the number
of first parameter found to be in error, where 1 designates the leftmost parameter.
NOTE: The PROCESS_CREATE_ parameters are counted as in TAL (see the
PROCESS_CREATE_ Syntax for TAL Programmers (page 987)) rather than C. Thus,
program-file:length is parameter 1, library-file:length is parameter 2,
and so on; priority is reported as parameter 5 although it is the 9th parameter
in the C calling sequence.
File-system error occurred on user library file; error-detail contains a file-system
error number.
1
4
File-system error occurred on swap file; error-detail contains a file-system error
number.
1
5
File-system error occurred on extended swap file; error-detail contains a
file-system error number.
1
6
File-system error occurred while creating the process file segment (PFS);
error-detail contains a file-system error number.
1
7
Invalid home terminal (device either does not exist or is wrong device type);
error-detail contains a file-system error number.
1
8
I/O error to home terminal; error-detail contains a file-system error number.
1
9
Unable to communicate with system-monitor process; error-detail contains a
file-system error number.
1
10
Process-name error; error-detail contains a file-system error number.
1
File-system
error 44 indicates that, when trying to create a named process, either the DCT is full
or there are no system-generated names available.
11
Invalid program-file format; error-detail subcodes are described in Table 37
(page 1070).
12
Invalid user-library-file format; error-detail subcodes are described in Table 37
(page 1070).
13
The process has one or more references to undefined external procedures, but was
started anyway (this is a warning, accompanied by a message to the home terminal).
14
• For a TNS or non-PIC native program, this warning occurs only when the external
references in the program or user library (UL) file must be “fixed up”: the first time
the object file is loaded after it is created or duplicated, or after a system load,
or if a program’s user library changes (from none to a UL, from a UL to none, or
from one UL object to another). Renaming a program does not affect its fix-up
status.
On a TNS/R system, unresolved procedure references in a TNS or native non-PIC
program are bound to the DEBUG procedure, so an attempt to invoke an
unresolved procedure calls the debugger.
1062 Guardian Procedure Calls (P)