Compuware ISPW Pros and Cons
Compuware ISPW Pros
It does our CICS NEWCOPYs and our Db2 binds for us, whereas before, that was a manual process. It takes a lot of the workload off of the operations folks and off the DBAs.
We had parallel development before, but the way ISPW implements it is better. It has more control and oversight of the process, whereas before, it was like the Wild West. Everybody could have their own package with their own version of the component in it... ISPW is constantly aware of it. It notifies when someone else is using or has a different version of that component.View full review »
The visual ability to see potential downstream impacts to changes being made assists our developers in understanding the impact associated with their change.View full review »
Compuware ISPW Cons
One thing I would really like to see some improvement on is the promotion diagnostic messages. It invokes utilities "under the covers" to copy components, and it does not echo back any of the error messages from those utilities.
There are some features that are not well documented, so documentation could use a little help, on things like setting up deployment and which structures in the database correspond to which tables.View full review »
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.View full review »