From: Peter Thomas on 06/16/97 11:37 AM
Something I've "toyed" with doing but haven't actually tried yet would be
do have a task that monitors the ADSM console and takes actions such as
you've mentioned based on messages for task completion..

The console is accessible by running "dsmadmc" with the command line option
"-console". Right now, I am monitoring the console for things like critical
ADSM error messages and eMailing my Notes account with any that do occur.

Peter Thomas
Manulife Financial
Phone: (416)963-7371
Fax: (416)926-5454




From: lipp @ STORSOL.COM on 16/06/97 08:49 AM CST

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L @ VM.MARIST.EDU
cc:    (bcc: ADSM)
Subject:  Serialization of Server commands,




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