This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
programs:odxsql:commandline [2009/11/30 03:59] tdo |
programs:odxsql:commandline [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| - | ====== OdxSQL Command Line Options ====== | ||
| + | ====== OdxSQL Command Line Options ====== | ||
| + | {{page>:odxsql_bar&nofooter&noeditbtn}} | ||
| OdxSQL can accept the Omnidex Environment as well as several other options. | OdxSQL can accept the Omnidex Environment as well as several other options. | ||
| Line 16: | Line 16: | ||
| 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. | 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. | ||
| - | - | ||
| - | ===== Other Options ====== | + | ===== Other Command Line Options ====== |
| + | |||
| + | Command line options can be specified in either upper or lower case. | ||
| + | |||
| + | The following is a lits of available command line options for OdxSQL. | ||
| ^ Option ^ Option Description ^ | ^ Option ^ Option Description ^ | ||
| - | | Omnidex_Environment_filespec | Omnidex Environment | | + | | Omnidex_Environment_Filespec | Omnidex Environment Filespec used by OdxSQL to automatically connect. | |
| | -help %%|%% -? | Display the list cf command line options | | | -help %%|%% -? | Display the list cf command line options | | ||
| - | | -version | Program version | | + | | -version | Display the OdxSQL Program version. | |
| - | | -use=filespec | Execute statements in named file | | + | | -use=filespec | Execute statements in the named filespec. | |
| - | | -cmd='cmd1;cmd2' | Execute specified OdxSQl commands | | + | | -cmd='cmd1;cmd2' | Execute specified OdxSQl commands. | |
| - | | -where='criteria' | Apply criteria to use statement | | + | | -where='criteria' | Apply criteria to use statement. | |
| - | | -exit | Exit after completion of use file | | + | | -exit | Exit after completion of processing the commands in the Use File. | |
| - | | -exit_on_error | Exit if an error occurs | | + | | -exit_on_error | Exit if an error occurs. | |
| - | | -nobanner | Do not print banner | | + | | -nobanner | Suppress the display the OdxSQL banner. | |
| - | | -cloa | Run OdxSQL using the CLOA client interface | | + | | -cloa | Run OdxSQL using the CLOA client interface. | |
| - | | -odbc | Run ODXsql using the ODBC client interface | | + | | -odbc | Run OdxSQL using the ODBC client interface. | |
| - | | -jdbc | Run ODXsql using the JDBC client interface | | + | | -jdbc | Run OdxSQL using the JDBC client interface. | |
| - | | -odxnet[=port] | Launch an OdxNet listener for this session | | + | | -odxnet[=port] | Launch an OdxNet listener for this OdxSQL session. | |
| == -? or -help == | == -? or -help == | ||
| Line 70: | Line 74: | ||
| 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 -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. | ||
| + | |||
| + | == -version == | ||
| + | |||
| + | The -version option will display the OdxSQL version. Because OdxSQL displays the Omnidex version in the OdxSQL banner and the OdxSQL command displays Omnidex detailed information, use the -version option to verify the particular version of OdxSQL. | ||
| + | |||
| + | == -exit == | ||
| + | |||
| + | Exit after completion of processing the commands in the Use File. This option is typically used in creating operating system batch processing scripts so that OdxSQL automatically terminates. | ||
| + | |||
| + | == -exit_on_error == | ||
| + | |||
| + | Exit if an error occurs. | ||
| + | |||
| + | OdxSQL will normally continue processing OdxSQL commands from a Use file even when a command or syntax error occurs. Seeting the -exit_on_error option will cause OdxSQL to terminate when an error is encountered. | ||
| + | |||
| + | == -nobanner == | ||
| + | |||
| + | Suppress the display the OdxSQL banner. | ||
| + | |||
| + | ==-cloa == | ||
| + | Run OdxSQL using the CLOA client interface. | ||
| + | |||
| + | This option allows the testing of the OmniAccess CLOA API. Although DISC recommends that new applications are developed using the Omnidex ODBC or JDBC drivers, the CLOA API is supported for backward compatibility. When using the CLOA option, the OdxSQL Connect command connects to an Omnidex Client DataSource created with the DSEDIT Windows Client program. | ||
| + | |||
| + | == -odbc == | ||
| + | |||
| + | The ODBC option directs OdxSQL to use ODBC calls to connect and interact with SQL statements. | ||
| + | |||
| + | This option allows OdxSQL to test ODBC Connections. | ||
| + | |||
| + | When using this option, the OdxSQL Connect command is used to connect to an ODBC Datasource. | ||
| + | |||
| + | == -jdbc == | ||
| + | |||
| + | The JDBC option directs OdxSQL to use JDBC calls to connect and interact with SQL statements. | ||
| + | |||
| + | This option allows OdxSQL to test JDBC Connections. | ||
| + | |||
| + | When using this option, the OdxSQL Connect command is used to connect to a JDBC Datasource. | ||
| ===== Examples ===== | ===== Examples ===== | ||