Object Code Accelerator Manual

Using OCA
Object Code Accelerator Manual—528144-003
4-4
Using Obey Files
OCA outputs an accelerated object file that does not have the same file label as the
input TNS object file. The file label contains the PROGID attribute that determines the
ownership of an executing process for NonStop SQL/MP. OCA turns off the PROGID
attribute of the accelerated object file. To set the PROGID value, use the SQL ALTER
PROGRAM statement or the Safeguard security subsystem interface. Refer to the
NonStop SQL/MP Reference Manual or the Safeguard Reference Manual for details.
Using Obey Files
In the Guardian environment, you can provide OCA options on the OCA command line
itself, in a text file whose name is given as a command-line option, or both.
The text file is referred to as an obey file. An obey file can include any option that can
be given on the command line, including other obey file invocations. Any number of
obey files may be invoked within an OCA command.
You specify an obey file as a run-option within the slashes that optionally follow the
keyword oca, as in this example:
oca /in fred/ input-file, output_file output-file
or in the oca-options -list part of the command, following the semicolon:
oca input-file, output_file output-file, obey fred
OCA resolves partially qualified pathnames using the current working directory.
Obey files can contain any number of OCA options. The list of options can be as long
as you like, with any number of comma-separated options on each line. Options that
take an indefinite number of arguments can be followed by a blank-separated list of
such arguments. Each option, together with all its arguments, must appear in its
entirety on a single line, and not be continued onto a following line. See Specifying an
Obey File on page 5-4 for more information.
Comments
You can use comments in obey files to annotate the commands you specify to OCA.
(You cannot use comments on the OCA command line.) A comment can be on any
line. This obey file also directs OCA to read more options from the obey file
MOREOPTS.
Example
•
The following example displays the contents of an obey file:
-- obey file fred
inheritscc MYPROC
obey moreopts -- get more options from file moreopts