My work around deals with that issue.  It uses touch files to signal the 
other streams that they can begin, including telling them that they 
"master" script failed.  If the master script fails, then all associated 
streams exit with a 73.

At 10:44 PM 6/20/2001 -0500, scott.kendall AT abbott DOT com wrote:
>One issue with this is that all the streams will be queued together.  If more
>than one stream starts running at roughly the same time (which is going to
>happen if you're using mux'ing or more than one tape drive is available), you
>have the 1st stream getting the database ready for the backup.  What about the
>other streams?  If you have the script immediately exit for these they will
>start their backups.  If the bpstart from the first stream is still running
>trying to get the database ready and the other streams start to backup files,
>the backups will not be good.  All subsequent streams must wait for the first
>stream to finish before they proceed or the database will not be ready.
>
>Also, if a stream runs and then finishes all while other streams for the same
>backup are still queued.  There won't be any stream*.active files that exist
>and the database will be brought up before the queued streams even start.

---
W. Curtis Preston
Principal Consultant for Storage Designs, your storage experts
Webmaster: http://www.backupcentral.com Phone: 760 653 1007