|
|
|
OCS allows you to monitor and control your regions by receiving messages and allowing you to issue commands. Events from your network are sent to your OCS window. You can issue commands to take control of any problems that might occur.
As you receive messages and output from commands, you can control, reorder, or clear output on the screen so that it can be read more easily.
When the bottom line of the display area is filled, the system pauses before wrapping back to the top of the display area to write the next message.
Sometimes, a large number of messages might be sent to the screen within a very short period of time. This causes the display to roll messages faster than you can read them. There are two options you can use to temporarily suspend message delivery or change the way the messages display:
To stop the flow of output to the screen at any time, press the Enter key while nothing is in the command line. This freezes the display and no further messages appear until you enter data.
While the screen is frozen, the word HOLDING appears immediately above the command line.
The default value for automatic hold supplied with your system automatically freezes an OCS window when a message fills the last line and there are messages queued to wrap back to the top of the screen. This is specified by the AUTOHOLD command.
When AUTOHOLD freezes your screen, the caption AUTOHOLD is displayed above the command line. No further messages appear until you input something.
The AUTOHOLD command option is part of your operator profile.
Note: If more unsolicited messages arrive while the screen is in HOLDING or AUTOHOLD mode, the caption above the command line changes to MSG QUED, and the terminal alarm sounds.
Your system queues a limited number of messages for an OCS window while in the HOLDING or AUTOHOLD mode. The queue limit default before any OCS window messages are discarded is 200 messages.
The HOLDING or AUTOHOLD caption above the command line changes to 75% LIMIT, HOLD LIMIT, and then MSGS LOST, as this limit is approached, reached, and then exceeded. Each caption change also sounds the terminal alarm. These conditions vary and update while you actively monitor and release system messages in the OCS window.
You can define the queue limit for each OCS user window by using the PROFILE command.
One of the characteristics of an OCS window is that your system can send messages to your window at the same time as you are entering a command. These messages are displayed differently depending on the type of terminal you are using:
Any data you have just entered is immediately frozen and any new data entered is ignored while the message writes to the screen. You can then continue to type in your command text when message delivery has finished.
A contention condition arises. The terminal is seen as being in a send state (because you have started typing on the keyboard), and refuses to accept any output from your system until your input has been sent. However, rather than defer your system, the system interrupts you after a set period and forces the output of a message.
The default contention delay interval is 15 seconds. This is usually long enough to let you complete a standard command input operation.
To resequence or unwrap messages displayed in your OCS window, enter the ORDER command.
The OCS messages are redisplayed in the window in chronological order, with the oldest messages at the top of the window.
The ORDER command is assigned to F12 by default.
Note: This command does not affect the HOLDING or AUTOHOLD condition.
After many messages have appeared in your OCS window, you may want to clear the window before any new messages arrive.
To clear your OCS window, enter the CLEAR or K command.
| Copyright © 2010 CA. All rights reserved. |
|