Library Allocations for Static SQL and Compiled REXX
Describes library allocations for static SQL in compiled REXX applications.
The load modules which contain application static SQL must be accessible to
RLX
through either the standard MVS search order (STEPLIB or the ISPLLIB concatenation) or through the RLX
LOAD private library. If the RLX
LOAD file is allocated (defining the RLX
private load library), then the dataset into which your SQL load module was link-edited must be concatenated to the RLX
LOAD file. Otherwise, RLX
does not find your SQL load module, even if it is allocated to STEPLIB or ISPLLIB. See the first pitfall.In contrast, the compiled REXX load module can only be accessed though the standard MVS search order. The ISPF LIBDEF service is not suitable for either purpose.
Moreover, care must be exercised to ensure that only that version of your
RLX
application which you intend to execute (that is., original REXX, translated REXX, or compiled REXX) is accessible to the system -- otherwise, erroneous results may occur. You should assign unique names to your compiled and interpreted REXX procedures. Alternatively, use the same names for the original, translated, and compiled REXX procedures if EXEC and load module libraries are allocated properly as described in the following two cases.CASE 1:
To run a static SQL plan in conjunction with the precompiled and translated REXX EXEC, ensure that the translated EXEC rather than the original source EXEC is accessible through the standard SYSPROC or SYSEXEC concatenation.CASE 2:
Alternatively, to run compiled SQL together with compiled REXX, ensure that the compiled REXX load module is accessible to RLX
. It is further advisable to ensure that neither the original nor translated REXX procedures appear in the EXEC search order. Otherwise, the system may attempt to interpret the original procedure rather than execute the compiled version.The REXX function search order flag bit named FUNCSOFL governs whether the system searches for a load module before searching for an EXEC of the same name. The REXX parameter module that is named
RLX
ISPRM used by the RLX
S front end directs the system to search for a load module before searching for an EXEC. The IBM supplied the REXX parameter modules IRXPARMS, IRXRSPRM, and IRXISPRM also direct the system to search for a load module before searching for an EXEC. Check with your TSO systems programmer whether this default is overridden at your installation.