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: [email protected] [mailto:[email protected]] 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 [email protected] To unsubscribe, send email to [email protected] 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 [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
