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 subsystem servers
A Subzero subsystem server receives redirected subsystem access requests from a client, communicates with the target subsystem, and returns request results to the client.
When the Subzero controlling agent on a target LPAR receives the first redirected request to a target subsystem, the controlling agent starts a subsystem server automatically. The subsystem server receives the request and connects to the target subsystem. The target subsystem sends the fulfilled request to the subsystem server. The subsystem server sends the fulfilled request directly to the client through XCF. The client sends subsequent access requests directly to the subsystem server.
The controlling agent terminates a subsystem server automatically when the server is no longer needed (such as when the corresponding subsystem has terminated). To control a subsystem server manually, you can issue console commands.
A subsystem server runs as a separate address space on the target LPAR. DBC manages the address space as an external agent. One subsystem server is required to serve each defined redirection relationship between a client (running on the client LPAR) and a target subsystem (running on the target LPAR).
The default address space job name of the subsystem server is BRDssid, where ssid is the subsystem ID of the target subsystem.A subsystem server address space uses minimal system resources, limited to those necessary to enable access to the remote subsystem. It does not use ECSA or common memory objects and does not create any cross-memory environments.
Related topic