BMC AMI Ops Reviews

BMC AMI Ops is our main tool for monitoring and managing the z/OS mainframe environment day-to-day. We primarily use it to monitor system performance, identify issues or abnormal activity, and check the status of mainframe resources. It helps us quickly identify potential problems before they affect applications or users.

Recently, we used BMC AMI Ops to investigate a performance issue on the mainframe. We noticed unusual resource usage and used the monitoring views to identify which system resources were contributing. This helped the support team narrow down the cause quickly and take corrective action before it had a wider impact.

BMC AMI Ops is mainly part of our regular mainframe monitoring. It gives us a quick view of system health and helps the team identify performance or resource issues during day-to-day operations.

BMC AMI Ops has mainly helped us improve the visibility and responsiveness of our mainframe. The team can monitor system health and resource usage, which makes it easier to notice unusual activity and investigate issues before they become larger operational problems. It also improved troubleshooting because the support team has more information available when a performance issue occurs. Instead of spending as much time collecting information from different places, we can use the monitoring views and alerts to narrow down the affected area and start the investigation. Overall, it has helped make our operations more stable and reduced the time spent on identifying the initial cause of some issues.

We have not tracked a specific percentage reduction in downtime, but we have seen an improvement in how quickly the team can respond to issues. When there is a sudden CPU or resource-related issue, the monitoring information and alerts help us identify the affected area much faster than relying only on manual checks. The main benefit is the reduction in the initial investigation. The team can see the current system condition, identify the abnormal activity, and start troubleshooting with the available information. Thus, it helps us resolve issues more efficiently and reduce the risk of performance problems affecting end users.

The monitoring and real-time visibility are the features I found most useful in BMC AMI Ops. We can quickly check CPU and system resource usage, identify unusual activity, and drill into issues when there is a performance problem. The alerts and different monitoring views also make day-to-day troubleshooting very easy.

The alerts in BMC AMI Ops help the team notice abnormal resource usage or performance issues early, instead of waiting for a user to report a problem. The real-time views give us the current system status, which is useful when investigating an issue. The troubleshooting tools are generally easy to use once you are familiar with the different views. Although, new users may need some time to get comfortable with the interface.

BMC AMI Ops provides good visibility across different aspects of the mainframe environment, rather than requiring us to rely on separate monitoring tools for everything. The different monitoring views make it easier to move from higher-level system information to more detailed information when investigating a problem. I also find the historical information useful for troubleshooting recurring performance issues. We can compare what is happening currently with the activity and use that information during analysis. There is a learning curve for users who are new to the product, but once the team becomes familiar with the monitoring options, it becomes a useful part of operations.

BMC AMI Ops is useful for monitoring, but the interface can take some time for new users to understand. I would prefer to see a more modern and intuitive UI with simpler navigation. The product could also make troubleshooting easier by providing more consolidated information. Better dashboards and more customizable alerts would help the team focus on the most important issues without having to move to multiple screens. Improved documentation and more guided workflows for common troubleshooting scenarios would also be helpful for new users.

Another important improvement would be making the product easier for new team members to learn. Some of the monitoring options and views take time to understand, especially when troubleshooting an unfamiliar issue. A more simplified dashboard, clearer navigation, and better guidance around alerts would make the day-to-day experience smoother. It would also be useful to have more flexibility in customization, so each team can focus on the metrics and alerts that are most relevant to their environment.

I have been using BMC AMI Ops for one year.

BMC AMI Ops is stable.

BMC AMI Ops has handled our existing mainframe monitoring requirements well as the workload and system activities change. We have not experienced major scalability issues in our environment. This is useful because we can monitor the system resources and workload from the same environment as activity increases. For a larger or more complex environment, proper configuration and tuning would still be important to maintain good monitoring performance as the environment grows.

We have reached out to the BMC support team when we needed help with the product configurations. Overall, the support experience has been satisfactory. The support team was helpful in understanding the issue and guiding us through the troubleshooting process. For more complex mainframe-related issues, the resolution can sometimes require additional investigation and back-and-forth communication. However, having BMC support available is useful when the internal team needs assistance with configuration or troubleshooting.

We did not make a direct switch from another comparable solution, so I would not want to make a comparison based on assumption. BMC AMI Ops is part of our existing mainframe monitoring. We use it for performance visibility and troubleshooting.

