SQL Programming Manual for Pascal

Program Compilation and Execution
HP NonStop SQL Programming Manual for Pascal—528614-001
5-5
Running the Accelerator
Binder and issue the Binder command described here. For more information on using
Binder with Pascal, see the Pascal Reference Manual.
The command to invoke Binder is:
command-file
specifies a file that contains Binder commands.
list-file
specifies the file to receive output listings.
run-options
are the RUN command options documented in the TACL Reference Manual.
You can put the Binder commands in a command file or you can enter them
interactively. (If you enter the commands interactively, you must type EXIT or CTRL/Y
after the BIND session to return to the command interpreter.)
Follow these guidelines when you bind SQL program files:
•
Consider SQL program files to be like other object files.
•
Bind object files after they are compiled by either the Pascal or the SQL compiler.
•
Binding invalidates a previously SQL validated program file (which is the result of a
successful explicit SQL compilation). You must explicitly SQL compile the program
file again to revalidate it.
To run the resulting program file, you must meet the following conditions:
•
Each SQL-Pascal module bound together with a program must have a unique
module name.
•
After the program file is produced by the bind operation, the program file should be
explicitly SQL compiled.
For information about the Binder, see the Binder Manual.
Running the Accelerator
If your object file will run on a TNS/R system, you can run the Accelerator to optimize
the object code. Because the Accelerator invalidates SQL object files, you must run it
BIND [ / [ IN command-file ] [, OUT list-file ] / ]
[, run-options ... ] / ]
Caution. Do not use the Binder command STRIP on any object files that contain embedded
SQL. 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 an error occurs.