Automated Operations - handles the complex operations job scheduling procedures to ensure that work is completed in a timely manner.

ÞVerifying that the resources needed for a scheduled workload are available; for example, that the required disk or tape volumes are available for a backup operation.

ÞPlanning to ensure the availability of day-to-day operations items, such as printer paper, tapes, and control center equipment.

ÞSpecifying operations policies and procedures, preventive maintenance schedules and procedures, and operations recovery procedures.

ÞSupporting output delivery as defined by service-level agreements.

Workload control - distributes work-handling and work-processing responsibilities across systems. It includes monitoring, analyzing, and adjusting of work in those systems. Examples of these functions include:

ÞTranslating workload policies into system specifics.

ÞDistributing workload policies to systems.

ÞReceiving work requests and distributing them to systems, based on needs and policies.

ÞManaging resources needed for a workload for example, ensuring a tape volume needed by a batch job is mounted and ready for use on a tape drive.

ÞMonitoring systems and resources to determine work progress.

ÞResponding to queries about the status and progress of work.

ÞAccepting, and responding to, notification requests for work-related events, such as job termination.

ÞTaking action on workload-related events, such as restarting or rerouting work.

ÞManaging the printing and delivery of hard copy output.

Operations control - applying operations policies for exception conditions, resource shortages, and other situations.

30.5.3Methodology

Operators must have documentation and tools to understand how the system and workloads are supposed to be set up and run, the instructions to carry out setup/execution tasks, information on what to monitor and look for, instructions on what to do when something goes wrong, and a callout list of who should be contacted for various situations. This information can be kept in a set of files or in a PDS for starters; while it is popular to have hard copy ²run² books, these are much more vulnerable to becoming out of date. In either case, a strong maintenance process that is tied into the problem, change, and configuration process is required to ensure accurate and up-to-date information.

Automating operational tasks is one of the most productive activities to carry out in the OS/390 environment. Automation will reduce problem detection and bypass time, eliminate human error, and support higher availability by carrying out quicker recovery actions. Automation can also make operators more productive by carrying out more mundane and repetitive tasks, monitoring for situations, and doing initial recovery. One of the simplest tasks to automate is message suppression, so that only critical messages are displayed at consoles;

466VSE to OS/390 Migration Workbook

Page 490
Image 490
IBM OS/390 manual Methodology

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.