We changed our name from IT Central Station: Here's why

Compuware ISPW OverviewUNIXBusinessApplication

Compuware ISPW is #4 ranked solution in top Software Configuration Management tools. PeerSpot users give Compuware ISPW an average rating of 10 out of 10. Compuware ISPW is most commonly compared to CA Endevor Software Change Manager: Compuware ISPW vs CA Endevor Software Change Manager. The top industry researching this solution are professionals from a computer software company, accounting for 25% of all views.
What is Compuware ISPW?

A modern, end-to-end Agile source code management, release automation and deployment automation tool that enables mainframe application developers at all skill levels to fulfill business requirements, optimize code quality, and improve developer productivity through mainframe DevOps. With ISPW, developers can:

  • Easily perform concurrent development to support Agile Development practices
  • Leverage Jenkins plugins to manage code throughout the lifecycle
  • Use REST APIs to automatically connect mainframe applications into modern DevOps toolchains
  • Collaborate with other developers through features like alerts when another programmer has checked out code
  • See versions of a program at multiple points in the development cycle to prevent incorrect overlaying and ensure smooth code integration
  • Access an intuitive relationship visualization that guides users to failure points
Buyer's Guide

Download the Software Configuration Management Buyer's Guide including reviews and more. Updated: January 2022

Compuware ISPW Customers

mBank, Standard Bank

Compuware ISPW Video

Archived Compuware ISPW Reviews (more than two years old)

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
User at a insurance company with 1,001-5,000 employees
Real User
Auto-deploy reduces development time for some of our applications
Pros and Cons
  • "The visual ability to see potential downstream impacts to changes being made assists our developers in understanding the impact associated with their change."
  • "Better discussions to identify inventory prior to the start of any migration would be helpful for potential clients that have applications with code that is not modified often."

What is our primary use case?

Today, the mainframe is our foundation where our customer data lives. Interfacing with the mainframe is how our distributed systems provide services to our customers, regardless of the channel  used (Mobile, User Interface, etc).  Until an alternative cost-efficient technology is identified that has the processing power of the mainframe, our focus will remain on modernization.  Our focus is to utilize tools and technology that allow for more automation, real-time services, and communication with our distributed products in a way that reduces cost and increases efficiency.

How has it helped my organization?

With the use of ISPW, we were able to reduce our deployment time for specific applications  by utilizing the auto-deploy features. Using tools such as ISPW also increases our mainframe developer’s knowledge of Eclipse-based tools that the distributed products utilize. 

We’re also experimenting with being able to utilize distributed developers to see if they can utilize the  ISPW analysis tool to identify/make changes in COBOL without really knowing this technology.     

What is most valuable?

The visual ability to see potential downstream impacts to code changes is a value add in helping our developers identify and understand the impact associated with their change. Utilization of the deploy feature in ISPW has also been a key functionality.

What needs improvement?

My advice for new clients migrating to ISPW is to take the time needed to understand your current inventory of ASIs, code that is not executed/no longer required,  and any unique situations that may need to be handled differently than the standard migration approach.   This vendor is great in walking through different options and finding solutions for any special handling.   

For how long have I used the solution?

One year.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
ITCS user
Support for Development Teams on Mainframe at CNP TI
Real User
It helps us with the changing of SCM and ALM products, and also to change the life cycle including two branches

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).

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Software Configuration Management Report and find out what your peers are saying about Compuware, Broadcom, Micro Focus, and more!