Category: NSK

Mark Whitfield, Senior IT Project Manager

Mark Whitfield is a highly experienced IT Senior Project Manager and Engagement Manager based in Manchester, UK, specializing in Agile Scrum, PRINCE2, and Waterfall methodologies. He holds a degree in Computing (1990) and has extensive experience in IT hardware solutions, financial services, and Aerospace & Defence. 

Here is a comprehensive summary of his profile, with links based on the provided search data:

Professional Profile

  • Name: Mark Whitfield
  • Role: IT Senior Project Manager / Engagement Manager (SC Cleared)
  • Key Skills: Agile Scrum, PRINCE2, ITIL, Financial Forecasting, Stakeholder Management, Technical Initiative Leadership.
  • Education: Computing (Graduated 1990). 

Comprehensive Career History

  • Capgemini UK (Jan 2016 – Present): SC Cleared Engagement Manager (A8) in Custom Bespoke Solutions.
    • Recent Experience: Project Manager for a UK-wide Air Traffic organisation, delivering new Apple iOS Apps for military and public use.
  • Betfred Limited (Dec 2014 – Jan 2016): IT Senior Digital Project Manager, Online and Mobile Division.
  • Wincor Nixdorf Limited (Sep 2013 – Dec 2014): Project Manager, Professional Services – Banking Division.
    • Key Project: Managed a £5+ million project replacing legacy HP NonStop software systems with AIX-based J2EE/Oracle technologies for a major UK bank.
  • Reflex / Insider Technologies (Aug 1995 – Sep 2013): Project Manager – Strategic Technical Initiatives.
  • eFunds (1994 – 1995): Lead Analyst. 

Certifications & Training

  • Cloud & Project Management: AZ-900 Microsoft Certified Azure Fundamentals (2022), Advanced Engagement Management (2017), Registered PRINCE2 Practitioner (2011).
  • Agile: Agile SCRUM Training (2011).
  • Technical: TANDEM Performance Analysis (1995), C++ for Non-C Programmers (1997), Querying MS SQL 2000 (2009). 

Awards

  • C&CA UK’s Communications & Engagement Award Winner – Cloud & Custom Applications (Capgemini UK, Dec 2022).
  • Project Recognition Award – Wincor Nixdorf (Retail Banking Project). 

Web Presence & Documents

Mark Whitfield, Senior IT Project Manager

By era;

Mark Whitfield is a highly experienced IT Project Manager, Senior Developer, and SC-cleared consultant with over 30 years of experience, specializing in HP NonStop (Tandem) systems, banking software, and digital transformation projects. He is currently an Engagement Project Manager at Capgemini. 

Career Overview

  • Specialism: HP NonStop (Tandem) mainframes, BASE24, transaction monitoring, Agile/Waterfall methodologies.
  • Key Industries: Financial services, electronic banking, government, automotive, aerospace.
  • Core Competencies: Software development (C, C++, COBOL, TAL), Project Management (PRINCE2 Practitioner, Scrum), Pre-sales technical consultancy. 

Career Timeline by Era and Year

1. The Foundation & Tandem Era (1990–1995)

  • 1990: Graduated in Computing and started as a Programmer for The Software Partnership in Runcorn, specializing in sp/ARCHITECT-BANK on Tandem Computers.
  • 1990-1994: Developed banking code for TSB, Bank of Scotland, Rabobank, and Girofon (Denmark).
  • 1992: Worked on the Barclays Business Master II (BBM II) project in Knutsford.
  • 1994: Company taken over by Deluxe Data (later FIS). 

2. Insider Technologies & Monitoring Era (1995–2013)

  • 1995–2013: Joined Insider Technologies Ltd as a Senior Development Engineer and Project Manager.
  • 1995-2004: Developed monitoring/diagnostic software (Reflex 80:20, Reflex ONE24) for HP NonStop payment systems.
  • 1997: Worked on projects for CRESTCo.
  • Early 2000s: Focused on HP NonStop transaction/payment monitoring for ATM/POS devices using ACI’s XPNET.
  • 2005-2013: Managed first HP OpenView Operations Smart Plug-In certification for NonStop; designed XPERT24.
  • 2011: Certified as a PRINCE2 Practitioner. 

