You are lucky if it is only every 3 minutes with the message...
     The duration of the message is over the life of the schedule
     window/duration... so the one node must be in a schedule with a 5 hour
     duration.... and I really need to get around to seeing if I can alter
     the retry period for the schedule prompter... where you see the
     command retry period would be if something like a reclamation (tape)
     fails or a migrate diskpool to tapepool fails... then it will retry
     that often...
     My schedule prompter tries & fails every 6 seconds, some for 4,5 or 6
     hours.... god that is a lot of junk in the database.....
     later
          Dwight



______________________________ Reply Separator _________________________________
Subject:
Author:  ADSM-L at unix,mime/dd.RFC-822=ADSM-L\@VM\.MARIST\.EDU
Date:    7/11/96 11:54 AM


Date: Thu, 11 Jul 96 07:42:16 PDT
From: Dave Sanders <DSanders AT massmutual DOT com>
Subject: ADSM  Anr2716E messages
To: ADSM-L AT VM.MARIST DOT EDU
X-Mailer: Chameleon ENGP1, TCP/IP for Windows, NetManage Inc.
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII