Tag: Tandem

HPE NonStop Tandem Programming Languages, a development timeline

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).

Evolution of C++ on HPE NonStop Tandem systems

The evolution of C++ on HPE NonStop systems traces the platform’s transition from proprietary Tandem architectures to modern x86-64 standards.

HPE NonStop C++ Evolution Timeline

  • Early 1990s: Introduction of Native C/C++ (TNS/R)
    With the move to MIPS-based TNS/R architecture, Tandem introduced native C and C++ compilers. These supported the Guardian and the then-new Open System Services (OSS) personalities.
  • 2005: Itanium Transition (TNS/E)
    As the platform migrated to Intel Itanium processors (J-Series), the C++ compiler was updated to support the TNS/E (Tandem Native Stack / EPOC) architecture. This era introduced more robust Standard C++ Library support, though it required specific header management (e.g., CPATHEQ pragmas).
  • 2015: x86 Migration (TNS/X)
    The launch of NonStop X (L-Series) on Intel x86-64 marked a major shift. The compiler suite was re-engineered to leverage the x86-64 Instruction Set Architecture, providing significantly higher performance for C++ applications.
  • 2017: 64-Bit Addressing Support
    HPE introduced comprehensive 64-bit support for OSS processes (LP64 data model). This allowed C++ applications to access massive memory heaps beyond the previous 32-bit (ILP32) limits.
  • 2020–2022: Modern C++ Standards (C++11/14/17)
    HPE updated its toolchains to support modern language standards. The NonStop Development Environment for Eclipse (NSDEE) 13.x versions specifically introduced a dedicated UI for setting the C++17 Language Standard.
  • 2024: Kernel-Level Threading (KLT)
    The release of the L25.09 RVU brought Kernel-Level Threading to native C++ applications. This allowed C++ threads to execute concurrently across different IPUs, moving beyond the older POSIX User Threads (PUT) model.
  • 2025: Cloud-Native Development
    HPE now offers the HPE NonStop Development Environment (NSDevEnv) in the public cloud, allowing developers to build fault-tolerant C++ applications using a cross-compiler model without on-premise hardware. 

Evolution of C++ on HPE NonStop Tandem systems

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 Macros, Routines, 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/O, Pathway 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

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 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:

  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

HPE NonStop Tandem Timeline History

HPE NonStop (originally Tandem) has a nearly 50-year history as the gold standard for fault-tolerant, “always-on” computing. Originally developed by Tandem Computers to eliminate single points of failure, the platform has survived through several major corporate acquisitions while evolving its underlying processor architecture. 

Founding and The Tandem Era (1974–1997)

The “NonStop” architecture was born from the idea that a single hardware failure should never crash a system.

  • 1974: Tandem Computers is founded by Jimmy Treybig and three former HP engineers.
  • 1976: The first Tandem/16 (later NonStop I) is shipped to Citibank. It featured a “shared-nothing” architecture where each CPU had its own memory and copy of the Guardian OS.
  • 1981: NonStop II is released, introducing 32-bit addressing to support larger applications.
  • 1983: The NonStop TXP and Pathway software are introduced. Pathway revolutionized the platform by allowing programmers to write fault-tolerant apps without manually coding “checkpoints”.
  • 1986: NonStop SQL is launched, the first fault-tolerant relational database.
  • 1989: NonStop Cyclone arrives, a high-end mainframe-class system.
  • 1991–1993: Transition to MIPS RISC processors begins with the Cyclone/R and the Himalaya K-series. 

Corporate Acquisitions and Transition (1997–2014)

The platform changed hands twice in five years, but the mission-critical nature of the technology kept it alive.

  • 1997: Compaq acquires Tandem for $3 billion to bolster its enterprise server offerings.
  • 1997: The Himalaya S-Series introduces ServerNet, a high-speed interconnect that later evolved into the industry-standard InfiniBand.
  • 2002: HP merges with Compaq, bringing the NonStop line under Hewlett-Packard.
  • 2005: NonStop i (Integrity) is launched, transitioning from MIPS to Intel Itanium processors. 