3. Banking Transformation & Consultancy Era (2013–2016)

  • 2013–2014: Wincor Nixdorf UK – Worked as a Project Manager in Professional Services for the Banking Division.
  • 2013-2014: Assigned to Lloyds Banking Group (LBG) for the Self-Service Software Replacement (SSSR) program (ATM estate upgrade).
  • 2014–2016: Joined Betfred as an IT Project Manager in the gambling/casinos industry, delivering mobile/online payment gateways (iOS, Android). 

4. Digital Transformation & Capgemini Era (2016–Present) 

  • 2016: Joined Capgemini UK as a client-facing Engagement Manager.
  • 2016-2017: Led digital projects for automotive, local government, and aerospace sectors.
  • 2017: Obtained Microsoft Excel Expert skills and Advanced Engagement Management certifications.
  • 2018–2019: Augmented into MuleSoft as a Delivery Manager for the Anypoint Platform.
  • 2022: Completed Microsoft Azure Fundamentals (AZ-900) certification.
  • 2023–2024: Assigned to a UK Government account for a cloud migration of 130+ applications and the Fish Export Service (FES) project. 

Key Qualifications

  • PRINCE2 Practitioner & Agile Scrum
  • ITIL Certified
  • SC Cleared (UK Government)
  • Technical Skills: C, C++, MS SQL, COBOL, TAL, Java, ASP.NET, HP NonStop

HPE NonStop architecture overview and technical commentary and approach by era and year

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. 
  • Summary of Architectural Evolution

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.

Mark Whitfield, Website Author – Background and Career Timline

Mark Whitfield is a Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC). He is currently a SC-cleared Engagement Manager at Capgemini UK. 

Professional Background by Era

  • 1990–1995: Early Programming (The Software Partnership/Deluxe Data)
    • Role: Programmer/Lead Analyst.
    • Focus: Developed electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers (now HPE NonStop).
  • 1995–2013: Senior Development & Product Management (Insider Technologies)
    • Role: Progressed from Senior Programmer to Project Manager for Strategic Technical Initiatives.
    • Focus: Developed platform health and diagnostic modules for the “Reflex” monitoring product.
  • 2013–2014: Project Management (Wincor Nixdorf)
    • Role: Project Manager, Professional Services – Banking Division.
    • Focus: Managed the Wincor Nixdorf workstream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
  • 2014–2016: Digital Project Management (Betfred)
    • Role: Senior Digital Project Manager, Online and Mobile Division.
    • Focus: Delivered payment gateways, sportsbooks, and virtual gaming components for iOS, Android, and Windows.
  • 2016–Present: Senior Engagement Management (Capgemini)
    • Role: Engagement Manager (A8), Custom Bespoke Solutions.
    • Focus: Leading digital transformation and cloud migration projects for public and private sector clients. 

Technologies & Frameworks

  • Project Methodologies: Agile SCRUM, PRINCE2 (Practitioner), Waterfall, ITIL, and ISO QA.
  • Mainframe & Infrastructure: HPE NonStop (Tandem), IBM ESB, UNIX shell scripting, and Cloud (MS Azure/AWS).
  • Programming & Databases: C/C++, MS SQL, Java, COBOL85, TAL, TACL, and SCOBOL.
  • Tools: MS Project, MS Excel/Office, MuleSoft Anypoint Platform, and Jira. 

Major Projects & Customers

  • UK Government: Managed a £13.5m cloud migration of 130 applications and the £1m+ Fish Export Service (FES) to CHIP portal.
  • Royal Mail Group (RMG): Managed a £4.3m data centre migration project involving over 1,100 interfaces.
  • Lloyds Banking Group (LBG): Led a £5m+ self-service software replacement project.
  • Other Notable Clients: Jaguar Land Rover (JLR), Heathrow, NATS (Air Traffic Control), Barclays, HSBC, Deutsche Bank, and Euroclear. 

