Inspect Manual

Debugging Processes and Save Files
Inspect Manual—429164-006
4-14
Examining Save Files
RESUME
SAVE
SELECT DEBUGGER DEBUG
STEP
If you attempt to use one of these commands, Inspect displays the message:
The TYPE clause of the DISPLAY command may yield different results for a save file
than for the equivalent running process. These types rely on dynamic information that
may have changed since the save file was created:

PROCESS HANDLE

SSID

TRANSID
These types may be affected if the save file is moved to another node on the network:

USERID

USERNAME
These types are affected if the save file is removed from one network to another:

CRTPID

DEVICE

FILENAME

FILENAME32

SYSTEM
Type TIMESTAMP will use the daylight saving time table and Greenwich Mean Time
offset of the current node to format and display the local civil time.
You can transport save files between systems for examining problems. It may be
necessary to point Inspect at the object file(s) for the process. This can be done using
the CODE and LIB clauses of the ADD PROGRAM command. It may also be
necessary to point to the locations of source files, which is described in the SOURCE
ASSIGN command portion of Section 6, High-Level Inspect Commands
.
When transporting save files to systems running different releases of Inspect, it may be
necessary to transport the Inspect component of the Inspect sub-system for use in
examining the save file if the installed version of Inspect does not recognize the
version of the save file. When this is done, the Inspect can only be used for the
purpose of examining save files.
When you are finished examining a save file, you use the STOP command to notify
Inspect that you are done with the save file.
** Inspect error 21 ** Invalid operation on a saved program