|
Thanks Steve. I was attempting to backup up the whole system on a bimonthly basis. We don't do a lot of development on that machine, but this may increase in the future. What is there needs to be backed up in case of the usual disaster recovery situation. And I appreciate the reassurance...just very confused. Used to working on systems where I can get my hands on the details. Not much to work with here, or I just don't know enough to find it. -----Original Message----- From: Steve Richter [mailto:srichter@AutoCoder.com] Sent: Thursday, December 20, 2001 12:26 PM To: midrange-l@midrange.com Subject: Re: Probably very easy, Newbie question Dont dispair yet Newbie. Option 21 will save the user and system libraries. Do you need to do that, or just the user libraries ? If just the user libraries, you just need to make sure no user jobs are running when you do the backup. - get everyone to signoff. - end all batch jobs ( or wait for them to end ) - from the command line, run the cmd: SAVLIB LIB(*ALLUSR) DEV(TAP01) SEQNBR(1) ENDOPT(*UNLOAD) CLEAR(*ALL) If some objects were in use and could not be saved, you will get completion messages telling you so. Hope this helps, Steve Richter ----- Original Message ----- From: "Jill Grine" <JillG@gtsoftware.com> To: <midrange-l@midrange.com> Sent: Thursday, December 20, 2001 12:05 PM Subject: RE: Probably very easy, Newbie question > I really hate to say this, but I really meant it when I said that the only > keyboard in the vicinity of the AS400 is attached to a PC, then goes to the > 400. Maybe something strange about the way it was set up. > > Well, it looks then like I can't use this option to back up the system. > Guess I'll have to look for something else. (Sigh.) Thanks all. You'd > think backups should be relatively straightforward. Thanks, Murphy. > > -----Original Message----- > From: alan shore [mailto:SHOREA@dime.com] > Sent: Thursday, December 20, 2001 11:53 AM > To: midrange-l@midrange.com > Subject: RE: Probably very easy, Newbie question > > > On the command line type > WRKACTJOB > and press Enter. > This will display the Work with Active jobs screen. > There are numerous columns. > Under the column > Subsystem/Job > you should see the following > QBATCH - for jobs run in batch > QCMN - communications subsystem > QCTL - the control subsystem. This is where you should see your User Profile > (in this case QSECOFR) under the User column > QINTER - the Interactive subsystem. If you see your profile (in this case > QSECOFR) under the User column after this subsystem - you are NOT at the > console. Therefore option 21 - Full system save - should NOT work. You need > to sign on at the console, usually near where the AS/400. > > >>> Jill Grine <JillG@gtsoftware.com> 12/20/01 11:36AM >>> > Thanks for the response, Richard. Uh oh...What is "qinter"? I don't find > that in the index, and I'm hoping it's a typo. Also, we don't have anything > set up as a "console". We are accessing it via Client Access from another > PC. I am doing this from the QSECOFR id, which is supposed to have all the > access necessary based on the Backup and Recovery manual. > > Ahhh the learning curve. > > -----Original Message----- > From: Richard Reeve [mailto:richreeve@yahoo.com] > Sent: Thursday, December 20, 2001 11:23 AM > To: midrange-l@midrange.com > Subject: RE: Probably very easy, Newbie question > > > -- > [ Picked text/plain from multipart/alternative ] > > Two things come to mind; > 1. The system needs to be in a restricted state i.e. qinter should be > ended, thereby making it necessary to perform this function from the > console. > 2. The authority level of the person that is perfoming this may be > incorrect. It has been a while for me, but at a minimum I believe that you > will need *savsys specified on the special authority field for the user that > is perfoming this task. You may also need *allobj authority but I can't > swear to that one. > > > > > > > --------------------------------- > Do You Yahoo!? > Check out Yahoo! Shopping and Yahoo! Auctionsfor all of your holiday gifts! > _______________________________________________ > 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. > _______________________________________________ > 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.