Hmmm !! ' DevType :UNNASSIGNED' (sic)
So there is no device for the 'jspprint' ( despooling process ) to 'attach' to so I would expect this 'Status' to be 'KILLED - Despool detected killed in unknown manner' Similarly for the 'Default' 'Device Type' ( NT ) on Windows / ( LPTR ) on Unix : FormQueue :STANDARD (DEVCONFIG*0) Status :KILLED (8) DevType :NT (5) DevName : LockPid :*** ??? *** Created :Administrator 1 09 NOV 2010 00:57:13 Stop Reason :Despool detected killed in unknown manner A 'Device Type' of 'NT' / 'LPTR' goes directly to the 'Default Windows / Unix spooler/printer', bypassing the jBASE Spooler, so again there is 'no device' ( or requirement ) for the 'jspprint' process to 'attach' to this device cf a 'Device Type' of 'PROG' where the 'jspprint' process 'despools' ( pipes the Print output ) to the 'executable' specified to the 'PROG' setting On Jul 20, 8:00 am, VK <kzm...@yahoo.com> wrote: > Hi > > Strange, under win32 model bank I always have it "KILLED" though I can > print to Windows default printer (physical one is OK, though CutePDF > being set as a default always results in an empty pdf file). > > in my case the output is: > > jsh t24 ~ -->jsp_scan -v > jsp_scan - Version $Revision: 3.1 $ > SpoolerDir=C:\kzm\ModelBank\Temenos\bnk\bnk.run\jspooler > 883 Items read; 0 Locked; 0 Read errors > > FormQueue :STANDARD (DEVCONFIG*0) > Status :KILLED (8) > DevType :UNNASSIGNED (99) > DevName :0 > LockPid :*** ??? *** > Created :modelsg 22 23 AUG 2007 15:24:37 > Stop Reason :Despool detected killed in unknown manner > > NextJobNumber - 15780894 > > OwnerGroupSpooler - 11 > > What you think Pat? > > VK > > On Jul 19, 12:27 pm, pat <pat...@gmail.com> wrote: > > > The 'error code', for the 'KILLED' Form Queues, shown by : > > > jsp_scan -v > > > may assist in determining the reason for the Form Queue showing a > > status of 'KILLED' > > > On Jul 19, 7:11 am, Wilson Chikatala <wchikat...@gmail.com> wrote: > > > > Sorry for not being clear. > > > > I regularly check the status of print devices in the spooler due to > > > printing > > > problems faced by users. Usually the status of the queues in the spooler > > > is > > > "KILLED" instead of "ASSIGNED". For this reason, I have to restart the > > > spooler. > > > > On Mon, Jul 18, 2011 at 8:37 PM, Jim Idle <j...@temporal-wave.com> wrote: > > > > You are asking the wrong question – start with why you are restarting > > > > the > > > > spooler all the time, how you are restarting the spooler and most of > > > > all why > > > > you *think* you need to restart the spooler all the time. Also, please > > > > read the posting guidelines and provide all the information about your > > > > system. > > > > > Jim > > > > > *From:* jbase@googlegroups.com [mailto:jbase@googlegroups.com] *On > > > > Behalf > > > > Of *Wilson Chikatala > > > > *Sent:* Monday, July 18, 2011 6:55 AM > > > > *To:* jBASE@googlegroups.com > > > > *Subject:* T24 - Spooler > > > > > Dear All, > > > > > I have to restart the spooler all the time and as a result users are not > > > > able to print all the time in eMerge. This problem became common after > > > > migrating from Windows to Linux server. > > > > > Does anyone have a permanent solution to this problem? > -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to jBASE@googlegroups.com To unsubscribe, send email to jbase-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
