Rob,
I have a very similar control group for system saves.
I'm still puzzled why the recovery report is stating this.
Researching this further, the first recovery report following the system sate states it differently.
__ STEP 001 : Recover Licensed Internal Code
Start date/time __________________ Stop date/time __________________ Duration _________________
You must recover the Licensed Internal Code.
To do so, you must follow the procedures for "Recovering the Licensed
Internal Code" as detailed in the "Recovering your system" topic.
Use the media listed for the *SAVSYS saved item to recover the
Licensed Internal Code.
The Licensed Internal Code distribution media will be required in
addition to the *SAVSYS saved item to recover the system.
__ STEP 002 : Recover Operating System
Start date/time __________________ Stop date/time __________________ Duration _________________
You must recover the Operating System.
Edit Backup Control Group Entries PENCOR05
Group . . . . . . . . . . : SAVSYS05
Default activity . . . . . *BKUPCY
Text . . . . . . . . . . . Pencor05 System Save
Type information, press Enter.
Weekly Retain Save SWA
Backup List ASP Activity Object While Message Sync
Seq Items Type Device SMTWTFS Detail Active Queue ID
10 *EXIT *******
20 *SAVSYS FFFFFFF
30 *IBM *SYSBAS FFFFFFF *NO *NO
40 *ALLUSR *SYSBAS FFFFFFF *ERR *NO
50 *ALLDLO FFFFFFF *NO *NO
60 *LINK *ALLAVL FFFFFFF *YES *NO
70 *EXIT *******
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, October 27, 2016 3:31 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS recovery report questions/issues
When you do your system save you ARE using BRMS right? You're not using GO SAVE, 21 or anything like that, are you?
A control group for full system save may look like the following:
Weekly Retain Save
Backup List ASP Activity Object While
Seq Items Type Device SMTWTFS Detail Active
10 *SAVSYS *DFTACT
20 *IBM *SYSBAS *DFTACT *ERR *NO
30 *ALLUSR *SYSBAS *DFTACT *OBJ *NO
40 *ALLDLO *DFTACT *NO *NO
50 *LINK *ALLAVL *DFTACT *YES *NO
Key thing being we:
- Use BRMS to also do our dedicated full system saves.
- Use a different control group for our dedicated full system saves than we do for our other saves.
I cannot recall the last time we used GO SAVE, 21. Even for an unload/reload. This is where Jim and I differ. Personally I find that doing it in BRMS really builds your confidence in the brms recovery strategy.
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: 10/27/2016 03:23 PM
Subject: RE: BRMS recovery report questions/issues
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Here's some additional issues
If I just did a system save, why am I seeing this on the BRMS recovery
report.
Stating both LIC and OS has NOT been saved.
STEP 001 : Recover Licensed Internal Code
Start date/time __________________ Stop date/time __________________
Duration _________________
----- Attention ---------------------------------------------------
The Licensed Internal Code has not been saved.
---------------------------------------------------------------------
Since the Licensed Internal Code has not been saved, you must use the
distribution media and the procedure for "Recovering the Licensed
Internal Code" as detailed in the "Recovering your system" topic.
STEP 002 : Recover Operating System
Start date/time __________________ Stop date/time __________________
Duration _________________
----- Attention
---------------------------------------------------
The operating system has not been saved.
---------------------------------------------------------------------
Since the operating system has not been saved, you must use the
distribution media and the procedure for "Restoring the Operating
System as detailed in the "Recovering your system" topic.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Thursday, October 27, 2016 2:37 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS recovery report questions/issues
Rob and Marc,
You both hit the nail on the head.
USEDUPMED defaults to *NO.
I changed it to *YES, all old volumes disappeared from the report.
However, I run the recovery report via STRMNTBRM.
When run this way, you lose the ability to change USEDUPMED from *NO to
*YES.
I may have to :
CHGCMDDFT CMD(QBRM/STRRCYBRM) NEWDFT('USEDUPMED(*YES)')
SHWDLTLIB only became available with V7R2.
I'm not seeing that option with V7R1.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Thursday, October 27, 2016 2:22 PM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS recovery report questions/issues
STRRCYBRM
Maybe it's a translation thing, but is this the option you're talking
about
Show deleted libraries . . . . . SHWDLTLIB *YES
if he changes that to *NO they will drop off the recovery report?
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: Marc Rauzier <marc.rauzier@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 10/27/2016 01:55 PM
Subject: Re: BRMS recovery report questions/issues
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Le 27/10/2016 à 16:39, Steinmetz, Paul a écrit :
Rob,
We keep our month end saves forever, auditing requirements, etc.
Those deleted libraries are on those saves.
I could expire those libraries from those backups.
That would be very time consuming, and not sure it's the proper thing
to
do.
Any other suggestions?
The recovery report helps us in case we need to restore something which is
needed to run daily activities. If you want BRMS to keep track of objects,
but do not want them to remain on the system. You have to use archiving
function. This function has an option to *delete* the objects after save
to tape. And the sequence used to save to tape does not appear in the
Recovery report. However, I am unsure if we can archive a library. We can
do it for some objects types, but not sure for library.
What you can do is archive the objects but keep the library empty.
By the way, there is an OMITLIB parameter, which accepts *DELETE value
which could answer you question.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Berendt
Sent: Thursday, October 27, 2016 10:31 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS recovery report questions/issues
We'll start with 2, the deleted libraries. You still have save copies
of them. They will stay in this fashion until you remove all saves of
them.
Rob Berendt
--
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.
--
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.
--
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.
midrange.com
