We chose NOT to use an outside scheduler for ADSM functions, although
     we DO USE Autosys for a great many things.

     Our reasoning was that there is no internal command response to the
     status of the backups from ADSM, and we use Tivoli to issue an ADSM
     command "Q EV <domain> <schedule> ..." to alert us via pager's when
     errors occur.

     When using Autosys, this command has no meaning.

     It was ONE way to go out of many.  The real choice will be up to you
     once you have compiled a list of pro's and con's.

     Bil McKinley
     Merrill Lynch & Company
     212.647.2083
     BIL_MCKINLEY AT ML DOT COM


______________________________ Reply Separator _________________________________
Subject: ADSM & AutoSys / Maestro
Author:  "Keenan D. Stratton" <stratkee AT GTI DOT NET> at UNIXGTWY
Date:    5/23/97 10:28 AM


ADSM'ers,

In implementing an enterprise wide job management/job processing solution, does
it make sense to have a scheduling package kick off ADSM client services or use
the ADSM server/client to manage that piece of it?

We are evaluating the strengths and weaknesses of schedulers and trying to
determine if it makes sense.  Any experiences?


Keenan Stratton
ISI / Mars, Inc. Consultant
Keenan AT webname DOT com