FLEX-CUB

The FLEX-CUB architecture consists of three primary components: the Control Process, the Device Emulation Layer, and the Storage Manager. The Control Process is the central management component, responsible for starting, stopping, and monitoring the emulation environment. It also handles configuration loading and system-level tasks.

, 3390 disk, 3490 tape). This layer translates mainframe I/O commands into operations on the underlying UNIX file system. The Storage Manager handles the storage of emulated data.

It interacts with the UNIX file system to store and retrieve data for emulated disks and tapes. Communication between components occurs via inter-process communication (IPC). The Control Process uses configuration files to define the emulated devices and their properties.

The Device Emulation Layer uses TCP/IP for communication with the mainframe. The Storage Manager uses the file system for data storage. The product supports LDAP and Kerberos authentication.

Monitoring is achieved through system logs and the `cubstatus` command. The CLI provides the primary interface for administration and configuration. The product does not expose REST or SOAP APIs.