The initial setup requires some planning around the environment and licensing requirements. I don't have the exact licensing cost available to provide. From an implementation perspective, the main effort was getting the monitoring configuration fine-tuned with our existing mainframe environment rather than basic installation itself.

We have not measured a specific financial ROI or headcount reduction from BMC AMI Ops, so I would not put an exact amount on it. The main benefit is time saved during monitoring. For example, when there is an unusual CPU or resource utilization issue, the team can use the monitoring information to quickly identify the affected area instead of spending as much time on manual investigation. The value for us is mainly in faster issue identification, more efficient troubleshooting, and better visibility into the mainframe.

The pricing and licensing are more suitable for organizations that require a base for enterprise-level mainframe.

We looked at the available options for mainframe monitoring before selecting BMC AMI Ops, comparing them based on the monitoring coverage, performance visibility, alerting, and how well they fit in our existing OS infrastructure. The main consideration was having a solution that would provide detailed system monitoring and support day-to-day troubleshooting without requiring major changes to our existing environment. BMC AMI Ops fit our operational requirements.

I would recommend first defining what you need to monitor and which mainframe resources are most important to your team. BMC AMI Ops provides a lot of monitoring information. Spending some time on the initial configuration and learning the different views will make the product much easier to use. I would also suggest starting with the key alerts and performance views that the operation team actually needs, rather than trying to configure everything. Once the team becomes comfortable with the product's monitoring features, it can become a useful part of regular monitoring. My overall review rating for BMC AMI Ops is ten out of ten.

On-premises

We usually use BMC AMI Ops to automate tasks as described, and there are a couple of batch files running in the tool itself which we monitor for the health of the servers that are being assigned to the agents in BMC AMI Ops.

We can take one example of a job that is being done on BMC AMI Ops, which is a file transfer job. Before file transfer happens, there is one job called file watcher that watches the file at a specific location on the server. Once the file is received at the path, it gives commands to the next job, which is a file FTP job to transfer that file. Once successful transfer is done, it removes the source file and marks the job as completed.

The file watcher and file transfer combination is really helpful to accomplish our tasks. As an SME, we do not know when we are going to receive a file from our offshore clients, so we need to have it monitored to a certain window or time accordingly to process the further steps.

There is a job feature called Azure jobs that we were not aware of earlier. It supports cloud pipelines jobs directly integrated with BMC AMI Ops. We are under exploration of that and have experimented with the jobs to run Azure pipelines, which is almost on the verge of successful completion. It is a new feature, and there are a couple of areas we have not explored yet, but as of now, Azure pipeline is helpful.

There are three different sections in BMC AMI Ops: define mode, monitoring mode, and others. In the monitoring section, there are varieties of things to be monitored on the dashboard itself. You can customize it and get all the information on one panel, which is usually helpful because you can see everything at one glance, reducing the time and allowing you to take action accordingly.

If you are going to check all of the monitoring sections individually, it usually takes around five minutes to check one section, so it would take around fifteen minutes total. However, using it on one dashboard and checking all of the monitoring sections at once lets us save up to half an hour, compared to checking ten monitoring tasks manually.

We usually use automation in day-to-day executions. For example, we have tasks where files are delivered by offshore teams to us, and we can read the files, check for errors, and execute SQL queries to check for the desired output, confirming whether it is successful. If it is not, it presents the error indicating that it is not the desired output we expect. Automation is used daily and helps streamline our processes significantly.

Cost is monitored by the number of job executions, which helps us understand what is really required. Previously, using automation tools, we ran all jobs across all environments, such as dev, test, and production. However, after learning from IR management that we pay for every job execution, we collaborated with SMEs to rectify unnecessary executions and streamline our operations according to necessity.

BMC AMI Ops has been in use at our company for more than a year.

We were previously using CA workload automation tool before BMC AMI Ops. There were certain limitations with that tool, and we have been using BMC AMI Ops since a year or more than that. It has broader features, helps streamline our processes smoothly, and it has zero downtime while upgrading and better notification, which is really helpful for us.

