Re: [WDSCI-L] re: iSeries Projects

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Thanks, Diz.

My main issue now is, if I pull something from a location, why is it pushed 
somewhere else?

I can see numerous times where source could come from different places - a 
fix could involve both objects in common and specific to a product. A 
project could be set up for the entire product and would automatically pull 
from multiple sources. But I'd never want all that source to go somewhere 
else than where I took it from.

The CM products will pull things into a development area, as ACMS and 
TurnOver do - then promote up to QA and integration, and finally production 
(I forget TurnOver's versions of these terms as used in ACMS - sorry, 
Mark  ;-)  I had more time with ACMS, although I recommended TurnOver at a 
later job.). I can see this project model working when there is extensive 
software control of where things are.

It seems I'd be better off using a member (maybe object?) filter, adding 
the references to what I need at the time. This'd work OK, I think.

Oh, well, I was hoping for a poor-man's change management system. Sigh!

Now, how about including source from disparate systems - consider a Delphi 
GUI that uses certain iSeries programs - can they all be included under one 
umbrella somewhere in WDSC?

Regards

Vern

At 07:27 AM 6/6/2003 -0400, you wrote:
> <So, does a project allow you to specify a build program? is this like 
> your "wizard" or "style"? Does this program run in the "associated" 
> library? Are these wizards part of TurnOver or of WDSC?
>
> Later
>
> Vern>

-snip-

> Both of the Program and Command build styles push your source changes back 
> to the project's associated library.  But the source can be pulled into 
> the project from any source library on the iSeries.

-snip-