Object Code Accelerator Manual

Object Code Accelerator Manual—528144-003
4-1
4 Using OCA
The OCA program processes TNS object code programs and produces accelerated
object code programs. You can run OCA only from the Guardian environment; OCA
does not support the Open System Services (OSS) environment. This section
describes:
•
A Strategy for Using OCA on page 4-1 describes a strategy for using OCA.
•
Invoking OCA on page 4-2 describes how to run OCA from the Guardian
environment.
•
Specifying the Code Space on page 4-3 describes the OCA options that affect the
code space in which a program runs.
•
Accelerating Programs With Embedded SQL on page 4-3 explains how to
accelerate user libraries and programs that contain embedded NonStop SQL/MP
or SQL/MX statements.
•
Using Obey Files on page 4-4 explains how to use obey files with OCA.
•
OCA Listings on page 4-6 describes OCA listings.
•
Online Help on page 4-5 describes the OCA online help facility.
A Strategy for Using OCA
This basic strategy shows you how to accelerate a program that runs in user code
space, does not contain embedded SQL statements, and does not contain TAL CODE
statements. This strategy uses the default OCA option settings. The option settings
provide the OCA with additional information about the program to be accelerated. For
the vast majority of programs, the default settings for these options result in a correctly
accelerated program. Either the options are concerned only with performance, or they
can be set to the “wrong” value safely; that is, their misuse is detected and reported by
the OCA, and can be corrected by setting the option and re-running OCA.
1. Make sure that your program does not contain any of the variances described in
Section 3, Preparing Programs for Acceleration or Section 2, Preparing Your
Program for TNS/E Systems of this manual.
2. Compile and bind your TNS object program. For optimum results, retain both the
Binder and Inspect symbols regions.
3. Debug the TNS version of your complete program.
4. Run OCA. If OCA issues an error message, it does not produce an output file.
Correct the error and re-run OCA.
5. Examine the OCA listing. If there are any warning messages, investigate each
warning, and fix it if necessary. OCA issues warning messages to call your
attention to possible problems. Refer to Section 8, Error and Warning Messages
for cause, effect, and recovery information about warning messages.