Object Code Accelerator Manual

Using OCA
Object Code Accelerator Manual—528144-003
4-2
Invoking OCA
6. Perform final testing on the accelerated program.
This is a quick and simple strategy for using OCA. The following table guides you to
the appropriate sections to learn how to perform more advanced OCA tasks.
Invoking OCA
OCA runs as a Guardian process in the Guardian environment. You can invoke OCA
explicitly on D40 series and later releases using TNS/R and TNS/E NonStop servers.
When you invoke OCA from the command line it takes the name of a type-100 TNS
object file as an argument. You can specify one or more OCA options on the command
line, but these are optional. See OCA Options on page 5-2 for a listing and description
of all OCA options. Once OCA translates a TNS object file, you can execute the
accelerated type -100 file on an TNS/E system where it immediately executes at full
speed.
The oca command invokes OCA from the Guardian environment.
run-options
is zero or more standard run-time options, as described in the TACL Reference
Manual. Each option keyword, along with any accompanying arguments, must be
separated by a comma from the next.
input-file
is the name of the file containing the TNS object program that the OCA is to
process.
oca-option-list
is zero or more OCA options. See Section 5, OCA Syntax and Option Summary for
a detailed description of each option. Each option keyword, along with any
accompanying arguments, must be separated by a comma from the next keyword.
Partially qualified pathnames are resolved using the current working directory. If you
run the OCA using the gtacl command, pathnames must be fully qualified. See
To: Refer to:
Make it more convenient to
accelerate a program
Using Obey Files
on page 4-4
Accelerate a program with
embedded SQL statements
Accelerating Programs With Embedded SQL
on
page 4-3
Accelerate code that runs in
user library, system code, or
system library space
Specifying the Code Space
on page 4-3
oca [/ run-options/] input-file, [, oca-option-list]