What are some common commands and configuration methods?

Common commands include ADDRESS OPSCTL for issuing OPS/REXX commands, OPSVIEW for monitoring system status, and OPSCMD for executing z/OS commands. Configuration is primarily managed through ISPF panels and the OPS/REXX language.

What type of API does OPS/MVS expose?

OPS/MVS exposes a native API accessible through Ops/REXX. Specific API endpoint patterns depend on the integrated subsystem (e.g., IMS, CICS).

What are the main system components?

The main components include the OPS/MVS Engine, the Event Monitor, and the Rule Processor. These components communicate through internal queues and shared memory. Data is stored in VSAM datasets.

What administrative interfaces are available?

Administrative interfaces include ISPF panels and a command-line interface accessible through TSO. User management is integrated with z/OS security systems like RACF, ACF2, or Top Secret.

How does OPS/MVS provide business value?

OPS/MVS reduces operational costs by automating repetitive tasks, minimizing manual intervention, and improving system availability through proactive problem resolution.

How does automation improve operational efficiency?

By automating responses to system events, OPS/MVS ensures consistent and timely actions, reducing the risk of human error and improving overall operational efficiency.

How does OPS/MVS empower non-programmers?

OPS/MVS allows staff without programming knowledge to create automation rules using EasyRule, empowering a wider range of personnel to contribute to automation efforts.

What authentication methods are supported?

OPS/MVS integrates with z/OS security systems such as RACF, ACF2, and Top Secret for authentication and authorization. It supports role-based access control (RBAC).

What access control model is used?

OPS/MVS uses the access control mechanisms provided by the underlying z/OS security system (RACF, ACF2, Top Secret) to control access to resources and functions.

What audit/logging capabilities exist?

OPS/MVS provides audit logging of system events, rule executions, and operator actions, enabling tracking and analysis of operational activities.

What monitoring/logging capabilities exist?

OPS/MVS provides monitoring capabilities through OPSVIEW, allowing operators to view system status, resource utilization, and active automation rules. Logging is performed to SMF datasets.

What are the main configuration parameters?

Configuration parameters are managed through ISPF panels and stored in VSAM datasets. Key parameters include rule definitions, event filters, and subsystem connection settings.

How is user management handled?

User management is handled through the integrated z/OS security system (RACF, ACF2, Top Secret). OPS/MVS leverages these systems for user authentication and authorization.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

OPS/MVS

Broadcom Active z/OS

Operating System Automation

Vendor

Broadcom

Product Overview

OPS/MVS automates z/OS operations through event monitoring and rule-based responses. The architecture includes the OPS/MVS Engine, which processes events and executes rules; the Event Monitor, which captures system messages and events; and the Rule Processor, which evaluates rules and triggers actions. These components communicate through internal queues and shared memory.

Rules are defined using EasyRule (ISPF panels) or Ops/REXX. The system integrates with z/OS security systems (RACF, ACF2, Top Secret) for authentication and authorization, supporting role-based access control (RBAC). Key commands include ADDRESS OPSCTL, OPSVIEW, and OPSCMD.

OPS/MVS interacts with subsystems like IMS and CICS. Configuration data is stored in VSAM datasets. Audit logging is performed to SMF datasets.

Competing products include IBM Z System Automation. A key architectural advantage is the separation of event monitoring, rule processing, and action execution, allowing for flexible and scalable automation. The native API, accessible through Ops/REXX, enables integration with other z/OS components.

Frequently Asked Questions

What is the primary function of OPS/MVS?

OPS/MVS automates z/OS operations by monitoring system messages and events. It uses rules defined through EasyRule or Ops/REXX to respond automatically, reducing manual intervention.

What are EasyRule and Ops/REXX?

EasyRule provides an ISPF panel-driven interface for creating automation rules without requiring programming knowledge. Ops/REXX allows for more complex logic and integration using the REXX language.

Can OPS/MVS interact with other z/OS subsystems?

OPS/MVS can interact with subsystems like IMS and CICS through optional features, extending its automation capabilities to these environments.

What is the history of OPS/MVS?

The product was originally developed by MVS Software Inc., then acquired by Goal Systems. Legent acquired Goal Systems and integrated AutoMate into OPS/MVS. Broadcom acquired it through the CA acquisition in 2018.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Share Your Product Experience

OPS/MVS

Product Overview

Frequently Asked Questions

What is the primary function of OPS/MVS?

What are EasyRule and Ops/REXX?

Can OPS/MVS interact with other z/OS subsystems?

What is the history of OPS/MVS?

What are some common commands and configuration methods?

What type of API does OPS/MVS expose?

What are the main system components?

What administrative interfaces are available?

How does OPS/MVS provide business value?

How does automation improve operational efficiency?

How does OPS/MVS empower non-programmers?

What authentication methods are supported?

What access control model is used?

What audit/logging capabilities exist?

What monitoring/logging capabilities exist?

What are the main configuration parameters?

How is user management handled?

Related Products

More from Broadcom

AcceleREXX

ACF2

Allocate DASD Space and Placement

Auditor for z/OS

Automation Point

Bind Analyzer for Db2

Similar Products

_beta access monitor

(E)JES

$avers

4Tune

ABARS/Assist

ACC

Help Improve This Directory

Are You a Vendor? Claim Your Listing