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

Subject: Restoring QSYS2
From: Matt Gross <prrgg1@xxxxxxxxxxxxx>
Date: Wed, 23 Aug 2006 06:23:20 -0700 (PDT)
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I was unaware of QSYS2 being part of *ALLUSR starting in V5R2.  When this was 
recently restored during a disaster recovery test,  it created a nightmare.
   
  I've heard of two ways to deal with this...
   
  1)  Don't back it up & don't restore it or *Omit this library when running 
*ALLUSR portion of restore.
   
  2)  Before restoring *ALLUSR - Immediately after RTVUSRPRF, run RSTAUT and 
this will take care of it.
   
  Do we need this library restored in the event of a disaster?
   
  Any suggestions much appreciated.
   
  Matt

As an Amazon Associate we earn from qualifying purchases.

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.