The Modern HPE Era (2015–Present)

Today, the platform focuses on integrating with modern data centre standards like x86 and cloud-native virtualisation. 

  • 2014–2015: NonStop X (TNS/X) is introduced, moving the architecture to industry-standard Intel x86-64 processors.
  • 2015: HP splits; the server line becomes part of Hewlett Packard Enterprise (HPE).
  • 2017: Virtualised NonStop (vNS) is released, allowing the software stack to run in virtual machines (KVM/OpenStack).
  • 2020: HPE officially ends sales of Itanium-based systems, completing the transition to x86.
  • 2024: The platform celebrates its 50th anniversary, continuing to power the majority of the world’s ATM and credit card transactions. 

HPE NonStop Tandem Timeline History

Insider Tech : 1995 – 2013
My Career in HPE NonStop Tandem, 1995 thru 2013
TSP / Deluxe Data : 1990 – 1995
My Career in HPE NonStop Tandem, 1990 thru 1995

HPE NonStop Tandem ViewPoint EMS Event log viewer

The timeline of HPE NonStop ViewPoint (and its modern successor, Web ViewPoint) reflects the evolution of NonStop systems from Tandem’s fault-tolerant beginnings to Hewlett Packard Enterprise’s modern cloud-integrated management. 

Detailed History Timeline

  • Pre-2000: Legacy ViewPoint
    • Originally developed for the Tandem NonStop platform to provide a graphical operations interface for monitoring system status and events.
    • Featured early support for DSM/PM (Distributed Systems Management/Performance Monitor) and event management through primary and alternate event logs.
  • 2003–2005: Transition to Web ViewPoint
    • September 2003: Version 4 AAD released as an early iteration of the web-based management tool.
    • May–October 2004: Progressive upgrades (Versions 5.0 and 5 AAF) introduced refined management capabilities for S-Series servers.
    • March 2005: Version 5 AAG released, consolidating features for the S-Series.
    • November 2005: Web ViewPoint for Itanium (Version H01AAI) launched, marking the shift to the Intel Itanium-based Integrity NonStop architecture.
  • 2013–2015: The x86 Revolution & Virtualization
    • 2014: Support for Intel x86 architecture was officially announced, leading to the launch of NonStop X.
    • Evolution to Web ViewPoint Enterprise (WVP E): The platform evolved into an automated management product, eventually adding integration with cloud-based analytics like HPE Remote Analyst.
  • 2018–Present: Modern Hybrid Cloud Era
    • L-Series Support: Continued updates provided support for L-Series operating environments and enhanced security monitoring.
    • 2023–2024: Recent developments focus on Web ViewPoint Enterprise, featuring a global configuration platform and enhanced historical data capture through integrations like Sentinel for HPE NonStop. 

For more specific documentation, you can browse the HPE NonStop Manuals on the HPE Support Center. 

HPE NonStop Tandem Transaction Logs

HPE NonStop Tandem Transaction Logs

HPE NonStop Tandem represents a line of fault-tolerant, high-availability servers

HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers designed for 24/7, zero-downtime operations. Originally created by Tandem Computers in 1974, the architecture is now owned by Hewlett Packard Enterprise (HPE) and supports mission-critical workloads like banking and finance. 

Key Aspects of HPE NonStop (Tandem):

  • Continuous Availability: Designed to eliminate single points of failure with 100% fault tolerance.
  • Architecture: Initially used a proprietary Tandem T/16 design; modern systems are based on HPE Integrity/x86 architectures.
  • Operating System: Traditionally runs the Guardian OS, which handles the system’s specialized, continuous processing capabilities.
  • Evolution: Founded by James Treybig in 1974, Tandem was acquired by Compaq in 1997, which then merged with HP in 2002.
  • Applications: Ideal for transactional applications requiring strict data integrity and real-time processing.
  • Modern Platforms: Current systems include HPE NonStop Compute NS9 X5 and NS5 X5. 

The systems are still widely used today for mission-critical applications that cannot afford to be offline. 

HPE NonStop (formerly Tandem) represents a line of fault-tolerant, high-availability servers.

