HPE NonStop Tandem Programming Languages and Development Timeline

The development of programming languages on the HPE NonStop platform (originally founded as Tandem Computers) is tightly bound to its architectural hardware transitions: from custom CISC stack machines to MIPS RISC, Intel Itanium, and eventually standard Intel x86-64 infrastructures.


Detailed List of NonStop Programming Languages

1. Core Proprietary & System Languages

  • TAL (Transaction Application Language): The foundational system programming language for Tandem. It is a block-structured, machine-dependent procedural language designed to compile directly into highly efficient machine instructions. It features ALGOL/Pascal-like syntax but implements C-like semantics, structural pointers, and weak data typing.
  • pTAL & epTAL: Specialized evolutions of TAL. Rather than rewriting legacy codebases from scratch during architecture shifts, pTAL was introduced to compile existing TAL code natively into MIPS RISC architectures. Later, epTAL was developed to target Intel Itanium microprocessors.
  • TACL (Tandem Advanced Command Language): A built-in command interpreter and interpreted scripting language. It functions like a Unix Bash shell but features highly complex macro capacities used to orchestrate system configurations, monitor processes, and automate failover procedures.

2. Enterprise & Enterprise Legacy Languages

  • COBOL85 (and older COBOL74): The undisputed workhorse of NonStop commercial workloads. HPE’s tailored implementation of the COBOL85 standard natively interfaces with the Guardian OS. It allows programmers to embed SQL/MP statements and program fault-tolerant Process Pairs through HPE NonStop Pathway (TS/MP).
  • SCOBOL (Screen COBOL): A specialized, high-level structural derivative of COBOL utilized exclusively to build blocks for character-cell terminal interfaces (such as the 6530 terminal environments) running within Pathway architectures.
  • NonStop SQL (SQL/MP and SQL/MX): While technically a database system, its embedded syntax acts as a declarative language integrated into C and COBOL. SQL/MP works with the legacy Guardian file system, while SQL/MX brings ANSI-compliant SQL closely bound with the Open System Services (OSS) environment.

3. Standard Mainstream Languages

  • C & C++: Heavily introduced during the RISC transition to allow software portability. Mainstream development on modern NonStop systems uses standard C/C++ cross-compilers. They run in either the native fault-tolerant Guardian personality or the standard POSIX-compliant Open System Services (OSS) environment.
  • Java: A first-class language layer deployed natively on NonStop. HPE optimizes the Java Virtual Machine (JVM) to scale across multi-CPU shared-nothing frameworks, allowing modern enterprise web apps to run with out-of-the-box system availability.

4. Modern Open-Source Options

  • Python, Go, & JavaScript (Node.js): Modern procedural and script utilities provided by HPE. These environments leverage the OSS POSIX platform layer, running modern DevOps orchestration, microservices, and hybrid-cloud pipelines alongside the native database engines.

Detailed Timeline Breakdown by Era and Year

The evolution of NonStop languages maps directly across distinct engineering ownership eras.

The Proprietary Foundation Era (Tandem Computers: 1974–1989)

  • 1976: Tandem ships the original Tandem/16 (NonStop I). TAL is the only available language on the platform. The entire Guardian Operating System is written completely in TAL.
  • 1981: The NonStop II hardware is introduced. Tandem expands language support to include COBOL74, FORTRAN, and BASIC to attract mainstream banking clients.
  • 1983: Tandem releases the Transaction Monitoring Facility (TMF) and Pathway application management software. SCOBOL is introduced alongside them to program secure terminal entry interfaces.
  • 1985: TACL is deployed, completely modernizing the command line shell ecosystem with scalable macros and structured operational control.
  • 1986: Tandem launches NonStop SQL, the first linearly scalable, fault-tolerant relational database engine. Embedded SQL syntax is integrated directly into TAL and COBOL compilers.
  • 1988: Compilers undergo a major update to natively support the newly established COBOL85 standard, which quickly replaces COBOL74 for all mission-critical banking transactions.

The Open Systems & Hardware Transition Era (Compaq: 1990–2001)

  • 1991: Hardware migrates from CISC stacks to MIPS RISC architectures with systems like the Cyclone/R. To protect client software assets, Tandem delivers the pTAL compiler to translate TAL source code into native RISC binaries.
  • 1995: Tandem introduces Open System Services (OSS), a POSIX-compliant UNIX subsystem running over the Guardian kernel. This brings full-scale, native native compliance for standard ANSI C and C++ programming.
  • 1997: Compaq acquires Tandem Computers. Engineering shifts heavily toward implementing Java on NonStop, targeting cross-platform, enterprise internet-banking codebases.
  • 2000: NonStop SQL/MX is released. It allows developers to use embedded SQL statements within standard C, C++, and emerging Java applications inside the OSS runtime environment.

