Inside Products z/OS

EE Problem Finder Modernization Guide

Networks and CommunicationProblem Analysis and RecoveryTools and Utilities

EE Problem Finder is a networks and communication product by Inside Products. Explore technical details, modernization strategies, and migration paths below.

Product Overview

EE Problem Finder is a tool designed to analyze Enterprise Extender (EE) traces on z/OS systems.

It allows you to examine EE traffic, identify bottlenecks, and pinpoint errors that may be affecting network performance.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does EE Problem Finder do?

EE Problem Finder analyzes Enterprise Extender (EE) traces to help diagnose and resolve network communication issues on z/OS systems. It provides insights into EE traffic, helping identify bottlenecks and errors.

Is this a system, application, or tool?

EE Problem Finder is a tool designed to analyze specific data related to Enterprise Extender communications. It is not a general-purpose system or application, but rather a specialized tool.

What types of organizations use this?

Organizations that rely on Enterprise Extender (EE) for network communication on z/OS, particularly those with complex network configurations, can benefit from using EE Problem Finder. This includes enterprises in industries like banking, finance, and insurance.

When should we consider EE Problem Finder?

A company should consider using EE Problem Finder when they experience performance issues or communication errors related to Enterprise Extender. It is also useful for proactive monitoring and troubleshooting of EE connections.

What are the alternatives to EE Problem Finder?

Alternatives to EE Problem Finder include general network analyzers and trace tools, but these may not provide the same level of EE-specific analysis. Other options are CleverView for cTrace Analysis and CLEVER Decoder.

Technical

What infrastructure is required?

EE Problem Finder runs on z/OS and requires access to EE traces. It typically operates within an LPAR and relies on z/OS subsystems for data collection and analysis.

For mainframe products: Does this run in an LPAR?

As a z/OS product, EE Problem Finder runs within an LPAR. It is dependent on the z/OS operating system and its associated subsystems for capturing and analyzing EE traces.

What specific data formats does it analyze?

EE Problem Finder analyzes Enterprise Extender traces. The specific format and content of these traces are defined by the EE protocol and z/OS implementation.

What configuration files are used?

EE Problem Finder likely uses configuration files to specify trace input sources, filtering options, and output formats. The exact format and location of these files are product-specific.

Business Value

How does this improve business operations?

EE Problem Finder helps organizations reduce downtime and improve the performance of their Enterprise Extender-based network communications. By quickly identifying and resolving issues, it minimizes disruptions to business operations.

How does this save time and money?

By providing detailed analysis of EE traces, EE Problem Finder enables faster problem resolution, reducing the time and resources required to diagnose and fix network issues. This leads to cost savings and improved efficiency.

Who benefits most from using this product?

Organizations that rely on EE for critical business applications will see the most value. Industries such as banking and finance, where reliable network communication is essential, benefit significantly.

Security

How does this integrate with existing security?

EE Problem Finder operates within the z/OS security environment. It leverages existing z/OS security mechanisms for authentication and authorization. Access to EE traces is controlled by z/OS security policies.

How is access controlled?

Access to EE Problem Finder functions and data is typically controlled through z/OS Resource Access Control Facility (RACF) or equivalent security systems. This ensures that only authorized personnel can access sensitive network information.

What audit logging capabilities exist?

EE Problem Finder likely provides audit logging capabilities to track user activity and access to EE traces. These logs can be used for security monitoring and compliance purposes.

Operations

What level of expertise is required?

Implementing EE Problem Finder requires technical expertise in z/OS and Enterprise Extender. Familiarity with network tracing and analysis techniques is also beneficial.

What are the ongoing operational requirements?

Ongoing operational requirements include monitoring EE Problem Finder performance, maintaining access to EE traces, and ensuring the tool is properly configured to capture relevant data. Regular review of analysis results is also important.

What are common implementation challenges?

Common implementation challenges include configuring EE tracing, ensuring sufficient storage for trace data, and integrating EE Problem Finder with existing monitoring and alerting systems.

What monitoring capabilities exist?

EE Problem Finder likely provides logging and monitoring capabilities to track its own performance and identify potential issues. These logs can be integrated with z/OS system logs for centralized monitoring.

Ready to Start Your Migration?

Download our comprehensive migration guide for EE Problem Finder or calculate your ROI.

Calculate ROI