Tag: HPE NonStop

HPE NonStop Conferences Insight and Timeline by Era

The HPE NonStop community, historically rooted in Tandem Computers’ culture of openness, has held an annual gathering since the early 1980s.

Originally known as the International Tandem Users Group (ITUG) summits, the main conference evolved into the NonStop Technical Boot Camp (TBC), now organized by Connect Worldwide and heavily supported by Hewlett Packard Enterprise. 

The conference serves as the premier annual gathering for NonStop users, focusing on technical education, mission-critical applications, and networking. 

Detailed Historical Timeline (1990–2026)

The “Tandem/ITUG” Era (1990–1996)

  • Focus: Transitioning from proprietary stack machines to MIPS RISC microprocessors, introducing Open System Services (OSS).
  • 1990: Tandem reaches peak revenue; ITUG meetings focus on fault tolerance in ATM networks.
  • 1993: Introduction of NonStop Himalaya K-series using MIPS R4400 processors.
  • 1994: NonStop Kernel (NSK) extended with POSIX-compliant Unix.
  • 1995: Introduction of ServerNet, foundational for future x86 architectures. 

The Compaq & HP Transition Era (1997–2014) 

  • Focus: Integration into larger portfolios, migration from MIPS to Intel Itanium (TNS/E).
  • 1997: Compaq acquires Tandem. ITUG summits begin navigating the new corporate structure.
  • 2003: HP acquires Compaq. NonStop conferences become key components of HP’s high-end mission-critical offerings.
  • 2005: Introduction of HP Integrity NonStop i servers based on Intel Itanium.
  • 2008: Connect Worldwide (independent user group) takes over, revitalizing the “Technical Boot Camp” name.

The HPE NonStop X & Virtualization Era (2015–2019) 

  • Focus: Migration to x86-64 (NonStop X), Virtualization (vNonStop), and cloud integration.
  • 2015: Formation of Hewlett Packard Enterprise (HPE). Focus shifts to modernized “NonStop X” systems.
  • 2016: vNonStop demoed at TBC, allowing fault-tolerant systems in virtual machines.
  • 2017: TBC highlights AI and cybersecurity, reflecting modern enterprise needs.
  • 2019: Discussions around “NonStop-as-a-Service” (XaaS) and GreenLake integration. 

The AI & 50th Anniversary Era (2020–2026)

  • Focus: Hybrid Cloud, Artificial Intelligence, 50th Anniversary of NonStop.
  • 2020: TBC goes virtual, with high attendance from a global community.
  • 2022: Continued focus on XaaS (everything as a service).
  • 2023-2024: Emphasis on cyber resilience, SQL improvements, and integration with modern DevOps tools.
  • 2025/2026: HPE NonStop 50th Anniversary. Conferences focus on AI-driven transformation, cybersecurity, and the new business track. 

Conference Insights and Evolution

  • The “Beer Bust”: A tradition started in the early days of Tandem, now a staple social event at the TBC to foster community and open communication.
  • Format: The NonStop TBC typically features 4 days of technical sessions, user case studies, and partner exhibitions (e.g., XYPRO, NTI).
  • Regional Events: Alongside the main TBC, regional events (e.g., MexTUG) occur throughout the year.
  • Key Themes: Uninterrupted performance, database integrity, and migration to x86/cloud. 

NonStop TBC 2026 is scheduled for Sept 14–18 in Orlando, FL. 

The history of Tandem Computers (now HPE NonStop) conferences is a nearly 50-year chronicle of community-driven knowledge sharing, evolving from the Tandem User’s Group (TUG) in 1978 to the modern HPE NonStop Technology & Business Conference (TBC).

These events have served as the primary venue for sharing best practices on fault tolerance, high availability, and mission-critical application design, bridging the gap between Tandem’s founding in 1974 and HPE’s current virtualized NonStop systems. 

