well, and the disciplines should include those to avoid ²the hole in the boat isn¢ t on my side of the ship, so all is well² syndrome that can develop.

30.1.3 The Role of Automation

Automation involves the ability to correct, bypass, or circumvent failed system and network elements and applications, based on defined policies and using hardware or software functions without human intervention. Automation improves availability and reduces operational costs.

To put it bluntly, as your environment grows, it will be impossible to manage it without automation. The number of systems, subsystems, applications, connections, files, databases and so on that have to be monitored and controlled will simply be overwhelming for any size staff (if you can afford and even find a large enough staff). Automation can be applied to all of the disciplines to make them more efficient; to do this it must follow prescribed management policies, which can be developed directly from a structured approach.

The following sections describe a set of the typical categories or grouping of management functions or tasks required, and will identify some of the key products that support the tasks. The degree to which you implement each function will vary based on your organization and systems management objectives; this is just to show you the tasks that should be considered when looking at Systems Management in the OS/390 environment.

30.2 Change Management

30.2.1 Overview

The change management discipline was discussed above as the example showing the effects of the environmental changes and the opportunities to exploit systems management disciplines to derive benefits from those changes. For a migration it is probably the most active discipline initially, simply because of the differences between the VSE and OS/390 environments - you have to change things for them to still work. After the migration, change management is still important - it will be driven by other disciplines such as problems (making changes to address/eliminate problem situations), performance management (making changes to improve the performance of applications, or allowing a resource to provide better performance to applications), and configuration (making changes to implement or meet the requirements of new levels of hardware and software), to name a few.

30.2.2 Tasks

The change management process includes the following:

∙Collection - recognizing and gathering the changes, so that the focus is on changes as a whole, and not just on individual changes.

∙Assessment - evaluation and approval of a change from both a technical and business standpoint.

∙Planning - creating a plan that defines the steps in the change installation process. This also requires information regarding the current levels of hardware (including microcode) and software for system and network components, which is best met with a common repository for configuration data.

460VSE to OS/390 Migration Workbook

Page 483 Page 485
Page 484
Image 484
IBM OS/390 manual Role of Automation, Change Management Overview
Page 483 Page 485

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