No need to restart SFS. One should learn about the .CMS SFS operator command. The "problem" is that one first neads to zap a bit in the SFS server's storage before .CMS is accepted. Look for and SFSDOT file on one of MAINT's minidisks.
My SCIF package includes a SFSCMS EXEC that includes (and issues) the needed commands. Example: SCIFSFS VMSERVS .CMS ACC 192 D Thanks to the .CMS command one can dynamically increase its backup minidisk. That is what we did: - prepare a new mindisk - verify that the log isn't near full - SCIFSFS VMSERVS CP DET 192 CP LINK * 192 192 M .CMS ACCESS 192 D 2008/7/22 Rob van der Heij <[EMAIL PROTECTED]>: > On Mon, Jul 21, 2008 at 10:16 PM, Schuh, Richard <[EMAIL PROTECTED]> wrote: > >> affects ever user that is actively using SFS. The documentation also >> says that backing up to a different filepool instead of to dasd or tape >> will cause less interference with the users. It will take longer, but >> the users will not be affected as much. > > The problem with that is if you have to recycle that filepool with the > control backups, the access will be gone and the control backup fails. > And I believe that unless you poke in the SFS server, you can't > re-access that other than STOP NOBACKUP and restart? > -Rob > -- Kris Buelens, IBM Belgium, VM customer support
