Re: Knowing Nonstop

JigarP — Tue, 19 May 2026 19:08:50 GMT

Hi Surya,

Here is something from my notes, can't say if links are updated and probably not complete but should be enough information to start the Nonstop journey.

--Regards

HPE NonStop Complete Technology Stack (virtualized NonStop information follows this later below)

-----------------------------------------------------------------------------------------------------------------------

1. Hardware / Infrastructure Layer

Server Platforms

┌───────────────────┬────────────┬──────────────────────────────┐
│ Platform │ Generation │ Architecture │
├───────────────────┼────────────┼──────────────────────────────┤
│ NS9-X5 │ Latest │ x86 Intel Xeon (Virtualized) │
├───────────────────┼────────────┼──────────────────────────────┤
│ NS9-X4 │ Current │ x86 Intel Xeon │
├───────────────────┼────────────┼──────────────────────────────┤
│ NS3200 │ Recent │ x86 (Blade-based) │
├───────────────────┼────────────┼──────────────────────────────┤
│ NS-X │ Previous │ x86 (Itanium successor) │
├───────────────────┼────────────┼──────────────────────────────┤
│ Itanium-based │ Legacy │ HP PA-RISC / Itanium │
└───────────────────┴────────────┴──────────────────────────────┘

Architecture Fundamentals

Shared-Nothing Architecture:
├─ N+1 redundancy (every component duplicated)
├─ Loosely-coupled processor modules
├─ No single point of failure
├─ Fault-tolerant interconnect (ServerNet/VirtualNet)
├─ Physical and Virtual NonStop platforms
└─ Continuous Process Pairs (primary + backup)

Key Hardware References

HPE NonStop Hardware Docs:
https://www.hpe.com/us/en/servers/nonstop.html

HPE Support Portal (manuals, firmware):
https://support.hpe.com/hpesc/public/home

QuickSpecs for NS9 systems:
https://www.hpe.com/h20195/v2/getpdf.aspx/a00068837enw.pdf

-----------------------------------------------------------------------------------------------------------------------

2. Operating System Layer

NonStop OS (TNS/E, TNS/X)

TNS = Tandem NonStop (legacy name)
├─ TNS/E: Itanium-based NonStop OS
└─ TNS/X: x86-based NonStop OS (current)

Key OS Concepts:
├─ Guardian: Native NonStop OS environment
│ ├─ Device naming: \SYSTEM.$VOL.SUBVOL.FILE
│ ├─ Process naming: $PROCESS, $PROCESSNAME
│ └─ Flat file system (volumes/subvols)
│
├─ OSS: Open System Services (POSIX layer)
│ ├─ UNIX-like environment on NonStop
│ ├─ /home, /etc, /var, /tmp
│ └─ POSIX API compatibility
│
└─ Virtualized NonStop (vNS):
├─ Runs on VMware vSphere (coming soon to Ubuntu/KVM)
├─ Software-based fault tolerance
└─ Cloud-ready deployment

Key OS Components

┌───────────────────────────────────────────┬────────────────────────────────┐
│ Component │ Purpose │
├───────────────────────────────────────────┼────────────────────────────────┤
│ $SYSTEM │ System volume │
├───────────────────────────────────────────┼────────────────────────────────┤
│ TMF (Transaction Monitoring Facility) │ Transaction management │
├───────────────────────────────────────────┼────────────────────────────────┤
│ Measure │ Performance measurement │
├───────────────────────────────────────────┼────────────────────────────────┤
│ EMS (Event Management Services) │ Event logging/monitoring │
├───────────────────────────────────────────┼────────────────────────────────┤
│ SCF (Subsystem Control Facility) │ Configuration management │
├───────────────────────────────────────────┼────────────────────────────────┤
│ OSM (Open System Manager) │ Hardware/OS management console │
└───────────────────────────────────────────┴────────────────────────────────┘

OS Documentation Links

Guardian Programmer's Guide:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045440en_us

OSS User Guide:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045444en_us

SCF Reference Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045472en_us

EMS Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045437en_us

-----------------------------------------------------------------------------------------------------------------------

3. Networking / CLIM Layer

CLIM (Cluster I/O Module)

CLIM = Linux-based I/O processor
├─ Runs embedded Linux (CentOS/RHEL-based)
├─ Handles TCP/IP networking
├─ Handles storage I/O
├─ Communicates with NonStop via ServerNet
└─ Types:
├─ NCLIM: Network CLIM (Ethernet/IP)
├─ SCLIM: Storage CLIM (Fibre Channel/SAS)
└─ Combo: Combined network + storage