Awards & Education

  • Awards:
    • C&CA UK’s Communications & Engagement Award (2022) at Capgemini UK.
    • Project Recognition Award from Wincor Nixdorf for achievements on the LBG SSSR project.
  • Education:
    • HND in Computer Studies (Distinction) from the University of Greater Manchester (formerly BIHE), 1988–1990.
    • A-Levels in Computer Science and Biology from Leigh College. 

Project Management Templates

Whitfield provides a library of over 200 editable resources through his site, PROject Templates, designed for Agile, Waterfall, and PRINCE2 7th Edition delivery. Key items include: 

  • Plan on a Page (POaP): Over 35+ executive-level summary slides.
  • Detailed Project Plans: Templates in MS Project (MPP) and Excel for SDLC tracking.
  • RAID Logs: Comprehensive registers for risks, actions, issues, and dependencies. 

Mark Whitfield Background and Career Timline

RTLX by Insider Technologies, Overview and Timeline by Year

Insider Technologies RTLX 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

HP NonStop Tandem Overview and Timeline History by year

HP NonStop is a series of fault-tolerant server computers designed for online transaction processing (OLTP) and mission-critical applications that require 100% uptime. Originally introduced by Tandem Computers Inc. in 1976, the platform uses a proprietary, integrated hardware and software stack known as NonStop OS (formerly Guardian) to eliminate single points of failure through massive redundancy and “fail-fast” logic. 

Historical Timeline by Era

1. The Tandem Founding Era (1974–1981) 

  • 1974: Tandem Computers Inc. is founded by James (Jimmy) Treybig and a team from Hewlett-Packard’s HP 3000 division.
  • 1976: The first system, the Tandem/16 (later NonStop I), is shipped to Citibank.
  • 1977: Tandem systems gain early traction as intelligent front-end processors for bank ATM networks. 

2. The Stack Machine Expansion (1981–1990) 

  • 1981: NonStop II is introduced, adding 32-bit addressing capabilities and replacing magnetic core memory with battery-backed DRAM.
  • 1983: NonStop TXP (Transaction Processing) launches as the first new implementation of the architecture, featuring cache memory and 2.0 MIPS performance.
  • 1986: Introduction of NonStop VLX (Very Large eXpansion) and NonStop SQL, the first fault-tolerant relational database designed for linear scalability.
  • 1987: NonStop CLX launches as a lower-cost, compact minicomputer for remote office environments.
  • 1989: NonStop Cyclone is released for high-end mainframe markets, featuring superscalar CPUs and fiber optic interconnects. 

3. The MIPS RISC Transition & Acquisitions (1991–2003)

  • 1991: Cyclone/R (or CLX/R) marks the move to MIPS R3000 RISC processors, using object code translation to maintain backward compatibility.
  • 1993: Himalaya K-series is released using MIPS R4400 processors.
  • 1995: Open System Services (OSS) is added to the NonStop Kernel to provide a POSIX/Unix-like environment.
  • 1997: Compaq acquires Tandem Computers. The Himalaya S-Series introduces ServerNet, which later becomes the InfiniBand industry standard.
  • 2002/2003: HP merges with Compaq, bringing the NonStop line under Hewlett-Packard. 

4. The HP Integrity & x86 Era (2005–Present)

  • 2005: HP Integrity NonStop (TNS/E) is introduced, migrating the platform to Intel Itanium microprocessors.
  • 2014: NonStop X (TNS/X) launches, shifting the architecture to Intel x86-64 processors for greater industry-standard alignment.
  • 2015: Following the HP corporate split, NonStop becomes part of Hewlett Packard Enterprise (HPE).
  • 2020: Sales of Itanium-based systems officially end in July 2020.
  • 2024–2025: HPE expands the platform with Virtualized NonStop Software for private clouds and consumption-based models via HPE GreenLake.

