The Subsystem Service Model: SOA for Mainframe Environments

BY

Service Orientated Architecture (SOA) has emerged as a popular standard to “modernize” legacy mainframe applications into today’s infrastructures. However, mainframes are often viewed as only “black box” service providers to the loosely coupled distributed applications. As a result, the efficiencies of SOA have not been realized on the mainframe itself.

The Subsystem Service Model (SSM), enabled by BMC’s Subsystem Optimizer for zEnterprise, extends the concept and benefits of SOA into the mainframe infrastructure. Like SOA, the key concept of SSM is centered around the separation of service consumers from service providers. Mainframe LPARs consist of service-consuming transaction managers (MQ, CICS, IMS) and the service providing database managers (DB2, IMS), which up until now had to reside on the same logical partition (LPAR).

Subsystem Optimizer, affectionately called Subzero, enables organizations to separate, or isolate, transaction processing and database subsystem workloads on to their respective LPARs. See the figure below.

Similar to how SOA was a shift in thinking for distributed software applications and environments, SSM with Subsystem Optimizer changes how mainframe infrastructures can be arranged and managed. The decoupling of the service consumer (transaction manager) from the service provider (database) on the same LPAR is a dramatically different approach that opens the door to a variety of environmental configurations. The result has many benefits: dramatic cost savings, enhanced availability, ease of maintenance, and perhaps most importantly, environmental simplification. The success of SOA in the distributed world is now possible on the mainframe with SSM.

Read more about SSM in my future blogs, and learn more about Subsystem Optimizer today.

Forbes State of ITSM 2017


Learn how leading organizations are meeting the changing needs of IT and business technology

Download Report ›

These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.

Share This Post


Jeremy Hamilton

Jeremy Hamilton

Jeremy Hamilton is a technical Software Consultant for BMC’s Mainframe Cost Optimization Suite (R4). He has over 9 years’ experience in the software industry, primarily in the technical sales role. He started his career as a physicist for IBM Research before moving into the mainframe software world. At IBM he worked with many large corporations and government agencies, and wrote three IBM Redbooks regarding the IBM Application Development Tools. In his current role, he works with various customers to educate, consult, and implement the R4 solutions, as well as drive enhancements for the products. Jeremy has a Masters in Information Systems from Santa Clara University, and an American Indian Science and Engineering Society (AISES) Sequoyah Fellow.