SQL Programming Manual for TAL
Program Compilation and Execution
HP NonStop SQL Programming Manual for TAL—527887-001
5-4
Using the Binder Program
named ZZBI nnnn on your default subvolume (nnnn is a 4-digit number determined
by the system).
directive
is a TAL compiler directive as described in this manual or in the TAL Reference
Manual.
You must include the SQL directive either in the command line or at the beginning
of the primary source file. Other TAL compiler directives are optional. For more
information on the description of the SQL directive, see Section 3, NonStop SQL
Statements and Directives.
In this example, the TAL compiler compiles the source file PARTSRC, writes the listing
to the spooler location $S.#PARTLST, and writes the object file to the disk file
PARTOBJ on your default subvolume.
TAL /IN partsrc, OUT $s.#partlst, NOWAIT / partobj; SQL
For more information about TAL compiler options, see the TAL Reference Manual.
Using the Binder Program
The Binder program allows you to read, link, modify, and build executable object files
for SQL and TAL object files (as well as C, COBOL85, and Pascal object files). Follow
these guidelines when you bind SQL object files:
•
Consider SQL object files to be like other object files.
•
Bind object files after they are compiled by either the TAL or the SQL compiler.
•
Binding invalidates a previously SQL validated object file (which is the result of a
successful explicit SQL compilation). You must explicitly SQL compile the file again
to revalidate it.
Including the TALLIB Run-Time Library
Before you can compile an object file using the SQL compiler, the TALLIB run-time
library must be bound with the object file. The TALLIB library should be installed on the
same subvolume as the TAL compiler. Specify the TALLIB library file either during the
TAL compilation using a SEARCH directive or after compilation using the Binder
program.
Caution. Do not use the Binder STRIP command on object files that contain embedded SQL
statements. The STRIP command removes the Binder and INSPECT tables from the object
file. Without the Binder table, the SQL compiler cannot compile the program and the SQL
executor cannot execute the program.