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


  1.  Home
  2. MIDRANGE-L
  3. December 2010

Re: what had a lock on files trying to restore

Even if checked at start of restore, does not guarantee mid restore issues.
I'm pushing for restricted state.
Later
Jim Franz

---- rob@xxxxxxxxx wrote:
Try skipping the SAVRSTLIB. Instead, save it to a save file, send the
save file over. Lock the library then perform the restore. If the ALCOBJ
of the library fails before the restore begins analyze the object locks
using the appropriate API's and kill the jobs.

Will that work for you?


Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: <franz400@xxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 12/14/2010 04:09 PM
Subject: Re: what had a lock on files trying to restore
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Jim,

Our issue is the restore side of a SAVRSTLIB between two systems.
So far it's looking like there is no better log than the joblog - which
doesn't have what we need.
Jim Franz

---- Jim Oberholtzer <midrangel@xxxxxxxxxx> wrote:
Save While Active? If you have BRMS simply use a separate control group

to manage the whole thing.

In the absence of BRMS kick off the save in a CLP. Send all the SWA
messages to the same queue. Then you will be able to monitor any
checkpoint errors in that message queue.

Other than Apache, domino, and WAS log files, I rarely have trouble with

SWA.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC


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


--
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 ...
Follow-Ups:
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.