Connect : HPE Nonstop Ecosystem – formerly NSK, Tandem, Himalaya

Connect’s Influencer of the Year Program

Connect : HPE Nonstop Ecosystem – formerly NSK, Tandem, Himalaya

HP HPE NonStop NSK Himalaya Tandem Date Timeline

The HP NonStop (originally Tandem) timeline spans over 50 years of evolution in fault-tolerant computing, beginning with the vision of James Treybig and transitioning through several major corporate owners. 

Founding and Initial Growth (1974–1980s)

  • 1974: Tandem Computers Incorporated is founded by James (Jimmy) Treybig in Cupertino, CA.
  • 1976: The first NonStop I (T/16) servers are shipped to Citibank, introducing the “fail-fast” architecture.
  • 1981: NonStop II is introduced, adding 32-bit addressing support to the 16-bit registers.
  • 1983: NonStop TXP (Tandem Extended Processor) debuts, featuring the first use of cache memory and a native Transaction Monitoring Facility (TMF).
  • 1986: NonStop VLX (Very Large eXtension) is released, introducing 32-bit data paths and the first fault-tolerant SQL database, NonStop SQL.
  • 1987: NonStop CLX is launched as a low-cost, office-ready minicomputer system.
  • 1989: NonStop Cyclone is introduced for high-end mainframe workloads, alongside the Integrity line of Unix-based servers. 

Architecture Transitions (1990s–2000s)

  • 1991: Cyclone/R (CLX/R) marks the start of the TNS/R migration to MIPS microprocessors.
  • 1993: NonStop Himalaya K-series is released, featuring native-mode Guardian OS on MIPS R4400 processors.
  • 1994: Open System Services (OSS) adds a POSIX-compliant environment to the NonStop Kernel.
  • 1997: NonStop Himalaya S-Series introduces ServerNet, replacing older bus technologies with high-speed point-to-point connections.
  • 1997: Compaq acquires Tandem Computers to bolster its high-end enterprise server offerings.
  • 2002: Hewlett-Packard (HP) acquires Compaq, bringing Tandem technology under the HP banner as the NonStop Enterprise Division.
  • 2005: The HP Integrity NonStop (TNS/E) series is launched, migrating the architecture from MIPS to Intel Itanium processors. 

The Modern Era (2010s–Present)

  • 2014: NonStop X (TNS/X) is introduced, transitioning the platform to standard Intel x86-64 processors.
  • 2015: HP splits into HP Inc. and Hewlett Packard Enterprise (HPE); the NonStop line moves to HPE.
  • 2017: Virtualized NonStop (vNS) is introduced, allowing the system to run in software-defined data centres and cloud environments.
  • 2020: HP ends sales of Itanium-based systems in July, completing the transition to the x86 platform.
  • 2024: The NonStop community celebrates 50 years of Tandem/NonStop technology. 
HP HPE NonStop NSK Himalaya Tandem Date Timeline

HPE NonStop Tandem NonStop – Guardian Principles Course – 1993 – High Wycombe

HPE NonStop Tandem NonStop – Guardian Principles Course – 1993 – High Wycombe

Career, Insider Technologies Limited, ITL – 1995 to 2013 as HPE NonStop Tandem specialist and Product Manager

Career, Insider Technologies Limited, ITL – 1995 to 2013 as HPE NonStop Tandem specialist and Product Manager

HPE NonStop previously Tandem Computers

NonStop is a series of server computers introduced to market in 1976 by Tandem Computers Incorporated,[1] beginning with the NonStop product line.[2] It was followed by the Tandem Integrity NonStop line of lock-step fault-tolerant computers, now defunct (not to be confused with the later and much different Hewlett-Packard Integrity product line extension). The original NonStop product line is currently offered by Hewlett Packard Enterprise since Hewlett-Packard Company’s split in 2015. Because NonStop systems are based on an integrated hardware/software stack, Tandem and later HPE also developed the NonStop OS operating system for them.