Key CLIM Files:
├─ /etc/clim/failover.conf - Failover configuration
├─ /etc/clim/mirror/ - Sync config (CONFSYNC)
└─ /var/log/ - CLIM logs

Networking Stack

NonStop Network Layers:
├─ SWAN (ServerNet Wide Area Network)
│ └─ High-speed internal interconnect
│
├─ TCP/IP (via CLIM)
│ ├─ Expand: NonStop-to-NonStop networking
│ └─ IP Services: Standard TCP/IP
│
├─ RoCE (RDMA over Converged Ethernet)
│ ├─ High-performance storage/network
│ └─ Uses MLX5 driver (Mellanox ConnectX)
│
└─ InfiniBand (optional high-performance interconnect)

Networking References

TCP/IPv6 Config & Mgmt Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045475en_us

CLIM Installation & Config:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045419en_us

-----------------------------------------------------------------------------------------------------------------------

4. Storage Layer

Storage Components

NonStop Storage:
├─ Storage CLIMs (SCLIM)
│ ├─ SAS (Serial Attached SCSI)
│ └─ Fibre Channel
│
├─ NonStop Storage Architecture:
│ ├─ Disc Process Pairs (mirrored)
│ ├─ RAID via Disc processes
│ └─ Logical disc volumes
│
└─ External Storage:
├─ HPE 3PAR / Primera / Alletra
├─ Fibre Channel SAN
└─ NVMe (newer deployments)

Filesystem Types

┌───────────────────────────────────────┬────────────────────────────────┐
│ Filesystem │ Description │
├───────────────────────────────────────┼────────────────────────────────┤
│ Guardian filesystem │ Native NonStop flat filesystem │
├───────────────────────────────────────┼────────────────────────────────┤
│ OSS filesystem (DP2) │ POSIX filesystem (UNIX-like) │
├───────────────────────────────────────┼────────────────────────────────┤
│ Enscribe │ Native NonStop database files │
├───────────────────────────────────────┼────────────────────────────────┤
│ SQL/MX │ Relational database storage │
├───────────────────────────────────────┼────────────────────────────────┤
│ SMS (Storage Management Services) │ Backup/archiving │
└───────────────────────────────────────┴────────────────────────────────┘

-----------------------------------------------------------------------------------------------------------------------

5. Database Layer

NonStop Databases

Native NonStop Databases:
├─ NonStop SQL/MX (primary RDBMS)
│ ├─ ANSI SQL compliant
│ ├─ Fault-tolerant, ACID compliant
│ ├─ Distributed transactions (TMF)
│ └─ Accessed via JDBC, ODBC, embedded SQL
│
├─ Enscribe
│ ├─ Native NoSQL-like record manager
│ ├─ Key-sequenced, relative, unstructured files
│ └─ Foundation for many legacy apps
│
├─ NonStop SQL/MP (legacy)
│ ├─ Predecessor to SQL/MX
│ └─ Still in production at some sites
│
└─ RDF (Remote Database Facility)
├─ Database replication
├─ Disaster recovery
└─ Real-time audit trail replication

Database References

NonStop SQL/MX Reference Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045467en_us

Enscribe Programmer's Guide:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045433en_us

RDF Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045462en_us

TMF Programmer's Guide:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045476en_us

-----------------------------------------------------------------------------------------------------------------------

6. Transaction Processing / Middleware Layer

Core Middleware

NonStop Middleware Stack:
├─ TMF (Transaction Monitoring Facility)
│ ├─ Distributed ACID transactions
│ ├─ Two-phase commit
│ └─ Audit trail management
│
├─ Pathway (OLTP Framework)
│ ├─ Request/reply transaction processing
│ ├─ Server classes (dynamic scaling)
│ ├─ TCP/IP and LU6.2 access
│ └─ Works with SCREEN COBOL, pTAL, C
│
├─ TS/MP (Transaction Processing Monitor)
│ ├─ High-performance OLTP
│ ├─ Server management
│ └─ Fault-tolerant transaction routing
│
├─ NonStop NS Guardian IPC
│ ├─ Message-based process communication
│ ├─ WRITEREAD, WRITE, READ primitives
│ └─ File System protocol (fundamental IPC)
│
└─ Expand
├─ Wide-area network protocol (NonStop native)
├─ Connects multiple NonStop systems
└─ Transparent remote file access

