ADSM-L

Re: AW: [ADSM-L] Automating server scripts

2006-02-14 09:06:12
Subject: Re: AW: [ADSM-L] Automating server scripts
From: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 14 Feb 2006 09:05:42 -0500
Hello all,

I set up a script to run every hour. with the following commands in the
script. When I run the script I receive a invalid parameter error for
the wait parameter.


/* This script queries the backuppool stgpool then stops migration on the 
backuppool stgpool*/
run test_query_script wait=yes
run stop_disk_mig_script wait=yes
run test_query_script

The wait parameter is invalid can this be used in this sequence?


Thanks for any help!


ANR2020E RUN: Invalid parameter - WAIT.
ANR2020E RUN: Invalid parameter - WAIT.

Storage       Device        Estimated     Pct     Pct   High   Low   Next
Pool Name     Class Name     Capacity    Util    Migr    Mig   Mig   Storage
                                                         Pct   Pct   Pool
-----------   ----------   ----------   -----   -----   ----   ---   -----------
ARCHIVEPOOL   DISK               63 G     0.0     0.0     90    70   H3592POOL
BACKUPPOOL    DISK            1,014 G    67.6    67.6     70    40   H3592POOL
H3592POOL     3592CLASS     266,231 G    25.8    31.4     90    70
MIGPOOL       DISK               84 G    12.8    12.8     75    50   H3592POOL
R3592POOL     3592RCLASS    270,464 G    25.4

ANR1462I RUN: Command script TEST_QUERY_SCRIPT completed successfully.
ANR1462I RUN: Command script GLOBAL_SCRIPT completed successfully.
PAC Brion Arnaud wrote:

> Timothy,
>
> You should build an admin schedule, which initiates something like "run 
> Global_script", and then in this "global_script", have all of your commands, 
> like:
>
> run test_query_script wait=yes
> run stop_disk_migration wait=yes
> run test_query_script
>
> Hope this helped !
> Cheers.
>
> Arnaud
>
> ******************************************************************************
> Panalpina Management Ltd., Basle, Switzerland,
> CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
> Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
> Direct: +41 (61) 226 19 78
> e-mail: arnaud.brion AT panalpina DOT com
> ******************************************************************************
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Timothy Hughes
> Sent: Thursday, 09 February, 2006 16:34
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: AW: [ADSM-L] Automating server scripts
>
> Hello all,
>
> I ran this via the admin schedule but it just seem to execute the first part 
> of the script (run test_query_script)?
> do I need a second admin schedule to kick off the next script and so on? If 
> so how would the serial part of the command be incorporated into to that? I 
> tried wait=yes and the server log showed Invalid parameter - WAIT
>
> thanks
>
> CHECK_STGPOOL
> Description TEST SCRIPT COMMAND
> Command  run test_query_script serial run stop_disk_migration serial run 
> test_query_script Priority 5 Start date 2006-02-08 Start time 08:13:00 
> Duration 15 Duration units MINUTES Period 1 Period units HOURS Day of Week 
> ANY Expiration - Active? YES Last Update Date/Time 2006-02-09 08:11:40.000000 
> Last Update by (administrator) Managing profile - Schedule Style CLASSIC 
> Month - Day of Month - Week of Month -
>
> 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
> >
> > >>> Ramakrishna_Choudarapu AT ML DOT COM 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:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> > Of Timothy Hughes
> > Sent: Wednesday, February 08, 2006 9:55 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > 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
> > >
> > > >>> Joachim.Schaub AT ABRAXAS DOT CH 02/08/06 7:49 AM >>>
> > > Simple:Build an admin scheduler with command run script ;-)
> > >
> > >
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im
> > > Auftrag von Timothy Hughes
> > > Gesendet: Mittwoch, 8. Februar 2006 14:48
> > > An: ADSM-L AT VM.MARIST DOT EDU
> > > 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/
> > --------------------------------------------------------