Detailed Historical Conference & Product Timeline (1970s–Present)

  • 1974–1979: The Founding Era
    • 1974: Jimmy Treybig founds Tandem Computers in Cupertino, CA, with a mission to create fault-tolerant systems for online transaction processing (OLTP).
    • 1976: First Tandem/16 (T/16) system shipped to Citibank, initiating the NonStop era.
    • 1978: Creation of the Tandem User’s Group (TUG) in San Jose, CA, as the foundational user community. Introduction of the Encompass database management system.
  • 1980–1989: Growth and Expansion
    • 1981: TUG is renamed the International Tandem User’s Group (ITUG), reflecting global growth. Introduction of NonStop II.
    • 1983: Introduction of the Tandem NonStop Extended Processor (TXP) and Guardian B-Series OS.
    • 1984: Formation of the British Isles Tandem User Group (BITUG).
    • 1985–1986: Introduction of the entry-level NonStop EXT system.
    • 1987-1988: Large-scale adoption of Tandem systems by international financial institutions and growing ITUG conference attendance, often characterized by strong community spirit.
    • 1989: Release of NonStop Cyclone and relational database software, challenging IBM’s dominance in transaction processing.
  • 1990–1999: The Move to Open Systems & Acquisition
    • 1990: Announcement of the Integrity S2 line for Unix-based fault tolerance.
    • 1991: Release of Cyclone/R (CLX/R) based on MIPS R3000, signaling a move away from custom proprietary CPUs.
    • 1993: Launch of the Himalaya K-series, supporting the MIPS R4400 and native mode NSK.
    • 1994-1995: Introduction of Open System Services (OSS), extending the NonStop Kernel to include a Unix-like POSIX environment.
    • 1997: Compaq acquires Tandem for $3 billion. Tandem releases the NonStop Himalaya S-Series, introducing the ServerNet interconnect technology.
  • 2000–2010: Compaq-HP Merger and Modernization
    • 2001: Hewlett-Packard merges with Compaq, taking over the NonStop product line and initiating a migration to Intel Itanium processors (TNS/E).
    • 2001: ITUG is renamed to “Compaq Users Group” before transitioning to the combined Connect community group.
    • 2002: Formation of a Tandem Alumni Group, celebrating the unique culture.
    • 2005: Introduction of Integrity NonStop servers, fully leveraging Intel’s Itanium architecture.
  • 2011–Present: HPE NonStop and Cloud Era
    • 2014: Formation of HPE (Hewlett Packard Enterprise).
    • 2015: Introduction of NonStop X, moving from Itanium to Intel x86-64 processors.
    • 2023-2024: Celebration of 50 years of Tandem/NonStop. The platform embraces virtualization and converged infrastructure.
    • 2025/2026: NonStop TBC 2026 is scheduled for Sept 15-17 in Orlando, FL, focusing on AI integration, modernization, and hybrid cloud. 

Key Conference Themes & Insights (2026 Perspective)

  • Legacy + Future: Current TBC conferences balance supporting existing high-value transaction applications with modernization approaches like REST APIs, Java, and DevOps.
  • Virtualization & Cloud: A major focus is deploying NonStop as virtualized instances (vNS) and integrating with public/hybrid clouds.
  • Community Continuity: Despite multiple mergers (Tandem HPE), the user community has remained tight-knit, with organizations like Connect hosting the NonStop TBC.
  • Continuous Availability: The core focus remains 100% uptime, with sessions analyzing how to achieve it in modern containerized environments.

HPE NonStop ViewSys Overview and Timeline by Era

ViewSys is a legacy, interactive system monitoring utility for HPE NonStop servers that provides real-time visibility into system resource utilization. Similar to PEEK and Measure, it allows system operators to view resource consumption as it happens, allowing for immediate analysis of the impacts of process relocations or controller path changes. 

HPE NonStop ViewSys Overview

  • Purpose: Monitors system resources, including processor utilization, I/O performance, and memory usage, on NonStop systems.
  • Key Features: Provides online viewing of system resources, allowing for quick recognition of performance bottlenecks, which helps in performance tuning.
  • Functionality: Unlike Measure, which is typically analyzed offline, ViewSys offers an interactive, live, and graphical view of system performance.
  • Operation Requirement: Runs from HPE block mode terminals or non-Stop terminal emulators, presenting average resource usage for each polling interval. 

Detailed Historic Timeline: ViewSys & NonStop Monitoring Evolution

The history of ViewSys is deeply intertwined with the development of the HPE NonStop OS and its monitoring toolkit.

