Solve:Problem Modernization Guide

Solve:Problem was a problem management system that ran on z/OS. It automated the process of detecting problems from the z/OS console, Netmaster, or Netview, and automatically opened a problem ticket to track the issue.

Solve:Problem was an application designed to automate and streamline problem management processes within a z/OS environment. It provided a centralized system for problem detection, ticket creation, and tracking.

Organizations that relied on z/OS for critical business applications and needed to ensure high availability and rapid problem resolution would have used Solve:Problem. These organizations typically had complex IT environments and a need for automated problem management.

An organization would have considered Solve:Problem when they needed to automate problem detection and ticketing in their z/OS environment, reduce manual effort, and improve response times to system issues. It was particularly useful for organizations with a large number of z/OS systems and applications.

Alternatives to Solve:Problem include other problem management systems and automation tools for z/OS, such as IBM NetView, Broadcom MainView, and various open-source solutions. These alternatives offer similar capabilities for problem detection, alerting, and automation.

Solve:Problem ran on the z/OS operating system and integrated with systems management tools like Netmaster and Netview. It required access to the z/OS console to monitor system messages and detect problems.

Solve:Problem was dependent on the z/OS operating system and required specific subsystems to be active for monitoring and integration. It typically ran in an LPAR (Logical Partition) within the z/OS environment.

Solve:Problem integrated with Netmaster and Netview to receive alerts and events, and to correlate them into problem tickets. This integration allowed for a more comprehensive view of system health and faster problem resolution.

The core components of Solve:Problem included the problem detection engine, the ticketing system interface, and the integration modules for Netmaster and Netview. These components worked together to automate the problem management process.

Solve:Problem provided business value by automating problem detection and resolution, reducing downtime, and improving system availability. It helped organizations to minimize the impact of system issues on business operations.

By automating problem management, Solve:Problem reduced the need for manual intervention, freeing up IT staff to focus on other tasks. This improved efficiency and reduced operational costs.

The integration with Netmaster and Netview provided a centralized view of system health, allowing for faster problem identification and resolution. This improved overall system stability and reduced the risk of major outages.

Solve:Problem helped organizations to meet service level agreements (SLAs) by ensuring that problems were detected and resolved quickly. This improved customer satisfaction and reduced the risk of penalties for failing to meet SLAs.

Solve:Problem used the security features of z/OS to control access to problem management data and functions. It supported standard z/OS authentication methods to verify user identities.

Access to Solve:Problem functions and data was controlled through z/OS security mechanisms, such as RACF (Resource Access Control Facility). This ensured that only authorized users could access sensitive information and perform critical operations.

Solve:Problem logged all significant events and actions, providing an audit trail for security and compliance purposes. These logs could be used to track user activity and identify potential security breaches.

Solve:Problem leveraged z/OS security features; therefore, encryption methods used were those available within the z/OS environment for data at rest and in transit.

Solve:Problem was typically deployed on-premise within the z/OS environment. It required a dedicated LPAR and access to the z/OS console and system management tools.

Implementing Solve:Problem required expertise in z/OS systems management, Netmaster, and Netview. Ongoing operational requirements included monitoring system performance, maintaining the integration with other systems, and managing user access.

Common implementation challenges included ensuring compatibility with existing z/OS systems and applications, configuring the integration with Netmaster and Netview, and training IT staff on the new system.

Ongoing operational requirements included monitoring system performance, reviewing logs for potential issues, and applying updates and patches as needed. Regular maintenance was essential to ensure the continued stability and reliability of the system.