CARMA

Figure 1. CARMA flow
CARMA flow
CARMA (Common Access Repository Manager) is used to access a host based Software Configuration Manager (SCM), for example CA Endevor® SCM. Figure 1 shows a schematic overview of how a Developer for z/OS® client can access any supported host-based Software Configuration Manager (SCM).
  1. The client has a Common Access Repository Manager (CARMA) plugin.
  2. The CARMA plugin communicates with the CARMA miner, active as a user-specific thread within the RSE thread pool (RSEDx). This communication is done by way of the existing RSE connection.
  3. When the client requests access to a SCM, the CARMA miner will bind to a TCP/IP port and will start a user-specific CARMA server, with the port number as startup argument. The CARMA server will then connect to this port and use this path for communication with the client. Note that host based SCMs expect single-user address spaces to access their services, which requires CARMA to start a CARMA server per user. It is not possible to create a single server supporting multiple users.
  4. The CARMA server will load the Repository Access Manager (RAM) that supports the requested SCM.
  5. The RAM deals with the technical details of interacting with the specific SCM, and presents a common interface to the client.