Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
programs:oacomp:overview [2009/11/29 17:48]
tdo
— (current)
Line 1: Line 1:
-====== OACOMP Internal Environment Compiler ====== 
-===== Overview ===== 
  
-OACOMP is an internal console based application that compiles an environment source file into a compiled Omnidex Environment that can then be connected via the Omnidex SQL CONNECT Statement. 
- 
-OACOMP can create either a compiled Omnidex Environment or as of version 5.0, an XML Omnidex Environment. 
- 
-Compiled Omnidex Environments can be directly used by DBINSTAL. ​ However XML Omnidex Environments can only be used by OdxAdmin or maintained using OdxSQL and the Omnidex DDL statements such as CREATE ENVIRONMENT and CREATE TABLE. 
-===== Running OACOMP ===== 
- 
-OACOMP requires a Omnidex Environment Source file.  
- 
-  oacomp [ Options ] Source_Filespec ​ 
-         [ Object_Filespec.env ] | [XML_Filespec.xml ] 
-         [ List_Filespec ] 
- 
-Source File is the uncompiled environment source detailing the database, tables and columns, and other pertinent information used by Omnidex. A .src extension is assumed and will automatically be appended to the end of the supplied file name. 
- 
-Object File is the name of the output file, the compiled environment catalog. If omitted, the output file will be the same as the source file with a .env extension. 
- 
-List File is an optional message file where OACOMP messages will be written. If omitted, messages will be displayed to the console. ​ 
- 
-===== OACOMP Examples ===== 
-== Simple == 
- 
-Compiles orders.src into orders.env 
- 
-  os> oacomp orders 
- 
-Compiles orders.src into orders.env 
- 
-  os> oacomp orders.src orders.env 
- 
-Translates an Environment Source into an Environment XML file. 
- 
- 
- 
-Usage: oacomp [<​Options>​] <Source File> <Object File> [<List File>] 
- 
-    ...where <Source File> contains compiler input source, 
-       ​compiled output is written to <Object File>, and 
-       ​compiler messages are written to optional <List File>, 
-       and <​Options>​ may include any of the following: 
-         -xml 
-         ​-nostats 
- 
-===== OaComp Operation ===== 
- 
-This operation occurs in three phases: 
- 
-  * The parsing phase checks the source file for valid syntax. ​ 
-  * The validation phase checks for unresolved references. ​ 
-  * The compilation phase creates and writes out the physical Environment Catalog. 
- 
-  os> oacomp <Source File> <Object File> [<List File>] 
- 
- 
-  
- 
-===== Running OACOMP ===== 
- 
-Run OACOMP from the command line with the environment source file as an argument. 
- 
-If passing the source file by itself, taking the default output file, do not include the .src suffix. ​ 
- 
-If passing the source file and the output file, include both the .src suffix for the source file and the .env suffix for the output file.  
- 
-<​code>​ 
-C:​\omnidex\demo>​oacomp orders 
-DS73010 2.6.11 OmniAccess Environment Compiler Tue Sep 30 12:35:52 2003 
-(c) Dynamic Information Systems Corp. 1981-2003 
-LICENSEE: DISC Internal Copy 
- 
-Parsed; Validated; Compiled; Done 
-** Environment Compiled Successfully! ** 
- 
-C:​\omnidex\demo>​ 
-</​code>​ 
- 
-You can specify fully qualified the path of the source file as well as the output .env file.  
- 
-<​code>​ 
-C:​\omnidex\demo>​oacomp d:​\test\orders.src d:​\test\env\orders.env 
-DS73010 2.6.11 OmniAccess Environment Compiler Tue Sep 30 12:35:52 2003 
-(c) Dynamic Information Systems Corp. 1981-2003 
-LICENSEE: DISC Internal Copy 
- 
-Parsed; Validated; Compiled; Done 
-** Environment Compiled Successfully! ** 
- 
-C:​\omnidex\demo>​ 
-</​code>​ 
 
Back to top
programs/oacomp/overview.1259516929.txt.gz ยท Last modified: 2012/10/26 14:25 (external edit)