In a message dated 3/5/02 9:49:39 PM Pacific Standard Time,
[log in to unmask] writes:


> (3)  Create and run ADAGER job that you think
> implements all those changes in production
> (after backing up your database, of course).
>
>

Oh No!  I KNOW that the jobstream implements all those changes... because
it's the SAME jobstream as the one I used to alter the development copy of
the very same database.

Something that those of us with a bit of experience seem to intuitively know
is that implementation of software/data structure changes is not always a
simple affair.  Various things need to all happen together and be properly
incorporated into the regular production environment.  Maybe I am missing
something but all the fancy color/graphics/whizbang/GUI/etc. development
tools are just that - development tools.  I personally would love to know a
lot more about how to put the input of these various tools into simple batch
files and make the results automated and reproducable.

Something that goes along with Ken's approach in it's objective, is a batch
file that makes the actual changes to a dictionary, thus allowing you to run
the changes in a reproducable manner against both a development copy of a
dictionary and then the regular production copy.

Ken's accuracy check method takes only a trivial amount of time to run.  An
ounce of prevention....

Wayne Boyer

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *