Mainframe Networking — VTAM & TCP/IP on z/OS Guide
In this tutorial, you'll learn about Mainframe Networking. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.
Mainframe networking on z/OS combines the traditional SNA/VTAM world with modern TCP/IP — a dual-stack architecture where legacy 3270 terminal traffic flows alongside REST API calls, MQ channels, and enterprise integration traffic across the same physical adapters.
What You'll Learn
VTAM and SNA concepts, TCP/IP on z/OS, OSA adapters, TN3270 terminal access, Enterprise Extender, and network security configuration for Mainframe environments.
Why It Matters
Mainframes do not operate in isolation. They connect to thousands of terminals, peer systems, cloud services, and external networks. Understanding Mainframe networking is critical for architects designing hybrid Mainframe-cloud infrastructure and for operators maintaining connectivity.
Doda Browser uses TN3270-inspired session management for its enterprise features. Durga Antivirus Pro applies Mainframe network security patterns for endpoint communication.
Real-World Use
A financial institution runs SNA traffic for ATMs and TCP/IP for online banking — both over the same OSA adapter. The Mainframe's networking stack prioritizes ATM traffic using WLM, ensuring PIN verification completes in under 500ms while API traffic is queued accordingly.
Learning Path
flowchart LR A["z/OS Overview"] --> B["RACF Security"] B --> C["Mainframe Networking
You are here"] C --> D["Parallel Sysplex"] D --> E["Mainframe DevOps"] style C fill:#f90,color:#fff
What Is Mainframe Networking?
Mainframe networking on z/OS operates at two levels:
- SNA/VTAM: The legacy IBM networking architecture — Systems Network Architecture managed by Virtual Telecommunications Access Method
- TCP/IP: The standard Internet protocol stack provided by Communications Server for z/OS
Network Architecture
flowchart LR
subgraph "z/OS LPAR"
A[TCP/IP Stack]
B[VTAM]
C[Enterprise Extender]
D[OSA Adapter]
end
subgraph "Network"
E[LAN/SAN]
F[SNA Network]
G[Internet/Cloud]
end
A --> D --> E
B --> D --> F
C --> A
C --> B
D --> G
style D fill:#f90,color:#fff
VTAM and SNA
VTAM manages SNA resources on z/OS:
V NET,ACT,ID=APPL1 Activate an application
V NET,INACT,ID=LU1 Deactivate a logical unit
D NET,APPLS Display active applications
D NET,MAJNODES Display major node status
SNA Network Components
| Component | Purpose |
|---|---|
| SSCP | System Services Control Point — manages the SNA domain |
| PU | Physical Unit — manages hardware resources |
| LU | Logical Unit — endpoint for user communication |
| SSCP-PU | Session between SSCP and PU |
| LU-LU | Session between two LUs (user session) |
TCP/IP on z/OS
TCP/IP on z/OS is configured through profile datasets:
; TCP/IP Profile - PROFILE.TCPIP
;
; Define network interfaces
INTERFACE OSA1
DEFINE IPAQENET
PORTNAME OSA1PORT
IPADDR 10.0.1.100/24
; Define listening ports
PORT
20 TCP OMVS NODELAYFIX
21 TCP OMVS
23 TCP TN3270
80 TCP HTTP SERVER
443 TCP HTTPS SERVER
1414 TCP MQ CHANNELS
; Define routing
ROUTE DEFAULT 10.0.1.1 OSA1 MTU 1500
TN3270 Configuration
TN3270 allows telnet clients to access Mainframe 3270 applications:
; TN3270E configuration
TN3270
PORT 23
LULIST USER.POOL1 SIZE=500
LULIST USER.POOL2 SIZE=500 INACT=60
DEFAULTAPPL TSO
OSA Adapters
Open Systems Adapters (OSA) are the physical network interfaces:
- OSA-Express: Standard Ethernet adapter
- OSA-Express2: Improved throughput, VLAN support
- OSA-Express3: 10 Gb Ethernet, hardware offload
- OSA-Express6S: 25/100 Gb Ethernet, crypto support
Enterprise Extender
Enterprise Extender (EE) carries SNA traffic over IP networks using HPR (High Performance Routing):
; Enterprise Extender configuration
BEGINVTAM
EE NETID=USIBM1 CPCNAME=ZOS1
CONNTYPE EE
IPNETWORK 10.0.1.0 255.255.255.0
ENDVTAM
Common Errors
1. OSA port misconfiguration
Verify OSA port definitions match the physical adapter connections. Use V ACTIVATE to test.
2. TN3270 port conflicts
Ensure the TN3270 port is not blocked by firewalls and is active in VTAM.
3. TCP/IP stack inactive
Check the TCP/IP started task with D TCPIP,,NLIST and restart if needed.
4. Routing table errors
Use NETSTAT ROUTE to display the routing table and verify default routes.
5. VTAM buffer shortages
Monitor VTAM buffer pools. Shortages cause SNA session failures.
Practice Questions
What is VTAM on z/OS? Virtual Telecommunications Access Method — the software that manages SNA network resources on the Mainframe.
How does TCP/IP differ from SNA on mainframes? TCP/IP uses standard Internet protocols for modern applications. SNA is IBM's legacy networking architecture still used for 3270 terminal access.
What is an OSA adapter? Open Systems Adapter — the physical network interface card that connects the Mainframe to Ethernet networks.
What does TN3270 provide? Telnet access to 3270 Mainframe applications from standard telnet clients or TN3270 emulators.
What is Enterprise Extender? A feature that encapsulates SNA traffic in IP packets, allowing SNA applications to run over TCP/IP networks.
Challenge: Design a Mainframe network topology with redundant OSA adapters, VLAN separation for production/test traffic, and Enterprise Extender for connecting remote SNA devices over an IP WAN.
FAQ
What's Next
| Tutorial | What You'll Learn |
|---|---|
| Parallel Sysplex Guide | Mainframe clustering and high availability |
| WLM Workload Manager Guide | Network traffic prioritization |
Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro. Updated 2026-06-24.
Built by the developers of DodaTech
Doda Browser, DodaZIP & Durga Antivirus Pro