What infrastructure was required?

DASDMON required a z/OS environment with access to disk subsystem performance data. It typically ran in an LPAR and utilized z/OS system services to collect and analyze performance metrics.

How was DASDMON deployed?

DASDMON was deployed on-premise within the z/OS environment. It was not a cloud-based or SaaS solution. It required installation and configuration on the mainframe system.

What configuration files were used?

DASDMON used configuration files to specify the disks and caches to monitor, as well as the types of reports to generate. These files defined the scope and format of the performance data collected.

What were the main system components?

DASDMON's architecture included components for data collection, analysis, and reporting. These components worked together to gather performance metrics, process them, and present them in a user-friendly format.

What business problems did DASDMON solve?

DASDMON provided business value by helping organizations optimize their disk I/O performance, reduce response times, and improve overall system efficiency. This resulted in cost savings and better service levels.

What would happen without DASDMON?

Without DASDMON, organizations would have difficulty identifying and resolving disk I/O bottlenecks, leading to slower application performance, increased costs, and potential service disruptions.

How did DASDMON help with capacity planning?

DASDMON helped organizations make informed decisions about disk subsystem upgrades and capacity planning. By providing detailed performance data, it enabled them to optimize their investments and avoid unnecessary expenses.

What security features did DASDMON have?

DASDMON's security features included access controls to restrict who could view and modify performance data. It also provided audit logging to track user activity and ensure accountability.

How did DASDMON integrate with z/OS security?

DASDMON integrated with z/OS security systems, such as RACF, ACF2, or Top Secret, to authenticate users and enforce access controls. This ensured that only authorized personnel could access sensitive performance data.

What information was included in the audit logs?

DASDMON's audit logs recorded user logins, report generation, and configuration changes. These logs could be used to investigate security incidents and ensure compliance with regulatory requirements.

What ongoing operational requirements existed?

DASDMON required ongoing monitoring to ensure that it was collecting and reporting accurate performance data. This included checking for errors, verifying data integrity, and tuning the configuration as needed.

What were common implementation challenges?

Implementing DASDMON could be challenging due to the complexity of z/OS environments and the need to understand disk subsystem performance metrics. It required skilled personnel with expertise in both z/OS and disk I/O concepts.

How were reports generated and viewed?

DASDMON generated reports that could be viewed online or printed. These reports provided detailed information about disk I/O activity, cache hit ratios, and other performance metrics.

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

DASDMON

Legent Not Supported z/OS

Disk Performance

Vendor

Legent

Product Overview

DASDMON was a disk performance monitoring solution for z/OS mainframe systems. Its architecture comprised data collection, analysis, and reporting components. The data collection component gathered performance metrics from the z/OS system, including disk I/O activity, cache hit ratios, and response times.

The analysis component processed this data to identify performance bottlenecks and trends. The reporting component generated detailed reports that could be viewed online or printed. DASDMON integrated with z/OS security systems, such as RACF, ACF2, or Top Secret, to authenticate users and enforce access controls.

It used configuration files to specify the disks and caches to monitor, as well as the types of reports to generate. Organizations seeking similar functionality now use alternatives such as IBM's Resource Measurement Facility (RMF), CA Disk, and BMC AMI Ops Monitor for DASD. These tools offer comparable disk performance monitoring capabilities for z/OS environments and often provide more modern architectures and integration options.

Frequently Asked Questions

What does DASDMON do?

DASDMON was a disk performance monitor for z/OS systems. It provided reports on disk and cache performance, helping administrators identify and resolve bottlenecks.

Is this a system, application, or tool?

DASDMON is a system tool designed to monitor and report on disk I/O performance. It is not an application in the traditional sense, but rather a utility that provides insights into system-level operations.

What types of organizations used this?

Organizations that relied on z/OS mainframe systems for critical applications used DASDMON. These were typically large enterprises in industries such as banking, insurance, and government.

When was DASDMON considered?

DASDMON was considered when organizations needed detailed insights into disk subsystem performance on their z/OS systems. This included identifying slow-performing disks, optimizing cache configurations, and planning for capacity upgrades.

What are the alternatives to DASDMON?

Alternatives to DASDMON include IBM's Resource Measurement Facility (RMF), CA Disk, and BMC AMI Ops Monitor for DASD. These tools provide similar disk performance monitoring capabilities for z/OS environments.

Related Products

Adabas Parallel Services

Active

by Software AG

z/OSzVSE/VSEn

Adabas Parallel Services (APS) is designed to enhance the performance of Adabas databases by enabling parallel processing on multi-CPU systems. The architecture comprises the APS...

ADABAS Performance

View Details →

Adabas Review

Active

by Software AG

z/OSz/VMzVSE/VSEn

Adabas Review provides comprehensive performance monitoring for Adabas databases. Key components include the Review Collector, which gathers performance data, and the Review Analyzer, which processes...

ADABAS Performance

View Details →

Adabas Statistics Facility

Active

by Software AG

z/OSz/VMzVSE/VSEn

Adabas Statistics Facility is a key component for monitoring and optimizing Adabas database performance. The system comprises two main parts: the Store Program, which gathers...

ADABAS Performance

View Details →

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

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