|
|
|
|
|
A special Control‑O operator command can be used to modify the operating mode of Control‑O. Under normal circumstances, Control‑O operating mode must not be modified. However, if severe Control‑O problems are detected and BMC Customer Support representative has requested debugging information, these commands can help isolate and solve the problem.
Use the following operator command to modify the Control‑O operating mode:
F CONTROLO,MODE[=modename] |
where modename is the mode in which Control‑O must be run. The following modes can be specified:
Table 198 Control-O Operating Modes
Mode |
Description |
|---|---|
blank |
Displays the current operating mode of Control‑O. Under normal circumstances, the following message is issued in response to this command: CTO138I Control‑O OPERATING MODE IS NORMAL |
FREEZE |
Freezes all Control‑O automatic processes. No rules are activated and rules that are currently running (for example, they are paused due to a DO WAIT statement) are frozen. In FREEZE mode, messages and commands are not analyzed by Control‑O and the Automation Log (Screen OL) does not display any new messages or commands. |
LOGONLY |
Stops all Control‑O automatic processes. No rules are activated and rules that are currently running (for example, they are paused due to a DO WAIT statement) are frozen. In LOGONLY mode, no messages or commands are analyzed by Control‑O. However, the Automation log (Screen OL) displays all new messages and commands. |
TRIGGERONLY |
Stops all Control‑O automatic processes. No rules are activated and rules that are currently running (for example, they are paused due to a DO WAIT statement) are frozen. However, Control‑O examines rules to determine if they must be activated. In TRIGGERONLY mode, the Automation log (Screen OL) displays all new messages and commands and indicates what actions (that is, rules) would have been performed if Control‑O were operating in NORMAL mode. |
RESUME, option |
Returns Control‑O to NORMAL mode. All automatic processes are resumed. The option appended to this command determines whether to continue rules that were running when the automatic processes were interrupted.
|
The longer Control‑O automatic processes are halted (due to a MODE command), the more likely Control‑O’s examination of messages and commands will result in unexpected actions. Therefore, it is recommended that you stop Control‑O (using command P CONTROLO) and start Control‑O (using command S CONTROLO) as soon as a debugging session is complete.
Parent Topic |