Dynamic routing functions  Creating custom filters

Chapter 3: Building Production Objects

Non-dynamic routing functions


submit()

Description

Submits the data that the filter object is processing back to the SFM via a production record. The name of the production object for which the new transaction is being submitted.

WARNING! There must be a routing function name in the SFM configuration file, which cannot be “ENGINE.”

Arguments

NoteIf you have a null character in the data string, but not at the beginning, the data is truncated to the point of the null.


tranCancel()

Description

Specifies the actions that the SFM should perform when a transaction encounters a processing error through a production object. Allows the destination to continue to receive new transactions, just as if the destination had returned a -999 for the transaction. Overrides any error option selections made in the Production Object Options window.

Arguments

None.


submitTran()

Description

Submits the data that the filter object is processing back to the SFM via a transaction record. If you have a null character in the data string, but not at the beginning, the data is truncated to the point of the null.

WARNING! There must be a routing function name in the SFM configuration file, which cannot be “ENGINE.”

Arguments


tranDestID()

Description

Appends the ID number (flavor value) of the production object’s destination, as defined in the SFM configuration file, to the current blob area.

Argument

None.


tranDestName()

Description

Appends the reference name of the production object’s destination, as defined in the SFM configuration file, to the current blob area.

Arguments

None.


tranHalt()

Description

Specifies the actions that SFM should perform when a transaction encounters a processing error through this production object. Halts the destination, and prevents it from receiving any further transactions until the unprocessable transaction is placed in the unprocessable log. Overrides any error option selections made in the Production Object Options window.

Argument

None.


tranPriority()

Description

WARNING! Use only in the post-qualification rule in a production object. If you call tranPriority() at any other point during transaction production, it has no effect.

Assigns a priority to the transaction. Whenever e-Biz Impact receives a transaction that has a priority set, it processes that transaction before any non-prioritized transactions. When more than one prioritized transaction is waiting for processing, e-Biz Impact processes transactions from the highest priority to the lowest. If multiple transactions have the same priority, e-Biz Impact processes them based on their timestamp.

A priority set with this builtins filter function overrides a priority assignment in a route or production object setting in the SFM configuration or a priority assignment in the Priority argument in the route_recx() function.

Arguments

Priority – enter a number (0 to 255), where 1 is the lowest priority and 255 is the highest.

NoteLimit your priorities to 1-16, as 17-255 are reserved. 0 removes a priority set through the Transaction ID record.


tranSerialNo()

Description

Appends the serial number assigned by the SFM to the current module to the end of the current blob area. The serial number data is in string format.

Arguments

None.


tranSourceName()

Description

Appends the source name sent from the input transaction’s acquisition module to the end of the current blob area.

Arguments

None.





Copyright © 2005. Sybase Inc. All rights reserved. Creating custom filters

View this book as PDF