Technologies, Systems & Platforms worked with across eras

Mark Whitfield‘s career history showcases a progression from specialized mainframe banking code development to enterprise-scale agile digital delivery and hybrid cloud migrations.

Mark Whitfield | Career Hardware & Software experience
Mark Whitfield | Career Hardware & Software experience
Mark Whitfield HPE NonStop Mainframe to Modern Cloud Project Delivery
Mark Whitfield | HPE NonStop Tandem Mainframe to Modern Cloud Project Delivery

A detailed breakdown of the technologies, systems, and platforms he has worked with across his professional eras is outlined below.

💻 1990–1995: Early Programming & Lead Analysis Era

During this foundational period, Whitfield worked as a Programmer and Lead Analyst focused on core electronic banking architectures and early digital money transfer logic.

  • Companies & Key Clients: The Software Partnership / Deluxe Data, Barclays Bank (Knutsford & Poole), Girofon (Denmark), TSB, Bank of Scotland, and Rabobank.
  • Core Software Frameworks: sp/ARCHITECT-BANK, Barclays Business Master II (BBM II), custom batch billing modules, and a touch-tone phone banking suite integrated with Periphonics VRAM.
  • Technical Stack:
    • Hardware & OS: Tandem Mainframe Computers running Tandem Guardian O/S.
    • Languages: COBOL85, NonStop SQL, SCOBOL (Screen COBOL), TAL (Tandem Application Language), C, and C++.
    • Subsystems & Tools: PATHWAY, PATHMAKER, ENSCRIBE, EMS, and INSPECT.

🛠️ 1995–2013: Engineering, Product & Strategic Project Management Era

Over his 18-year tenure, Whitfield transitioned from a technical infrastructure engineer into real-time transaction monitoring product management.

  • Company & Key Clients: Insider Technologies Limited (ITL), CRESTCo (Euroclear), Bank of England, Deutsche Bank, HSBC, Alliance & Leicester (Santander), Standard Chartered, Global Payments, and Al Rajhi Bank.
  • Core Software Frameworks: Reflex 80:20 Suite (Console, Status Monitor, Service Monitor modules), RTLX Reactor (Real-Time Log Extraction), Sentra monitoring layer, XPERT24, and DotNetNuke (Open CMS framework).
  • Technical Stack:
    • Hardware & OS: HPE NonStop (Tandem K-Series, S-Series, and Itanium J-Series), Windows 2000/XP, Linux, and Unix.
    • Languages: TAL, NonStop C/C++, COBOL85, SCOBOL, NonStop SQL, TACL, and Enscribe.
    • Enterprise Software Interfaced: ACI BASE24 Classic, BASE24-eps, XPNET middleware, ICE (Insession), IBM TIVOLI, COMMAND/POST, and HP OpenView Operations (secured the first 2-way Smart Plug-In certification for NonStop environments).

🏦 2013–2014: Professional Services Banking Delivery Era

Whitfield moved into consultant-driven banking professional services, managing high-value legacy modernization and operating system upgrades.

  • Company & Key Client: Wincor Nixdorf Banking Division, leading a stream for Lloyds Banking Group’s Self-Service Software Replacement (SSSR) programme.
  • Core Software Frameworks: Wincor ProClassic Enterprise (PC/E) product suite.
  • Technical Stack:
    • Operating Systems: Migrating legacy terminal setups over to Windows 7 platforms and distributed UNIX/AIX environments.
    • Databases & Interfaces: Oracle databases integrated with core banking frameworks; overseeing transactions shifting away from mainframe-reliant BASE24 Classic.

🎮 2014–2016: Digital Infrastructure & Enterprise Betting Era

Whitfield shifted his delivery domain from banking mainframes over to real-time, high-throughput sportsbooks and digital customer gaming platforms.

  • Company: Betfred Online and Mobile Division.
  • Core Software Platforms: .COM and .mobi channels, Native apps, fraud mitigation tools, and payment gateways.
  • Technical Stack & Multi-Vendor Integrations:
    • Mobile Frameworks: Native app deployment workflows across iOS, Android, and Windows Phone.
    • Gaming Modules: RNG (Random Number Generator) components and frontend systems built with third parties like Playtech, Inspired, IGT, Virtue Fusion, and Degree 53.
    • Data Feeds & Push Engines: Real-time push technology from Onionsack, OtherLevels, SIS (Satellite Information Services), and StreamUK.
    • Analytics Pathways: Ingestion pipelines via Appsflyer, Income Access, and Activewin.

☁️ 2016–Present: Cloud Integration, Middleware, & Public Sector Era

In his current active era, Whitfield functions as an SC-cleared Engagement and Delivery Manager orchestrating massive hybrid cloud migrations and API ecosystems.

  • Company & Roster of Clients: Capgemini UK Consultancy, working with UK Government public sector frameworks, MuleSoft, NATS (National Air Traffic Services), Royal Mail Group (RMG), Jaguar Land Rover (JLR), Heathrow Airport, Welsh Water, Rabobank, Barclays, and UKEF.
  • Core Software Frameworks: Salesforce MuleSoft Anypoint Platform, Anypoint Code Builder configurations, microservices infrastructure, and automated system management models.
  • Technical Stack:
    • Cloud Frameworks: Large-scale cloud architecture deployment across Microsoft Azure and Amazon Web Services (AWS) platforms.
    • API & Automation: API-led connectivity pipelines, middleware application refactoring, hyper-automation flows, and secure Apple iOS custom deployment paths for defense and data-sensitive spaces.

Mark Whitfield | Career Hardware & Software experience above

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

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.