|
* Put the report on hold * Stop the writer* Vary off the printer and verify "it took" (sometimes it cannot vary off until some other error condition is resolved, that we can have a hard time finding what condition that is) ** If you could not get it to vary off, display LOCKS for the printer to find what job is using it ... I have on occasion had to stop all printers, stop QSPL subsystem ... the cause was some OS/400 task that writes directly to printer without sharing spooler
* Turn the printer off/on * Reverse the vary off/ locks resolution steps * Start the writer * Release the report from on-hold - Al Macintyre http://www.ryze.com/go/Al9Mac BPCS/400 Computer Janitor ... see http://radio.weblogs.com/0107846/stories/2002/11/08/bpcsDocSources.html
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.