RE: BRMS daily save did not do SWA, and did not do incremental

["Lindstrom, Scott R." <slindstrom@xxxxxxxxxx>]

Yep - V5R2.

I ran the recovery report and found it has this:

*********************                                                  
***** ATTENTION *****                                                  
*********************                                                  
Requires recovery from your distribution media.                        
Since the Licensed Internal Code has not been saved, you need to use   
distribution media and the procedure for "Recovering the Licensed      
Internal Code" as detailed in the "Backup and Recovery" book.          

So I think my theory is correct.

Scott Lindstrom
Pactiv Corporation |  Unix, Storage and AS/400 Administrator
605 Heathrow Drive
Lincolnshire, IL 60069
p:847 482 7602   fx:847-615-3560
slindstrom@xxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Thursday, October 06, 2011 11:16 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS daily save did not do SWA, and did not do incremental

Did I really see V5R2?

The way to resolve if your theory is correct is to look at the recovery 
report that is generated with the BRMS maintenance.  It will show you 
how it is planning a recovery.  I suspect you are correct about the 
expired tapes.

SWA at V5R2 was at best not really all that strong, so I am not 
surprised it is not behaving properly.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 10/6/2011 9:16 AM, Lindstrom, Scott R. wrote:
> After running fine for the first couple days my daily save control group did not do a SWA save (no messages were sent to the MSGQ specified), and it appears it did a complete *ALLUSR save (lots of libs were saved that we know hadn't changed since the night before).
>
>
>
> Is there some condition that would cause this?  There are no messages listed anywhere that indicate some unusual situation occurred that caused BRMS to change the way it worked compared to the previous nights.  (V5R2, BTW).
>
>
>
> I have a theory - I did a full system save Sunday night when I took over responsibility for this system that moved here.  Due to a shortage of tapes I have my retention period set to 1 day.  So once I started running STRMNTBRM the full save would have been expired.  Perhaps when BRMS tried to run an incremental save and saw it did not have a 'reference point tape' for the INCR it reverted to a full save.  But there were no messages indicating this is what was happening.  But that doesn't explain why it didn't try to do a SWA.
>
>
>
> Scott Lindstrom