DISC

Contents | What's New | Quick Links

 

OACOMP

Introduction

Software Installation

Concepts and Design

Designing Applications

Omnidex Environments

SQL Reference

Omnidex API's

Utilities

Interfaces

Performance Guide

Troubleshooting Guide

Appendix

 

 

Compilation Phase

Validation PhaseUtility Reference

 

When OACOMP compiles an environment catalog source file, it displays the following string on the terminal screen:

Parsed; Validated; Compiling...

When the compile has completed successfully, OACOMP displays the following and returns to an operating system prompt:

Parsed; Validated; Compiled; Done

** Environment Compiled Successfully! **

Parsing Phase

Validation Phase

Compilation Phase

OACOMP

OADECOMP

Utility Reference

 

  • If a compiled environment catalog by that name already exists, OACOMP automatically overwrites the existing file with the new file.
  • If an existing file that is not an environment catalog bears the name you assigned the compiled environment file, OACOMP issues an error during the validation phase.

Parsed; Validating...

[ 40] Object file connect error (ORDERSEC), error=41999, info=0

In the example above, “ORDERSEC”, which was assigned to the compiled environment, conflicts with an existing file that is not an environment catalog and is enclosed in parentheses in the error message.

If the compile operation is successful, the compiled environment catalog is created with the name specified at run time. After compiling, the environment catalog is ready to be installed with OMNIDEX index keys through DBINSTAL and accessed through the OmniAccess routines.

Keep the source files for the environment catalogs. They provide useful information about the data, and are therefore useful in resolving technical support issues. They also serve as a backup, in case something happens to a compiled environment catalog.

 

top

Dynamic Information Systems Corporation - Omnidex Version 3.8 Build 6 J15.03-Copyright © 2003

DISC | Documentation Home