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
The HPE NonStop Data Definition Language (DDL) dictionary is a specialized subsystem used to define and manage data objects for Enscribe files and translate those definitions into source code for various programming languages. It serves as a central repository for metadata, ensuring consistent data structures across applications written in C, COBOL, TAL, or TACL.
Program Summary
The DDL dictionary program functions as a metadata management tool. Key capabilities include:
Centralised Definition: Defines records, fields, and file attributes in a hierarchical structure.
Code Generation: Translates DDL definitions into language-specific source code (e.g., COBOL copybooks or C headers).
Dictionary Maintenance: Allows users to create, examine, and update dictionaries to reflect changes in data structures.
Interoperability: Modern tools like Ddl2Bean convert dictionary files into Java Beans or XML, enabling cross-language and cross-platform use.
Future Outlook
The future of HPE NonStop DDL focuses on modernisation and integration rather than replacement.
Data Virtualization: Integration with AI factories and object storage platforms to expose legacy metadata in open-table formats like Apache Iceberg.
API Centricity: Enhancements to the NonStop API Gateway will likely use DDL metadata to automate REST/JSON service orchestration.
Real-time Analytics: Native streaming of NonStop data into platforms like Kafka, using DDL definitions to map real-time changes into analytics-ready formats.
HPE NonStop PATHCOM is the interactive management interface for the Pathway transaction processing environment. It allows administrators to configure, monitor, and control PATHMON-governed objects such as serverclasses, TCPs (Terminal Control Processes), and links.
Historical Timeline: The Evolution of Pathway & PATHCOM
The history of PATHCOM is inseparable from the Tandem NonStop platform, which pioneered fault-tolerant Online Transaction Processing (OLTP).
The Tandem Era (1974 – 1997)
1974 – 1976: Tandem Computers is founded. The first NonStop I system ships in 1976.
1983: Tandem introduces Pathway software alongside the Transaction Monitoring Facility (TMF). This milestone removes the requirement for developers to manually code fault tolerance into applications, as the Pathway infrastructure (managed via PATHCOM) handles it automatically.
Early 1990s: The platform migrates from proprietary stack machines to MIPS RISC processors (TNS/R architecture). PATHCOM evolves to manage more complex distributed environments.
1994: Open System Services (OSS) is introduced, allowing NonStop to support a Unix-like POSIX environment.
2005: Migration from MIPS to Intel Itanium (Integrity NonStop) begins.
2010s: Pathway evolves into HPE NonStop Pathway with TS/MP (Transaction Services/Massive Parallelism), enabling near-linear scalability for massive OLTP workloads.
The Modern HPE Era (2014 – Present)
2014: NonStop X is introduced, migrating the architecture to Intel x86-64 processors.
2015: Hewlett-Packard splits; the platform continues under Hewlett Packard Enterprise (HPE).
2020 – 2024: Focus shifts toward virtualisation and hybrid cloud. Modern Pathway/TS environments now support massive scaling up to 24,480 cores in a single system image.
Summary of PATHCOM Functionality
Future of NonStop Pathway
HPE’s roadmap for NonStop focuses on integrating mission-critical reliability with modern data centre technologies:
Modernisation: Support for Kubernetes Helm deployments and cloud-native frameworks.
Hardware Advancements: New NS9 X5 and NS5 X5 platforms offer double the memory capacity and 2x faster system interconnects.
Open Integration: Continued emphasis on open application development environments and open-source frameworks.
Hybrid Cloud: Positioning NonStop as a key component of HPE GreenLake for mission-critical workloads in the cloud.
HPE NonStop Inspect is the primary symbolic, source-level debugger for applications running on the HPE NonStop (formerly Tandem) operating system. It allows developers to interactively control program execution, examine and change data variables, and debug complex multi-process applications in both the Guardian and Open System Services (OSS) environments.
Program Summary
The Inspect debugger family facilitates high-availability software development through several specialized versions:
Inspect (Legacy): A command-line tool for TNS, TNS/R, and TNS/E systems.
Native Inspect (eInspect/xInspect): Adapted from GDB for Itanium and x86 architectures; it provides a command-line interface with scripting capabilities.
Visual Inspect: A Windows-hosted GUI debugger that provides “point-and-click” efficiency for setting breakpoints and displaying variables.
NSDEE (Eclipse): Modern debugging integrated into the Eclipse-based development environment, supporting NonStop Application, Attach Process, and Snapshot debug configurations.
Historic Timeline by Era
The evolution of the NonStop debugger mirrors the platform’s hardware transitions over five decades.
The Tandem Era (1974 – 1997)
1974: Tandem Computers is founded; the platform begins with T/16 (NonStop I).
1980s:Inspect is introduced as the standard interactive debugger for the TNS (Tandem Network Strategy) CISC architecture.
Early 1990s: Migration to MIPS-based TNS/R systems; Inspect is updated to support RISC instruction sets and optimized compilers.
The Compaq & Early HP Era (1997 – 2014)
1997: Compaq acquires Tandem.
2002: HP acquires Compaq; migration to TNS/E (Intel Itanium) architecture begins.
2005 – 2010:Visual Inspect becomes a staple for developers seeking a GUI experience on Windows.
2013: Release of the Inspect H01 Manual, documenting full support for TNS/R and TNS/E concurrent debugging.
The Modern HPE Era (2014 – Present)
2014: Introduction of NonStop X (x86-64 architecture). Native Inspect (xInspect) is launched, based on GDB, to support the move away from Itanium.
2015: HPE is formed; focus shifts to the NonStop Development Environment for Eclipse (NSDEE).
2020 – 2024: Enhancements in NSDEE include improved OSS process handling and support for large-scale application debugging.
HPE’s roadmap for NonStop focuses on modernisation through tradition, ensuring that legacy tools like Inspect remain compatible while transitioning to cloud-native and virtualized environments.
Virtualized NonStop (vNS): Debugging tools are being adapted to work seamlessly within enterprise private clouds and HPE GreenLake consumption models.
Mark Whitfield is a highly experienced SC-cleared Senior IT Project Manager and Engagement Manager with over 30 years of experience in the software development lifecycle (SDLC), specializing in Agile and Waterfall delivery for financial, automotive, and public sector clients. He has a strong background in HP NonStop (Tandem) systems and currently works for Capgemini.
Mark Whitfield, Senior IT PM and Project templates author
1990–1994: The Software Partnership (Runcorn): Programmer specializing in electronic banking software (sp/ARCHITECT-BANK) on Tandem Computers.
1994–1995: Deluxe Data (formerly TSP): Lead Analyst/Programmer, focusing on software investigation, design, coding, and on-site installation for clients like TSB, Bank of Scotland, and Rabobank.
Development & Technical Specialization (1995–2013)
1995–2013: Insider Technologies Limited: Spent 18 years progressing from Senior Development Engineer to Project Manager for Strategic Technical Initiatives.
Key Roles: Managed Reflex 80:20 and Reflex ONE24 product development, technical pre-sales, and consultancy. Developed diagnostic software for monitoring payment systems (BASE24).
Notable Project: Managed a bid to replace legacy ATM tools at LloydsTSB (5000 ATMs) with Reflex ONE24.
Banking & Digital Project Management (2013–2016)
2013–2014: Wincor Nixdorf: Project Manager in the Professional Services Banking Division, managing a £5m+ work stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
2014–2016: Betfred: Senior Digital Project Manager for the Online and Mobile Division, delivering payment gateways and sportsbooks for iOS, Android, and Windows.
Senior Engagement Management (2016–Present)
2016–Present: Capgemini UK: Engagement Project Manager responsible for delivering both Waterfall and Agile digital projects.
2016 (Approx.): Assigned to a UK-wide Air Traffic organization (NATS) for Apple iOS app delivery.
2018–2019: MuleSoft (Secondment): Served as a Delivery Manager for the Anypoint Platform.
Current Focus: Cloud Migration (Hybrid) of 130 apps for UK Government.
Agile Management: “Mark provided an excellent barrier between us (developers) and a difficult client…ensuring that we followed the agile principles” — Callum Marriage (Developer).
MuleSoft/Capgemini Engagement: “Customers loved him. His was extremely detailed oriented and understood the often-complex needs…never became flustered in high pressure situations” — Delivery Manager, MuleSoft.
Betfred (2015): “I would highly recommend Mark for his ability to successfully multi-task under significant pressure… [he] produced a very comprehensive handover document” — IT Compliance Analyst, Betfred.
Capgemini/JLR Project: “Mark was able to do a good planning, with the correct resources, on time delivery and with good relationship between stakeholders” — Head of Integration Development.
Mark Whitfield’s website (mark-whitfield.com) serves as a professional portfolio and resource hub for his 30+ year career as a SC-cleared Senior IT Project Manager. It offers over 200 editable project management templates for Agile, Waterfall, and PRINCE2 methodologies, alongside career insights and project experience.
Website & Content Overview
Project Management Resources: The site, often known as PROject Templates, provides downloadable templates for planning, scheduling (Gantt charts), project initiation (PID), and project control.
Methodology Focus: Resources are tailored for PRINCE2 (including Agile Scrum), and Agile/Waterfall delivery methods.
Career Portfolio: Features his work history as a Senior IT Project Manager, including roles at Capgemini, Betfred, and various financial institutions.
Technical Specialization: Highlights expertise in HP NonStop systems, digital projects, and payment/transaction systems.
Professional Background: Mentions his experience with major clients such as Jaguar Landrover, Heathrow, Royal Mail, and various banks.
The site is designed for project managers looking for templates to speed up project documentation and for clients looking to review his career accomplishments.
Senior IT Project Manager & Project Templates author – Mark Whitfield
Templates sold on this website are designed for Microsoft Office (Excel, Word, PowerPoint) and MS Project (MPP) and are used for tracking and planning software development lifecycle (SDLC) projects.
Template Breakdown
The templates, often sold in a bundle, include over 200+ editable items aimed at project delivery. Key components include:
Project Planning (MS Project & Excel): Detailed Waterfall project planners with Gantt views, Agile Sprint plans, and Plan on a Page (POaP) examples.
RAID Logs (Risk, Action, Issue, Dependency): Comprehensive Excel trackers for managing risks, issues, assumptions, and dependencies.
Financial & Resource Management: Project finance trackers (forecasts, actuals, variance) and resource trackers for tracking team members and costs.
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)
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.
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
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.
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.
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.
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
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:
Multi-Channel Support: Manages transactions from ATMs, POS terminals, mobile, and ecommerce.
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.
Mark Whitfield is a Senior, SC cleared IT Project and Engagement Manager with over 30 years of experience, specializing in the software development lifecycle (SDLC) for large-scale digital and financial payment systems.
Mark Whitfield is a Senior, SC cleared IT Project and Engagement Manager
Key Projects: Leading high-value digital transformations and cloud migrations for UK Government applications, automotive (Jaguar Land Rover), and aerospace (Air Traffic Management iOS apps).
2014–2016: Betfred Limited (UK)
Role: IT Senior Digital Project Manager, Online and Mobile Division.
Key Projects: Managed multiple Agile SCRUM projects for payment gateways, sportsbooks, and virtual gaming components across iOS, Android, and Windows platforms.
2013–2014: Wincor Nixdorf Limited (UK)
Role: Project Manager, Professional Services – Banking Division.
Key Projects: Managed a £5M+ workstream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) program, migrating legacy HP NonStop systems to AIX-based Oracle technologies.
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.
Radbroke Hall is a 64-acre “Innovation Campus” in Cheshire that serves as the global technology and operations hub for Barclays. Originally built as a French chateau-style private residence in 1917, it transitioned through use by a nuclear research group before Barclays acquired it in 1972. Today, it employs approximately 4,000–6,500 staff and has been the development site for pioneering banking technology, including the first ATMs, debit cards, and mobile banking platforms.
Radbroke Hall History Timeline
Era 1: Private Residence (1914–1956)
1914: Construction begins on the Hall for Manchester textile manufacturer Claude Hardy and his wife Olga.
1916: Claude Hardy dies; Olga oversees the completion of the Portland stone building alone.
1917: The Hall is completed as a private residence.
1920s–1930s: The Hall remains largely unoccupied during these decades.
Era 2: Industrial & Nuclear Research (1956–1972)
1956: The Hardy family sells the estate to The Nuclear Power Group.
1956–1972: The site is used for nuclear energy research, with offices and a testing tower constructed on the grounds.
Era 3: The Barclays Transformation (1972–1990s)
1972: Barclays purchases the site from The Nuclear Power Group to reduce high rental costs in London.
1972 (Relocation): Approximately 1,400 staff are relocated from London or hired locally; many find the move from London to the “rural North” a significant culture shock.
1970s–1980s: The site begins its role as an IT hub, instrumental in developing the first cash machines (ATMs) and debit cards.
1985: Barclays reorganises its UK and International banks into a single entity, further centralising tech and staff services at Radbroke.
Era 4: Global Tech & Modernisation (2000s–Present)
Early 2000s: The campus leads the development of Barclays’ online and mobile banking applications.
2012: Barclays celebrates the 40th anniversary of its presence at Radbroke Hall.
2017: The original Hall building marks its 100th anniversary.
2021: Barclays announces a major redevelopment plan to modernise the campus, including the demolition of older buildings (Kilburn, Lovelace, and Brooker Houses) to create a new central “town square” and “re-green” 80,000 sq. ft. of land.
2024: Investment continues to transform Radbroke into a “world-class campus” focused on the future of work and advanced banking APIs.
Barclays House, located at 1 Wimborne Road, was a dominant fixture of the Poole skyline for 46 years. Originally built to decentralise Barclays Bank International operations from London, the nine-storey brutalist structure served as a major regional headquarters from 1976 until its closure in 2022. Following its vacancy, the building was earmarked for conversion into a residential complex featuring 362 apartments.
Historical Overview
Purpose: The building was commissioned to move staff away from high London costs and boost local employment in Poole.
Architecture: Designed by Wilson, Mason and Partners, it features three interlinked octagonal/hexagonal towers in the brutalist style.
Landmark Features: A massive 14-foot aluminium eagle logo (the Barclays emblem) adorned the front of the building for decades.
Detailed Timeline Breakdown
The Development Era (1960s – 1975)
Late 1960s: Poole is selected as the primary location for Barclays Bank DCO (Dominion, Colonial and Overseas) decentralisation.
1971 (August): Planning permission is granted for the project after a public inquiry, with an estimated cost of £5 million.
1972 (September): Construction begins, led by the John Laing Group.
1975 (June): Construction is officially completed.
The Operational Era (1976 – 2021)
1976 (January): Barclays first occupies the building.
1976 – 1980s: Workforce grows rapidly; in its first year, it employed 800 people, eventually peaking at roughly 2,500 employees.
2007 (January): A planning bid to demolish the building for flats is refused due to its scale and lack of amenity space.
2008: Barclays announces plans to build a new HQ in Poole, though these did not result in immediate relocation from the Wimborne Road site.
2016: The building undergoes a major refurbishment to celebrate its 40th anniversary.
The Closure & Transition Era (2022 – Present)
2022 (January 26): Barclays officially closes its doors at Wimborne Road after 46 years.
2022 (October 27): The iconic Barclays eagle logo is removed from the building’s facade by cranes.
2022 (December): Remaining staff (approximately 700) are relocated to new offices in Bournemouth.
2023: VCRE Four Poole submits a planning bid to convert the structure into 362 homes.
2024 (March 8): The separate Poole High Street branch also closes.
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 is a highly experienced Senior IT Project Manager and former developer with over 30 years of expertise in HP NonStop (formerly Tandem) systems, primarily within the electronic banking and payments sectors. He is currently a Senior Project Manager at Capgemini (SC cleared until 2031) and maintains a professional portfolio at mark-whitfield.com.
Historical Timeline & Customer Breakdown
1990 – 1995: The Software Partnership / Deluxe Data (now FIS)
Customer/Projects: Developed electronic banking software, specifically sp/ARCHITECT-BANK, for major financial institutions including TSB, Bank of Scotland, Rabobank, and Girofon (Denmark).
Technical Breakdown: Focused on low-level programming using COBOL85, NonStop SQL, and TAL (Transaction Application Language).
Role: Programmer.
1995 – 2013: Insider Technologies Ltd (ITL)
Customer/Projects: Focused on HP NonStop monitoring, diagnostic, and payment software for high-value banking clients. Key products included Enterprise Manager, XPNET, BASE24, and EPS.
Technical Breakdown:
XPERT24: Produced technical designs for this performance monitoring tool to track XPNET layers and transaction interchange counters (ATM/POS approval rates).
RTLX Payments: Served as IT Project Manager for RTLX (Real-Time Long-term eXchange) payment software.
Infrastructure: Extensive use of Guardian utilities (PATHWAY, SCF, FUP, INSPECT), TACL, and SCOBOL.
Role: Software Design, Team Leading, and Product Management.
2013 – 2016: Freelance / Contract Projects
Customer/Projects: Managed software development lifecycle (SDLC) projects for various blue-chip companies.
Role: IT Project Manager.
2016 – Present: Capgemini
Customer/Projects: Managing large-scale digital and public sector transformations. Notable clients include UK Government (MS Azure Cloud migration), Jaguar Land Rover (JLR), Heathrow, Royal Mail Group, Bank of England, HSBC, Barclays, and Deutsche Bank.
Technical Breakdown: Transitioned from legacy Tandem environments to modern Agile Scrum delivery and Microsoft Azure Cloud hosting.
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 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
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.
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).
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).
TAL (Tandem Application Language) is the original system programming language for the HPE NonStop (formerly Tandem) platform. Developed by Tandem Computers in the mid-1970s, it was designed to provide high-level efficiency while allowing low-level machine access, similar to C but with a syntax influenced by ALGOL.
Detailed Development Timeline
Mid-1970s: The Genesis
Tandem Computers, founded by James Treybig, introduces the first NonStop I system in 1976.
TAL is released as the primary language for writing the Guardian Operating System and system-level utilities.
The Tandem Advanced Command Language (TACL) is initially developed during this decade using TAL.
1980s: Growth and Maturity
1981–1983: Introduction of the NonStop II and TXP systems. TAL becomes the standard for developing mission-critical transaction applications like banking and point-of-sale systems.
1985: The TAL Reference Manual is updated (March 1985), formalising advanced features like DEFINEs, LITERALs, and complex pointer arithmetic.
1990s: Transition to RISC
Tandem introduces TNS/R (RISC) systems based on MIPS processors.
pTAL (Portable TAL) is introduced to allow TAL code to run “natively” on RISC hardware, offering better performance than the emulated TNS environment.
2000s–Present: Modernisation and Maintenance
2003–2005: HP (which acquired Compaq, who had bought Tandem) migrates NonStop to Intel Itanium (TNS/E) and later x86 architectures (TNS/X).
2006: The Common Run-Time Environment (CRE) is enhanced to support mixed-language programs (C, COBOL, pTAL) seamlessly.
Current Status: TAL is considered a legacy language, with most new development occurring in C/C++ or Java. However, it remains vital for maintaining the core Guardian OS and legacy banking kernels.
Typical Program Development Workflow
According to the TAL Programmer’s Guide, a developer follows this “timeline” to create a program:
Source Code Creation: Writing statements, removing comments, and defining PROCs and SUBPROCs.
Compilation: Running the TAL Compiler to generate an object file.
Binding: Using the Binder Program to link the object file with the TALLIB Run-Time Library.
Acceleration: Running the Accelerator (for TNS code) to optimise it for native hardware execution.
PROject Templates 