Era 1: Tandem Era (The Early Days)

  • 1976: Initial Tandem NonStop System introduced; basic system monitoring is manual and console-based.
  • 1980s (Mid-late): As Transaction Monitoring Facility (TMF) and Pathway are introduced, the need for interactive monitoring grows.
  • 1990s: ViewSys becomes a key utility for operators managing massive OLTP (Online Transaction Processing) workloads. 

Era 2: Compaq/Early HP Era (The Transition)

  • 1997: Compaq Acquires Tandem.
  • 2003: HP Acquires Compaq. The monitoring focus begins to merge with Integrity-based architecture.
  • 2004: The ViewSys User’s Guide highlights ViewSys alongside PEEK and Measure, standardizing its use for interactive monitoring.
  • 2005: Introduction of HP Integrity “NonStop i” (TNS/E) servers using Intel Itanium processors. ViewSys adapted to monitor Itanium systems. 

Era 3: Modern HPE Era (The Modernization) 

  • 2014: First NonStop X (TNS/X) systems on x86-64 are introduced. ViewSys remains a available tool, but modernization efforts begin.
  • 2015: Hewlett Packard Enterprise (HPE) is formed.
  • 2016-2020: Shift towards Web ViewPoint Enterprise (by Idelji Corporation), which provides web-based dashboards for monitoring EMS events and system metrics.
  • 2020: Sales of Itanium-based systems end. Modern monitoring focuses heavily on NonStop X systems and virtualized environments.
  • Present: While legacy ViewSys may exist in older environments, it is largely superseded by modern GUI-based, browser-independent monitoring solutions like Web ViewPoint and Remote Analyst. 

HPE NonStop ViewSys Overview and Timeline by Era

HPE NonStop EMSDIST, Event Management Service EMS Distributor Timeline by Era

HPE NonStop EMSDIST (Event Management Service Distributor) is a critical component within the HPE NonStop operating system responsible for distributing and managing event messages (logs) generated by the system, subsystems, or applications. It is part of the Event Management Service (EMS), which is essential for fault-tolerant monitoring. 

EMS events (via EMSDIST) seen in the Reflex 80:20 application ( now Sentinel (Nonstop Monitoring) by ETI-NET)

EMSDist Overview

  • Purpose: EMSDIST reads events from an EMS collector process ($0, $ZLOG, etc.) or a collector logfile, filters them based on user criteria, and sends them to a user-specified destination (such as a terminal, printer, or another file).
  • Key Functionality: It enables both real-time monitoring and historical analysis of events.
  • Event Handling: It handles EMS messages, including those generated by the EMS subsystem itself (messages 513-999) and those from EMS distributors (messages > 1000).
  • Integration: Often used in conjunction with TACL (Tandem Advanced Command Language) for automated event management scripts. 

Detailed Historic Timeline and Evolution

EMSDIST has evolved alongside Tandem / Compaq / HPE NonStop systems, transitioning from basic console management to complex distributed management systems. 

1. The Tandem Guardian Era (Late 1970s – 1980s)

  • Context: The emergence of Tandem NonStop systems focused on continuous availability.
  • EMS Origins: Initial event handling was largely via console messages. As systems grew, the need to manage logs across multiple processors led to early Event Management Service components.
  • Role of EMSDist: Early distributors primarily moved messages from local collectors to a central console or tape log.

2. The D-Series & TMF Era (1990s)

  • Context: Introduction of sophisticated transaction monitoring and distributed databases.
  • 1996: A significant EMS Reference Summary was released (PN 114754), formalizing the structure of EMS collectors and distributors.
  • Capabilities: EMSDIST became capable of filtering high-volume events, separating critical errors from warning messages (513-1019).
  • Evolution: Began integrating with the Distributed Systems Management (DSM) suite for better network-wide event visibility. 

3. The Compaq & Integrity (J-Series/H-Series) Era (2000s – 2010s)

  • Context: Shift from MIPS-based processors to Intel Itanium (Integrity) servers.
  • 2003-2005: Integration with Windows-based management systems (DSM/NOW) and improvements to the Multi Event Viewer (MEV).
  • 2014: HP Integrity NonStop Operations Guides emphasized using EMSDIST alongside modern tools like OSM (Open System Management) Event Viewer, especially for H-Series and J-Series systems.
  • Key Capability: Improved handling of large logs, with better time-based querying (TIME and STOP options) for auditing and troubleshooting. 

