BMC AMI Data Reviews

I use BMC AMI Data for detecting abnormal batch behavior, finding DB2 deadlocks, intelligent alert correlation, production support automation, mainframe performance monitoring, capacity planning, AI-based anomaly detection, faster root cause analysis, developer productivity, and finding audit compliance and change tracking.

I primarily use BMC AMI Data for mainframe performance monitoring. In real time, I gain visibility of CICS regions, MQs, DB2 threads, CPU usage, storage, JES initiators, and long running jobs. Our batch processes used to run longer during the nights, so for better monitoring purposes, we implemented this solution. We also experience peak hours during that time. We depend on the CICS regions and ensure they are up and running. Due to the holiday season, this solution helped us process bulk orders without any issues.

Another main use case for me is detecting abnormal batch behaviors. Some jobs were running more than three hours long, some jobs were processing duplicates, and some were creating routes with delays. I compared current execution versus historical patterns using BMC AMI Data and identified unusual CPU and I/O and wait spikes. Additionally, I was able to identify a DB2 object that was causing the slowdown. I was able to find the root cause in minutes instead of hours.

I have used BMC AMI Data many times in my company for day-to-day DB2 data management activities to reduce manual DBA efforts, including space monitoring, reorg recommendations, statistics collection, performance analysis, utility scheduling, and copy and recovery management. SQL tuning insights can also be automated proactively and monitored instead of relying on manual analysis.

With AI-driven anomaly detection, I was able to analyze historical operational patterns and identify abnormal behavior such as sudden batch time runtime increases, unusual DB2 locking and deadlocks, abnormal CICS transaction spikes, unexpected MQ queue buildups, CPU anomalies, and repeating job failures. This helped my operations and support teams detect these issues earlier, reduce the outage impact, and accelerate root cause analysis before business users are affected.

BMC AMI Data's best feature is AI-based anomaly detection. This is one of the strongest features because it can automatically detect abnormal batch runtimes, unusual CICS behavior, DB2 performance degradation, sudden MQ spikes, and storage and CPU anomalies. These capabilities are very useful for my users before issues are noticed. The second valuable feature is glass monitoring. Instead of checking JES, CA7, DB2, and MQ separately, BMC AMI Data provides centralized operational visibility. This is providing significant benefits for my production support teams, command centers, incident managers, and architects. Since I am using it for intelligent event correlation, instead of generating one hundred alerts, BMC AMI Data correlates all the related failures into one incident chain, reducing alert fatigue significantly. It is also helping me find real-time DB2 performance analysis. I am able to automate jobs, suppress alerts, and automate ticket generation with recovery reaching threshold every time I maintain.

My team found predictive analytics to be valuable. Using BMC AMI Data, I am able to identify trends, growth patterns, capacity risks, and recurring failures. With this capability, I am able to plan modernization effectively and prepare for peak season while maintaining scalability properly. Additionally, I am able to integrate modern features including Git integration, pipeline visibility, deployment tracking, automated testing support, and change intelligence. It is helping me modernize the CI/CD features in my system.

I have reduced a lot of incident failures since using BMC AMI Data. I am able to see a significant improvement in CICS transactional response times and overall region health. Additionally, I am able to stop storage violations and transactional bottlenecks that I faced earlier. I used to have task buildups, but I have stopped them. This improvement is very visible in my high-volume real-time environments.

BMC AMI Data monitors technical components very well, but end-to-end business transaction tracing is still limited. For instance, the flow of business transactions from order creation to generation of the ASN is limited. I would say it would be great if cross-system business flow visibility were improved. Moreover, I would say stronger AI root cause accuracy is needed. Current AI capabilities are useful but still heavily rule-based in many environments. I would also suggest having a somewhat easier UI for better user experience, as it remains operational heavy, menu-driven, and less intuitive for new engineers. Cleaner dashboards, drill-down visualizations, interactive topology maps, and easier search or filtering would be beneficial. Additionally, better cloud and hybrid visibility along with native event-driven monitoring would improve the solution.

I feel there are still some features that need improvement. Particularly, business cross-functional visibility and cross-systems visibility need enhancement.

I have been using BMC AMI Data for twenty-four months.

BMC AMI Data is stable. The reliability during high-volume processing tasks holds up well under pressure. There were some times when the batch volume and batch processing in CICS regions were both busy, and getting data to the BMC AMI Data console took time, but this was very limited. Everything else is working well.

BMC AMI Data is good from a data scalability perspective.

The customer support is good. With BMC AMI Data, I am able to manage thousands of DB2 objects, massive transaction volumes, twenty-four seven batch and online workloads, multiple LPARs, and subsystems in hybrid integration environments. From a customer support perspective, I am getting good responses. As soon as I raise a case, they are able to solve it. I would rate the customer support of BMC AMI Data as a nine.

I did not use any other solution. This is the first time I am using BMC AMI Data. Earlier, I was using mainframe inbuilt tools.

Initially, the pricing, setup cost, and licensing were good, but later on, they seem to be increasing. However, as of now, it remains manageable.

When it comes to integration across my mainframe ecosystem, specifically with BMC AMI Ops, AMI Security, and DevOps pipelines, I was able to find it out. I had to work a lot with mainframe engineers to set up user access patterns on the security side. Initially, I faced some access issues for some users, but later I fixed them. From a DevOps perspective, there were some initial challenges to move the source code from mainframe to Git; initially, there were objections, but later I resolved those issues.

Employee productivity has increased. On the employee side, I did not reduce staff, but I saved some money on CPU utilization and storage. I got some return on investment.

I did not evaluate any other options. This is the one I went through.

I would tell others looking into using BMC AMI Data that they will get a return on what they invest. It is helpful and will help maintain a healthy system. I rate this product a nine overall.