Category: TACL

HPE NonStop Tandem Programming Languages and Development Timeline

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 MultiBatch is an advanced workload automation & scheduling manager

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.

The Software Partnership was a highly specialized software house in Runcorn

The Software Partnership (TSP) was a highly specialized British software house based in Runcorn, Cheshire, that played a key role in early cutting-edge electronic banking software. The firm famously developed sp/ARCHITECT-BANK, an innovative enterprise banking system built explicitly for Tandem Computers (now HPE NonStop) fault-tolerant server systems. I was based there between 1990 and 1995.

The Software Partnership Logo, Runcorn Software House, Deluxe Data
The Software Partnership Logo

Below is a detailed overview of the company’s operational history, alongside the corresponding hardware/software architectural eras of the HPE NonStop platform it relied upon.

Detailed Overview

  • Core Focus: The Software Partnership specialized in online transaction processing (OLTP) and electronic automated banking software. Long before the internet became mainstream, TSP engineered early desktop access environments for corporate bookkeeping and inter-account bank transfers.
  • Key Product: Its flagship software suite, sp/ARCHITECT, ran on Tandem’s highly unique, redundant architecture. The software handled complex high-volume retail transactions, ATM networking, and ledger balances.
  • Major Clients: High-profile financial institutions deployed TSP’s systems, including TSB (Trustee Savings Bank), Bank of Scotland, Rabobank, and Denmark’s Girofon.
  • Legacy: TSP initiated a massive lineage of financial tech operations in the Runcorn/Warrington area. After subsequent buyouts and transitions, its corporate DNA integrated into modern banking giants, eventually operating under Fidelity National Information Services (FIS).

Detailed Timeline by Era and Year

The history of TSP mirrors the evolution of the underlying fault-tolerant architecture originally built by Tandem, later managed by Compaq, HP, and currently Hewlett Packard Enterprise (HPE).

Era 1: The Tandem Founding & TSP Inception (Mid-1970s – 1989)

This era is marked by Tandem’s creation of the fault-tolerant server market, which birthed the niche that TSP filled.

  • 1974–1976: Tandem Computers is founded and ships its first 16-bit NonStop I (T/16) system, utilizing complete component redundancy to guarantee close to zero downtime for the financial industry.
  • 1981: Tandem introduces the NonStop II, transitioning to battery-backed DRAM memory and enabling early 32-bit addressing.
  • Mid-1980s: The Software Partnership (TSP) is co-founded by Nigel Walsh. It establishes offices first in Timperley (Wingate Drive), then moves to Crowngate (Norton House) in Runcorn. The team begins developing online banking architectures explicitly for Tandem OS (Guardian) and early UNIX nodes.
  • 1989: Tandem launches the NonStop Cyclone, a high-end mainframe system featuring superscalar CPUs and fiber-optic interconnects.

Era 2: The MIPS RISC Transition & Corporate Buyouts (1990 – 1999)

TSP reaches peak software deployment exactly as Tandem shifts its internal processor technology.

  • 1990: TSP establishes itself as a major regional employment hub for software engineers following a massive boom in terminal banking technology. Software programmers deploy sp/ARCHITECT-BANK code for massive retail banks internationally.
  • 1991: Tandem shifts its structural hardware away from proprietary chips, introducing its first MIPS RISC-based NonStop systems.
  • 1992: TSP expands its Runcorn footprint, moving to custom facilities at Wingate House on Northway, Runcorn.
  • 1994: TSP is acquired by American firm Deluxe Electronic Payment Systems (a division of Deluxe Corporation, one of the largest check printers and transaction processors in the US). The corporate name transitions to Deluxe Data.
  • 1997: Due to shifts in the enterprise hardware landscape, Compaq Computer Corporation acquires Tandem Computers for $3 billion, taking over the NonStop lineage.

Era 3: The Itanium Migration & eFunds Realignment (2000 – 2013)

The architecture sheds its proprietary processors for industry standards, and TSP’s corporate legacy transforms.

  • 2000: Deluxe Data’s electronic payment wing splits off and rebrands as EFD eFunds.
  • 2001–2002: HP (Hewlett-Packard) merges with Compaq, absorbing the NonStop portfolio. Simultaneously, HP begins shifting NonStop servers from MIPS architectures to Intel Itanium processors.
  • 2007: Following industry consolidation, the corporate remnants of the original TSP Runcorn operations are absorbed into Fidelity National Information Services (FIS) and relocated to Aegon House in Daresbury, Warrington.

Era 4: The Modern HPE NonStop X & Virtualization Era (2014 – Present)

The legacy of the high-availability software pioneered in Runcorn culminates in cloud and x86 integration.

  • 2014: HP introduces NonStop X, completely migrating the underlying architecture to Intel x86-64 processors and implementing InfiniBand connectivity fabrics.
  • 2015: Hewlett-Packard officially splits into two entities; the core mission-critical banking platform continues its five-decade lineage under Hewlett Packard Enterprise (HPE).
  • 2020s–Present: HPE modernizes the software architecture to support Virtualized NonStop Software (vNS). Modern variants allow banking systems to run mission-critical apps seamlessly inside enterprise private clouds and scalable HPE GreenLake consumption models with 100% fault tolerance.
Deluxe Data International Operations, Wingate House, Northway, Runcorn, Cheshire
Deluxe Data International Operations, Wingate House, Northway, Runcorn, Cheshire
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire
The Software Partnership, Norton House, Crowngate, Runcorn, Cheshire

⚙️ sp/ARCHITECT

