TAL Reference Manual

Compiler Directives
TAL Reference Manual—526371-001
16-74
Usage Considerations
Usage Considerations
SAVEABEND and NOSAVEABEND can appear in the compilation command or
anywhere in the source program. The compiler uses the last specification when it
builds the object file.
SAVEABEND requests a save file and sets the INSPECT directive on; at run time the
Inspect product must be available on the system that runs the process.
NOSAVEABEND suppresses the save file but does not affect the INSPECT directive
setting.
After compilation, you can specify the SAVEABEND option by using Binder or TACL
RUN options.
Save File
The save file contains data-area and file-status information at the time of process
failure. You can examine the save file by using Inspect commands. The Inspect
product assigns the save file a name of the form ZZSA
nnnn, where nnnn is an integer.
The defaults for volume and subvolume are the object file’s volume and subvolume.
(You can specify a name for the save file by using the Inspect product.) For more
information, see the
Inspect Manual.
Example of SAVEABEND Directive
This example generates a save file for the object file if execution terminates abnormally
in procedure A:
?SAVEABEND !Set Inspect product; generate save file
PROC a;
BEGIN
!Lots of code
END;
?NOSAVEABEND !Suppress save file
PROC b;
BEGIN
!Lots of code
END; !INSPECT and NOSAVEABEND still in effect
VST1651.vsd
NOSAVEABEND
SAVEABEND