What is our primary use case?
In 2018, we executed a migration from an LCM product (ASG: Allen Software Group company) to an ISPW in order to manage our mainframe programs (mostly Cobol, few C, and ASM).
- We use ISPW for SCM and ALM, built and deployed from the development environment to the production environment on IBM z/OS.
- ISPW can be used on both Eclipse Neon 4.6.3 and ISPF panels.
- In our company, developers are using ISPW in Eclipse to have the benefit of an IDE and to use others plugins from Compuware Topaz solution or other providers we have.
- ISPW administrators and production teams use ISPW on both Eclipse and ISPF panels depending on the tasks they have to manage (a part of the administrative task is not available in Eclipse plugin).
How has it helped my organization?
- It helps us with the changing of SCM and ALM products, and also to change the life cycle including two branches.
Of course, it's still a recent migration, so we are still in progress to improve our organization and use of the product.
What is most valuable?
- The plugin ISPW integrated into Eclipse is a really valuable functionality for developers who already use it. It helps to have quick access to the components, to see versions, life cycle, and to do generation and deployment in the environments.
- ISPW deployment can be interfaced using API to "XL Release" product (XebiaLabs). In the months coming, we are going to implement this functionality in our DevOps project.
What needs improvement?
- The ISPW plugin could be improved to add some functionality which is already in ISPF panels and not in the plugin.
- It could also be improved to better help the developer manage merging versions in the life cycle (even if he can already use Eclipse merge view), and to have prompts on warnings and errors during generation and deployment, followed by a pop-up and before the promotion task.
For how long have I used the solution?
Less than one year.
How are customer service and technical support?
The customer service of Compuware and its technical support is at a really standard level.
Which solution did I use previously and why did I switch?
We used LCM: Life Cycle Manager (ASG: Allen Software Group). We changed production because the support and evolution of the product were in risk and because it was not available in Eclipse IDE.
What about the implementation team?
We carried out the migration and implementation with a migration team of the vendor, and an in-house team. Technical support from Compuware was very helpful and useful during the implementation and migration.
Which other solutions did I evaluate?
We had a quick presentation of Endevor (CA) and ChangeMan (ex Serena Software), and we did a proof of concept using Dimensions CM with Serena Software (now Micro Focus).