Keep in mind that SWA is a sick joke when dealing with IFS stuff and if you're default wait time is 120 seconds then for every IFS object locked you've just added two minutes on to the run time.
There's also a few qsys.lib objects in which SWA will not save if they are locked. *USRQ, *USRIDX and that genre comes to mind. Again the default wait time comes in play.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Wednesday, January 16, 2019 10:43 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: BRMS migration / restore using 4 drives, submitted to batch - LCKW issue
5=Work with
12. Work with locks, if active
8=Work with object locks
I tend to run such migration saves interactive, from the console, on a dedicated system.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steinmetz, Paul
Sent: Wednesday, January 16, 2019 9:38 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: BRMS migration / restore using 4 drives, submitted to batch - LCKW issue
Testing a BRMS migration/restore, using 4 drives, submitted to batch.
I'm seeing some of the restore jobs sitting in a LCKW status.
Anyone in the group experience this or know how to determine what is causing the LCKW.
QBATCH QSYS SBS .0 DEQW
VOL1301 QSECOFR BCH 3.5 PGM-Q1AC2RCY RUN
VOL1316 QSECOFR BCH 1.7 PGM-Q1AC2RCY LCKW
VOL1327 QSECOFR BCH .1 PGM-Q1AC2RCY LCKW
VOL1328 QSECOFR BCH .1 PGM-Q1AC2RCY LCKW
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.