System choice of serial transaction batching
Original Publication Date: 2002-Aug-16
Included in the Prior Art Database: 2003-Jun-21
BACKGROUND It is standard procedure to batch a series of sequential actions (subtransactions) into transaction batch. The batch boundary is decided by the application based on number of subtransactions, time since start of batch, or total 'size' of accumulated transaction. This applies in many messaging and database application areas such as: 1. Java* Messaging Service (JMS)/WebSphere** MQ batch programs (as described above) 2. JMS/MQSeries**with 'implicit' looping/transactions. e.g.