PL/I

PL/I
Name	PL/I
Paradigm	Procedural, imperative, structured, concurrent
Designer	IBM C. A. R. Hoare?
Developer	IBM
First appeared	1964
Typing	Static, strong?
Influenced by	Fortran, COBOL, ALGOL 60, Assembly language
Influenced	Ada, C, ALGOL 68, Pascal, Modula-2

PL/I is a high-level programming language developed in the 1960s for scientific, engineering, and business applications. It combined features from Fortran, COBOL, and ALGOL 60 to provide numeric computation, record handling, file processing, and system programming facilities in a single language. Designed during the era of mainframe computing by IBM and influenced by contemporaneous work at institutions such as RAND Corporation and universities, the language sought to unify diverse programming needs across United States government and industry projects.

History

PL/I originated in the early 1960s when IBM initiated internal projects to reconcile differing customer needs for scientific programming, represented by Fortran, and business processing, represented by COBOL. Key development groups at IBM Research and the IBM Palo Alto Scientific Center collaborated with engineers who had worked on FORTRAN IV, COBOL, and ALGOL 60 implementations. The language was announced in 1964 amid competition from languages such as Algol, MAD, and proprietary systems from vendors like Burroughs Corporation and UNIVAC. During the Cold War era, governmental procurement influenced design choices, while standards bodies including ANSI and ISO later engaged in formalizing extensions and bindings for mainframe environments.

Language design and features

PL/I's design emphasized a single language suitable for both numeric computation and business data processing, borrowing numeric arrays and complex arithmetic from Fortran and record and file structures from COBOL. It introduced structured programming constructs influenced by ALGOL 60 and later control-flow innovations traced to work by computer scientists at Stanford University and Massachusetts Institute of Technology. Features included exception handling and condition handling mechanisms uncommon at the time, concurrency support with multitasking primitives that echoed research at Bell Labs and MIT Lincoln Laboratory, and rich data types such as packed decimal influenced by financial processing needs in New York City banking systems. The language provided low-level facilities for bit manipulation and address arithmetic, aligning with system programming practices seen in DEC hardware environments and research at University of Cambridge Computer Laboratory.

Syntax and semantics

The syntax combined ALGOL-like block structure with declarations reminiscent of COBOL and Fortran's array notation. Declarations for scalars, arrays, records, and pointers used keywords and attribute clauses that reflected design work from IBM Research and standards committees. PL/I included a distinctive condition handling concept, where named conditions and ON-unit handlers allowed recovery from runtime events; this approach paralleled exception models explored at Xerox PARC and in early designs at Bell Labs. Semantics for input/output and file organization incorporated concepts from COBOL and system-level I/O conventions on IBM System/360 hardware, while lexical scope and parameter passing exhibited influences from ALGOL 60 and implementation experience at University of Waterloo.

Implementations and compilers

Major commercial implementations were produced by IBM for the IBM System/360 and later IBM System/370 families, with compilers optimized for mainframe batch and transaction processing environments such as CICS and IMS. Other vendors and institutions produced compilers and translators: Stanford University researchers, compiler groups at Honeywell, and software houses serving United Kingdom financial firms. Academic work on optimizing PL/I compilers appeared at institutions like Carnegie Mellon University and University of Illinois Urbana–Champaign, contributing to code generation and optimization techniques used later in compilers for Ada and C. Open-source and proprietary ports emerged targeting DEC VAX, UNIX System V, and microcomputer platforms, with runtime systems integrating with operating systems such as VM/CMS and MS-DOS via runtime libraries.

Usage and applications

PL/I found extensive use in large-scale administrative computing at banking institutions in New York City, airline reservation systems managed by companies such as IBM contractors, and scientific computation in aerospace projects connected to NASA centers. Government agencies, including departments in the United States federal infrastructure, deployed PL/I for business reporting and transaction processing on mainframes operated at data centers. Educational institutions taught PL/I alongside Fortran and COBOL in computing curricula at universities like Princeton University and University of California, Berkeley during the 1960s and 1970s. The language's facilities for file processing and decimal arithmetic made it suited for payroll, inventory, and ledger systems in corporate IT centers across Europe and Asia.

Legacy and influence

PL/I's attempt to amalgamate features influenced later language design debates and inspired features in languages such as Ada for safety-critical systems and ALGOL 68 for orthogonal design. Concepts from PL/I's condition handling and multitasking contributed to exception and concurrency models in languages developed at Bell Labs and research groups at Xerox PARC. Compiler research on PL/I advanced optimization techniques later applied in compilers from GNU Project and industrial vendors like Microsoft and Sun Microsystems. While overt commercial usage declined with the rise of C and COBOL continuations, legacy PL/I systems remain in maintenance at enterprises and institutions that continue to operate mainframe applications built during the language's heyday.

Category:Programming languages