4. The HPE NonStop X & Modern Era (2015 – Present)

  • Context: Adoption of x86 architecture and cloud-ready systems (L-Series).
  • 2015: HPE takes over the portfolio, accelerating integration with HPE InfoSight for AI-driven log analysis.
  • Modernization: While EMSDIST remains, modern environments heavily leverage NS Software Essentials and third-party tools for advanced analytics.
  • Continued Importance: EMSDIST remains essential for analyzing historical logs via the LOGFILE option, especially when dealing with cold-standby or restored logs from tape/disk. 

Key Functional Milestones

  • Message Categorization: Formalization of messages 513-999 (collectors) and >1000 (distributors) for structured analysis.
  • Filtering Efficiency: Implementation of complex FILTER parameters allowed operators to filter events by process, user, or time.
  • Logfile Access: The ability for EMSDIST to process archived or older LOGFILE entries independently of the live $0 collector.
  • Template Support: Ability to use specific =_EMS_TEMPLATES for customizable output formatting. 

HPE NonStop EMSDIST, Event Management Service Distributor Timeline by year

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline

The HPE NonStop Data Definition Language (DDL) dictionary is a specialized subsystem used to define and manage data objects for Enscribe files and translate those definitions into source code for various programming languages. It serves as a central repository for metadata, ensuring consistent data structures across applications written in C, COBOL, TAL, or TACL. 

Program Summary

The DDL dictionary program functions as a metadata management tool. Key capabilities include: 

  • Centralised Definition: Defines records, fields, and file attributes in a hierarchical structure.
  • Code Generation: Translates DDL definitions into language-specific source code (e.g., COBOL copybooks or C headers).
  • Dictionary Maintenance: Allows users to create, examine, and update dictionaries to reflect changes in data structures.
  • Interoperability: Modern tools like Ddl2Bean convert dictionary files into Java Beans or XML, enabling cross-language and cross-platform use. 

Future Outlook

The future of HPE NonStop DDL focuses on modernisation and integration rather than replacement. 

  • Data Virtualization: Integration with AI factories and object storage platforms to expose legacy metadata in open-table formats like Apache Iceberg.
  • API Centricity: Enhancements to the NonStop API Gateway will likely use DDL metadata to automate REST/JSON service orchestration.
  • Real-time Analytics: Native streaming of NonStop data into platforms like Kafka, using DDL definitions to map real-time changes into analytics-ready formats. 

Internet Links & Manuals

HPE NonStop Data Definition Language (DDL) dictionary overview and timeline

HPE NonStop PATHCOM, interactive management interface, Pathway transaction processing environment

HPE NonStop PATHCOM is the interactive management interface for the Pathway transaction processing environment. It allows administrators to configure, monitor, and control PATHMON-governed objects such as serverclasses, TCPs (Terminal Control Processes), and links. 

Historical Timeline: The Evolution of Pathway & PATHCOM

The history of PATHCOM is inseparable from the Tandem NonStop platform, which pioneered fault-tolerant Online Transaction Processing (OLTP). 

The Tandem Era (1974 – 1997) 

  • 1974 – 1976: Tandem Computers is founded. The first NonStop I system ships in 1976.
  • 1983: Tandem introduces Pathway software alongside the Transaction Monitoring Facility (TMF). This milestone removes the requirement for developers to manually code fault tolerance into applications, as the Pathway infrastructure (managed via PATHCOM) handles it automatically.
  • Early 1990s: The platform migrates from proprietary stack machines to MIPS RISC processors (TNS/R architecture). PATHCOM evolves to manage more complex distributed environments.
  • 1994: Open System Services (OSS) is introduced, allowing NonStop to support a Unix-like POSIX environment. 

The Compaq & Early HP Era (1997 – 2014) 

  • 1997: Compaq acquires Tandem.
  • 2002: HP merges with Compaq.
  • 2005: Migration from MIPS to Intel Itanium (Integrity NonStop) begins.
  • 2010s: Pathway evolves into HPE NonStop Pathway with TS/MP (Transaction Services/Massive Parallelism), enabling near-linear scalability for massive OLTP workloads. 

