pTAL Reference Manual (G06.24+, H06.09+, J06.03+)

?
indicates a directive line, and can appear only in column 1.
directive
is a directive listed in Table 74 (page 377) or Table 75 (page 379), except OPTIMIZEFILE, which
can appear only in the command line (see Compilation Command (page 367)).
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 (page 381)).
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
NOTE: This topic applies only to Guardian platforms, not Windows platforms.
The following directives accept Disk File Names (page 518), DEFINE names, and ASSIGN names
as arguments:
• ERRORFILE (page 391)
• SAVEGLOBALS (page 413) (not recommended)
• SOURCE (page 416)
• USEGLOBALS (page 423) (not recommended)
A DEFINE name or an ASSIGN name is considered a logical file name (see Logical File Names
(page 520)). 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 (page 519).
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 328 (page 372).
368 Compiler Directives