|
Jorge You are right, a savsys should always be performed from the console, even other device coupled to the controlling subsystem is not enough. There are several options for you here. 1e. The product BRMS has a trick for this, most other backuppackages (Robot Save, Help system AOS tapemanager) use the same trick. They start a monitor program on the console and than they start a job from somewhere, scheduler, batch with a wait. this job trickers the monitor to start the full backup options. 2e. Create a CL program you start on the console with a userprofile that can only start this (initial program) no attn-key allows and *SIGNOFF in the profile. Make some test if you are on the console. Test the tapedrive if a tape is there. Wait till you want the backup to start and then endsbs *all backup all you want start QCTL or IPL If needed I can find a example CL Groetjes (Greetings) =========================================================== Name: Eduard van den Braken E-mail: e.vd.braken@hccnet.nl Town: Leusden -- the Netherlands Homepage: http://home.hccnet.nl/e.vd.braken/ =========================================================== -----Oorspronkelijk bericht----- Van: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]Namens jmoreno@militarycars.com Verzonden: vrijdag 2 augustus 2002 15:32 Aan: Midrange-L@midrange.com Onderwerp: Full System Backup in BATCH mode ? Hello Midrange Users, I am sure this question has been asked before But what about at V5R1 or V5R2 ? Has anyone been able to figure out if a full System Backup can be run in BATCH mode ? By Full System Backup I mean: Operating System, QSYS, IBM Libraries, Licensed Programs *ALLUSR libraries *ALL Folders and *ALL User Directories However to my knowledge The SAVSYS requires the system to be in a restricted state. Does it mean that only a device attached to the Controlling Subsystem can perform this function ? Just want to know your opinions Thanks in advance Jorge Moreno Systems Analyst Overseas Military Car Sales Woodbury, New York _______________________________________________ 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-2025 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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.