Earlier we only had notifications on the failure of completions, but with BMC AMI Ops, we have a couple of features in the notification part that allow us to add the group and assign a couple of team members to that group, and it triggers the notifications accordingly. For example, if a job is getting failed or stuck somewhere during execution and takes longer than expected, it triggers the notifications. We have notification categories, such as notifying within BMC AMI Ops window and email notifications, and these features usually help us.

We have used a BMC AMI Ops AI feature called jet, which usually helps in the monitoring mode, but not in the defined mode. There are certain limitations, and with the help of AI, we can give commands or prompts to get things executed, which has been really helpful so far.

The accuracy and reliability in the monitoring mode of BMC AMI Ops are quite good.

BMC AMI Ops provides a better experience in operations. In terms of system health visibility, we can have the monitoring section in one dashboard, which is quite good and handy for reviewing all of the monitoring aspects in the system and subsystems.

It reduces the time and minimizes the chance of human error that occurs when we monitor things manually. If we correctly prompt the AI and give the right command, it executes the tasks as we want, which has usually been helpful for us.

It is really hard to say if there are any improvement areas or not, but every software has improvement areas that should be found out. As of now, I do not have anything in mind, so it would be difficult to specify. I do not have any small improvements or wishes for future updates at this time.

There are a couple of features in BMC AMI Ops, and it has plenty of features, but it is really difficult to understand as a new BMC AMI Ops user. We should go through a couple of training sessions to understand the various features available in the define mode, monitoring mode, agent mode, and all of these aspects. It is a bit difficult to track everything, but there are always certain improvement areas in software.

I have been working with BMC AMI Ops since twenty twenty four.

BMC AMI Ops is stable as of now.

BMC AMI Ops is scalable. If we encounter any limitations, we contact BMC AMI Ops support team. They provide solutions, and if they do not have one, they contact the development team to address our scaling needs.

Customer support is good, but sometimes we receive less interactive solutions, so we occasionally do not get the answers we need. We need to have a couple of conversations and often receive solutions later.

I previously used a different solution before BMC AMI Ops.

We were using CA workload automation tool and I previously shared certain limitations of that tool which was on premises and caused larger downtimes during upgrades. In contrast, BMC AMI Ops is cloud-based and helps us integrate wherever we want in the cloud, which is significantly helpful.

BMC AMI Ops has plenty of features, but it is really difficult to understand as a new BMC AMI Ops user. We should go through a couple of training sessions to understand the various features available in the define mode, monitoring mode, agent mode, and all of these aspects. It is a bit difficult to track everything, but there are always certain improvement areas in software.

It is quite helpful, and I would suggest others use BMC AMI Ops. Use all the features carefully because it has a large amount of functionalities that can help ease tasks and enable error-free execution of automations.

BMC AMI Ops is quite good, and while we have used the tool so far, I can suggest others use it to automate tasks. I would rate this solution an eight overall.

Public Cloud

Amazon Web Services (AWS)

My main use case for BMC AMI Ops is to monitor the health and performance of our maintenance to keep the system running optimally. It helps us detect issues, monitor system resources, and ensure critical business applications run smoothly.

I can provide a specific example of how I have used BMC AMI Ops in my day-to-day work. Recently, we noticed CPU utilization was much higher than normal during peak business hours. Because of BMC AMI Ops, we received an immediate alert and identified that our workload was utilizing maximum CPU. We resolved the issue before any users were impacted.

To monitor everything effectively, I need to keep an eye on my CPU and any utilization patterns.

BMC AMI Ops offers excellent features including real-time monitoring, performance dashboard, and intelligent alerts, plus the automation capabilities we are using. It is easily accessible with visibility across multiple systems.

I rely most heavily on the performance dashboard and real-time monitoring. The real-time monitoring and alerts keep us informed about problems immediately rather than waiting for users to report issues.

BMC AMI Ops has impacted my organization very positively, primarily in terms of timing. Our manpower previously was required to investigate issues, which took considerable time just to identify the problem. Now we identify issues very early and solve them immediately.

The positive outcomes include mainly reduced downtime and improved efficiency of our manpower. Earlier, when users reported high-priority issues, we had to spend extensive time investigating, resulting in system downtime. Now everything is much easier with BMC AMI Ops.

