Metamon Live Modernization Guide
Metamon Live is a problem analysis and recovery product by Cue-Metamon. Explore technical details, modernization strategies, and migration paths below.
Product Overview
Metamon Live is a tool set designed to debug COBOL and Assembler batch programs running on z/OS.
Configuration files are used to define debugging parameters and user access controls.
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 Metamon Live do?
Metamon Live is a debugging tool for batch COBOL and Assembler programs running on z/OS. It allows developers to analyze and resolve issues in real-time as the programs execute. This helps to reduce downtime and improve application performance.
Is this a system, application, or tool?
Metamon Live is a tool set designed for debugging and problem analysis. It provides functionalities to monitor, trace, and diagnose issues within batch applications.
What types of organizations use this?
Organizations that develop and maintain batch COBOL and Assembler applications on z/OS mainframes benefit from Metamon Live. This includes enterprises in finance, insurance, and government sectors.
When should we consider Metamon Live?
A company should consider using Metamon Live when they experience frequent issues with their batch COBOL or Assembler programs, leading to delays or failures. It is also useful when migrating or modernizing legacy applications.
What are the alternatives to Metamon Live?
Alternatives to Metamon Live include other debugging tools and application performance management (APM) solutions for z/OS, such as IBM Debug Tool for z/OS or Compuware Topaz. These tools offer similar debugging and analysis capabilities.
Technical
For mainframe products: Does this run in an LPAR?
Metamon Live runs on the z/OS platform and is dependent on the operating system's services and subsystems. It typically operates within an LPAR (Logical Partition) on the mainframe.
What infrastructure is required?
Metamon Live requires a z/OS environment with the necessary subsystems and libraries to support COBOL and Assembler program execution. It may also require specific security configurations to access program data.
What configuration files are used?
Metamon Live uses configuration files to define debugging parameters, data sources, and user access controls. These files are typically maintained by system administrators or security personnel.
How is user management handled?
Metamon Live integrates with existing security systems on z/OS, such as RACF, ACF2, or Top Secret, to authenticate users and control access to debugging functions and data. It leverages these systems for user management and authorization.
Business Value
What is the business value of Metamon Live?
Metamon Live helps organizations reduce the time and resources spent on debugging batch COBOL and Assembler programs. By providing real-time analysis capabilities, it enables faster problem resolution and minimizes application downtime.
What would happen if an organization did NOT use this product?
Without Metamon Live, organizations may face increased costs associated with debugging and resolving issues in batch applications. This can lead to delays in processing critical data, impacting business operations and customer service.
How does this product integrate with enterprise ecosystems?
Metamon Live integrates with enterprise ecosystems by leveraging existing security systems and data sources on z/OS. It can also integrate with other monitoring and management tools to provide a comprehensive view of application performance.
Security
What specific authentication methods are supported?
Metamon Live supports authentication methods provided by the z/OS security systems, such as RACF, ACF2, or Top Secret. It leverages these systems to verify user identities and grant access to debugging functions.
What access control model is used?
Metamon Live uses an access control model based on the z/OS security system in place (RACF, ACF2, Top Secret). It assigns permissions to users or groups, controlling their ability to access specific debugging functions and data.
What encryption is used and where?
Metamon Live encrypts sensitive data at rest and in transit using encryption methods supported by z/OS. This includes encrypting debugging data and communication between components.
What audit/logging capabilities exist?
Metamon Live provides audit logging capabilities to track user activity and system events. These logs can be used to monitor security and compliance, and to investigate potential security breaches.
Operations
How is this product typically deployed?
Metamon Live is typically deployed on-premise within the z/OS environment. It requires technical expertise to configure and integrate with existing systems.
What ongoing operational requirements exist?
Ongoing operational requirements for Metamon Live include monitoring system performance, maintaining configuration files, and managing user access. This requires skilled personnel with z/OS and security expertise.
What are common implementation challenges?
Common implementation challenges for Metamon Live include integrating with existing security systems, configuring data sources, and training users on the tool's features. Proper planning and coordination are essential for a successful implementation.
What administrative interfaces are available?
Metamon Live provides administrative interfaces through a command-line interface (CLI) and potentially a graphical user interface (GUI). These interfaces allow administrators to manage users, configure settings, and monitor system activity.
Ready to Start Your Migration?
Download our comprehensive migration guide for Metamon Live or calculate your ROI.