Category: Career

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)

The Centre for Computing History, Commodore Pet 1977

The Centre for Computing History, Commodore Pet 1977

In November 2017 – Capgemini Advanced Engagement Management Course – Level 2 Exam

November 2017 – Capgemini Advanced Engagement Management Course – Level 2 Exam

In December 2022 – C&CA UK’s Communications & Engagement Award Winner – Cloud & Custom Applications – Capgemini UK

December 2022 – C&CA UK’s Communications & Engagement Award Winner – Cloud & Custom Applications – Capgemini UK

October 2018 to June 2019, augmented into MuleSoft (a Salesforce company) as a Delivery Manager

From October 2018 to June 2019, I was augmented into MuleSoft (a Salesforce company) as a Delivery Manager managing a number of accounts across the UK, for the delivery of the Anypoint Platform. 

The Anypoint Platform includes various components such as Anypoint Design Center, which allows API developers to design and build APIs; Anypoint Exchange, a library for API providers to share APIs, templates, and assets; and Anypoint Management Center, a centralized web interface to analyze, manage, and monitor APIs and integrations.

mark whitfield delivery_manager_anypoint_platform_mulesoft_mark_whitfield

The Delivery Manager role is much like a Programme Manager role and typically links with the client’s Project /Programme Manager role to ensure that any project plans align to the MuleSoft Outcome Based Delivery (OBD) framework to achieve the agreed business outcomes.

The OBD framework provides a structured set of work streams, tasks and sub-tasks for the client to become fully enabled in an API-led project delivery as part of the business operating model. It also provides best practice guidance on the required business and IT culture modifications and governance to support the correct API ownership approach. The 3 OBD streams are; 1) Business Outcomes, 2) Technology Delivery and 3) Org Enablement.

Attended BIHE 1988 – 1990, Bolton Institute of Higher Education (University of Bolton – 2004)

BIHE, Bolton Institute of Higher Education (University of Bolton – 2004)

(University status attained in April 2004)

Website:    http://www.bolton.ac.uk

Year:         1988 – 1990

Course:     BTEC Higher National Diploma in Computer Studies

Awarded:   DISTINCTION  (overall first over the 2 years)

Operating SystemLanguages / Other

VAX / VMS OPERATING SYSTEM

PASCAL, DBASE3, MS-DOS, SQL, COBOL74, ORACLE, FMS

The HND course I attended at BIHE was a 2-year, full-time course made up of the following modules:

  • Computer Systems Architecture
  • Programming Methodology Theory / Practice (final year project)
  • Data Processing
  • Business Studies
  • Quantitative Techniques
  • System Analysis
  • Business Information Systems Theory / Practice
bihesideaspectview
The old Bolton Institute for Higher Education (BIHE) building

My final year project consisted of an ORACLE SQL-forms designed GUI interface running under an MS-DOS operating system. The GUI interface provided insert, update, delete and transaction rollback facilities for recording information about students attending courses at BIHE, along with their module assignment and exam result details.

The student data was held in an ORACLE SQL database set-up on a PC local to the application. The tables were designed in accordance with Third Normal form (TNF) design methodology in order to cancel out repeating student data. The resulting application catered for both snapshot and historical reports. System analysis work was carried out using SSADM (Structured Systems Analysis and Design Methodology).

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. 

Project Management Group on LinkedIn

https://www.linkedin.com/groups/163300

Project Management Group on LinkedIn

Project Management Delivery Templates – ProjectTemplatesSoft – Etsy UK

https://www.etsy.com/uk/shop/ProjectTemplatesSoft

Both Agile and Waterfall (including PRINCE2) project delivery / management templates available at Etsy.

PM Templates are in Microsoft Office (MS Excel, Word, PowerPoint) and Microsoft Project formats.

The complete project management templates bundle (130+ templates) are also available on my website at : https://mark-whitfield.com/project-templates/

Project Management Templates – examples above plus many, many more…

Project Management – KEY Documentation Templates

Timeline history of PRINCE2

Agile SCRUM Training Course

Registered PRINCE2 Practitioner with ILX

Plan On a Page (POaP)

Template Tip of the day :

Good’ish to Good PMs will know this – 146 times out of a 147 (max), in my IT career and PM’ship to date, I have often found a well laid out plan on a page (POaP) is the key backbone and most requested PM artefact for team/client discussions (helps you lead from the front – pivotal really… right?)…

https://mark-whitfield.com/project-templates/

Project Management KPIs