HP 3000 Manuals HP 3000 Manuals
OCA Operation
OCA is a tool designed to aid in migrating applications from an MPE
V/E-based system to an MPE/iX-based system. OCA is a dialog-driven
program that scans specified MPE V/E program and SL files in either batch
or interactive mode and generates either brief or detailed reports of
both definite and potential problem areas that may be encountered when
migrating an application to an MPE/iX-based system. OCA allows you to
specify the following options prior to entering the scanning portion of
the program:
* The Scan User Externals option enables you to add your own list of
incompatible procedures to OCA's set of predefined system
incompatibilities. This list can include either system entry
points or user-written procedures which are called as externals of
a program or SL being scanned.
* The Build Indirect File option enables you to construct indirect
files (files that contain file specifications, including other
indirect file names) from generic file sets.
These two options can be used only one time per execution of OCA. Thus,
one set of options remains in effect for all program or SL files scanned.
If only default values are desired, the first part can be skipped, and
OCA proceeds to the scanning part of the program.
During the scanning portion of the program, you direct OCA to scan MPE
V/E program and SL files and report both definite and potential problem
areas that may be encountered when migrating an application to an
MPE/iX-based system. The scanning portion of the program can be repeated
until all specified program and/or SL files are scanned.
OCA outputs a report of incompatibilities in either a brief report format
or a detailed report format. The brief report format (the default)
includes names of externally referenced procedures that have been
identified as incompatibilities for the purposes of migration. Use the
brief report format if you are interested primarily in a migration
report. Appendix D, "Incompatibilities", gives greater detail on each of
the incompatibilities detected by OCA, as well as corrective actions to
take.
When you specify a detailed report format, OCA reports on all of the
program file's externally referenced procedures, as well as general
information about the program's structure. Thus, the detailed report
creation may take much longer to produce than the brief report, and the
output volume is much greater.
During the scanning portion of the program, OCA opens each file you
specify and determines if it is an SL file or a program file. If the
file is a program file, OCA satisfies the program's external references
before proceeding. If the file is an SL file, OCA does not satisfy
external references. For either type of file, OCA compares the procedure
names against OCA's predefined set of incompatible system procedures. If
a detailed report is specified, then OCA reads every record of the file
and determines the locations of the procedure call (PCAL) instructions to
incompatible procedures.
NOTE In extremely rare cases, OCA cannot distinguish between a valid
PCAL and a piece of data that resembles a PCAL. Some PCALs,
therefore, might be detected and reported as incompatibilities
erroneously.