This is an old revision of the document!
OdxSQL can accept the Omnidex Environment Filespec to automically connect as well as several other options.
odxsql [Omnidex_Environment_Filespec] [options]
If specified, OdxSQL will automatically attempt to connect to the Omnidex Environment Filespec. If the Omnidex Environment Filespec is not passed as a program argument, then a CONNECT statement must be performed to establish a connection to the Omnidex Environment.
Omnidex_Environment_filespec | Omnidex Environment |
-help | -? | Help |
-version | Program version |
-use=filespec | Execute statements in named file |
-cmd='cmd1;cmd2' | Execute specified OdxSQl commands |
-where='criteria' | Apply criteria to use statement |
-exit | Exit after completion of use file |
-exit_on_error | Exit if an error occurs |
-nobanner | Do not print banner |
-cloa | Run odxsql using the CLOA client interface |
-odbc | Run odxsql using the ODBC client interface |
-jdbc | Run odxsql using the JDBC client interface |
-odxnet[=port] | Launch an OdxNet listener for this session |
The -use=use_file parameter instructs OdxSql to process all the commands contained within the specified use file. The right hand side of the parameter, use_file, is the filespec of the file containing the commands.
The following is a display of the -? option that displays a list of available options.
Options: -help | -? Help -version Program version -use=filename Execute statements in named file -cmd='cmd1;cmd2' Execute specified statements -where='criteria' Apply criteria to use statement -exit Exit after completion of use file -exit_on_error Exit if an error occurs -nobanner Do not print banner -cloa Run odxsql using the CLOA client interface -odbc Run odxsql using the ODBC client interface -jdbc Run odxsql using the JDBC client interface -odxnet[=port] Launch an OdxNet listener for this session
os> odxsql
Use the OdxSQL CONNECT command to connect to an Omnidex Evironment from within OdxSQL.
os> odxsql myenv.xml
os> odxsql -use=commands.txt