OPS/MVS Modernization Guide

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.

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.

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

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.

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.

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

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.

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.

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

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

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

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

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.

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

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.

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

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.