  Step 
        4 - Environment Catalog
      This section describes the Omnidex 
        Environment Catalog in detail, including syntax, some special design 
        options to add more functionality to an installation, and variations based 
        on the underlying database. This section also describes the Omnidex utilities 
        OAHELPER, OACOMP, and OADECOMP, which can be used to automatically generate, 
        compile, and decompile an Omnidex Environment Catalog. 
      The Omnidex Environment Catalog is Omnidex’s view of the structure 
        of a data base and sets default operating values for Omnidex’s run-time 
        characteristics. The Omnidex Environment Catalog is a necessary and central 
        component of using Omnidex. 
      In an open systems environment, where a variety of operating systems 
        support a variety of data management systems, the environment catalog 
        provides a standard means of describing your data to OmniAccess applications, 
        including DBINSTAL and DATADEX. It is used to coordinate Omnidex with 
        the underlying database file layout by explicitly defining the database's 
        tables and columns to the Omnidex software. 
      The Environment Catalog source files are created using any system text 
        editor. Alternatively, for Oracle, Sybase, Informix, and TurboImage, the 
        Environment Catalogs can be automatically generated through the Omnidex 
        utility OAHELPER. 
      The Omnidex utility OACOMP is used to compile the Environment source 
        file into the Environment object file, also called the compiled Environment 
        Catalog file. If the original Environment source file is needed but unavailable, 
        the Omnidex utility OADECOMP will create a separate Environment source 
        file from an existing compiled Environment file. 
        
      OAHELPER
      OAHELPER is used to 
        generate an initial prototype of an Omnidex 
        Environment Catalog Source against a target data base. A text editor 
        is then used to manually manipulate the generated source code to add desired 
        characteristics. OAHELPER works against any supported data base that contains 
        an internal schema such as Oracle, Sybase, Informix, TurboImage or an 
        ODBC accessible data base. 
      OAHELPER does not work against file structures such as POSIX flat files 
        or VMS RMS files that do not support an internal data schema. 
      You can also use a text editor to manually create a source file. 
      OADECOMP can also be 
        used to decompile an existing environment catalog into an editable source 
        file. 
        
      OACOMP
      OACOMP compiles the environment 
        source file into the binary format, the Omnidex 
        Environment Catalog. 
        
      Top  
	   |