The Corporate Alignment & Itanium Era (Hewlett-Packard: 2002–2014)

  • 2002: HP merges with Compaq. Java is designated as a first-class citizen on the platform, receiving deeper optimization to tie into native clusters seamlessly.
  • 2005: HP releases the Integrity “NonStop i” servers, moving processors away from MIPS onto Intel Itanium architectures. The epTAL compiler is rolled out alongside standard C/C++ updates to seamlessly compile older environments onto Itanium.
  • 2011: Open-source scripting engines, including early ports of modern Python, are introduced to the OSS environment, easing the system-management burden for engineers unfamiliar with legacy TACL.

The Modern Enterprise Era (Hewlett Packard Enterprise: 2015–2026)

  • 2015: HP splits, and the platform transitions to HPE. Standard Intel x86-64 hardware dominates with the NonStop X architecture. Compilers utilize an standard GCC/LLVM-based back end, allowing normal Linux/Unix C++ programs to build on NonStop with minimal alteration.
  • 2020: Sales of Itanium systems officially terminate. Legacy languages like TAL are deprecated for new software creation but are preserved to support older, foundational logic.
  • 2023–2024: HPE rolls out modern cloud-ready DevOps Starter Kits. Full, native support is added for modern languages such as Go, modern Python 3.x, and Node.js, allowing them to integrate into modern automated CI/CD build environments.

HPE NonStop Tandem Programming Languages and Development Timeline

Popular Computing Weekly British Computer Magazine from 1982 thru 1990

Popular Computing Weekly (frequently abbreviated as PCW) was a highly influential British computer magazine published from 23 April 1982 to 14 June 1990.

Popular Computing Weekly British Computer Magazine from 1982 thru 1990
Popular Computing Weekly British Computer Magazine from 1982 thru 1990

Launched by Sunshine Publications and led by founding editor Duncan Scot, it stood out by providing rapid-fire weekly news, hardware reviews, type-in software programs, and gaming coverage at the height of the UK’s home microcomputer boom.

Over its eight-year lifespan, it produced 415 issues, adapting its identity from a broad hobbyist guide to a gaming-centric publication before closing in the early 1990s.

Magazine Overview & Core Elements

Unlike glossy monthly publications such as Personal Computer World or Your Computer, Popular Computing Weekly acted as a fast-paced “newspaper” for the UK micro community. Because it hit newsagent shelves every seven days, it could report on dramatic price drops, industry buyouts, and hardware delays weeks before monthly rivals.

The magazine catered to a wide array of early systems, including the ZX Spectrum, Commodore 64, BBC Micro, Amstrad CPC, Atari 8-bit, Dragon 32, VIC-20, and later the 16-bit machines. Its format generally consisted of:

  • News Desk: Urgent industry reporting, micro-market trade wars, and launch delays.
  • Hardware and Software Reviews: Critical evaluations of new home computers and software titles.
  • Type-In Listings: Pages of raw BASIC or Machine Code that readers meticulously copied into their systems to run games and utilities.
  • Gaming Coverage & Puzzles: Dedicated spaces for arcade game high scores, maps, and adventure hints.

Detailed Timeline Breakdown (1982–1985)

1982: Launch and the 8-Bit Explosion

  • April: On 23 April 1982, Issue 1 was published by London-based Sunshine Publications. The launch editor, Duncan Scot, managed the first 8 issues before handing the reins over to Brendon Gore.
  • May–June: The magazine’s debut directly coincided with Sir Clive Sinclair’s unveiling of the ZX Spectrum. Popular Computing Weekly quickly positioned itself as a critical hub for Spectrum and BBC Micro setup guides and technical support.
  • System Agnosticism: Early volumes accommodated a highly fractured market, including type-in listings for the ZX81, VIC-20, Acorn Atom, TRS-80, and early Apple II systems.
  • Cover Price: The early issues cost just 30p.

1983: Price Wars and Rising Circulation

  • The Boom Year: Home computing exploded in the UK. PCW capitalised on its fast turnaround to report on brutal, ongoing price slashes initiated by Commodore, Sinclair, and Atari.
  • Market Diversification: Content expanded heavily to track new contenders like the Oric-1, Dragon 32, and the newly launched Commodore 64.
  • Commercialisation: Software companies grew rapidly. Advertising pages surged with multi-page spreads from early publishing giants like Imagine Software, Ocean Software, and Ultimate Play The Game.

