Controlling system messages and commands

Messages are the system’s chief means of communication with you. Messages range from informational, which are important but do not require a response, to immediate action, which are not only important but require that you perform the requested action at once. The action might be required because the message issuer waits until the action is performed, or because taking the action as soon as possible can improve system performance. Less urgent, but still important, are the eventual action and critical eventual action messages. The message issuer is not waiting for you to perform the action, but a number of unanswered requests might degrade system performance.

The size of the screen’s message area varies, depending on the type of display console. When the message area becomes full, you need to delete messages to make room for new ones. You can delete messages, or have the system do it for you automatically. (See “Deleting Messages from the Console Screen” .) Once an action message is deleted from the screen, you cannot see the entire message again unless the action message retention facility is active and you have issued a DISPLAY R command.

So that you do not have to delete messages too often, make sure that you manage message traffic carefully on all consoles. For example, if you find that a console screen often fills with action messages, think about:
  • Adjusting routing codes and assigning message levels. Any console should receive only messages for which the operator of that console is directly responsible.
  • Activating the action message retention facility so you can put the console in roll mode without losing action messages.