BMC AMI Ops vs. IBM Z Anomaly Analytics

The best part of AMI Ops for z OS, CICS DB2, or Network management, which I like and prefer to use, is that there are so many very useful Views for almost all purposes, specifically to analyze system performance issues that really impact Business.

Incentivized

• Monitor the health of the system. Alert when the threshold is met such as CPU DASD I/O MVS Storage
• Does a very good job with IMS Reporting and threshold notification. region Looping, high CPU
• Java region Gabbage collection reporting work great with IBM Health center.

Incentivized

• Going back in history must be improved, its not that flexible.
• The current interval in the z OS panel is 1 minute. However, the backward details show 15 15-minute intervals, which is not helpful.
• The job delay reason column should include a more exact reason instead of a general statement.

Incentivized

Because of the overall feature set is has. However I feel there is some room for improvement especially in documentation and wider API integration

Incentivized

BMC AMI Cloud and Data provides a data resiliency solution for the cloud. It is for customers looking to 1. backup their decades-worth of data stored in physical or virtual tapes to Cloud storage (AWS S3), 2. perform analytics and business intelligence to run targeted customers or campaigns on mainframe data now available in the cloud, and 3. use the data as backup/ restore copies in the event of a disaster.

Incentivized

• Negative: Not effective use of archive data for historical displays, it takes much time and hangs.
• Negative: The installation method through the installer is not friendly.
• Positive: CICS issues can be identified, diagnosed and fixed promptly.
• Negative: Applying passcodes is more difficult than desired.

Incentivized