This is the way most print spoolers operate. Print jobs should be listed in the spooler system so you can delete jobs entered in error or no longer needed.

Depending on the operating system you are using there may be issues restarting the dump after the printer comes back on line.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

Hi Ed.

Thanks for the reply, but, perhaps I should be more specific. Most likely, it will be a Windows 2003 server handling the print jobs.

Also, I am talking about keeping the jobs for 24 hours in the spooler before the printer becomes available.

It is something I have tried. I am trying to find a way so there is no user interaction, once the job has been sent, as soon as the printer becomes available, it will start printing.

Juan.

So far as remaining in the queue, there is no problem. It will remain there until removed or printed.

WS2003 isn't in my playpen so I don't know any details of restarting or lockouts.

Ed Fair
Give the wrong symptoms, get the wrong solutions.