Chapter 28. Orientation to OS/390 Console Operation

28.1 Introduction

There are enough differences between VSE and OS/390 operations to warrant each operator and systems programmer attending a class on the subject.

This chapter is intended only to provide the reader with an overview of OS/390 console operations on a single system. (Multi-system or sysplex operation are not covered here.) It is not intended to replace more formal training which should be given to all OS/390 operators and system programmers. It is also not intended to replace the standard OS/390 Operations publications listed herein.

The OS/390 system can be operated without a lot of manual intervention if set up correctly, and various automation products are used.

28.1.1 Operating Hardware Consoles

Before you can operate the system, you must be able to configure the hardware elements, and initialize the processor using the hardware console which is usually integrated into the service processor of the CPU. These consoles vary from processor to processor, and most should be familiar to the VSE operator using the same hardware:

Hardware Management Console (HMC)

The IBM S/390 CMOS (9672) and Multiprise processors have hardware consoles which are used to power on, IPL, reset, configure, and power off the processor. (The HMC is not required for an S/390 Multiprise.)

S/390 Multiprise Stand-Alone Support Element (SASE)

This an external console running OS/2 Warp which can be used for hardware management and has a look and feel similar to the HMC.

Other S/390 System Consoles

The IBM ES/9000 9021, 9121, and 9221 processors have integrated system consoles using the Service Processor or Processor Control Element (PCE) to power on, IPL, reset, configure, and power off the processor.

All of these hardware system consoles have interfaces for operating the OS/390 software, but are not usually used except for emergency or test.

28.2 Understanding the Operator Interfaces

Operator commands come in many flavors (MVS, JES2, SDSF, other subsystem), and can be entered through many different interfaces, such as:

The System Console

Hardware Management Console (HMC)

MCS (Multiple Console Support) Consoles

Subsystem Consoles

Extended MCS Consoles

TSO Operator Consoles

SDSF (System Display and Control Facility)

© Copyright IBM Corp. 1998

443

Page 467
Image 467
IBM Orientation to OS/390 Console Operation, Operating Hardware Consoles, Understanding the Operator Interfaces, 443

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.