Guardian Procedure Calls Reference Manual

ZSYSTAL section PROCESS^GETINFOLIST^RETURN with identifiers
ZSYS^VAL^PINF^TYPE^suffix.
DescriptionID suffixValuesCode
Mask to isolate the loadfile type; one of the values 0 through 8, as follows:LTMASK15
Error (for example, no loadfile segment at the specified address)ERROR0
Unaccelerated TNS programTNSUNAXLPRG1
Unaccelerated TNS user libraryTNSUNAXLUL2
Accelerated TNS programTNSAXCLPRG3
Accelerated TNS user libraryTNSAXCLUL4
Non-PIC ELF programNOPICELFPRG5
Non-PIC ELF shared run-time library (SRL)NOPICELFSRL6
PIC ELF programPICELFPRG7
PIC ELF dynamic-link library (DLL)PICELFDLL8
Mask to isolate the next three values:LIBMASK768
Ordinary library (not a public or implicit library)PRIVATELIB256
Public library (one of the set of installed public libraries)PUBLICLIB512
Implicit libraryIMPLIB768
This object is included in OSIMAGEOSIMAGE2048
This library was loaded dynamicallyDYNAMIC4096
This file was loaded in an OSS process, so its name is in OSS formatOSSPROCESS8192
Privilege is not required to debug (set breakpoints in) this fileMAYSETBPT16384
Using the Loadfile Type Code Values
The type code value returned is one of the values 0 through 8 plus other values as appropriate.
Thus, for example, a DLL dynamically loaded into an OSS process would have a type code value
of 28936, broken down as follows:
28936 = 0x7108
= 8 (DLL)
+ 256 (ordinary library)
+ 4096 (dynamically loaded)
+ 8192 (loaded in OSS process)
+ 16384 (OK to debug)
Attribute Codes and Value Representations
Each attribute code is contained in a 16-bit word defined as follows:
contains the attribute indexlow-order 12 bits
contains the length, in 16-bit words, of any auxiliary datahigh-order 4 bits
For attributes with no auxiliary data, the data length is 0.
The individual attribute codes and their associated value representations are shown in Table 34.
The attribute codes are defined symbolically in ZSYSDDL. For example, see section
process_itemcodes in ZSYSC or PROCESS^ITEMCODES in ZSYSTAL. (Comments in these files
see the attribute codes as "item codes".) These files are distributed in an installation subvolume
named ZSYSDEFS.
Except for attributes 125 and 126, all file names that are specified as search parameters are
assumed to be sufficiently qualified and are not resolved against defaults. They are interpreted
PROCESS_GETINFOLIST_ Procedure 1019