Mainframe Communications — The Portals Between Worlds

01 — Overview

What the Communications Server Actually Does

The z/OS Communications Server is what turns a mainframe from an isolated, powerful machine into a fully connected part of the modern world — the component responsible for how data enters, leaves, and stays protected. It has to support two very different networking philosophies, because mainframes have been carrying enterprise traffic since long before the modern internet existed.

Trace the Route

Pick a protocol and watch how a request actually gets from your app to the mainframe

Choose a protocol above to trace its path to z/OS.

02 — Interactive

The Hardware Underneath

Click a component to see what it actually does.

🔌

OSA

⚡

HiperSockets

🔗

SMC-R / SMC-D

03 — Resilience

Staying Up When Everything Depends on It

A VIPA (Virtual IP Address) is tied to a service rather than a piece of hardware. If the machine hosting that service fails, the VIPA simply moves to another healthy machine in the cluster — the user notices, at worst, a brief pause. Try it below.

VIPA Failover Simulator

One server currently holds the VIPA and serves all traffic. Fail it, and watch the address move.

All three systems healthy. SYS-A currently holds the VIPA and is serving 100% of traffic.

04 — Not Frozen in Time

Not Stuck in the Past

Modern IBM Z hardware runs containers, including Kubernetes workloads, using the same dependable networking infrastructure that's carried traditional workloads for decades. IBM has even introduced AI-powered packet batching — a model that observes traffic patterns and predicts the optimal batching strategy in real time, cutting CPU usage without meaningfully affecting speed.

05 — Defence in Depth

Security at Every Layer

Little of this depends on individual developers remembering to "do the right thing" — security here is a property of the infrastructure, not something each service has to implement correctly on its own. Trace what happens to a single connection as it passes through every layer.

IP Filtering ✓Network

Controls exactly which traffic is permitted in or out — a strict checkpoint at every entry point.

IPSec ✓Network

Encrypts data travelling between systems, so intercepted traffic reveals nothing useful.

AT-TLS ✓Application

Automatically encrypts application traffic without the application itself needing to do anything differently.

zERT ✓Visibility

Monitors network connections and reports on encryption status — a clear picture of what's protected and what isn't.

06 — Wrap Up

Summary

The z/OS Communications Server speaks two networking languages, relies on specialised hardware to move data efficiently, stays available through mechanisms like VIPA, and wraps all of this in layered security. None of it is visible when you tap your card at a checkout — that invisibility is the point.

This article was co-authored with Salaudeen Zainab Moyinoluwa, and inspired by Edward Seidl's "z/OS Communications Server Network Security Overview" talk at the WAVEZ Spring 2026 Event.