RE: V4R3 Writers placing Spools on Hold

["Gallagher, Debbie" <dgallagher@xxxxxxxxxxx>]

Bill:

I had endless aggravation with this at a client site last year, and the
software
vendor kept telling the client that they must have set the printers up
wrong, or
if not that then they needed to check into what ptfs IBM had to fix such a
problem.

As project manager, I continued to nag the vendor - they had set up the
printing, and it was only a couple of reports that always were the problem.
The
vendor finally looked a the problem and they had shipped the product with
the
wrong data stream specified - e.g ipds instead of scs or the other way
around. I
don't remember exactly the specifics, but that's the gist of it. Yours may
be
different situation, but that's the same event that occurred for my client.
End/restart writer - sometimes even that didn't work.

Debbie Gallagher
 
-----------------------
Original Message
-----------------------
Date: Tue, 2 Nov 1999 17:42:14 -0500 
From: "Bill Harrell" <bill.harrell@twcable.com>
Subject: V4R3 Writers placing Spools on Hold

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 ?

- ---------------------------------------------------------------
Bill Harrell
Division AS400 Systems Analyst
Morrisville, North Carolina  27650
bill.harrell@twcable.com
+---
| 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
+---