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.
DevOps Developer at a tech vendor with 10,001+ employees
Real User
Top 20
Sep 24, 2026
One improvement I would appreciate is stronger integration between DevX debugging and other troubleshooting information, such as JCL, job output, abend details, and application logs, all in one place. It would also be useful to have more automated root cause suggestions for common abends like SOC7 and SOC4. That could reduce the amount of manual analysis and make production troubleshooting even faster. Overall, the current debugging capabilities are useful, but better integration and automation would make the experience more efficient. One thing that stands out for me is the combination of debugging and code analysis capabilities. Being able to step through the COBOL program, set breakpoints, and monitor variable values gives me a much clearer picture of what is happening during execution. One feature I would find useful is an even deeper integration with production diagnostics where job logs, abend information, source code, and debugging could be brought together in one place. That could make production troubleshooting even faster. Overall, the debugging and analysis features are the ones I find most valuable in my daily work. If I could suggest improvements, I would focus on making the user experience more intuitive, expanding practical documentation, and providing deeper integration between debugging, JCL, job output, and diagnostic information. Those additions would make an already useful tool even more convenient for mainframe developers and support teams.
BMC AMI DevX is a strong platform, but there are a few areas where it could improve, such as simplifying the initial installation and configuration, especially for first-time users. It could also improve performance when working with very large mainframe applications or on slower network connections, and making the UI more intuitive so advanced features are easier to discover. These improvements would make the platform easier to adopt and more productive for both experienced mainframe developers and newcomers. Regarding improvements needed for BMC AMI DevX, I would suggest making the UI more intuitive so advanced features are easier to discover and providing more built-in tutorials, guides, onboarding, and documentation for new developers.
I definitely think BMC AMI DevX could be improved or enhanced in terms of the logging in features. BMC AMI DevX's logging in feature is not so great. Whenever you try to log in, it always prompts you for passwords. Then when you have to switch sessions, because we usually have to switch between production and UAT, there's no quick way of switching between the two. Every time you try to switch, it prompts you to log in. Additionally, there's a pop-up that I always receive. When you click X on it, it doesn't disappear. Eventually, I just end up minimizing it. Furthermore, the startup of BMC AMI DevX takes a long time to start up before it loads. It doesn't just immediately start up and it's ready. It takes a good solid two to three minutes before it's ready so that you can work on it. BMC AMI DevX's logins and the other ones I can understand because security has to be there, but I do feel that once I've logged in, I shouldn't need to log in again. The startup problem is the annoying one because if I want to do something, I need to open it two or three minutes earlier to give it time to load up. The startup problem is the one that definitely needs to be addressed.
To improve BMC AMI DevX, consideration should be given to cloud-style provisioning and development models, as well as integration of more AI capabilities. Enhancements in VS Code extensions to develop BMC-specific agents that developers can use in their day-to-day work could also make a significant difference.
The only thing that bothers me about BMC AMI DevX Code Pipeline is the screen movement. On the screens, I cannot move to fields easily. I have to put my cursor on the field and tap it to bring focus there, or use the tab key multiple times to get to a field on the screen. This sometimes bothers me. If BMC AMI DevX Code Pipeline can improve the UI and user interface on the screens, that would be beneficial. Otherwise, I think the product works well.
It's a very complicated tool. Sometimes the customer wants better, faster transaction times. They want the solution to move as fast as possible. We're trying to scale and grow our application with more servers to get the level of speed desired. Everything from small processes to big batch processing needs to be faster.
BMC AMI DevX is a mainframe DevOps platform for IBM Z environments that helps development and platform engineering teams increase release velocity, reduce change risk, and build a sustainable mainframe developer workforce. Whether the priority is attracting the next generation of mainframe talent, safely evolving decades of business-critical code, accelerating release velocity, or demonstrating development ROI to leadership — BMC AMI DevX is designed to address all on a single platform. Teams...
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.
One improvement I would appreciate is stronger integration between DevX debugging and other troubleshooting information, such as JCL, job output, abend details, and application logs, all in one place. It would also be useful to have more automated root cause suggestions for common abends like SOC7 and SOC4. That could reduce the amount of manual analysis and make production troubleshooting even faster. Overall, the current debugging capabilities are useful, but better integration and automation would make the experience more efficient. One thing that stands out for me is the combination of debugging and code analysis capabilities. Being able to step through the COBOL program, set breakpoints, and monitor variable values gives me a much clearer picture of what is happening during execution. One feature I would find useful is an even deeper integration with production diagnostics where job logs, abend information, source code, and debugging could be brought together in one place. That could make production troubleshooting even faster. Overall, the debugging and analysis features are the ones I find most valuable in my daily work. If I could suggest improvements, I would focus on making the user experience more intuitive, expanding practical documentation, and providing deeper integration between debugging, JCL, job output, and diagnostic information. Those additions would make an already useful tool even more convenient for mainframe developers and support teams.
BMC AMI DevX is a strong platform, but there are a few areas where it could improve, such as simplifying the initial installation and configuration, especially for first-time users. It could also improve performance when working with very large mainframe applications or on slower network connections, and making the UI more intuitive so advanced features are easier to discover. These improvements would make the platform easier to adopt and more productive for both experienced mainframe developers and newcomers. Regarding improvements needed for BMC AMI DevX, I would suggest making the UI more intuitive so advanced features are easier to discover and providing more built-in tutorials, guides, onboarding, and documentation for new developers.
I definitely think BMC AMI DevX could be improved or enhanced in terms of the logging in features. BMC AMI DevX's logging in feature is not so great. Whenever you try to log in, it always prompts you for passwords. Then when you have to switch sessions, because we usually have to switch between production and UAT, there's no quick way of switching between the two. Every time you try to switch, it prompts you to log in. Additionally, there's a pop-up that I always receive. When you click X on it, it doesn't disappear. Eventually, I just end up minimizing it. Furthermore, the startup of BMC AMI DevX takes a long time to start up before it loads. It doesn't just immediately start up and it's ready. It takes a good solid two to three minutes before it's ready so that you can work on it. BMC AMI DevX's logins and the other ones I can understand because security has to be there, but I do feel that once I've logged in, I shouldn't need to log in again. The startup problem is the annoying one because if I want to do something, I need to open it two or three minutes earlier to give it time to load up. The startup problem is the one that definitely needs to be addressed.
To improve BMC AMI DevX, consideration should be given to cloud-style provisioning and development models, as well as integration of more AI capabilities. Enhancements in VS Code extensions to develop BMC-specific agents that developers can use in their day-to-day work could also make a significant difference.
The only thing that bothers me about BMC AMI DevX Code Pipeline is the screen movement. On the screens, I cannot move to fields easily. I have to put my cursor on the field and tap it to bring focus there, or use the tab key multiple times to get to a field on the screen. This sometimes bothers me. If BMC AMI DevX Code Pipeline can improve the UI and user interface on the screens, that would be beneficial. Otherwise, I think the product works well.
It's a very complicated tool. Sometimes the customer wants better, faster transaction times. They want the solution to move as fast as possible. We're trying to scale and grow our application with more servers to get the level of speed desired. Everything from small processes to big batch processing needs to be faster.