Overview of Classes Provided by Rexx

This section gives a brief overview of the classes and methods Rexx defines.

The Class Hierarchy

Rexx provides the following classes belonging to the object class:

(The classes are in a class hierarchy with subclasses indented below their superclasses.)

Note that there might also be other classes in the system, depending on the operating system. Additional classes may be accessed by using an appropriate ::requires directive to load the class definitions.

The following figures show Rexx built-in classes.

Figure 4-1. Classes and Inheritance (part 1 of 9)

Figure 4-2. Classes and Inheritance (part 2 of 9)

Figure 4-3. Classes and Inheritance (part 3 of 9)

Figure 4-4. Classes and Inheritance (part 4 of 9)

Figure 4-5. Classes and Inheritance (part 5 of 9)

Figure 4-6. Classes and Inheritance (part 6 of 9)

Figure 4-7. Classes and Inheritance (part 7 of 9)

Figure 4-8. Classes and Inheritance (part 8 of 9)

Figure 4-9. Classes and Inheritance (part 9 of 9)

Class Library Notes

The chapters that follow describe the classes and other objects that Rexx provides and their available methods. Rexx provides the objects listed in these sections and they are generally available to all methods through environment symbols (see Environment Symbols).


  1. In the method descriptions in the chapters that follow, methods that return a result begin with the word "returns".

  2. For [] and []= methods, the syntax diagrams include the index or indexes within the brackets. These diagrams are intended to show how you can use these methods. For example, to retrieve the first element of a one-dimensional array named Array1, you would typically use the syntax:


    rather than:


    even though the latter is valid and equivalent. For more information, see Message Terms and Message Instructions.

  3. When the argument of a method must be a specific kind of object (such as array, class, method, or string) the variable you specify must be of the same class as the required object or be able to produce an object of the required kind in response to a conversion message. In particular, subclasses are acceptable in place of superclasses (unless overridden in a way that changes superclass behavior), because they inherit a suitable conversion method from their Rexx superclass.

    The isA method of the Object class can perform this validation.