Modern Middleware Additions

┌───────────────────────────┬──────────────────────────────┐
│ Middleware │ Purpose │
├───────────────────────────┼──────────────────────────────┤
│ WebSphere MQ (IBM MQ) │ Message queuing │
├───────────────────────────┼──────────────────────────────┤
│ NSJMS │ JMS messaging on NonStop │
├───────────────────────────┼──────────────────────────────┤
│ NonStop JTTS │ Java Transaction Service │
├───────────────────────────┼──────────────────────────────┤
│ Shadowbase │ Data replication/integration │
├───────────────────────────┼──────────────────────────────┤
│ XPNET │ Cross-platform networking │
└───────────────────────────┴──────────────────────────────┘

Middleware References

Pathway/TS Programming Guide:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045455en_us

TMF Reference Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045477en_us

Guardian IPC Programmer's Guide:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045442en_us

-----------------------------------------------------------------------------------------------------------------------

7. Security Layer

NonStop Security Components

Security Stack:
├─ Safeguard
│ ├─ Access Control Lists (ACLs)
│ ├─ Authentication/Authorization
│ ├─ Audit logging
│ └─ SECURITY-CLIM-ADMIN groups
│
├─ SSH/SFTP (via OSS + CLIM)
│ ├─ Key management
│ ├─ SSOCLIM for Single Sign-On
│ └─ Known hosts management
│
├─ NonStop SSL
│ └─ TLS/SSL for encrypted comms
│
├─ XYGATE Suite (HPE Security)
│ ├─ XYGATE Access Control
│ ├─ XYGATE Merged Audit (XMA)
│ └─ Multi-factor authentication
│
└─ Compliance
├─ PCI-DSS (payments)
├─ HIPAA (healthcare)
└─ SOX (financial)

Security References

Safeguard Reference Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045464en_us

NonStop SSL Manual:
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045469en_us

-----------------------------------------------------------------------------------------------------------------------

8. Development / Programming Layer

Programming Languages

┌─────────────────────────┬───────────────────────────────────────────┐
│ Language │ Usage │
├─────────────────────────┼───────────────────────────────────────────┤
│ pTAL (Portable TAL) │ Native NonStop systems language │
├─────────────────────────┼───────────────────────────────────────────┤
│ TAL │ Original Tandem systems language (legacy) │
├─────────────────────────┼───────────────────────────────────────────┤
│ SCREEN COBOL │ Transaction screen applications │
├─────────────────────────┼───────────────────────────────────────────┤
│ COBOL85 │ Batch/OLTP COBOL │
├─────────────────────────┼───────────────────────────────────────────┤
│ C/C++ │ Modern application development │
├─────────────────────────┼───────────────────────────────────────────┤
│ Java (KLX) │ JVM on NonStop │
├─────────────────────────┼───────────────────────────────────────────┤
│ SCOBOL │ Screen COBOL for OLTP │
└─────────────────────────┴───────────────────────────────────────────┘

Development Tools

├─ TACL (Tandem Advanced Command Language)
│ └─ NonStop shell scripting (like bash on NonStop)
│
├─ INSPECT
│ └─ Native NonStop debugger
│
├─ TEDIT / ENFORM
│ └─ Text editor, query tool
│
├─ NonStop Development Environment (NDE)
│ └─ Eclipse-based IDE for NonStop
│
├─ SQLCI
│ └─ SQL/MX interactive query tool (like psql)
│
└─ SPT (System Performance Tool)
└─ Performance profiling

-----------------------------------------------------------------------------------------------------------------------

9. Monitoring & Management Layer

Management Tools

├─ OSM (Open System Manager)
│ ├─ Hardware & OS management console
│ ├─ GUI-based (web)
│ └─ Alerting, event management
│
├─ MEASURE
│ ├─ Performance measurement tool
│ ├─ CPU, disc, IPC, process metrics
│ └─ Native NonStop performance data
│
├─ EMS (Event Management Services)
│ ├─ System event logging
│ ├─ Event filtering/routing
│ └─ Custom event handling
│
├─ NTAnywhere / Web ViewPoint
│ └─ Remote NonStop system monitoring
│
└─ TACL scripts
└─ Automation and monitoring scripts

-----------------------------------------------------------------------------------------------------------------------

10. High Availability & DR Layer

