SAVE
Creates a section file -- a binary file containing all currently defined
procedures, variables, and key definitions.
Syntax
SAVE (filespec [,"NO_DEBUG_NAMES"] [",NO_PROCEDURE_NAMES"]
[",IDENT", string] )
Parameters
filespec Specifies the section file you want to create. If
you supply only the file name, DECTPU uses the
current (default) device and your current, default
directory. The default file type is .TPU$SECTION.
"NO_DEBUG_NAMES" Prevents DECTPU from writing procedure parameter
names or local variable names to the section file.
This reduces the size of the file, but should be
used only if you do not plan to debug the section
file.
"NO_PROCEDURE_NAMES" Prevents DECTPU from writing procedure names to
the section file. This reduces the size of the
file, but should be used only if you do not plan
to use the application created by the section file
with the TRACEBACK or LINE_NUMBER functions set to
ON.
"IDENT" Directs DECTPU to associate an identifying string
(such as a version identifier) with the section
file.
string Specifies the identifying string to be associated
with the section file.
Comments
Section files contain the following in binary form:
o All compiled procedures
o Names of all variables created (but NOT their contents)
o All key definitions binding a statement, procedure, program, or a learn
sequence to a key -- including comments added to the key definitions
The default section file is SYS$SHARE:EVE$SECTION.TPU$SECTION, for the EVE
editor. (See help on EVE.)
To invoke DECTPU with your section file, use the following DCL command:
$ EDIT/TPU/SECTION=disk:[directory]file
Use a complete file specification, including the disk (or device) and
directory; otherwise, DECTPU assumes the section file is in SYS$SHARE.
Alternatively, define the logical name TPU$SECTION to specify your section
file. This is useful if you want to use that section file for all or most
sessions. For more information, see DCL HELP on EDIT/TPU/SECTION.
Example
SAVE ("mysection");
Creates a section file called MYSECTION.TPU$SECTION in your your current,
default directory. The section file contains in binary form your compiled
procedures, key definitions, and variables -- including any already saved
in the section file you are currently using.