What are some common commands and their syntax?

Common commands include MODIFY (to dynamically adjust capping parameters), DISPLAY (to view current capping status), and REFRESH (to reload configuration parameters). For example: `MODIFY CAPxx,ADJUST=nn` adjusts the capping value.

What protocols and APIs are used for integration?

The product uses TCP/IP for communication between components. It does not expose a public REST API. Integration typically occurs through SMF data sharing or operator command interfaces.

How do the system components communicate?

The Capping Engine communicates with the z/OS system via SVC calls to enforce capping. The SMF Data Collector reads SMF data from the SMF datasets. The Policy Manager updates the Capping Engine's parameters via internal communication mechanisms.

What databases or storage mechanisms are used?

The product uses parmlibs for configuration data. SMF data is stored in standard z/OS SMF datasets. No external database is required.

How does this product provide business value?

By dynamically adjusting CPU capacity, the product reduces WLC software licensing costs. This is achieved by optimizing CPU usage and avoiding unnecessary MSU (Million Service Units) consumption during peak periods.

How does the product help with license compliance?

The product helps organizations comply with software licensing agreements by ensuring that CPU usage remains within defined limits. This reduces the risk of unexpected licensing fees and audit penalties.

What reporting capabilities are available?

The product provides detailed reports on CPU usage and capping activities, allowing organizations to track the effectiveness of their capping policies and identify further optimization opportunities. These reports can be generated through the ISPF interface.

What authentication methods are supported?

The product supports authentication via RACF, ACF2, and Top Secret. User access is controlled through these external security managers.

What access control model is used?

The product uses an Access Control List (ACL) model, managed through the external security managers (RACF, ACF2, Top Secret). Access to specific functions and data is determined by the user's security profile.

What encryption is used and where?

The product encrypts sensitive data, such as passwords and configuration parameters, using standard z/OS encryption facilities. Data in transit is secured via standard TCP/IP security protocols.

What audit/logging capabilities exist?

The product provides audit logging of all administrative actions and security-related events. These logs are integrated with z/OS system logging facilities and can be used for security monitoring and compliance reporting.

What administrative interfaces are available?

The product provides a CLI and ISPF interface for administrative tasks. User management is handled through the external security managers (RACF, ACF2, Top Secret).

What are the main configuration parameters?

Key configuration parameters include capping thresholds, MSU limits, and system-specific settings. These parameters are defined in parmlibs and can be dynamically adjusted using the MODIFY command.

What monitoring/logging capabilities exist?

The product provides comprehensive monitoring and logging capabilities. CPU usage, capping activities, and system events are logged and can be monitored through the ISPF interface or via SMF data analysis.

How does the product integrate with z/OS scheduling tools?

The product integrates with standard z/OS scheduling tools such as CA Workload Automation and IBM Workload Scheduler. This allows for automated capping adjustments based on workload priorities and schedules.

Share Your Product Experience

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

Share Your Experience

BMC AMI Ops Automation for Capping

Name: BMC AMI Ops Automation for Capping
Availability: InStock

BMC Active z/OS

Infrastructure and Computing Assets Usage Accounting/SMF

Vendor

BMC

Product Overview

BMC AMI Ops Automation for Capping provides a comprehensive architecture for dynamically managing CPU capacity on z/OS systems, focusing on reducing WLC costs. The core components include: * **Capping Engine:** Enforces capping policies based on real-time analysis. * **Policy Manager:** Defines and manages capping policies, thresholds, and system-specific settings.

* **SMF Data Collector:** Gathers SMF data (types 30, 70, 72, 89, 100) for analysis. These components communicate via TCP/IP and internal communication mechanisms. Configuration is managed through ISPF panels and parmlibs.

The product uses SVC calls to interact with z/OS for capping enforcement. It supports authentication via RACF, ACF2, and Top Secret, using an Access Control List (ACL) model. , `MODIFY CAPxx,ADJUST=nn`), `DISPLAY`, and `REFRESH`.

The system integrates with z/OS system logging for audit trails. Competing products include IBM Workload License Charge Manager. A key architectural advantage is its dynamic CPU adjustment based on workload, which some competitors do not offer.

The system uses parmlibs for configuration data and standard z/OS SMF datasets for SMF data storage.

Frequently Asked Questions

What is the core function of BMC AMI Ops Automation for Capping?

BMC AMI Ops Automation for Capping dynamically adjusts CPU capacity based on workload demands to optimize WLC software licensing costs. It analyzes SMF data to identify capping opportunities and enforces defined capping policies.

What types of SMF records does the product analyze?

The software analyzes SMF records, particularly types 30, 70, 72, 89, and 100, to understand CPU usage patterns and identify potential capping opportunities. It uses these records to determine optimal capping levels without impacting critical workloads.

How is the product configured?

The primary configuration interface is through ISPF panels. Parameters are stored in parmlibs, which define capping policies, thresholds, and system-specific settings. Users can also interact with the system through operator commands.

What are the main system components?

The main system components include the Capping Engine, the Policy Manager, and the SMF Data Collector. The Capping Engine enforces the capping policies, the Policy Manager defines and manages the policies, and the SMF Data Collector gathers the necessary SMF data.

Related Products

View Details →

AutoSoftCapping

Active

by ZETALY

z/OS

AutoSoftCapping is designed to optimize WLC costs by dynamically managing CPU consumption on z/OS. The core components include the Capping Engine, Policy Manager, and Monitoring...

Infrastructure and Computing Assets Usage Accounting/SMF

View Details →

Beta 93 SMF Reporter

Supported

by Beta Systems

z/OS

Beta 93 SMF Reporter is designed for comprehensive analysis of SMF records on z/OS. The core functionality centers around data extraction, report generation, and data...

Report Generation and Management Tools and Utilities

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

Share Your Product Experience

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

Share Your Experience