Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!uwm.edu!bionet!agate!ucbvax!cim-vax.honeywell.com!derstad
From: derstad@cim-vax.honeywell.com ("DAVE ERSTAD")
Newsgroups: comp.sys.apollo
Subject: DPAT problem
Message-ID: <9010161441.AA07687@umix.cc.umich.edu>
Date: 16 Oct 90 15:40:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20


We've found a strange happening with DPAT (Apollo's process monitoring
utility).  The following sequence of events occurs on a Series 400.

We are monitoring a fairly CPU intensive program using DPAT.  All is 
well.  An unrelated CPU intensive program starts up.  All is still
well (the various programs time-slice).  A second unrelated
CPU intensive program starts up.  Now, the monitored program
blocks somehow and gets no further CPU time.

I've replicated this using "while ((1)) do enddo" statements for the
unrelated CPU intensive programs.  I have not yet tried to make it 
happen while monitoring programs other than the original application,
so I don't know how unique a problem this is.

Can anyone offer a rational explanation?

Dave Ersatd
DERSTAD@cim-vax.honeywell.com
Honeywell SSEC