ADSMer's

Here was the answer to the problem I was having with my scheduler...

Thanks,

Rick Smith
------ Forwarded by Richard Smith on 03/29/99 03:11 PM ------
 (Embedded      (Embedded image moved to file:
 (Embedded      (Embedded image moved to file:
 image moved to PIC27490.PCX)
 file:          From: Daniel Thompson
 PIC22900.PCX)  (Embedded image moved to file:
                PIC13955.PCX)
                03/29/99 01:52:00 PM
                (Embedded image moved to file:
                PIC14609.PCX)



To:   John Shaw, Richard Smith, Alex Sapronov, Alexei Kojenov, Yu Chen, Tim
      Williams, Steve Robinson
cc:
Subject:  I: Mystery of 30 second looping

Gents,

     As you may or may not know, there was a problem we were experiencing
with ADSM00s9 with a session being established between it and SM40M002.
The symptoms were:

   ADSM00s9 was getting a session with SM40m002 every 30 seconds and it
   appeared as if sm40m002 was initiating the session.  The schedmode on
   this client was prompted and there was no pending schedule on sm40m002.
   SM40M002 was getting a session with ADSM00S9 every 30 seconds and it
   appeared as if ADSM00S9 was initiating the session. Once again, there
   was no pending schedule for this client.
   There was no apparent symptoms, other than the above that was causing
   the problems.  There were times starting Friday that this session would
   not be established.  We assumed that this was due to the work going on
   in the site lab, but during the time the sessions would not establish,
   there was connectivity between ADSM00s9 and SM40m002, so this did not
   make any sense.

By pure accident, we have found the problem.  After the maintenance done
this weekend, I checked on Snoopy per SOP.  I checked the activity log, for
no particular reason, and found that this ADSM server was contacting
ADSM00S9 every 30 seconds.  Some of the demonstration schedules we had set
up for the client config. facility were still in place.  So here was what
was happening:
   Snoopy was trying to prompt ADSM00s9 for a schedule, as was directed by
   the schedule.
   ADSM00S9 accepted the session and then connected back to its server
   (SM40M002) for the information on the schedule.
   SM40M002 would respond that ADSM00S9 has no schedule and the session
   would be closed.
   This would recur every 30 seconds.

This resolves this problem, but those of use who set up demonstration
schedules on Snoopy, or even live schedules need to be careful to stop the
schedules once the machines have been redirected to the new machines.

Dan T.