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

RE: BRMS migration / restore using 4 drives, submitted to batch - LCKW issue

Rob,

BRMS is already do this automatically.
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72/brms/bkumisobj.htm
Any missed IFS object is written to a Z... list within the control group you specify.

Missed object policy . . . . . . . . . . SAVMISS05 Name, *NONE, *BKUPCY
Clear missed objects . . . . . . . . . *YES *NO, *YES

Z732720001 *BKU *LNK Entry created by BRM configuration

policy-name
Specifies the name of the backup control group and
lists to use for tracking missed objects during backup
control group processing.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Wednesday, January 16, 2019 3:07 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS migration / restore using 4 drives, submitted to batch - LCKW issue

Nice.

Actually their 5250 interface could use a little work. For example there's CHGLNKLBRM but there's no ADDLNKLBRM type command. Where this would be useful is some process which analyzes the joblog, and for every message that the object was skipped (providing necessary criteria were met) do an ADDLNKLBRM to omit that additional entry.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Wednesday, January 16, 2019 2:39 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: BRMS migration / restore using 4 drives, submitted to batch - LCKW issue

Earlier we were discussing attributes that can only be changed in the GUI.
Apparently IBM was listening:

https://www.ibm.com/developerworks/community/wikis/home?lang=en_us#!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Change%20GUI%20only%20control%20groups%20attributes

Interface to change GUI only control groups attributes

In PTF for 7.2 SI68567
<http://www-01.ibm.com/support/docview.wss?uid=nas3SI64248>and for SI68568 <http://www-01.ibm.com/support/docview.wss?uid=nas3SI64250>7.3,
enhancements have been made to change the GUI only control group attributes for TCP/IP servers, unmount user-defined file systems, and run maintenance after backup.

Interface to control which control group will not use the select user space code.

- Parm1: (Input, char 10) OL Identifier CHGCTLGATR
- Parm2: (Input, char 10) Control group name
- Parm3: (Input, char 10) Control group attribute

Special values allowed:

- *TCPSERVER – TCP/IP srevers
- *UNMNTUDFS – Unmount user-defined file systems
- *RUNMAINT – Run maintenance after backup



- Parm4: (Input, char 10) Attribute Value object list name - name or *ALL

Valid attribute values:

- If Parm 3 is *TCPSERVER only *NO, *END, *RESTART or *BOTH are allowed
- If Parm 3 is *UNMNTUDFS or *RUNMAINT only *NO or *YES are allowed

*Examples*

CALL PGM(QBRM/Q1AOLD) PARM('CHGCTLGATR' ‘MYCTLGNAME’ '*TCPSERVER’
‘*END ‘)

CALL PGM(QBRM/Q1AOLD) PARM('CHGCTLGATR' ‘MYCTLGNAME’ '*UNMNTUDFS’
‘*YES ‘)

CALL PGM(QBRM/Q1AOLD) PARM('CHGCTLGATR' ‘MYCTLGNAME’ '*RUNMAINT ‘ ‘*YES
‘)

-

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Wed, Jan 16, 2019 at 11:29 AM Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

Rob,

These are dedicated restores, not saves.
The restore is from a dedicated system save, using 4 drives, no SWA.

The SWA 120 wait only applies for library objects, not IFS objects.
IFS objects are immediately skipped, there is no wait time.

I possibly have identified the source of the LCKW.
X-lib LF causing IDX rebuilds which puts locks on the PF.
The other restore job(s) are trying to restore LF over a locked PF.

If you only ran one restore job, you would not have this issue,
however, total migration time will be longer.
If you ran the processes interactively, you also would not see this issue.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Rob Berendt
Sent: Wednesday, January 16, 2019 10:48 AM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS migration / restore using 4 drives, submitted to
batch - LCKW issue

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

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

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