Supporting Services

The architecture of CA Chorus Software Manager comprised several key components. The Software Manager Server acted as the central point for managing software installations and updates. The...

The architecture of CA Common Services (CCS) on z/OS is centered around several key components. CAIRIM is responsible for initializing resources during system startup....

The architecture of CA TNG Framework is centered around a set of core services that are integrated into other CA products. These services...

CA 90s provided a set of common services for CA Technologies products on z/OS. The architecture included components such as the Common Services Manager, Resource...

The Oasis architecture comprises several key components that work together to provide its services. The Oasis/DMS is responsible for cross-system communication, enabling interaction...

Common services for Beta Systems products

The architecture of Beta 28 Systems Management Integrator (SMI) is centered around three primary components: the Message Collector, the Event Processor, and the Reporting Engine....

The architecture of Beta 23 is centered around providing essential browse and read functions for document management products on z/OS. The main components include...

The VPF (Virtual Print Facility) architecture on z/OS consists of several key components. The Print Server receives print jobs, validates them, and places them in the spool. The...

Data1 Fonts were a set of uniform, 13.3 pitch fonts designed for IBM 3800 printers on z/OS. These fonts are now a base element of z/OS. The architecture comprised several...

Runtime libraries for EGL applications

The architecture of Rational COBOL Runtime for z/VSE comprises several key components that work together to enable the execution of COBOL applications generated from EGL. The central...

The System Services Runtime Environment's architecture comprised several key components. A web container handled HTTP requests and responses, managing the lifecycle of web applications. The Java Virtual Machine (JVM)...

SMP/E's architecture centers around several key components. The CSI (Consolidated Software Inventory) data set is the central repository, storing metadata about installed software,...

The architecture of SMP4 was centered around the z/OS operating system and the SMP/E environment. Key components included the SMP/E environment...

The architecture of GPAR was centered around batch processing on the z/OS platform. The main components included a data collection module, a processing engine, and a reporting...

Infoprint Fonts, now part of the z/OS base, previously provided a set of fonts for use with the Infoprint Server on z/OS. The architecture consisted of font libraries and...

The architecture of AFP DBCS Fonts involves several key components within the z/OS environment. The primary components include the z/OS print subsystems,...

The architecture of AFP Font Collection is tightly integrated with the z/OS print subsystem. The core components include the Print...

The architecture of ACF/NCP is centered around the Network Control Program (NCP), which resides within communication controllers. These controllers, such as the 3705, 3725, and 3745,...

The architecture of ACF/SSP centers around the Network Control Program (NCP) and the utilities that manage it. The main components include: NCPGEN (NCP Generation Utility), LOAD (NCP Load Utility),...

The Emulation Program's architecture comprised components within the mainframe system and the communication controller. The mainframe components handled application interaction, while the controller...

The architecture of the X.25 Network Packet Switching Interface comprised three main components: the host system (z/OS, z/VM, or zVSE), the communication controller (e.g., 3725 or 3745), and...

The architecture of Network Terminal Option (NTO) comprised key components within the IBM mainframe environment and the communication controllers (e.g., 3725, 3745). The mainframe components managed the SNA...