Regarding BMC AMI Ops's AI capabilities, I believe its governance and security are very strong. We are currently handling almost eighty percent of our projects with it, and it is very stable with enterprise-level performance, including strong role-based access and monitoring capability.

BMC AMI Ops is very reliable. The monitoring data is accurate, and the alerts are very specific and timely.

BMC AMI Ops can be improved by offering a more modern user interface and better dashboard customization. While we can customize the current interface, it could be more robust. Additionally, more cloud integration is necessary.

I have been using BMC AMI Ops for the last year.

BMC AMI Ops is very stable.

Its scalability is very strong. Currently, we are using it for one to three systems, and it remains very stable and scalable.

The customer support is very good. Previously, we faced an issue and contacted the team, and they were very helpful.

I see a return on investment based on time. It reduces time requirements by almost fifty to sixty percent.

My experience with pricing, setup cost, and licensing is that the pricing is quite reasonable, making it accessible for new firms looking to get started with it.

I would rate my experience with using BMC AMI Ops for monitoring the health of my whole system as very effective, providing a unified view across all mainframe systems. This allows us to detect issues faster and more accurately, thus reducing the time spent by manpower trying to find problems while shifting between different monitoring tools.

We are using the observability and AIOps-driven early detection feature in BMC AMI Ops, which helps us detect any abnormal activities in the integrated systems, and it is very helpful.

We have not yet used the integrated monitoring, automation, and OpenTelemetry features in BMC AMI Ops.

In my experience, BMC AMI Ops has helped improve mean time to detection. I can provide a recent example. Earlier, it took considerable time to identify errors, but during peak business hours, we faced an issue with CPU usage that was blocking somewhere. We managed to solve it without any downtime or affecting users.

We have not tested any other tools.

We have not evaluated any other options before choosing BMC AMI Ops.

My advice for others considering BMC AMI Ops is that if you are a new startup looking for data security and securing your CPUs to gain visibility, this tool is very reliable and worth implementing.

I would rate my overall experience with BMC AMI Ops as a nine out of ten.

I have been using BMC AMI Ops for one and a half years.

My main use case for BMC AMI Ops is mostly for automation, specifically different kinds of job automation. Depending on the conditions that match, there are scripts that need to be run. With the help of this tool, we run multiple scripts when the conditions are satisfied.

An example of how I use BMC AMI Ops for automation is that my job is not focused on scheduling or creating any job. My job is very limited to rerunning, restarting, and troubleshooting jobs. Although I have never automated any job, I have exposure to automating a small job. For instance, if the conditions are satisfied, we need to run a particular script, and there, we can use BMC AMI Ops.

I don't have anything else to add about my main use case or any other ways BMC AMI Ops helps me in my role because my role is very limited.

Regarding BMC AMI Ops's AI capabilities, I haven't used the AI feature extensively. However, I was impressed by what I saw at a BMC roadshow concerning how the AI works. I don't have much interaction with BMC AI so far, so I can't comment much on that.

Since I don't have much interaction with the AI in my day-to-day work with BMC AMI Ops, I prefer not to comment on its accuracy and reliability of output.

In my opinion, the best features BMC AMI Ops offers are all the features, as I like them overall. The most important feature is when there is a job that is waiting for some input or prerequisite. We don't have to dig manually a lot; we can just click an option on the job page to find out why the job is waiting, what it is waiting for, and what the prerequisites are.

I use that feature to check job prerequisites or troubleshoot issues quite often, and it does save me a lot of time compared to manual digging. If that feature is not there, I will have to check the neighbors, the successor job, the predecessor jobs, and then check each job and the entire flow. Instead of all that digging, I can simply click on that particular option to get the exact answer I need, regarding why the job is waiting and what needs to be done.

Another feature I rely on often is the viewpoint feature, where we can apply multiple filters and generate reports about various jobs, such as specific folders, applications, sub-applications, and sub-folders. These filters help us get the exact results we want on our dashboard, allowing us to manage the jobs that require our focus. The viewpoint feature is very important.

BMC AMI Ops has positively impacted my organization in multiple ways, especially in automation, as we do not have to manually run or search for or run scripts. When the conditions match, we can simply schedule the jobs, and it will run that script automatically. Without this feature, we would have to keep human resources available to monitor jobs 24/7, matching conditions and running scripts. This automation has helped us significantly.

