Great follow-up. Thanks. Is it typical that jBASE sites have 300+ print queues? Is that something that the Temonos sites deal with? Most MultiValue installations that I am aware of have somewhere between 1 and 10 print queues. Excluding Temenos, what is the typical jBASE installation in terms of size?
Dick On Sun, Nov 6, 2011 at 5:58 AM, pat <pat...@gmail.com> wrote: > Why is it not immediate ? > [ Note : ***, below, is the 'fall back' mechanism for detecting > available Print Jobs. Details of the 'primary mechanism' are provided > further into this post ] > > *** In order for the 'jspprint' to 'know' that there are print jobs > waiting to be printed, 'jsprint' scans the print queue looking for new > Print jobs, on its associated Print Queue, that are 'Ready' to be > printed > > If the customer has 300 plus Print Queues, with 300 plus associated > 'jspprint' processes, then the system would be spending all of it's > time 'scanning the Form Queues' ( if 'jspprint' did NOT have a 'wait > period' ( of 30 seconds by default )) > > Hence the ( default ) period of a 30 second interval between each > 'scan' for each 'jspprint' process > > The 'Primary mechanism', to notify the 'jspprint' process(es) that > there is a new Print Job ready to be despooled ( Unix only ) > > When 'jlp' has finished creating a Print Job, the 'jlp' process sends > a ( Unix ) signal to the relevant 'jspprint' process, to 'wake' the > 'jspprint' process ( ie stop waiting for the full 30 seconds and scan > the Print Queue now ) > > However, if your 'jspprint' processes are started as 'root' user > ( say ), and the 'jlp' processes, started by the 'PRINT' statement in > the users Basic program, are running as a 'normal' user, then the > ( Unix ) signal will not be received by the 'jspprint' process started > by 'root'( and the 'jspprint' process will wait for the full 30 > seconds before svcanning the Print Queue for available Print jobs ) > > Solution, start the 'jspprint' process(es) as the 'normal' user rather > than 'root' > > Note : if the 'Print Queue Device' is 'LPTR' ( Unix ) / > 'NT' ( Windows ) ( ie NOT 'PROG' or some other device type ), the > 'print job' goes directly to the Unix / Windows printer, bypassing the > jBASE Form Queue ( and related 'jspprint' process ) on jBASE 4.1.6 and > above > > 'What is baffling is that jlp ...' > > Was 'jspprint' already running, for this Print Queue prior to issuing > the 'jlp' command ? > Or was 'jspprint' started, as the same 'user', by the 'jlp' command > ( in the event that 'jspprint' is not already running ) ? > What was the Device Type of the associated Form Queue used by the > particular 'jlp' command ? > > > 'after some time the spooler sleep slips back ...' > > Are the 'jspprint' processes being restarted, manually, 'after some > time' ? > Is the 'JBC_DESPOOLSLEEP' environment variable set for the user > 'restarting' the 'jspprint' process ? > ( remember the 'jspprint' process will be started ( automatically ) > when the 'jlp' process detects that 'jspprint' is not already running > for its associated Form Queue ) > > > On Nov 5, 10:45 am, Ken Brown <k...@bntnz.co.nz> wrote: > > I note that the knowledgebase states this is windows only. The problem > > exists on unix as well. Also be aware that after issuing the > > JBC_DESPOOLSLEEP command, that after some time the spooler sleep slips > > back to 20-30 seconds. We have now resorted to issuing this each end > > of day batch. > > > > Why is the default 30 seconds? Why is it not immediate? I cannot > > imagine any retail/wholesale business expecting customers to wait 30 > > seconds for an invoice. > > > > Ken Brown > > > > Bnt - NZ > > > > On Nov 5, 9:58 am, "Dan Ell" <d...@jbase.com> wrote: > > > > > > > > > > > > > > > > > Darrin > > > > > You would want to set JBC_DESPOOLSLEEP=5 where you set your environment > > > variables. > > > > > This will cause jBASE to check for despoiled jobs every 5 seconds. By > > > default it checks every 30. > > > > > > http://www.jbase.com/r5/knowledgebase/manuals/3.0/30manpages/man/env2_JB > > > C_DESPOOLSLEEP.htm > > > > > Dan > > > > > -----Original Message----- > > > From: jbase@googlegroups.com [mailto:jbase@googlegroups.com] On Behalf > > > > > Of Darrin > > > Sent: Friday, November 04, 2011 3:00 PM > > > To: jBASE > > > Subject: Slow to despool? (sometimes) > > > > > While standing up a new installation of jbase 3.4.10 on RHEL 5.2, > > > we've run into an interesting problem with slow printing. > > > > > Printing from the command line works great. lpr prints files > > > immediately. So does jlp. However printing with PRINTER ON / PRINTER > > > OFF / PRINTER CLOSE from a jbc program, results in jobs being "QUEUED" > > > in the jbase spooler. They hang for around 20 seconds and then print > > > as normal. > > > > > What is baffling is that jlp also sends jobs through the jbase spooler > > > but these print immediately as expected. > > > > > Cups receives the jobs and unloads them to the printer in less than a > > > second. It is just that they're hung up and visible in the SP-JOBS > > > screen. > > > > > Any ideas? > > > > > -- > > > 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 athttp:// > groups.google.com/group/jBASE?hl=en > > -- > 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 > -- 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
