Re: Logicals on source files?

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

To James - you don't have to create the objects into the same library as 
the source library. We do this all the time - so under programmatic 
control, maybe modify the destination library and just use the source in 
its sole location.

Eh?
Vern

On 3/30/2011 8:24 AM, Needles,Stephen J wrote:
> James,
>
> We had something similar where I used SQL ALIAS's to point to specific source members as needed, copied the contents to the member into a source PF in QTEMP, compiled the object and trashed the QTEMP stuff when finished.
>
> Perhaps something like this will work for you?
>
> Steve Needles
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
> Sent: Monday, March 28, 2011 11:06 AM
> To: Midrange Systems Technical Discussion
> Subject: Logicals on source files?
>
> An idea that just occurred to me:
>
> We have situations in which a source codebase in one library has to be
> compiled, *under programmatic control* in other libraries. For
> maintenance purposes, we don't want source scattered across the various
> target libraries.
>
> Is it possible to (1) set up logicals of source files in the target
> libraries, with all the members visible, and (2) use them for compilation?
>
> (I'm about to undertake about a half-hour exercise in manually
> recompiling a bunch of stuff in precisely the situation I described, or
> I'd research it myself before asking about it.)
>
> --
> JHHL