Modernization Hub

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Showing 145-168 of 217 products

CQ-3780

Active
The architecture of CQ-3780 comprises several key components designed to facilitate file transfers between Windows applications and mainframe systems using BSC over RJE. The...
The architecture of Barr Host Communications Suite is centered around several key components. The RJE Client and NJE Client handle the initiation and management of file...

Barr/RJE

Not Supported
The architecture of Barr/RJE consists of several key components designed to facilitate file transfer and remote job entry between DOS/Windows and mainframe systems. The communication module handles TCP/IP connections,...

Barr/NJE

Not Supported
The architecture of Barr/NJE comprised several key components. The NJE transmitter and receiver were central to file transfer operations. These components communicated using NJE protocols over TCP/IP networks....
The Barr/Print Channel architecture is built around three core components: the Channel Interface, Print Spooler, and Output Processor. The Channel Interface handles communication with...
The architecture of Barr Enterprise Print Server is centered around several key components: the Print Server, the Output Manager, and platform-specific connectors. The Print Server acts as...

Barr/Print390

Supported
The architecture of Barr/Print390 is centered around the Barr Enterprise Print Server. The main components include the Print Server, the Print390 module, and the channel connectivity components....

Barr/Channel

Supported
The Barr/Channel architecture centers around the channel attachment card, which provides the physical connection to the mainframe channel (ESCON or Bus and Tag). The Barr/Channel...
Sponsored

World Time clock

Track time across the world

The architecture of Barr/Channel In SDK centers around enabling direct channel-based communication with mainframes. The main components include the Channel Interface, the API Library,...
The architecture of the Barr/Channel Out SDK centers on enabling communication between client applications and mainframe-attached printers. The main components include the client application, the...

Barr/Sync

Supported
The Barr/Sync architecture comprises the Barr/Sync Client, installed on the Microsoft HIS server, and the Barr/Sync Server, installed on the mainframe. These...

OnePrint

Active
The OnePrint architecture is composed of several key components: the Print Server, Conversion Engine, and Routing Module. The Print Server receives print jobs from the mainframe. The...

T5

Active
The T5 architecture is designed for secure, remote access to z/OS mainframe applications. The core components include the T5 Server, Client Interface, and...
The architecture of Application/Fax is based on a modular design, comprising several key components. The Fax Engine is responsible for processing fax requests and managing the...

OV/RerRouter

Supported
The architecture of OV/RerRouter is centered around three primary components: the Rerouting Engine, the Rule Manager, and the Logging Service. The Rerouting Engine is the core of the...
Sponsored

Master Your Schedule

Advanced timer solutions for professionals who value precision and punctuality

The architecture of Tivoli System Automation for Integrated Operations Management is designed for high availability and scalability. The core components include the Automation...
TCIME's architecture involved components on the mainframe (zSecure Audit) and within TSIEM. The communication between these components utilized a proprietary API. Data storage relied on the underlying...
The architecture of IBM Integration Bus (IIB) comprises several key components. The Integration Node is the runtime environment responsible for processing messages. The Integration Server is a...
The architecture of Omegamon II for Mainframe Networks comprised several key components. The VTAM monitor collected data from VTAM sessions, providing information on session activity, response times, and error...
The architecture of OMEGAMON for Networks on z/OS is centered around the OMEGAMON Agent, the Tivoli Enterprise Monitoring Server (TEMS), and the Tivoli...
The architecture of Tivoli Monitoring for Network Performance (TMN) comprised several key components. The Data Collection Agents resided on the z/OS mainframe and collected performance...
The architecture of Tivoli NetView Performance Monitor (NPM) comprised several key components. The NPM Agent resided on the z/OS or z/VM system...
The architecture of Tivoli NetView for TCP/IP Performance comprised several key components. The data collector was responsible for gathering network performance data through various TCP/IP...
The architecture of Websphere Enterprise Service Bus (WESB) centered around the Service Integration Bus (SIB), which facilitated communication between applications. Key components included...

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now