Yes. Do a "help define schedule" and look at the "period" and "perunits" section. Tune your duration from the script and your "every two hours", otherwise your next backup stg will fail with a "already in prog" error.
But, why? Why do you want every 2 ours a backup stg proces? Regards, Karel -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Hughes Sent: woensdag 8 februari 2006 17:16 To: [email protected] Subject: Re: AW: [ADSM-L] Automating server scripts Karel thanks! But can this be schedule to run "every two hours" using Just one Admin schedule? "Bos, Karel" wrote: > Hi, > > Change script to: > > query stgpool > Migrate stg backuppool lo=30 dur=XX wait=yes query stgpool > > And try again. > > Regards, > Karel > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Timothy Hughes > Sent: woensdag 8 februari 2006 16:42 > To: [email protected] > Subject: Re: AW: [ADSM-L] Automating server scripts > > ok thanks again Rama and Bill, > > Here's and example! Of a script that I would run every 2 hours. > > run query stgpool > then "run update stgpool backuppool highmig=60 lowmig=30" > when complete "run query stgpool command" > > Thanks > > Bill Kelly wrote: > > > I think that's correct; if you want the scripts to run in parallel, you'll > > need multiple admin schedules. If you want the scripts to run serially, > > you could kick off the first script via an admin schedule, then have that > > script run the second script, and so on... > > > > -Bill > > > > Bill Kelly > > Auburn University OIT > > 334-844-9917 > > > > >>> [EMAIL PROTECTED] 02/08/06 9:04 AM >>> > > Multiple scripts inside an admin schedule? > > I believe each schedule can contain one cmd/script... > > You may have to create multiple schedules, one for each server script. > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > > Behalf Of Timothy Hughes > > Sent: Wednesday, February 08, 2006 9:55 AM > > To: [email protected] > > Subject: Re: [ADSM-L] AW: [ADSM-L] Automating server scripts > > > > Thanks to all! > > > > I know about the admin scheduler already, I just wasn't sure if I > > could put multiple scripts inside a admin schedule and run them > > simultaneously say every 3 hours. I guess I would use multiple run > > commands? > > > > Thanks again! > > > > Bill Kelly wrote: > > > > > Sorry...obviously, one should substitute > > > > > > cmd="run script-name" > > > > > > for > > > > > > cmd="q proc" > > > > > > but you all knew what I meant. :-) > > > > > > > To be more specific, set up the schedule with something a>long the > > > > lines of this: > > > > def sched queryproc t=a desc="query processes" cmd="q proc" > > > > startt=13:59:00 dur=15 duru=m day=any per=1 peru=hours > > > > active=yes Which will run the script every hour at (roughly) > > > > xx:59:00 > > > > > > -Bill > > > > > > >>> [EMAIL PROTECTED] 02/08/06 7:49 AM >>> > > > Simple:Build an admin scheduler with command run script ;-) > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im > > > Auftrag von Timothy Hughes > > > Gesendet: Mittwoch, 8. Februar 2006 14:48 > > > An: [email protected] > > > Betreff: [ADSM-L] Automating server scripts > > > > > > Hello, > > > > > > Does anyone know of a way to Automate sever scripts to run on there own?? > > > I have scripts set up that I would like to run say every two hours. I > > > know to run a script you would use the run command but can that be > > > automated? > > > > > > TSM 5.3.2.1 > > > AIX 5.3 > > > > > > Thanks for any help or suggestions > > > > > > Regards > > -------------------------------------------------------- > > > > If you are not an intended recipient of this e-mail, please notify the > > sender, delete it and do not read, act upon, print, disclose, copy, retain > > or redistribute it. Click here for important additional terms relating to > > this e-mail. http://www.ml.com/email_terms/ > > -------------------------------------------------------- > > ------------------------------------------------------------------------ > Name: Disclaimer.txt > Disclaimer.txt Type: Plain Text (text/plain) > Encoding: base64
Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien de integriteit van het bericht niet veilig gesteld is middels verzending via internet, kan Atos Origin niet aansprakelijk worden gehouden voor de inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten waaronder Atos Origin goederen en/of diensten levert zijn met uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos Origin van toepassing. Deze worden u op aanvraag direct kosteloos toegezonden. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Origin supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Origin exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
