When you run a "endsbs *all", the only thing running is the console. I think you can run the console as a PC using the software VNC (allow you to run the console from a remote location via TCP/IP). If you want to run the back up as a batch job in QCTL, you will have to stop all the subsystem singlely but not QCTL. This will leave QCTL being able to run multiple jobs in QCTL. ================================================================ The SAVSYS command cannot be run except as an interactive command. This is because the system cannot be active when the operating system is saved. And that means the system must be in restricted state so that no subsystems are active (including the controlling subsystem, QCTL or QBASE). But that's usually not a problem since there's no reason to run SAVSYS more than maybe once or possibly twice a year. You take the system to restricted state, run SAVSYS, and start the controlling subsystem. Done for the year. Everything else can be done without restricted state. That includes the two components of SAVSYS that should be done on a regular basis -- SAVSECDTA and SAVCFG. Since those don't require a SAVSYS, why run the command on a regular basis anyway? Note that BRMS does provide a method of initiating a SAVSYS from batch. Also note that at V5R3 a SAVSYS can be scheduled to run at the console interactively for those who don't have BRMS. Tom

When you run a "endsbs *all", the only thing running is the console. I think you can run the console as a PC using the software VNC (allow you to run the console from a remote location via TCP/IP). If you want to run the back up as a batch job in QCTL, you will have to stop all the subsystem singlely but not QCTL. This will leave QCTL being able to run multiple jobs in QCTL. ================================================================ The SAVSYS command cannot be run except as an interactive command. This is because the system cannot be active when the operating system is saved. And that means the system must be in restricted state so that no subsystems are active (including the controlling subsystem, QCTL or QBASE). But that's usually not a problem since there's no reason to run SAVSYS more than maybe once or possibly twice a year. You take the system to restricted state, run SAVSYS, and start the controlling subsystem. Done for the year. Everything else can be done without restricted state. That includes the two components of SAVSYS that should be done on a regular basis -- SAVSECDTA and SAVCFG. Since those don't require a SAVSYS, why run the command on a regular basis anyway? Note that BRMS does provide a method of initiating a SAVSYS from batch. Also note that at V5R3 a SAVSYS can be scheduled to run at the console interactively for those who don't have BRMS. Tom