CA OPS/MVS Event Management and Automation Previous Solutions

Art McKendrick
Senior Automation Analyst at a financial services firm with 1,001-5,000 employees
We started out with IBM's "AO NetView", now known as SysView. It has a Message Automation Table (MAT), which can drive REXX execs to run in internal servers. At the time, there was no option to continue processing a message after the first hit in the MAT, so it was easy to configure it such that a given event would never trigger the desired automation. The entire MAT had to be reloaded for every change. There was no meaningful cross-system communication. There was no "front end". The product required thousands of fixes a year. We were discouraged from using a large number of global variables (we use thousands in OPSMVS). There was no equivalent to SSM. View full review »
Tom Kruger
Senior System Programmer at a healthcare company with 1,001-5,000 employees
We previously used and we continue to use a different solution. (We still have two LPARs on a different solution.) The #1 reason we switched to this product was the ease of operations and the hands-off approach in day-to-day usage. View full review »
Infrastructure Engineer Manager at a financial services firm with 1,001-5,000 employees
The path we were going down was between IBM and CA, and we thought about which one we should go with. For us, the flexibility and scalability is what sold us on this. View full review »
Systems Analyst / Programmer at a manufacturing company with 1,001-5,000 employees
We didn't switch from a previous solution. In 1988 when we started, this solution was one of about three tools that were available. We evaluated all of them and this one was the best. It was the most flexible and the one that would work best in our environment. View full review »
Mainframe Automation Support at a tech company with 1,001-5,000 employees
We had a home grown product before choosing OPS. View full review »
Vice President, Managing Director Defined Contribution at a financial services firm with 1,001-5,000 employees
In a previous life, I supported NetView and also the old Auto-operator. OPS/MVS is much more intuitive to use, especially compared to Netview/SA/GDPS. View full review »
Richard Chow
Systems Programmer at a energy/utilities company with 1,001-5,000 employees
Because sometimes the system has new messages. Every time we installed another new product, the message is different, so we would have to constantly upgrade, and follow up with the upgrade. That is how we knew that we needed this product. View full review »
Lead z/OS Systems Programmer
We had been a user of AF/OPERATOR, and needed a replacement for it. We switched because of cost and because our implementation of AF/OPERATOR was substandard. View full review »
Steve Dorsa
Production Control with 1,001-5,000 employees
When I first started using OPS, there were not any similar products from other vendors, with all the features OPS provided. View full review »
IT System Software - Technical Consultant at a insurance company with 1,001-5,000 employees
We've been using the solution for quite a long time; 15 years or more. View full review »
Gadi Ben-Avi
z/OS system Programmer at a tech services company with 1-10 employees
As the system became more complex, a solution was needed to make things simpler for operators and system programmers. View full review »
Mainframe System Sofware Support at a financial services firm with 1,001-5,000 employees
I did not previously use a different solution. View full review »
Nick Cianco
Lead Technology Architect – Systems Programmer at a tech company with 1,001-5,000 employees
Migrated from AutoMate/MVS in the 1990s. We went with the best automation solution available. View full review »

Sign Up with Email