multiple mcsapi sessions use the same txnID

mcsapi requests a new txnID every time, unfortunately it uses a fixed sessionID and DBRM gives an existing txnID if there is one open.

This means that a multi-threaded mcsapi application could use the same txnID for two transactions. Causing one commit/rollback to commit/rollback both.