HP NonStop Tandem Overview and Timeline History by year

HPE NonStop (formerly Tandem and Compaq NonStop) is a family of fault-tolerant, integrated hardware and software systems designed for mission-critical enterprise workloads. Since its introduction in 1976, it has served as the backbone for high-volume transaction environments like banks, stock exchanges, and payment systems, offering 100% continuous uptime. 

Core Architecture and Features

The platform is defined by its “shared-nothing” architecture, where every component is redundant to eliminate single points of failure. 

  • Continuous Availability: If a hardware or software component fails, a backup takes over immediately without disrupting the application, a process often managed through process pairs (primary and hot backup processes).
  • Linear Scalability: You can add capacity (CPUs, memory) seamlessly without downtime. Systems can scale from a few processors to clusters of over 4,000 CPUs while maintaining a single-system image for management.
  • Integrated Stack: Unlike standard servers, NonStop includes a fully integrated stack of hardware, the NonStop OS (a proprietary kernel), a relational database (NonStop SQL), and middleware.
  • Fail-Fast Design: Modules are self-checking; they stop immediately upon detecting an error to prevent data corruption, allowing the redundant backup to resume processing from the last known good state. 

Current Hardware and Deployment

While historically based on proprietary or Itanium processors, modern NonStop systems (NonStop X) utilize industry-standard Intel Xeon processors and high-speed InfiniBand interconnects. 

  • High-End Systems: Models like the NS9 X5 are built for the most demanding high-volume transaction processing (OLTP).
  • Mid-Range/Entry Systems: Models like the NS5 X5 offer fault tolerance for smaller enterprises or development environments.
  • Virtualization & Cloud: HPE Virtualized NonStop Software allows the platform to run on standard private cloud infrastructure (e.g., VMware, OpenStack), and it is also available via HPE GreenLake as a consumption-based, pay-as-you-go service. 

Software and Security

  • Database: Supports NonStop SQL/MX and SQL/MP for multi-tenant, fault-tolerant data management.
  • Development: Supports modern languages like Java, C++, Python, COBOL, and the TACL scripting language. Developers can use the Eclipse-based IDE for building and debugging applications.
  • Security: Built with Zero Trust principles, including hardware-level vulnerability mitigations (e.g., against Spectre/Meltdown) and real-time threat detection. 

Detailed Architecture

HPE NonStop architecture is a fault-tolerant, shared-nothing, massively parallel computing platform designed for 100% operational continuity. Originally developed by Tandem Computers, it is engineered so that no single hardware or software failure can bring down the system. 

Core Architectural Pillars

  • Shared-Nothing Architecture: Each processor has its own dedicated memory, I/O bus, and copy of the HPE NonStop Operating System (NSK). This eliminates resource contention and single points of failure found in shared-memory systems.
  • Massive Scalability: Systems scale linearly by adding more processors. A single node can support up to 16 CPUs, and multiple nodes can be clustered to support over 4,000 CPUs.
  • Fault Tolerance (Process Pairs): Software availability is maintained through “process pairs”—a primary process and a passive backup process. If the primary fails, the backup immediately takes over without losing data or state.
  • Fail-Fast Design: Hardware and software modules are designed to stop immediately upon detecting an error (“fail-stop”) to prevent data corruption from propagating. 

Hardware Components

  • Compute Nodes: Modern HPE NonStop X systems use standard Intel Xeon x86-64 processors but implement fault tolerance through specialized system interconnects.
  • System Interconnect (Fabric):
    • InfiniBand: Used in NonStop X systems for high-speed, low-latency communication between CPUs and I/O devices (up to 56 Gbps).
    • ServerNet: The legacy high-speed, point-to-point switched fabric used in older S-series and Integrity i-series systems.
  • CLIMs (Cluster I/O Modules): Specialized offload engines for networking (IP CLIM), storage (Storage CLIM), and telco protocols. They handle I/O processing to free up the main host CPUs. 

