How can I access or get the transaction id or some thing that can help me group multiple DML's together? A transaction which can have mutiple inserts ,mutiple updates and multiple deletes. I want group all these operation together.

Each connection can only have one transaction at a time. A transaction is everything between one commit/rollback to the next.

Andy

If you really need a transaction ID, you may want to have a look here: Transaction IDs in DB2 Note that the article is a few years old and you may have to adjust the log reading/scanning part.

What exactly do you want to do? I'm asking because usually the request to have some sort of transaction ID indicates a problem in your application design. You should be able to do without something like this. It would be much safer, too.

Thanks Kunt and Andy for the replies.

I have a table which stores group and the linked operation. When ever the operation linked to group changes. The system deletes all the rows for that group and reinserts all the new changes. I am using triggers to capture all the changes in this table. My trigger inserts into a temp table when ever there is insert to the original table. This is working as expected. I need something (transaction id) to group inserts for a group together so that i can put sequence as in 1,2,3 etc.

Example
Suppose Group A can have 1,2,3,4 operations. When the group is created the trigger will insert four rows for group into temp table. I want something using which I can tie these rows together and put a change count 1. Suppose later the group is changes to have five operation 1,2,3,4,5. The trigger will again insert these five rows into temp table. Again here I want to put a change count of 2 to this group. The logic should apply for all the group changes.

The combination of the application ID and the UOW ID should be sufficiently unique for your purpose. Something like:

You don't need a transaction ID. If your temp table is a a real temp table (declared or created), then the trigger (which is executed in the scope of the current transaction) will only see the rows it puts into the temp table itself. It won't see data from other transactions. You should create/declare the temp table in such a way that it discards rows on ROLLBACK and COMMIT, of course.