HP Guardian Errors Manual page 162

Table 8 Error Subcodes for Process Creation Errors 12, 13, 70, 76, 84, and 3xx (continued)
Subcode Meaning
23 File has entry in TNS/R fixup list with invalid external entry-point (XEP) index value or invalid code
address value.
24 Accelerated file has external procedure identifier list (EPIL), internal procedure identifier list (IPIL), or
external entry-point (XEP) table with incorrect format.
25 UC (user code) or UL (user library) was accelerated using the wrong Accelerator option (UC, UL, SC,
or SL).
26 The file was accelerated with an incompatible version of the Accelerator.
27 The file has an invalid callable gateway (GW) table.
28 The program file contains processor-specific code that cannot be run on the current processor.
29 Fixup of accelerated code was attempted in an object file that was not accelerated.
30 An internal structure of the file contains an error.
31 An internal structure of the file contains an error.
32 An internal structure of the file has an entry point value of 0.
33 An internal structure of the file contains an error.
34 The list of unresolved procedure names contains an error.
35 The fixup computed an invalid file offset to the code area.
36 The file has an invalid fixup item.
37 An internal structure of the file contains an error.
38 The instruction at a call site is not the type expected for its fixup item.
39 Not used.
40 A virtual address specified in an ELF file is outside its allowed range. For example, a text or data segment
is specified at an address not valid for this type of file.
41 Not used.
42 The code area or data area is too large.
43 The file either has a gateway (GW) table but no callable procedures or has gateways that are not in
the (GW) area.
44 The file codes of the program file and library file do not match. (Not used since G06.12; see 5 and 6
instead.)
45 The file being started can run only in the Guardian environment and it is being started in the OSS
environment, or vice versa.
46 Either the TNS program or the TNS User library (but not both) expected the library to contain global
data.
47 Either the TNS program needs to import data from the TNS User library and the library is not exporting
any data, or the library needs global data space and the program is not providing it.
48 A TNS program file uses a TNS shared run-time library and is switching to a new library, but the program
was accelerated by an old version of the Accelerator that does not support library data relocation at
fixup time. Use a version of the Accelerator provided with the D30.00 or later release of the operating
system.
49 A TNS object file has no code space.
50 The native object file is not loadable. Either it is a linkable file (such as unlinked compiler output) or it
is an incorrect type of loadable file (such as a DLL encountered with a non-PIC program.)
162 Process Creation Errors