Resolving to REXX procedures

[<lgoodbar@xxxxxxxxxxxxxx>]

Since REXX is the hot topic today, here's a question on resolving to a
REXX procedure.

 

I have a command called DOREX in library PRODLIB, which points to
*LIBL/QREXSRC, DOREX. As long as PRODLIB is at the top of my library
list, all is well.

 

In my development environment, I have LOYD then PRODLIB in my library
list. LOYD has an empty QREXSRC source file. LOYD also has a program
WHERESREX. If I run LOYD/WHERESREX, which tries to call *LIBL/DOREX, I
get an error CPF7CF2, "REXX procedure DOREX not found."

 

The problem occurs because:

Library PRODLIB, command DOREX points to *LIBL/QREXSRC.

Library LOYD, higher in the library list, also has a QREXSRC file, but
without the DOREX member.

 

Other than hard coding the REXX procedure library in the command, is
there a way to work around this? I seem to recall my change management
system (Aldon) has some difficulty with specifying compile options (&LIB
not allowed for parameter REXSRCFILE and such). I'll bug them about this
also.

 

Loyd Goodbar

Business Systems

BorgWarner Shared Services

662-473-5713