-v option

Allows you to specify what information is logged to the message log file and displayed in the synchronization window.

Syntax 
mlsrv11 -c "connection-string" -v[ levels ] ...
Remarks

This option is particularly useful when dbmlsync transaction-level uploads are used.

This option controls the type of messages written to the message log file.

If you specify -v alone, the MobiLink server writes a minimal amount of information about each synchronization.

A high level of verbosity can adversely affect performance and should only be used during development.

The values of levels are as follows. You can use one or more of these options at once; for example, -vnrsu.

  • +   Turn on all logging options that increase verbosity.

  • c   Show the content of each synchronization script when it is invoked. This level implies s.

  • e   Show system event scripts. These system event scripts are used to maintain MobiLink system tables as well as SQL scripts that control the upload.

  • f   Show first-read errors. This logs errors caused when load-balancing devices check for server liveness by making connections that don't send any data, and thus result in failed synchronizations.

    For TCP/IP connections, you might be better off using the TCP/IP option ignore. For more information, see -x option.

  • h   Show the remote schema as uploaded during synchronization.

  • n   Show row-count summaries.

  • o   Show SQL passthrough activity.

  • p   Show progress offsets.

  • r   Display the column values of each row uploaded or downloaded.

  • s   Show the name of each synchronization script as it is invoked.

  • t   Show the translated SQL that results from scripts that are written in ODBC canonical format. This level implies c. The following example shows the automatic translation of a statement for SQL Anywhere. 
    I. 02/11 11:02:14. [102]: begin_upload synch2
{ call SynchLogLine( ?, ?, ’begin_upload’ ) }
I. 02/11 11:02:14. [102]: Translated SQL:
call SynchLogLine( ?, ?, ’begin_upload’ )

    The following example shows the translation of the same statement for Microsoft SQL Server.

    I. 02/11 11:03:21. [102]: begin_upload synch2
{ call SynchLogLine( ?, ?, ’begin_upload’ ) }
I. 02/11 11:03:21. [102]: Translated SQL:
EXEC SynchLogLine ?, ?, ’begin_upload’

  • u   Show undefined table scripts. This may help new users understand the synchronization process.

Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0