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

 

 

Validation Phase

Parsing PhaseCompilation Phase

 

If your catalog source file is free of syntax errors, OACOMP validates the entities (DATABASEs, TABLEs and so on) to be sure that all references are logically consistent. As it validates the catalog, OACOMP displays the string Parsed; Validating... on your terminal screen.

When a declared entity has no definition within the catalog, OACOMP returns an error message, like the one below, before aborting.

Parsing Phase

Validation Phase

Compilation Phase

OACOMP

OADECOMP

Utility Reference

[Parsed; Validating...

[ 10008] Match not found (Column-Spec)

>CUSTOMER_NUM<; Env=ORDERSEC; DB=ORDERS; Tbl=CUSTOMERS;

Clause=PARENT

%% Compilation ABORTED after 1 Validation error(s)! %%

In all validation error messages, OACOMP displays the declaration where the mismatch occurs.

On the line below the error message, OACOMP displays the mismatched value inside angle brackets (>CUSTOMER_NUM<, in the example above), and tells where the mismatch occurs. In the example above, this is in the ENVIRONMENT statement for ORDERSEC, the DATABASE statement for ORDERS, the TABLE statement for CUSTOMERS, and in the PARENT clause.

The key, CUSTOMER_NUM, declared for the table CUSTOMERS is not defined for that table in a COLUMN statement.

OACOMP does not validate the accuracy of external references to existing data structures. It validates for cross references within the environment catalog.

If the validation phase of the compile completes successfully, OACOMP compiles the environment source file.

 

top

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

DISC | Documentation Home