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.
- Execution: Deploying via the TACL interface.
HPE NonStop Tandem TAL Detailed Timeline