SRCMID

It is important to note that for tracing to work, the definition of the metadata field SRCMID must be expanded. In previous versions, the SRCMID was only assigned when a message’s MID was reassigned. In this case, the SRCMID was assigned to the message’s previous MID. The SRCMID would then remain null whenever a new message was created, whether in Xlate, TPS, reroute, or any other situation.

Now, whenever a new message is created from a previous message, the new message also has its SRCMID assigned to the MID of the preceding message. For example, the SRCMID of a reply message is the MID of the original message that generated the reply. A rerouted message shows up as a new message, but the SRCMID is the MID of the original message.

A new message that is generated in a translation or procedure also has the SRCMID point to the message that was being translated or had the procedure called on.