× 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 assuming ownership and authority issues are handled manually so my suggestion is to remove logical files, sql views and sql indexes first then delete tables/files rather than clrlib. This will reduce the number of "old" tables/logicals/views/indexes on the restore. They can be removed using your favorite admin tool to delete them if you don't want to write programs to do it.

Then just do a rstlib.

Thanks,
Gary Monnier
IT Software Engineer CSM, CSPO


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Pavlichek
Sent: Wednesday, January 13, 2016 10:02 AM
To: Midrange List
Subject: Clear or Delete Library

Is there a performance difference between a CLRLIB and DLTLIB? I have a customer who is refreshing over 10TB of data from PROD to DEV using BRMS save/restore and is needing to get the process done quicker.

They are submitting CLRLIBs to batch and are running multiple jobs concurrently. Would single threading these help at all?

Any other suggestions?

Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.