Mark Whitfield is a prominent UK-based, SC-cleared Senior IT Project Manager, Engagement Manager, and technology executive with over 35 years of experience spanning the entire Software Development Lifecycle (SDLC). He specialises in complex digital transformations, hybrid cloud migrations, and API-led system integrations.
Throughout his career, he has successfully delivered enterprise-scale solutions for massive blue-chip clients, including Barclays Bank, Jaguar Land Rover (JLR), Royal Mail Group (RMG), Lloyds Banking Group, and the Bank of England.
Executive Overview:
Core Expertise: Hybrid Cloud Migrations (Azure, AWS), API middleware architectures, and digital banking platforms.
Methodologies: Certified PRINCE2 Practitioner and Agile SCRUM delivery lead.
Security Clearance: Active UK Security Check (SC until 2031) clearance for public and defense-sector projects.
Industry Portfolio: Banking, Automotive, Gambling/Casinos, Aerospace & Defence, and Regional Government.
Professional Timeline & Milestones:
1990–1995 (Early Engineering): Began his career immediately after graduating in Computing. He worked as a core programmer at The Software Partnership, building cutting-edge electronic banking software (sp/ARCHITECT-BANK) on legacy Tandem Mainframes (now HPE NonStop).
1995–2013 (Insider Technologies Limited): Spent 18 years escalating from a Senior Programmer into a strategic project manager in Salford Quays, UK. He spearheaded high-volume mainframe transaction monitoring systems and ATM software delivery for major global banking institutions like HSBC and Al Rajhi Bank.
2013–2016 (Retail & Gaming Delivery): Transitioned to Wincor Nixdorf as an Agile IT PM managing ATM software pipelines, followed by a Senior PM role at Betfred, delivering complex mobile sportsbook and online payment gateways.
2016–Present (Enterprise Leadership): Joined Capgemini as a client-facing Engagement Project Manager. He later augmented into MuleSoft (a Salesforce company) as a Delivery Manager for the Anypoint Platform, directing massive cloud infrastructure overhauls.
Thought Leadership & Knowledge Sharing
Beyond active corporate execution, he is the creator of PROject Templates, an open professional repository where he publishes free upgrade enterprise project tracking models, RAID logs, and Agile planning frameworks used extensively by modern PMOs.
The European BASE24 User Group (EBUG) was established in the 1980s as an independent, community-led organization for users of the BASE24 payment processing system developed by Applied Communications, Inc. (now ACI Worldwide).
Originally a regional forum for IT professionals in Europe to discuss HPE NonStop (Tandem) transaction monitoring and network security, the group expanded globally over time.
Insider Technologies regularly attended EBUG, booth in 2007 – RTLX now ETI-NET C-Deep
Following ACI’s withdrawal of direct corporate backing, EBUG evolved into “The Independent Group for All Payments System Users”—affectionately known as the Everybody Belongs User’s Group—welcoming users of multiple payment platforms like Postilion.
The detailed historical timeline of EBUG and the evolution of its core system, BASE24, outlines its development from a regional user collective to a global payments forum:
The Foundation Era (1975–1989)
1975: ACI is founded in Omaha, Nebraska, initially developing software for fault-tolerant Tandem NonStop computers to connect ATMs to bank networks.
1982: The BASE24 product family is officially launched globally, acting as “baseline” software for 24-hour financial operations.
1980s:EBUG is established as a regional European community for BASE24 users to collaborate on ATM networking and transaction processing.
Early 2000s: EBUG annual conferences grow in prestige, featuring technical tracks on BASE24 transaction logging, Point-of-Sale (POS) networks, and network resilience.
2007: EBUG hosts a high-profile international conference in Istanbul, Turkey.
2008: EBUG hosts its annual meeting in Vienna, Austria, which is historically noted as a pivotal year where ACI began supporting immediate payments in Europe and discussed a strategic shift toward IBM platforms. ACI officially announces the future retirement of “BASE24 Classic”.
2009: The conference is held in Prague, Czech Republic, maintaining strong community support for BASE24 on Tandem servers despite broader industry shifts.
Global Expansion, Rebranding & The Cloud Era (2010–Present)
2012: ACI introduces BASE24-eps, their next-generation, platform-independent payments engine designed to replace the legacy BASE24 on HPE NonStop. EBUG’s technical focus shifts to real-time payments and log extraction.
2013: With ACI ending direct involvement, the user group officially rebrands as the “Everybody Belongs User’s Group” at their conference in London, expanding attendance to professionals from Mexico, South Africa, and Australia.
2015: ACI celebrates 40 years in payments. EBUG solidifies its status as a supplier-agnostic payments forum, opening sessions to non-BASE24 users.
2020s: With BASE24 Classic retired, legacy users migrate to modern systems like BASE24-eps for cloud deployments and immediate payments.
Recent Years: ACI goes live as a pioneer in the Federal Reserve’s FedNow Service, building upon the decades-long transaction switching architecture first developed in the 1970s and 1980s.
European BASE24 User Group (EBUG) Timeline from Inception
Focus: Electronic banking programming and development on Tandem Mainframe Computers.
Projects: Wrote, developed, and maintained software like sp/ARCHITECT-BANK and associated billing software (in Poole, 1993). This involved building early electronic banking systems for desktops long before internet banking was prevalent.
Location: Insider Technologies, Salford Quays, Manchester, UK
Focus: NonStop product management, software design, and real-time event monitoring.
Projects: Product managed software lifecycles for four monitoring products (two NonStop based). This included creating health and diagnostic tools (RTLX, Reflex 80:20, Reflex ONE24,XPERT24) for mission-critical NonStop environments. He also deployed volume testing on early HP NonStop S7000 nodes for CRESTCo in London in 1997.
Insider Technologies, Salford Quays, Manchester, UK
Location: Wincor Nixdorf & ATM/POS Financial Services, UK
Focus: Modernization and migration of legacy systems.
Projects: Managed a £5M+ replacement of legacy HP NonStop software systems at a large UK retail bank, migrating functionalities to AIX-based J2EE and Oracle architectures.
Focus: Delivery of enterprise-scale middleware, digital transformation, and cloud.
Projects: Acts as an Engagement Manager and SC-Cleared Project Manager. Focus includes Agile software delivery for Air Traffic organisations (e.g., iOS applications for military and public-facing airspace tracking) and rolling out middleware solutions.
Running natively on the fault-tolerant HPE NonStop platform (formerly Tandem Computers), it utilizes a modular architecture to acquire, authenticate, route, and authorize financial transactions.
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
The application modules of ACI BASE24 (spanning Classic and modern BASE24-eps configurations) are categorized in complete detail below:
💳 Channel Acquisition Modules
These front-end modules connect directly to consumer-facing self-service devices and touchpoints to ingest financial messages.
BASE24-pos: Facilitates electronic data interchange with Point of Sale (POS) merchant terminals, accepting debit, credit, and smart card transactions.
Stored Value Module (SVM): A localized sub-component within channel management dedicated to the online issuance, balance check, and validation of stored-value gift cards.
🔄 Routing, Switching, & Interfacing Modules
These modules orchestrate the delivery of messages from endpoints to localized authorization hosts or global networks.
BIC ISO Interface: Implements standard ISO 8583 payment messaging protocols to communicate directly with major international networks (such as Mastercard or Visa).
ACI Commerce Gateway: Operates as a secure payment gateway firewall, linking internal HPE NonStop processing routines with public internet channels.
🔐 Security & Authentication Modules
Data integrity modules protect transactions and enforce industry-standard security.
Transaction Security Services (TSS): Manages PIN verification, encryption/decryption tasks, and hardware security module (HSM) messaging, including native Triple DES (3DES) support.
These back-end engines decide whether a transaction flight should be accepted, declined, or deferred.
Enhanced Authorization Module: Runs customized business logic scripting to evaluate cardholder limits, fraud signals, and stand-in authorization processing.
Positive Balance File (PBF) Interface: Interfaces with real-time local file structures to check account limits when backend core banking host systems are offline.
📊 Back-Office & Data Management Modules
These modules ensure post-transaction data is accounted for, settled, and audited.
Interchange Log File (ILF) / Transaction Log File (TLF for ATM, PTLF for POS): Core architectural data constructs that maintain comprehensive records of all ongoing financial messages for balancing and error recovery.
BASE24-infobase: Provides centralized tools for operational reporting, financial data clearing, settlement processing, and accounting audits.
🛠️ HPE NonStop System Integration Architecture
BASE24 is highly reliable because it integrates with native HPE NonStop mainframe utilities:
PATHWAY (PATHCOM): Acts as the transaction processing middleware to dynamically load-balance BASE24 server processes across multiple CPUs.
Enscribe & NonStop SQL/MX: Serves as the native flat-file or relational database layer optimized for low-latency, high-concurrency write operations.
HPE Shadowbase / AutoTMF: Interacts with the Transaction Monitoring Facility (TMF) to enable active/active dual-site replication, providing instant failover for near-zero transaction downtime.
ACI BASE24 core components on HPE NonStop mainframe platform
BASE24 Electronic Funds Transfer (EFT) software application developed by ACI Worldwide, Overview
Mark Whitfield’s project involvement with ACI Worldwide’s BASE24 / BASE24-eps and XPNET communication middleware is rooted deeply in his tenure at Insider Technologies Limited (ITL) and subsequent senior project management roles. His work primarily spans real-time performance monitoring, transactional tracking, and infrastructure management across HPE NonStop (Tandem) platforms.
His involvement across specific initiatives and client deployments is categorised below:
Product Development & R&D Projects
BASE24 XPNET Monitoring in Reflex ONE24
Role: R&D Lead and Software Developer.
Involvement: Researched and developed specialised software utilities to automatically detect and extract architectural information from XPNET components. He leveraged XPNET EMS (Event Management Service) events and user requests to facilitate real-time monitoring. These components were mapped into graphical drill-down object trees inside the Reflex Status Monitor application.
XPERT24 (Performance Monitoring & Tracking)
Role: R&D Lead, Technical Contributor, and Project Manager.
Involvement: Managed the lifecycle of this NSK-based monitoring tool, which tracks XPNET performance counters including states, traffic rates, and queues across lines, stations, nodes, and processes. The project also involved building mechanisms to track transaction approval and denial metrics over ATM and POS networks.
Client Deployment & Customisation Projects
HSBC Transaction Monitoring Project
Role: Technical Lead / Solution Designer.
Involvement: Designed and executed the implementation of ITL’s RTLX Reactor product on HP NonStop. The project required mapping monitoring solutions into HSBC’s heavily customised payment ecosystem to track ATM and POS transactions governed by BASE24.
Off-shore Retail Banking Transaction Tracking (Riyadh, Saudi Arabia)
Role: IT Project Manager (2013).
Involvement: Managed the delivery of a massive log-parsing project utilizing the BASE24 Classic payment framework. The project safely extracted, relayed, and optimized the parsing of multiple Terabytes of historical ATM and POS transaction logs archived on tapes, moving them into a modern reporting system.
Global Payments / Standard Chartered Integration Project
Involvement: Integrated real-time BASE24 transaction tracking and XPNET capabilities directly into external corporate enterprise frameworks, specifically IBM Tivoli and XPERT24.
Lloyds Banking Group (LBG) Estate Transformation
Role: Senior Project Manager.
Involvement: Led a massive migration strategy that decoupled ATM driving responsibilities away from BASE24 Classic running on HP NonStop platforms, transferring them to Wincor’s ProClassic Enterprise (PC/E) environment.
HP OpenView Operations (OVO) is a foundational enterprise systems management (ESM) platform designed to centrally monitor and manage infrastructure, multi-vendor operating systems, and enterprise applications across distributed IT environments.
The system operates on an Agent-Server Architecture. Core components include:
Management Server: Central hub that aggregates system logs, processes alerts, correlates events, and triggers automated remediation scripts.
Smart Plug-ins (SPIs): Specialized modular add-ons that inject domain-specific monitoring logic for applications like Oracle databases, Microsoft Active Directory, or SAP.
Intelligent Agents: Lightweight background processes deployed on managed nodes to collect log events, metrics, and state data, formatting them into structured OVO messages.
1. HP OVO screenshot in 2002
2. HP OVO screenshot in 2002
See bottom of this post for HPE NonStop (previously Tandem) monitoring in OpenText Operations Bridge Manager. I overlooked an integration with HP OpenView Operations for a HPE NonStop product in 2002, called Reflex 80:20.
Detailed Timeline Breakdown by Era and Year
🌅 Era 1: Origins and The Foundation (Late 1980s – 1994)
This era established HP’s footprints in IT infrastructure management, pivoting from pure SNMP network map discovery toward server telemetry.
Late 1980s: HP releases Operations Center (OpC) as an add-on application for its core Network Node Manager (NNM) platform. It replaces slow SNMP polling with Remote Procedure Calls (RPC) to gather host logs.
1990–1993: HP scales OpC into a robust engine capable of executing basic automation scripts on remote UNIX boxes when specific thresholds break.
🚀 Era 2: The “ITO” and OpenView Operations Boom (1995 – 2000)
The framework shifted from isolated utilities into an integrated, market-dominating enterprise suite.
1995: HP tightly merges NNM and Operations Center into a single product called IT Operations (ITO) Version 3.x.
1996:HP OpenView Service Navigator is embedded into the product line. It provides a graphical hierarchy of business services instead of just a raw list of broken servers.
1999: The suite formally adapts to include broad SNMP traps alongside its core agents and is renamed HP OpenView Operations ITO.
🔄 Era 3: Platform Split and VantagePoint Transition (2001 – 2006)
HP decoupled its codebases to natively handle Windows NT/2000 scaling alongside legacy Unix environments while heavily investing in product renaming.
2001: HP briefy rebrands the suite to HP VantagePoint Operations (VPO). However, customer brand loyalty forces them to quickly pivot back to the popular HP OpenView Operations (OVO) naming convention.
2002: Codebases officially bifurcate into OVOU (OpenView Operations for Unix) and OVOW (OpenView Operations for Windows, built natively on Microsoft WMI frameworks).
2005:OVO Version 8.0 drops. It features heavy integration capabilities for external service desks, advanced HTTP/HTTPS agent communication protocols, and a refreshed Java GUI console.
🏢 Era 4: The Business Technology Optimization (BTO) Era (2007 – 2016)
Massive corporate acquisitions changed the software landscape. OVO ceased to be a standalone system monitoring tool and transformed into an automated operations center.
2007: HP drops the legendary “OpenView” moniker. Following the acquisitions of Mercury Interactive, Peregrine, and Opsware, the suite is rebranded as HP Operations Manager (HPOM) under the HP Business Technology Optimization (BTO) banner.
2009: HP rolls out Operations Manager i (OMi), integrating topology-based event correlation (TBEC) to suppress duplicate alert storms across the data center.
2015: Hewlett-Packard splits into two companies; the portfolio lands under Hewlett Packard Enterprise (HPE). The engine is bundled into the HPE Operations Bridge (OpsBridge) suite.
☁️ Era 5: Divestiture and Modern Legacy (2017 – Present)
2017: HPE spins off its enterprise software division. The entire legacy OpenView/Operations Manager portfolio is sold to Micro Focus.
2023:OpenText completes its acquisition of Micro Focus. The underlying technical heritage of the old OVO agents survives today, evolved into cloud-ready containerized architectures inside the modern OpenText Operations Bridge cloud monitoring portfolio.
OpenText Operations Bridge Manager Screenshot example
HPE NonStop (previously Tandem) Monitoring
Micro Focus Operations Bridge (now part of OpenText AI Operations Management) provides end-to-end IT monitoring by consolidating data from over 200 sources. For HPE NonStop, it utilizes specialized Management Packs to ingest metrics, system events, and health data for comprehensive, real-time hybrid IT analysis.
To monitor HPE NonStop servers using the modern OpenText Operations Bridge/AIOps platform, the setup revolves around the Operations Bridge Manager (OBM) and targeted management packs:
Management Packs for HPE NonStop: OpenText provides specific management packs and solutions designed for NonStop systems. These capture system health, CPU/disk metrics, pathway status, and system messages.
Operations Agent: A lightweight agent is deployed directly on the NonStop nodes, which securely streams local performance data and events back to the central OBM console.
Centralized Event Consolidation: OBM acts as a “manager of managers”. It ingests the NonStop events and correlates them alongside data from your cloud (AWS/Azure), containers, and network endpoints.
AIOps and Remediation: The platform utilizes built-in machine learning to reduce alert noise and accelerate root cause analysis. You can also use automated Runbooks to automatically remediate known issues on the NonStop platform.
Because the platform has been fully integrated into the OpenText portfolio, these integrations are supported across containerized deployments, on-premise, or SaaS models.
The HPE NonStop architecture (originally engineered by Tandem Computers in 1976) is a specialized, 100% fault-tolerant computing platform designed to achieve continuous application availability and absolute data integrity. Unlike traditional mainframes or high-availability clusters that rely on rapid rebooting or switching resources upon a crash, NonStop prevents downtime entirely by masking failures through a hardware-software co-designed shared-nothing architecture.
At the physical tier, a NonStop system is built as a Loosely Coupled Multiprocessing (LCM) environment.
Independent Processor Modules: A single system consists of 2 to 16 independent CPUs (expandable via clustering up to 4,000+ CPUs). Each processor module contains its own dedicated Intel Xeon cores, memory, and I/O logic. Processors share no main memory, buses, or execution states. This isolation guarantees that a memory corruption or hardware crash in one CPU cannot physically propagate to another.
The Interconnect Fabric (ServerNet / RoCE): Because CPUs share nothing, they cooperate entirely by passing high-speed messages. Historically, this handled via a proprietary dual-bus named Dynabus, which evolved into ServerNet (the foundational grandfather of InfiniBand). Modern HPE NonStop X systems leverage RDMA over Converged Ethernet (RoCE) as the multi-gigabit interconnect fabric, providing dual-path, point-to-point messaging with sub-microsecond latency.
Dual-Ported, Redundant I/O Controllers: Every storage device, network interface, and controller card is physically dual-ported and cross-connected to two separate processor modules. If Processor A fails, Processor B seamlessly accesses the disk or network line using the alternate hardware path.
No-Spare, Active-Active Components: Every active element operates under a “no-spare” philosophy. Power supplies, cooling fans, and storage arrays are fully redundant and hot-swappable, ensuring the system can be repaired or upgraded while fully operational.
2. Operating System Architecture: NonStop OS (Guardian)
The foundational operating system is NonStop OS, which embeds the Guardian Kernel.
Distributed Copy Model: Every individual processor module loads and runs its own separate copy of the Guardian kernel. Rather than a monolithic OS orchestrating all chips, the system runs as a highly cooperative, message-driven distributed microkernel OS.
The Message System: The core of Guardian is its message router. Every operational request—whether writing a line to a database, opening a network socket, or checking a disk—is written as an inter-process message sent across the RoCE fabric. If a local resource is occupied, the message router redirects the request transparently across the fabric, making the entire cluster appear to applications as a single system image (SSI).
Continuous Heartbeats: All components and processors continually broadcast periodic “alive” heartbeat messages to one another. If a processor fails to respond to a heartbeat within a few milliseconds, the remaining CPUs immediately sever ties with it, declare it dead, and safely re-route pending workloads.
3. Software Fault Tolerance: Process Pairing
Hardware isolation is only half the battle. To tolerate software failures without dropping transactions, NonStop utilizes Process Pairs.
Primary and Backup Processes: When a critical application or system service starts, it creates two instances: a Primary Process executing on Processor 1, and a Hot-Standby Backup Process residing on Processor 2.
Real-Time Checkpointing: As the primary process performs work (e.g., executing a financial transaction step), it sends regular checkpoint messages to the backup process. These checkpoints copy vital state changes, register values, and memory updates.
Instant Takeover: If Processor 1 crashes, the Guardian OS instantly promotes the backup process to Primary. Because the backup contains the mirror state of the last transaction checkpoint, it picks up execution precisely where the failed process stopped. No state is lost, no connections drop, and the end-user experiences zero interruption.
4. Database & Storage Architecture: Enscribe, NonStop SQL, and TMF
Data integrity is paramount in NonStop’s design. It enforces strict ACID compliance at massive scale through layered data management software.
Enscribe & NonStop SQL/MX: NonStop supports Enscribe (a highly resilient structured file system) and NonStop SQL/MX (an ANSI-compliant relational database management system). Both are entirely decentralized, natively distributing table partitions across different physical disk drives managed by separate CPUs.
Mirrored Disks: Storage volumes are configured via volume-level mirroring (Disk 1 and Disk 2 track identical data blocks). Disk writes are executed in parallel across distinct I/O paths. If a drive fails or a sector corrupts, reads are immediately diverted to the mirror disc.
Transaction Monitoring Facility (TMF): TMF is the protected transaction manager. It acts as a distributed two-phase commit coordinator. If an application crashes mid-transaction, or an entire processing module loses power, TMF uses audit logs to back out incomplete transactions cleanly, guaranteeing that the database is never left in an inconsistent or corrupt state.
The development of programming languages on the HPE NonStop platform (originally founded as Tandem Computers) is tightly bound to its architectural hardware transitions: from custom CISC stack machines to MIPS RISC, Intel Itanium, and eventually standard Intel x86-64 infrastructures.
Detailed List of NonStop Programming Languages
1. Core Proprietary & System Languages
TAL (Transaction Application Language): The foundational system programming language for Tandem. It is a block-structured, machine-dependent procedural language designed to compile directly into highly efficient machine instructions. It features ALGOL/Pascal-like syntax but implements C-like semantics, structural pointers, and weak data typing.
pTAL & epTAL: Specialized evolutions of TAL. Rather than rewriting legacy codebases from scratch during architecture shifts, pTAL was introduced to compile existing TAL code natively into MIPS RISC architectures. Later, epTAL was developed to target Intel Itanium microprocessors.
TACL (Tandem Advanced Command Language): A built-in command interpreter and interpreted scripting language. It functions like a Unix Bash shell but features highly complex macro capacities used to orchestrate system configurations, monitor processes, and automate failover procedures.
2. Enterprise & Enterprise Legacy Languages
COBOL85 (and older COBOL74): The undisputed workhorse of NonStop commercial workloads. HPE’s tailored implementation of the COBOL85 standard natively interfaces with the Guardian OS. It allows programmers to embed SQL/MP statements and program fault-tolerant Process Pairs through HPE NonStop Pathway (TS/MP).
SCOBOL (Screen COBOL): A specialized, high-level structural derivative of COBOL utilized exclusively to build blocks for character-cell terminal interfaces (such as the 6530 terminal environments) running within Pathway architectures.
NonStop SQL (SQL/MP and SQL/MX): While technically a database system, its embedded syntax acts as a declarative language integrated into C and COBOL. SQL/MP works with the legacy Guardian file system, while SQL/MX brings ANSI-compliant SQL closely bound with the Open System Services (OSS) environment.
3. Standard Mainstream Languages
C & C++: Heavily introduced during the RISC transition to allow software portability. Mainstream development on modern NonStop systems uses standard C/C++ cross-compilers. They run in either the native fault-tolerant Guardian personality or the standard POSIX-compliant Open System Services (OSS) environment.
Java: A first-class language layer deployed natively on NonStop. HPE optimizes the Java Virtual Machine (JVM) to scale across multi-CPU shared-nothing frameworks, allowing modern enterprise web apps to run with out-of-the-box system availability.
4. Modern Open-Source Options
Python, Go, & JavaScript (Node.js): Modern procedural and script utilities provided by HPE. These environments leverage the OSS POSIX platform layer, running modern DevOps orchestration, microservices, and hybrid-cloud pipelines alongside the native database engines.
Detailed Timeline Breakdown by Era and Year
The evolution of NonStop languages maps directly across distinct engineering ownership eras.
The Proprietary Foundation Era (Tandem Computers: 1974–1989)
1976: Tandem ships the original Tandem/16 (NonStop I). TAL is the only available language on the platform. The entire Guardian Operating System is written completely in TAL.
1981: The NonStop II hardware is introduced. Tandem expands language support to include COBOL74, FORTRAN, and BASIC to attract mainstream banking clients.
1983: Tandem releases the Transaction Monitoring Facility (TMF) and Pathway application management software. SCOBOL is introduced alongside them to program secure terminal entry interfaces.
1985: TACL is deployed, completely modernizing the command line shell ecosystem with scalable macros and structured operational control.
1986: Tandem launches NonStop SQL, the first linearly scalable, fault-tolerant relational database engine. Embedded SQL syntax is integrated directly into TAL and COBOL compilers.
1988: Compilers undergo a major update to natively support the newly established COBOL85 standard, which quickly replaces COBOL74 for all mission-critical banking transactions.
The Open Systems & Hardware Transition Era (Compaq: 1990–2001)
1991: Hardware migrates from CISC stacks to MIPS RISC architectures with systems like the Cyclone/R. To protect client software assets, Tandem delivers the pTAL compiler to translate TAL source code into native RISC binaries.
1995: Tandem introduces Open System Services (OSS), a POSIX-compliant UNIX subsystem running over the Guardian kernel. This brings full-scale, native native compliance for standard ANSI C and C++ programming.
1997: Compaq acquires Tandem Computers. Engineering shifts heavily toward implementing Java on NonStop, targeting cross-platform, enterprise internet-banking codebases.
2000: NonStop SQL/MX is released. It allows developers to use embedded SQL statements within standard C, C++, and emerging Java applications inside the OSS runtime environment.
The Corporate Alignment & Itanium Era (Hewlett-Packard: 2002–2014)
2002: HP merges with Compaq. Java is designated as a first-class citizen on the platform, receiving deeper optimization to tie into native clusters seamlessly.
2005: HP releases the Integrity “NonStop i” servers, moving processors away from MIPS onto Intel Itanium architectures. The epTAL compiler is rolled out alongside standard C/C++ updates to seamlessly compile older environments onto Itanium.
2011: Open-source scripting engines, including early ports of modern Python, are introduced to the OSS environment, easing the system-management burden for engineers unfamiliar with legacy TACL.
The Modern Enterprise Era (Hewlett Packard Enterprise: 2015–2026)
2015: HP splits, and the platform transitions to HPE. Standard Intel x86-64 hardware dominates with the NonStop X architecture. Compilers utilize an standard GCC/LLVM-based back end, allowing normal Linux/Unix C++ programs to build on NonStop with minimal alteration.
2020: Sales of Itanium systems officially terminate. Legacy languages like TAL are deprecated for new software creation but are preserved to support older, foundational logic.
2023–2024: HPE rolls out modern cloud-ready DevOps Starter Kits. Full, native support is added for modern languages such as Go, modern Python 3.x, and Node.js, allowing them to integrate into modern automated CI/CD build environments.
HPE NonStop Tandem Programming Languages and Development Timeline
HPE NonStop Pathway is a premier transaction processing and application server environment (TS/MP) that powers mission-critical Online Transaction Processing (OLTP). It handles critical application services—such as fault tolerance, load balancing, memory management, and process scheduling—automatically, allowing developers to focus strictly on business logic.
HPE NonStop Pathway is a transaction processing & application server environment (TS/MP)
Detailed Timeline Breakdown
The history and evolution of the Tandem NonStop platform and its Pathway environment span decades of architectural transformations and corporate ownership, categorized by distinct hardware and software eras:
1. The Tandem Era (1974–1997)
1974: Tandem Computers Inc. is founded by Jimmy Treybig to build the first fault-tolerant commercial hardware.
1976: The first Tandem NonStop system (NSI) is launched. Early apps had to be manually coded for fault tolerance.
1981: NonStop II is released, bringing 32-bit addressing.
1983: The Transaction Monitoring Facility (TMF) is introduced. Together with the launch of the Pathway transaction management software, the need for programmers to write manual fault-tolerance logic into their code is officially eliminated.
1986: Tandem releases the EXT as an entry-level system, followed by the VLX.
1991: Tandem introduces the Cyclone/R and initiates a massive architectural shift away from proprietary stack machines towards MIPS RISC processors.
1997: Compaq acquires Tandem Computers, placing the NonStop product line under its umbrella.
2. The Compaq & Early HP Era (1997–2014)
2001–2002: Hewlett-Packard (HP) merges with Compaq. The platform is rebranded as HP NonStop.
2005: The HP Integrity NonStop (TNS/E) series is introduced, migrating the fault-tolerant platform to Intel Itanium microprocessors. Pathway continues to be the main driver for high-volume banking and telecom applications.
2011: Further hardware advancements lead to the release of HP Integrity NonStop BladeSystems.
3. The Modern HPE Era (2015–Present)
2015: Hewlett-Packard splits, and the NonStop environment transitions to Hewlett Packard Enterprise (HPE).
2015/2016: Introduction of NonStop X (TNS/X) systems, marking the platform’s migration to standard Intel x86-64 processors and adopting InfiniBand interconnects. Pathway capabilities are updated to span dynamic server classes across multiple systems (Pathway Domains).
Present: HPE continues to modernize the NonStop architecture, integrating the platform with HPE GreenLake for consumption-based models and providing native support for modern DevOps tools and hybrid cloud deployments.
In the HPE NonStop ecosystem, EMS (Event Management Service) is the core software subsystem responsible for collecting, formatting, filtering, logging, and routing system and application event messages. It provides fault-tolerant monitoring by gathering data from EMS collectors and selectively delivering alerts to consoles, log files, or automated management applications.
The evolution and detailed historical timeline of NonStop EMS events and architecture is broken down by era below:
1. The Tandem Guardian Era (Late 1970s – 1980s)
Focus: Foundation of Fault-Tolerant Event Logging
1976: Tandem releases the original Tandem/16 (NonStop I) system. Early event handling was primarily a rudimentary terminal console logging process.
1978: System administrators struggled with message scaling as clusters and terminal networks expanded. Tandem began developing structured event tracking, paving the way for standardized subsystem messages.
1980s: Introduction of early message formatting. Event messages 1 through 511 were reserved for unformatted, raw console events. The Event Management Service (EMS) was gradually formalized to centralize scattered terminal messages.
2. The D-Series & TMF Era (1990s)
Focus: Distributed Management & The Birth of Modern EMS
1991: Tandem releases the Cyclone/R (CLX/R) and later the Himalaya K-series using MIPS processors.
1993: The publication of the seminal EMS Reference Summaries standardized EMS APIs and SPI (System Programming Interface). Event IDs were structured into standardized subsystems (e.g., negative-numbered kernel messages).
1995: The NonStop Kernel introduced Open System Services (OSS), natively integrating Unix-like event logs into the Guardian architecture.
1997: Compaq acquires Tandem Computers. EMS underwent significant rewrites to interface with remote servers and client networks. The S-Series was launched utilizing ServerNet fabric, introducing advanced, distributed event collectors and distributors.
3. The Compaq Transition & HP Integration (2000s)
Focus: Web-Based Management and Automation
2000 – 2003: Legacy ViewPoint tools were expanded. The emergence of GUI interfaces and DSM/PM (Distributed Systems Management/Performance Monitor) allowed operators to browse and filter EMS logs on alternate/primary event files.
2003 – 2005: The transition to Web ViewPoint commenced, turning text-based EMS event logs into interactive, web-based graphical operations interfaces.
2006 – 2009: With HP fully in charge after merging with Compaq, EMS event viewing was modernized through TSM (Tandem/HP Systems Management) and the Open System Management (OSM) Event Viewer.
2015 – 2017: The platform is rebranded as HPE NonStop as the architecture migrates to x86 processors. EMS systems are upgraded to handle large datasets, feeding complex event processing (CEP) and SNMP trap frameworks for modern data centers.
2018 – 2023: HPE integrates NonStop systems with HPE GreenLake. EMS event logging is modernized with API-driven integrations, allowing system events to be consumed by off-platform enterprise loggers, Splunk, and cloud-management consoles.
2024 – 2026: EMS events operate in highly virtualized and hybrid cloud (x86 and Virtual NonStop) environments. Event management heavily relies on modern distributed systems where EMS distributors push logs seamlessly into centralized IT monitoring suites and continuous availability dashboards.
The HPE NonStop Technology & Business Conference (Nonstop TBC 2026)—hosted by Connect Worldwide—will take place from September 14 to September 17, 2026, at The Rosen Plaza in Orlando, Florida.
This signature annual event brings together enterprise IT leaders, software engineers, and solution architects to explore innovations shaping mission-critical environments.
Core Event Schedule
The four-day conference partitions its educational and collaborative tracks as follows:
September 14: Dedicated exclusively to HPE Education Day, featuring expanded deep-dive technical pre-conference courses.
September 15–17: The primary conference technical program and breakout sessions.
Key Focus Areas & Tracks
The 2026 event focuses heavily on bridging mission-critical legacy stability with modern software frameworks:
AI-Driven Transformation: Adapting continuous availability to the demands of modern artificial intelligence and machine learning workloads.
Digital Resilience & Security: Mitigating modern risks, modernising backup systems, and maintaining absolute runtime security.
FinTech & Payments: Real-world operational strategies from global peers managing transaction-heavy workloads.
Expanded Business Track: New for 2026, this track aligns executive business drivers with technical architectures for practical IT roadmap building.
Logistics and Pricing
Venue: The Rosen Plaza Hotel, situated at 9700 International Drive, Orlando, Florida.
Pricing: A newly reduced Early Bird Registration ticket is available for $895.
Accommodations: Registered attendees gain access to a dedicated Connect block rate of $181 per night (including tax).
Sponsorships: Major industry partners, such as comforte, sponsor the event, granting enterprise buyers direct visibility into third-party NonStop infrastructure add-ons.
ActionView.400 is an enterprise tracking and diagnostics software solution developed by Insider Technologies Limited. It was purpose-built as a dedicated monitoring tool for the Open System Interconnection / Message Handling System (OSI/MHS) X.400 subsystem deployed on Tandem, Compaq, HP, and HPE NonStop server platforms.
The software acts as a critical infrastructure layer used heavily by banking institutions, telecommunications providers, and government/military defense sectors.
It ensures that high-volume, secure electronic mail infrastructure meets strict Service Level Agreements (SLAs) by allowing engineers to account for every message, calculate end-to-end processing times, and issue real-time tracking metrics.
Detailed Timeline Breakdown by Year
1989: Insider Technologies Limited is incorporated in Manchester, England, by a collective of IT industry veterans. The firm initially focuses on building service management and custom tracking middleware for the rapidly expanding Tandem NonStop server ecosystem.
1990s (Early to Mid): As X.400 protocols become the global standard for secure EDI (Electronic Data Interchange) and military messaging, Insider Technologies develops ActionView 400. The product is integrated directly into Tandem’s core software stack and begins shipping natively with Tandem NonStop platforms.
1997: Tandem Computers is acquired by Compaq. ActionView 400 is sustained through this transition to maintain critical operations for tier-one banks and national military infrastructures relying on NonStop systems.
2002: Compaq merges with Hewlett-Packard (HP). ActionView 400 is bundled under the HP NonStop software catalog (product designation T8443), managing and diagnosing log audits like the AUDLOG framework.
2000s (Mid to Late): Insider Technologies starts shifting forward-looking tracking requirements toward its newer central architecture platform, Sentra. While ActionView 400 continues handling legacy X.400 pipelines, Sentra begins acting as a unified web console to consolidate both X.400 and modern SMTP/MIME email flows across multi-vendor systems.
2015: HP splits its corporate structures. The NonStop computing line and the management of ActionView 400 shift over to Hewlett Packard Enterprise (HPE).
2018: In December 2018, HPE officially moves ActionView 400 to Obsolete status, marking the formal end of its product life cycle and standard vendor service life.
2019 – Present: Despite official obsolescence on the HPE hardware list, Insider Technologies continues to directly support and maintain the solution for deep-legacy military, defense, and governmental bodies. Because these sectors still mandate uncompromised, zero-loss X.400 message accounting, the software remains active, feeding tracking telemetry directly into Insider’s modern Middleware Monitoring and Sentra platform interfaces.
Sentra – unified web console to consolidate both X.400 and modern SMTP / MIME email flows across multi-vendor systems
HPE NonStop MultiBatch is an advanced workload automation and scheduling manager designed explicitly for mission-critical HPE NonStop environments. Originally created to support complex scheduling needs in banking and finance, it automates job flows and parallel processing across multiple CPUs.
Detailed Description
The original NonStop batch scheduler (NetBatch) was built for basic sequential job queues. As large enterprises required deeper integration with databases, real-time events, and complex parallel schedules, MultiBatch (developed originally by Insider Technologies, now part of ETI-NET) emerged.
Core Functions: It automates job submission, tracks job flow, handles conditional parameters, manages event timers, and triggers jobs “On Demand” based on real-time system events.
High Availability: Like the underlying HPE NonStop system, MultiBatch is engineered for fault tolerance, ensuring automated workflows do not fail due to hardware or software interruptions.
Enterprise Integration: It supports Open System Services (OSS) and standardizes auditing, security, and menu-based operations across distributed NonStop systems.
Breakdown by Year / Era
The evolution of MultiBatch parallels the architectural changes of the HPE NonStop platform.
1985–1990s: Tandem Era & Origin
1985: Conceived. MultiBatch was developed by Insider Technologies specifically to meet the complex batch schedule demands of large financial institutions that exceeded native NetBatch capabilities.
Early 1990s: The system was officially rolled out for Tandem processors to automate transaction data loads and daily reconciliation tasks for ATMs and financial ledgers.
1997–2014: Compaq & Early HP Era
1997: Following Compaq’s acquisition of Tandem, MultiBatch was adapted to support the NonStop Himalaya systems and server software, which expanded data and network scaling.
2000s: During the HP Itanium and MIPS Era, MultiBatch evolved to support more dynamic processing pools and expanded job limits, increasing fault tolerance under the HP-UX integrated environment.
2014–2020: Transition to NonStop X & Modernization
2014: As HPE shifted the platform to standard Intel x86-64 processors (NonStop X), MultiBatch was updated for L-series operating systems to run efficiently on high-speed InfiniBand fabrics.
2019: Insider Technologies made significant updates to MultiBatch to modernize the GUI and improve code stability for the new generation of NonStop users transitioning to X-series hardware.
2020–Present: MultiBatch 10 & 10.2
2023: MultiBatch 10 was released. It included a new Operations GUI Server, significantly increased configuration limits (e.g., supporting up to 2,500 jobs), enhanced conditional parameters, improved processing of Open System Services (OSS), and “On Demand” job capabilities.
2025: MultiBatch 10.2 was released by ETI-NET. This update focused heavily on digital resilience, providing deep alignment with the NIST Cybersecurity Framework to protect against operational and cyber threats.
Current Status: Fully integrated into modern systems supporting the HPE GreenLake consumption-based cloud model, MultiBatch 10.2 serves as the primary automation engine for large enterprises executing complex HTAP (Hybrid Transaction/Analytical Processing) workloads.
Mark Whitfield invested many years in the HPE NonStop field from 1990. The HPE NonStop architecture (originally Tandem Computers) is a legendary fault-tolerant system known for 100% continuous availability. The platform’s hardware and software execution evolved across six distinct eras and processor transitions:
Architecture: The foundational “shared-nothing” parallel architecture. Featured redundant components (processors, disks, power supplies) connected by a proprietary dual-bus (Dynabus). The operating system provided instant automated failover.
Architecture: Expanded into 32-bit computing. To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while heavily emulating the original instruction set for compatibility.
3. The Himalaya/ServerNet Era (1997–2004)
Years: 1997–2004
Processors: MIPS R-series
Architecture: Replaced the legacy Dynabus with ServerNet, a high-speed system interconnect that served as an early precursor to modern networking fabrics. (Compaq acquired Tandem in 1997, which subsequently merged with HP in 2002).
4. The Integrity Itanium Era (2005–2013)
Years: 2005–2013
Processors: Intel Itanium (TNS/E)
Architecture: Branded as HP Integrity NonStop (NonStop i). The platform moved off proprietary silicon to standard Intel Itanium processors. This was driven by the “NonStop Advanced Architecture” (NSAA), lowering hardware costs while maintaining Availability Level 4 (AL4) standards.
5. The NonStop X (x86-64) Era (2014–Present)
Years: 2014–2026
Processors: Intel Xeon x86-64 (TNS/X)
Architecture: Fully decoupled the OS from proprietary hardware by shifting to standard Intel x86-64 processors and InfiniBand fabric. The latest compute nodes (such as the NS5 X5 and NS9 X5) utilize modern Intel Xeon Scalable processors to maintain maximum Availability Level 4 (AL4) workloads.
6. The Virtualized NonStop Era (Present)
Years: 2015–Present
Processors: Virtual Machines / Cloud / x86
Architecture: HPE extended the platform to support Virtualized NonStop Software, allowing fault-tolerant enterprise workloads to run entirely in private clouds via standard VMware or hybrid architectures, independent of specific physical servers.
These terms map directly to the foundational 1990s technology stack behind Barclays Business Master II (BBM II), one of the UK’s earliest enterprise electronic desktop banking platforms.
Before the mainstream internet, this corporate banking infrastructure relied on specialized high-availability mainframe software to process secure corporate transactions.
🧱 Architectural Component Breakdown
Barclays Business Master (BBM / BBM II): A landmark corporate desktop electronic banking solution developed by Barclays Bank. It allowed businesses to dial directly into the bank to perform inter-account transfers, check balances, and automate book-keeping long before web browser banking became standard.
sp/ARCHITECT (or sp/ARCHITECT-BANK): The core electronic banking software package that powered BBM. It was originally engineered in the late 1980s and early 1990s by The Software Partnership (a UK-based fintech software house based in Runcorn that was later acquired by Deluxe Data). It eventually evolved into the widely known CONNEX advantage payment solution.
NonStop (Tandem Computers): The underlying hardware and operating system environment. Because banking infrastructure requires absolute uptime, sp/ARCHITECT was built to run on Tandem NonStop fault-tolerant computers (now HPE NonStop). These systems utilize a unique “shared-nothing” architecture to ensure zero transactional data loss.
💻 Legacy Technical Environment
During the era when BBM was deployed across Barclays’ tech hubs (such as Knutsford), developers working on this specific stack utilized highly specialized mainframe tools:
Languages: Code for sp/ARCHITECT was primarily written in TAL (Transaction Application Language) or COBOL85, which were native to the Tandem platform.
Interfaces: Early implementations integrated desktop client interactions with the Tandem host via middleware components like Tandem Pathway and Remote Server Call (RSC) facilities.
HPE NonStop Reflex (often referred to as Reflex 80:20) is a graphical, integrated IT management suite developed by Insider Technologies. It provides continuous health monitoring, automated workflow management, and diagnostic logging for mission-critical HPE NonStop environments, serving as a single, consolidated “pane of glass” for fault-tolerant network operations.
Detailed Timeline Breakdown by Era & Year
The history of the NonStop Reflex suite closely mirrors the architectural evolution of the underlying HPE NonStop (originally Tandem) fault-tolerant hardware platforms.
1. The Tandem / ITUG Era (1989 – 1996)
1989: Insider Technologies was founded in Salford Quays, Manchester, UK, establishing an early specialization in Tandem (NonStop) messaging software and message tracking utilities.
1990s: As massive online transaction processing (OLTP) workloads grew, native Tandem utilities proved increasingly cumbersome. This spurred the initial development of platform diagnostic and event-filtering tools that would soon become the Reflex suite.
1995: Insider Technologies actively codes and launches the initial iterations of Reflex 80:20, providing operators with an aggregated view of Tandem platform events.
2. The Compaq & Early HP Transition Era (1997 – 2014)
1997: Compaq acquires Tandem Computers. Reflex 80:20 begins updating its backend architecture to handle ServerNet clustering and the newly combined enterprise platforms.
2002: Hewlett-Packard (HP) acquires Compaq. HP begins the hardware migration from proprietary processors to Intel Itanium (HP Integrity NonStop).
2004: Insider Technologies formalizes its ongoing product development, heavily pushing both Reflex 80:20 and releasing new variants like Reflex ONE24 to support extended tracking for ATM and POS networks.
2007: Reflex and other Insider monitoring software platforms are highly integrated into FIS solutions, serving tier-one global banks and stock exchanges.
2013: Insider Technologies solidifies the Reflex 80:20 status as the ultimate consolidated replacement for legacy HP components, publishing technical insights in dedicated NonStop journals.
3. The Modern HPE & x86 Era (2014 – 2019)
2014: Hewlett Packard Enterprise (HPE) is formed and officially launches NonStop X, moving the architecture onto standard Intel x86-64 processors. Reflex 80:20 interfaces are updated to support InfiniBand fabrics and the newer Open System Services (OSS) environments.
2017 – 2019: HPE launches Virtualized NonStop (vNS), bringing continuous application fault tolerance directly to private and hybrid clouds. Reflex adapts its system management capabilities to securely monitor both physical x86 non-stop servers and virtual hypervisor instances.
4. The AI & Hybrid Cloud Era (2020 – 2026)
2020: HPE ends the sale of older Itanium-based platforms. Reflex fully commits its diagnostic support to modern HPE NonStop X and vNS environments.
2023 – 2024: The NonStop platform embraces AI integrations, expanded SQL/cloud workloads, and integrations with modern DevOps tools. Reflex tools receive updates to accommodate enhanced cyber resilience tracking and modern API-driven services.
2025: HPE celebrates 50 years of the fault-tolerant NonStop computing ecosystem. The Reflex suite provides compatibility for the upgraded, high-capacity hardware iterations running the L25 series OS.
2026: Reflex remains a staple ecosystem management suite for complex enterprise networks, processing and escalating exception conditions, EMS events, and subsystem alerts within the highly available HPE GreenLake consumption models.
The Insider RTLX product at ETI-NET is now called C-Deep for Transaction Monitoring;
The official HPE Nonstop Technology Architecture is a specialized, 100% fault-tolerant infrastructure built with a tightly integrated hardware and software stack designed to eliminate any single point of failure. Formal instruction and architectural frameworks have been modernized under the newly relaunched HPE Nonstop Compute Training Portfolio curriculum.
Originally developed by Tandem Computers in 1976, the platform eventually became part of Hewlett Packard Enterprise (HPE). Unlike standard servers that can crash due to a single component failure, NonStop uses a tightly integrated, “shared-nothing” architecture to ensure that if a hardware or software component fails, another instantly takes over with zero downtime or data loss.
Core Architectural Features
To understand how HPE NonStop works, you need to understand its unique design principles:
Shared-Nothing Architecture: Every processor has its own dedicated memory, I/O channels, and copy of the operating system. No single component is shared, eliminating any single point of failure.
Process Pairs: Applications run using a primary process and a backup process on a different processor. The primary process constantly copies its state to the backup. If the primary fails, the backup immediately takes over.
Massive Scalability: Systems can scale up seamlessly from small distributed environments to massive clusters containing up to 24,000 processor cores without interrupting running operations.
Hardware Platform: The modern software environment runs on industry-standard x86 architectures, available as physical server racks (like the HPE NonStop NS9 X5) or as virtualized instances in hybrid cloud environments.
Dual Operating Environments
HPE NonStop runs a specialized operating system called NonStop OS. Inside this OS, developers and administrators interact with two distinct environments:
Guardian Environment: The native, proprietary environment optimized for high-volume Online Transaction Processing (OLTP). It handles tasks sequentially through process-oriented manually-started jobs rather than traditional automated queues.
Open System Services (OSS): A UNIX-like, POSIX-compliant environment built on top of the NonStop kernel. This allows organizations to run standard open-source applications, tools, and scripts natively alongside Guardian.
Ecosystem and Use Cases
HPE NonStop is rarely used for standard office automation or basic web hosting. Instead, it serves as the backbone for global industries where an hour of downtime could cost millions of dollars:
Financial Transactions: Powers global stock exchanges, automated teller machines (ATMs), and retail point-of-sale credit card processing, eg. BASE24.
Travel and Logistics: Runs critical airline reservation systems and real-time cargo routing infrastructure.
Database Management: Features its own highly secure, distributed database engine called NonStop SQL, which guarantees absolute data integrity across all transactions.
Modern Development: Supports traditional languages like COBOL85 and ANSI C, alongside modern DevOps integrations like Git, Ansible, and Eclipse-based IDE environments.
An architectural blueprint of an HPE NonStop environment typically separates the layout into three core interdependent layers:
Hardware & Fabric Layer: Consists of independent, loosely-coupled Processor Nodes (handling up to 24,000 cores globally) connected via an ultra-fast InfiniBand or ServerNet system fabric backbone.
I/O & Subsystem Layer: Utilizes Cluster I/O Protocols (CLIMs), splitting tasks between Storage CLIMs (SCLIMs) and Network CLIMs (NCLIMs) to isolate external communication from main processing.
Operating System & DB Layer: Runs the NonStop OS, which simultaneously manages the traditional Guardian environment, Open System Services (OSS) for UNIX/Linux paradigms, and the NonStop SQL distributed database engine.
Recommended Architecture Training Curriculum
HPE organizes its technical blueprints into structured educational paths for engineers.
1. Foundational Blueprint Concepts
Course Code: U4147S (HPE Nonstop Compute System Fundamentals).
Focus: Delivers a top-down view of system goals, transaction processing, and fundamental architecture.
Key Modules: Explores Guardian vs OSS, Pathway application management, and basic database interaction.
2. System Operations & Administration
Course Code: H1SC3S (HPE Nonstop Compute System Administration I).
Focus: Maps physical and virtual components to real-world deployment.
The HPE NonStop community, historically rooted in Tandem Computers’ culture of openness, has held an annual gathering since the early 1980s.
Originally known as the International Tandem Users Group (ITUG) summits, the main conference evolved into the NonStop Technical Boot Camp (TBC), now organized by Connect Worldwide and heavily supported by Hewlett Packard Enterprise.
The conference serves as the premier annual gathering for NonStop users, focusing on technical education, mission-critical applications, and networking.
Detailed Historical Timeline (1990–2026)
The “Tandem/ITUG” Era (1990–1996)
Focus: Transitioning from proprietary stack machines to MIPS RISC microprocessors, introducing Open System Services (OSS).
1990: Tandem reaches peak revenue; ITUG meetings focus on fault tolerance in ATM networks.
1993: Introduction of NonStop Himalaya K-series using MIPS R4400 processors.
1994: NonStop Kernel (NSK) extended with POSIX-compliant Unix.
1995: Introduction of ServerNet, foundational for future x86 architectures.
The Compaq & HP Transition Era (1997–2014)
Focus: Integration into larger portfolios, migration from MIPS to Intel Itanium (TNS/E).
1997: Compaq acquires Tandem. ITUG summits begin navigating the new corporate structure.
2003: HP acquires Compaq. NonStop conferences become key components of HP’s high-end mission-critical offerings.
2008: Connect Worldwide (independent user group) takes over, revitalizing the “Technical Boot Camp” name.
The HPE NonStop X & Virtualization Era (2015–2019)
Focus: Migration to x86-64 (NonStop X), Virtualization (vNonStop), and cloud integration.
2015: Formation of Hewlett Packard Enterprise (HPE). Focus shifts to modernized “NonStop X” systems.
2016: vNonStop demoed at TBC, allowing fault-tolerant systems in virtual machines.
2017: TBC highlights AI and cybersecurity, reflecting modern enterprise needs.
2019: Discussions around “NonStop-as-a-Service” (XaaS) and GreenLake integration.
The AI & 50th Anniversary Era (2020–2026)
Focus: Hybrid Cloud, Artificial Intelligence, 50th Anniversary of NonStop.
2020: TBC goes virtual, with high attendance from a global community.
2022: Continued focus on XaaS (everything as a service).
2023-2024: Emphasis on cyber resilience, SQL improvements, and integration with modern DevOps tools.
2025/2026:HPE NonStop 50th Anniversary. Conferences focus on AI-driven transformation, cybersecurity, and the new business track.
Conference Insights and Evolution
The “Beer Bust”: A tradition started in the early days of Tandem, now a staple social event at the TBC to foster community and open communication.
Format: The NonStop TBC typically features 4 days of technical sessions, user case studies, and partner exhibitions (e.g., XYPRO, NTI).
Regional Events: Alongside the main TBC, regional events (e.g., MexTUG) occur throughout the year.
Key Themes: Uninterrupted performance, database integrity, and migration to x86/cloud.
NonStop TBC 2026 is scheduled for Sept 14–18 in Orlando, FL.
The history of Tandem Computers (now HPE NonStop) conferences is a nearly 50-year chronicle of community-driven knowledge sharing, evolving from the Tandem User’s Group (TUG) in 1978 to the modern HPE NonStop Technology & Business Conference (TBC).
These events have served as the primary venue for sharing best practices on fault tolerance, high availability, and mission-critical application design, bridging the gap between Tandem’s founding in 1974 and HPE’s current virtualized NonStop systems.
1974: Jimmy Treybig founds Tandem Computers in Cupertino, CA, with a mission to create fault-tolerant systems for online transaction processing (OLTP).
1976: First Tandem/16 (T/16) system shipped to Citibank, initiating the NonStop era.
1978:Creation of the Tandem User’s Group (TUG) in San Jose, CA, as the foundational user community. Introduction of the Encompass database management system.
1980–1989: Growth and Expansion
1981: TUG is renamed the International Tandem User’s Group (ITUG), reflecting global growth. Introduction of NonStop II.
1983: Introduction of the Tandem NonStop Extended Processor (TXP) and Guardian B-Series OS.
1984: Formation of the British Isles Tandem User Group (BITUG).
1985–1986: Introduction of the entry-level NonStop EXT system.
1987-1988: Large-scale adoption of Tandem systems by international financial institutions and growing ITUG conference attendance, often characterized by strong community spirit.
1989: Release of NonStop Cyclone and relational database software, challenging IBM’s dominance in transaction processing.
1990–1999: The Move to Open Systems & Acquisition
1990: Announcement of the Integrity S2 line for Unix-based fault tolerance.
1991: Release of Cyclone/R (CLX/R) based on MIPS R3000, signaling a move away from custom proprietary CPUs.
1993: Launch of the Himalaya K-series, supporting the MIPS R4400 and native mode NSK.
1994-1995: Introduction of Open System Services (OSS), extending the NonStop Kernel to include a Unix-like POSIX environment.
1997:Compaq acquires Tandem for $3 billion. Tandem releases the NonStop Himalaya S-Series, introducing the ServerNet interconnect technology.
2000–2010: Compaq-HP Merger and Modernization
2001: Hewlett-Packard merges with Compaq, taking over the NonStop product line and initiating a migration to Intel Itanium processors (TNS/E).
2001: ITUG is renamed to “Compaq Users Group” before transitioning to the combined Connect community group.
2002: Formation of a Tandem Alumni Group, celebrating the unique culture.
Legacy + Future: Current TBC conferences balance supporting existing high-value transaction applications with modernization approaches like REST APIs, Java, and DevOps.
Virtualization & Cloud: A major focus is deploying NonStop as virtualized instances (vNS) and integrating with public/hybrid clouds.
Community Continuity: Despite multiple mergers (Tandem HPE), the user community has remained tight-knit, with organizations like Connect hosting the NonStop TBC.
Continuous Availability: The core focus remains 100% uptime, with sessions analyzing how to achieve it in modern containerized environments.
ViewSys is a legacy, interactive system monitoring utility for HPE NonStop servers that provides real-time visibility into system resource utilization. Similar to PEEK and Measure, it allows system operators to view resource consumption as it happens, allowing for immediate analysis of the impacts of process relocations or controller path changes.
HPE NonStop ViewSys Overview
Purpose: Monitors system resources, including processor utilization, I/O performance, and memory usage, on NonStop systems.
Key Features: Provides online viewing of system resources, allowing for quick recognition of performance bottlenecks, which helps in performance tuning.
Functionality: Unlike Measure, which is typically analyzed offline, ViewSys offers an interactive, live, and graphical view of system performance.
Operation Requirement: Runs from HPE block mode terminals or non-Stop terminal emulators, presenting average resource usage for each polling interval.
The history of ViewSys is deeply intertwined with the development of the HPE NonStop OS and its monitoring toolkit.
Era 1: Tandem Era (The Early Days)
1976: Initial Tandem NonStop System introduced; basic system monitoring is manual and console-based.
1980s (Mid-late): As Transaction Monitoring Facility (TMF) and Pathway are introduced, the need for interactive monitoring grows.
1990s:ViewSys becomes a key utility for operators managing massive OLTP (Online Transaction Processing) workloads.
Era 2: Compaq/Early HP Era (The Transition)
1997: Compaq Acquires Tandem.
2003: HP Acquires Compaq. The monitoring focus begins to merge with Integrity-based architecture.
2004: The ViewSys User’s Guide highlights ViewSys alongside PEEK and Measure, standardizing its use for interactive monitoring.
2005: Introduction of HP Integrity “NonStop i” (TNS/E) servers using Intel Itanium processors. ViewSys adapted to monitor Itanium systems.
Era 3: Modern HPE Era (The Modernization)
2014: First NonStop X (TNS/X) systems on x86-64 are introduced. ViewSys remains a available tool, but modernization efforts begin.
2015: Hewlett Packard Enterprise (HPE) is formed.
2016-2020: Shift towards Web ViewPoint Enterprise (by Idelji Corporation), which provides web-based dashboards for monitoring EMS events and system metrics.
2020: Sales of Itanium-based systems end. Modern monitoring focuses heavily on NonStop X systems and virtualized environments.
Present: While legacy ViewSys may exist in older environments, it is largely superseded by modern GUI-based, browser-independent monitoring solutions like Web ViewPoint and Remote Analyst.
HPE NonStop EMSDIST (Event Management Service Distributor) is a critical component within the HPE NonStop operating system responsible for distributing and managing event messages (logs) generated by the system, subsystems, or applications. It is part of the Event Management Service (EMS), which is essential for fault-tolerant monitoring.
EMS events (via EMSDIST) seen in the Reflex 80:20 application ( now Sentinel (Nonstop Monitoring) by ETI-NET)
EMSDist Overview
Purpose: EMSDIST reads events from an EMS collector process ($0, $ZLOG, etc.) or a collector logfile, filters them based on user criteria, and sends them to a user-specified destination (such as a terminal, printer, or another file).
Key Functionality: It enables both real-time monitoring and historical analysis of events.
Event Handling: It handles EMS messages, including those generated by the EMS subsystem itself (messages 513-999) and those from EMS distributors (messages > 1000).
Integration: Often used in conjunction with TACL (Tandem Advanced Command Language) for automated event management scripts.
Detailed Historic Timeline and Evolution
EMSDIST has evolved alongside Tandem / Compaq / HPE NonStop systems, transitioning from basic console management to complex distributed management systems.
1. The Tandem Guardian Era (Late 1970s – 1980s)
Context: The emergence of Tandem NonStop systems focused on continuous availability.
EMS Origins: Initial event handling was largely via console messages. As systems grew, the need to manage logs across multiple processors led to early Event Management Service components.
Role of EMSDist: Early distributors primarily moved messages from local collectors to a central console or tape log.
2. The D-Series & TMF Era (1990s)
Context: Introduction of sophisticated transaction monitoring and distributed databases.
1996: A significant EMS Reference Summary was released (PN 114754), formalizing the structure of EMS collectors and distributors.
Capabilities: EMSDIST became capable of filtering high-volume events, separating critical errors from warning messages (513-1019).
Evolution: Began integrating with the Distributed Systems Management (DSM) suite for better network-wide event visibility.
3. The Compaq & Integrity (J-Series/H-Series) Era (2000s – 2010s)
Context: Shift from MIPS-based processors to Intel Itanium (Integrity) servers.
2003-2005: Integration with Windows-based management systems (DSM/NOW) and improvements to the Multi Event Viewer (MEV).
2014: HP Integrity NonStop Operations Guides emphasized using EMSDIST alongside modern tools like OSM (Open System Management) Event Viewer, especially for H-Series and J-Series systems.
Key Capability: Improved handling of large logs, with better time-based querying (TIME and STOP options) for auditing and troubleshooting.
4. The HPE NonStop X & Modern Era (2015 – Present)
Context: Adoption of x86 architecture and cloud-ready systems (L-Series).
2015: HPE takes over the portfolio, accelerating integration with HPE InfoSight for AI-driven log analysis.
Modernization: While EMSDIST remains, modern environments heavily leverage NS Software Essentials and third-party tools for advanced analytics.
Continued Importance: EMSDIST remains essential for analyzing historical logs via the LOGFILE option, especially when dealing with cold-standby or restored logs from tape/disk.
Key Functional Milestones
Message Categorization: Formalization of messages 513-999 (collectors) and >1000 (distributors) for structured analysis.
Filtering Efficiency: Implementation of complex FILTER parameters allowed operators to filter events by process, user, or time.
Logfile Access: The ability for EMSDIST to process archived or older LOGFILE entries independently of the live $0 collector.
Template Support: Ability to use specific =_EMS_TEMPLATES for customizable output formatting.
HPE NonStop EMSDIST, Event Management Service Distributor Timeline by year
The HPE NonStop Data Definition Language (DDL) dictionary is a specialized subsystem used to define and manage data objects for Enscribe files and translate those definitions into source code for various programming languages. It serves as a central repository for metadata, ensuring consistent data structures across applications written in C, COBOL, TAL, or TACL.
Program Summary
The DDL dictionary program functions as a metadata management tool. Key capabilities include:
Centralised Definition: Defines records, fields, and file attributes in a hierarchical structure.
Code Generation: Translates DDL definitions into language-specific source code (e.g., COBOL copybooks or C headers).
Dictionary Maintenance: Allows users to create, examine, and update dictionaries to reflect changes in data structures.
Interoperability: Modern tools like Ddl2Bean convert dictionary files into Java Beans or XML, enabling cross-language and cross-platform use.
Future Outlook
The future of HPE NonStop DDL focuses on modernisation and integration rather than replacement.
Data Virtualization: Integration with AI factories and object storage platforms to expose legacy metadata in open-table formats like Apache Iceberg.
API Centricity: Enhancements to the NonStop API Gateway will likely use DDL metadata to automate REST/JSON service orchestration.
Real-time Analytics: Native streaming of NonStop data into platforms like Kafka, using DDL definitions to map real-time changes into analytics-ready formats.
HPE NonStop PATHCOM is the interactive management interface for the Pathway transaction processing environment. It allows administrators to configure, monitor, and control PATHMON-governed objects such as serverclasses, TCPs (Terminal Control Processes), and links.
Historical Timeline: The Evolution of Pathway & PATHCOM
The history of PATHCOM is inseparable from the Tandem NonStop platform, which pioneered fault-tolerant Online Transaction Processing (OLTP).
The Tandem Era (1974 – 1997)
1974 – 1976: Tandem Computers is founded. The first NonStop I system ships in 1976.
1983: Tandem introduces Pathway software alongside the Transaction Monitoring Facility (TMF). This milestone removes the requirement for developers to manually code fault tolerance into applications, as the Pathway infrastructure (managed via PATHCOM) handles it automatically.
Early 1990s: The platform migrates from proprietary stack machines to MIPS RISC processors (TNS/R architecture). PATHCOM evolves to manage more complex distributed environments.
1994: Open System Services (OSS) is introduced, allowing NonStop to support a Unix-like POSIX environment.
2005: Migration from MIPS to Intel Itanium (Integrity NonStop) begins.
2010s: Pathway evolves into HPE NonStop Pathway with TS/MP (Transaction Services/Massive Parallelism), enabling near-linear scalability for massive OLTP workloads.
The Modern HPE Era (2014 – Present)
2014: NonStop X is introduced, migrating the architecture to Intel x86-64 processors.
2015: Hewlett-Packard splits; the platform continues under Hewlett Packard Enterprise (HPE).
2020 – 2024: Focus shifts toward virtualisation and hybrid cloud. Modern Pathway/TS environments now support massive scaling up to 24,480 cores in a single system image.
Summary of PATHCOM Functionality
Future of NonStop Pathway
HPE’s roadmap for NonStop focuses on integrating mission-critical reliability with modern data centre technologies:
Modernisation: Support for Kubernetes Helm deployments and cloud-native frameworks.
Hardware Advancements: New NS9 X5 and NS5 X5 platforms offer double the memory capacity and 2x faster system interconnects.
Open Integration: Continued emphasis on open application development environments and open-source frameworks.
Hybrid Cloud: Positioning NonStop as a key component of HPE GreenLake for mission-critical workloads in the cloud.
The HPE NonStop Spoolcom (Spooler Command Language) program is the administrative interface for managing the Spooler subsystem on HPE NonStop systems. It allows operators to configure, monitor, and control print jobs, collectors, and print processes.
Program Summary
Purpose: Used to define and manage spooler objects such as collectors, devices, and jobs.
Key Functions: Starting/stopping the spooler, modifying device attributes, and controlling job states (e.g., hold, release, delete).
Architecture: Operates within the Guardian environment, communicating with the Spooler supervisor process to maintain 24/7 fault-tolerant printing operations.
Historical Timeline by Era
1. The Tandem Era (1974–1997)
1976: Introduction of the Tandem NonStop system; basic spooling capabilities were essential for early OLTP (Online Transaction Processing).
1980s: The Spooler evolved to handle complex routing and multiple collectors to support growing enterprise needs.
1997: Spooler D41 released, providing stable management for the MIPS-based architecture.
2. The Compaq & Early HP Era (1997–2014)
1999–2000: Release of Spooler D46, enhancing device ownership and virtual device support.
2001–2002: Spooler D48 released during the transition to the HP Integrity NonStop (Itanium) platform.
2012: Major updates to Spooler D48 to support H01 and H02 RVUs, improving scalability for high-end systems.
3. The Modern HPE Era (2014–Present)
2014: NonStop X (x86-64) introduced. Spoolcom adapted to support the new architecture and virtualised environments.
2018–2020: Focus shifted toward modernised interfaces. While Spoolcom remains the CLI standard, graphical alternatives like MultiBatch began gaining traction for batch management.
2023–2024: Continued integration with HPE GreenLake and hybrid cloud models, ensuring spooling services are available in private cloud deployments.
Futures and Roadmap
Modernisation: HPE is pushing toward “modernisation through tradition,” which includes better integration of legacy tools like Spoolcom with modern DevSecOps and cloud-native frameworks.
Kernel-Level Threading (KLT): Future updates aim to leverage KLT to improve the performance and scale-up capabilities of management processes.
Data-Centric Security: Integration with security platforms like TAMUNIO for field-level tokenization ensures that printed data remains compliant with PCI DSS 4.0 and GDPR.
Richard Buckle, founder of Pyalla Technologies, is a prominent thought leader in the HPE NonStop community known for his “Real Time View” column. His work provides a detailed chronological perspective on the platform’s evolution from its Tandem origins to modern cloud-native implementations.
The Tandem Era: Foundations (1974 – 1997)
This era established the core architecture of fault tolerance and “non-stop” processing.
1974: Tandem Computers is founded; the first “NonStop” system is commissioned.
1970s – 1980s: The platform gains dominance in financial services, telco, and healthcare.
1996: Managed service models begin for Tandem users, with firms like Tandem Computer Management (TCM) winning major contracts like Bank of Scotland.
The Compaq & Early HP Era: Transition (1997 – 2013)
A period of shifting corporate ownership and the end of the original Cupertino campus era.
1997: Compaq acquires Tandem Computers.
2002: HP acquires Compaq, bringing NonStop into the HP Enterprise fold.
2008: The official end of the Cupertino Tandem campus as NonStop teams move to other facilities.
The X86 & Virtualization Era: Modernization (2013 – 2023)
Buckle documented the massive shift from proprietary hardware to industry-standard Intel x86 architecture.
2013: Announcement at NonStop TBC that the platform will support Intel x86.
The HPE NonStop architecture is defined by its “shared-nothing” design, where every hardware and software component is redundant and operates independently to ensure 100% operational continuity. For over 40 years, it has evolved through four distinct hardware eras while maintaining upward software compatibility.
1. The Tandem Era (1974–1997): Proprietary Foundations
Architecture Approach: Founded by James Treybig, Tandem introduced the first commercial fault-tolerant system using a proprietary 16-bit stack-based architecture.
Key Technical Milestones:
1976 (NonStop I/T16): Introduced the Dynabus, a custom inter-processor backplane, and the Guardian OS, which used message-passing instead of shared memory to isolate faults.
1981–1983 (NonStop II & TXP): Introduced 32-bit addressing and the Transaction Monitoring Facility (TMF), which allowed applications to be fault-tolerant without specialized coding.
1986–1989 (VLX & Cyclone): Scaled to the mainframe market with ECL gate-array chips and the first fault-tolerant relational database, NonStop SQL.
2. The MIPS Era (1991–2004): Migration to RISC
Architecture Approach: To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while emulating the original instruction set for compatibility.
Key Technical Milestones:
1991 (Cyclone/R): The first MIPS-based system.
1997 (Himalaya S-Series): Replaced Dynabus with ServerNet, a high-speed system interconnect that later evolved into the industry-standard InfiniBand.
Ownership Shift: Compaq acquired Tandem in 1997, and HP merged with Compaq in 2002.
3. The Itanium Era (2005–2013): HP Integrity NonStop
Architecture Approach: Branded as Integrity NonStop (NonStop i), this era moved the platform to Intel Itanium processors.
Key Technical Milestones:
2005 (NS-series/J-series): Focused on “NonStop Advanced Architecture” (NSAA), leveraging standard HP server components to lower costs while maintaining Availability Level 4 (AL4).
Technical Commentary: While powerful, the reliance on Itanium’s EPIC architecture eventually limited growth as the industry consolidated around x86-64.
4. The Modern HPE Era (2014–Present): x86-64 & Virtualization
Architecture Approach: Shifted to standard Intel x86-64 processors (NonStop X), fully decoupling the software stack from proprietary hardware.
Key Technical Milestones:
2014 (NonStop X/TNS/X): Introduced the L-series operating system. The architecture transitioned to a standard InfiniBand fabric for inter-processor communication.
2017–2020 (vNS): Launched Virtualized NonStop (vNS), allowing the environment to run on standard hypervisors like VMware, bringing fault tolerance to private and hybrid clouds.
2025 (NS9 X5): Modern systems now support up to 8 TB of RAM and are integrated into the HPE GreenLake consumption-based cloud model.
HPE NonStop (formerly Tandem) has evolved through distinct architectural eras, each introducing specific programming languages and environments to maintain its legendary fault tolerance.
1. The Tandem Stack Machine Era (1974–1990)
This era focused on the proprietary 16-bit stack-based architecture (TNS), where software was designed to “fail-fast” and operate in process pairs.
Nov 1974: Tandem Computers founded by Jimmy Treybig.
May 1976:TAL (Transaction Application Language) launched with the first Tandem/16 (NonStop I) system. It was the only language available at launch, derived from HP 3000’s SPL.
Late 1970s:COBOL74, FORTRAN, and MUMPS were added to support business and scientific applications.
1981:NonStop II introduced support for 32-bit addressing, enabling larger application memory.
1983:SCOBOL (Screen COBOL) emerged alongside the Pathway transaction manager to handle terminal-based user interfaces and fault-tolerant logic.
1986:NonStop SQL released as the first fault-tolerant relational database language.
1987:C was introduced to the platform.
1989:Integrity S2 line launched using MIPS processors, introducing a variant of Unix called NonStop UX.
2. The MIPS RISC / Himalaya Era (1991–2004)
As Tandem migrated to MIPS processors (TNS/R), it introduced a Unix-like personality to attract modern developers while maintaining its legacy Guardian environment.
1991:Cyclone/R launched. Most software still ran in TNS stack mode using an “Accelerator” tool to translate code to MIPS instructions.
1993:Himalaya K-Series released with native-mode compilers for C and COBOL to leverage MIPS performance.
1994/1995:Open System Services (OSS) introduced a POSIX-compliant environment, enabling C++ and standard Unix utilities.
1995:Java was first supported on the platform.
1997: Compaq acquired Tandem; ServerNet became the standard interconnect.
Late 1990s: Support for scripting languages like Perl, Python, and PHP began appearing in the OSS environment.
3. The HP Integrity Itanium Era (2005–2013)
Following the HP merger, the architecture moved to Intel Itanium (TNS/E), branded as HP Integrity NonStop.
2005:NonStop i introduced. Compilers for C, C++, and Java were updated for the Itanium architecture.
2000s:pTAL (Portable TAL) became the standard for system-level programming to bridge legacy TAL code to modern RISC/Itanium architectures.
2011: Enhanced support for modern web languages and frameworks within the OSS environment.
4. The Modern x86 / NonStop X Era (2014–Present)
HPE migrated the entire stack to standard Intel x86-64 processors (TNS/X) while retaining binary compatibility for legacy applications.
2014:NonStop X launched. All languages (COBOL, C, C++, Java) were migrated to target x86-64.
2015: Transition to Hewlett Packard Enterprise (HPE) branding.
Recent Years: Integration of modern open-source dev-ops tools and languages, including JavaScript (Node.js), Python 3, Go, and Samba via the HPE NonStop OSS environment.
HPE NonStop (formerly Tandem) programming has evolved from proprietary languages designed for fault-tolerant, transaction-oriented processing (TAL, COBOL85) to supporting open-source languages (Java, C++, Python, PHP) on modern x86-64 hardware. The ecosystem spans from the initial Guardian OS to modern J-series and L-series OS, supporting TNS, TNS/R, TNS/E, and TNS/X architectures.
Key Programming Languages & OS Timeline
1970s–1980s (Tandem Guardian): Core development centered on TAL (Transaction Application Language) (system programming), COBOL85 (business logic), and TACL (Tandem Advanced Command Language) (command shell scripting).
1990s (Guardian 90 / NonStop UX): Introduction of C and C++ for more flexible application development, alongside Pascal and FORTRAN.
2000s (H-Series / J-Series – Itanium): Shift towards Java and enhanced support for C/C++ in the Pathway server environment.
2010s–Present (J-Series / L-Series – x86-64): Modern NonStop systems, particularly on x86-64, expanded to include scripting languages like Perl, PHP, and Python within the Open System Services (OSS) environment.
pTAL (Portable TAL): Introduced to bridge native TAL to newer, more portable processor architectures.
Operating System & Architecture Evolution
Guardian (TNS): The foundational OS, relying on Tandem’s native stack, with TAL as the primary low-level language.
OSS (Open System Services): Introduced to bring POSIX-compliant, Unix-like functionality to NonStop, enabling easier porting of C/C++ and open-source applications.
Modern OS (J-series/L-series): Supports both Guardian (native) and OSS environments, allowing for a hybrid approach where traditional transaction processing (COBOL/TAL) mixes with modern web services (Java/Python).
The evolution of C++ on HPE NonStop systems traces the platform’s transition from proprietary Tandem architectures to modern x86-64 standards.
HPE NonStop C++ Evolution Timeline
Early 1990s: Introduction of Native C/C++ (TNS/R) With the move to MIPS-based TNS/R architecture, Tandem introduced native C and C++ compilers. These supported the Guardian and the then-new Open System Services (OSS) personalities.
2005: Itanium Transition (TNS/E) As the platform migrated to Intel Itanium processors (J-Series), the C++ compiler was updated to support the TNS/E (Tandem Native Stack / EPOC) architecture. This era introduced more robust Standard C++ Library support, though it required specific header management (e.g., CPATHEQ pragmas).
2015: x86 Migration (TNS/X) The launch of NonStop X (L-Series) on Intel x86-64 marked a major shift. The compiler suite was re-engineered to leverage the x86-64 Instruction Set Architecture, providing significantly higher performance for C++ applications.
2017: 64-Bit Addressing Support HPE introduced comprehensive 64-bit support for OSS processes (LP64 data model). This allowed C++ applications to access massive memory heaps beyond the previous 32-bit (ILP32) limits.
2020–2022: Modern C++ Standards (C++11/14/17) HPE updated its toolchains to support modern language standards. The NonStop Development Environment for Eclipse (NSDEE) 13.x versions specifically introduced a dedicated UI for setting the C++17 Language Standard.
2024: Kernel-Level Threading (KLT) The release of the L25.09 RVU brought Kernel-Level Threading to native C++ applications. This allowed C++ threads to execute concurrently across different IPUs, moving beyond the older POSIX User Threads (PUT) model.
2025: Cloud-Native Development HPE now offers the HPE NonStop Development Environment (NSDevEnv) in the public cloud, allowing developers to build fault-tolerant C++ applications using a cross-compiler model without on-premise hardware.
HPE NonStop Pathway (now often part of NonStop TS/MP) has a legacy spanning nearly five decades, evolving from a terminal management system into a sophisticated middleware for high-scale, fault-tolerant Online Transaction Processing (OLTP).
Comprehensive Evolution Timeline
1976: Genesis (Tandem Computers) The HP NonStop platform was originally introduced by Tandem Computers Inc. as the first fault-tolerant commercial computer. Pathway was soon developed to manage the distribution of transaction requests across multiple server processes.
1980s: The Classic Pathway Era Pathway became the standard for “Screen COBOL” applications. It introduced the PATHMON process to monitor and manage serverclasses, ensuring that if one process failed, another would immediately take its place.
1997: Compaq Acquisition Compaq acquired Tandem, integrating the NonStop technology into its enterprise portfolio. During this time, Pathway began adapting to newer networking protocols and client-server architectures.
2002: Hewlett-Packard (HP) Acquisition HP merged with Compaq, and the platform was rebranded as HP NonStop. Pathway evolved into NonStop TS/MP (Transaction Services/Massive Parallelism), allowing for even greater scalability across massive clusters of processors.
2014–2015: The x86 Revolution HP announced the NonStop X architecture, moving the platform from Itanium processors to standard Intel x86 hardware. Pathway (TS/MP) was optimized to run on this new architecture, providing the same high availability with modern hardware performance.
2015–Present: HPE and Modern Middleware Following the split of HP, Hewlett Packard Enterprise (HPE) continued developing Pathway. Modern versions (like NonStop TS/MP 2.8) support advanced features like:
Dynamic Server Processes: Automatically scaling server instances based on load.
Heterogeneous Interoperability: Allowing TUXEDO or Java clients to access Pathway servers.
Virtualization: Deployment via HPE NonStop Virtual Enterprise (vNS).
Core Components Over Time
PATHMON: The “manager” process that monitors all objects in the environment.
PATHCOM: The command-line interface used to configure and start Pathway objects.
Tandem Advanced Command Language (TACL) is the interpreted, high-level command and programming language for HPE NonStop (formerly Tandem) systems. Its timeline follows the evolution of Tandem hardware and the Guardian operating system.
Comprehensive TACL Timeline
1974–1976: Foundation of Tandem
Tandem Computers Inc. was founded. The initial operating system, Guardian, was designed for fault-tolerant computing.
Late 1970s: Initial Release
TACL was introduced in the 1970s as the primary command interface, replacing or augmenting earlier, more primitive command interpreters. It was written in TAL (Tandem Application Language).
1980s: Mature Programming Capabilities
TACL evolved from a simple shell into a powerful programming language. Key features like Macros, Routines, and Variables (TEXT, ALIAS, STRUCT) were solidified during this era to automate complex system tasks.
1994: D-Series (D30.00) Release
A significant update was documented in the TACL Programming Guide for D30.00, which detailed advanced features like Nowait I/O, Pathway Server integration, and SPI/EMS programmatic interfaces.
1997–2000s: Corporate Transitions (Compaq & HP)
1997: Compaq acquired Tandem.
2002: HP merged with Compaq, and TACL development continued under the HP NonStop banner.
2000: Updated reference manuals detailed TACL’s environment customization and the use of the _EXECUTE variable for program flow.
2010s: H-Series and HPE Era
2013: Comprehensive Reference Manuals were released, refining built-in functions for the H-Series architecture.
2015: Hewlett Packard Enterprise (HPE) was formed. TACL is now maintained as part of the HPE NonStop software stack.
Current: Legacy & Automation
TACL remains the essential tool for administrative tasks and system-level automation on modern HPE NonStop X (x86) platforms.
TAL (Tandem Application Language) is the original system programming language for the HPE NonStop (formerly Tandem) platform. Developed by Tandem Computers in the mid-1970s, it was designed to provide high-level efficiency while allowing low-level machine access, similar to C but with a syntax influenced by ALGOL.
Detailed Development Timeline
Mid-1970s: The Genesis
Tandem Computers, founded by James Treybig, introduces the first NonStop I system in 1976.
TAL is released as the primary language for writing the Guardian Operating System and system-level utilities.
The Tandem Advanced Command Language (TACL) is initially developed during this decade using TAL.
1980s: Growth and Maturity
1981–1983: Introduction of the NonStop II and TXP systems. TAL becomes the standard for developing mission-critical transaction applications like banking and point-of-sale systems.
1985: The TAL Reference Manual is updated (March 1985), formalising advanced features like DEFINEs, LITERALs, and complex pointer arithmetic.
1990s: Transition to RISC
Tandem introduces TNS/R (RISC) systems based on MIPS processors.
pTAL (Portable TAL) is introduced to allow TAL code to run “natively” on RISC hardware, offering better performance than the emulated TNS environment.
2000s–Present: Modernisation and Maintenance
2003–2005: HP (which acquired Compaq, who had bought Tandem) migrates NonStop to Intel Itanium (TNS/E) and later x86 architectures (TNS/X).
2006: The Common Run-Time Environment (CRE) is enhanced to support mixed-language programs (C, COBOL, pTAL) seamlessly.
Current Status: TAL is considered a legacy language, with most new development occurring in C/C++ or Java. However, it remains vital for maintaining the core Guardian OS and legacy banking kernels.
Typical Program Development Workflow
According to the TAL Programmer’s Guide, a developer follows this “timeline” to create a program:
Source Code Creation: Writing statements, removing comments, and defining PROCs and SUBPROCs.
Compilation: Running the TAL Compiler to generate an object file.
Binding: Using the Binder Program to link the object file with the TALLIB Run-Time Library.
Acceleration: Running the Accelerator (for TNS code) to optimise it for native hardware execution.
HPE NonStop (originally Tandem) has a nearly 50-year history as the gold standard for fault-tolerant, “always-on” computing. Originally developed by Tandem Computers to eliminate single points of failure, the platform has survived through several major corporate acquisitions while evolving its underlying processor architecture.
Founding and The Tandem Era (1974–1997)
The “NonStop” architecture was born from the idea that a single hardware failure should never crash a system.
1974:Tandem Computers is founded by Jimmy Treybig and three former HP engineers.
1976: The first Tandem/16 (later NonStop I) is shipped to Citibank. It featured a “shared-nothing” architecture where each CPU had its own memory and copy of the Guardian OS.
1981:NonStop II is released, introducing 32-bit addressing to support larger applications.
1983: The NonStop TXP and Pathway software are introduced. Pathway revolutionized the platform by allowing programmers to write fault-tolerant apps without manually coding “checkpoints”.
1986:NonStop SQL is launched, the first fault-tolerant relational database.
1989:NonStop Cyclone arrives, a high-end mainframe-class system.
1991–1993: Transition to MIPS RISC processors begins with the Cyclone/R and the Himalaya K-series.
Corporate Acquisitions and Transition (1997–2014)
The platform changed hands twice in five years, but the mission-critical nature of the technology kept it alive.
The timeline of HPE NonStop ViewPoint (and its modern successor, Web ViewPoint) reflects the evolution of NonStop systems from Tandem’s fault-tolerant beginnings to Hewlett Packard Enterprise’s modern cloud-integrated management.
Detailed History Timeline
Pre-2000: Legacy ViewPoint
Originally developed for the Tandem NonStop platform to provide a graphical operations interface for monitoring system status and events.
Featured early support for DSM/PM (Distributed Systems Management/Performance Monitor) and event management through primary and alternate event logs.
2003–2005: Transition to Web ViewPoint
September 2003: Version 4 AAD released as an early iteration of the web-based management tool.
May–October 2004: Progressive upgrades (Versions 5.0 and 5 AAF) introduced refined management capabilities for S-Series servers.
March 2005: Version 5 AAG released, consolidating features for the S-Series.
November 2005:Web ViewPoint for Itanium (Version H01AAI) launched, marking the shift to the Intel Itanium-based Integrity NonStop architecture.
2013–2015: The x86 Revolution & Virtualization
2014: Support for Intel x86 architecture was officially announced, leading to the launch of NonStop X.
Evolution to Web ViewPoint Enterprise (WVP E): The platform evolved into an automated management product, eventually adding integration with cloud-based analytics like HPE Remote Analyst.
2018–Present: Modern Hybrid Cloud Era
L-Series Support: Continued updates provided support for L-Series operating environments and enhanced security monitoring.
2023–2024: Recent developments focus on Web ViewPoint Enterprise, featuring a global configuration platform and enhanced historical data capture through integrations like Sentinel for HPE NonStop.
For more specific documentation, you can browse the HPE NonStop Manuals on the HPE Support Center.
HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers designed for 24/7, zero-downtime operations. Originally created by Tandem Computers in 1974, the architecture is now owned by Hewlett Packard Enterprise (HPE) and supports mission-critical workloads like banking and finance.
Key Aspects of HPE NonStop (Tandem):
Continuous Availability: Designed to eliminate single points of failure with 100% fault tolerance.
Architecture: Initially used a proprietary Tandem T/16 design; modern systems are based on HPE Integrity/x86 architectures.
Operating System: Traditionally runs the Guardian OS, which handles the system’s specialized, continuous processing capabilities.
Evolution: Founded by James Treybig in 1974, Tandem was acquired by Compaq in 1997, which then merged with HP in 2002.
Applications: Ideal for transactional applications requiring strict data integrity and real-time processing.
Modern Platforms: Current systems include HPE NonStop Compute NS9 X5 and NS5 X5.
The systems are still widely used today for mission-critical applications that cannot afford to be offline.
HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers.
PROject Templates 