NonStop systems are, to an extent, self-healing. To circumvent single points of failure, they are equipped with almost all redundant components. When a mainline component fails, the system automatically falls back to the backup.

These systems can be used by banks, stock exchanges, payment applications, retail companies, energy and utility services, healthcare organizations, manufacturers, telecommunication providers, transportation, and other enterprises requiring extremely high uptime.

History

Originally introduced in 1976 by Tandem Computers Inc., the line was later owned by Compaq (from 1997), Hewlett-Packard Company (from 2003)[3] and Hewlett Packard Enterprise (since 2015). In 2005, the HP Integrity “NonStop i” (or TNS/E) servers, based on Intel Itanium microprocessors, was introduced. In 2014, the first “NonStop X” (or TNS/X) systems, based on Intel x86-64 processors, were introduced. Sales of the Itanium-based systems ended in July 2020.[4]

Early NonStop applications had to be specifically coded for fault tolerance. That requirement was removed in 1983 with the introduction of the Transaction Monitoring Facility (TMF), along with Pathway transaction management software and SCOBOL applications (or, later, NonStop Tuxedo transaction management software), which handles the various aspects of fault tolerance on the system level.

Software

NonStop OS is a message-based operating system designed for fault tolerance. It works with process pairs and ensures that backup processes on redundant CPUs take over in case of a process or CPU failure. Data integrity is maintained during those takeovers; no transactions or data are lost or corrupted.

The operating system as a whole is branded NonStop OS and includes the Guardian layer, which is a low-level component of the operating system and the Open System Services (OSS) personality which runs atop this layer, which implements a Unix-like interface for other components of the OS to use.

The operating system and application are both designed to support the fault tolerant hardware. The operating system continually monitors the status of all components, switching control as necessary to maintain operations. There are also features designed into the software that allow programs to be written as continuously available programs. That is accomplished using a pair of processes where one process performs all the primary processing and the other serves as a “hot backup”, receiving updates to data whenever the primary reaches a critical point in processing. Should the primary stop, the backup steps in to resume execution using the current transaction.[5]

The systems support relational database management systems like NonStop SQL and hierarchical databases such as Enscribe.

Languages supported include Java,[6] C, C++,[6] COBOL, SCOBOL (Screen COBOL), Transaction Application Language (TAL), etc. It uses the scripting and job control language TACL (Tandem Advanced Command Language), and is written in TAL and C.

Hardware

The HPE Integrity NonStop computers are a line of fault-tolerant, message-based server computers based on the Intel Xeon processor platform,[4] and optimized for transaction processing. Average availability levels of 99.999% have been observed.[7] NonStop systems feature a massively parallel processing (MPP) architecture and provide linear scalability. Each CPU runs its own copy of the OS, and systems can be expanded up to over 4000 CPUs. This is a shared-nothing architecture—a “share nothing” arrangement also known as loosely coupled multiprocessing.

Due to the integrated hardware/software stack and a single system image for even the largest configurations, system management requirements for NonStop systems are rather low. In most deployments there is just a single production server, not a complex server farm.

Most customers also have a backup server in a remote location for IT disaster recovery. There are standard products to keep the data of the production and the backup server in sync, for example, HPE’s Remote Database Facility (RDF),[8] hence there is fast takeover and little to no data loss also in a disaster situation with the production server being disabled or destroyed.

HP also developed a data warehouse and business intelligence server line, HP Neoview, based on the NonStop line. It acted as a database server, providing NonStop OS and NonStop SQL, but lacked the transaction processing functionality of the original NonStop systems. The line was retired, and no longer marketed, as of 24 January 2011.[9]

See also

HPE NonStop Tandem Enscribe Database

Enscribe is the native hierarchical database in the commercial HP NonStop (Tandem) servers. It is designed for fault tolerance and scalability and is currently offered by Hewlett Packard Enterprise.

The product was originally developed by Tandem Computers. Tandem was acquired by Compaq in 1997. Compaq was later acquired by Hewlett-Packard in 2002. When Hewlett-Packard split in 2015 into HP Inc. and Hewlett Packard Enterprise, Enscribe and the rest of the NonStop product line went to Hewlett Packard Enterprise.

