The product’s implementation process is complicated and restrictive. It is difficult to find file programs and use a different tool for the setup as the compilation process is all locked up, at least in our implementation. We might switch to MySQL for the same reason.
The main challenges are its limited interface and the complexity of the customization. The user interface may seem outdated and affect user experience.
If I had to comment on an area of improvement or something new in the next or future version, I would like to see AI-assisted coding and impact analysis for mainframes. It is actually a fairly complete product. It is robust with a solid history and is always growing in functionality. It has a high level of maturity, which benefits the users and the administrators. This tool, with its group of options, facilitates the integration with other business processes, which allows you to take advantage of other solutions by incorporating automatic functions.
Concurrent development has room for improvement. The cost of the solution has room for improvement. The initial setup can be less complex and has room for improvement.
The solution can improve its parallel development, unlike more distributed source management systems like GIT or PVCs. It is more oriented towards single control of the source.
Analyst & Developer at a tech services company with 201-500 employees
Real User
2021-02-10T09:04:15Z
Feb 10, 2021
I would like to have better integration with other products. It's impossible to work in parallel mode with the source. For example, we have one check for many banks and you can't change the parallel source for different projects.
CA Endevor Administrator at a insurance company with 10,001+ employees
Real User
2018-06-19T08:17:00Z
Jun 19, 2018
One feature of Endevor is its Backout feature. If there is a problem, it can back out the executables. The only problem with that is that it will not back out the source in Endevor. For example, you can do a back out and it will back out the executable to the previous version, but it doesn't back out the source version in Endevor. It would make it much better if when you did a back out of Endevor, it would back out both the source and the executable and keep them in sync. Right now, if you do a back out and you leave it out, you have to sync the source code back in Endevor. That can be a challenge.
CA Endevor Software Change Manager (CA Endevor SCM) is the most widely used change management software for the mainframe environment. It can automate your entire development process, adapting to your specific business requirements and helping ensure consistency and complete control. Integration with IBM Rational Developer for System z can improve productivity, accelerate time-to-delivery and ensure the auditability of all programmer activities. Eclipse-ready, CA Endevor SCM helps shorten the...
The product’s implementation process is complicated and restrictive. It is difficult to find file programs and use a different tool for the setup as the compilation process is all locked up, at least in our implementation. We might switch to MySQL for the same reason.
The main challenges are its limited interface and the complexity of the customization. The user interface may seem outdated and affect user experience.
If I had to comment on an area of improvement or something new in the next or future version, I would like to see AI-assisted coding and impact analysis for mainframes. It is actually a fairly complete product. It is robust with a solid history and is always growing in functionality. It has a high level of maturity, which benefits the users and the administrators. This tool, with its group of options, facilitates the integration with other business processes, which allows you to take advantage of other solutions by incorporating automatic functions.
Endevor can improve parallel development.
The scalability of Endevor could improve.
Concurrent development has room for improvement. The cost of the solution has room for improvement. The initial setup can be less complex and has room for improvement.
The solution is very good and prevalent in larger organizations, but the solution can be improved by integrating more smoothly with the open world.
The solution can improve its parallel development, unlike more distributed source management systems like GIT or PVCs. It is more oriented towards single control of the source.
There should be better integration between CA Endevor Software Change Manager and Zowe.
I would like to have better integration with other products. It's impossible to work in parallel mode with the source. For example, we have one check for many banks and you can't change the parallel source for different projects.
One feature of Endevor is its Backout feature. If there is a problem, it can back out the executables. The only problem with that is that it will not back out the source in Endevor. For example, you can do a back out and it will back out the executable to the previous version, but it doesn't back out the source version in Endevor. It would make it much better if when you did a back out of Endevor, it would back out both the source and the executable and keep them in sync. Right now, if you do a back out and you leave it out, you have to sync the source code back in Endevor. That can be a challenge.