When you create MobiLink applications with SQL Anywhere remote databases, there are two types of client log file that you should be aware of:

dbmlsync message log

By default, dbmlsync messages are sent to the dbmlsync message window. In addition, you can send the output to a message log file using the -o or -ot options. The following partial command line sends output to a log file named dbmlsync.log.

dbmlsync -o dbmlsync.log ...

Logging dbmlsync activity is particularly useful during the development process and when troubleshooting. Verbose output is not recommended for normal operation in a production environment because it can slow performance.

You can control the size of log files, and specify what you want done when a file reaches its maximum size:

For more information, see:

• -o option
• -ot option
• -os option

You can control what information is logged to the message log file and displayed in the dbmlsync messages window using the -v option.

For more information, see -v option.

You can manage log files using the delete_old_logs option.

For more information, see delete_old_logs option [MobiLink client] [SQL Remote] [Replication Agent].

When no message log file is specified, all output is displayed in the dbmlsync messages window. When a message log file is specified, less output is sent to the dbmlsync messages window.

SQL Anywhere transaction log

See Transaction log files.