I can't say how BMC AMI Ops can be improved because my role is very limited, and I have not explored the entire tool in my organization yet, so I can't comment on that.

Regarding needed improvements, by default, when we open a viewpoint, we don't see the jobs in a linear way. If all jobs could be displayed in the correct flow by default, it would be better. For example, Job 1 should run first, then Job 2, and so on. Sometimes, I find Job 1 somewhere down, Job 3 somewhere up, and Job 4 somewhere else. The jobs should be arranged sequentially by default; this could be improved.

BMC AMI Ops is very stable. Whenever there is maintenance work, the tools admin takes good care of it, so there is not much impact on downtimes. Therefore, I would say it's a very stable tool.

Regarding the scalability of BMC AMI Ops, I can say that it is scalable. My organization is a bank, and at the end of every month, some delays occur in the jobs due to a lack of CPU resources. The company is not ready to increase CPU capacity because only at the end of the month are those resources in high demand. I have not worked on scalability much as I'm only responsible for the jobs, but I see the tools admin doing some work behind the scenes to manage resources when more jobs need to be run.

I can't share specific metrics about return on investment, as I'm not the correct person for this query. However, I can say that after deploying this tool, we have saved costs and reduced the need for employees, leading to less manual work.

My advice for others looking into using BMC AMI Ops is to get certified from BMC while using this product. It will really make your life easy and help your organization, especially in the banking and BFSI sectors. Since I am BMC certified, I emphasize the importance of getting good training to effectively use this tool in day-to-day operations. I give this review a rating of 8 out of 10.

Private Cloud

Amazon Web Services (AWS)

BMC AMI Ops' most used cases are to monitor the health and performance of mainframe environments, primarily used for CPU, memory, and system utilizations, as well as for monitoring alerts if there are any higher values than the preferred performance values. We use BMC AMI Ops for monitoring and resource utilization, and it helps in assisting with troubleshooting of any performance issues or it can be used for operations work.

BMC AMI Ops offers real-time monitoring of z/OS systems and related subsystems, providing immediate visibility of the health and performance. It helps for proactive monitoring or alerting of any irregularities or spikes in performance. The automation capabilities reduce the manual work in operational tasks, and root cause analysis helps us determine exactly where the problem started, assisting in resolution to prevent reoccurrence in the future. Real-time monitoring with intelligent alerting of the system and the automations are the standard features that we use day in and day out.

The automation capabilities have reduced the majority of the work that our team used to do manually, as manual processes consume a lot of time and are prone to human error. When it comes to automation, we see the performance has been raised, and clients are also satisfied with the performance. We do not have much downtime or any critical issues that are highlighted which impact the business. Automation has really changed and is a game changer for us.

BMC AMI Ops has had a major impact because we are using it for one of our major clients. The alerting system gives us precise alerts, and based on that we try to fix issues before they lead to a business impact. The client is happy when there is no business impact, which is a really positive thing. The improvements we have seen include a reduction in the FTEs or headcount needed for operations work because of automation, and that has really helped us for cost savings.

The monitoring and integrated monitoring and automation system have improved incident response by providing us with a unified view of the health system and data across the environment. It helps us with real-time monitoring and automated alerts, enabling early detection for the team to effortlessly fix issues before they escalate. Manual efforts have been reduced, allowing us to respond to incidents consistently.

The alerting system could be improved. Sometimes false alerts pop up, so if there is any automation that checks before putting up an alert on our consoles to determine whether it is a genuine alert or a false alert, that would be really helpful and would reduce the time we spend investigating false alerts.

Overall, I find it is well designed, but only two points less because, as I mentioned, a few false alerts still require our resources to investigate other issues, and the graphical representations, UIs, reports, and other aspects need some improvements, indicating a scope for improvement. Graphical representation helps us with better analysis for our business analysts, so that would be an improvement.

I have been using BMC AMI Ops for the past five years.

Security-wise, we do not think there is any breach. On the governance side, everything is going well, and we have not notified any issues reported anywhere while using this application.

The operation experience is solid due to the dependencies across z/OS, CICS, DB, IMS, and MQ, which is helpful. A unified monitoring interface is helpful, and the quick time, centralized dashboards, and alerts across multiple components result in better visibility and operational efficiency.

