The main concern with save while active on an *ALLUSR is when you use any synch point except *LIB. *SYNCLIB and *SYSDFN may take a LONG time to reach a synchronization point with all of the libraries on the system.

If you use *LIB as the save while active synchronization point you should not have any issues, I do it all the time.

I also use the technique you mention with two control groups, one for restricted state for what ever is needed there, then bring the system back up for use and start a save while active on the other libraries.

I use a control language program to do it so I can manage the shut down and start up properly.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 1/10/2013 1:13 PM, Jeff Crosby wrote:
I read in "Backup Recovery and Media Services
for OS/400: A Practical Approach" (PDF available here: that save while active
is strongly discouraged with *ALLUSR. The last update to this redbook was
2003, so I'm wondering if that's changed. Anyone doing *ALLUSR save while

Another thought I had was to put the *SAVSYS in one control group
(restricted state), everything else in another control group (not
restricted), and run them back to back. This might be trickier, though, as
the first control group has to finish before the next one starts. I don't
know if BRMS has that built in or not. Just thought of that idea while
writing. Also, since I want everything on a single tape, I need to make
sure the 2nd control group doesn't clear the tape.

Suggestions welcome.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page