Remote Printer Hung

From MidrangeWiki
Revision as of 03:40, 1 June 2005 by Al Mac (talk | contribs)
Jump to: navigation, search

One of the problems that can be a contributor to solving Degradation - suppose you had a communication line go down, while printer going at remote site, and the 400 manages most of the task of reconnecting devices, but the printer is stuck because it cannot recover the print job that was in the printer communications cache when the communications line went down, or perhaps the 400 not know if the forms aligned right, or any number of other possibilities.

So it cannot do the next recovery step because it is hanging on an earlier recovery step. The simplest thing to do here is

  1. Determine the last page printed ... now this OUGHT to be done by someone at the remote site, because the 400 may have sent 25 pages to the print buffer, but only 22 printed before we lost the connection, like perhaps there was a power outage at the remote site, and the printer also lost what was in its buffer.
  2. Put that report on hold, and change its restart to print page based on what is next needed.
  3. Bring everything down on the printer, then bring everything back up again.
    1. Some of this may need to be done with a person whose 400 security is higher than the average user.
    2. You may need to stop the job that is using the printer writer ... you can locate that with GO CMDLCK and then specify the printer involved.
    3. You need to stop the writer to that printer, but before it will let you do that, you may need to stop the job that is using the printer writer.
    4. You may want to vary off the printer, but you need to stop the writer before this.