TCP/IP AS/400 printing
George Applegate
I have a new Gestetner 6002 copier that is attached to my network. I
would like to configure this to be used as a network printer on our
AS/400...
Does anyone know how I can accomplish this? I can set the address on
the Gestetner (IP address) but I'm not sure how to Create the Device
Description on the AS/400 and what to fill in for the different
parameters.
Any help would be GREATLY APPRECIATED.
thanks,
ga
George Applegate
gapp...@fscoop.com
Richard Huelbig
I work for Ricoh Corporation--we manufacture not only Ricoh devices but
Savin and Gestetner as well. If I'm not mistaken the Gestetner 6002 is the
equivalent of the Aficio 1060. I've written a couple of white papers on
AS/400 printing (and I've recently completed a paper on SAP printing). If
you follow this link it will take you to the support and knowledgebase
section of the Ricoh web site:
http://www.ricoh-usa.com/support/knowledgebase.asp
Click on the white papers section and you'll see one called AS/400 Printing
With Ricoh MFP And Printers. I think that paper should have everything you
need to setup your printer. You'll find the information you need for the
device description (using the CRTDEVPRT command), or you can use the CRTOUTQ
command as an alternate print configuration. The main difference, for this
discussion, between the two is that the device description will be
configured to print to the port 9100 of the printer, whereas using the
CRTOUTQ command to setup printing will configure your AS/400 to print to the
6002's internal device (or queue) name. (I'm pretty sure the device name
used by the 6002 is "lp", all lower case, not quotes).
Anyway, I hope this helps some. Please don't hesitate to repost if you have
additional questions.
Regards,
Richard Huelbig
George Applegate
Wow!!! Thanks for the quick response!! I am sure this will help me get
this up and working!! Thanks again for being so quick to reply!!
ga
"Richard Huelbig" <hue...@optonline.net> wrote:
George Applegate
gapp...@fscoop.com
Richard Huelbig
One other point that is worth mentioning. If you are going to use a device
description, meaning that you'll print to the 6002's port 9100, you'll have
to enable the bidirectional printing on that port--this is done on the
machine.
You'll first want to get to a command line (at your computer) and enter the
command TELNET, along with the IP address of the 6002. For example, you
might type the command TELNET 10.10.10.40.
Then when the PASSWORD prompt appears, enter the word "password" (without
the quotes).
Now you should see a prompt on the screen that looks like this "msh>".
You're now in a TELNET session with the machine.
At the "msh>" prompt, type "diprint bidirect on". The device should respond
"bidirect on".
Now, and this is importnat, do not simply close the terminal screen. If you
do, your change will not be saved and the bidirectional capability will not
have been enabled. To prevent this, at the "msh>" prompt, enter the command
"logout".
You'll now be asked to "Type Yes To Save The Changes, And Press The ENTER
key". Type the complete word "Yes" and press the ENTER key. A message will
appear stating that the changes have been saved.
That's all there is to it...
Good luck and if you've got additional questions feel free to ask.
Regards,
Richard Huelbig
George Applegate
I think I have done everything as indicated, but when I go to print,
it ends the writer and doesn't print.
I am getting a CPD338D message - From Program - QWPPJLDR in QSYS,
Instruction *STMT TO Program is QWPPJLDR in QSYS Inst STMT.
From module - WPPJLDR
From procedure - Socket_Recv
Statement - 40
To module - WPPJLDR
To procedure - _C_pep
Statement *N
An error occurred while receiving data.
A communications error occurred while receiving data from remote
device at RMTLOCNAM 10.10.1.63. The error code is 3426. (What is that
error code????). This error can also occur when the system attempts
to print to the remote device after it has been powered off and on
while the printer writer remains active.
From the log on the printer I see this:
#[diprintd(48)]03/11/09 12:04:37 receive job reject. now rebooting.
WARNING:
#[diprintd(48)]03/11/09 12:05:38 receive job reject. now rebooting.
WARNING:
#[diprintd(48)]03/11/09 12:17:36 receive job reject. now rebooting.
WARNING:
Any thoughts on how I can figure out what is wrong?
This shouldn't be a big deal as I am able to print to the Gestetner
from word on all PC's, but I do see the gateway is entered wrong...I
tried to reenter that on the printer and it didn't take...it shows the
10.10.1.63 on the copier, but when I telnet in, it shows 101.10.1.63.
Still, I am able to print from PC's in word or excel, so I don't think
that's the issue.
I also did the diprint bidirect on, and logged-out and saved it as you
indicated me to do.
Any thoughts or suggestions???????????????????????????????
George Applegate
Everything is okay now. I just had to power off/on the copier.
Apparently when I was trying to print stuff earlier with some wrong
values filled in on the device description, it must have caused a
communication line error or something. I powered it off and back on
and now everything works slick as a whistle. Thanks so much for all
your help and your paper.
By the way, I got the following message from this fellow, John Garen,
and talk about a great idea - it would only necessitate having client
access on the server and the session opened...
Thanks,
ga
--------------------------------------------------------------------------------------------------------------------------------
There is a drop dead easy auto-create way of doing this.
If you have client access.
Load up client access on your windows print server platform, I am
assuming
this printer can print from windows. And configure client access to be
a
printer and use the network printer for the client access. It will
auto
create the device you need. Works really swift for us.
v5r2
-------------------------------------------------------------------------------------------------------------------------
George Applegate
gapp...@fscoop.com
Richard Huelbig
Good to hear that everything is working fine!
I also want to thank you for the information passed to you regarding client
access.
If there's anything else I can help you with just ask.
Regards,
Richard Huelbig