Integrated Software Stack

The NonStop platform is a “tightly coupled” environment where hardware and software are integrated for availability. 

  • NonStop OS (NSK): A message-based operating system that manages the distributed resources as a single system image.
  • HPE NonStop SQL/MX: A distributed, fault-tolerant relational database that provides ANSI SQL compliance and automatic load balancing across the cluster.
  • HPE Pathway (TS/MP): An application server and middleware framework that manages workload distribution, load balancing, and automatic process restarts.
  • TMF (Transaction Monitoring Facility): Ensures database integrity by managing atomic transactions; if an update fails, TMF automatically rolls back the changes. 

Modern Deployment Options

  • HPE Virtualized NonStop (vNS): The complete software stack decoupled from proprietary hardware, allowing it to run as a set of virtual machines on industry-standard x86 servers within a private cloud (VMware).
  • HPE GreenLake: A consumption-based model providing NonStop capabilities as a cloud-like service. 

Mark Whitfield HP NonStop Tandem experience & Project Management Templates

Mark Whitfield is an experienced IT Project Manager and software developer who has spent over 22 years specialising in HP NonStop (formerly Tandem) systems. He is currently an Engagement Project Manager at Capgemini. 

Career & Expertise

Whitfield’s career in HP NonStop began in 1990 and includes significant technical and leadership roles across the financial and technology sectors: 

  • Software Development: Early in his career, he worked as a programmer for The Software Partnership (later Deluxe Data/FIS), focusing on electronic banking software like sp/ARCHITECT on Tandem mainframes.
  • Insider Technologies (1995–2013): He spent 18 years at Insider Technologies as a Senior Development Engineer and Project Manager. His work involved:
    • Developing monitoring and diagnostic software such as Reflex 80:20, Reflex ONE24, and RTLX (Real-Time Log Extraction) for payment systems.
    • Managing the first HP OpenView Operations Smart Plug-In certification for the NonStop platform.
    • Designing XPERT24, a performance tracking product for ACI’s XPNET layer.
  • Capgemini (2016–Present): As an Engagement Project Manager, he has led digital projects for major clients in the automotive, government, and aerospace sectors, including a cloud migration for UK Government applications. 

Technical Contributions

  • Publications: He has authored articles for globally published journals like The Connection (2013), discussing topics such as querying terabytes of legacy transaction log data from NonStop mainframes.
  • Project History: He has managed high-value projects, including a £5 million initiative to migrate legacy HP NonStop software to AIX-based technologies for a large UK retail bank.
  • Training: He is trained in various NonStop-specific technologies, including TAL (Transaction Application Language), COBOL85, PATHWAY, and NonStop SQL. 

Whitfield also maintains a professional website, mark-whitfield.com, where he provides project management templates and resources related to HP NonStop and Tandem systems. 

Mark Whitfield provides a comprehensive bundle of over 200 editable project management templates designed for Agile, Waterfall, and PRINCE2 methodologies. These templates are based on over 30 years of project delivery experience and are available for purchase via his official website or Etsy shop. 

Key Template Categories

The bundle includes a wide variety of tools across different formats (Excel, PowerPoint, Word, and MS Project): 

  • Planning & Scheduling:
    • Plan on a Page (POaP): Over 30 PowerPoint slide examples for executive-level summaries.
    • Detailed Project Plans: MS Project (MPP) and Excel templates for SDLC, PRINCE2 7th Edition, and Agile Scrum projects.
    • Gantt Charts: Built-in tracking views for both MS Project and Excel.
  • Tracking & Control:
    • RAID Logs: Comprehensive logs for tracking Risks, Actions, Issues, and Dependencies, plus additional tabs for Change Requests and Lessons Learned.
    • RACI Matrix: Templates to define project roles and responsibilities (Responsible, Accountable, Consulted, Informed).
    • Finance Trackers: Tools for internal and external forecast vs. actual costs, including margin and variance tracking.
  • Agile Specific Tools:
    • Burn Down & Burn Up Charts: Excel-based alternatives when tools like Jira are unavailable.
    • Agile Story Dependency Tracking: Specifically for managing dependencies between agile stories and external suppliers.
  • Reporting & Governance:
    • Status Reports: Weekly and monthly templates in Word and PowerPoint formats.
    • Stakeholder Analysis: Power/interest mapping and engagement plan templates.
    • Benefits Realisation: Plans to track project outcomes against initial business goals. 

