Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 17 » MobiLink - Server Administration » MobiLink server

MobiLink server logging

Logging the actions that the server takes is particularly useful during the development process and when troubleshooting. Verbose output is not recommended for normal operation of a production environment because it can slow performance.

Logging output to a file

Selected logging output is sent to the MobiLink server messages window. In addition, you can send the output to a message log file using the -o option. The following command sends output to a message log file named mlsrv.log.

mlsrv17 -o mlsrv.log -c ...

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

  • Use the -o option to specify that a message log file should be used.

  • Use the -ot option to specify that a message log file should be used and you want the previous contents of the file to be deleted before messages are sent to it.

  • In addition to -o or -ot, use the -on option to specify the size at which the message log file is renamed with the extension .old and a new file is started with the original name. This option limits the total disk space taken up by the message log files.

  • In addition to -o or -ot, use the -os option to specify the size of old message log files when they are assigned a new name based on the date and a sequential number.

Controlling the amount of logging output

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

Controlling which warning messages are reported

You can control which warning messages are reported using the mlsrv17 -zw, -zwd, and -zwe options.