BMC z/OS

Subsystem Optimizer for zEnterprise Modernization Guide

SharingNetworks and Communication

Subsystem Optimizer for zEnterprise is a sharing product by BMC. Explore technical details, modernization strategies, and migration paths below.

Product Overview

Subsystem Optimizer for zEnterprise streamlines communication between DB2, IMS, and CICS subsystems residing on different LPARs, enabling them to function as if they were on a single LPAR.

The product integrates with z/OS security features, including RACF, ACF2, and Top Secret, for authentication and authorization.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What does Subsystem Optimizer for zEnterprise do?

Subsystem Optimizer for zEnterprise optimizes communication between DB2, IMS, and CICS subsystems across different LPARs, making them operate as if they were on the same LPAR. It enhances resource utilization and simplifies subsystem consolidation.

Is Subsystem Optimizer transparent to the existing subsystems?

The solution operates transparently to DB2, IMS, and CICS. It can be dynamically enabled or disabled without requiring changes to the applications or subsystems themselves.

How does Subsystem Optimizer help with subsystem consolidation?

Subsystem Optimizer facilitates the consolidation of IMS, DB2, and CICS subsystems onto fewer LPARs, leading to reduced infrastructure costs and simplified management.

Technical

What are the main system components of Subsystem Optimizer?

The main components include the Intercept Module, the Optimization Engine, and the Control Interface. The Intercept Module captures communication requests, the Optimization Engine optimizes the cross-LPAR communication, and the Control Interface manages the configuration and control of the solution.

What configuration files are used by Subsystem Optimizer?

Subsystem Optimizer uses a configuration file, typically a PARMLIB member, to define the subsystems to be optimized and the optimization parameters. The Control Interface also allows dynamic modification of these parameters.

What protocols does Subsystem Optimizer use for communication?

The product uses standard z/OS communication protocols, such as XCF (Cross-System Coupling Facility), to facilitate communication between LPARs. Specific ports depend on the z/OS configuration.

Business Value

How does Subsystem Optimizer improve application performance?

By optimizing cross-LPAR communication, Subsystem Optimizer reduces latency and improves transaction throughput. This leads to better application performance and a more responsive user experience.

What are the cost benefits of using Subsystem Optimizer?

Consolidating subsystems onto fewer LPARs reduces the overall infrastructure footprint, leading to lower hardware and software licensing costs. It also simplifies system management and reduces operational overhead.

How does Subsystem Optimizer improve business agility?

Subsystem Optimizer enables greater flexibility in workload placement and resource allocation. Subsystems can be moved and consolidated without requiring application changes, improving agility and responsiveness to changing business needs.

Security

What authentication methods are supported by Subsystem Optimizer?

Subsystem Optimizer leverages z/OS security features, including RACF, ACF2, and Top Secret, for authentication and authorization. It integrates with the existing security infrastructure to ensure secure communication between subsystems.

What access control model is used by Subsystem Optimizer?

The product supports Role-Based Access Control (RBAC), allowing administrators to define roles with specific permissions for managing and monitoring the solution. This ensures that only authorized personnel can access sensitive functions.

What audit/logging capabilities exist in Subsystem Optimizer?

Subsystem Optimizer uses z/OS System Management Facilities (SMF) to provide comprehensive audit trails of all configuration changes and operational events. These logs can be used for security monitoring and compliance reporting.

Operations

What administrative interfaces are available for Subsystem Optimizer?

Subsystem Optimizer provides a command-line interface (CLI) and a web-based console for administrative tasks. The CLI is used for scripting and automation, while the web console provides a user-friendly interface for monitoring and configuration.

What are the main configuration parameters for Subsystem Optimizer?

The main configuration parameters include the definition of optimized subsystems, communication parameters, and security settings. These parameters are defined in the configuration file and can be dynamically modified using the Control Interface.

What monitoring capabilities exist in Subsystem Optimizer?

Subsystem Optimizer integrates with z/OS monitoring tools, such as IBM Tivoli OMEGAMON, to provide real-time performance data and alerts. It also generates SMF records for detailed performance analysis and reporting.

Ready to Start Your Migration?

Download our comprehensive migration guide for Subsystem Optimizer for zEnterprise or calculate your ROI.

Calculate ROI