Re: iSeries Projects 'Create compile command'

[Adam Glauser <adamglauser@xxxxxxxxxxxx>]

Buck wrote:
> Mark S. Waterbury wrote:
> > If you are going to do all that work, why not just use Alan Campin's 
> > COMPILE command instead? 

> The reason to capture the compile commands is so I can re-create all the 
> related objects in my test library during testing, but mostly so I can 
> recreate them all once the source gets moved back to production.  The 
> problem isn't the compilation, so much as identifying the members to be 
> compiled.

I'm not quite sure what you mean here.  I think you could all of the 
necessary source in the iSeries project, and have 'COMPILE &L/&N' as 
your last compile command for each source type.  Then, when you do your 
'Remote Actions -> Generate COMPILE.CLLE', you would have a script to 
build all of the objects into the test library associated with your project.

When you want to compile to production, you can change the associated 
library and regenerate the COMPILE.CLLE.  Of course, you still have a 
problem if you want to deploy to multiple libraries, but that is almost 
certainly a case of running into "insert CMS vendor here" line.

I'm probably missing something, but hope that helps anyway.

- Adam