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

SQL Anywhere 11.0.1 » MobiLink - Server Administration » MobiLink Reference » MobiLink server system procedures » MobiLink system procedures


ml_add_passthrough_repair system procedure

Use this system procedure to define rules for handling script errors. Each rule defines the action that a client should perform when a specific script generates a given error code. This procedure adds an entry to the ml_passthrough_repair system table. If an entry with the given failed_script_name and error_code already exists in the table, the procedure updates the entry.

ml_add_passthrough_repair ( 




VARCHAR(128). The name of the failed script to which this rule applies. This value must be a valid script name in the ml_passthrough_script table.


INTEGER. The SQL Anywhere error code that this rule handles.


VARCHAR(128). The name of a script to replace the failed script when action is R. If action is S, P, or H, this value must be null. If action is R, this value must be a valid script name in the ml_passthrough_script table, and can be the same as failed_script_name.


CHAR(1). The action that a client should perform when error_code is generated for failed_script_name. This value must be one of the following:

  • R   (replace) Indicates that the failed script should be replaced with the one specified by new script name and an attempt should be made to run the new script. To rerun the failed script, choose new script name to be the same as failed script name.

  • P   (purge) Indicates that the remote database should discard all the scripts that it has received and continue executing script normally after that.

  • S   (skip) Indicates that the remote database should ignore the failed script and continue executing scripts as if the failed script had succeeded.

  • H   (halt) Indicates that the remote should not execute any more scripts until it receives further instructions.


You should make every effort to avoid failed SQL passthrough scripts by testing scripts thoroughly.

For DB2 mainframe consolidated database types, this procedure is called ml_add_pt_repair. See IBM DB2 mainframe system procedure name conversions.

See also