Purchase Benefits

  • Lifetime Upgrades: Once purchased, all future additions and updates to the template package are provided for free.
  • Compatibility: Templates are designed for Microsoft Office 365 but also include Excel versions compatible with earlier software.
  • Support: The package typically includes walkthrough Word documents to guide users on how to use each major template.

Mark Whitfield HP NonStop Tandem experience & Project Management Templates

IT Career snapshot of Mark Whitfield, Senior IT Project Manager (SC cleared)

This resume summarizes the career of Mark Whitfield, a Senior IT Project Manager with over 30 years of experience specializing in digital and software development lifecycles, cloud migrations, and HP NonStop systems. 

Personal Details

  • Name: Mark A. Whitfield
  • Location: Manchester, UK
  • Nationality: British
  • Security Clearance: SC Cleared to 2031
  • Professional Profiles: Official Website | LinkedIn Profile 

Executive Summary

  • Experience: 30+ years in IT.
  • Core Focus: Senior Project Management for Digital/ Software Development Lifecycles (SDLC).
  • Expertise: Transitioning from a technical background in programming (pre-2000) to senior leadership in large-scale projects for global blue-chip companies. 

Key Skills & Competencies

  • Methodologies: PRINCE2 Practitioner, Agile (Scrum/ Kanban), Waterfall, ITIL, ISO QA.
  • Project Controls: MS Project, Budget & Burn Tracking, GDPR compliance, Supplier & Stakeholder Management, Statement of Work (SoW).
  • Technical Proficiencies:
    • Platforms: HP NonStop (Tandem), Cloud Migration (Hybrid).
    • Languages (Historical): C/C++, Java, COBOL85, TAL, TACL, SCOBOL, SQL, MS SQL.
    • Utilities: PATHWAY, SCF, FUP, INSPECT, XPNET. 

Professional Experience

  • Senior IT Project Manager (Various Projects):
    • Managed large-scale solutions for clients including Jaguar Land Rover (JLR), Heathrow, Royal Mail Group (RMG), NATS, and Euroclear.
    • Extensive work within the financial sector for Bank of England, Barclays, HSBC, Santander, Standard Chartered, Deutsche Bank, and Global Payments.
    • Government and public sector projects for Defra, UKEF, Welsh Water, and Scottish Water.
  • Early Career (Programmer / Technical Lead):
    • 1990 – 1995: Programmer at The Software Partnership (later Deluxe Data) in Runcorn, specializing in electronic banking software (sp/ARCHITECT-BANK) on Tandem Mainframe Computers. 

Education & Certifications

  • Degree: Higher National Diploma (HND) in Computing (Distinction, Graduated 1990).
  • Certifications:
    • Microsoft Azure Fundamentals (Certified).
    • PRINCE2 Practitioner.
    • Agile/ Radtac Course Completion. 

HPE NonStop Tandem Programming Languages, a development timeline

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).

Evolution of C++ on HPE NonStop Tandem systems

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. 

Evolution of C++ on HPE NonStop Tandem systems

HPE NonStop Pathway (now often part of NonStop TS/MP) – Detailed Timeline

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.
  • Serverclasses: Groups of identical server processes that distribute transaction load for fault tolerance. 

HPE NonStop Pathway (now often part of NonStop TS/MP) – Detailed Timeline

