Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uxe.cso.uiuc.edu!sandrock From: sandrock@uxe.cso.uiuc.edu Newsgroups: comp.os.vms Subject: HELP: symbiont dies under 4.7 Message-ID: <62500009@uxe.cso.uiuc.edu> Date: 17 May 88 15:54:00 GMT Lines: 38 Nf-ID: #N:uxe.cso.uiuc.edu:62500009:000:1644 Nf-From: uxe.cso.uiuc.edu!sandrock May 17 10:54:00 1988 Since we recently upgraded our VAX/780 from VMS 4.4 to 4.7, a rather annoying problem is cropping up with TeX/LaTeX files spooled to our Xerox 2700 laser printer. The problem is that certain TeX/LaTeX files will print to a certain point in the file, and then cause the symbiont process to terminate! The result is that all three printer queues (all terminal queues) are stopped until someone with the right privs executes a START/QUEUE for each of the three printer queues. The following messages appear on the operator's console each time: %%%%%%%%%%% OPCOM 16-MAY-1988 15:35:05.74 %%%%%%%%%%% Message from user JOB_CONTROL %JBC-E-SYMDEL, unexpected symbiont process termination %%%%%%%%%%% OPCOM 16-MAY-1988 15:35:05.77 %%%%%%%%%%% Message from user JOB_CONTROL -PSM-F-BADLOGIC, internal logic error detected at PC 0000CCD1 One idea was to go back to the 4.4 PRTSMB.EXE, until we discovered that not only was PRTSMB.EXE unchanged by the upgrade(s), but in fact, our PRTSMB.EXE is *identical* (using DIFF) to a known good PRTSMB.EXE on another VMS node across campus. If any VMS expert could shed some light on what the hay is going on here, we would be very grateful. I am to the point of trying to get hex dumps of everything going to the printer, but am hoping someone else may already know about the solution to this problem. Regards, Mark Sandrock University of Illinois at Urbana-Champaign School of Chemical Sciences Computing Services 505 S. Mathews Ave., Urbana, IL 61801 BITNET: sandrock@uiucscs Internet: sandrock@b.scs.uiuc.edu Phone: 217-244-0560