Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Subzero architecture
BMC Subsystem Optimizer for zEnterprise (Subzero) uses a set of components and supporting technologies to redirect subsystem requests in the z/OS environment.
Subzero components and technologies shows the interaction between components and technologies that support Subzero:
- BMC Execution Component for z/OS (DBC)
- BMC Configuration Component for z/OS (LGC)
- Runtime Component System (RTCS)
- Subzero controlling agent
- Subzero subsystem server
The following topics explain how Subzero works:
- Summary of the redirection workflow summarizes the process for completing a redirection, specifying which component or technology is involved in each step.
- Overview of components and technologies describes how the components and technologies work.
Summary of the redirection workflow
The following process summarizes how Subzero completes a redirection, specifying which component or technology is involved in each step.
- A BMC Execution Component for z/OS (DBC) address space starts on each z/OS logical partition (LPAR) that will participate in Subzero redirection.
- Each DBC starts a Subzero controlling agent on the same LPAR.
One controlling agent (internally designated as the master) requests the current Subzero option set from DB2 Product Configuration (LGC).
The option set identifies the participants in Subzero redirection activities as clients and targets. A client is the subsystem access routine and LPAR to which applications are sending requests for subsystem access. A target is the subsystem and LPAR to which Subzero will redirect those requests.
- LGC obtains the option set from its datastore, which is stored in a Runtime Component System (RTCS) registry. LGC returns the option set to the master controlling agent, which shares the configuration information with the other controlling agents.
- If the option set identifies that a client is on an LPAR, the controlling agent on that LPAR initializes a task to handle that client.
- An application program issues the first subsystem access request as usual. (No application program changes are required.)
- The first request is routed to the Subzero controlling agent on the client LPAR.
- The controlling agent on the client LPAR receives the first request, and sends it to the controlling agent on the target LPAR.
- In response to the first request, the target controlling agent initializes a Subzero subsystem server on the target LPAR, and passes the request to that new server.
The subsystem server establishes a connection with the target subsystem, which fulfills the request and returns the results to the subsystem server.
To the target subsystem, the subsystem server appears to be an ordinary subsystem access routine. (No target subsystem changes are required.)
The subsystem server establishes an XCF connection with the client on the client LPAR, and sends the fulfilled response to the client.
To the client, the subsystem server appears to be an ordinary subsystem access routine. From this point, the client and the subsystem server communicate directly with each other through XCF. DBC and the controlling agents no longer participate.
- The application program receives the results of the request.
Overview of components and technologies
Subzero uses the following components and technologies: