|
I would caution that Al's statement could be understating the facts for the less than savvy systems person... Al, don't you cover these steps/cmds in your Common presentation? On Sat, 8 Sep 2001 barsa@barsaconsulting.com wrote: > > I would caution that the code to determine that you are truly in a > restricted state is tricky. > > Al > > Al Barsa, Jr. > Barsa Consulting Group, LLC > > 400>390 > > 914-251-1234 > 914-251-9406 fax > > http://www.barsaconsulting.com > http://www.taatool.com > > > > > > > Chuck Morehead > <cbmorehead@nokuse. To: midrange-l@midrange.com > com> cc: > Sent by: Subject: Re: Save System >question > midrange-l-admin@mi > drange.com > > > 09/08/01 11:15 AM > Please respond to > midrange-l > > > > > > > You could write a CL program to do this. Here's a basic outline: > > DLYJOB until you want it to start. > ENDSBS *ALL *IMMED to go to restricted state. > SAVSYS to save the system. > SAVLIB *NONSYS to save all non-system libs. > SAVDLO to save the QDLS file system. > SAV to save any other file systems you may have in the IFS. > SIGNOFF > > > ----- Original Message ----- > From: <gcrane@johansonmfg.com> > To: <midrange-l@midrange.com> > Sent: Saturday, September 08, 2001 7:47 AM > Subject: Save System question > > > > > > > > Is there a way to have the System Console signed off upon completion of > the Save > > System? The user is logged on to the system console Save Menu and using > option > > 21 save entire system and scheduled for a later time in the middle of the > night. > > Just do not want the terminal signed on when the save finishes. > > > > Also, what authority rights does the operator really need to do a > complete > > System Save - must be able to back up all files/libraries and the IFS > > directories that are secured. > > > > > > > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.