sp/ARCHITECT (specifically sp/ARCHITECT-BANK) was a foundational electronic banking and transaction framework engineered in the 1990s by The Software Partnership (a UK-based fintech house later acquired by Deluxe Data). It primarily powered corporate banking portals and telephone-driven banking services.

The platform acted as highly reliable middleware, serving as a bridge between the customer and back-end banking mainframes. The breakdown of its architecture, infrastructure, and core functions includes:

⚙️ Architectural Breakdown

  • Hardware & OS: Built to run natively on fault-tolerant Tandem NonStop computers (now HPE NonStop). This “shared-nothing” architecture was designed for absolute transactional uptime and zero data loss.
  • Programming Languages: Built using legacy enterprise standards. Code was primarily written in COBOL85 and TAL (Transaction Application Language) native to the Tandem ecosystem.
  • Middleware Integration: Utilized Tandem-specific middleware like Pathway and Remote Server Call (RSC) to handle client-to-host communications.

💻 Core Capabilities & Modules

  • Electronic Delivery Framework: Served as a multi-channel framework, accommodating a wide variety of early access devices like desktop clients, UNIX workstations, and smart phones.
  • Transaction Handlers: Deployed custom scripts/handlers that enabled end-users to securely access real-time account data and perform early inter-account transfers without visiting a physical branch.
  • Testing Utilities: Included proprietary simulation tools like sp/TESTBED, acting as a PC-to-host test harness so developers could emulate user queries and transaction flows.

🏦 Industry Footprint

  • European Rollout: Heavily adopted by large European financial institutions, including TSB, Rabobank, Bank of Scotland, and Girofon.
  • BBM II Integration: Powered landmark corporate desktop banking solutions like Barclays Business Master II (BBM II), long before modern web browser banking existed.
  • Evolution: Following its acquisition, its design philosophies eventually evolved into Deluxe Data’s broader CONNEX suite of payment solutions.

HPE NonStop architecture (Tandem Computers) by Era and Year

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:

1. The Tandem Founding Era (1976–1981)

  • Years: 1976–1981
  • Processors: Proprietary 16-bit stack processors (e.g., Tandem/16, NonStop II)
  • 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.

2. The Cyclone & Early RISC Era (1981–1996)

  • Years: 1981–1996
  • Processors: Proprietary non-RISC (NonStop Cyclone) & MIPS R-series RISC
  • 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.
Globally published HP NonStop journal – ‘The Connection’
HPE NonStop article by Mark Whitfield in 2013, working for Insider Technologies Limited in Salford Quays

HPE NonStop System Monitoring Reflex Product

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;

C-Deep (Transaction Monitoring)

C-Deep (Transaction Monitoring)

The Insider Reflex product at ETI-NET is now called Sentinel for NonStop Monitoring;

Sentinel (Nonstop Monitoring)

Sentinel (Nonstop Monitoring)

C-Deep for Transaction Monitoring & Sentinel for HPE NonStop Monitoring

BASE24 and BASE24-eps architecture overview

The BASE24 electronic payment system developed by ACI Worldwide exists in two primary architectural generations:

BASE24 Classic (historically deployed on HPE NonStop / Tandem fault-tolerant hardware) and

BASE24-eps (Enterprise Payments System, built using an object-oriented C++ framework deployable across open systems, z/OS, and cloud infrastructure).

Despite structural differences, both share a highly optimized, component-based transaction routing engine.

BASE24 and BASE24-eps architecture overview
BASE24 architecture overview

Core Structural Component Layers

The component architecture maps the complete end-to-end lifecycle of a financial message (such as ISO 8583) through five distinct functional sub-systems:

1. Network & Message Routing Component (XPNET)

  • Purpose: Coordinates all message traffic across internal processes and physical network nodes.
  • Function: Operates as a specialized middleware network manager that decouples low-level communication links from upper transaction routing layers.
  • Configuration: Relies on a Logical Network Configuration File (LCONF) to define active execution nodes, hardware lines, and physical stations.

2. Perimeter Access Layer (Device Handlers)

  • Purpose: Translates device-specific message protocol formats into the system’s unified internal format.
  • ATM Device Handlers (ATMDH): Manage direct connectivity to automated teller machines, unpack specific vendor dialects (such as Diebold or NCR states), and track terminal hardware statuses.
  • POS Device Handlers (POSDH): Interface with point-of-sale acquirer terminals and merchants.
  • Security Operations: Triggers immediate payload encryption/decryption and Hardware Security Module (HSM) PIN-block translation directly within this ingestion ring.

3. Core Transaction Logic (Authorization System)

  • Purpose: Determines whether a payment request should be accepted, rejected, or modified.
  • Full On-Us Authorization: Inspects internal databases for matching account records, positive balances, and velocity thresholds to issue real-time decisions.
  • Parametric/Negative Checks: Validates card status against offline negative files, usage restrictions, or custom risk parameters.
  • Scripting Engine: Modern BASE24-eps variants execute localized transaction routing scripts via customized operators without forcing a compile rewrite of the core engine core.

4. Boundary Channels (Interchange & Host Interfaces)

  • Interchange Interfaces (ICH): Package and transform the transaction payload into international network profiles (e.g., Visa, Mastercard, regional switches). It handles strict message mapping and regional network check requirements.
  • Host Interfaces (HIF): Create synchronous links back to an institution’s underlying Core Banking system to apply ledger adjustments, check balances, or execute real-time holds.

5. Offline & Administrative Subsystems

  • Extract Component: Gathers active transaction logs and streams filtered payloads out to analytical reporting databases.
  • Refresh Component: Updates terminal operational data, key packages, and card exclusion lists from parent systems down to active execution nodes.
  • Settlement Initiator: Groups, cleanses, and batches net-clearing totals to finalize payment entries into regional clearinghouses.

