CA OPS/MVS Event Management and Automation Room for Improvement

Greg Payne
Sr. Analyst/Technology Infrastructure at a energy/utilities company with 1,001-5,000 employees
I just installed version 12.3, which actually already has a number of new features. It's going to make it easier for some of our new users. I'm old-school, I learned it the old way. I actually want to go back and implement it and start doing things the new way. As I need to train people, it's going to make it easier for them and make the learning curve much shorter. The new release addressed some shortcomings of the product. It was old-school. The learning curve was a little bit long in the beginning, but it's really come a long way. View full review »
Lead z/OS Systems Programmer
One thing that comes to mind is the MQ interface. The last time we tried to use it, it seemed a little clunky. Also, performing a stop/restart of OPS/MVS could be a little smoother too. Without special coding, some undesired tasks will be started and some necessary tasks will be stopped if we have to bounce OPS/MVS during the day. View full review »
Nick Cianco
Lead Technology Architect – Systems Programmer at a tech company with 10,001+ employees
* The interfaces to USS, CA UIM could be better. * CA Common Services interfaces - namely Zdata Mover, Zmessage Service, Zdatacolletcor - are poorly documented. View full review »
Find out what your peers are saying about Broadcom, IBM, BMC and others in Event Monitoring. Updated: January 2020.
396,781 professionals have used our research since 2012.