Configure this event to indicate when a transmission fails or was not confirmed. For example, when a transmission fails, you can use this event to insert a row in an audit table or to send a push notification.
The following table details the parameters that can be captured using the error_handler event:
Script parameter | Type | Description |
---|---|---|
request_option (out) | Integer |
Controls what the Notifier does to the push request after the error handler returns. The output can be one of the following values:
|
error_code (in) | Integer |
Use one of the following values for the error code:
|
request_id (in) | Integer | Identifies the request. |
gateway (in) | Varchar | Specifies the gateway associated with the push request. |
address (in) | Varchar |
Specifies the address associated with the push request. For security reasons, when the optional Notifier error handler is invoked, an asterisk (*) is substituted for any character in the subject or content of the notification that is not one of the following:
The value sent in the notification is the same as the original value. |
subject (in) | Varchar |
Specifies the subject associated with the push request. For security reasons, when the optional Notifier error handler is invoked, an asterisk (*) is substituted for any character in the subject or content of the notification that is not one of the following:
The value sent in the notification is the same as the original value. |
content (in) | Varchar |
Specifies the content associated with the push request. For security reasons, when the optional Notifier error handler is invoked, an asterisk (*) is substituted for any character in the subject or content of the notification that is not one of the following:
The value sent in the notification is the same as the original value. |
This event requires the use of a system procedure. You cannot configure this event directly using Sybase Central. See MobiLink server settings for server-initiated synchronization.
![]() |
Discuter à propos de cette page dans DocCommentXchange.
|
Copyright © 2013, SAP AG ou société affiliée SAP - SAP Sybase SQL Anywhere 16.0 |