the MPF list can be customized to carry this out. For other automation tasks, IBM provides several products to support workload and operational planning and control:

TME 10 NetView, while many think of it as a network management product, is also a robust automated operations product for detecting and reacting to messages and alerts (for a wide variety of platforms), and carrying out automated and monitoring actions. NetView can also provide an automated interface with products such as TME 10 Information Management and Performance Reporter for MVS, to integrate operations management data with data from other systems management disciplines.

TME 10 NetView also provides a central point of monitoring and automation from/to other operating system platforms; for example, it can monitor and detect a problem in a LAN Server or UNIX workstation that is required to allow users to access OS/390 resident applications.

System Automation for OS/390 (SA for OS/390) is a NetView application for automating scheduling, monitoring and recovery of various OS/390 workloads, ESCON I/O configurations, and local or remote OS/390 hardware platforms. For example, it can be used to IML and IPL another OS/390 system, start in proper sequence a set of CICS and DB2 regions, alter an ESCON director configuration, and provide a central workstation to monitor what is running across one or more OS/390 systems.

30.5.3.1 Automating Operational Procedures

You should look at automating as many operational procedures as you can. Automation will reduce human error and provide consistency to the procedure. All of the operational procedures identified in the preceding section can be automated to some degree by using things such as:

MVS facilities, such as exits, the Message Processing Facility (MPF) list and Automated Restart Management.

An automated operation product, such as TME 10 NetView, System Automation for OS/390, or a third party automation product.

Specialized products with automation interfaces, such as TME 10 OPC/ESA, DFSMS, and TME 10 Information Management.

Automation should be planned and added in stages as your OS/390 environment evolves. Both systems programming and operations personnel should be involved. Procedures should be tested thoroughly before being put into production. General types of activities you should consider automating include:

Console operations, such as suppressing messages and replying to WTORs.

Workload scheduling, such as starting up and shutting down online subsystems and batch jobstreams.

Event detection, to quickly discover problems or potential problems that will affect system availability (for example, the JES2 spool filling up.)

Monitoring performance and availability.

Distributing software - both system software and application output, such as reports.

Data backup and restore for both system and application datasets.

Chapter 30. Systems Management Philosophy and Methodology 467

Page 491
Image 491
IBM OS/390 manual Automating Operational Procedures

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.