Visibility into cost and capacity awareness has improved planning and provided insights for MSU usages in the workload, helping us optimize resource utilization. We have cut off four resources based on automation, which controls costs and prevents unexpected system performance issues.

I cannot disclose directly the numbers and figures because they are organization confidential values. However, I can say that previously we had ten FTEs or resources for monitoring and now we have six, so we have cut off four resources, which is the benefit.

Currently, we are not using the observability and AI Ops-driven early detection feature, but we have to implement this as it is not yet in our organization. Currently, we are not using the OpenTelemetry operations, so I have no answers for this.

You have to extend your knowledge and views to maximize the capabilities of BMC AMI Ops. My review rating for BMC AMI Ops is eight out of ten.

I use BMC AMI Ops to maintain its usability for the main team so that the main team can use the product to install it for various clients. BMC AMI Ops is a product that is given to us by a vendor, and we run a couple of jobs called JCL, which is a language in mainframes. Mainframes are a really old kind of technology. In mainframes, we use all these vendor products to help our clients manage their own system.

BMC AMI Ops offers an analysis of the mainframe system. It has automation, AI features, and can keep track of storage, providing a whole analysis of the mainframe system.

I prefer automation the most out of automation, AI features, and storage tracking. I think AI is only going to get bigger as we evolve with technology, and AI is only going to help us grow.

BMC AMI Ops has improved outcomes for my team, and it has definitely improved outcomes for the clients that we serve. The real reason we maintain these products is for our clients.

The client was able to use BMC AMI Ops to track their usage of the system. The client was able to automate a lot of the processes in their system, and that helped them.

I would like to see more AI in BMC AMI Ops, such as an AI feature that lets you keep track of storage in some way, perhaps some kind of automatic disk cleanup.

I have been working here since January of 2026. It has been about a month since I started using BMC AMI Ops.

BMC AMI Ops is stable.

I do not know how BMC AMI Ops's scalability is; the main team would know.

BMC AMI Ops customer support is pretty good, but I have not had any experience with it. I would rate the customer support of BMC AMI Ops an eight on a scale of one to ten.

I am not aware if we previously used a different solution because I actually just started this January of 2026.

I do not deal with the pricing, setup cost, and licensing for BMC AMI Ops. I am not a salesperson.

The implementation team is something that the client chooses regarding BMC AMI Ops. If the client wants a specific software vendor package, we give it to them.

I would not know if there has been a return on investment because I am not a sales person.

I do not deal with the pricing, setup cost, and licensing for BMC AMI Ops. I am not a salesperson.

I am not aware if we previously used a different solution because I actually just started this January of 2026.

I would not really know how BMC AMI Ops's observability and AI Ops-driven early detection feature has helped in identifying abnormal behavior early because I think the main team really uses the features. I am just aware of the features.

Only the main team would know the real usage of the integrated monitoring, automation, and open telemetry features in BMC AMI Ops. I only know the features.

I assume BMC AMI Ops has helped in improving mean time to detection, MTTD because the main team usually says that it was implemented well.

I do not really know other companies and how they use BMC AMI Ops, but I am sure it is a great product.

I liked this interview because I got to see how AI works. I would appreciate a short poem or haiku that will summarize my review. My overall review rating for BMC AMI Ops is eight.

On-premises

Other

My main use case for BMC AMI Ops is daily monitoring activities, checking alerts, system health, or job status.

BMC AMI Ops offers excellent features including the monitoring dashboard and alerts, which I appreciate even though I only used them at a basic level.

BMC AMI Ops positively impacted my organization during the evaluation phase. The main benefit was improved visibility into the mainframe environment, providing a clear view of alerts and system status.

My experience with BMC AMI Ops was limited, but during this evaluation, I believe it could be improved by making some features easier for new users to understand, probably with better guidance or more practical examples.

I have been using BMC AMI Ops for just a few months.

BMC AMI Ops is stable for the short time that I used it.

I don't have much information about BMC AMI Ops's scalability.

I have never interacted with customer support for BMC AMI Ops, so I cannot evaluate this.

I never used a different solution before, as this evaluation was not my specific field and was only a test.

I was not directly involved in the deployment process of BMC AMI Ops, so I don't have enough details about the architecture.

