BMC AMI Ops Automation for Capping Modernization Guide

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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

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.

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.

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.

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

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.

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.

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.