Question 1

What did ASG-VM Contention Monitor do?

Accepted Answer

ASG-VM Contention Monitor was designed to identify and analyze resource contention issues within z/VM environments. It provided insights into potential performance bottlenecks caused by virtual machines competing for system resources. The tool helped administrators understand and resolve contention problems to optimize system performance.

Question 2

Was this a system, application, or tool?

Accepted Answer

ASG-VM Contention Monitor was a monitoring tool specifically designed for z/VM operating systems. It was not a general-purpose system, application development framework, or middleware. Its primary function was to provide detailed monitoring and analysis of resource contention within the z/VM environment.

Question 3

What types of organizations used this?

Accepted Answer

Organizations that relied on the z/VM operating system for their virtualized environments would have found ASG-VM Contention Monitor useful. These organizations typically included large enterprises with significant mainframe infrastructure, such as those in the financial, insurance, and government sectors. Any company using z/VM and needing to optimize the performance of their virtual machines was a potential user.

Question 4

When should a company have considered ASG-VM Contention Monitor?

Accepted Answer

Companies should have considered using ASG-VM Contention Monitor when they experienced performance degradation in their z/VM environments, particularly when suspecting resource contention among virtual machines. Identifying and resolving these contentions could lead to improved system responsiveness and efficiency. If performance bottlenecks were impacting critical applications, this tool could help pinpoint the root causes.

Question 5

What are the alternatives to ASG-VM Contention Monitor?

Accepted Answer

Alternatives to ASG-VM Contention Monitor include other mainframe performance monitoring tools such as Info/CPU, SYSVIEW, and Rocket TMON PA for z/OS. These tools offer similar capabilities for monitoring and analyzing system performance, including resource contention. Each tool has its own strengths and weaknesses, so organizations should evaluate their specific needs when choosing a replacement.

Question 6

What infrastructure was required?

Accepted Answer

ASG-VM Contention Monitor required a z/VM environment to operate. It was designed to run within the z/VM operating system and monitor its resources. No other specific operating systems were required, but it needed the standard z/VM infrastructure, including the hypervisor and virtual machines.

Question 7

For mainframe products: Did this run in an LPAR?

Accepted Answer

As a mainframe product, ASG-VM Contention Monitor ran within an LPAR (Logical Partition) on the mainframe. It was not directly dependent on z/OS, but it operated within the z/VM environment, which could coexist with z/OS on the same physical mainframe. It did not require specific z/OS subsystems.

Question 8

Was this a standalone product?

Accepted Answer

ASG-VM Contention Monitor was a standalone product designed to enhance the monitoring capabilities of z/VM. It did not extend or enhance another specific ASG product, but it could integrate with other monitoring and management tools in the environment. It provided specialized insights into resource contention that might not be available in generic monitoring solutions.

Question 9

What other products or components had to be present for this to work?

Accepted Answer

ASG-VM Contention Monitor required the z/VM operating system to be present. It also needed the standard z/VM components, such as the Control Program (CP) and the Conversational Monitor System (CMS). The tool interacted with these components to gather performance data and identify resource contention issues.

Question 10

What was the business value of ASG-VM Contention Monitor?

Accepted Answer

The primary business value of ASG-VM Contention Monitor was its ability to improve the performance and efficiency of z/VM environments. By identifying and resolving resource contention issues, organizations could reduce bottlenecks, improve application responsiveness, and optimize resource utilization. This led to cost savings and better service levels.

Question 11

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

Accepted Answer

Without ASG-VM Contention Monitor, organizations might have struggled to identify and resolve resource contention issues in their z/VM environments. This could lead to performance degradation, application slowdowns, and inefficient resource utilization. Troubleshooting performance problems could become more difficult and time-consuming, potentially impacting business operations.

Question 12

When was this product a good fit?

Accepted Answer

ASG-VM Contention Monitor was a good fit for organizations that heavily relied on z/VM for their virtualized environments and needed detailed insights into resource contention. It was particularly useful for companies running critical applications on z/VM and requiring optimal performance. However, it was not a good fit for organizations that did not use z/VM or had minimal virtualization needs.

Question 13

What specific security features did ASG-VM Contention Monitor have?

Accepted Answer

Specific security features of ASG-VM Contention Monitor are not available. However, mainframe environments typically rely on robust security measures provided by the underlying operating system and security software. Access to monitoring data and administrative functions would be controlled through these existing security mechanisms.

Question 14

What authentication methods were supported?

Accepted Answer

ASG-VM Contention Monitor would have leveraged the existing authentication methods provided by z/VM. This likely included standard mainframe authentication mechanisms such as RACF (Resource Access Control Facility) or similar security systems. User authentication was essential to ensure that only authorized personnel could access monitoring data and administrative functions.

Question 15

What access control model was used?

Accepted Answer

The access control model used by ASG-VM Contention Monitor would have been based on the security features of z/VM. This likely involved Role-Based Access Control (RBAC), where users were assigned roles with specific privileges. These roles determined which monitoring data and administrative functions users could access. Mainframe security systems like RACF often implement RBAC.

Question 16

How was this product typically deployed?

Accepted Answer

ASG-VM Contention Monitor was typically deployed on-premise within the organization's mainframe environment. It was installed directly on the z/VM system and integrated with the existing infrastructure. Cloud, hybrid, and SaaS deployment models were not applicable, as it was specifically designed for on-premise z/VM environments.

Question 17

What level of technical expertise was required to implement it?

Accepted Answer

Implementing ASG-VM Contention Monitor required a moderate level of technical expertise. Mainframe systems programmers or administrators with experience in z/VM were needed to install, configure, and maintain the tool. Understanding z/VM performance concepts and resource management was essential for effective use.

Question 18

What ongoing operational requirements existed?

Accepted Answer

Ongoing operational requirements for ASG-VM Contention Monitor included monitoring the tool's performance, maintaining its configuration, and ensuring its integration with the z/VM environment. Regular reviews of the monitoring data were necessary to identify and address resource contention issues. Staffing requirements included trained personnel to operate and interpret the monitoring data.

Share Your Product Experience

ASG-VM Contention Monitor

Product Overview

Frequently Asked Questions

What did ASG-VM Contention Monitor do?

Was this a system, application, or tool?

What types of organizations used this?

When should a company have considered ASG-VM Contention Monitor?

What are the alternatives to ASG-VM Contention Monitor?

What infrastructure was required?

For mainframe products: Did this run in an LPAR?

Was this a standalone product?

What other products or components had to be present for this to work?

What was the business value of ASG-VM Contention Monitor?

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

When was this product a good fit?

What specific security features did ASG-VM Contention Monitor have?

What authentication methods were supported?

What access control model was used?

How was this product typically deployed?

What level of technical expertise was required to implement it?

What ongoing operational requirements existed?

Related Products

More from ASG Technologies

ASG-APC Performance Desktop

ASG-AutoChange

ASG-Bridge

ASG-Cortex-MS

ASG-Cortex-OMS

ASG-CSD/Auditor

Similar Products

(E)JES

4Tune

ABARS/Assist

ACC

Access 1

ACO SolutionPac

Help Improve This Directory

Share Your Product Experience