Chapter 3 Connection and Communication Parameters
61
No log file
"Debug connection parameter" on page 56
If you want to save client error messages and debugging messages in a file,
use the Logfile parameter.
If the file name includes a path, it is relative to the current working directory
of the client application.
The LogFile connection parameter is connection-specific, so from a single
application you can set different LogFile arguments for different
connections.
The following command line starts Interactive SQL connecting to the
ASA 7.0 Sample data source with a LogFile parameter:
dbisql -c "dsn=ASA 7.0 Sample;dbg=ON;log=d:\logs\test.txt"
Typical log file contents are as follows:
Tue May 30 2000 11:00
CONN: Starting remote ports
Trying to start TCPIP link ...
Loading wsock32.dll
Loading ws2_32.dll
TCP using Winsock version 2.0
My IP address is 172.31.140.75
My IP address is 127.0.0.1
TCPIP link started successfully
Password connection parameter [PWD]
To provide a password for the connection.
Anywhere
No password provided.
"EncryptedPassword connection parameter" on page 58
Every user of a database has a password. The password must be supplied for
the user to be allowed to connect to the database.
The password parameter is not encrypted. If you are storing passwords in a
data source, you should use the EncryptedPassword parameter. Sybase
Central and the Adaptive Server Anywhere ODBC configuration tool both
use encrypted parameters.
If both Password and EncryptedPassword are specified, Password takes
precedence.
Default
See also
Description
Example
Function
Usage
Default
See also
Description
To Next Page
Loading...