Re:RE: Compiling into production libraries -- MIDRANGE-L

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

>>Also, at the sites where the clients have development
>>libraries, there is such a disparity between the development
>>side and the production side that if you move programs from
>>dev to prod they will (dare I say it?) level check..
>
>Which means of course that the program you compile into production is
>not the same as the one you originally compiled and tested (?) in
>development. You are putting untested programs into production..

Dave,
        All too true, but it's as close as we can get at this moment.
That's why I started (and continued) this thread.  I was really hoping
for some practical suggestions that can help us turn things around.
Sigh.

Buck Calabro
Commsoft, Rensselaer, NY

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.