1984: Amstrad’s Arrival and Market Shocks

  • April: The magazine closely documented Alan Sugar’s entry into the computer market with the Amstrad CPC 464, which changed the landscape by packaging a computer, keyboard, and monitor into an all-in-one unit.
  • The Crash Warning: PCW reported extensively on the high-profile financial collapse of Imagine Software and structural corrections across the British software industry.
  • The MSX Standard: The magazine devoted substantial print space to tracking the arrival of Japanese MSX standard computers (such as Toshiba’s HX-10) attempting to break into the UK.

1985: Transition to 16-Bit and Gaming Domination

  • January: The magazine followed the rocky release of the business-oriented Sinclair QL and the debut of the dual-mode Commodore 128.
  • May: The news desk shifted focus to the 16-bit horizon, tracking early announcements for the Atari 520ST and Commodore Amiga.
  • Pricing: Driven by inflation and increased page counts, the cover price rose to 40p.
  • Software Pivot: As users grew tired of typing in complex code by hand, the publication reduced its raw code listings and pivoted towards dedicated, full-colour video game previews, software reviews, and maps.

Post-Early Eighties Legacy (1986–1990)

Beyond its golden era, the publication continued to evolve through the late 1980s. By 1989, regular home micro content declined as the industry consolidated around IBM-compatible PCs, the Amiga, and the Atari ST. To compensate for falling sales, PCW incorporated Computer Gamesweek in 1989, morphing almost entirely into a video games magazine.

1. Popular Computing Weekly British Computer Magazine from 1982 thru 1990
Popular Computing Weekly British Computer Magazine
2. Popular Computing Weekly British Computer Magazine

Sunshine Publications eventually closed the magazine on 14 June 1990 with its 415th issue, ending its run as a primary historical record of the 1980s British microcomputing phenomenon.

Mark Whitfield – Senior Project Manager – training received

Mark Whitfield, an SC cleared Senior Project Manager based in the Manchester area, has over 30 years of experience transitioning from a software engineer to an IT program leader.

His extensive technical and project management training spans methodologies, cloud infrastructure, and software applications.

A detailed breakdown of his training, certifications, and academic background includes:

Project Management Methodologies

  • PRINCE2 Practitioner: Certified via the ILX Group.
  • Agile SCRUM: Trained in-house with RADTAC.
  • Advanced Engagement Management: Level 2 certification completed via Capgemini.
  • Project Fundamentals: Completed “Fundamentals of Successful Project Management” and “Managing Multiple Projects” via Skillpath.
  • Microsoft Project: Microsoft Project ’98 certified.

Technical & Cloud Training

  • Microsoft Azure: AZ-900 Microsoft Certified Azure Fundamentals.
  • MuleSoft: Completed outcome-based delivery training and is a specialized Delivery Manager.
  • Technical Programming: Includes foundational database and software language training, such as C++ and MS SQL 2000 query training, as well as VPS and Tandem (HPE NonStop) technical/development courses.
  • Productivity: Completed Microsoft Excel Refresher and Expert skills training (Udemy and Microsoft).

Formal Education

  • Higher National Diploma (HND): Graduated with a Distinction (top) in Computing (1990).

You can review his detailed credential breakdown on the PROject Templates Professional Training Page.

HPE NonStop architecture (Tandem Computers) by Era and Year

Mark Whitfield invested many years in the HPE NonStop field from 1990. The HPE NonStop architecture (originally Tandem Computers) is a legendary fault-tolerant system known for 100% continuous availability. The platform’s hardware and software execution evolved across six distinct eras and processor transitions:

1. The Tandem Founding Era (1976–1981)

  • Years: 1976–1981
  • Processors: Proprietary 16-bit stack processors (e.g., Tandem/16, NonStop II)
  • Architecture: The foundational “shared-nothing” parallel architecture. Featured redundant components (processors, disks, power supplies) connected by a proprietary dual-bus (Dynabus). The operating system provided instant automated failover.

2. The Cyclone & Early RISC Era (1981–1996)

  • Years: 1981–1996
  • Processors: Proprietary non-RISC (NonStop Cyclone) & MIPS R-series RISC
  • Architecture: Expanded into 32-bit computing. To keep pace with industry performance, Tandem transitioned from proprietary processors to off-the-shelf MIPS RISC processors while heavily emulating the original instruction set for compatibility.