Architectural Divergence: Classic vs. EPS

The structural design varies significantly depending on the generation of the software deployment:

BASE24 and BASE24-eps architecture overview
BASE24 and BASE24-eps architecture overview

End-to-End Component Transaction Flow

  1. An ATM transaction arrives at the network interface layer managed by XPNET.
  2. The message is routed to the Device Handler, which strips hardware packaging and requests translation from the HSM.
  3. The clean internal message passes to the Authorization Engine.
  4. If it is a “Not-On-Us” card, the engine identifies the destination BIN and transfers routing control to the Interchange Interface.
  5. The Interchange Interface maps the payload to the external scheme standard (such as Visa) and transmits it to the external network.
  6. The outbound network response is unwrapped by the Interchange component and tracked through the core engine to log final response codes.
  7. The transaction safely records inside the active log file, allowing the Extract / Settlement components to pick it up later during batch processing.

BASE24 and BASE24-eps architecture overview

BASE24 and BASE24-eps architecture overview
BASE24 and BASE24-eps architecture overview

HPE NonStop MultiBatch Batch Job Scheduling Overview and Timeline

Overview

MultiBatch is a robust enterprise workload automation and job scheduling tool designed specifically for the HPE NonStop parallel architecture. Developed originally by Insider Technologies and subsequently managed/distributed alongside partners like ETI-NET, it enables organization-wide task automation.

MultiBatch provides high-performance, concurrent execution of batch schedules across multiple nodes. It natively supports both Guardian and OSS environments. By utilizing modern graphical user interfaces (GUIs) alongside traditional Pathway components, it eliminates the need for complex, manual, and high-maintenance TACL or JCL scripts.

Core Technical Capabilities

  • Parallel Execution: Uses NonStop architecture to execute batch workloads concurrently across one or multiple nodes.
  • Advanced Scheduling: Drives automated tasks based on time parameters, complex intervals, custom calendars, and direct cross-job dependencies.
  • Reusable Infrastructure: Environment classes—including PARAM, ASSIGN, DEFINE, FD, and environmental variables—can be configured once and safely shared across various jobs.
  • Inbuilt Disaster Recovery: Features automated, built-in monitor recovery mechanisms to preserve execution integrity during hardware or connection failures.
  • Seamless Migration: Simplifies moving production workloads between environments via a deep migration utility that automatically handles environmental translation without manual intervention.

Timeline Breakdown by Year and Version

The evolution of MultiBatch highlights its transition toward broader configuration capacities, simplified environment integrations, and eventual product lifecycle milestones.

2020: Operational and Security Consolidation

  • Version Focus: Pre-v10 Infrastructure (Enterprise Deployments)
  • Key Enhancements:
    • Formalized rigid separation of internal user roles, establishing MBAT.OPS for view-only status monitoring and MBAT.CONFIG for structural schedule maintenance.
    • Refined the “Migrator” module, eliminating manual TACL operations when extracting and inserting batch definitions across network test and production nodes.
    • Added capabilities allowing all MultiBatch jobs to execute securely under the system Batch Monitor Process (BMON) owner or explicitly assigned application user IDs.

2022 (November): MultiBatch Version 10.0 Launch

  • Version Focus: Architecture Restructuring
  • Key Enhancements:
    • Define Classes: Introduced reusable Define Classes to group environments cleanly.
    • Scale Upgrades: Upgraded the main Batch Monitor (BMON) subsystem to actively scale up to 2,500 jobs concurrently.
    • Parameterization: Modified the core configuration boundaries and decoupled utility processes (MBPARHK) to seamlessly process non-step related records across database structures.
    • Clean Up: Formally deprecated legacy components including UTCSV to reduce technical debt.

2023 (February): MultiBatch Version 10.1 Refinement

  • Version Focus: OSS Overhaul & Operational Control
  • Key Enhancements:
    • OSS Reworking: Re-engineered and optimized support for Open System Services (OSS) processes, granting them equal parity with traditional Guardian tasks.
    • On-Demand Execution: Enabled ad-hoc “On Demand Job” invocation directly through user channels without altering master schedules.
    • Conditional Variables: Extended character limits for Conditional Parameter values up to 100 characters.
    • Subsystem Unification: Consolidated Event Timer processing and Conditional Parameters fully into standard MultiBatch menus, auditing frameworks, and security tracking.
    • Control Commands: Integrated the SWITCH BMON command line directive to easily pass control between operational monitors.
    • Interface Upgrade: Rolled out an entirely new Ops GUI Server to modernize scheduling visibility.

Current Era: Version 10.2 Maintenance & Commercial Sunset

  • Version Focus: Version 10.2 / Product Lifecycle Transition
  • Key Milestones:
    • MultiBatch 10.2: Operates as the current, stable production tier delivered via ETI-NET, featuring deep parameterization and centralized network deployment protocols.
    • Commercial End of Life: As of March 1, 2026, new software licenses for Multi-Batch are no longer available for purchase. The software has officially reached the end of its commercial sales life.
    • Ongoing Support: Existing license holders retain full permission to execute, maintain, and run the product inside their environments according to their long-term licensing agreements.

HPE NonStop MultiBatch Batch Job Scheduling Overview and Timeline

HPE Nonstop Technology Architecture – specialized, 100% fault-tolerant infrastructure

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.

If you plan to work directly with these systems, you can explore formal pathways like the Concepts and Facilities for HPE NonStop Systems course provided by HPE Education Services.

Core Architectural Layers (Diagram Blueprint)

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.
  • Key Modules: Covers Processor Nodes, configuring SCLIMs/NCLIMs, and hands-on fault-scenario testing.

