Home > IT Answers > AS/400 > Very New to AS/400 Operations (and I hate printers already)
Jean43
370 pts.
 Very New to AS/400 Operations (and I hate printers already)
AS/400 print errors, AS/400 printers, AS/400 printing, CRTDEVPRT, Okidata 590
I have an Okidata 590 impact printer that needs to be created on our AS/400. I used CRTDEVPRT to create the new printer device, but I'm not sure what to select in all the parameters and the printer will not print. I can ping the device on the network. And I get the outq to say RLS/WTR but the print jobs in the queue never get past the RDY state. They don't even go to PND. I must have an incorrect parameter.....any ideas on this? Thanks.

Software/Hardware used:
ASKED: February 24, 2009  5:22 PM
UPDATED: February 26, 2009  4:48 PM
RELATED QUESTIONS
Answer Wiki:
The Okidata 590 may not be capable of printing output direct from the AS/400 without using a protocol converter. If your system has PSF/400 then one possible approach is to output IPDS and convert it to an Epson printer language that the Okidata 590 will understand. I have a software product that will do this. Please feel free to visit my Public Profile and contact me if you have any questions.
Last Wiki Answer Submitted:  February 24, 2009  10:27 pm  by  Oneprint4ipds   30 pts.
All Answer Wiki Contributors:  Oneprint4ipds   30 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

There are Okidata dot matrix printers attached to our AS/400 via HP JetDirect boxes. This requires no special software which we really like. Just need to configure your output queue for an IP attached printer and enter the Okidata printer model in the MFRTYPMDL parm and you should be good to go.

WoodEngineer
 5,555 pts.
 

The printer is connected to an HP JetDirect box. Here’s what I’ve selected when I created the device using CRTDEVPRT. I hit enter and let the system create the outq with the same name. Even though the printer looks like it started, the print jobs just stay in RDY mode. Do you see anything that I missed or entered incorrectly? Any suggestions for me to try? Thanks.

DevDesc = wheyship
DevClass = *LAN
DevType = 3812
DevModel = 1
LAN Attachment = *IP
Port = 0
Online at IPL = *YES
Font ID = 11
Point Size = *NONE
Form feed = *Autocut
Sep. Drawer = *FILE
Sep. Pgrm = *NONE
Printer Error Msg = *INQ
Msg Queue = QSYSOPR
Activation Time = 170
Inactivty Timer = *ATTACH
Host Print Transform = *YES
Manuf type and model = *OKI590IBM
Paper Source 1 = *MFRTYPMDL
Paper Source 2 = *MFRTYPMDL
ASCII code = *NO
Image Config = *NONE
Graphic Char Set = *SYSVAL
IP = ’10.1.2.228′
User defined option = *NONE
User defined object = *NONE
Data transform pgm = *NONE
System driver pgm = HPPJLDRV
Secure connectin = *NO
Validation list = *NONE
Support duplex = *UNKNOWN
Support color = *UNKNOWN
Pages per min black = *UNKNOWN
Pages per min color = *UNKNOWN
Location = *BLANK
Data streams supported = *UNKNOWN
Description = SP shipping plant
Remove network identifier = *NETATR
Workstation customizing object = *NONE
Authority = *CHANGE

Jean43
 370 pts.
 

Hello

You mighjt try changing the port from 0 to 9100.
RayV

RayV
 65 pts.
 

Forgive me, but a STRPRTWTR command needs to be done to connect the printer to the outq.

TimRac
 25 pts.
 

Our Okidata printers do not have a DEVD on the AS/400 – just an output queue. This simplifies things and works well. When starting printers attached in this manner we use STRRMTWTR.
There is a technique where a DEVD is created. We’ve tried both techniques and found no advantage to the DEVD method.

WoodEngineer
 5,555 pts.