Re: Re: iSeries Project -- WDSCI-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.

We use one library for source that is common to multiple products, as well as separate product source libraries. So this model does not work for us. Build scripts (CL) need to refer to both, as well as, possible, the destination libraries, too. Because of this limitation, I've rejected the Projects concept in WDSC. In addition, source members are not handled in the same way as they are in the RSE perspective, IIRC. Many problems at this time that made this otherwise attractive prospect mostly unusable.

Vern

At 04:58 PM 6/5/2003 -0500, you wrote:

  You would create a project for each library or create new library(s) to
better organize your source. Typically a library associates to a "project",
"application", or "system".

"Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>
wrote in message
news:2497EFFF2CEDF746A51832AD269D45D947E321@xxxxxxxxxxxxxxxxxxxxxxxxx
> I am attempting to use iSeries Projects and it is asking me to specify an
> "Associated Library".  What if we happen to have more than one library on
> our system that we store code in?
>
> Aaron Bartell

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.