In the development environment, you can trace connections as you work in the Database painter or DataWindow painter, and when you run and test your applications. The trace information that is collected can help you troubleshoot your applications before you deploy them. You can use two tools to collect information: the PocketBuilder Database Trace tool and the ODBC Driver Manager Trace tool.
The rest of this chapter describes these tools.
In your deployed application, SQL Anywhere provides several different ways to create log files of database activity:
To save the server window output to a file, start the database engine with the -o option for dbsrvXX, or dbengXX, where XX is the SQL Anywhere version number. For example:
dbeng9 -c 8m -o asademo.out -n asademo9 "D:\Program Files\Sybase\asademo.db"
To save client error messages and debugging messages in a file, use the Logfile connection parameter when you specify the ConnectString. For example:
sqlca.dbparm="ConnectString='DSN=ASA 9.0 Sample;LOGFILE=D:\logs\asademo.txt'"
To save a log when you run the MobiLink synchronization server (dbmlsrv9 or mlsrv10) or client (dbmlsync) to synchronize SQL Anywhere remote databases with a consolidated database, use the -o option to specify the name of the output file, the -v option to specify the level of message logging, and the -dl option to display all logging messages on the screen. For example:
dbmlsrv9 -c "dsn=consoldb" -o mlserver.mls -v+ -dl
dbmlsync -c "dsn=remotedb" -o dbmlsync.out -v+ -dl
For more information about these tools, see the SQL Anywhere documentation.
