Sybase recommends that you use the Java edition of dbisql, rather than dbisqlc or isql, unless instructed otherwise for specific tasks. Note that although dbisqlc is supported, dbisqlc does not contain all the features of the Java version dbisql.
Do not use the Import option in the dbisql Data menu (or Command | Options | Input Format in dbisqlc). This option is not supported for use with IQ databases. Use the LOAD TABLE statement or the INSERT statement to load data into IQ tables.
If you run dbisql (Interactive SQL Java) with the -q (quiet mode) option, and the data extraction commands (primarily setting the option TEMP_EXTRACT_NAME1 to an output file) are in a command file, you must first set and make permanent the dbisql option “Show multiple result sets.” If you do not set this option, the output file is not created.
To set the “Show multiple result sets” option, click Tools | Options in the dbisql window, choose “SQL Anywhere,” and select the “Results” tab. Then select “Show all results sets.”
Online help is not available for dbisql and dbisqlc. [CR 560925]
The query plan in the dbisql Plan tab is a SQL Anywhere style query plan. For a Sybase IQ query plan, refer to the IQ .iqmsg file.
If you set the terminal type on UNIX and Linux systems to “dumb” or “unknown” and then start dbisqlc, Sybase IQ returns an error. For example:
% setenv TERM dumb % dbisqlc
error at line 1 Unable to initialize screen routines
To avoid problems, run dbisql (Interactive SQL Java) instead, or use an xterm window to run dbisqlc on UNIX and Linux systems. For example, you can start an xterm window with a scroll bar as follows:
% xterm -sb
