rod@CHEETA.ISI.EDU.UUCP (03/04/87)
In my earlier note I said that our printer symbiont was dying
with something about privileged images not installed. I'm embarassed;
it wasn't the symbiont that died that way, it was ANALIMDMP's attempt
to put me in the debugger! I was flying without documentation and didn't
realize it was trying to put me in the debugger.
It seems ANALIMDMP wants Sys$Library:UISSHR to be installed.
Why did it come installed on my microvax, but not on our cluster?
Well, now it's time to try and figure out why things die. If
the image associated with a queue bombs, should that corrupt the
queue structure? Our biggest problems have been with our printer
symbiont, but the queue manager dies at the same time. Sometimes
simply restarting the queue manager and all the queues clears things
up, sometimes job control gets out of whack, too, with errors
reading job control mailbox.
I didn't write our symbiont; someone who is no longer here did.
I've got a feeling it's sending something bogus to job control and
really screwing things up; how vulnerable is job control to others'
stupidity?
--Rod
rod@ISI.EduRAY@CRVAX.SRI.COM.UUCP (03/04/87)
When using symbionts the JobController wants to talk to your process using the SMB$Send_To_Jobctl library call. What often happens is that the process will run into an Exception that isn't handled this causes your symbiont to have the output of the Exception to goto the Jobctl which doesn't like it at all and frequently dies. It is also possible that the symbiont does something like $Exit_S R0 - this has the smae result if R0 is not odd...In general you have to be very careful that you don't output inadvertanly or otherwise to Sys$Output... Ray