Object Code Accelerator Manual

Object Code Accelerator Manual—528144-003
5-1
5 OCA Syntax and Option
Summary
This section provides detailed information about using OCA on the command line and
how you can use additional options to specify more advanced translation functions.
•
OCA Syntax on page 5-1 describes how to run OCA from the command line.
•
OCA Options on page 5-2 details and provides examples for using options that can
be placed in the [, oca-option-list] portion of the command line. Using additional
oca options is not required.
OCA Syntax
To run OCA from the command line, use the following syntax model:
run-options
is one or more standard run-time options, as described in the TACL Reference
Manual. The most useful option for the oca command is:
•
OUT file-name, to specify to which file OCA is to write its listing. If no file is
entered, the listing is written to the specified hometerm.
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
translate. The file must be fully bound, runnable, and of file code type 100 or 180.
The input file may have been previously accelerated; OCA ignores the TNS/R
region of the TNS object file if one exists.
If you do not enter a OUTPUT_FILE name, OCA augments the input file with a
new region that contains TNS/E instructions provided the existing file is secured so
that the OCA invoker has permission to replace the existing file. When OCA
augments an existing input file with TNS/E instructions, it updates the file’s
timestamp. If OCA cannot augment an existing file, it tries to create a second file in
the same subvolume with a name in the form “ZZZZnnnn” where n is a placeholder
for a number. OCA displays this file in the listing if it needs to create this second
file.
oca [/ run-options/] input-file [, oca-option-list]