|
Generating load modules: Before you can use an object module, you must
link it to the appropriate stub (a stub transforms input parameters into a
form understandable by the compiled REXX program). This can be done with
the REXXL cataloged procedure supplied by IBM, which is listed under
"REXXL (EAGL)" in topic APPENDIX1.D.6, with the REXXL EXEC explained in
"REXXL (z/OS)" in topic 1.6.2.5, or with the REXXC EXEC as described in
"Invoking the Compiler with the REXXC (FANC) EXEC" in topic 1.2.1.1.
Stubs are provided for the parameter-passing conventions as described in
"Stubs" in topic APPENDIX1.A.3.
After you have linked the modules to the appropriate stubs, you can use
the modules in the same way you use modules of other high-level language
compilers.
Notes:
1. By default, the link-edit step adds a dollar ($) sign to the beginning
of the temporary name. If the name consists of 8 characters, the last
character is dropped. That is why you must not use 8-character names
that differ only in the eighth character, for load modules that are
made up of multiple object modules.
To avoid renaming it is recommended that you use a %STUB definition as
described in "%STUB" in topic 1.3.2.4.
2. Compiled programs linked with RENT modules located in an APF library
can cause a system abend in the module IRXSTAMP. To avoid this
problem, compile the program using the CONDENSE option. The compiled
program is uncondensed at runtime and the storage is getmained in the
TSO subpool 78 for execution of the program. For information on the
CONDENSE compiler option, see "CONDENSE" in topic 1.3.1.5.
3. Object modules generated with STUB code terminate abnormally if they
are run under z/VM.
Subtopics:
|
IBM Compiler and Library for REXX on zSeries V1R4 User's Guide and Reference
Copyright IBM Corporation 1990, 2014