RE: method to view objects in production lib with locks on them

Joel,

Any update on your SWA?
Can you send a clip from the joblog showing your save command, with all parameters?
What are your SWA wait time setting?

I'm having SWA IFS issues, which may be slightly different.

Paul.



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Monday, August 25, 2014 11:35 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: method to view objects in production lib with locks on them

Joel,

We've used SWA for decades, prior SAVLIB, currently BRMS.
We don't shut anything down, but very limited activity (lt 5 interactive users, no batch jobs) Never had any issues with locks on libraries with SWA, only with IFS objects.

Both SAVLIB and/or BRMS save has an option Object pre-check . . . . . . . . *NO
Default is no.
I've never used it, you may want to test/try it.

Can you send a clip from the joblog showing your save command, with all parameters?

Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Darryl Freinkel
Sent: Monday, August 25, 2014 10:35 PM
To: Midrange Systems Technical Discussion
Cc: Midrange Systems Technical Discussion
Subject: Re: method to view objects in production lib with locks on them

I had the same problem with a backup routine. I do not have the code with me, but what I did was use the features in the SAVLIB command to output the list of objects. Then if the save fails to lock any objects, it does not start the save. I then have the out file with the details of objects that cannot be saved. I use that information with API's to track the locking jobs, which I then end immediately. The program then loops back and does the save again. It works and we now get all objects saved that save while active cannot save.


Darryl Freinkel
Dfreinkel@xxxxxxxxxxxxxxxxx

On Aug 25, 2014, at 4:50 PM, "Stone, Joel" <Joel.Stone@xxxxxxxxxx> wrote:

Each evening we bring down all users and run save-while-active on production files.

Once in a while the save-while-active job cannot get a lock on a file.

After bringing down the online system, we would like to run a job prior to the save that sends a text message to a few people showing the JOB/lib/file of any production objects with a lock on them.

This would avoid the scenario where the SAVE job cannot get a lock on each and every object for a moment.

Is a good method to DSPOBJD to an outfile of all PFs in the lib, and then RCVF thru the outfile with ???

Would it only be necessary to check PFs? Ie would a LF lock also show that the underlying PF has a lock?

Then what? ALCOBJ to each object, trying to get a *EXCL lock on it? And if ALCOBJ fails, then send a text message?

Is there a TAATOOL that will accomplish this? Or maybe a different OS400 tool?

Thanks!



______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
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.

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