The following general information applies to using collection:
The dbInsert filter overwrites any existing data if the key is already present in the specified table name. Use the dbNotExist function to verify that there is not already data present in the collection file.
The dbSelect filter copies the data from the collection files, so production objects can collect the data more than once and place it into different output transactions. However, the dbSelect filter does not perform concatenation, so if there is already data present in the current message area, this filter overwrites it. Therefore, call this filter from within an empty rule component object each time you want to copy an entry from a collection file to the output transaction.
Once you no longer need the data, use the dbDelete filer to remove the data from the collection file. However, do not delete data from a collection file until all outstanding transactions using that data have a successful return from their delivery AIMs. This keeps the data available in case a system failure results in the loss of the collected transaction.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
