Our use case now includes the addition of two new LPARs. OPS/MVS is implemented on both additional LPARs.

It's distribution. The logistics of distribution. Warehousing, distribution, inventory control, shipping, bills of material.

Considering it's 35 years old, it's still functioning well, primarily because of the resources that are available, and tools that have been introduced that can connect to legacy applications. 

We use OPS to manage our workflow with jobs.

It performs great.

Our primary use of OPS/MVS is automation on the mainframe system, controlling resources, and tasks. 

The performance of it is beyond exceptional. It is probably one of the best products that I have ever worked with. It is easy to use, comprehensive, and can perform almost any task you need it to. 

We use it to monitor day-to-day activity in the system and to automate things like start-up, start a task. Basic overall health of the mainframe, and day-to-day business as usual.

It has performed very well.

Mainframe: Everything from message suppression to posting jobs in CA 7 and opening tickets.

It is performing well.

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.

Mainframe automation.

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

System/ops automation, SSM, OPSLOG, etc.

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.

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. 

z/OS automation.

We use it to look for jobs that are running late in our scheduling system.