|
>essentially runs them through the prompter in batch. Al, I'm guessing that you do this interactively using a macro? If so, how do you catch the ones that fail? - Dan --- Al Barsa <barsa@barsaconsulting.com> wrote: > > I've used this command, and it does a good, but not perfect job. On > each > release, I retrieve all of the commands on the system, and then run > the > source through my own code that essentially runs them through the > prompter > in batch. 99% prompt properly, but there is that less than 1% that > fails. > The other advantage of running them through the prompter is that they > take > considerably less disk space. What Dave essentially does is put each > parameter on it's own source line, which adds considerably to the > size of > the source members. > > Al __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
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.