Using globals

If you have TCL procedures that set globals in the global namespace, then it helps to know how your message flow is affected when using globals.

For example, the first message arrives in the TCL (TPS) for the Inbound TPS UPoC. A global is set to check the next message for status. The second message arrives in this same TCL procedure and the logic examines if this is the expected next message.

There is only one SMS interpreter that does the TPS per protocol thread. This is true even if threaded SMS is not enabled.

When threaded, the difference is that the work in this interpreter is performed in a sub-thread. In this case, globals work fine and anything that is performed in the startup mode stays around. This is per protocol thread, so the IB and OB use other ones.

This differs from threaded xlates where they can bounce around depending on the options selected.

The threaded option only runs if the message type is data. The same interpreter is used when you have a reply, but it is not threaded.