For mainframe products: Does this run in an LPAR?

zMON runs on the z/VM platform. It is not z/OS dependent but operates within the z/VM environment to monitor its performance and resources.

How is zMON typically deployed?

zMON is typically deployed on-premise, within the same data center as the z/VM systems it monitors. It requires a dedicated instance within the z/VM environment.

What infrastructure is required?

zMON requires a z/VM environment to be present. It integrates directly with the z/VM hypervisor to collect performance data. No other specific products are strictly required, but integration with other management tools is possible.

What configuration files are used?

zMON uses configuration files to define monitoring parameters and thresholds. These files are typically edited by system administrators to customize the monitoring behavior.

What business problem does it solve?

zMON provides business value by enabling proactive management of z/VM systems. This leads to improved system availability, reduced downtime, and optimized resource utilization.

What would happen if an organization did NOT use this product?

Without zMON, organizations may experience difficulty in identifying and resolving performance issues in their z/VM environments. This can lead to degraded application performance and increased operational costs.

How does this product integrate with enterprise ecosystems?

zMON integrates with enterprise ecosystems by providing APIs and data export capabilities. This allows organizations to incorporate z/VM performance data into their existing monitoring and reporting systems.

What is the typical licensing model?

The licensing model for zMON is typically perpetual or subscription-based, depending on the vendor's offerings. The total cost of ownership includes licensing fees, implementation costs, and ongoing maintenance expenses.

What specific authentication methods are supported?

zMON supports various authentication methods, including standard username/password authentication and integration with external security systems. The access control model is typically role-based (RBAC), allowing administrators to define granular permissions for different user roles.

What audit/logging capabilities exist?

zMON provides audit logging capabilities to track user activity and system events. These logs can be used to monitor security breaches and ensure compliance with regulatory requirements.

How does zMON control access to sensitive resources?

zMON controls access to sensitive z/VM resources by enforcing role-based access control (RBAC). This ensures that only authorized users can access critical system data and perform administrative tasks.

What level of technical expertise is required to implement it?

Implementing zMON requires technical expertise in z/VM systems and monitoring tools. Ongoing operational requirements include monitoring the zMON system itself, performing regular maintenance, and ensuring adequate staffing to interpret the monitoring data.

What administrative interfaces are available?

zMON provides administrative interfaces through a command-line interface (CLI) and potentially a web-based console. User management is typically handled through the CLI or the z/VM security system.

What are common implementation challenges?

Common implementation challenges include configuring zMON to accurately reflect the specific z/VM environment, integrating it with existing monitoring tools, and training staff to effectively use the system.

What monitoring/logging capabilities exist?

zMON offers monitoring and logging capabilities to track system performance and identify potential issues. These logs can be used to troubleshoot problems and optimize system performance.

Share Your Product Experience

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

Share Your Experience

zMON

Velocity Software Active z/VM

Operating System Monitor

Vendor

Velocity Software

Product Overview

zMON is a system monitoring solution specifically designed for z/VM environments. It provides real-time performance data and historical analysis, enabling architects to design and optimize mainframe systems for maximum efficiency and reliability. zMON helps identify performance bottlenecks, optimize resource utilization, and ensure system availability.

From an architectural perspective, zMON consists of several key components. These include data collectors, a central repository, and a reporting engine. The data collectors gather performance data from the z/VM hypervisor.

The central repository stores the collected data for analysis. The reporting engine generates reports and dashboards. zMON communicates using standard network protocols.

It integrates with existing monitoring and reporting systems through APIs. Alternatives include Info/CPU, SYSVIEW, and Rocket TMON. zMON distinguishes itself by providing a comprehensive view of the z/VM environment, facilitating informed decision-making and efficient resource management.

It supports role-based access control (RBAC) and provides audit logging capabilities.

Frequently Asked Questions

What does zMON do?

zMON is a systems monitor designed specifically for z/VM environments. It provides real-time performance data and historical analysis capabilities to help administrators manage and optimize their z/VM systems.

Is this a system, application, or tool?

zMON is best classified as a system monitoring tool. It provides a comprehensive view of the z/VM environment, enabling proactive management and problem resolution.

What types of organizations use this?

Organizations that rely on z/VM for their mainframe workloads are the primary users of zMON. This includes enterprises in industries such as banking, finance, insurance, and government.

When should we consider zMON?

A company should consider using zMON when they need detailed insights into the performance and health of their z/VM systems. This is particularly important when experiencing performance bottlenecks or when planning for capacity upgrades.

What are the alternatives to zMON?

Alternatives to zMON include Info/CPU, SYSVIEW, Rocket TMON PA for z/OS, and Rocket TMON for z/OS. Each of these products offers similar monitoring capabilities for mainframe environments.

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

Share Your Product Experience

zMON

Product Overview

Frequently Asked Questions

What does zMON do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider zMON?

What are the alternatives to zMON?

For mainframe products: Does this run in an LPAR?

How is zMON typically deployed?

What infrastructure is required?

What configuration files are used?

What business problem does it solve?

What would happen if an organization did NOT use this product?

How does this product integrate with enterprise ecosystems?

What is the typical licensing model?

What specific authentication methods are supported?

What audit/logging capabilities exist?

How does zMON control access to sensitive resources?

What level of technical expertise is required to implement it?

What administrative interfaces are available?

What are common implementation challenges?

What monitoring/logging capabilities exist?

Related Products

More from Velocity Software

Similar Products

Help Improve This Directory

Share Your Product Experience