3. Low-Level OS Internals

  • Course Code: U8609S (HPE Integrity Nonstop Operating System Architecture).
  • Focus: Deep dive into runtime architecture, process control, and memory allocation.
  • Key Modules: Focuses on Inter-process Message Systems, synchronization mechanisms, and system debugging.

Training Delivery Options

Enrolling via HPE Education Services grants access to various professional development features:

  • HPE vLabs: Direct sandbox access to practice configuration and live fault injection inside virtual environments.
  • Digital Learner Credits: Flexible licensing options to assign corporate learning units across teams.
  • Modernized Tracks: Courses have been fully overhauled to support contemporary cloud paradigms and hybrid integration via HPE GreenLake frameworks.

My HPE NonStop (Tandem Computers) Certificates :

Insider Tech : 1995 – 2013
HPE NonStop (Tandem) Career Experience at Insider Technologies Limited, ITL
BASE24 eps monitoring

Tandem Computers ( HPE NonStop ) Overview & Detailed Timeline

Tandem Computers, founded in 1974 by James (Jimmy) Treybig, revolutionized the computing industry by pioneering fault-tolerant computer systems. Designed specifically for online transaction processing (OLTP) in banking, stock exchanges, and telephone switching, Tandem’s “NonStop” systems provided near-zero downtime by utilizing redundant, modular processors and a “shared-nothing” architecture. 

Tandem remained an independent, rapidly growing company until it was acquired by Compaq in 1997, later becoming part of Hewlett Packard Enterprise (HPE). 

Overview of Key Technologies

  • NonStop Architecture: The core design featured multiple independent processors, each with its own memory and I/O bus, interconnected by a redundant inter-CPU bus called the Dynabus.
  • Guardian OS: A message-based operating system designed to detect faults immediately (“fail-fast”) and mirror process states to a backup processor, allowing seamless failover.
  • NonStop SQL (1986): The first fault-tolerant SQL database, known for linear scalability.
  • ServerNet (1995): A high-speed, scalable, point-to-point network system that replaced the Dynabus and influenced modern InfiniBand standards. 

Detailed Historic Timeline by Era and Year

The Founding Era (1974–1979) 

  • 1974: Tandem Computers is founded in Cupertino, California, by Jimmy Treybig, formerly of HP. Initial venture capital investment comes from Kleiner & Perkins.
  • 1975: Design of the Tandem/16 (T/16) is completed.
  • 1976: The first T/16 NonStop system is shipped to Citibank.
  • 1977: Tandem goes public; sales begin rapid, exponential growth.
  • 1978: Introduction of the ENCOMPASS database management system.

The Growth and Competition Era (1980–1989)

  • 1980: Inc. magazine ranks Tandem as the fastest-growing public company in America.
  • 1981: NonStop II is introduced, supporting 32-bit addressing to allow for larger applications.
  • 1982: Competition intensifies as Stratus Technologies enters the fault-tolerant market. Tandem faces its first quarter of declining growth.
  • 1983: Introduction of the NonStop TXP, the first entirely new implementation of the TNS architecture with cache memory.
  • 1985: Attempted entry into the PC market with the MS-DOS-based Dynamite PC, which fails commercially and is withdrawn.
  • 1986: Introduction of the NonStop VLX (32-bit datapath) and the revolutionary NonStop SQL database.
  • 1987: Introduction of the low-cost NonStop CLX for small office environments.
  • 1988: Tandem acquires Ungermann-Bass, Inc. to strengthen networking capabilities.
  • 1989: Introduction of the NonStop Cyclone, a high-end ECL-based processor aimed at mainframe markets. 

The Open Standards & MIPS Transition Era (1990–1996)

  • 1990: Tandem introduces the Integrity line of fault-tolerant Unix systems.
  • 1991: Cyclone/R (CLX/R) is released, marking the start of the migration from proprietary stack machines to MIPS R3000 RISC microprocessors.
  • 1993: Introduction of the NonStop Himalaya K-series using faster MIPS R4400 processors.
  • 1994: NonStop Kernel (NSK) is extended with Open System Services (OSS), a POSIX-compliant Unix environment.
  • 1995: Introduction of ServerNet, designed for extremely low-latency inter-processor communication.
  • 1995–1997: Partnered with Microsoft on the “Wolfpack” project, which becomes Microsoft Cluster Server. 

Acquisition and Integration Era (1997–Present)

  • 1997: Compaq acquires Tandem Computers for roughly $3 billion. The Himalaya S-Series is introduced.
  • 1998: Compaq acquires DEC, leading to a shift in engineering strategy towards Alpha/Itanium instead of MIPS.
  • 2001: Compaq terminates Alpha engineering, committing to Intel’s Itanium (Merced) processors.
  • 2002: Hewlett-Packard acquires Compaq. Tandem becomes the core of the HP Integrity NonStop Server division.
  • 2005: The first HP Integrity NonStop servers (TNS/E) based on Itanium processors are released.
  • 2014: Completion of the migration to Intel x86 architecture (NonStop X). 

Note: Following the split of HP into Hewlett Packard Enterprise (HPE) and HP Inc., the NonStop product line continues to be developed and supported by HPE.

Tandem Computers Overview and Detailed Timeline

HPE NonStop EMSDIST, Event Management Service EMS Distributor Timeline by Era

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

sp/ARCHITECT electroinic banking by The Software Partnership TSP

sp/ARCHITECT was a pioneering electronic banking and funds-transfer software suite originally developed by the Runcorn-based firm The Software Partnership (TSP). Following its acquisition by the American firm Deluxe Electronic Payment Systems in 1994, the Runcorn office became the European hub for what was then rebranded as Deluxe Data. 

