We used to us an IBM product, but OPS/MVS has a lot more flexibility in what we can do with it.

We're able to do a lot more ad hoc-type things. We can set up for different events, or do out-paging for a mainframe interface, or issue MVS commands. It's flexible enough for us to use it when needed outside the normal automation flows.

We obviously also use all the basic functionalities of it, like time-of-day, message, and other command rules. Command rules are especially great when our operators have repetitive tasks.

The most valuable features of this solution are its ease of use and capability to solve problems across different platforms and different software products.

To me, the most valuable features are its ease-of-use and being able to clone some of what you've done with some of the rules. It makes it really easy to administer. I've had people tell me that it's one of the best automated systems they've ever worked on.

It's very secure, because it's a legacy application. It allows a natural, organic encapsulation of data.

Automation is very important to any data center; just the ability to optimize things, run more efficiently. OPS/MVS does that tremendously.

System State Manager and all the built-in functions.

• The ability to create your own automation
• Flexibility
• The reliability of constant, active monitoring

• Rules
• OPS/REXX
• SQL
• SSM
• Global variables
• OPSLOG

• SSM keeps startup and shutdown of all tasks synchronised in a hierarchy.
• MSF - cross-system and cross-Sysplex links between instances of the product.
• OPSLOG - similar to OPERLOG, but it also includes some SMF events, and it can be filtered to ease analysis.
• Individual rules for various events can be updated in flight without bouncing the product.
• Global variables can be set at the job, system or Sysplex level.

The product is really a very good automation. It's around the Rolls-Royce products of the automation products that are around. It's a very stable product. I very much like the SSM stuff in it. The rules engine, it's awesome.

It brings up the jobs. We can schedule them into different groups, so we can bring up the base system first and then the applications just run on top of the that; then the jobs that aren't quite as important after that. 

We can enter special commands. It can go out and see messages as the job comes up, and you can reply commands to the messages. 

Satisfies the dependencies. 

What I like about it personally is that I can go out and interrupt what's going on and bring a job down if I need to, and bring it back up. It works out really well.

• Simplicity of use
• Reliability of the product
• Scalability
• The performance functionality

The width and breadth of the options available that we do currently not use, but are available to us.

The simplicity of it, as far as getting new people to use the tool.

It's very flexible. You can customize what you need to, which is good. For example, you can do your own coding inside the tool, make your own scripting tooling.

The scalability. We're able to use it across our whole enterprise.

By far, the most valuable features of this product are:

• SSM
• AOF
• OpsLog

I do not have to keep recordings. It is there and is proactive. It helps the operators, human editors, and me.

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

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

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

We like the flexibility that enables us to keep up with all the other products that are coming up and available.

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

• 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.
  

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

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.

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.

• Responding to various events in the system.
• Performing automatic IPL and shutdown.
• Verifying system status.

It makes our job, as operators, easier.

To help monitor our scheduling system, in case there is something late. 

The effectiveness and stability of the solution is something that we require and something that this solution delivers.