Re: Moving large libraries to another system: -- 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.

Paul wrote:

> How 'bout 2 programs:  At the sending end, it does
> a DSPOBJD to an outfile, reads the outfile, and saves
> each object -individually- to a tiny SAVF.  Then send
> the SAVF to the other end.

The Johnny Cash method - build it one piece at a time. One thing to watch
out for if you do it this way is object dependencies. It's no good trying
to restore a logical file before the physical(s) it depends on. So it might
be a good idea to make sure all the physicals are restored ahead of all the
logicals.

It might also be worth considering whether or not to save access paths. In
most cases it's a good idea, but if bandwidth is important and rebuild time
on the target machine is not an issue it might be better not to save them.

Dave...
               _________  ,___o
             __________   _\ <;_
           ___________   (_)/ (_)       http://www.twickenhamcc.co.uk
=======================================================
The opinions expressed in this communication are my own and do not
necessarily reflect those of my employer.

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.