MobiLink provides the following stored procedures to help you create your applications.

System procedures to add or delete scripts

You must add synchronization scripts to system tables in the consolidated database before you can use them. The following system procedures add or delete synchronization scripts in the consolidated database:

• ml_add_connection_script system procedure
• ml_add_table_script system procedure
• ml_add_dnet_connection_script system procedure
• ml_add_dnet_table_script system procedure
• ml_add_java_connection_script system procedure
• ml_add_java_table_script system procedure

When you use the MobiLink server API for Java or .NET, you use these stored procedures to register a method as the script for an event, so that the method is run when the event occurs. You can also use them to unregister your methods.

When you add a script using a system procedure, the script is a string. Any strings within the script need to be escaped. For SQL Anywhere, each quotation mark (') needs to be doubled so as not to terminate the string.

You cannot use system procedures to add scripts longer than 255 bytes to Adaptive Server Enterprise 11.5 or earlier. Instead, use Sybase Central or direct insertion to define longer scripts.

DB2 mainframe version 8.1 supports a backward compatibility mode, where column names and other identifiers are limited to a maximum of 18 characters. To support this environment, all MobiLink system objects in DB2 mainframe have names of 18 characters or less. See IBM DB2 mainframe system procedure name conversions.

IBM DB2 LUW prior to version 6 only supports column names and other identifiers of 18 characters or less, and so the names are truncated. For example, ml_add_connection_script is shortened to ml_add_connection_.

Other system procedures

• ml_add_property system procedure
• ml_delete_sync_state_before system procedure
• ml_reset_sync_state system procedure