As a rule, the debugger does not follow messages through the server from channel to channel. A single message can, however, be followed by setting conditional breakpoints across the channels that test the TID special register. The TID, once assigned in the first channel to which the message is presented, remains with the message through its life in the application. While in a real production run the application may not change the TID, while debugging you can reset the TID special register to a simpler value to avoid tracking long, complicated character sequences. This process will simplify setting breakpoints and also not confuse other components of the server, such as iWay Business Activity Monitor (BAM).

Note: It is recommended that iWay BAM be disabled during a debugging sequence if the TID is to be changed.

breakpoint -if _sreg(tid)=='tidvalue'