I use QREXSRC in each application's library with source type REXX. You
get some JIT performance benefit if you keep the source type as REXX. If
it's a user utility, I front end with a command, and tell it where the
REXX source lives - CRTCMD blah PGM(*REXX) REXSRCFILE(blahlib/qrexsrc)

One caveat on parameter passing between commands and REXX procedures:
dates are passed just as users enter them, instead of being converted to
*CYMD char(7).


Loyd Goodbar
Business Systems
BorgWarner Shared Services
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Monday, July 28, 2008 10:58 AM
To: Midrange Systems Technical Discussion
Subject: Where to put QREXSRC


Having just created my second ever REXX procedure, I just discovered
that when using STRREXPRC the REXX procedure must be in the first
QREXSRC of the library list. How do you chaps normally organise
yourselves for this ?

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page