The Unrouteable Transactions view (Figure 3-9) displays transactions that do not qualify for any SFM production objects, and, therefore, are not routeable to any destinations. These transactions are stored in the unrouteable log file, which is named Unroute.log by default.
To change log file names and locations, right-click
an SFM in the Configurator, select Properties, then select the Log
Files tab.
The Unrouteable Transactions view allows you to edit unrouteable transactions and resubmit corrected transactions to the SFM.
You can also skip and repair unrouteable transactions. See “Repairing unprocessable, cancelled, and unrouteable d transactions”.
Figure 3-9: SFM application Unrouteable Transactions view
To delete a transaction, right-click the transaction and select delete. The transaction is not removed from the unrouteable log file, but is marked as DELETED. You cannot repair deleted transactions.
When a transaction is repaired, the SFM generates a new transaction that is linked to the original transaction serial number, which prevents loss of the initial transaction and provides a repair history. Once the transaction is repaired, the original transaction is given a REPAIRED status.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
