RE: V4R3 Writers placing Spools on Hold

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

Check the job log of the print writer for the specific reason the spooled
files are going on hold.  If the writer is a TCP/IP remote, may I suggest
changing to a device instead?  The device method is much more robust than
the OUTQ-only method, and will allow PAGERANGE and COPIES to work properly
too.

Buck Calabro
Aptis; Albany, NY

> -----Original Message-----
> From: Bill Harrell 
> Sent: Tuesday, November 02, 1999 5:42 PM
> To:   'Midrange-L@midrange.com'
> Subject:      V4R3 Writers placing Spools on Hold
> 
> 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 ?
> 
> Bill Harrell
> 
+---
| 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
+---