TACL for HPE NonStop Tandem, Detailed Timeline

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.

TACL for HPE NonStop Tandem, Detailed Timeline

HPE NonStop Tandem TAL Detailed Timeline

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:

  1. Source Code Creation: Writing statements, removing comments, and defining PROCs and SUBPROCs.
  2. Compilation: Running the TAL Compiler to generate an object file.
  3. Binding: Using the Binder Program to link the object file with the TALLIB Run-Time Library.
  4. Acceleration: Running the Accelerator (for TNS code) to optimise it for native hardware execution.
  5. Execution: Deploying via the TACL interface. 

HPE NonStop Tandem TAL Detailed Timeline

COBOL Development Detailed Timeline Overview

COBOL (Common Business-Oriented Language) has evolved from a 1959 “stopgap” experiment into a cornerstone of global finance, currently powering approximately 95% of ATM swipes and 80% of in-person credit card transactions. 

The Early Years (1959–1965)

  • 1959 (Origins): Following a meeting at the Pentagon in May, the Conference on Data Systems Languages (CODASYL) was formed to create a machine-independent language for business. It was heavily influenced by Grace Hopper’s FLOW-MATIC.
  • 1960 (First Release): The COBOL-60 specifications were published. In December, the same program was successfully run on two different manufacturers’ computers (RCA and Univac), proving portability.
  • 1961–1965 (Rapid Revisions): Successive updates included COBOL-61 and COBOL-65, which introduced critical features like the SORT and REPORT WRITER facilities. 

Standardisation & Dominance (1968–1985) 

  • 1968 (COBOL-68): The American National Standards Institute (ANSI) published the first official standard, making COBOL the industry benchmark.
  • 1974 (COBOL-74): This update added file organisation methods and the DELETE statement, further refining data management capabilities.
  • 1985 (COBOL-85): A major milestone that introduced structured programming (e.g., END-IF, EVALUATE) to improve code readability and maintainability. 

Modernisation & Object-Orientation (2002–Present) 

  • 2000 (The Y2K Crisis): COBOL regained global attention as programmers rushed to fix the “Millennium Bug” in legacy systems.
  • 2002 (COBOL-2002): The first major update in 17 years introduced Object-Oriented (OO) features, Unicode support, and XML processing.
  • 2014 (COBOL-2014): Simplified the language by making several niche features (like the SCREEN SECTION) optional and adopting IEEE 754 floating-point math.
  • 2023 (COBOL-2023): The current ISO/IEC 1989:2023 standard added modern programming comforts like asynchronous messaging (SEND/RECEIVE), transaction processing (COMMIT/ROLLBACK), and bitwise operators. 

Today, despite its age, an estimated 800 billion lines of COBOL remain in active use, with modernization efforts focusing on cloud integration and interoperability with Java and .NET.

COBOL Development Detailed Timeline Overview

sp/ARCHITECT-BANK module – development in Runcorn, Cheshire by The Software Partnership

The software known as sp/ARCHITECT (specifically the sp/ARCHITECT-BANK module) has a timeline tied to its development in Runcorn, Cheshire, by a firm originally called The Software Partnership. 

Company & Product Timeline

  • Mid-1980s: The Software Partnership is co-founded by Nigel Walsh.
  • 1989: The company begins significant operations in Runcorn, initially at Wingate Drive (Timperley) and later moving to Norton House in Crowngate.
  • 1990–1994: Development period for sp/ARCHITECT in Runcorn. The software was a banking system used by major institutions including TSB, Bank of Scotland, and Rabobank.
  • 1992: The firm relocates its Runcorn base to Wingate House on Northway.
  • 1994: The Software Partnership is acquired by the American company Deluxe Electronic Payment Systems (a division of Deluxe Corporation).
  • Post-1994: Following the acquisition, the entity operated as Deluxe Data International Operations.
  • Later Transitions: The lineage of the Runcorn operations eventually merged into larger fintech entities, including eFunds, EFD, and ultimately FIS. 
