Component overview

Figure 1 shows a generalized overview of the combined z/OS Explorer, z/OS Debugger, and Developer for z/OS layout on your host system.

(z/OS Explorer) Remote Systems Explorer (RSE) provides core services, such as connecting the client to the host and starting other servers for specific services. RSE consists of two logical entities:
- RSE daemon (RSED), which manages connection setup. RSE daemon is also responsible for running in single server mode. To do so, RSE daemon creates one or more child processes known as RSE thread pools (RSEDx).
- RSE server, which handles individual client request. An RSE server is active as a thread inside a RSE thread pool.
(z/OS Debugger) Debug Manager (DBGMGR) coordinates debugger activity.
(z/OS Explorer) TSO Commands Service (TSO cmd) provides a batch-like interface for TSO and ISPF commands.
(z/OS Explorer) JES Job Monitor (JMON) provides all JES related services.
Common Access Repository Manager (CARMA) provides an interface to interact with Software Configuration Managers (SCMs), such as CA Endevor® SCM.
More services are available, which can be provided by Developer for z/OS itself or corequisite software.

The description in the previous paragraph and list shows the central role assigned to RSE. With few exceptions, all client communication goes through RSE. This allows for easy security related network setup, as only a limited set of ports are used for client-host communication.

To manage the connections and workloads from the clients, RSE is composed of a daemon address space, which controls thread pool address spaces. The daemon acts as a focal point for connection and management purposes, while the thread pools process the client workloads. Based upon the values defined in the rse.env configuration file, and the amount of actual client connections, multiple thread pool address spaces can be started by the daemon.