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 MacrosRoutines, 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/OPathway 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