Deluxe Data, Wingate House
The Software Partnership, Norton House

sp/ARCHITECT-BANK module – development in Runcorn, Cheshire by The Software Partnership

TSP / Deluxe Data : 1990 – 1995

HPE NonStop Tandem Timeline History

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.

  • 1997: Compaq acquires Tandem for $3 billion to bolster its enterprise server offerings.
  • 1997: The Himalaya S-Series introduces ServerNet, a high-speed interconnect that later evolved into the industry-standard InfiniBand.
  • 2002: HP merges with Compaq, bringing the NonStop line under Hewlett-Packard.
  • 2005: NonStop i (Integrity) is launched, transitioning from MIPS to Intel Itanium processors. 

The Modern HPE Era (2015–Present)

Today, the platform focuses on integrating with modern data centre standards like x86 and cloud-native virtualisation. 

  • 2014–2015: NonStop X (TNS/X) is introduced, moving the architecture to industry-standard Intel x86-64 processors.
  • 2015: HP splits; the server line becomes part of Hewlett Packard Enterprise (HPE).
  • 2017: Virtualised NonStop (vNS) is released, allowing the software stack to run in virtual machines (KVM/OpenStack).
  • 2020: HPE officially ends sales of Itanium-based systems, completing the transition to x86.
  • 2024: The platform celebrates its 50th anniversary, continuing to power the majority of the world’s ATM and credit card transactions. 

HPE NonStop Tandem Timeline History

Insider Tech : 1995 – 2013
My Career in HPE NonStop Tandem, 1995 thru 2013
TSP / Deluxe Data : 1990 – 1995
My Career in HPE NonStop Tandem, 1990 thru 1995

BASE24 and core Networking Component XPNET timeline

The technical timeline for BASE24 and its core networking component, XPNET, reflects the evolution of high-availability payment switching on HP NonStop (Tandem) systems.

Technical Evolution Timeline

  • 1980s: The Foundation
    • BASE24 Release: Originally developed by Applied Communications Inc. (now ACI Worldwide), BASE24 was built for the Tandem Guardian operating system.
    • XPNET Introduction: Developed as the Message-Oriented Middleware (MOM) to handle all transaction routing and communications. It introduced a multi-node architecture allowing different “satellite” processes (ATM, POS, Host) to communicate.
  • 1990s: Scale and Maturity
    • Classic Era: BASE24 “Classic” became the industry standard for ATM and POS switching.
    • XPNET 3.x: Enhanced to support larger networks and more complex auditing through NCPCOM.
    • Language & DB: The system relied on TAL (Tandem Application Language), COBOL, and the Enscribe database.
  • 2000s: The Shift to BASE24-eps
    • 2003–2005: ACI introduced BASE24-eps (Electronic Payment Systems). This was a re-architecture using C++ and Java to provide platform independence.
    • XPNET 4.1: Released to support the transition, adding features like Common Transport Subsystem (CTS) for better Pathway integration and support for external processes.
    • z/OS Support: By 2009, BASE24-eps was fully ported to IBM z/OS using CICS and VSAM.
  • 2010s – Present: Modernisation & Cloud
    • 2014–2017: Continued updates to BASE24 Classic R6.0, maintaining its relevance for legacy users.
    • Cloud Enablement: Recent versions of BASE24-eps focus on REST API integration via tools like LightWave, allowing legacy XPNET paths to be exposed as web services.
    • Active/Active Environments: Modern implementations focus on “continuous availability” using GoldenGate for data replication between sites. 

Key Technical Components

  • NMM (Network Management Module): The core process of XPNET that manages the configuration of lines, stations, and links.
  • LCONF: The Logical Network Configuration File used by XPNET to define how messages route between processes.
  • Auditing: XPNET provides the primary transaction auditing mechanism, which is still utilized by both Classic and eps versions.

BASE24 and core Networking Component XPNET