Saving and Restarting

Network Monitor is a GUI tool.  Restarting the GUI would have no effect on running engines.

You would need to either restart the engine processes that use the table, or use the “purge caches” button on the processes in question in order for the changes to be recognized.

And if you are running 5.5Rev1, the purge cache button doesn’t work.  You need to enter the purge command from the command line

setsite (to the correct site)

hcicmd -p -c ‘. purgex’

Personally, anytime I change anything in a process I always cycle the process.

That way I’m always sure to pick up the change and don’t have to remember anything else or worry if it really worked this time.

Yes cycling the entire process is overkill sometimes but I can always depend on it doing what I want and I like that.

Personally, anytime I change anything in a process I always cycle the process.

I have been living by a similar axiom…

When all else fails, bounce the process!   8)

Most of our translation is in TCL, in the inbound or outbound TPS. We use a ‘change script’ to bounce the thread and check all is well.  We’ve used this successfully since 3.3.0!

Changing socket ports works well, but changing thread protocol generally requires a process bounce.