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[lower-alpha 1] be recognized by the low level qualifier EXEC or may[lower-alpha 2] 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.
Features
Rexx has the following characteristics and features:
Simple syntax
The ability to route commands to multiple environments
The ability to support functions, procedures and commands associated with a specific invoking environment.
A built-in stack, with the ability to interoperate with the host stack if there is one.
Small instruction set containing just two dozen instructions
Straightforward access to system commands and facilities
Simple error-handling, and built-in tracing and debugger
Few artificial limitations
Simplified I/O facilities
Unconventional operators
Only partly supports Unix style command line parameters, except specific implementations
Provides no basic terminal control as part of the language, except specific implementations
Provides no generic way to include functions and subroutines from external libraries, except specific implementations
Rexx has just twenty-three, largely self-evident, instructions (such as call, parse, and select) with minimal punctuation and formatting requirements. It is essentially an almost free-form language with only one data-type, the character string; this philosophy means that all data are visible (symbolic) and debugging and tracing are simplified.
Rexx's syntax looks similar to PL/I, but has fewer notations; this makes it harder to parse (by program) but easier to use, except for cases where PL/I habits may lead to surprises. One of the REXX design goals was the principle of least astonishment.[9]
History
pre–1990
Rexx was designed and first implemented, in assembly language, as an 'own-time' project between 20 March 1979 and mid-1982 by Mike Cowlishaw of IBM, originally as a scripting programming language to replace the languages EXEC and EXEC 2.[3] It was designed to be a macro or scripting language for any system. As such, Rexx is considered a precursor to Tcl and Python. Rexx was also intended by its creator to be a simplified and easier to learn version of the PL/I programming language. However, some differences from PL/I may trip up the unwary.
It was first described in public at the SHARE 56 conference in Houston, Texas, in 1981,[10] where customer reaction, championed by Ted Johnston of SLAC, led to it being shipped as an IBM product in 1982.
The Amiga version of Rexx, called ARexx, was included with AmigaOS 2 onwards and was popular for scripting as well as application control. Many Amiga applications have an "ARexx port" built into them which allows control of the application from Rexx. One single Rexx script could even switch between different Rexx ports in order to control several running applications.
1990 to present
In 1990, Cathie Dager of SLAC organized the first independent Rexx symposium, which led to the forming of the REXX Language Association. Symposia are held annually.
Several freeware versions of Rexx are available. In 1992, the two most widely used open-source ports appeared: Ian Collier's REXX/imc for Unix and Anders Christensen's Regina[2] (later adopted by Mark Hessling) for Windows and Unix. BREXX is well known for WinCE and Pocket PC platforms, and has been "back-ported" to VM/370 and MVS.
OS/2 has a visual development system from Watcom VX-REXX. Another dialect was VisPro REXX from Hockware.
Portable Rexx by Kilowatt and Personal Rexx by Quercus are two Rexx interpreters designed for DOS and can be run under Windows as well using a command prompt. Since the mid-1990s, two newer variants of Rexx have appeared:
NetRexx: compiles to Javabyte-code via Java source code; this has no reserved keywords at all, and uses the Java object model, and is therefore not generally upwards-compatible with 'classic' Rexx.
In 1996 American National Standards Institute (ANSI) published a standard for Rexx: ANSI X3.274–1996 "Information Technology– Programming Language REXX".[14] More than two dozen books on Rexx have been published since 1985.
Rexx marked its 25th anniversary on 20 March 2004, which was celebrated at the REXX Language Association's 15th International REXX Symposium in Böblingen, Germany, in May 2004.
On October 12, 2004, IBM announced their plan to release their Object REXX implementation's sources under the Common Public License. Recent releases of Object REXX contain an ActiveX Windows Scripting Host (WSH) scripting engine implementing this version of the Rexx language.
On February 22, 2005, the first public release of Open Object Rexx (ooRexx) was announced. This product contains a WSH scripting engine which allows for programming of the Windows operating system and applications with Rexx in the same fashion in which Visual Basic and JScript are implemented by the default WSH installation and Perl, Tcl, Python third-party scripting engines.
As of January2017[update] REXX was listed in the TIOBE index as one of the fifty languages in its top 100 not belonging to the top 50.[15]
In 2019, the 30th Rexx Language Association Symposium marked the 40th anniversary of Rexx. The symposium was held in Hursley, England, where Rexx was first designed and implemented.[16]
Toolkits
The RexxUtil toolkit is a package of functions that is available for most Rexx implementations and most host operating systems.[17][18][19] RexxUtil is a package of file and directory functions, windowed I/O, and functions to access system services such as WAIT and POST.
Rexx/Tk, a toolkit for graphics to be used in Rexx programmes in the same fashion as Tcl/Tk is widely available.
A Rexx IDE, RxxxEd, has been developed for Windows.[12] RxSock for network communication as well as other add-ons to and implementations of Regina Rexx have been developed, and a Rexx interpreter for the Windows command line is supplied in most Resource Kits for various versions of Windows and works under all of them as well as DOS.
Spelling and capitalization
Originally the language was called Rex (Reformed Executor); the extra "X" was added to avoid collisions with other products' names. REX was originally all uppercase because the mainframe code was uppercase oriented. The style in those days was to have all-caps names, partly because almost all code was still all-caps then. For the product it became REXX, and both editions of Mike Cowlishaw's book use all-caps. The expansion to REstructured eXtended eXecutor was used for the system product in 1984.[9]
The loop control structure in Rexx begins with a DO and ends with an END but comes in several varieties. NetRexx uses the keyword LOOP instead of DO for looping, while ooRexx treats LOOP and DO as equivalent when looping.
Conditional loops
Rexx supports a variety of traditional structured-programming loops while testing a condition either before (do while) or after (do until) the list of instructions are executed:
dowhile[condition][instructions]end
dountil[condition][instructions]end
Repetitive loops
Like most languages, Rexx can loop while incrementing an index variable and stop when a limit is reached:
The increment may be omitted and defaults to 1. The limit can also be omitted, which makes the loop continue forever.
Rexx permits counted loops, where an expression is computed at the start of the loop and the instructions within the loop are executed that many times:
doexpression [instructions]end
Rexx can even loop until the program is terminated:
doforever[instructions]end
A program can break out of the current loop with the leave instruction, which is the normal way to exit a do forever loop, or can short-circuit it with the iterate instruction.
Combined loops
Like PL/I, Rexx allows both conditional and repetitive elements to be combined in the same loop:[20]
For single instructions, DO and END can also be omitted:
if[condition]then[instruction]else[instruction]
Indentation is optional, but it helps improve the readability.
Testing for multiple conditions
SELECT is Rexx's CASE structure, derived from the SELECT; form[lower-alpha 3] of the PL/ISELECT statement. Like some implementations of CASE constructs in other dynamic languages, Rexx's WHEN clauses specify full conditions, which need not be related to each other. In that, they are more like cascaded sets of IF-THEN-ELSEIF-THEN-...-ELSE code than they are like the C or Java switch statement.
The NOP instruction performs "no operation", and is used when the programmer wishes to do nothing in a place where one or more instructions would be required.
The OTHERWISE clause is optional. If omitted and no WHEN conditions are met, then the SYNTAX condition is raised.
Simple variables
Variables in Rexx are typeless, and initially are evaluated as their names, in upper case. Thus a variable's type can vary with its use in the program:
Unlike many other programming languages, classic Rexx has no direct support for arrays of variables addressed by a numerical index. Instead it provides compound variables.[21] A compound variable consists of a stem followed by a tail. A . (dot) is used to join the stem to the tail. If the tails used are numeric, it is easy to produce the same effect as an array.
doi=1to10stem.i=10-i end
Afterwards the following variables with the following values exist: stem.1 = 9, stem.2 = 8, stem.3 = 7...
Unlike arrays, the index for a stem variable is not required to have an integer value. For example, the following code is valid:
i='Monday'stem.i=2
In Rexx it is also possible to set a default value for a stem.
After these assignments the term stem.3 would produce 'Unknown'.
The whole stem can also be erased with the DROP statement.
dropstem.
This also has the effect of removing any default value set previously.
By convention (and not as part of the language) the compound stem.0 is often used to keep track of how many items are in a stem, for example a procedure to add a word to a list might be coded like this:
It is also possible to have multiple elements in the tail of a compound variable. For example:
m='July'd=15y=2005day.y.m.d='Friday'
Multiple numerical tail elements can be used to provide the effect of a multi-dimensional array.
Features similar to Rexx compound variables are found in many other languages (including associative arrays in AWK, hashes in Perl and Hashtables in Java). Most of these languages provide an instruction to iterate over all the keys (or tails in Rexx terms) of such a construct, but this is lacking in classic Rexx. Instead it is necessary to keep auxiliary lists of tail values as appropriate. For example, in a program to count words the following procedure might be used to record each occurrence of a word.
add_word:procedureexposecount.word_list parseargw.count.w=count.w+1/* assume count. has been set to 0 */ifcount.w=1thenword_list=word_listw return
and then later:
doi=1towords(word_list)w=word(word_list,i)saywcount.w end
At the cost of some clarity it is possible to combine these techniques into a single stem:
doi=1todictionary.0w=dictionary.i sayiwdictionary.w end
Rexx provides no safety net here, so if one of the words happens to be a whole number less than dictionary.0 this technique will fail mysteriously.
Recent implementations of Rexx, including IBM's Object REXX and the open source implementations like ooRexx include a new language construct to simplify iteration over the value of a stem, or over another collection object such as an array, table or list.
doioverstem.sayi'-->'stem.i end
In sum, compound variables provide a mechanism to create almost any kind of data structure in Rexx. These include lists or simple arrays, n-dimensional arrays, sparse or dense arrays, balanced or unbalanced trees, records, and more.
Keyword instructions
PARSE
The PARSE instruction is particularly powerful; it combines some useful string-handling functions. Its syntax is:
parse[upper]origin[template]
where origin specifies the source:
arg (arguments, at top level tail of command line)
linein (standard input, e.g. keyboard)
pull (Rexx data queue or standard input)
source (info on how program was executed)
value (an expression) with: the keyword with is required to indicate where the expression ends
var (a variable)
version (version/release number)
and template can be:
list of variables
column number delimiters
literal delimiters
upper is optional; if specified, data will be converted to upper case before parsing.
Examples
Using a list of variables as template
myVar="John Smith"parsevarmyVarfirstNamelastName say"First name is:"firstName say"Last name is:"lastName
displays the following:
First name is: JohnLast name is: Smith
Using a delimiter as template:
myVar="Smith, John"parsevarmyVarLastName","FirstName say"First name is:"firstName say"Last name is:"lastName
also displays the following:
First name is: JohnLast name is: Smith
Using column number delimiters:
myVar="(202) 123-1234"parsevarMyVar2AreaCode57SubNumber say"Area code is:"AreaCode say"Subscriber number is:"SubNumber
displays the following:
Area code is: 202Subscriber number is: 123-1234
A template can use a combination of variables, literal delimiters, and column number delimiters.
INTERPRET
The INTERPRET instruction evaluates its argument and treats its value as a Rexx statement. Sometimes INTERPRET is the clearest way to perform a task, but it is often used where clearer code is possible using, e.g., value().
Other uses of INTERPRET are Rexx's (decimal) arbitrary precision arithmetic (including fuzzy comparisons), use of the PARSE statement with programmatic templates, stemmed arrays, and sparse arrays.[how?]
/* demonstrate INTERPRET with square(4) => 16 */X='square'interpret'say'X||'(4) ; exit'SQUARE:returnarg(1)**2
This displays 16 and exits. Because variable contents in Rexx are strings, including rational numbers with exponents and even entire programs, Rexx offers to interpret strings as evaluated expressions.
This feature could be used to pass functions as function parameters, such as passing SIN or COS to a procedure to calculate integrals.
Rexx offers only basic math functions like ABS, DIGITS, MAX, MIN, SIGN, RANDOM, and a complete set of hex plus binary conversions with bit operations. More complex functions like SIN were implemented from scratch or obtained from third party external libraries. Some external libraries, typically those implemented in traditional languages, did not support extended precision.
Later versions (non-classic) support CALL variable constructs. Together with the built-in function VALUE, CALL can be used in place of many cases of INTERPRET. This is a classic program:
/* terminated by input "exit" or similar */doforever;interpretlinein();end
A slightly more sophisticated "Rexx calculator":
X='input BYE to quit'dountilX='BYE';interpret'say'X;pullX;end
PULL is shorthand for parse upper pull. Likewise, ARG is shorthand for parse upper arg.
The power of the INTERPRET instruction had other uses. The Valour software package relied upon Rexx's interpretive ability to implement an OOP environment. Another use was found in an unreleased Westinghouse product called Time Machine that was able to fully recover following a fatal error.
e = 2.7182818284590452353602874713526624977572470936998
SIGNAL
The SIGNAL instruction is intended for abnormal changes in the flow of control (see the next section). However, it can be misused and treated like the GOTO statement found in other languages (although it is not strictly equivalent, because it terminates loops and other constructs). This can produce difficult-to-read code.
Error handling and exceptions
It is possible in Rexx to intercept and deal with errors and other exceptions, using the SIGNAL instruction. There are seven system conditions: ERROR, FAILURE, HALT, NOVALUE, NOTREADY, LOSTDIGITS and SYNTAX. Handling of each can be switched on and off in the source code as desired.
The following program will run until terminated by the user:
signalonhalt;doa=1saya do100000/* a delay */endendhalt:say"The program was stopped by the user"exit
A signalonnovalue statement intercepts uses of undefined variables, which would otherwise get their own (upper case) name as their value. Regardless of the state of the NOVALUE condition, the status of a variable can always be checked with the built-in function SYMBOL returning VAR for defined variables.
The VALUE function can be used to get the value of variables without triggering a NOVALUE condition, but its main purpose is to read and set environment variables, similar to POSIXgetenv and putenv.
Conditions
ERROR
Positive RC from a system command
FAILURE
Negative RC for a system command (e.g. command doesn't exist)
HALT
Abnormal termination
NOVALUE
An unset variable was referenced
NOTREADY
Input or output error (e.g. read attempts beyond end of file)
SYNTAX
Invalid program syntax, or some other error condition
LOSTDIGITS
Significant digits are lost (ANSI Rexx, not in TRL second edition)
When a condition is handled by SIGNAL ON, the SIGL and RC system variables can be analyzed to understand the situation. RC contains the Rexx error code and SIGL contains the line number where the error arose.
Beginning with Rexx version 4 conditions can get names, and there's also a CALL ON construct. That's handy if external functions do not necessarily exist:
ChangeCodePage:procedure/* protect SIGNAL settings */signalonsyntaxnameChangeCodePage.Trap returnSysQueryProcessCodePage()ChangeCodePage.Trap:return1004/* windows-1252 on OS/2 */
↑ The TSO EXEC command with an unqualified dataset name and neither the CLIST nor EXEC option examines the low level qualifier or EXEC.
↑ If the first line of a script fetched from SYSPROC is a comment containing REXX then it is treated as REXX rather than CLIST. A script fetched from SYSEXEC must be REXX.
↑ Rexx has no equivalent to the SELECT (expression); form of SELECT.
Related Research Articles
In computer programming, a macro is a rule or pattern that specifies how a certain input should be mapped to a replacement output. Applying a macro to an input is known as macro expansion. The input and output may be a sequence of lexical tokens or characters, or a syntax tree. Character macros are supported in software applications to make it easy to invoke common command sequences. Token and tree macros are supported in some programming languages to enable code reuse or to extend the language, sometimes for domain-specific languages.
A shell script is a computer program designed to be run by a Unix shell, a command-line interpreter. The various dialects of shell scripts are considered to be scripting languages. Typical operations performed by shell scripts include file manipulation, program execution, and printing text. A script which sets up the environment, runs the program, and does any necessary cleanup or logging, is called a wrapper.
In computer science, an interpreter is a computer program that directly executes instructions written in a programming or scripting language, without requiring them previously to have been compiled into a machine language program. An interpreter generally uses one of the following strategies for program execution:
Parse the source code and perform its behavior directly;
Translate source code into some efficient intermediate representation or object code and immediately execute that;
Explicitly execute stored precompiled bytecode made by a compiler and matched with the interpreter's Virtual Machine.
Bytecode is a form of instruction set designed for efficient execution by a software interpreter. Unlike human-readable source code, bytecodes are compact numeric codes, constants, and references that encode the result of compiler parsing and performing semantic analysis of things like type, scope, and nesting depths of program objects.
Mike Cowlishaw is a visiting professor at the Department of Computer Science at the University of Warwick, and a Fellow of the Royal Academy of Engineering. He is a retired IBM Fellow, and was a Fellow of the Institute of Engineering and Technology, and the British Computer Society. He was educated at Monkton Combe School and the University of Birmingham.
In some programming languages, eval, short for the English evaluate, is a function which evaluates a string as though it were an expression in the language, and returns a result; in others, it executes multiple lines of code as though they had been included instead of the line including the eval. The input to eval is not necessarily a string; it may be structured representation of code, such as an abstract syntax tree, or of special type such as code. The analog for a statement is exec, which executes a string as if it were a statement; in some languages, such as Python, both are present, while in other languages only one of either eval or exec is.
TI-BASIC is the official name of a BASIC-like language built into Texas Instruments (TI)'s graphing calculators. TI-BASIC is a language family of three different and incompatible versions, released on different products:
XEDIT is a visual editor for VM/CMS using block mode IBM 3270 terminals.
ARexx is an implementation of the Rexx language for the Amiga, written in 1987 by William S. Hawes, with a number of Amiga-specific features beyond standard REXX facilities. Like most REXX implementations, ARexx is an interpreted language. Programs written for ARexx are called "scripts", or "macros"; several programs offer the ability to run ARexx scripts in their main interface as macros.
CMS EXEC, or EXEC, is an interpreted, command procedure control, computer scripting language used by the CMS EXEC Processor supplied with the IBM Virtual Machine/Conversational Monitor System (VM/CMS) operating system.
EXEC 2 is an interpreted, command procedure control, computer scripting language used by the EXEC 2 Processor originally supplied with the CMS component of the IBM Virtual Machine/System Product (VM/SP) operating system.
NetRexx is an open source, originally IBM's, variant of the REXX programming language to run on the Java virtual machine. It supports a classic REXX syntax, with no reserved keywords, along with considerable additions to support object-oriented programming in a manner compatible with Java's object model, yet can be used as both a compiled and an interpreted language, with an option of using only data types native to the JVM or the NetRexx runtime package. The latter offers the standard Rexx data type that combines string processing with unlimited precision decimal arithmetic.
This article compares a large number of programming languages by tabulating their data types, their expression, statement, and declaration syntax, and some common operating-system interfaces.
A batch file is a script file in DOS, OS/2 and Microsoft Windows. It consists of a series of commands to be executed by the command-line interpreter, stored in a plain text file. A batch file may contain any command the interpreter accepts interactively and use constructs that enable conditional branching and looping within the batch file, such as IF, FOR, and GOTO labels. The term "batch" is from batch processing, meaning "non-interactive execution", though a batch file might not process a batch of multiple data.
LOLCODE is an esoteric programming language inspired by lolspeak, the language expressed in examples of the lolcat Internet meme. The language was created in 2007 by Adam Lindsay, a researcher at the Computing Department of Lancaster University.
C# Open Source Managed Operating System (Cosmos) is a toolkit for building GUI and command-line based operating systems, written mostly in the programming language C# and small amounts of a high-level assembly language named X#. Cosmos is a backronym, in that the acronym was chosen before the meaning. It is open-source software released under a BSD license.
The syntax and semantics of PHP, a programming language, form a set of rules that define how a PHP program can be written and interpreted.
A scripting language or script language is a programming language that is used to manipulate, customize, and automate the facilities of an existing system. Scripting languages are usually interpreted at runtime rather than compiled.
PL/SQL is Oracle Corporation's procedural extension for SQL and the Oracle relational database. PL/SQL is available in Oracle Database, Times Ten in-memory database, and IBM Db2. Oracle Corporation usually extends PL/SQL functionality with each successive release of the Oracle Database.
↑ EXEC 2 Reference(PDF) (Seconded.). International Business Machines Corporation. April 1982. p.92. SC24-5219-1. Archived from the original(PDF) on April 2, 2020. Retrieved March 28, 2019.
1 2 M. F. Cowlishaw (1984). "The design of the REXX language"(PDF). IBM Systems Journal (PDF). 23 (4). IBM Research: 333. doi:10.1147/sj.234.0326. Retrieved January 23, 2014. Could there be a high astonishment factor associated with the new feature? If a feature is accidentally misapplied by the user and causes what appears to him to be an unpredictable result, that feature has a high astonishment factor and is therefore undesirable. If a necessary feature has a high astonishment factor, it may be necessary to redesign the feature.
↑ Lundin, Leigh; Woodruff, Mark (April 23, 1987). "T/REXX, a REXX compiler for CMS". U.S. Copyright Office (TXu000295377). Washington, DC: Independent Intelligence Incorporated. Archived from the original on March 3, 2016. Retrieved February 20, 2010.
Callaway, Merrill. The ARexx Cookbook: A Tutorial Guide to the ARexx Language on the Commodore Amiga Personal Computer. Whitestone, 1992. ISBN978-0963277305.
Callaway, Merrill. The Rexx Cookbook: A Tutorial Guide to the Rexx Language in OS/2 & Warp on the IBM Personal Computer. Whitestone, 1995. ISBN0-9632773-4-0.
Cowlishaw, Michael. The Rexx Language: A Practical Approach to Programming. Prentice Hall, 1990. ISBN0-13-780651-5.
Cowlishaw, Michael. The NetRexx Language. Prentice Hall, 1997. ISBN0-13-806332-X.
Daney, Charles. Programming in REXX. McGraw-Hill, TX, 1990. ISBN0-07-015305-1.
Ender, Tom. Object-Oriented Programming With Rexx. John Wiley & Sons, 1997. ISBN0-471-11844-3.
Fosdick, Howard. Rexx Programmer's Reference. Wiley/Wrox, 2005. ISBN0-7645-7996-7.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