3. The Himalaya/ServerNet Era (1997–2004)

  • Years: 1997–2004
  • Processors: MIPS R-series
  • Architecture: Replaced the legacy Dynabus with ServerNet, a high-speed system interconnect that served as an early precursor to modern networking fabrics. (Compaq acquired Tandem in 1997, which subsequently merged with HP in 2002).

4. The Integrity Itanium Era (2005–2013)

  • Years: 2005–2013
  • Processors: Intel Itanium (TNS/E)
  • Architecture: Branded as HP Integrity NonStop (NonStop i). The platform moved off proprietary silicon to standard Intel Itanium processors. This was driven by the “NonStop Advanced Architecture” (NSAA), lowering hardware costs while maintaining Availability Level 4 (AL4) standards.

5. The NonStop X (x86-64) Era (2014–Present)

  • Years: 2014–2026
  • Processors: Intel Xeon x86-64 (TNS/X)
  • Architecture: Fully decoupled the OS from proprietary hardware by shifting to standard Intel x86-64 processors and InfiniBand fabric. The latest compute nodes (such as the NS5 X5 and NS9 X5) utilize modern Intel Xeon Scalable processors to maintain maximum Availability Level 4 (AL4) workloads.

6. The Virtualized NonStop Era (Present)

  • Years: 2015–Present
  • Processors: Virtual Machines / Cloud / x86
  • Architecture: HPE extended the platform to support Virtualized NonStop Software, allowing fault-tolerant enterprise workloads to run entirely in private clouds via standard VMware or hybrid architectures, independent of specific physical servers.
HPE NonStop article by Mark Whitfield in 2013, working for Insider Technologies Limited in Salford Quays

sp/ARCHITECT was a pioneering electronic banking & funds-transfer software suite

sp/ARCHITECT was a pioneering electronic banking and funds-transfer software suite. Originally built by the UK-based Software Partnership (TSP), it ran natively on fault-tolerant Tandem (now HPE NonStop) systems. It provided highly available transaction routing and real-time electronic book-keeping for major international financial institutions.

Detailed Timeline by Era and Year

1. The Genesis & Independent Era (Mid-1980s – 1989)

  • Mid-1980s: The Software Partnership (TSP) is co-founded in Timperley, UK. Development begins on sp/ARCHITECT, designed with a client-server architecture.
  • 1986: Tandem launches NonStop SQL, providing the underlying high-availability relational database foundation that sp/ARCHITECT relied upon to ensure absolute data integrity for banks.

2. Mainstream Banking Adoption Era (1990 – 1994)

  • 1990: TSP relocates to Norton House in Runcorn, UK. sp/ARCHITECT achieves production deployment and is widely utilized for inter-account transfers and book-keeping by major banks like TSB and Bank of Scotland.
  • 1992: Due to rapid expansion, the Runcorn operations relocate to Wingate House.
  • 1994: Deluxe Electronic Payment Systems (a subsidiary of Deluxe Corporation) acquires TSP to expand its global electronic funds transfer (EFT) footprint. The platform is globally marketed and supported, expanding to clients like Rabobank.
1990: TSP relocates to Norton House in Runcorn
1990: TSP relocates to Norton House in Runcorn
1992: Due to rapid expansion, the Runcorn operations relocate to Wingate House.
1992: Due to rapid expansion, the Runcorn operations relocate to Wingate House.

3. Global Expansion & Compaq Transition Era (1995 – 2005)

  • 1995 – 1997: The Runcorn-based team (operating as Deluxe Data) codes additional regional adaptations of sp/ARCHITECT for banks worldwide (e.g., Girofon in Denmark).
  • 1997: Compaq acquires Tandem Computers, placing sp/ARCHITECT on Compaq’s enterprise roadmap.
  • 2002: Hewlett-Packard (HP) acquires Compaq, absorbing the Tandem platform into the HP Integrity server line. The application undergoes adaptation to integrate modern Windows-based management systems (like DSM/NOW).