HA Architecture

├─ Process Pairs
│ ├─ Primary + Backup process per workload
│ └─ Automatic failover on fault
│
├─ RDF (Remote Database Facility)
│ └─ Real-time DB replication for DR
│
├─ Shadowbase
│ └─ Third-party active/active replication
│
├─ TMDS (Transaction Monitor DR)
│ └─ Transaction-level failover
│
└─ Disaster Recovery
├─ Tandem Disaster Recovery Facility (TDRF)
└─ Geographically dispersed HA

-----------------------------------------------------------------------------------------------------------------------

Master Documentation Reference Links

HPE NonStop Product Page:
https://www.hpe.com/us/en/servers/nonstop.html

HPE Support Portal (all NonStop manuals):
https://support.hpe.com/hpesc/public/home
→ Search: "NonStop" for all documentation

HPE NonStop Library (full doc index):
https://support.hpe.com/hpesc/public/docDisplay?docId=a00045418en_us

NonStop Technical Community (HPE):
https://community.hpe.com/t5/HPE-NonStop/ct-p/nonstop

NonStop Wikipedia Overview (concepts):
https://en.wikipedia.org/wiki/NonStop_(server_computers)

ITUG (Independent NonStop user group):
https://www.connect-community.org

NonStop Open Source Tools:
https://nonstoptools.com

-----------------------------------------------------------------------------------------------------------------------

Full Stack Summary

┌─────────────────────────────────────────────────┐
│ Applications (Banking, Payments, Telco, Retail) │
├─────────────────────────────────────────────────┤
│ Development: pTAL, COBOL, C, Java, TACL │
├─────────────────────────────────────────────────┤
│ Monitoring: OSM, EMS, MEASURE, ViewPoint │
├─────────────────────────────────────────────────┤
│ Security: Safeguard, XYGATE, SSH, NonStop SSL │
├─────────────────────────────────────────────────┤
│ Middleware: Pathway, TS/MP, TMF, Expand │
├─────────────────────────────────────────────────┤
│ Database: SQL/MX, SQL/MP, Enscribe, RDF │
├─────────────────────────────────────────────────┤
│ OS: Guardian + OSS (POSIX) + TNS/X │
├─────────────────────────────────────────────────┤
│ Networking: CLIM, TCP/IP, RoCE, SWAN │
├─────────────────────────────────────────────────┤
│ Storage: DP2, Enscribe, SMS, SAS/FC CLIMs │
├─────────────────────────────────────────────────┤
│ Hardware: NS9 x86, ServerNet, Process Pairs │
└─────────────────────────────────────────────────┘

-----------------------------------------------------------------------------------------------------------------------

HPE Virtualized NonStop (vNS) Platform

-----------------------------------------------------------------------------------------------------------------------

What Is Virtualized NonStop?

Traditional NonStop:
└─ Fault tolerance = HARDWARE-based
├─ Dedicated proprietary servers
├─ Physical redundant processor modules
└─ Specialized ServerNet interconnect

Virtualized NonStop (vNS):
└─ Fault tolerance = SOFTWARE-based
├─ Runs on standard x86 servers
├─ Hypervisor provides infrastructure
├─ NonStop software replicates process pairs in VMs
└─ Same NonStop OS/apps, different hardware layer

-----------------------------------------------------------------------------------------------------------------------

Two Flavors of Virtualized NonStop

1. HPE Virtualized NonStop Software (vNS)

Deployed on-premise on customer's own infrastructure
├─ Runs on: VMware vSphere (ESXi)
├─ Hardware: Any HPE ProLiant or compatible x86 servers
├─ Guest OS: NonStop OS (TNS/X) as virtual machine
├─ Min VMs: 3 NonStop VMs per cluster (N+1 redundancy)
└─ Use case: Enterprise private cloud, own datacenter

2. GreenLake Flex Solution for NonStop

HPE-managed consumption model
├─ Pay-as-you-go (OpEx vs CapEx)
├─ HPE-owned hardware, customer-operated
├─ Same vNS software underneath
├─ Scalable consumption based on usage
└─ Use case: Avoid capital expenditure

-----------------------------------------------------------------------------------------------------------------------

vNS Architecture Deep Dive

Physical Layer

