Rexx

Rexx
Paradigmmultiparadigm: procedural, structured
Designed byMike Cowlishaw
DeveloperMike Cowlishaw, IBM
First appeared1979 (1979)
Stable release
ANSI X3.274 / 1996 (1996)
Typing disciplineDynamic
Filename extensions.cmd, .bat, .exec, .rexx, .rex, EXEC
Major implementations
VM/SP R3,[1] TSO/E V2, SAAREXX, ARexx, BREXX, Regina,[2] Personal REXX, REXX/imc
Dialects
NetRexx, Object REXX, now ooREXX, KEXX
Influenced by
PL/I, ALGOL, EXEC, EXEC 2
Influenced
NetRexx, Object REXX

Rexx (Restructured Extended Executor) is a programming language that can be interpreted or compiled. It was developed at IBM by Mike Cowlishaw.[3][4] It is a structured, high-level programming language designed for ease of learning and reading. Proprietary and open source Rexx interpreters exist for a wide range of computing platforms; compilers exist for IBM mainframe computers.[5]

Rexx is a full language that can be used as a scripting, macro language, and application development language. It is often used for processing data and text and generating reports; this means that Rexx works well in Common Gateway Interface (CGI) programming and is used for this purpose, like later languages such as Perl. Rexx is the primary scripting language in some operating systems, e.g. OS/2, MVS, VM, AmigaOS, and is also used as an internal macro language in some other software, such as SPF/PC, KEDIT, THE and the ZOC terminal emulator. Additionally, the Rexx language can be used for scripting and macros in any program that uses Windows Scripting Host ActiveX scripting engines languages (e.g. VBScript and JScript) if one of the Rexx engines is installed.

Rexx is supplied with VM/SP Release 3 on up, TSO/E Version 2 on up, OS/2 (1.3 and later, where it is officially named Procedures Language/2), AmigaOS Version 2 on up, PC DOS (7.0 or 2000), ArcaOS,[6] and Windows NT 4.0 (Resource Kit: Regina). REXX scripts for CMS share the filetype EXEC with EXEC and EXEC2, and the first line of the script specifies the interpreter to be used. REXX scripts for MVS may[a] be recognized by the low level qualifier EXEC or may[b] be recognized by context and the first line. REXX scripts for OS/2 share the filename extension .cmd with other scripting languages, and the first line of the script specifies the interpreter to be used. REXX macros for REXX-aware applications use extensions determined by the application. In the late 1980s, Rexx became the common scripting language for IBM Systems Application Architecture, where it was renamed "SAA Procedure Language REXX".

In mainframe programming, a Rexx script or command is sometimes referred to as an EXEC in a nod to the CMS file type used for EXEC,[7] EXEC 2[8] and REXX scripts on CP/CMS and VM/370 through z/VM.

  1. ^ IBM (1999). "REXX/VM Reference" (PDF). MANMRK. Retrieved May 29, 2023.
  2. ^ Mark Hessling (October 25, 2012). "Regina Rexx Interpreter". SourceForge project regina-rexx. Retrieved February 10, 2014.
  3. ^ Cite error: The named reference RexHist was invoked but never defined (see the help page).
  4. ^ Cite error: The named reference RexMay95 was invoked but never defined (see the help page).
  5. ^ "Catalog of All Documents (filter=rexx)". IBM library server. 2005. Archived from the original on February 15, 2013. Retrieved February 10, 2014.
  6. ^ "Does ArcaOS include REXX support?". Retrieved September 3, 2020.
  7. ^ IBM Virtual Machine Facility /370: EXEC User's Guide (PDF) (Second ed.). International Business Machines Corporation. April 1975. GC20-1812-1.
  8. ^ EXEC 2 Reference (PDF) (Second ed.). International Business Machines Corporation. April 1982. p. 92. SC24-5219-1. Archived from the original (PDF) on April 2, 2020. Retrieved March 28, 2019.


Cite error: There are <ref group=lower-alpha> tags or {{efn}} templates on this page, but the references will not show without a {{reflist|group=lower-alpha}} template or {{notelist}} template (see the help page).


Developed by StudentB