AS400 Printing to HP4200 using IP

[KeironHodgson]

Can anyone help with this please:

When sending a print to the HP4200 all is fine until the printer runs out of paper.

Once reloaded with paper and checking on the print queue on the as400 it says that the queue is not associated with a started printer.

This then has to be reset. I have set the printer up to store up to 100 jobs and job timeout for 1 day with autocontinue.

Is there anyway of allowing the printer to run out of paper, refill it and it continue to print without having to reset the service on the as400?

Many thanks.

Frustrated Support engineer

 

[iSeriesCodePoet]

How do you have it set up? With a device or remote printer?

iSeriesCodePoet
IBM iSeries (AS/400) Programmer

See my progress to converting to linux.

http://koldark.hopto.org/linux/

 

[KeironHodgson]

It is a remote printer with a natted IP address.

 

[iSeriesCodePoet]

Hmm... we have never has a problem with this. We about about 30-40 printers setup this way (using the crtoutq cmd). I don't know if we have a HP 4200 connected though. I don't know how to help you beyond this... sorry.

iSeriesCodePoet
IBM iSeries (AS/400) Programmer

See my progress to converting to linux.

http://koldark.hopto.org/linux/

 

[KeironHodgson]

Thanks for having a look.

I will put a Sniffer on and see what traffic is passing between the as400 and printer.

Hopefully it is something that can be switched off with an option on the printer.

Will post results on this thread.

If anyone else has any ideas in the meantime please post them in.

Thanks.

 

[Krash878]

Remote out queues are very unpridictable. When the AS400 sends a file to a remote printer it sends it only wanting to know if the printer got the print job. Once the printer has it the AS400 could care less what happens. If your printer is not storing the print job before it prints it, then you may want to invest in another printer that supports saving print jobs.

Krash

 

[KeironHodgson]

Results from Sniffer tracing:

The printer when out of paper is sending the as400 "printer status online=false"
Once refilled is sending "printer status online=true".

Unfortunately I have discovered the user sending the prints is telling the as400 to continue printing at the message waiting prompt and then refilling the printer with paper, instead of correcting the printer first and then telling the as400 to continue.

I have gone through this with the user and not surprisingly the printing is now working fine.

Maybe the as400 shuts the print down when asked repeatedly to send to a printer that is not ready?

Just another example of PEBCAK (problem exists between chair and keyboard).

Hopefully this will be of use to someone.

 

[iSeriesCodePoet]

That makes sense... TUF, the user factor ;-)

iSeriesCodePoet
IBM iSeries (AS/400) Programmer

See my progress to converting to linux.

http://koldark.hopto.org/linux/

 

[technick400]

We are setting up our first HP4200 via IP on our as400. We have 40+ printers already setup via IP, but this one seems to be giving us greif. I was wondering what method you used to attached the printer to your as400? Did you create a device description or a remote output queue? If you did a device description, could you provide the details?

Thanks
-nick

 

[iSeriesCodePoet]

I user remote outqs.

iSeriesCodePoet
iSeries Programmer/Lawson Software Administrator

See my progress to converting to linux.

http://koldark.hopto.org/linux/

The Programmer's Knowledge Base ->

http://koldark.hopto.org/twiki/bin/view/Programkb/WebHome

 

[kgreer]

I am trying to eliminate all of are client access sessions running are printers. We are using HP4000 printers. I was able to create a outq with CRTOUTQ. This works fine until you try to run a query against that printer. It needs a Device Description as well. Does anyone know how to create a device description with all the parameters. I have created on but the printer dies when you send a job to be printed. Any comments would be helpfull.

-ken

 

[chucklemark]

We use the same procedure as yourself and I create device descriptions as follows:
CRTDEVPRT DEVD(xxxx) DEVCLS(*VRT) TYPE(3812) MODEL(1) ONLINE(*NO) FONT(011)

where DEVD(xxxx) is the name of the outq your have alreay created.

Also ensure that the OUTQ you create is in library QUSRSYS as this is where OS400 expects it to be. If you create the OUTQ in another library apart from qusrsys and you then use the above command to create a devd you will end up with 2 OUTQ's of thge same name but in different libs and only one will have a devd attached to it.
If you have already created the outq in qusrsys and then use the above cmd to create a devd yopu will get a message at the bottom of your screen teling you that outq XXXX already exists in qusrsys.
Hope this is of help.
I have user it many times with no problem , having found it on an AS400 technical web site.
Let me know if you want the URL to this site as it has loads of technical tips - it is an IBM site.

Regards - Mark