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 DEFINEsLITERALs, 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

Unknown's avatar

Author: Mark Whitfield

Welcome to my site! After graduating in Computing in 1990, I accepted a position as a programmer at a Runcorn based software house specialising in electronic banking software, namely sp/ARCHITECT-BANK on Tandem Computers (now HPE NonStop). This was before the internet became more prevalent and so the notion of enabling desktop access to company accounts for inter-account transfers and book keeping was still quite a cutting edge idea (and smartphones only ever hinted at in Space 1999). The company was called The Software Partnership (which was taken over by Deluxe Data in 1994). I spent 5 years in Runcorn developing code for SP/ARCHITECT for various banks like TSB, Bank of Scotland, Rabobank and Girofon (Denmark) to name but a few. I then moved onto a software house in Salford Quays for further bank facing projects. After a further 23 years in the IT industry and now a Senior IT Project Manager (both Agile and Waterfall delivery), I thought I would echo out my Career Profile in this corner of the internet for quick and easy access.

Leave a comment