My advice to others looking into using BMC AMI DevX is to evaluate it against your organization's specific requirements rather than adopting it solely because of its feature list. If you are a large organization with COBOL applications and want to modernize development and DevOps workflow, it is worth evaluating. I recommend running a proof of concept with your own applications involving both experienced developers and newer developers, assessing integration with your existing source control, CI/CD, and security. Training is essential to get the most value from BMC AMI DevX. I would rate this product an 8.5 overall.
From that perspective, I don't think I can give input about the impact of automated DORA metrics tracking on my organization's decision-making processes because I don't participate most of the time in that department, which just checks how quick the jobs are run or what's the difference between the two. For that one, I don't think I have any input there. I think BMC AMI DevX has provided overall benefits and a positive impact because I've seen a lot of developers, not just the new developers, but even the old developers. I'm very young, so I found a lot of old developers here that have been with the business for a while and have used the green screen their entire life. I've seen most of them also developing with BMC AMI DevX, migrating into the newer screen. They call it, "We are leaving the green screen," is what they say. They look at BMC AMI DevX as VS Code for COBOL developers, which is for us. I've seen it, not only from the old developers but even the young developers, I've seen most of them using it. I'm still in a process where I'm trying to do a sort of a hybrid style, use both. Where there's an advantage, I use this one, and where there's an advantage, I use that one. I do think it provides a more modern way of working with old technologies, with legacy systems. I think it's very good there. It's modernizing the legacy way of doing things, the mainframe. I've gone to the official documentation or guides provided by BMC for BMC AMI DevX once or twice because I was still trying to find out more about it or what it is because when I landed, I didn't know what this workbench and BMC AMI DevX thing were. I did go to the website, but I didn't get the time to just go through everything. That's something I also need to do. I think BMC AMI DevX's Open Borders approach is very good for maintaining my existing processes. I think it's very good in terms of its ability to integrate smoothly with the mainframe or the other applications. For that reason, I think its effect is very good. It's a very good effect because it doesn't disrupt existing processes or any of the existing applications. Instead, it sort of helps or integrates perfectly with them without disrupting. For example, if I was to go into a dataset with BMC AMI DevX and make changes, and then someone else logs on to the mainframe and tries to view those, they're also going to be able to pick them up. It's not that now I have to wait for something to happen or need to save on that side. It integrates smoothly, so everything just works smoothly and seamlessly. Based on my experience with every aspect of BMC AMI DevX, I would rate this product an eight because I still feel there is room for me to explore on it, but so far from what I've seen, it's very good and it definitely has a huge amount of potential.
BMC AMI DevX Code Pipeline is a solid product that any company can benefit from if they want to have tight control and a standard way of deploying applications into production in a secure manner. This is an excellent product to work with. I give this product a rating of 9.
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.
I would recommend evaluating BMC AMI DevX based on the specific needs of the mainframe development team. If the team spends a lot of time on COBOL application maintenance and production troubleshooting, the debugging and code analysis capabilities can be particularly useful. I would also suggest starting with a small group of developers, providing some hands-on training, and measuring things such as debugging time and incident resolution effort before expanding usage. Overall, I would say it is worth evaluating, especially for teams looking to make mainframe development and application maintenance more efficient. I would rate this product an 8 out of 10.
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...
My advice to others looking into using BMC AMI DevX is to evaluate it against your organization's specific requirements rather than adopting it solely because of its feature list. If you are a large organization with COBOL applications and want to modernize development and DevOps workflow, it is worth evaluating. I recommend running a proof of concept with your own applications involving both experienced developers and newer developers, assessing integration with your existing source control, CI/CD, and security. Training is essential to get the most value from BMC AMI DevX. I would rate this product an 8.5 overall.
From that perspective, I don't think I can give input about the impact of automated DORA metrics tracking on my organization's decision-making processes because I don't participate most of the time in that department, which just checks how quick the jobs are run or what's the difference between the two. For that one, I don't think I have any input there. I think BMC AMI DevX has provided overall benefits and a positive impact because I've seen a lot of developers, not just the new developers, but even the old developers. I'm very young, so I found a lot of old developers here that have been with the business for a while and have used the green screen their entire life. I've seen most of them also developing with BMC AMI DevX, migrating into the newer screen. They call it, "We are leaving the green screen," is what they say. They look at BMC AMI DevX as VS Code for COBOL developers, which is for us. I've seen it, not only from the old developers but even the young developers, I've seen most of them using it. I'm still in a process where I'm trying to do a sort of a hybrid style, use both. Where there's an advantage, I use this one, and where there's an advantage, I use that one. I do think it provides a more modern way of working with old technologies, with legacy systems. I think it's very good there. It's modernizing the legacy way of doing things, the mainframe. I've gone to the official documentation or guides provided by BMC for BMC AMI DevX once or twice because I was still trying to find out more about it or what it is because when I landed, I didn't know what this workbench and BMC AMI DevX thing were. I did go to the website, but I didn't get the time to just go through everything. That's something I also need to do. I think BMC AMI DevX's Open Borders approach is very good for maintaining my existing processes. I think it's very good in terms of its ability to integrate smoothly with the mainframe or the other applications. For that reason, I think its effect is very good. It's a very good effect because it doesn't disrupt existing processes or any of the existing applications. Instead, it sort of helps or integrates perfectly with them without disrupting. For example, if I was to go into a dataset with BMC AMI DevX and make changes, and then someone else logs on to the mainframe and tries to view those, they're also going to be able to pick them up. It's not that now I have to wait for something to happen or need to save on that side. It integrates smoothly, so everything just works smoothly and seamlessly. Based on my experience with every aspect of BMC AMI DevX, I would rate this product an eight because I still feel there is room for me to explore on it, but so far from what I've seen, it's very good and it definitely has a huge amount of potential.
BMC AMI DevX Code Pipeline is a solid product that any company can benefit from if they want to have tight control and a standard way of deploying applications into production in a secure manner. This is an excellent product to work with. I give this product a rating of 9.
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.
I would recommend evaluating BMC AMI DevX based on the specific needs of the mainframe development team. If the team spends a lot of time on COBOL application maintenance and production troubleshooting, the debugging and code analysis capabilities can be particularly useful. I would also suggest starting with a small group of developers, providing some hands-on training, and measuring things such as debugging time and incident resolution effort before expanding usage. Overall, I would say it is worth evaluating, especially for teams looking to make mainframe development and application maintenance more efficient. I would rate this product an 8 out of 10.
We use various versions of the solution. I'd rate the solution overall at a seven out of ten.