Printer Problems since relocation and client upgrade
Home > IT Answers > AS/400 > Printer Problems since relocation and client ...
EventHorizon
0 pts.
0
Q:
Printer Problems since relocation and client upgrade
AS/400, Database
Printer will not start.

Recently we moved a PC and a printer to a different desk and once everything was hooked back up we can't get the AS/400 to recognize the printer. I get a message that states:

Device PAMPRT1 not available.

The status is 'Vary on pending'. The spool writer, labeled P9 shows the status as 'End'. I've tried starting it but it keeps saying the device is not available. We can print through the network so it is attached and the network is seeing the printer, but the AS/400 sees the printer as powered off or not available. Other than that change from one desk to another I also upgraded to a different version of the ISeries Client. I removed the old version which I believe was 4.2(or .3) and installed 5.2.

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. Typically someone will have a job waiting on their spool, they will tell it to print to P9(PAMPRT1) and it will go but because the PAMPRT1 is showed powered off/not available...we are unable to use it. Please help. Thank you.
ASKED: Aug 25 2005  10:47 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Stegman
0 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
I am sure you have down some research on the web, but I found this site, that may help. http://faq.midrange.com/data/cache/1.html

There is a printing folder, but I am not sure if it will have all that you are looking for.

Take care
Last Answered: Aug 26 2005  11:47 AM GMT by Stegman   0 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

JPLamontre   0 pts.  |   Aug 29 2005  8:23AM GMT

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.

 

AS400PR0   0 pts.  |   Aug 29 2005  12:05PM GMT

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.

 

TomLiotta   7655 pts.  |   Nov 2 2009  2:55AM GMT

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

 
0