The Modern HPE Era (2014 – Present)

  • 2014: NonStop X is introduced, migrating the architecture to Intel x86-64 processors.
  • 2015: Hewlett-Packard splits; the platform continues under Hewlett Packard Enterprise (HPE).
  • 2020 – 2024: Focus shifts toward virtualisation and hybrid cloud. Modern Pathway/TS environments now support massive scaling up to 24,480 cores in a single system image.
Summary of PATHCOM Functionality

Future of NonStop Pathway

HPE’s roadmap for NonStop focuses on integrating mission-critical reliability with modern data centre technologies:

  • Modernisation: Support for Kubernetes Helm deployments and cloud-native frameworks.
  • Hardware Advancements: New NS9 X5 and NS5 X5 platforms offer double the memory capacity and 2x faster system interconnects.
  • Open Integration: Continued emphasis on open application development environments and open-source frameworks.
  • Hybrid Cloud: Positioning NonStop as a key component of HPE GreenLake for mission-critical workloads in the cloud.

HPE NonStop PATHCOM, interactive management interface, Pathway transaction processing environment

HPE NonStop Spoolcom subsystem Spooler Command Language program Overview and Timeline

The HPE NonStop Spoolcom (Spooler Command Language) program is the administrative interface for managing the Spooler subsystem on HPE NonStop systems. It allows operators to configure, monitor, and control print jobs, collectors, and print processes. 

Program Summary

  • Purpose: Used to define and manage spooler objects such as collectors, devices, and jobs.
  • Key Functions: Starting/stopping the spooler, modifying device attributes, and controlling job states (e.g., hold, release, delete).
  • Architecture: Operates within the Guardian environment, communicating with the Spooler supervisor process to maintain 24/7 fault-tolerant printing operations. 

Historical Timeline by Era

1. The Tandem Era (1974–1997) 

  • 1976: Introduction of the Tandem NonStop system; basic spooling capabilities were essential for early OLTP (Online Transaction Processing).
  • 1980s: The Spooler evolved to handle complex routing and multiple collectors to support growing enterprise needs.
  • 1997: Spooler D41 released, providing stable management for the MIPS-based architecture. 

2. The Compaq & Early HP Era (1997–2014)

  • 1999–2000: Release of Spooler D46, enhancing device ownership and virtual device support.
  • 2001–2002: Spooler D48 released during the transition to the HP Integrity NonStop (Itanium) platform.
  • 2012: Major updates to Spooler D48 to support H01 and H02 RVUs, improving scalability for high-end systems. 

3. The Modern HPE Era (2014–Present)

  • 2014: NonStop X (x86-64) introduced. Spoolcom adapted to support the new architecture and virtualised environments.
  • 2018–2020: Focus shifted toward modernised interfaces. While Spoolcom remains the CLI standard, graphical alternatives like MultiBatch began gaining traction for batch management.
  • 2023–2024: Continued integration with HPE GreenLake and hybrid cloud models, ensuring spooling services are available in private cloud deployments. 

Futures and Roadmap

  • Modernisation: HPE is pushing toward “modernisation through tradition,” which includes better integration of legacy tools like Spoolcom with modern DevSecOps and cloud-native frameworks.
  • Kernel-Level Threading (KLT): Future updates aim to leverage KLT to improve the performance and scale-up capabilities of management processes.
  • Data-Centric Security: Integration with security platforms like TAMUNIO for field-level tokenization ensures that printed data remains compliant with PCI DSS 4.0 and GDPR. 

Useful Resources

HPE NonStop Spoolcom subsystem Spooler Command Language program – Overview and Timeline

Richard Buckle of Pyalla Technologies, is a thought leader in the HPE NonStop community

Richard Buckle, founder of Pyalla Technologies, is a prominent thought leader in the HPE NonStop community known for his “Real Time View” column. His work provides a detailed chronological perspective on the platform’s evolution from its Tandem origins to modern cloud-native implementations. 

The Tandem Era: Foundations (1974 – 1997)

This era established the core architecture of fault tolerance and “non-stop” processing. 

  • 1974: Tandem Computers is founded; the first “NonStop” system is commissioned.
  • 1970s – 1980s: The platform gains dominance in financial services, telco, and healthcare.
  • 1996: Managed service models begin for Tandem users, with firms like Tandem Computer Management (TCM) winning major contracts like Bank of Scotland. 