The product primarily is used for online transaction processing and is tailored for organizations that need high availability and scalability for their database system. Typical users of the product are stock exchanges, telecommunications, POS, and bank ATM networks.

Somewhat similar to Record Management Services on OpenVMS platforms, some Enscribe features are:[1]

  • Five disk file structures: unstructured, key-sequenced, queue, entry-sequenced, and relative
  • Partitioned (multiple-volume) files
  • Multiple-key access to records
  • Relational access among files (where a field value from one file is used as a key to access a data record in another file)
  • Optional automatic maintenance of all keys
  • Optional key compression in key-sequenced data or index blocks
  • Support of transaction auditing through the Transaction Management Facility (TMF/MP). TMF is the main functional component of the NonStop Transaction Manager/MP product.
  • Optional compression of audit-checkpoint records
  • Record level locking and file level locking
  • Cache buffering
  • Optional sequential block buffering
  • Waited and Nowaited I/Os (multi-threading of I/O calls by the programmer)[2]

The NonStop OS Guardian APIs or the utility FUP (File Utility Program) can be used to work with Enscribe files.

A “convert” utility was provided by Tandem to aid in converting Enscribe files to NonStop SQL files, when desired.[3]

Many of the applications developed in HP NonStop servers (often critical ones) run on Enscribe databases.

History

Enscribe is designed to run effectively on parallel computers, adding functionality for distributed data, distributed execution, and distributed transactions.

First released in the early 1980s, and initially carrying an added charge until it was included with the operating system, the product became one of the few hierarchical data base systems that scales almost linearly with the number of processors in the machine: adding a second CPU to an existing server almost exactly doubled its performance.

See also

HPE NonStop Tandem SQL/MP

NonStop SQL is a commercial relational database management system that is designed for fault tolerance and scalability, currently offered by Hewlett Packard Enterprise. The latest version is SQL/MX 3.4.

NonStop SQL

Original author, Tandem Computers

Developer, HPE

Initial release, 1987

Stable release, 3.4

Operating system, NonStop OS

Platform, NonStop

Standard, ANSI standard (NonStop SQL/MX)

Available in :-

NonStop COBOL, NonStop SCOBOL, NonStop Java, NonStop C, NonStop C++, Transaction Application Language (TAL), pTAL, epTAL

Type, DBMS

License, Proprietary

The product was originally developed by Tandem Computers. Tandem was acquired by Compaq in 1997. Compaq was later acquired by Hewlett-Packard in 2002. When Hewlett-Packard split in 2015 into HP Inc. and Hewlett Packard Enterprise, NonStop SQL and the rest of the NonStop product line went to Hewlett Packard Enterprise.

The product primarily is used for online transaction processing and is tailored for organizations that need high availability and scalability for their database system. Typical users of the product are stock exchanges, telecommunications, POS, and bank ATM networks.[1]

History

NonStop SQL is designed to run effectively on parallel computers, adding functionality for distributed data, distributed execution, and distributed transactions.

First released in 1987, a second version in 1989[2] added the ability to run queries in parallel, and the product became fairly famous for being one of the few systems that scales almost linearly with the number of processors in the machine: adding a second CPU to an existing NonStop SQL server almost exactly doubled its performance.

The second version added /MP to its name, for Massively Parallel. A third version, NonStop SQL/MX, created a product that was more ANSI SQL compliant than its predecessor. NonStop SQL/MX has shipped on the NonStop platform since 2002, and can access tables created by NonStop SQL/MP, although only “Native SQL/MX tables” offer ANSI compliance and many “Oracle-like” enhancements. The HP Neoview business intelligence platform was built using NonStop SQL as its origins. NonStop SQL/MX is HP’s only OLTP database product.

Parts of the Neoview code base were open sourced in 2014 under the name Trafodion, which is now a top-level Apache project.

See also

My HPE Tandem NonStop SQL/MP experience.

COBOL85 programming language on HPE NonStop systems (formerly Tandem NonStop)