4. The HPE Modernization & Hybrid Era (2014 – 2026)

  • 2014: HPE (Hewlett Packard Enterprise) is formed, spinning off from HP. NonStop shifts to Intel x86-64 architecture (NonStop X), requiring sp/ARCHITECT and related Tandem subsystems (like Pathway, COBOL, and TAL) to modernize for TNS/X processing.
  • 2020: Legacy Itanium-based environments are phased out. sp/ARCHITECT systems, if still active, are migrated to virtualized NonStop (vNS) and operated within private cloud infrastructures.
  • 2025/2026: HPE NonStop celebrates its 50th Anniversary. Applications originally designed on the sp/ARCHITECT schema are heavily evaluated for AI integration, continuous cyber resilience, and consumption-based models like HPE GreenLake.

HPE Nonstop Technology Architecture – specialized, 100% fault-tolerant infrastructure

The official HPE Nonstop Technology Architecture is a specialized, 100% fault-tolerant infrastructure built with a tightly integrated hardware and software stack designed to eliminate any single point of failure. Formal instruction and architectural frameworks have been modernized under the newly relaunched HPE Nonstop Compute Training Portfolio curriculum.

Originally developed by Tandem Computers in 1976, the platform eventually became part of Hewlett Packard Enterprise (HPE). Unlike standard servers that can crash due to a single component failure, NonStop uses a tightly integrated, “shared-nothing” architecture to ensure that if a hardware or software component fails, another instantly takes over with zero downtime or data loss.

Core Architectural Features

To understand how HPE NonStop works, you need to understand its unique design principles:

  • Shared-Nothing Architecture: Every processor has its own dedicated memory, I/O channels, and copy of the operating system. No single component is shared, eliminating any single point of failure.
  • Process Pairs: Applications run using a primary process and a backup process on a different processor. The primary process constantly copies its state to the backup. If the primary fails, the backup immediately takes over.
  • Massive Scalability: Systems can scale up seamlessly from small distributed environments to massive clusters containing up to 24,000 processor cores without interrupting running operations.
  • Hardware Platform: The modern software environment runs on industry-standard x86 architectures, available as physical server racks (like the HPE NonStop NS9 X5) or as virtualized instances in hybrid cloud environments.

Dual Operating Environments

HPE NonStop runs a specialized operating system called NonStop OS. Inside this OS, developers and administrators interact with two distinct environments:

  • Guardian Environment: The native, proprietary environment optimized for high-volume Online Transaction Processing (OLTP). It handles tasks sequentially through process-oriented manually-started jobs rather than traditional automated queues.
  • Open System Services (OSS): A UNIX-like, POSIX-compliant environment built on top of the NonStop kernel. This allows organizations to run standard open-source applications, tools, and scripts natively alongside Guardian.

Ecosystem and Use Cases

HPE NonStop is rarely used for standard office automation or basic web hosting. Instead, it serves as the backbone for global industries where an hour of downtime could cost millions of dollars:

  • Financial Transactions: Powers global stock exchanges, automated teller machines (ATMs), and retail point-of-sale credit card processing, eg. BASE24.
  • Travel and Logistics: Runs critical airline reservation systems and real-time cargo routing infrastructure.
  • Database Management: Features its own highly secure, distributed database engine called NonStop SQL, which guarantees absolute data integrity across all transactions.
  • Modern Development: Supports traditional languages like COBOL85 and ANSI C, alongside modern DevOps integrations like Git, Ansible, and Eclipse-based IDE environments.

If you plan to work directly with these systems, you can explore formal pathways like the Concepts and Facilities for HPE NonStop Systems course provided by HPE Education Services.


Core Architectural Layers (Diagram Blueprint)

An architectural blueprint of an HPE NonStop environment typically separates the layout into three core interdependent layers:

  • Hardware & Fabric Layer: Consists of independent, loosely-coupled Processor Nodes (handling up to 24,000 cores globally) connected via an ultra-fast InfiniBand or ServerNet system fabric backbone.
  • I/O & Subsystem Layer: Utilizes Cluster I/O Protocols (CLIMs), splitting tasks between Storage CLIMs (SCLIMs) and Network CLIMs (NCLIMs) to isolate external communication from main processing.
  • Operating System & DB Layer: Runs the NonStop OS, which simultaneously manages the traditional Guardian environment, Open System Services (OSS) for UNIX/Linux paradigms, and the NonStop SQL distributed database engine.

Recommended Architecture Training Curriculum

HPE organizes its technical blueprints into structured educational paths for engineers.

1. Foundational Blueprint Concepts

  • Course Code: U4147S (HPE Nonstop Compute System Fundamentals).
  • Focus: Delivers a top-down view of system goals, transaction processing, and fundamental architecture.
  • Key Modules: Explores Guardian vs OSS, Pathway application management, and basic database interaction.

