siptrace flag fixes

[grumvalski]

Pre-Submission Checklist

• Commit message has the format required by CONTRIBUTING guide
• Commits are split per component (core, individual modules, libs, utils, ...)
• Each component has a single commit (if not, squash them into one commit)
• No commits to README files for modules (changes must be done to docbook files
  in doc/ subfolder, the README file is autogenerated)

Type Of Change

• Small bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would change existing functionality)

Checklist:

• PR should be backported to stable branches
• Tested changes locally
• Related to issue #XXXX (replace XXXX with an open issue number)

Description

[miconda]

You can go ahead and merge it.

I am thinking that it could make sense to add some dedicated functions to the TM module and TM API to get only the needed fields from a transaction, not to have to backup active transaction, lookup the one we need for checking and then restoring to the old one, as long as we do not need to do any other operation with the searched transaction. But this only as a future enhancement (the idea popped up a while ago, for some other parts of the code, but could be used here as well).

[grumvalski]

Agree that such functions could be very useful in cases like this one.
Should I backport to 5.3?