Re: V4R3 Writers placing Spools on Hold

Bill, I saw the same thing at a client site. Here is my post about the problem:
> OK folks,
> I've got one that has me stumped. Printing to a remote writer through
> TCP, the printer appears to be printing fine. After a variety of print
> files are printed, an error occurs on the Host Print Transform of a
> spool file, and the spool file is placed on hold. At this point, any
> spool file in the output queue is placed on hold. The only way to
> correct the problem is to end the writer and restart it. At this point,
> ALL of the files will print, including the one that caused the problem
> (I think it is the one causing the problem) I have only seen joblogs of
> the problem, and each time it is the same spool file, but that may be
> misleading, because almost all of the printing for that printer is this
> one particular spool file.
>

One thing about the problem is that the writer's job log showed an error in the
HostPrintTransform portion of IBM's writer code. this was to a TCP/IP writer.
client could not reproduce the problem when I was on site, and refused to save
the spool files he claimed were causing the problems.

Bob

Bill Harrell wrote:

> After we upgraded to V4R3, we have observed the sporadic problem of Spools
> waiting to print on a writer going on hold.  This problem occurs randomly
> and we cannot yet identify the cause.
>
> When the spools are released, they immediately go back on hold again without
> printing.  No error messages are written to the Sysop / History / or problem
> logs.
>
> If the writer is ended, and then restarted, the spools will then print.    T
>
> Has anyone else experienced this problem and is there a PTF to cure it ?
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---