Places a stronger emphasis on service, as it promotes keeping one¢s ²eye on the ball.²

Provides more effective and productive processes.

Challenges in this approach are not just to segment the activities, but also to recognize how the disciplines interrelate and how they cross functional boundaries. Also, all responsibilities must be assigned and understood, and disciplines documented.

30.1.2 Systems Management Scope - What Needs to be Managed?

In almost all systems, hardware (at the mainframe site, anyway) is reasonably controlled. As our systems become networks of autonomous users who can control their own configuration and setup, it is possible for an end user to destroy his or her own ability to interact with the host and other server systems. In some cases, they can also impact the connections and services to other users.

Host operating system and subsystem software (0S/390, ACF/VTAM, CICS/ESA, DB2) similarly have a relatively small group of people who control and manage their attributes and status. In the new OS/390 environment, however, it is likely that the number of people responsible for these components could be larger than is typical in computer systems running VSE/ESA or VM/VSE. In addition, problems and changes in one component may affect other components and workloads. Because of the increase in number of people who control these components, it is recommended to implement Systems Management in a way that all the systems support personnel will be aware of planned and completed management activities. In addition, this process permits the implementation of peer review of planned activities, which both catches errors and educates other staff members in the various Systems Management disciplines.

Application program software is likely to be impacted with higher volumes during an 0S/390 migration in several areas. For one example, it is likely that application source programs will be changed (from DOS/VS COBOL to COBOL for MVS, and VSE assembler macros to OS/390 macros). Much of this will be automated, but because of new language nuances, program maintenance and development will require more effort, at least to begin with. Systems Management disciplines such as change and operations management can help reduce this extra effort by avoiding rediscovery, identifying reasons for failure, and more. Change management will help control JCL changes, application setup and run instructions, and more. Operations management will invoke and monitor the applications, provide for problem bypass, and provide feedback for any further changes to be made.

Overall, then, you should realize more benefits by extending the scope of your implementation of systems management disciplines all the way from hardware configuration and setup on one end to application programming and JCL on the other end. Whether the discipline being applied is Change Management, Problem Management, Performance Management, Operations Management, Security Management, or others, the most benefit can be derived when the scope for the discipline covers the system.

The disciplines should also include the network elements (we will define network as anything on the non-mainframe side of a communications controller); the availability of the workloads to the users will depend upon those elements as

Chapter 30. Systems Management Philosophy and Methodology 459

Page 483
Image 483
IBM OS/390 manual Systems Management Scope What Needs to be Managed?

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.