2. System Operations & Administration

  • Course Code: H1SC3S (HPE Nonstop Compute System Administration I).
  • Focus: Maps physical and virtual components to real-world deployment.
  • Key Modules: Covers Processor Nodes, configuring SCLIMs/NCLIMs, and hands-on fault-scenario testing.

3. Low-Level OS Internals

  • Course Code: U8609S (HPE Integrity Nonstop Operating System Architecture).
  • Focus: Deep dive into runtime architecture, process control, and memory allocation.
  • Key Modules: Focuses on Inter-process Message Systems, synchronization mechanisms, and system debugging.

Training Delivery Options

Enrolling via HPE Education Services grants access to various professional development features:

  • HPE vLabs: Direct sandbox access to practice configuration and live fault injection inside virtual environments.
  • Digital Learner Credits: Flexible licensing options to assign corporate learning units across teams.
  • Modernized Tracks: Courses have been fully overhauled to support contemporary cloud paradigms and hybrid integration via HPE GreenLake frameworks.

My HPE NonStop (Tandem Computers) Certificates :

HPE NonStop (Tandem) Career Experience at Insider Technologies Limited, ITL
BASE24 eps monitoring

Mark Whitfield, High-Level Project Management Summary

You can review or download the targeted, one-page CV for Mark Whitfield (Senior Project Manager specializing in HPE NonStop systems) via the Mark Whitfield CV PDF link.

Mark Whitfield, High-Level Project Management Summary
Mark Whitfield, High-Level Project Management Summary

The high-level, scannable overview of his professional profile is outlined below:

Executive Profile

  • Role: IT Senior Project Manager / Delivery Lead
  • Background: 30+ years of experience delivering highly complex technology, business transformation, and infrastructure projects.
  • Core Skills: Cloud migration (hybrid), legacy ATM software modernisation, Point of Sale (POS) implementations, and software development lifecycles (SDLC).
  • Methodologies: Agile, Waterfall, PRINCE2 Practitioner, and ITIL certified.

Core Expertise & Competencies

  • HP NonStop & Legacy Integration: Deep technical roots in Tandem Computers/ HPE NonStop development, TAL programming, and high-volume transaction environments.
  • Global Delivery: Managed large-scale IT and system monitoring rollouts across the UK and international markets (e.g., Saudi Arabia).
  • Stakeholder Management: Experienced in bridging the gap between highly technical development teams and high-level business stakeholders.

For direct access to his official templates, articles, and full professional journey, you can visit the PROject Templates Website.

Mark Whitfield IT, Technical & Project Management Training Overview

Mark Whitfield, a Manchester-based Senior IT Project Manager, has completed extensive professional training throughout his career, focusing on project management methodologies, delivery software, and technical tools.

Core Project Management Methodologies :

  • PRINCE2 Practitioner: Certified as a registered PRINCE2 Practitioner in May 2011 via the ILX Group (Gold e-Learning).
  • Agile SCRUM Training: Attended in-house training with RADTAC in May 2011.
  • Advanced Engagement Management (Level 2): Completed at Capgemini in November 2017.
  • Project Management Fundamentals: Completed “Fundamentals of Successful Project Management” in February 2000 through Skillpath in Manchester.
  • Managing Multiple Projects: Attended “Managing Multiple Projects, Objectives and Deadlines” in October 1999/1998 via Skillpath.

Software & Cloud Platforms :

  • AZ-900 Microsoft Azure Fundamentals: Certified in February 2022.
  • Microsoft Project: Completed the Microsoft Project ’98 Certification Series in May 2000 through the IIL UK Education Centre in Reading.
  • Microsoft Excel Expert Skills: Upgraded skills via a 2017 Expert course and a July 2024 Udemy refresher.

Technical & Programming Courses :

  • Tandem / HP NonStop: Completed Tandem Guardian Principles (1993), Tandem Performance Analysis (1995), and Tandem TAL Programming (1995).
  • C / C++ Programming: Attended “C++ for Non-C Programmers” with Comtec Computer Training in March 1997.
  • Database Querying: Completed “Querying Microsoft SQL 2000 with Transact SQL” via QA Training in March 2009.
  • Web Applications: Attended “Developing MS ASP Web Applications using MS Visual Studio .NET” in January 2007.

Marketing & Communication Training :

  • Writing for the Web: Completed in May 2009 with gbdirect (iTrain Education in London).
  • Brochure & Document Design: Attended a SkillPath Seminar on designing marketing brochures and reports in April 2006.