Re: SAVLIBBRM and the SAVACTWAIT parameter

[Evan Harris <spanner@xxxxxxxxxx>]

Hi John

I'm not sure whether this will help you much; I had a similar problem with 
BRMS but I actually wanted to make it wait longer than 120 seconds. 
Personally I wouldn't see a 2 minute wait as an issue :)

In my case I used the SAVWACTMSGQ parameter on the SAVLIBBRM command, 
specifying a message queue monitored by a MONSWABRM command. This was set 
via an *EXIT as the previous entry in the BRMS control group and restarted 
processing when the save while active checkpoint was reached; this actually 
worked better for my purposes than trying to establish a time limit or delay.

I couldn't find anywhere to set or influence the time when I was trying to 
do what you want to do but that's  not to say it doesn't exist !

Hope this helps

Regards
Evan Harris

> I'm currently reviewing a backup policy with a view to introducing weekly 
> cumulative SWA backups using BRMS on a development iSeries (on V5R2M0).
> To cater for the cumulative aspect, it will be necessary for me to specify 
> the reference date/time. Consequently, the save cannot be started using 
> STRBKUBRM (as now) and instead the SAVLIBBRM command will have to be used. 
> SAVLIBBRM has the REFDATE/REFTIME parameters that I require.
> The problem is that there appears to be no SAVACTWAIT parameter on 
> SAVLIBBRM. SAVACTWAIT is available on SAVLIB, allowing the wait for locked 
> objects to be reduced from 120 seconds to something shorter. Does anyone 
> know how I can reduce the 120 second SWA wait in SAVLIBBRM.... or is there 
> another way to use BRMS to perform cumulative backups using SWA and a 
> reference date/time?
> John.