When I upgraded to version 3, I rewrote my script to use wait=yes for all
the commands (backup stg, backup db, etc.).   I never noticed that my
maxprocess=2 parameter was being ignored now until I looked after reading
your email, Roger.

There's nothing that I could find in the manual that says the maxpr=nn
parameter is only for background processes, not foreground ones with the
wait=yes parameter.  Has anyone else found documentation that says IBM
intended this to be true?

Tina

> -----Original Message-----
> From: Roger Hohmann [SMTP:Roger_Hohmann AT WESTLB DOT DE]
> Sent: Monday, December 28, 1998 2:55 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: ADSM Scripts
>
> I use it with wait=yes, but it seems to be limited to one (1) session
> (one process at a time). So I am copying my smaller pools first and my
> big one last with wait=n and maxsess=3.
>
>
> -----Original Message-----
> From:   Hilton Tina [SMTP:HiltonT AT TCE DOT COM]
> Sent:   Wednesday, December 23, 1998 7:23 PM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        Re: ADSM Scripts
>
> I do it inside a script, but with version 3 of the server use the
> wait=yes
> option.  You won't get control back until the backup has finished.  I
> assume
> it works the same way in a macro, but haven't tested it.
>
> > -----Original Message-----
> > From: Remeta, Mark [SMTP:MRemeta AT SELIGMANDATA DOT COM]
> > Sent: Wednesday, December 23, 1998 1:00 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      ADSM Scripts
> >
> > Hello all!
> >
> > I want to write a ADSM macro/script that will do several storage pool
> > backups but I don't want to start the second one until the first one
> > completes. How can I determine, in a macro, that the first backup
> > command completed before I issue the second?
> >
> > Thanks in advance,
> >
> > Mark Remeta
> > Seligman Data Corp.
> > 100 Park Avenue
> > New York, NY 10017
> > (212)716-2810