sp/ARCHITECT electroinic banking by The Software Partnership TSP

Overview

The Runcorn operation specialised in high-availability, mission-critical banking software, specifically the sp/ARCHITECT-BANK product. This software was designed to run on Tandem Computers (now HPE NonStop), which were known for their fault-tolerant architecture. The “sp/ARCHITECT” platform was highly valued for its client-server design, allowing it to be adapted for various hardware brands, including Unix-based systems. 

Historical Timeline

  • Mid-1980s: The Software Partnership (TSP) is co-founded by Nigel Walsh. The company starts developing online banking systems in Timperley before moving to Runcorn.
  • 1990: The firm establishes itself at Norton House in Crowngate, Runcorn, focusing on electronic banking software for major clients like TSB and Bank of Scotland.
  • 1992: The Runcorn office relocates to Wingate House on Northway.
  • 1994: Deluxe Electronic Payment Systems (a subsidiary of Deluxe Corporation) acquires The Software Partnership for an undisclosed sum. The acquisition is aimed at helping Deluxe expand its global presence and accelerate the use of the sp/ARCHITECT suite.
  • 1994–1995: The Runcorn office operates as Deluxe Data, providing software design, coding, and 24-hour support for international clients including Rabobank.
  • 2000: Following a series of corporate shifts, the company name changes to EFD eFunds.
  • 2007: By this year, the operation has transitioned to Fidelity National Information Services (FIS) and is based in Aegon House, Daresbury, Warrington. 

sp/ARCHITECT electroinic banking by The Software Partnership TSP

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline

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. 

Internet Links & Manuals

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline

TAL & PTAL Programming Language on Tandem HPE NonStop

Tandem TAL (Transaction Application Language) is a block-structured, procedural language designed in the mid-1970s for Tandem’s NonStop fault-tolerant operating systems, optimized for systems programming, high-reliability OLTP, and direct hardware interaction. It is heavily influenced by ALGOL and HP 3000 systems, allowing high-performance, message-based applications, and remains supported on modern HP Enterprise NonStop x86-64 platforms. 

Tandem TAL Programming certificate back in 1995, Mark Whitfield

Overview of TAL Programming

  • Purpose: Developed to run on Tandem’s GUARDIAN operating system to build highly available, fault-tolerant transactional systems.
  • Characteristics: Procedural, block-structured, efficient (closer to assembly than C), and designed for speed and direct memory access, according to a NonStop Insider article.
  • Features: Strong support for data manipulation, process management, and message-based IPC (Inter-Process Communication) necessary for node-to-node replication, as described on the Wikipedia page on Tandem Computers.
  • Relation to TACL: While TAL is for creating compiled applications, TACL (Tandem Advanced Command Language) is the interpreter/macro language used for command procedures and system interaction, as explained in a Scribd document. 

Historical Timeline of TAL

  • 1975–1976 (Founding Era): TAL is created for the first Tandem/16 system shipped in 1976, heavily utilizing expertise from HP 3000 systems programming, according to a personal blog post.
  • Early 1980s (Expansion): TAL becomes the standard for ATM networks and banking systems, requiring high-reliability code, as seen in this blogger.com article.
  • 1985 (Evolution): TAL is used to build complex OLTP environments, distinguishing it from nascent PC markets as noted in archived Tandem press clippings.
  • 1990s (Native TAL): Introduction of “Native” TAL (T/TAL) to handle new architecture requirements and move from 16-bit to 32-bit environments, according to a TAL Programmer’s Guide document.
  • 1997 (Compaq Merger): Tandem is acquired by Compaq; TAL continues as the core systems language.
  • 2001 (HP Merger): Tandem (via Compaq) is acquired by HP, bringing TAL to the HP Integrity (Itanium) platform.
  • 2010s–Present (Modernization): TAL applications are ported to HP Enterprise NonStop x86-64, with support for running TAL programs on Intel processors and in virtualized instances, according to a NonStop Insider article. 

Present Day

  • TAL remains essential for maintaining legacy systems, but new applications often utilize C/C++ or Java on the modern NonStop platform, as noted in the Wikipedia page on Transaction Application Language.
  • TAL applications are still relevant due to the “single system image” and fault-tolerance features that define the current NonStop environment, according to the NonStop Insider article. 

PTAL Overview and Timeline

Tandem PTAL (Portable Transaction Application Language) is a block-structured, procedural systems programming language used on HPE NonStop (formerly Tandem) servers. It is the portable successor to the original TAL (Transaction Application Language), designed to allow high-level systems programming without an assembler while maintaining near-machine efficiency. 

Overview: TAL, PTAL, and epTAL

The language evolved to support different processor architectures over Tandem’s 50-year history: 

  • TAL (Original): Designed for the 16-bit CISC stack machine architecture (TNS). It has the syntax of ALGOL/Pascal but the low-level semantics of C.
  • PTAL (Portable): Introduced during the migration to MIPS RISC processors (TNS/R). It removed machine-specific constructs to allow code to be compiled into native RISC instructions.
  • epTAL (Extended): Developed for the migration to Intel Itanium processors (TNS/E). 

Historical Timeline by Year

Year Milestone

1974, Tandem Computers founded by James Treybig; initial design of the Tandem/16 hardware begins.

1976, TAL released. The Tandem/16 (NonStop I) ships with TAL as its only programming language.

1981, NonStop II introduced, adding 32-bit addressing support to TAL via an “extended data segment”.

1983, NonStop TXP launched; first major reimplementation of the instruction set architecture supported by TAL.

