CARMA architecture

A CARMA system requires three components in order to function properly: a CARMA hierarchy, a CARMA transport, and a CARMA host.

A CARMA hierarchy is a client-side data structure that provides support for CARMA content navigation and the execution of CARMA operations. CARMA operation requests are sent via a CARMA transport to a CARMA host. A CARMA transport is a client-side communication service between CARMA hierarchies and CARMA hosts. CARMA hosts contain the host-side CARMA service, CARMA-390, which is responsible for managing the available content.

CARMA hierarchy

A CARMA hierarchy is a special type of tree data structure that is used to manage CARMA content. Each CARMA hierarchy is connected with exactly one CARMA transport and exactly one CARMA host (it uses its CARMA transport to communicate with its CARMA host). The CARMA plug-in acts as a workstation client and provides a graphical representation of CARMA hierarchies using the CARMA Repositories view. Each top-level node in this view represents a CARMA hierarchy.

CARMA transport

The CARMA transport is a service plug-in forDeveloper for z/OS® that manages the connection between a CARMA hierarchy and its CARMA host. Thus, the CARMA transport packages send commands from the CARMA hierarchy and returns responses from the CARMA host. The CARMA RSE transport is used for this purpose by the CARMA plug-in.

CARMA host

A CARMA host is a host system that provides the CARMA-390 service. Each CARMA host generally has a set of repository access managers (RAMs), which CARMA-390 uses to manage access to content.