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 ( 'failed_script_name', error_code, 'new_script_name', 'action' )
Syntax |
Description |
---|---|
failed_script_name |
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. |
error_code |
INTEGER. The SQL Anywhere error code that this rule handles. |
new_script_name |
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. |
action |
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:
|
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.
Discuss this page in DocCommentXchange. Send feedback about this page using email. |
Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1 |