Projected trends recorded in this way represent accurate growth measurements. These projections can be used to identify needed changes in system configuration with sufficient lead time to permit orderly procurement and installation of new resources. This will provide the capacity required over time as your system grows.

30.5 Operations Management

30.5.1 Overview

Operations management includes tasks for planning distributing, evaluating, and controlling workloads. It also addresses the resource availability needed to support the workloads.

The daily tasks required to activate system components, start workloads, and monitor activities to discover any discrepancies are the heart of supporting the system users. In a small environment these tasks may be carried out by a small number of people; in many cases the systems programming and daily operations functions are carried out by the same people. In the OS/390 environment, the opportunity for greater growth leads to the separation of operational tasks from systems programming tasks. Operations becomes the ²first line of defense² when a deviation from the norm occurs.

The operations management discipline is oriented towards defined workloads. It covers the activities of starting and stopping systems and resources (including, but not limited to, host systems, workstations, networks and databases) and receiving and responding to operational notifications. However, it encompasses more than the traditional operator¢s console commands, messages, and responses. The objective is to allow management to set policies to manage workloads and resource availability, and to automate the interactions required to implement these policies.

Operations management should provide the flexibility to centralize control of some functions and distribute others. This ability, together with other enhanced operator functions, will reduce the cost of operations.

The requirements for operations management may include:

∙Lights-out operation - automated operations, ranging from simple command lists to automate a trivial or repetitive operator function to applying Artificial Intelligence (AI) to automate operator decisions.

∙

∙

Data protection - automated backup and archiving of data files.

Monitoring - consistent, easy to use, graphical operations interface(s), that display system and network topology and resources.

30.5.2 Tasks

The operations process includes:

∙Workload planning - definitions, analyses, and reports of the enterprise¢ s workloads, both actual and anticipated.

∙Operations planning - determines the structure needed to support the availability of systems and resources for the defined workloads.

Chapter 30. Systems Management Philosophy and Methodology 465

Page 488 Page 490
Page 489
Image 489
IBM OS/390 manual Operations Management Overview
Page 488 Page 490

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.
Top Page Image Contents