“COBOL85 nonstop” refers to the use of the COBOL85 programming language on HPE NonStop systems (formerly Tandem NonStop). The HPE NonStop platform is known for its fault-tolerant, continuous availability architecture, often used for critical, large-scale transaction processing. 

Key aspects of COBOL85 on NonStop include:

  • Platform-Specific Implementation: HPE provided a specific implementation of the 1985 COBOL standard tailored to its unique Guardian operating system and hardware architecture.
  • Mission-Critical Applications: COBOL programs on NonStop are commonly used in industries such as finance, retail, and government for applications requiring high reliability and constant uptime (the “nonstop” nature of the system).
  • Fault Tolerance: NonStop systems achieve fault tolerance through mechanisms like process pairs, and the COBOL runtime library can interact with these features. For example, a PARAM NONSTOP OFF setting in a PATHMON configuration can prevent a COBOL85 server from running as a process pair if that behavior is not desired.
  • System Integration: Programmers can call Guardian procedures and use embedded SQL/MP statements within their COBOL85 programs to interact with the system’s robust file system and database.
  • Development and Maintenance: The combination of COBOL85 and HPE NonStop utilities is a specific skill set for developers maintaining these critical legacy systems.
  • Tools and Manuals: Documentation and tools, such as the INSPECT symbolic debugger and the FUP (File Utility Program), are specific to the NonStop environment and assist with development and maintenance. 

For detailed information, users can consult the official documentation, such as the HP COBOL Manual for TNS and TNS/R Programs or other manuals available on the NonStopTools website and HPE Support portals. 

My NonStop COBOL85 programming experience.

Transaction Application Language – TAL on HP HPE Nonstop mainframes (previously Tandem)

Transaction Application Language

Programming language

Tandem TAL - Visual Studio Marketplace
TAL User Defined Language for Notepad++ | sybond/project
Transaction Application Language – TAL on HP HPE Nonstop mainframes (previously Tandem)

Transaction Application Language or TAL is a block-structured, procedural language optimized for use on Tandem hardware. TAL resembles a cross between C and Pascal. It was the original system programming language for the Tandem Computers CISC machines, which had no assembler.

Source: Wikipedia

Transaction Application Language or TAL (originally “Tandem Application Language”) is a block-structured,[1] procedural language optimized for use on Tandem (and later HP NonStop) hardware. TAL resembles a cross between C and Pascal. It was the original system programming language for the Tandem Computers CISC machines, which had no assembler.[2]

Transaction Programming Language (TAL)
ParadigmBlock-structured procedural language
DeveloperHewlett-Packard Enterprise (originally Tandem Computers)
First appearedmid 1970s
PlatformMIPS, Itanium, x86-64
OSNonStop OS
LicenseProprietary commercial software
File formatsunstructured, Enscribe, NonStop SQL/MP, NonStop SQL/MX
Dialects
TAL, pTAL, epTAL
Influenced by
ALGOL, Pascal, C

The design concept of TAL, an evolution of Hewlett-Packard‘s SPL, was intimately associated and optimized with a microprogrammed CISC instruction set. Each TAL statement could easily compile into a sequence of instructions that manipulated data on a transient floating register stack. The register stack itself floated at the crest of the program’s memory allocation and call stack.

The language itself has the appearance of ALGOL or Pascal, with BEGIN and END statements. However, its semantics are far more like C. It does not permit indefinite levels of procedure nesting, it does not pass complex structured arguments by value, and it does not strictly type most variable references. Programming techniques are much like C using pointers to structures, occasional overlays, deliberate string handling and casts when appropriate.

Available datatypes include 8-bit, 16-bit, 32-bit and (introduced later) 64-bit integers.[3] Microcode level support was available for null terminated character strings. However, this is not commonly used.

Originally the Tandem NonStop operating system was written in TAL. Much of it has since been rewritten in C and TAL has been deprecated for new development.

In the migration from CISC to RISC, TAL was updated/replaced with pTAL – compilers allowed TAL to be re-compiled into Native RISC Applications. Later, the epTAL compiler was introduced for Itanium processors.

