Hi Preston,

I think you are assuming "Networker configuration changes" but maintenance 
operations may have to do with emergency work too. 

If I have a busy server and a big problem with devices (or any other that may 
need immediate attention) it would be nice to be able to put all or some jobs 
on hold by just raising a fence. Depending on the configured priority or 
priorities  of client , pool , group, etc,  that fence would prevent new jobs 
from starting if it is not a good time (as it always happens...).  

This feature would have been very useful in so many occasions. It was a key 
one for maintenace work when I worked with Tivoly Maestro (TWS) years ago.

I really wish Networker had something like that. But because it doesn't,  I 
have to nsradmin/disable all the jobs when required. It works, but  that is  a 
workaround and not a feature. 


jee







On Friday 20 Apr 2012 12:45:55 you wrote:
> IMHO, this is not a good architectural direction.
> 
> The enterprise solution I believe is:
> 
> - An overall software design that allows for in-flight configuration changes
> without any issues; - A technical implementation that allows for in-flight
> changes without interruption to backup/recovery processes.
> 
> Cheers,
> Preston.
> 
> On 20/04/2012, at 1:26 AM, Eddie Albert wrote:
> > My one item for the Networker v8.0, Wish List
> > 
> > Maintenance LOCKOUT" mode
> > 
> > Make it an active BUTTON and an event you can schedule.
> > 
> > Message to be displayed on all NMC if LOCKOUT is used or scheduled
> > 
> > "Maintenance LOCKOUT engaged - No new operations will start"
> > or
> > "Maintenance LOCKOUT engaged" - No new operations will start after 00:01
> > on 2012-04-19 until released"
> > 
> > Then if anyone logs into NMC or heaven forbid NSRADMIN it should display
> > at the top of the screen:
> > 
> > *** MAINTENANCE LOCKOUT ENGAGED ***
> > 
> > This would allow for truly scheduled maintenance, thoughts?
> > 
> > Semper fidelis et paratus, /ALE
> > 
> > To sign off this list, send email to listserv AT listserv.temple DOT edu and
> > type "signoff networker" in the body of the email. Please write to
> > networker-request AT listserv.temple DOT edu if you have any problems with
> > this list. You can access the archives at
> > http://listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER