Re: what had a lock on files trying to restore

[bll1981 <bll1981@xxxxxxxxxxxxx>]

I assume you don't have a license for iDoctor? I cannot recall the exact 
sequence, but if iDoctor job watcher is running you can drill down into lock 
contention statistics which will essentially give you the name of the offending 
process. Usually IBM will cut you a temp license for iDoctor if you ask for it 
or support needs it to solve an issue.

Personally speaking, if this is an isolated occurrence I would let it go. The 
trick to iDoctor is to have it running while the "problem" happens which is 
unlikely unless there is a failure pattern.  




________________________________
From: "franz400@xxxxxxxxxxxx" <franz400@xxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Sent: Tue, December 14, 2010 3:05:02 PM
Subject: Re: what had a lock on files trying to restore

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