You can implement this property to catch situations where a transmission failed or was not confirmed. For example, when a transmission fails you can cause a line to be inserted in an audit table or a notification sent to someone.

You can capture the following information. You can use all of the parameters or a subset. This property requires the use of a stored procedure.

See also

• ml_add_property system procedure

Example

In the following example, you create a table called CustomError. You log errors to the table using a stored procedure called CustomErrorHandler. In this example, the output parameter notifier_opcode is always 0, which means that default Notifier handling is used.

CREATE TABLE CustomError(
    error_code  integer,
    request_id  integer,
    gateway  varchar(255),
    address  varchar(255),
    subject  varchar(255),
    content  varchar(255),
    occurAt  timestamp not null default timestamp );
     
CREATE PROCEDURE CustomErrorHandler(
    out @notifier_opcode integer,
    in @error_code  integer,
    in @request_id  integer,
    in @gateway   varchar(255),
    in @address   varchar(255),
    in @subject   varchar(255),
    in @content   varchar(255) )
begin
    INSERT INTO CustomError( 
 error_code,
 request_id,
 gateway,
 address,
 subject,
 content )
    VALUES(
 @error_code,
 @request_id,
 @gateway,
 @address,
 @subject,
 @content );
    set @notifier_opcode = 0;
end

To use the stored procedure ml_add_property with a SQL Anywhere consolidated database, run the following command:

call ml_add_property( 
  'SIS',
  'Notifier(myNotifier)',
  'error_handler',
  'call CustomErrorHandler(?, ?, ?, ?, ?, ?, ?)');