Environment variables and shell commands can be used in many locations in the Omnidex product. In most cases, environment variables and shell commands can be used whenever a filename can be referenced in the Omnidex product. Environment variables and shell commands can also be used in CREATE statements that generate Omnidex Environment Files. The following is a list of common uses for environment variables and shell commands within the product:
Connection strings are used in many places within the Omnidex product. Environment variables and shell commands can be use in each portion of the connection string. Consult the documentation on Connection Strings.
Environment variables and shell commands can be used in the PHYSICAL clause to affect the service name for Oracle, and to affect the FILEDSN for SQL Server and ODBC (including MySQL).
Environment variables and shell commands can be used for the USER, PASSWORD and VERSION for all relational databases.
Environment variables and shell commands can be used for the INDEX_DIRECTORY for all databases.
Environment variables and shell commands can be used for PHYSICAL clause on Raw Data Files.
Environment variables and shell commands can be used for target filename for the EXPORT statement.
Environment variables and shell commands can be used for Omnidex Standalone Table filenames in the ATTACH statement.
Environment variables and shell commands can be used for the log directory named in the LOG_DIR option of the UPDATE INDEXES statement.
Environment variables and shell commands can be used in the filename parameter of the $RETRIEVE_FILE SQL function.
See also: