Comments on: Printer Problems since relocation and client upgrade

By: tomliotta

tomliotta — Mon, 02 Nov 2009 02:55:34 +0000

If I emulate a print session the printer will of course go active but this does not work for the way we use the printer.

That doesn’t make any sense. If that is actually true, it implies that it was always true. Either the printer is accessible through a printer emulation session, in which case it always was accessible that way, or you changed how the printer is connected — it was previously a network printer and now it is a local PC printer.

The error you reported was “Device PAMPRT1 not available.” A ‘device’ is either created because it is a LAN printer and it was configured by a person, or it was created through a PC printer session. It will be one or the other. The cabling that connects the printer will be either to a network port (LAN printer) or to a PC (PC printer session).

If it’s going to be a printer session now, then ensure that the session starts when the PC is started (and maybe keep the PC running.)

Tom

By: as400pr0

as400pr0 — Mon, 29 Aug 2005 12:05:22 +0000

Hello,

The following should help explain at least what is happening.

When the first spool file enters the queue it sends a signal to the printer to let it know that it wants to print. The spool file goes to pending.

The printer sends a signal telling the outq that it is ready to print. This message is not getting to the outq. The printer waits for the spool file to arrive.

Then the pending file gets held so that the following files go to the head of the line. Since the printer is already expecting the spool files, they go through with no problem. If the pending spool file gets released fast enough, it will go through as well.

You have to find out what is preventing printer’s signal from reaching the outq. It could be a bad printer cable, or the wrong type of printer cable, external printer server box, ect…

It could also be that the printer is getting a signal from somewhere that is telling it not to send out it’s PJL status. This signal could come from somewhere on the network or from a print from a pc with a corrupt driver.

By: jplamontre

jplamontre — Mon, 29 Aug 2005 08:23:55 +0000

is it an IP printer ?
Have you change any parameter in the printer ? if so, try go back.
Does it ping from your PC (yes it seems) ?
Does it ping from the 400 ?

What tool say that printer is unavailable ? wrkwtr ? wrkcfgsts ?

Is the device ONLINE(*YES)

Have you an other device active and using the same material ? if yes, destroy the unvorking printer then rebuild the device based a copy of a well-running device
or
if you have save your device description in a clp (with rtvcfgsrc), then rebuild your device from this save.