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



It depends on who created them and why. If they're temporary objects used to 
support the functioning of a program then they don't have to be saved and 
should probably be cleared from the system. If they're logs of past events then 
they should be saved, but you might want to do a selective purge of spaces that 
are so old they're not of any use anymore. There is a small chance they might 
contain vital information, but this isn't very likely.
  ----- Original Message ----- 
  From: Burns, Bryan 
  To: MIDRANGE-L@xxxxxxxxxxxx 
  Sent: Tuesday, August 29, 2006 10:22 AM
  Subject: Saving user spaces


  One of our company's nightly SAVLIB routine includes a library, IBSAISLOG, 
which consists of 230,000 *USRSPC objects.  The owner of the user spaces is 
QTMHHTP1 and the user spaces are the only type of objects in the library.

  Needless to say, the SAVLIB slows down when it hits the IBSAISLOG lib. Does 
it make sense to backup user spaces?  



  Bryan Burns
  M.I.S. Department
  ECHO, Incorporated


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

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.