┌─────────────────────────────────────────────────────────┐
│ Customer x86 Infrastructure │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ HPE ProLiant │ │ HPE ProLiant │ │ HPE ProLiant │ │
│ │ DL/ML Server │ │ DL/ML Server │ │ DL/ML Server │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ Ethernet / RoCE Interconnect │
└─────────────────────────────────────────────────────────┘

Hypervisor Layer

┌─────────────────────────────────────────────────────────┐
│ VMware vSphere (ESXi) │
│ ├─ vCenter manages the cluster │
│ ├─ vMotion for VM migration │
│ ├─ HA/DRS for VM-level fault tolerance │
│ └─ Networking: vSwitch or NSX-T │
└─────────────────────────────────────────────────────────┘

NonStop VM Layer

┌──────────┐ ┌──────────┐ ┌──────────┐
│ NS VM 0 │ │ NS VM 1 │ │ NS VM 2 │
│ Primary │↔──│ Mirror 1 │↔──│ Mirror 2 │
│ NonStop │ │ NonStop │ │ NonStop │
│ OS/Apps │ │ OS/Apps │ │ OS/Apps │
└──────────┘ └──────────┘ └──────────┘
│ │ │
└───────────────┴───────────────┘
VirtualNet (software ServerNet)
(Internal Ethernet)

Storage Layer

├─ Shared storage: HPE Primera / Alletra / 3PAR
├─ Or VMware vSAN (software-defined storage)
├─ NVMe / SSD recommended for performance
└─ Replicated across NonStop VMs (like physical disc pairs)

-----------------------------------------------------------------------------------------------------------------------

Key vNS Components

VirtualNet (Software ServerNet)

Physical NonStop: ServerNet = dedicated hardware interconnect
Virtualized NonStop: VirtualNet = Ethernet-based software equivalent

├─ Connects NonStop VMs for process pair synchronization
├─ Low-latency Ethernet (10GbE / 25GbE / 100GbE)
├─ RoCE (RDMA over Converged Ethernet) for performance
└─ Must be low latency (<1ms between VMs recommended)

vCLIM (Virtual CLIM)

Physical NonStop: CLIM = dedicated Linux I/O module hardware
Virtualized NonStop: vCLIM = Linux VM handling I/O

├─ Runs as Linux VM (same CLIM software, virtual hardware)
├─ Handles TCP/IP networking for NonStop VMs
├─ Handles storage I/O
└─ Multiple vCLIMs for HA (N+1 like physical CLIMs)

NonStop OS on VMs

Same NonStop OS (TNS/X) runs inside VMs:
├─ Guardian environment: unchanged
├─ OSS (POSIX) environment: unchanged
├─ All subsystems: TMF, Pathway, SQL/MX, etc.
└─ Apps: Binary compatible, no recompile needed

-----------------------------------------------------------------------------------------------------------------------

vNS vs Physical NonStop Comparison

┌───────────────────────┬──────────────────────┬─────────────────────────────────────┐
│ Feature │ Physical NonStop │ Virtualized NonStop │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Fault tolerance │ Hardware-based │ Software-based │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Processor pairs │ Physical CPU modules │ VM-based process pairs │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Interconnect │ ServerNet (HW) │ VirtualNet (SW/Ethernet) │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ I/O modules │ Physical CLIMs │ vCLIMs (Linux VMs) │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Deployment │ Dedicated servers │ Any VMware x86 infrastructure │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Cost │ High CapEx │ Lower CapEx / OpEx option │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Performance │ Maximum │ Slightly less (hypervisor overhead) │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ App compatibility │ Native │ Binary compatible │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Migration │ N/A │ Lift-and-shift from physical │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Scalability │ Add hardware modules │ Add VMs │
├───────────────────────┼──────────────────────┼─────────────────────────────────────┤
│ Cloud-ready │ No │ Yes (private cloud) │
└───────────────────────┴──────────────────────┴─────────────────────────────────────┘

-----------------------------------------------------------------------------------------------------------------------

Deployment Requirements

Minimum vNS Cluster

3 physical x86 servers minimum:
├─ Server 1: NonStop VM 0 (primary processor)
├─ Server 2: NonStop VM 1 (mirror processor)
├─ Server 3: NonStop VM 2 (mirror processor)
│
├─ Each server: HPE ProLiant DL380/DL560 or equivalent
├─ CPU: Intel Xeon (current gen)
├─ RAM: 384GB+ per server (recommended)
├─ Storage: SSD/NVMe (local or shared SAN)
└─ Network: 25GbE minimum, 100GbE recommended

