Compuware Topaz Workbench Pros and Cons
Compuware Topaz Workbench Pros
The smart editor helps because it will code-complete for me. I can see code working a lot faster and I'm able to get things coded in less time.
We can develop in parallel today on ISPF, but it's giving us the advantage of the newer interface into the mainframe programming languages that younger programmers can use and are familiar with, rather than using the ISPF green screen.View full review »
It helps our staff work by speeding up their documentation process.
Once we got the configurations and deployment rolled out, it was very stable. I haven't had any major issues with Eclipse or the Topaz Workbench plugins.View full review »
From a user perspective, the GUIs make it easier for people to see and interact with files on the mainframe.View full review »
The most valuable feature of Topaz is Xpediter. It's more flexible than Xpediter through MVS.View full review »
It's a modernized development portal and helps reduce the learning curve for younger people coming in to work on the platform,View full review »
Compuware Topaz Workbench Cons
I'm waiting to see what 19.2 for Topaz looks like, but I have a problem with the JES Explorer right now. It limits you to a certain prefix for job names and there are some groups that have multiple prefixes that they'd like to see all at once in their job names, because of how they work in a group. And they can't see that in the JES Explorer.View full review »
The area for improvement is related to the testing tools that are available for unit testing or acceptance testing. I know they have some out there that we are not licensed for at this time, but it seems like some of the Eclipse tools that are used for other programming languages, they're all just built-in and they're a little more intuitive to the developers. Making those testing tools as intuitive as possible, and as integrated as possible into the workbench, would be really beneficial.View full review »
It often doesn't play well with other plugins in the environment.
It would be nice to have an audit trail to see what mainframe developers are using what.
It would be good if the vendors would work together or at least have some collaboration between them, so they would know what would work and what wouldn't work. Right now, the way things are working, they're relying on the customer to make everything work.View full review »
I'm always looking for improvement in things like the documentation, to make things a little bit easier and simpler to understand, a place where people can go to troubleshoot issues.View full review »
The ability to edit source code that has special characters is limited. The ability to incorporate or convert REXX into macros that are usable under the Topaz software is not there. And the REXX macros that I have developed over 40 years of work are useless, so I have a toolbox I can't use or deploy using the Topaz technology, while I can use it under MVS.
It's not as intuitive as it should be. In terms of navigation, there is a large training curve for using it. For a millennial it might be better, if they're used to Eclipse. But coming from a non-Eclipse environment and using Eclipse, though I have experience with Eclipse, it might be cumbersome.View full review »