What is our primary use case?
BMC AMI DevX is used primarily for mainframe application development and troubleshooting, particularly for COBOL and JCL. I use it to edit and navigate code, browse datasets, and submit jobs, and also to debug application issues.
One example is when a COBOL batch job fails with a SOC7 data exception. I first check the job output and abend details to identify the calling program and statement. Then I use BMC AMI DevX to step through the COBOL program and check the variable values at the point of failure and trace the program flow. This helps me determine whether invalid numeric data or a specific piece of program logic caused the issue. Once I identify the root cause, I make the required changes, test them, and then follow the normal change and deployment process.
How has it helped my organization?
BMC AMI DevX has had a positive impact mainly by improving developer productivity and making mainframe development more accessible. The modern development environment reduces the need to switch between multiple tools for activities such as editing COBOL, browsing datasets, submitting jobs, and debugging. It also helps with newer development work where we work with legacy applications, as experienced developers transition away from traditional green screen workflows. Overall, it has made development and troubleshooting more efficient and provides a more modern way of working with existing mainframe applications.
The clearest measurable impact is faster troubleshooting and faster debugging. For issues where BMC AMI DevX is applicable, the debugging time has been reduced by 20 to 30% mainly because I can step through the COBOL program and check variable values. It has reduced manual effort by bringing code analysis and debugging into a more interactive experience.
What is most valuable?
The most valuable feature is the integrated COBOL debugging and code analysis capability. Being able to step through programs, set breakpoints, and monitor variable values to understand how the program flow operates makes troubleshooting much easier and more structured. I also appreciate the modern development environment for editing COBOL, browsing datasets, and submitting JCL jobs without constantly switching between different tools. The code navigation and AI-assisted code understanding capabilities are also useful for working with unfamiliar legacy applications.
The code understanding features have been useful when I need to work with unfamiliar COBOL applications. They help me explain existing code, identify the relationships and dependencies between programs and copybooks, and make it easier to understand the overall program flow. Instead of manually tracking every section of a large legacy application, I can use the AI assistance to get a quicker understanding of what the code is doing and where a change may have an impact. This reduces the time to get familiar with older code and makes maintenance and troubleshooting more straightforward and efficient.
What needs improvement?
I would suggest making the initial installation and configuration simpler, especially for new users. The login and startup experience could also be improved by reducing repeated login prompts and the time it takes for the application to become ready. I would like better integration between debugging and related information such as JCL, job output, abend details, and application logs. A more intuitive interface, stronger documentation website, and an easier onboarding process would also be beneficial. Additionally, enhanced AI-assisted capabilities would make the product easier to adopt.
For how long have I used the solution?
I have been using BMC AMI DevX for about one year.
What do I think about the stability of the solution?
BMC AMI DevX feels stable in my experience.
What do I think about the scalability of the solution?
BMC AMI DevX is good in terms of scalability. From my experience, it has been scalable for our mainframe development and support needs, handling large COBOL programs and large workloads.
How are customer service and support?
The customer support is responsive when issues are raised and takes technical cases seriously. In our environment, some requests are routed through our internal support or mainframe team rather than directly to BMC, but issues are still handled through appropriate channels. I have a positive impression of the support experience. I would rate the customer support 9 out of 10.
Which solution did I use previously and why did I switch?
We did not use any other solution before this. We were using mainframe tools before BMC AMI DevX.
What was our ROI?
For issues where BMC AMI DevX is applicable, I have seen debugging time decrease by around 20 to 30% because I can trace the COBOL programs and also inspect the variables. We can also identify the failing statement more efficiently, so the debugging time has been reduced by 20 to 30%.
What's my experience with pricing, setup cost, and licensing?
I do not have direct information about the setup cost and pricing and licensing. From the implementation perspective, I think the initial configuration can require some effort to align the product with existing enterprise processes and mainframe tooling.
Which other solutions did I evaluate?
We did not see many options, but we primarily relied on standard mainframe tools such as ISPF and SDSF, and we used to do manual tracking of COBOL.
What other advice do I have?
BMC AMI DevX provides a strong modern development and debugging experience for mainframe applications. I rate it in the range of 8 to 9 out of 10. What keeps it from being a 10 is mainly user experience, as the login and startup process can be frustrating, and the initial setup can also be challenging for new users.
I have a positive view of the security around BMC AMI DevX in an enterprise environment. However, I have not personally evaluated the underlying governance controls of its AI capabilities in detail. For AI-assisted code understanding, I want clear controls around access to source code and link data and permissions, as well as understanding how AI-generated explanations are processed. These areas would be important considerations before using the AI features with sensitive or business-critical mainframe code.
I find that the AI-assisted code understanding and output generated through BMC AMI DevX is useful and generally reliable for getting an initial understanding of unfamiliar COBOL applications. It can explain code, identify dependencies, and clarify program flow, which saves time when working through legacy code. However, I treat AI output as a starting point rather than the final authority, especially for business-critical logic, and I still validate the explanation against actual code and application behaviors before making any changes.
BMC AMI DevX is deployed in a hybrid cloud in our organization and integrates with our existing mainframe environment. IBM is the cloud provider for our hybrid cloud deployment.
My advice would be to evaluate BMC AMI DevX against the specific needs of your mainframe development team. If you work extensively with COBOL and want to modernize development, debugging, and DevOps workflows, it is worth considering. I would recommend running a full proof of concept with your applications and involving both experienced and newer developers. Pay particular attention to integration with existing source control, CI/CD, and security processes. Also, plan for some initial configuration and provide hands-on training so the team can get comfortable with the platform. My overall rating for BMC AMI DevX is 8 out of 10.