The CONSOLxx member of parmlib lets you define MCS consoles, HMCS consoles, SMCS consoles, or subsystem-allocatable consoles.

Subsystem-allocatable consoles are defined to a subsystem such as NetView®, which manages the console for the system. For an MCS, HMCS or SMCS console, CONSOLxx allows you to define various console attributes that control how operators can use the console and also control message routing and command processing for the console. For subsystem-allocatable consoles, you control console functions through the subsystem. It is beneficial to use an extended MCS console interface (when available) instead of a subsystem-allocatable because of the additional control provided by the extended MCS console interface.

How you define your console configuration depends on the MVS™ system environment at your installation. For a single MVS system, you might want to consolidate console functions using NetView. A single NetView console instead of several MCS consoles can serve as the focal point for MVS operator actions and for NetView automation tasks. An operator can handle many operational needs of the system from this one NetView console. For information on using NetView consoles, see NetView Automation: Planning.

For an MVS system that manages many system resources or subsystems, you might want to use several MCS consoles, each assigned with different functions. For example, defining a console cluster for a system can help your installation divide its console functions more efficiently. A console cluster is a group of several MCS, HMCS or SMCS consoles located together that you can use in place of a single console to divide up the functions and message traffic of the single console. Managing messages with a console cluster shows how to set up a console cluster for an MVS system.

If your MVS system requires increased security, your installation can use RACF® to control console logon and the commands that an operator can enter from a specific console. It is especially important to use RACF to control access to SMCS consoles and the commands they can issue. Using RACF with MCS, HMCS or SMCS consoles in an MVS system or sysplex can ensure that operators enter only the commands they are authorized to use.

In a sysplex, centralizing and coordinating console functions among different systems is an important operations goal. Message traffic and command routing are two considerations when you define consoles for a sysplex. In a sysplex, operators can receive messages from different systems on a single console, or can enter commands from a console to affect the processing of another system. How you define console functions for each MVS system can affect the operations of the sysplex as a whole. As a result, you need to understand the operations of the sysplex and plan the console configuration for each MVS system accordingly.

This topic describes how to set up an MCS, HMCS and SMCS console configurations for an MVS system using the CONSOLxx parmlib member. It describes how to define devices as consoles to MVS and how to define console functions to plan for console recovery and security. It also describes how to define console functions that help operators manage messages on their console screens and enter commands from their keyboards. Finally, it describes how you can define hardcopy processing to handle your MVS system recording. Because consoles in a sysplex present special cases, the topic also includes planning considerations for defining and using consoles in a sysplex environment.