If it is a network printer, just "create" another LDEV with the same
IP. The HP doesn't care if you have more than one LDEV to the same IP
(or DNS).
Raise the outfence on the original LDEV.
Once created, do a spoolf of any old spool files on that ldev to the new
ldev.
You can do it in a job that reschedules itself if it persists.
The first spool file still in a print state will probably be stuck, but
this technique should fix subsequent spool files.
The situation probably won't go away until the next reboot.
On 6/17/19 7:54 AM, John Sommer wrote:
> All,
> Somehow, a printer connected to our HP3000 received a "non-character" input and stopped printing.The spooler was told to stop so that the queue could be closed and restarted.
> Doing a show command on that spooler reports " *STOP .......CLOSING CONN "A little research found info that stated that it could take 24 hours before the HP3000 gives up and closes the connection.Well.......it has been a week now, and no change. The LDEV is still stuck in the closing mode.
> Also tried to just remove it from the config file and re-add it, but that did not work either.The HP3000 is used so much, it can't really be shut down any time soon.
> Does anyone have another idea that might make the HP3000 release its hold on that printer LDEV so that it can be cleared and reconnected?
> Thanks for any thoughts,John
>
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
--
Tracy Johnson
BT
NNNN
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
