Re: Resolving to REXX procedures -- MIDRANGE-L

× 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.

Subject: Re: Resolving to REXX procedures
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Mon, 21 Apr 2008 12:45:30 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

lgoodbar@xxxxxxxxxxxxxx wrote:

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.

Does the command have a "product library" set?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Resolving to REXX procedures , lgoodbar

This mailing list archive is Copyright 1997-2025 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.