Re: Remote system saves

[byting_time@xxxxxxx]

QCTL stays active until you do a PWRDWNSYS so you will be active even if QINTER 
is down

--
Furtner Consulting 
136 Crawford Dr 
Augusta, GA 
30907 
Home: 706-869-0205 
Cell: 706-627-6249 



-------------- Original message from "John Candidi" 
<jacandidi@xxxxxxxxxxxxxxxxxxxx>: -------------- 


> Doesn't the savsys end all subsystems and kill my path to the system? 
> ----- Original Message ----- 
> From: 
> To: "Midrange Systems Technical Discussion" 
> Sent: Thursday, November 11, 2004 10:50 AM 
> Subject: Re: Remote system saves 
> 
> 
> > Why don't you just run the command TFRJOB SBS(QCTL) and now you are the 
> system contorler. As long as your conection is enabled you have all 
> authority. I've done SAVSYS, RCLSTG, and Weekly backups. If you do 
> PWRDWNSYS you will loose your connection. 
> > 
> > -- 
> > Furtner Consulting 
> > 136 Crawford Dr 
> > Augusta, GA 
> > 30907 
> > Home: 706-869-0205 
> > Cell: 706-627-6249 
> > 
> > 
> > 
> > -------------- Original message from rob@xxxxxxxxx: -------------- 
> > 
> > 
> > > You can run this remotely under one of several situations: 
> > > 1) Use a twinax PC using an old emulation program, (not Client Access), 
> > > as your system console, with PC Anywhere loaded on it. 
> > > 2) Use Operations Console as your system console and access that with PC 
> > > Anywhere. How a client access like program like Operations Console can 
> > > operate on the iSeries when it's in restricted state baffles me - but it 
> > > does work just fine. Done it myself. 
> > > 3) Use an HMC to control your system and load the client on your PC to 
> > > access the HMC. Dying to try this one out. 
> > > 
> > > Rob Berendt 
> > > -- 
> > > Group Dekko Services, LLC 
> > > Dept 01.073 
> > > PO Box 2000 
> > > Dock 108 
> > > 6928N 400E 
> > > Kendallville, IN 46755 
> > > http://www.dekko.com 
> > > 
> > > -- 
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list 
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> > > To subscribe, unsubscribe, or change list options, 
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> > > 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@xxxxxxxxxxxx 
> > To subscribe, unsubscribe, or change list options, 
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> > 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@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>