Abstract for MVS Planning: Operations

This information supports z/OS® Version 2 (5650-ZOS).

Purpose of this information

This information contains planning information for MVS™ operations. It describes how to define and use multiple console support (MCS) consoles, SNA Multiple console support (SMCS) consoles (as of z/OS V1R1), and extended MCS (EMCS) consoles. It also describes how to manage messages and commands in an MVS single-system or sysplex environment.

Who should read this information

System programmers who plan MVS operations and persons who administer the security procedures for their installations should use this information. The information assumes that the user understands the installation's hardware and software, and also understands the general organization and functions of MVS. Users should also have a good understanding of parmlib and how to use it.

How to use this information

The information is organized as follows:
  • Planning MVS operations describes setting operations goals for an MVS environment. It provides a brief introduction to multiple console support (MCS) consoles, SMCS consoles, and extended MCS consoles.
  • Defining console configuration describes how to define an MCS and SMCS console configuration. It describes how to define a device as a console and how to define console functions in CONSOLxx of parmlib. It also provides information to plan for console recovery, console security, and system logging.
  • Managing messages and commands describes how to manage messages and commands for consoles in an MVS environment. It includes information about the message processing facility (MPF), the action message retention facility (AMRF), installation exits to modify messages and commands, and message translation using the MVS message service (MMS).
  • Planning for operation tasks describes how to plan for basic MVS operator tasks like initializing a system and operating MVS on a day-to-day basis.
  • Examples and MVS planning aids for operations provides examples of defining a console cluster to handle message traffic in an MVS system and defining a console configuration in a two-system sysplex. It also contains reference information to help you in your planning.

Conventions and terminology used in this information

When this information refers to RACF® (Resource Access Control Facility) it is the IBM® security management product for its large server z/OS operating system. You can substitute your security product in place of RACF if you are not using RACF.