The issues on Macros in Schedules is one which lots of us would like to see,
and also one which must drive developers loony - who has the Macro code you
want to run?  It sure would be nice, though, if when I established a
schedule, the Macro could be downloaded to the host and stored there - it
would have implied overhead (how to update, what if someone else wants to
change it. etc.), but there are so many things that people would like to do
in sequence, such as expire the inventory, then backup the DB.  My personal
favorite is a set of "Update Node" commands we run to avoid password
expiration on servers such as Novell that don't support Passwordaccess
Generate.  I would love to get out of maintaining about 40 odd separate admin
schedules.....

Thanks...

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Admin schedules - What commands?
Author:  INTERNET.OWNERAD at SNADGATE
Date:    2/23/98 10:58 AM


 The only restricted commands are MACRO and Query ACTLOG. The reason for
these 2:
1) MACRO--  Macros are valid only from administrative clients. Scheduling of
   admin commands is contained solely within the server and the server
   has no knowledge of macros.
2) Since all output from scheduled admin commands is forced to the actlog
   then scheduling a Query ACTLOG would force the resulitng output right
   back to the actlog thereby doubling the size of the actlog.

Tom Brooks
ADSM Development