Sybernet / ISQL
Release 3.00
Mar 12, 2005

ISQL

This UNIX application can be used in lieu of Sybase's isql. You might want to use this instead if you are executing stored procedures written for Sybernet.

Sybase's isql requires you to enter a password. ISQL doesn't require a password. Known passwords are stored encrypted in the .SQLPlusPasswords file. If the password is not known, you will be prompted for this password before connection can take place.

Command Line Arguments

The following command line arguments can be entered in any order except for [logon] which must be the last thing specified:

Option	Description
-SILENT	This option tells ISQL to run in silent mode. It inhibits (among other things) gratuitous output such as the SQL prompt. If you are interested in only the output from Sybase, -SILENT should be specified.
-VERBOSE	This option is used for internal purposes only and causes ISQL to generate extra debugging information.
-MAXPIPESIZE	This option is ignored.
-DEPTH	This option followed by a number determines how many input lines will be remembered by ISQL.
-INPUTFILE	This option followed by a valid filename allows you to specify the input file to ISQL.
-OUTPUTFILE	This option followed by a valid filename allows you to specify the output file that ISQL will write its results. Normally, you would also specify -SILENT when using this options.
-NLS_DATE_FORMAT	This option allows you to set the default date format.
[logon]	This option allows you to specify the connect string on the command line. If specified, the logon option uses this syntax: username[/password][@connect_identifier] If you omit the password, you will be prompted for its value. If you omit the connect_identifier, the default instance is used.

Example

The following example illustrates how to connect to DEVPAY as user DELTEK. Notice that no password is required:

isql deltek@oradev

Connected to devpay as deltek from 255.55.55.128
Your sessionid is 13
Adaptive Server Enterprise/12.5.1

SQL>

Once you are connected any command allowed by Sybase (as opposed to Sybase's isql) should work the same.

ISQL assumes you are executing a stored procedure if your command is not a valid SQL statement or anonymous block. This means preceding your command with the keyword EXECUTE is not required, but is allowed if you wish to do so. It only assumes this if the command is not a keyword recognized by ISQL.

Keywords

The following keywords are recognized by ISQL after you have connected to Sybase:

Command	Description
CONNect	Disconnects from your current session and logs you in with new logon specs. Disconnecting also means your save text queue is saved to disk.
DEPTH	Sets or interrogates the current save text depth.
DO	Runs the specified command file.
EDIT	Allows you to edit the current save text entry.
EXECute	Allows you to execute a procedure.
EXIT	Exit from ISQL.
HELP	List commands recognized by ISQL.
QUIT	Exit from ISQL.
SHOW	Shows the current save text entry, a particular save text entry or all save text entries. The current save entry is denoted as 0. The entry prior to this entry entry is denoted as 1 (and so on).
REHASH	This command allows you to change the password for a username at an instance recognized by ISQL. You are presented with a list of username and instance combinations. To leave the password untouched, just press the enter key. To change that password, enter a new password. This command does not change the password in Sybase. Rather it allows you to change the password that is known by ISQL. To work, you must change the password in both Sybase and ISQL.
REPeat	Repeats your last command. You may edit that command using <editspecs> which edits the entry prior to executing.
RESET	Terminates command input for the current save text entry.
RETrieve	Retrieve a prior command and optionally edits it and repeats it.
ISQL	Displays a list of command line arguments recognized by ISQL.
?	Executes a host operating system command without leaving ISQL.

Example 1

The following example illustrates how to execute a SQL command from ISQL:

SQL> select * from http.dbo.HTTP_COLORS;

Example 2

The following example illustrates how to repeat this command:

SQL> repeat

Example 3

The following example illustrates how to edit and repeat this command:

SQL> repeat /*/NAME

Example 4

The following example illustrates how to retrieve the prior command, edit it and repeat it:

SQL> ret rep/*/COLOR

Example 5

The following example illustrates how to edit the current (unfinished) command:

SQL> select *
  1> from HTTP_COLORS
  2> edit/*/NAME

SQL> select NAME
  1> from HTTP_COLORS
  2>

Example 6

The following example illustrates how to change the depth of save-text entries from the default of 10 to 30:

SQL> depth 30

External Files

The following external files are used by ISQL. Except for the .SQLPlusPasswords file, ISQL looks in your current working directory. The .SQLPlusPasswords file searches your current working directory first then looks in $ORACLE_HOME/bin.

.SQLPlusHistory             (history file)
.SQLPlusPasswords           (encrypted password file)
.SQLPlusSumlog              (log file)