Re: Remote outq vs. *DEVD

I suspect very little. If each is using host print transform they both need to do that work and the rest is communications.

First thing I would take a look at is the size of the memory pool used for spooling/printing. Bring up WRKSYSSTS and use F21 to set to 2 or 3(Intermediate or Advanced). Use F10 to reset statistics then have someone crank up a print job that is tagged as 'slow'. Using F5 (Not F10) refresh the screen and watch the Fault columns for the *SPOOL pool. I have seen those numbers go to 4 digits then I see the spool pool is at a measly 4 or 8M....... and that's the problem. If that's the case the pool needs to hold a bit more memory when it's not being used so that when work comes along it has space to work.

To fix it use WRKSHRPOOL and adjust the 'Minimum Size %' column for the *SPOOL pool. (You'll need to press F11 to see it) The default is 1 meaning it can shrink to 1% of the total memory on the system. For a 4G machine that's 40M but if you have a 1G machine it's only 10 which isn't likely enough. Available memory is displayed at the top of that page. Using that, figure out the percentage needed to set the 'floor' at about 32M to start. Then test again to see if performance improves. If not perhaps 48M is a good next step.

Of course if the machine is pounding along at 100% CPU this might not help as much so standard warning about YMMV!

I have seen this small change turn 2 minutes into 10 seconds for a print job, hopefully it helps you as much!

- Larry "DrFranken" Bolhuis

On 12/27/2011 10:28 AM, jmmckee flinthills.com wrote:

Is there any performance difference between using remote outq and a
*DEVD for printing? There are complaints where I work of output
taking "too long" to be produced from the i. Another system that
sends postscript data seems to print faster. Printers are Lexmark
Optra.

Thanks

John McKee