Process Controls dialog box options
Right-click a process to open the context menu. Selecting Process Controls dialog box.
to open theThis table lists the dialog box options:
Option | Description |
---|---|
Initiates the process by starting all the threads in the selected process. | |
Shuts down the process by stopping all the threads in the selected process. | |
Starts the threads in the process, with the outbound data on hold. | |
Starts the threads in the process with the last hold status. | |
Restarts the process. When restarting a process, the GUI can still be operated. The command line output is appended to the Command and Engine Output pane, where you can see the results. When restarting a process, the thread status icon on the GUI changes from green to red to green again. | |
Places a hold on all outbound data queues for all protocol threads in the process. | |
Releases held messages, so they can continue processing for all protocol threads in the process. | |
Holds transmission of all thread reply messages of the selected process until released. | |
Releases hold on all or a specified number of reply messages. | |
Reloads updated Tcl procedures. | |
Removes the configuration caches. Use this option after making a change to an existing configuration. This is not designed to be used for the creation of new threads, processes, routes, and so on. | |
Shows engine output as it happens. | |
Opens the log file of engine output. | |
Opens the Engine Log Configuration dialog box. Click to select the engine output alias. This applies an Engine Output (EO) alias, configured in the Engine Output Configurator, to the threads in the process. | |
Loads Tcl procedures that are created after the engine began running. | |
Causes the current engine log (.log) and error (.err) files to close and be renamed with an .old extension, and then opens new logs. | |
Opens the Status Report dialog box, which provides statistical information on the threads within the process. | |
Resets statistics and counts for a site’s process or
thread. This calls the hcimsiutil
engine command. Before using this option, there is the potential to produce unreliable counts. The memory is not corrupted when this option is used. The engine and Network Monitor both lock the shared memory for any write/clear. |