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