|
Rob,
I do not keep object level detail.
But why would it be there for some objects and not others?
Weekly Retain Save
SWA
Backup List ASP Activity Object While
Message Sync
Seq Items Type Device SMTWTFS Detail Active Queue
ID
10 *EXIT *******
20 *SAVSECDTA FFFFFFF *NO
30 *SAVCFG FFFFFFF *NO
40 *ALLUSR *SYSBAS FFFFFFF *ERR *YES QSYSOPR
*NONE
50 *ALLDLO FFFFFFF *NO *YES
60 *LINK *ALLAVL FFFFFFF *NO *NO
70 *EXIT *******
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Tuesday, January 17, 2017 3:14 PM
To: Midrange Systems Technical Discussion
Subject: RE: RSTOBJBRM fails with BRM1681 - Message . . . . : Save
level *CURRENT of object PEWPHY01 type *ALL library BRFILES not restored.
Perhaps, to keep your BRMS file sizes down, you don't record object detail?
"Retain object detail" (OBJDTL)
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 01/17/2017 03:06 PM
Subject: RE: RSTOBJBRM fails with BRM1681 - Message . . . . : Save
level *CURRENT of object PEWPHY01 type *ALL library BRFILES
not restored.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Rob,
The ones that restore appear in WRKOBJBRM.
The ones that fail do not appear in WRKOBJBRM.
So BRMS is only seeing "some" objects, even though they are all there.
What would cause this?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Tuesday, January 17, 2017 2:58 PM
To: Midrange Systems Technical Discussion
Subject: RE: RSTOBJBRM fails with BRM1681 - Message . . . . : Save
level *CURRENT of object PEWPHY01 type *ALL library BRFILES not restored.
WRKMEDIBRM LIB(ROB)
only shows
Volume Creation Expiration
Serial Status Date Date Location
G04001 *ACT 03/11/16 02/25/17 GRRTVTL
However
WRKOBJBRM OBJ(ROB/SPOOL) OBJTYPE(*FILE) shows
Save Save
Object Library Type Date Time Volume
SPOOL ROB *FILE 3/11/16 18:15:35 G04001
SPOOL ROB *FILE 6/11/16 9:55:07 G04006
SPOOL ROB *FILE 6/11/16 22:48:58 G04005
SPOOL ROB *FILE 9/17/16 8:45:45 G00142
SPOOL ROB *FILE 12/10/16 7:39:01 G00197
Now which one is *CURRENT? I suspect G00197.
Why does WRKMEDIBRM only show the one volume? I have no idea.
PS: The system I am working on is only saved once a quarter.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 01/17/2017 02:39 PM
Subject: RE: RSTOBJBRM fails with BRM1681 - Message . . . . : Save
level *CURRENT of object PEWPHY01 type *ALL library BRFILES not
restored.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Current volume is TAPMLB01.
A dup of current volume is offsite.
Some objects from the same save do succeed.
Some objects from the same save also fail.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob
Berendt
Sent: Tuesday, January 17, 2017 2:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: RSTOBJBRM fails with BRM1681 - Message . . . . : Save
level *CURRENT of object PEWPHY01 type *ALL library BRFILES not restored.
Is the volume id holding the current level offsite and the volume id
currently in TAPMLB01 a day or so older?
Don't confuse "current level" with "target release". They are unrelated.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 01/17/2017 02:30 PM
Subject: RSTOBJBRM fails with BRM1681 - Message . . . . : Save
level *CURRENT of object PEWPHY01 type *ALL library BRFILES not
restored.
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Trying to restore an object using RSTOBJBRM.
RSTOBJBRM OBJ(PEWPHY01) SAVLIB(BRFILES) DEV(TAPMLB01) RSTLIB(PAULS)
FROMSYS(PENCOR05)
Fails with BRM1681 - Message . . . . : Save level *CURRENT of object
PEWPHY01 type *ALL library BRFILES not restored.
If I use WRKMEDIBRM
7=Restore
7=Specify object
Restore is successful.
I tried some other objects, some work, some fail.
Anyone have similar issues with RSTOBJBRM?
BRM1681 Diagnostic 40 01/17/17 13:32:12.283206 Q1ACRO
QBRM *STMT QCMD QSYS 01C8
From module . . . . . . . . :
Q1ACRO
From procedure . . . . . . :
Q1ACRO
Statement . . . . . . . . . : 837
Message . . . . : Save level
*CURRENT of object PEWPHY01 type *ALL library
BRFILES not restored.
Cause . . . . . : Save level *CURRENT of object PEWPHY01 type *ALL
library
BRFILES could not be restored because the specified level does not
exist.
Recovery . . . : Use Work with Media Information (WRKMEDIBRM) command
specifying LIB(BRFILES) to review the save information that is
currently
available. Use options to work with saved objects or to restore as
appropriate, or use Restore Object (RSTOBJ) command specifying
OBJ(PEWPHY01)
SAVLIB(BRFILES) OBJTYPE(*ALL) as other parameters (VOL, SEQNBR,
etc.) as
appropriate based on the media information which you reviewed.
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
http://www.pencor.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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
