×
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.
I'm working on a utility that will update a "application environment"
library by pulling in file definitions from another environment library
(the "source" library, usually a "test" version of the application
environment) and applying them to the existing data in the "target"
library (usually a "production" version of the product environment).
Scenario: Universal Foobar has been running the application on the
environment in the FOO_PROD library for some time, but they have
prepared an improved version of the database, and have been running
tests on a modified version in the FOO_TEST library. They are now
satisfied that the environment as defined in FOO_TEST is going to work
as advertised, and want to put that version into production.
So for this utility that programmatically upgrades FOO_PROD to the new
data definitions in FOO_TEST, should the command be
UPDATEFOO FOO_TEST FOO_PROD
or should it be
UPDATEFOO FOO_PROD FOO_TEST
???
--
JHHL
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
