OPS/MVS Automation Intelligence Reviews

System/ops automation, SSM, OPSLOG, etc.

Orderly startup and shutdown of z/OS and all components.

• SSM - Provides for orderly startup and shutdown.
• OPSLOG - Enables filtering by message-id, and/or jobname(s).
  
• Rules - OPS/REXX interface streamlines deployment, interfaces easily with JES2 and z/OS.
  

• The interfaces to USS, CA UIM could be better.
  
• CA Common Services interfaces - namely Zdata Mover, Zmessage Service, Zdatacolletcor - are poorly documented.

No issues with stability.

No issues with scalability.

Tech support is excellent.

Migrated from AutoMate/MVS in the 1990s. We went with the best automation solution available.

Initial setup was straightforward, used CA-supplied migration tools.

NetView, Candle products, ASG-Zack.

It's easy to use.

The primary usage is we try to automate the system message, then transfer it to the command to automatically respond to the system requirement message.

To reduce the number of repetitive motions required by a human to respond to the system. This automation automatically replies, so the benefit is to reduce repetition of work.

To minimize the labor of responding to the required message. So, an automatic response is minimizing the labor work.

With stability, sometimes we do have problems with this product. I guess because a lot of times we have to write the script correctly, so finding the right person with the expertise on writing the script, or the automation, is the problem. So, that is the reason sometimes it is not stable, we do not have the expertise to write the script.

So far, so good. We can combine all the CA products and work with this product together, so we pretty satisfied with that.

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.

I was not a part of the initial setup.

We really do need this product. We have the necessity now, because we have implemented for so long that we can't function without this product.

Implement and write the script correctly from the beginning. Make sure and plan out ahead. Plan the project five, six, or seven years ahead, instead of just installing, implementing, and starting. Plan ahead.

We use it to automate our responses to messages, and to get early notification on potential problems. We also use it for orderly startups/shutdowns of the operating system and all started tasks.

We have eliminated human error in the startup of one of our most critical applications, thereby reducing the risk of unwanted downtime.

OPS/REXX, because it allows us almost unlimited flexibility in automating our system.

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.

No issues with stability.

No issues with scalability.

Superb. Every time I have an issue, tech support answers promptly, and they always have solutions.

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.

The setup was straightforward. We received on-site assistance from CA, and they not only helped us set up the system properly, they also made sure to transfer the knowledge to us.

We have looked at BMC's AutoOPERATOR.

Go for it. It's a superior product for automation.

I can use this solution to automate message traffic on the console.

With this tool, there is now less operator intervention and more of an automated, streamlined process. It's given us the ability to track problems and create service tickets to resolve them.

I've seen a mobile app that allows you to get the system status from your phone. That's a really nice feature that I’d like to see.

The stability is great. It's very solid.

The scalability is working very well for us so far.

I have used technical support and they are great. They work the problem until we have a solution. So far, it's worked very well for us.

When selecting a vendor, the most important thing is the ability to meet our needs. CA does a very good job of that. It's a very solid product. This tool is very good as far as doing what we need it to do.

I would recommend others to look at it and compare it to other products on the market. I think they'll find that OPS/MVS is a leader in the automation industry.

• System State Manager (SSM) and the RDF, EPI, POI REXX functions and commands
• Global variables
• MSF
• OPSLOG
• Archive capabilities

After implementing SSM, we dropped our IPL time from 40 minutes via manual commands to eight minutes via SSM.

Use something other than CCI for external communications.

I have been using it 20+ years.

I have not encountered any stability issues; very stable product.

I have not encountered any scalability issues; very scalable.

Technical support gets the highest rating; always knowledgeable and good response time.

I did not previously use a different solution.

Initial setup was very straightforward.

Before choosing this product, I evaluated BMC Control products, IBM.

Make sure to allocate enough space for the OPSLOG and for the global variables.

Mainframe automation.

In terms of performance, it is the gold standard in mainframe automation.

I personally like its System State Manager tools. They make starting and stopping a mainframe pretty much seamless.

I've always had it, so I don't really know that I can say how it improves my organization. I don't have anything to compare it to.

I don't know of anything that is required to be added.

I've never had any issues with stability.

It's scalable to the mainframe. No issues.

Technical support is good. I work on several CA products, I generally find that they have a very good response time. And if they can't answer your question they always have levels above them that they can send the tickets off to.

I would definitely get a demo and look at this product and compare it to what they're running. All of these vendors have conversion processes, so I'm sure they'd have to do the other stuff that I don't do, make the dollars work. If it works I'd do it. 

My primary use case is the automation of all of tasks. I used the scheduling feature and also automation of various time-critical top functions and facilities. 

It's made it so that with a lot of automation pieces we can bring this region up or take this region down, and it allows us to actually always meet our time critical requirements. If it's supposed to be up at 8am, it comes up at 8am. 

It works, and as far as the scheduling piece, it is wonderfully well-written and I use it all the time.

If something breaks and it goes down when it's not supposed to, automation brings it right back up. So it's really used mainly for availability.

It more or less does everything we need for it to do.

Very stable.

Scalability is really not an issue in the mainframe. It can handle anything we need it for to handle.

They do a good job. I have SYSVIEW and I'll call CA more for SYSVIEW than I would for Ops.

We actually had CA, one of their experts, come in and help us set it up. Now it seems simple, but I have to train folks on it and it's complex, but it does a lot for us. It's complex because it does everything.

OPSLOG, message rules, ability to manipulate the msg autoflag, MSF, RDF Tables. The whole product is very valuable, but if I have to list some, those are a good start.

The product is so advanced in all ways that it's hard to pick a specific area. OPSLOG and MSF has saved us more than once when a system was unavailable via TSO, but we could see what was going on via our cross domain logs. This allowed us to correct the problem with an actual IPL of the system.

The ability to manipulate the autoflag has allowed us to setup the kind of message forwarding that is important to our end users.

All of the OPS/REXX built in functions are great. We've recently used OPSTATUS to give our operators extra info they needed about WTORS that wasn't available via system commands.

We initially installed OPS in 1989 when it still was part of Goal.

It is an extremely stable product.

We're a large shop with many requirements and scalability has never been an issue.

The technical support is top notch. They have always been right there for us whenever we were needed, including the offer to be available on weekends during a recent upgrade if needed.

Friendly, professional, knowledgeable. I rate OPS/MVS technical support amongst the best support in the world.

We had a home grown product before choosing OPS.

Our initial setup was not overly difficult, but support was sent out to help us with our initial install.

I'm not involved in pricing and licensing. I'm aware that OPS (as well as other CA products) are considered to be pricier than most. Having said that, you get what you pay for. If you want the features and reliability of Cadillac, then you have to be willing to pay for it.

We evaluated basically all available options, narrowed it down to CA, BMC and one other (now absorbed) company.

If you're at the point of implementation, take advantage of CA technical support and the local OPS online community. Both are extremely helpful and willing to give advice to help new people avoid potential problems.