pTAL Reference Manual (H06.03+)

Compiler Directives
HP pTAL Reference Manual—523746-005
17-3
File Names as Compiler Directive Arguments
Rules for directive lines:
•
Begin each directive line by specifying ? in column 1. (? is not part of the directive
name.)
•
Place the name of the directive and its arguments on the same line unless the
directive description says you can use continuation lines.
•
Do not put extra characters (such as semicolons) at the end of a directive line.
•
Do not use an equal sign (=) in the directive unless the directive’s syntax includes
one (as in ASSERTION on page 17-18).
Rules for continuation lines:
•
Begin each continuation line by specifying ? in column 1.
?NOLIST, SYMBOLS, NOMAP, GMAP
?INNERLIST
•
Place the opening parenthesis of the argument list on the same line as the
directive name.
?NOLIST, SOURCE $SYSTEM.SYSTEM.EXTDECS (
? process_getinfo_,
? process_stop_)
File Names as Compiler Directive Arguments
The following directives accept Disk File Names on page B-1, DEFINE names, and
ASSIGN names as arguments:
•
ERRORFILE on page 17-28
•
SAVEGLOBALS on page 17-54 (not recommended)
•
SOURCE on page 17-58
•
USEGLOBALS on page 17-67 (not recommended)
A DEFINE name or an ASSIGN name is considered a logical file name (see Logical
File Names on page B-4). The directives listed above accept a logical file name in
place of a file name.
You can specify partial file names. If you specify a partial file name, the compiler uses
default values as described in Partial File Names on page B-3.
For the USEGLOBALS directive (not recommended) and the SOURCE and directive,
the compiler can use the node (system), volume, and subvolume specified in ASSIGN
SSV commands, as in Example 17-3 on page 17-7.
Note. This topic applies only to Guardian platforms, not Windows platforms.