C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

You can set the SAVEABEND object-file attribute after compilation using the Binder SET command
(for TNS programs) or a linker utility (for native programs).
For this option to be effective at run time, the symbolic debugger must be available on the
system on which the process runs.
The INSPECT and SAVEABEND pragmas are related:
If you specify NOINSPECT, the compiler automatically disables SAVEABEND (as though
you had explicitly specified NOSAVEABEND).
If you specify SAVEABEND, the compiler automatically enables the symbolic debuggers
(as though you had explicitly specified INSPECT).
The save file contains data area and file-status information at the time of failure. You can
examine the save file during a symbolic debugger session. The symbolic debugger assigns
the save file a name of the form ZZSAnnnn, where nnnn is an integer. The default names for
volume and subvolume are the object file's volume and subvolume. (You can specify a name
for the save file using the symbolic debugger.) For information on the save file, see the:
Inspect Manual
Native Inspect Manual
SEARCH
For TNS programs, the SEARCH pragma directs the Binder to search a given object file when
attempting to resolve external references in a program compiled with the RUNNABLE pragma.
For native programs compiled with the RUNNABLE pragma, the SEARCH pragma directs the nld
utility (for conventional code) or the eld or ld utility (for PIC code) to link in the entire given object
file (not just the procedure that contains the external reference). For more details, see the:
eld Manual
ld Manual
nld Manual
SEARCH "object-file"
object-file
specifies the name of the object file to be searched.
The pragma default settings are:
SYSTYPE OSSSYSTYPE GUARDIAN
Not set.Not setTNS C compiler
N.A.N.A.G-series TNS c89 utility
Not setNot setTNS/R native C and C++ compilers
N.A.N.A.Native c89 and c99 utilities
Not setNot setTNS/E native C and C++ compilers
236 Compiler Pragmas