Inspect Manual

Inspect Concepts
Inspect Manual—429164-006
2-5
Save Files
Inspect enables you to debug processes started from program files whose object code
was compiled from C, COBOL, COBOL85, FORTRAN, Pascal, or TAL source code.
With Inspect, you can also debug processes started from program files whose object
code was produced from one or more object files (compiled from any of these
languages) either by the BINDER utility or by a native linker such as nld (on TNS/R
systems), ld (for Position-Independent Code on TNS/R systems), or eld (on TNS/E
systems).
Inspect allocates heap during debugging a process (that is, setting a breakpoint,
resuming, displaying a variable and for various other Inspect debugging commands).
The limit for this heap for Inspect is 127.5 MB. If this limit exceeds, Inspect terminates.
Inspect also supports the debugging of TNS processes, in addition to emulated TNS
processes on TNS/R and TNS/E systems. An emulated TNS process is a TNS process
whose object file has been processed by the Axcel accelerator (on a TNS/R system) or
by OCA (on a TNS/E system) to optimize the process for the native system. For more
information about using Inspect on a TNS/E system, see Section 18, Using Inspect on
a TNS/E System.
Many of the high-level Inspect commands permit you to refer to items using the names
or identifiers you gave them in your source code. To take full advantage of these
commands, you should ensure that your program file includes symbol information.
Consequently, you must include the SYMBOLS compiler directive in the source code
or on the command line when you compile the source code.
Save Files
Save files are “snapshots” or “images” of a process or PATHWAY server stored on
disk. If a process or PATHWAY server terminates abnormally (abends) and its
SAVEABEND attribute is set, DMON creates a save file just before termination. You
can direct DMON to create a save file using the Inspect SAVE command.
A save file contains information regarding the state of the process or PATHWAY server
at the moment the image was created. This information includes:

The user data space (including extended data segments)

The values of machine registers

The names and status of any files opened by the process or PATHWAY server

Information about the programs execution environment.
Save files contain additional information about the TNS/R execution environment. This
includes an indication of whether the program has been accelerated and the current
instruction set that is being executed. For accelerated and TNS/R native programs, it
also stores TNS/R machine registers.