The Compaq & Early HP Era: Transition (1997 – 2013)

A period of shifting corporate ownership and the end of the original Cupertino campus era. 

  • 1997: Compaq acquires Tandem Computers.
  • 2002: HP acquires Compaq, bringing NonStop into the HP Enterprise fold.
  • 2008: The official end of the Cupertino Tandem campus as NonStop teams move to other facilities. 

The X86 & Virtualization Era: Modernization (2013 – 2023)

Buckle documented the massive shift from proprietary hardware to industry-standard Intel x86 architecture. 

  • 2013: Announcement at NonStop TBC that the platform will support Intel x86.
  • 2014 – 2015: Launch of HPE Integrity NonStop X, utilizing InfiniBand and x86 architecture.
  • 2016: Demonstrations of Virtual NonStop (vNonStop), moving the platform toward software-defined infrastructure.
  • 2020 – 2021: Focus shifts to hybrid cloud and containerized environments. 

The 50th Anniversary & AI Era: Resilience (2024 – 2026+)

Current columns focus on “Business Resilience” and the integration of AI into mission-critical systems. 

Richard Buckle of Pyalla Technologies, is a thought leader in the HPE NonStop community

Real Time View

HPE NonStop architecture overview and technical commentary and approach by era and year

The HPE NonStop architecture is defined by its “shared-nothing” design, where every hardware and software component is redundant and operates independently to ensure 100% operational continuity. For over 40 years, it has evolved through four distinct hardware eras while maintaining upward software compatibility.

1. The Tandem Era (1974–1997): Proprietary Foundations 

  • Architecture Approach: Founded by James Treybig, Tandem introduced the first commercial fault-tolerant system using a proprietary 16-bit stack-based architecture.
  • Key Technical Milestones:
    • 1976 (NonStop I/T16): Introduced the Dynabus, a custom inter-processor backplane, and the Guardian OS, which used message-passing instead of shared memory to isolate faults.
    • 1981–1983 (NonStop II & TXP): Introduced 32-bit addressing and the Transaction Monitoring Facility (TMF), which allowed applications to be fault-tolerant without specialized coding.
    • 1986–1989 (VLX & Cyclone): Scaled to the mainframe market with ECL gate-array chips and the first fault-tolerant relational database, NonStop SQL. 

2. The MIPS Era (1991–2004): Migration to RISC

  • Architecture Approach: To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while emulating the original instruction set for compatibility.
  • Key Technical Milestones:
    • 1991 (Cyclone/R): The first MIPS-based system.
    • 1997 (Himalaya S-Series): Replaced Dynabus with ServerNet, a high-speed system interconnect that later evolved into the industry-standard InfiniBand.
    • Ownership Shift: Compaq acquired Tandem in 1997, and HP merged with Compaq in 2002. 

3. The Itanium Era (2005–2013): HP Integrity NonStop 

  • Architecture Approach: Branded as Integrity NonStop (NonStop i), this era moved the platform to Intel Itanium processors.
  • Key Technical Milestones:
    • 2005 (NS-series/J-series): Focused on “NonStop Advanced Architecture” (NSAA), leveraging standard HP server components to lower costs while maintaining Availability Level 4 (AL4).
    • Technical Commentary: While powerful, the reliance on Itanium’s EPIC architecture eventually limited growth as the industry consolidated around x86-64. 

4. The Modern HPE Era (2014–Present): x86-64 & Virtualization 

  • Architecture Approach: Shifted to standard Intel x86-64 processors (NonStop X), fully decoupling the software stack from proprietary hardware.
  • Key Technical Milestones:
    • 2014 (NonStop X/TNS/X): Introduced the L-series operating system. The architecture transitioned to a standard InfiniBand fabric for inter-processor communication.
    • 2017–2020 (vNS): Launched Virtualized NonStop (vNS), allowing the environment to run on standard hypervisors like VMware, bringing fault tolerance to private and hybrid clouds.
    • 2025 (NS9 X5): Modern systems now support up to 8 TB of RAM and are integrated into the HPE GreenLake consumption-based cloud model. 
  • Summary of Architectural Evolution