×
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.
Mark S. Waterbury wrote:
If you are going to do all that work, why not just use Alan Campin's
COMPILE command instead?
I'm very familiar with that; I've been using a variant of that concept
for a long time now, but only for those 'funny' sorts of compiles where
PDM option 14 won't do it.
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 sure how to do that in a point and click world. Maybe create a
duplicate set of filters in production so it's easy to select all the
members? This is a company without formal change management software
and unlikely to get it any time soon.
Maybe another, better route is to poke through the files stored in this
directory tree
...\RemoteSystemsTempFiles\MYSYSTEMi\QSYS.LIB\BUCK00002.LIB\... I'll
have to see how hard it will be to read that and create the appropriate
copy/compile commands from the list.
--buck
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
