×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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)
rexsrcmbr(*cmd)
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).
HTH,
Loyd
Loyd Goodbar
Business Systems
BorgWarner Shared Services
662-473-5713
-----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
Hi,
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 ?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