VMware Requirements

├─ VMware vSphere 7.x or 8.x
├─ vCenter Server for cluster management
├─ vSphere HA enabled
├─ DRS (Distributed Resource Scheduler)
└─ Storage vMotion capability

Networking Requirements

├─ Dedicated VirtualNet VLAN (process pair sync)
├─ Management network (OSM, admin)
├─ Application network (client traffic)
├─ Storage network (iSCSI/FC/NVMe-oF)
└─ Low latency (<1ms) between all NonStop VMs

-----------------------------------------------------------------------------------------------------------------------

vNS Fault Tolerance Model

How Software Fault Tolerance Works

Physical: CPU module fails → Hardware failover
Virtual: VM fails → NonStop software failover

Step 1: NonStop process pair running across 2+ VMs
Primary process = NS VM 0
Backup process = NS VM 1

Step 2: NS VM 0 host fails (server crash, power loss)
├─ VirtualNet detects VM 0 gone
├─ NS VM 1 backup takes over immediately
└─ Application continues without interruption

Step 3: VMware HA restarts NS VM 0 on another host
└─ Re-joins cluster, becomes new backup

Failure Scenarios Covered

Physical server hardware failure
VM crash / OS panic
Network switch failure (redundant paths)
Storage controller failure (mirrored)
Application process failure (process pairs)
Datacenter-wide failure (needs RDF/remote site)

-----------------------------------------------------------------------------------------------------------------------

vNS Use Cases

┌────────────────────┬───────────────────────────────────────────────────┐
│ Use Case │ Description │
├────────────────────┼───────────────────────────────────────────────────┤
│ Dev/Test │ Cheaper than physical for dev environments │
├────────────────────┼───────────────────────────────────────────────────┤
│ Modernization │ Migrate aging physical NonStop to modern infra │
├────────────────────┼───────────────────────────────────────────────────┤
│ Private Cloud │ Run NonStop workloads in enterprise VMware cloud │
├────────────────────┼───────────────────────────────────────────────────┤
│ Security │ Euroclear uses vNS for security environments │
├────────────────────┼───────────────────────────────────────────────────┤
│ DR site │ Virtual NonStop as DR replica of physical primary │
├────────────────────┼───────────────────────────────────────────────────┤
│ Cost reduction │ Replace aging hardware with commodity servers │
└────────────────────┴───────────────────────────────────────────────────┘

-----------------------------------------------------------------------------------------------------------------------

vNS Software Stack (Same as Physical)

┌─────────────────────────────────────┐
│ Applications (COBOL, pTAL, Java) │ ← Binary compatible
├─────────────────────────────────────┤
│ Middleware (Pathway, TMF, TS/MP) │ ← Unchanged
├─────────────────────────────────────┤
│ Database (SQL/MX, Enscribe) │ ← Unchanged
├─────────────────────────────────────┤
│ NonStop OS (TNS/X Guardian + OSS) │ ← Unchanged
├─────────────────────────────────────┤
│ VirtualNet (Software ServerNet) │ ← NEW (replaces HW)
├─────────────────────────────────────┤
│ VMware vSphere (ESXi Hypervisor) │ ← NEW layer
├─────────────────────────────────────┤
│ x86 Hardware (ProLiant servers) │ ← Standard hardware
└─────────────────────────────────────┘

-----------------------------------------------------------------------------------------------------------------------

vNS Documentation & References

HPE Virtualized NonStop Software Product Page:
https://www.hpe.com/us/en/servers/nonstop.html
(See: "HPE Virtualized Nonstop Software" section)

vNS Software Datasheet (A00001556ENW):
https://www.hpe.com/psnow/doc/a00001556enw.pdf

HPE NonStop Family Brochure (includes vNS):
https://www.hpe.com/psnow/doc/4aa4-2988enw.pdf

GreenLake Flex for NonStop:
https://www.hpe.com/psnow/doc/a50010620enw.pdf

HPE Support Portal (vNS config guides):
https://support.hpe.com/hpesc/public/home
→ Search: "Virtualized NonStop" or "vNS configuration"

HPE NonStop Info Hub:
https://www.hpe.com/info/nonstop

-----------------------------------------------------------------------------------------------------------------------

topic Query: Knowing Nonstop in HPE NonStop Compute

Knowing Nonstop

Re: Knowing Nonstop

Re: Knowing Nonstop

Query: Knowing Nonstop