30.3.2 Tasks

The problem management process includes the following:

Problem determination - the detection of the loss or impending loss of availability of a system resource to its users, and the isolation of the detected problem to the failing hardware, software, or microcode component.

Problem diagnosis - the determination of the specific cause of a problem and the action required to resolve it. Diagnostic data gathered during problem determination provides input to this step. It may be necessary to gather and analyze additional information to complete problem diagnosis.

Problem reporting - logging or calling the appropriate group (for example, a help desk) to have a problem logged for follow-up and solution.

Problem bypass and recovery - the bypass of a failure, if necessary, until a problem can be resolved. The decision to bypass a failure is determined by the criticality of the lost resource and the cost of providing the bypass. If continuous operation is a requirement, recovery from a problem must take place immediately following problem determination and diagnosis. Bypass and recovery procedures should be automated whenever possible.

Problem assignment - directing the problem to the proper resolver, as defined by enterprise policy.

Problem resolution - the action taken to correct a problem. Once a problem is resolved, any steps taken to bypass it may be undone and the original resources placed back in service

Problem tracking and control - tracking of problems from detection until their final resolution. Many symptoms may result from the same problem, and different problems may be related. Problem tracking allows the correlation of related symptoms and problems and helps to ensure timely recovery. Escalation of problems that exceed the established policies is a critical part of this step.

Problem closing - specific notation that the problem has been solved to the satisfaction of the reporter. Problem cause and type must be noted for management analysis.

Problem analysis - analyzing problem trends to reduce the number and impact of problems is a required management activity.

30.3.3Methodology

As with change management, problem management depends upon the keeping of records about previous activities - in this case, problems that have been reported or discovered. The problems can be reported by end users who find anomalous behavior, system operations personnel, application programmers, or systems programmers. Automation can also be used to report problems - for example, if a critical job abends, NetView can detect this and create a problem record in TME 10 Information Management, and can also monitor and update the problem record as other detectable events occur, or at defined time intervals.

It is important that all problems be recorded in a file or database. This will serve as a repository for all reported problems, their current status, and their ultimate resolution, whether resolved by application change, system software change, vendor provided maintenance, or other. As the problems are worked toward resolution, the problem management database must be kept up-to-date. Many smaller OS/390 installations simply use TSO/ISPFs editor to create,

462VSE to OS/390 Migration Workbook

Page 486
Image 486
IBM OS/390 manual Tasks

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.