We use the basic feature set of Endevor to control and track all of the sales operations within our company. 

The solution guarantees the correspondence of the source and executable code (integrity) as well as automates the compilation processes. It also has other uses, such as automatic customization of JCLs/PROCs, and validation of standard names in PGMs, PROCs, JCL, PARM, etc.

It offers a single package of changes for mainframe and distributed and has reversal contingency and DRP.

There is a generation of environments to enable different stages of development and on-demand (DESA, UAT, and CRVL - Pre-production).

It offers security and audit of changes in information assets (software).

Primary use case would be that our application developers use Endevor for managing their mainframe software. They take their source code and they add it in to Endevor, and Endevor translates that source code into an output executable, and then from there it would get deployed to the various development areas, QA areas, and then finally to production.

I am using Endevor for a software controller.

We're using Endevor for application development.

We use it to control the source code versioning, implementation, generation, automation; pretty much anything that is source code on the mainframe. We manage COBOL assembler, we manage pretty much any mainframe language there is.

I use it on a daily basis as an administrator. It performs fairly well and has for 20-plus years.

Software configuration management.

We use it to move our mainframe code through development to production. From a release perspective, my team oversees it, and we help manage that. 

It has performed very well. We use it for our CSS mainframe development.

We are using Endevor as a manager for our software to have the promotion between environments.

We use it to update our production libraries.

We pull in the production version, Endevor creates the test version, we make our changes in the test version, and then we promote it out with Endevor to production.

Software changes and release management.

We use it for source code management. We use it to basically keep our applications that we use day-to-day, month-to-month, and week-to-week, all up-to-date. We use it to move it through those areas and manage it for auditing purposes, like dev, QA, production, etc. Our developers use it to build code in those different stages and move it forward.

We use it for version control in the mainframe area.

It's been great. To be honest, we use GitHub for enterprise for the distributed world, and we use SCM for the mainframe world. So far, I've looked around as well. I've not seen a computer that's close to Endevor in terms of performance, scalability and capability.

Source control management.

It performs well.

It is a tool the mainframe programmers use to do their work. If they need to make a change to a program, they go into Endevor and they check out a copy of the program. Then, they make their changes and check it back into Endeavor, and it gets built or compiled into whatever the language is. When they want to move a copy of it to QA for testing, they use Endevor to do that. Also, when it is time to go into production, they use Endevor to do that. The programmers do all their work through Endevor, and it is their bridge between development and production. 

We use the product as a source manager and program manager. It helps in controlling the mainframe code and performing data migrations.

Our primary use case for the solution is management, version control, process, or building management. Additionally, we deploy the solution on local storage.

I set up the security configurations for Endevor as well as everything in the mainframe. I am the security architect, so I determine what has to be done in order to secure the product going into production.

We use it to migrate our software from the different environments of development and QA, and then QA to production.

It performs pretty well. I like it.

We use it to manage our source, make sure everything is clean, and nobody puts anything in the production that does not belong. 

Application software management for multi-client applications.

As an outsourcer, in some cases software is maintained in-house, then distributed to clients.

Source code management. It works well.

We use CA Endevor Software Change Manager in order to control the lifecycle of the applications for mainframes.

We used Endevor for our source code management tool. We also use it for coordinating our testing that includes unit tests and system tests.

We have an on-premises mainframe environment. All of our storage is local.

We use it to track changes to our schedules. It performs great.