1. TAL (Transaction Application Language)
You can't talk about Tandem without talking about TAL. This was the foundational, system-level language for the platform. When the first Tandem NonStop systems shipped in the 1970s, the entire operating system, Guardian, was written in it. Think of it as a love
child of C and Pascal; it had the block structure of Pascal but the low-level power and pointer semantics of C. It was designed to be incredibly efficient, compiling directly into the machine's instruction set without an assembler. While it has been deprecated for new development and much of the OS has been rewritten in C, its DNA is everywhere in the NonStop world. To keep legacy code running, compilers like pTAL and epTAL were created to translate original TAL source for newer RISC and Itanium processors.
2. TACL (Tandem Advanced Command Language)
If TAL is the system's foundation, TACL is the key to controlling it. TACL is the platform's native command shell and scripting language, analogous to Bash on Unix systems but built from the ground up for a multi-CPU, fault-tolerant environment. It’s an interpreted language used for everything from system configuration and monitoring to automating complex operational procedures. Administrators use TACL scripts, often stored as macros or routines, to manage processes, orchestrate failover operations, and run batch jobs. Though HPE later introduced a more standard Unix-like shell (OSS), TACL remains essential for deep system control and is a core skill for any NonStop professional.
3. COBOL85
While TAL built the system, COBOL built the business. COBOL, specifically the COBOL85 standard, was the undisputed workhorse for commercial applications running on Tandem systems. Industries like banking, stock exchanges, and retail relied on it for their mission-critical transaction processing. HPE's implementation was tailored for the NonStop architecture, allowing programmers to embed SQL statements and build fault-tolerant applications using the Pathway transaction monitor. Even today, a massive amount of the world's financial transaction processing runs on COBOL programs executing on NonStop servers, making it a living piece of computing history that's very much still at work.
4. C and C++
As the computing world standardized, Tandem evolved. The introduction of C and C++ was a major step, particularly with the launch of the Open System Services (OSS) environment in 1995. This created a POSIX-compliant subsystem that ran on top of the Guardian kernel, making the NonStop platform look and feel much more like a familiar Unix system. This move was crucial for portability, allowing developers to bring existing applications and a wider talent pool to the platform. Modern NonStop systems offer standard C/C++ compilers, enabling developers to write high-performance applications that can run in either the classic Guardian environment or the more open OSS personality.
5. Java
Java became a first-class citizen on NonStop platforms in the late 1990s, a move accelerated after Compaq's acquisition of Tandem. The goal was to attract enterprise web applications, especially in the burgeoning internet banking sector. HPE heavily invested in optimizing the Java Virtual Machine (JVM) for the NonStop's unique shared-nothing architecture. This allows modern, object-oriented Java applications to take full advantage of the hardware's scalability and fault tolerance. Today, with full support for recent OpenJDK versions and a rich ecosystem of related tools, Java is a primary language for new development on NonStop servers.
6. Python
Reflecting the demands of modern IT, Python has also found a home on HPE NonStop systems. Running within the Open System Services (OSS) layer, Python allows developers to leverage its power for automation, data analysis, and DevOps orchestration alongside the core transactional systems. HPE provides support for modern Python 3, enabling integration with popular frameworks and continuous integration/continuous delivery (CI/CD) pipelines. This allows teams to manage NonStop environments using the same modern scripting tools and DevOps practices they use elsewhere, bridging the gap between legacy reliability and contemporary agility.
