Yes, there is a wait=yes for most commands.  What I am trying do is to use 1
script to reduce the ho/lo migration values to zero for several storage
pools, wait for the migration to start, and then return the hi/lo values to
there normal values. I am assuming that if I reduce them and immediately
increase them, the migration processes may not get started. However, I have
NOT checked this.

On Wed, 10 Feb 1999, Lynch, Rich wrote:

> I think there is a wait=yes option on most commands, is there not? Im going
> to try this on some of my backup copy pool commands as Im running into some
> timing issues, etc... Has anyone done this?
>
> -----Original Message-----
> From: Joel Fuhrman [mailto:joelf AT CAC.WASHINGTON DOT EDU]
> Sent: Wednesday, February 10, 1999 4:47 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: WAITING FOR PROCESSES IN ADSM SCRIPTS
>
>
> One suggestion supplied to me is to create an administrative schedule that
> is not active and is set to run once.  To do something relative to now, you
> update the schedule to make it active and change the starttime=now+dd:dd
>
> I hope that scripting will continue to be enhanced.  I would like a wait
> command and it would be nice to be able to call a perl or shell script
> within the adsm script.
>
>
> On Wed, 10 Feb 1999, Michael L. Gimm wrote:
>
> > Hi all
> >
> > Just spent a couple of hours yesterday looking at ADSM scripts - nice idea
> > - but I can't use
> > it for much if I can't wait for processes. I tried the following:
> >
> >
> > ..but aperently you cannot use GOTO for looping. Has anyone found a
> > solution?
> > Anything would be helpfull.
> >
> > Please use my direct mail as well as the list: mlg AT fourleaf DOT dk
> >
> > Best regards,
> > Michael L. Gimm
> >
>