sp/ARCHITECT-BANK – developed by a Runcorn-based software house called The Software Partnership (later acquired by Deluxe Data in 1994)

“sp/architect nonstop tandem” refers to SP/ARCHITECT-BANK, an electronic banking software that ran on the highly available, fault-tolerant Tandem NonStop servers (now part of the Hewlett Packard Enterprise, or HPE, NonStop product line). 

SP/ARCHITECT-BANK Software

  • Function: Developed as an electronic banking software package, it enabled functions like desktop access to company accounts, inter-account transfers, and bookkeeping, which was considered cutting-edge in the early 1990s.
  • Developer: The software was developed by a Runcorn-based software house called The Software Partnership (later acquired by Deluxe Data in 1994).
  • Users: Various banks, including TSB, Bank of Scotland, Rabobank, and Girofon (Denmark), used the software. 

Tandem NonStop Servers

The NonStop servers, originally from Tandem Computers Inc., are known for their extreme reliability and scalability, making them suitable for mission-critical applications in finance, telecommunications, and retail. 

Key architectural features include:

  • Fault Tolerance: The systems use redundant components (processors, storage, controllers, power supplies) with a “shared-nothing” architecture to ensure continuous operation even if a component fails.
  • Operating System: They use a proprietary, message-based operating system, the NonStop Kernel (NSK, originally Guardian), which manages fault detection and failover automatically, without human intervention.
  • Current Status: Tandem was acquired by Compaq in 1997, and Compaq was subsequently acquired by HP in 2002. The NonStop product line is now offered by Hewlett Packard Enterprise (HPE). More information is available on the HPE website. 

The Software Partnership (later acquired by Deluxe Data in 1994)

In 2013, delivered a large transaction tracking project at a retail bank in Riyadh

Retail Banking (off-shore) – in 2013, delivered a large transaction tracking project at a retail bank in Riyadh (Saudi Arabia). This involved the BASE24 Classic payment solution and the relay and optimised parsing of multiple Terabytes of tape archived POS & ATM transaction logs to a new monitoring and reporting system. Project managed the work and delivery both in Salford Quays, Manchester and locally at the bank in Riyadh.

mark whitfield wordpress_connection_HP_NonStop_to_Windows_Combined
RTLX_White_Paper+Download

HP NonStop (HPE) fault tolerant servers originally developed by Tandem Computers – Summary

My IT career between the years 1990 and 2014, involved significant programming and large projects for Tandem HP NonStop servers.

HP NonStop Tandem Computers

HP NonStop refers to the line of fault-tolerant servers and software originally developed by Tandem Computers and now owned by Hewlett Packard Enterprise (HPE). These systems are designed for continuous operation and uninterrupted transaction processing by using redundant hardware components and independent processors to automatically failover in the event of a failure, ensuring high availability for critical applications in banking, telecommunications, and healthcare. 

Origins and Evolution

  • Tandem Computers: Founded in 1974, Tandem introduced the NonStop system, a pioneering fault-tolerant computer with no single point of failure, revolutionizing continuous availability for online transaction processing. 
  • Acquisitions: Tandem Computers was acquired by Compaq in 1997, and Compaq was later acquired by Hewlett-Packard (HP) in 2001. 
  • Current Ownership: After the split of HP into Hewlett Packard Enterprise (HPE) and HP Inc. in 2015, the NonStop product line became part of HPE. 

Key Features and Uses

  • Fault Tolerance: The systems are built with redundant components, including identical processors and storage devices, allowing them to automatically detect and recover from hardware or software failures without interruption. 
  • High Availability: This fault-tolerant architecture is ideal for mission-critical applications that require constant uptime, such as financial transactions, emergency services, and large-scale banking systems. 
  • Scalability: NonStop systems are designed for scalability, able to handle large commercial workloads by adding independent processors. 
  • Dedicated Operating System: Historically, NonStop systems ran on proprietary software like the Guardian operating system and used the TAL programming language. 
  • Specialized Database: The line includes NonStop SQL (currently SQL/MX), a relational database designed for the high availability and scalability needs of these systems.