What infrastructure was required?

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.

For mainframe products: Did this run in an LPAR?

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.

How did Solve:Problem integrate with Netmaster and Netview?

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.

What were the main components of Solve:Problem?

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.

What business value did Solve:Problem provide?

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.

How did Solve:Problem improve efficiency?

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.

How did the integration with Netmaster and Netview help?

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.

How did Solve:Problem help meet SLAs?

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.

How was security handled in Solve:Problem?

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.

What access control model was used?

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.

What audit/logging capabilities existed?

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.

What encryption was used and where?

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.

How was Solve:Problem typically deployed?

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.

What level of technical expertise was required to implement it?

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.

What were common implementation challenges?

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.

What ongoing operational requirements existed?

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.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Solve:Problem

Name: Solve:Problem
Availability: InStock

CA Technologies Not Supported z/OS

Problem Analysis and Recovery Administration

Vendor

CA Technologies

Product Overview

Solve:Problem was a z/OS-based problem management system designed to automate the detection, ticketing, and initial analysis of system issues. It monitored the z/OS console, Netmaster, and Netview for alerts and events, automatically creating problem tickets and populating them with relevant diagnostic information. This automation reduced manual intervention, improved response times, and facilitated faster problem resolution.

Key architectural components included: * **Problem Detection Engine:** Monitored z/OS console, Netmaster, and Netview for alerts. * **Ticketing System Interface:** Created and updated problem tickets in a central repository. * **Integration Modules:** Facilitated communication with Netmaster and Netview using proprietary protocols.

Solve:Problem is no longer supported. Organizations should migrate to alternative solutions. IBM NetView and Broadcom MainView are viable options for z/OS environments, offering similar capabilities and integration points.

These alternatives typically support standard protocols for communication and data exchange, such as SNMP and REST APIs. Migration involves reconfiguring monitoring rules, updating integration scripts, and retraining operations staff.

Frequently Asked Questions

What did Solve:Problem do?

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.

Was this a system, application, or tool?

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.

What types of organizations used this?

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.

When should an organization have considered Solve:Problem?

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.

What were the alternatives to Solve:Problem?

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.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience