Print Queues Delaying

[phydea...@my-deja.com]

We have been having problems with our print queues
for some time now. When I submit a job to the
output queue directed at a printer, either a dot
matrix Epson or an HP LaserJet, nothing will come
out. Sometimes it will print hours later, most of
the time not at all. When I work with active jobs
and page down to the print queues, the status line
says either TIMW or DLYW or SELW. Occasionally we
can get just one page to go through ok, but
multiple pages never go through. The printers
themselves are up on the network and can print
from the network, just not from the 400. WE have
V4R1.

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

[Matthew Chan]

what kind of connection and config u have? (says ip attached printer)
Did u check the activation timer in the device?

as i know for ipds device it's better to config a *psfcfg
which can control the release time for writer.

Also check the Class if it's remote spool.

regards
Matthew Chan
System Pro Solutions Ltd

[L. Ed. Nelson]

Do you know for a fact that these jobs are not just running slowly through
your batch job queues? Output queues are just not going to do this, unless
you have messages waiting on the writers. Submit one of these and then use
WRKJOBQ to see if it is just sitting out there waiting to run...If you can
confirm that the job actually ran (using WRKSBMJOB), then use option 8 to
examine the spoolfiles...If the spoolfile is there, then use WRKWTR to see
if messages have it hung up.

Ed

<phydea...@my-deja.com> wrote in message
news:7phvl0$jt5$1...@nnrp1.deja.com...

[Rodney Johnson]

This problem has all of the symptoms of a remote writer trying to communicate
with a printer with too small of a TCP/IP timeout. Remote writers must
transform the whole spooled file before sending it to the printer (has to do
with LPR/LPD protocol). Also, to ensure that the printer will accept the
data, the remote writer (actually LPR) opens a connection to the printer
BEFORE the long transformation process begins. If the connection times out,
then the process starts all over again. It would also explain why spooled
files with multiple pages never print.

To determine if this is actually true, look at the output queue. If a spooled
file continuously stays in SND status, go to the writers job log and look for
TCP3701 type messages (cannot send file...). Increasing the time out on the
printer will help (set it as large as you can for your environment). Also,
increasing the amount of memory in the *SPOOL memory pool if possible. Doing
this will speed up the transformation process.

"L. Ed. Nelson" wrote:

--
Rodney A Johnson
Technical Team Lead for AS/400 Spool
Dept GJC
IBM Rochester, Minnesota

The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, IBM. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.