I wrote a rexx script on our RS6000 to do this.  I wanted to make sure both
that the commands executed serially AND that they completed successfully,
and there's no way to know if a command fails because of a tape error or
similar problem without checking the activity log.  Looping on a q proc will
only tell you when the task is done, while looking through the activity log
for the message saying the task has completed successfully will let you know
that it worked.  How you do it depends upon how sure you want to be
everything was a success.

Tina Hilton
Thomson Consumer Electronics
 ----------
From: Kelly J. Lipp
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Serialization of Server commands,
Date: Monday, June 16, 1997 9:49AM


Folks,

Ideally, the following ADSM server actions would be processed serially:

backup stg
backup db
backup volhist
backup devconfig

(the last two in no particular order)

However, both backup stg and backup db start sub-processes and then
serialization is lost.  One could set the subprocess limit to one, but that
isn't necessarily good in a live environment.  I'm using ADSM for NT.
Anybody have any ideas how to serialize these steps?  Is there a scheduler
for NT that might help?  I'm not looking forward to writing the code to
issue the backup stg and looping on a query proc until finished, but if
that's it...

Thanks,

Kelly