I don't have any information about return on investment, and I don't have relevant metrics to share such as fewer employees needed, money saved, or time saved.

I don't have any information about pricing, setup cost, and licensing because I was only involved for a very short time.

I don't believe I evaluated other options before choosing BMC AMI Ops.

I rate BMC AMI Ops an eight out of ten.

I choose eight because I used it for a limited time and found it to be a useful tool, but I don't give a higher score because my experience was very limited.

Regarding BMC AMI Ops's AI capabilities, I don't have enough experience with detailed assessment because my usage was mainly focused on basic monitoring, so I cannot provide more information about the security aspect in depth. I didn't use the AI capability actively, so I cannot provide a deep evaluation based on my monitoring experience.

I can only assess the unified operations experience provided by BMC AMI Ops in terms of system health visibility across mainframe systems and subsystems at a basic level, as my experience was limited. I only found improved visibility into system health for basic monitoring of the system.

I am not using the observability and AIOps-driven early detection feature in BMC AMI Ops. I have not used the integrated monitoring, automation, and open telemetry features in BMC AMI Ops.

BMC AMI Ops has not helped in improving mean time to detection (MTTD), and I don't have any information or example to share.

My advice to others looking into using BMC AMI Ops is to evaluate it based on operational needs and to test it in your own environment, as it can be useful for improving monitoring and visibility. My overall rating for this product is eight out of ten.

We use TM-AE for batch job management. Not only does it help enforce some of our standards, but allows us to control where certain jobs run based on licensed software. The service level and automated capacity manager functions allow us to control priorities, support SLA's and manage our 4HRA and reduce MLC for some software bills.

Software access control (SAC) limits systems where some of our products are not licensed. Again, the automated capacity manager helps manage our workload and reduce priorities of discretionary work so the critical path batch jobs are completed within the policy defined at our site.

Job binding services (JBS) is used by SAC, but also helps with our datas sharing environments. Any job can have multiple affinities (like SCHENV on steroids) associated to allow the job to run in a JESMAS and find all of the resources on a particular LPAR to satisfy requirements.

Our scheduler managed batch has standard checking prior to promotion. Enforcement of JCL standards for end user desktop submitted jobs has been very positive. We change processes (especially SYSOUT classes) based on standards to manage output.

There currently is a WUI that allows an operator a single pane of glass to see how TM is performing to meet service policies within a JESMAS environment. This is a new feature and multiple individuals have expressed desire to not only see real time monitoring, but the ability to historically go back at least several hours or possibly an entire day to review history.

Three to five years.

There have been little or no issues with the software as delivered.  We maintain the ability to run directly under WLM without TM if needed, but manage ALL batch via TM to make sure we receive maximum value from the tool.

TM can run on a single member or multiple member JESMAS configuration.

All cases are responded to in a timely manner.  The always provide valuable feedback or immediate solutions to an issue.

No, prior to data sharing and other initiatives we exploited a single affinity SCHENV and only scheduled batch processing was managed for standards.

Installed product in couple of hours.  The time has been spent creating and modifying policies along with the job action language coded to exploit functions. 

The vendor team met with us weekly to make sure we had the resources and answers to make our install successful.

Batch smoothing our 4HRA and implementation of group capacity profiles has allowed us to run sub-capacity and lower our MLC.  

The TM team was very helpful getting us started.  They provided a detailed project plan as a guide to successful implementation.  Installing the software is very easy, but the time is spent building you policies for service levels, capacity management and action code language used to tie all of the components together.

No

MainView is used as a central point of view to control and monitor systems on the mainframe like z/OS, CICS, MQSeries IMS, or DB2. 

MainView has enabled me, in the past, to solve production problems faster, or even avoid them preemptively with warnings.

The integration of IMS commands is very useful, because you do not have to switch to another tool to problem solve solutions.

More visualisation and support for mobile devices would be good. An expansion for distributed systems would be great, but probably not workable.

We did use IBM OMEGAMON, but switched to BMC MainView, because it is easier to use, more flexible, and it also came in a software package.

If you already use other products from BMC, you might be able to get a package deal from BMC's sales department.

Yes, we had IBM OMEGAMON, but decided against continuing to use it, because BMC MainView was more valuable.