1986, NonStop VLX introduced with 32-bit data paths; NonStop SQL released, often managed via TAL-based systems.

1989, NonStop Cyclone released, the high-end mainframe competitor for the TAL environment.

1991, PTAL Development starts with the release of Cyclone/R, the first MIPS-based machine. TAL code is initially translated via an “Accelerator” tool before native PTAL compilers take over.

1993, Himalaya K-series released; native mode operating system (NSK) and native compilers (PTAL) become standard.

1997, Compaq acquires Tandem. Migration begins from MIPS to Alpha (later abandoned).

2002, HP merges with Compaq. Development focuses on the Itanium (TNS/E) architecture.

2005, epTAL introduced for the new Integrity NonStop i servers based on Intel Itanium microprocessors.

2014, x86 Migration. NonStop X (TNS/X) systems are released, transitioning the TAL/PTAL environment to Intel x86-64 processors.

RTLX by Insider Technologies, Overview and Timeline by Year

Insider Technologies RTLX (now C-Deep (Transaction Monitoring) https://etinet.com/products/c-deep-transaction-monitoring/ ) is a real-time monitoring and tracking solution designed to provide end-to-end visibility for high-volume electronic payments and transactional processes. It specifically ensures that every stage of a payment—from the initial card “tap” at a point-of-sale (POS) terminal to the final movement of funds from an account—is monitored to maintain operational continuity. 

RTLX Overview

  • Function: Real-time transaction and payment monitoring.
  • Platforms: Runs on HP NonStop, Windows, Linux, and Unix.
  • Core Value: Simplifies “Big Data” for IT operations by alerting teams to potential failures before they impact consumers (e.g., preventing ATM or online banking outages).
  • Key Use Case: Used by major financial institutions like the Bank of England and Royal Bank of Scotland for settlement and transaction security. 

RTLX Historical Timeline

The development of RTLX is closely tied to Insider Technologies’ growth as a specialist in mission-critical HP NonStop environments. 

EBUG Conference, Mark Whitfield – Product Manager

The Foundational Era (1989–2000)

  • 1989: Insider Technologies Limited is founded in Manchester, UK, by IT industry veterans.
  • 1990s: The company establishes its “DNA” in the HP NonStop (Tandem) platform, developing core products like MultiBatch and Reflex.
  • 1995: Insider begins a period of rapid growth, providing technical support for critical UK financial infrastructure, including Euroclear (formerly CRESTCo), which settles 88% of UK equities. 

The Expansion Era (2001–2014)

  • 2002: Launch of the state-of-the-art Systems Training Platform, featuring 4x patented cloning technology for hyper-realistic simulations.
  • 2004–2013: Development of the Reflex suite (Reflex 80:20 and Reflex ONE24) and the introduction of Sentra and RTLX Reactor monitoring products.
  • 2014: Insider expands its product initiatives to include diagnostic and trending solutions for real-time electronic payments, solidifying the role of RTLX in global banking. 

The Acquisition & Integration Era (2015–Present)

  • 2015: ETI-NET acquires Insider Technologies on 1 July, integrating its monitoring expertise with ETI-NET’s mainframe storage and backup solutions.
  • 2019: Insider celebrates its 30th year of operations, highlighting RTLX’s role in monitoring modern POS and “tap” payment systems.
  • 2023–Present: Insider becomes part of the PartnerOne group, a global family of mission-critical software companies, further scaling its threat detection and real-time monitoring capabilities. 

RTLX by Insider Technologies, Overview and Timeline by Year

HP NonStop MultiBatch Overview and Historical Timeline

HP NonStop MultiBatch is a “mainframe-class” workload automation and batch scheduling manager developed by Insider Technologies (distributed by ETI-NET). It is designed specifically for the HPE NonStop (formerly Tandem) platform to automate, manage, and secure complex batch processing across both Guardian and OSS environments. 

Product Overview

While the native NonStop scheduler is NetBatch, MultiBatch is positioned as a modern, high-performance alternative that provides deeper integration with the NonStop architecture. 

  • Workload Automation: Manages thousands of concurrent jobs with sophisticated calendaring and dependency tracking.
  • Architecture: Built to leverage NonStop’s fault tolerance and linear scalability, allowing batch schedules to execute across multiple networked nodes.
  • Interfaces: Modernized from command-line tools to a suite of role-based Graphical User Interfaces (GUIs) for operations and management.
  • Security: Includes a secure, audited environment with full support for NonStop-specific security attributes like High-PIN and CPU selection. 

Historical Timeline by Era

The evolution of MultiBatch is closely tied to the history of the Tandem/NonStop platform, which spans over 50 years of ownership changes and architectural shifts. 

1. The Tandem Era (1974 – 1997)

  • 1974: Tandem Computers founded by James Treybig to build the first fault-tolerant commercial systems.
  • Late 1980s – Early 1990s: MultiBatch originated during this period (reportedly in the early 1990s) to address the needs of large financial institutions requiring complex batch schedules beyond the capabilities of the original NetBatch.
  • 1991: Release of the Cyclone/R and the start of the migration from proprietary stack machines to MIPS RISC processors. 

2. The Compaq & Early HP Era (1997 – 2014)

  • 1997: Compaq acquires Tandem.
  • 2002: Hewlett-Packard (HP) merges with Compaq. The NonStop platform begins its migration from MIPS to Intel Itanium (branded as Integrity NonStop).
  • Mid-2000s: MultiBatch matures as a mission-critical tool for global banks and stock exchanges. Development focuses on MultiBatch 7 and 8, enhancing GUI capabilities and adding support for Open System Services (OSS). 

3. The Modern HPE Era (2014 – Present)

  • 2014: NonStop X is introduced, moving the architecture from Itanium to Intel x86-64.
  • 2015: Hewlett-Packard splits into HP Inc. and Hewlett Packard Enterprise (HPE).
  • 2018 – 2020: MultiBatch 9.5 is released with an enhanced GUI. It increasingly becomes the primary alternative as HPE shifts focus away from active sales of the legacy NetBatch product.
  • 2023 – 2024: Release of MultiBatch 10, introducing “Define Classes,” support for up to 2,500 jobs, and improved OSS process handling. This era focuses on “modernisation through tradition,” aligning with HPE’s push for virtualized NonStop and hybrid cloud deployments. 

BASE24 by ACI Worldwide timeline by era and year

BASE24 is the world’s most widely used payment processing platform, developed by ACI Worldwide. Originally designed for ATM networks, it evolved into a comprehensive system for acquiring, authenticating, and routing card-based and digital transactions across various channels. It is known for its high-performance, fault-tolerant architecture, processing nearly 50% of the world’s electronic transactions at its peak. 

Comprehensive Timeline by Era

Era 1: Foundations & The Rise of BASE24 Classic (1975–1990s)

This era focused on high-availability software for the emerging automated banking industry, specifically for Tandem NonStop servers. 

  • 1975: ACI founded in Omaha, Nebraska, to develop software for the new “NonStop” server computers used by banks and stock exchanges.
  • 1981: Secured its first international client, an Australian bank, marking the start of global expansion.
  • 1982: Launch of BASE24, the first global product designed for 24-hour system operations, originally focused on ATM networks.
  • 1986: Rapid growth led to 131 customers across 14 different countries. 

Era 2: Expansion & Public Transition (1995–2000s) 

The platform expanded into Point of Sale (POS) and branch systems while the company underwent major structural changes. 

  • 1995: The company went public on NASDAQ as Transaction Systems Architects (TSA).
  • 1997: Officially adopted the name ACI Worldwide.
  • Early 2000s: Introduction of BASE24-es (later renamed BASE24-eps), a next-generation platform using C++ and object-based architecture to replace the legacy monolithic design. 

Era 3: Modernisation & The “eps” Shift (2005–2015)

ACI shifted focus toward BASE24-eps, a more flexible, open-architecture version designed for multi-channel transaction processing. 

  • 2005: ACI launches BASE24-eps, featuring a modular engine capable of processing approximately 2,000 transactions per second (TPS) with extremely low latency.
  • 2007: TSA officially rebranded all operations under the ACI Worldwide, Inc. (ACIW) name.
  • 2008: Announced that BASE24 Classic would begin maturing in 2011, urging customers to migrate to the eps platform for better integration with modern systems like IBM System z.
  • 2011–2012: Release of BASE24-eps 11.1, adding support for DB2 on IBM System p, enhanced EMV acquiring, and tools for easier migration from legacy BASE24. 

Era 4: Cloud & Universal Payments (2015–Present)

The platform moved toward cloud-native capabilities and broader ecosystem integration. 

  • 2015: ACI celebrated its 40th anniversary, continuing to power electronic payments for over 6,000 organisations worldwide.
  • 2018: Introduction of UP BASE24-eps on Linux in the Cloud, demonstrating significantly reduced Total Cost of Ownership (TCO) through public and private cloud deployment.
  • Present: BASE24 remains a core pillar of ACI’s portfolio, supporting traditional card, ATM, mobile commerce, and internet banking transactions.

BASE24-eps by ACI Worldwide timeline by era and year

BASE24-eps is a modular, high-availability payment processing engine developed by ACI Worldwide. It evolved from the original “BASE24 Classic” to provide a more flexible, open-system architecture for acquiring, authenticating, routing, and authorizing electronic transactions. 

Base24-eps Overview

  • Architecture: Unlike the TAL-based Classic version, BASE24-eps uses an object-oriented design written primarily in C++ and Java.
  • Key Features:

Detailed Timeline

The Foundation Era (1970s – 1990s)

  • 1975: ACI is founded in Omaha, Nebraska, initially developing software for NonStop server computers.
  • Late 1970s: Development of the original BASE24 (now known as “Classic”), focused on high-uptime ATM processing.
  • 1981: First international customer (an Australian bank) signs on, starting the global expansion of BASE24. 

Transition & Development Era (2000 – 2005)

  • Early 2000s: ACI begins developing the “next generation” platform, initially called BASE24-es (extended systems), which later becomes BASE24-eps (enterprise payment system).
  • 2003 – 2004: The product begins migrating to open architectures, moving away from platform-specific languages. 

Mainstream Adoption Era (2006 – 2013)

  • 2007: ACI highlights BASE24-eps as its strategic future platform in investor overviews.
  • 2008: ACI announces the maturation of BASE24 Classic (ending standard maintenance in 2011), urging customers to migrate to BASE24-eps.
  • 2009: IBM Redbooks releases technical guides for BASE24-eps 08.2 on z/OS, solidifying its place in enterprise banking.
  • 2013: Release of BASE24-eps 2.0, introducing the “customer component” and enhanced service-enabling wrappers. 

Modernization & Cloud Era (2014 – Present)

HP NonStop Tandem Training provided by HPE Education Services

HP NonStop (originally Tandem) training focuses on the platform’s unique fault-tolerant architecture, designed to ensure 24×7 availability and data integrity for mission-critical industries like finance and telecommunications. Current training is provided by HPE Education Services, which offers expert-led courses ranging from basic concepts to advanced system management and database administration. 

Training Overview

HPE’s curriculum is structured to support IT teams at all levels—from beginners to experienced operators—and can be customised for specific business needs. Key training areas include: 

  • System Operations: Managing NonStop environments, including S-Series or newer x86-based systems.
  • Architecture & Concepts: Understanding fault tolerance, “fail fast” mechanisms, and message-based operating systems.
  • Database Management: Specialized courses for NonStop SQL/MX, SQL/MP, and Enscribe.
  • Application Development: Training in languages like C/C++, COBOL, and TAL (Transaction Application Language).
  • Modern Environments: Transitioning to virtualised instances and hybrid cloud infrastructures. 

Detailed course information, including outlines and lab access, is available through the HPE NonStop Compute training portfolio. 

Detailed Textual Timeline: Era & Year

The NonStop platform has undergone three major architectural shifts since its founding.

1. The Tandem Era (1974–1997)

  • 1974: Tandem Computers Inc. is founded by James (Jimmy) Treybig.
  • 1975: Design of the Tandem/16 (later NonStop I) is completed.
  • 1976: The first system is shipped to Citibank, marking the birth of commercial fault-tolerant computing.
  • 1981: NonStop II is introduced, adding 32-bit addressing support.
  • 1983: NonStop TXP launches as the first new implementation of the instruction set, featuring cache memory.
  • 1983: Transaction Monitoring Facility (TMF) and Pathway are introduced, removing the need for applications to be manually coded for fault tolerance.
  • 1986: NonStop VLX is released with 32-bit datapaths and NonStop SQL, the first fault-tolerant SQL database.
  • 1987: NonStop CLX is introduced for the low-end/distributed market.
  • 1989: NonStop Cyclone debuts for high-end mainframe-level performance.
  • 1991: Migration to MIPS architecture begins with the Cyclone/R.
  • 1993: NonStop Himalaya K-series is released, using native MIPS R4400 processors.
  • 1994: Open System Services (OSS) adds a POSIX-compliant environment to the NonStop Kernel.
  • 1997: NonStop Himalaya S-Series introduces ServerNet, replacing older bus architectures. WikipediaWikipedia +7

2. The Compaq Era (1997–2002)

  • 1997: Compaq acquires Tandem Computers.
  • 1999: Zero Latency Enterprise (ZLE) solutions are introduced for real-time information access.
  • 2001: Compaq announces the migration of the entire NonStop line to Intel Itanium processors. 

3. The HP / HPE Era (2002–Present)

  • 2002: HP merges with Compaq, bringing the NonStop division under HP.
  • 2005: HP Integrity NonStop (“NonStop i” or TNS/E) is launched, completing the migration to Itanium.
  • 2014: NonStop X (TNS/X) is introduced, transitioning the platform to Intel x86-64 architecture.
  • 2015: Hewlett-Packard splits; NonStop becomes part of Hewlett Packard Enterprise (HPE).
  • 2020: Sales of Itanium-based systems officially end.
  • 2023–2024: NonStop evolves to support virtualised instances and deployment on hybrid infrastructures. 

HP NonStop Tandem Training provided by HPE Education Services

Website Author IT Career Timeline Breakdown

Mark Whitfield is a highly experienced IT professional with a career spanning over 30 years, transitioning from a technical programmer to a senior digital engagement and project manager. His expertise is rooted in HPE NonStop (Tandem) systems and has evolved to encompass complex Agile and Cloud delivery across diverse industries. 

Early Technical Era (1990–1995)

Following his graduation in Computing in 1990, Whitfield began his career as a Programmer at The Software Partnership (later Deluxe Data). 

  • Focus: Electronic banking software, specifically sp/ARCHITECT-BANK on Tandem Mainframe Computers.
  • Key Work: Developed code for major banks including TSB, Barclays, and Rabobank. This included early digital innovations like voice-driven phone banking and inter-account transfers before the internet was widespread. 

Growth and Product Management Era (1995–2004) 

Whitfield joined Insider Technologies Limited (ITL) in 1995 as a Senior Programmer. 

  • Focus: Platform health and diagnostic software for HPE NonStop systems.
  • Key Projects:
    • Co-developed diagnostic plug-ins for the Reflex monitoring suite.
    • Managed the first HP OpenView Operations (OVO) Smart Plug-In certification for the NonStop platform in 2002.
    • Consulted for CRESTCo (Euroclear) in 1997, conducting benchmark testing on new S7000 nodes. 

Strategic Leadership and Project Management Era (2005–2014) 

During this decade, he transitioned into IT Project Management, focusing on high-value financial transaction tracking. 

  • Focus: Waterfall and Agile project delivery for payment systems and banking infrastructure.
  • Key Milestones:
    • 2011: Led a massive transaction tracking project at Al Rajhi Bank (Saudi Arabia), parsing terabytes of tape-archived data into a normalised SQL database.
    • 2013–2014: At Wincor Nixdorf, managed a £5+ million project for Lloyds Banking Group to migrate ATM driving responsibilities from legacy systems to AIX-based Oracle technologies. 

Senior Digital Engagement Era (2014–Present)

Since 2014, Whitfield has focused on senior-level digital transformation and engagement management. 

  • Betfred (2014–2016): Served as Senior Digital Project Manager for online and mobile platforms (iOS/Android), managing fraud detection and payment gateway integrations.
  • Capgemini (2016–Present): Joined as an Engagement Manager (SC cleared).
    • Focus: Managing large-scale Agile and Waterfall digital projects across aerospace, defence, and government sectors.
    • Notable Projects: Leading a £13.5m programme to migrate 130 UK government applications to the cloud (AWS/Azure) and delivering real-time airspace monitoring apps for air traffic organisations. 
Mark Whitfield IT Career Timeline Breakdown