Configure Printer as400

Options to Configure a Printer on an IBM System i

Technote

There are many ways in which a printer might be configured; it depends on the type of printer, the capabilities of the printer, and how the printer is attached. This document discusses the most common methods of configuring a printer on an IBM System i and the general requirements for each method. For more specific information on requirements, see the documents listed under each method. The documents listed in this document are available at the following Web site: http://as400service.rochester.ibm.com/s_dir/slkbase.NSF . This document was last updated on 09/07/2010. If Your Printer Is Attached to the Network Using TCP/IP If your printer is attached to the network and is using TCP/IP to connect, the options for configuring the printer are:

o A Remote Output Queue (RMTOUTQ)o A *LAN 3812 PJL device descriptiono A *LAN 3812 SNMP device descriptiono A *LAN 3812 IPP device descriptiono A *LAN *IPDS device description For information on ASCII printers from various manufacturers, in particular on whether they can be configured using a *LAN 3812 PJL device description, *LAN 3812 SNMP device description, *LAN 3812 IPP device description, or Remote Output Queue (RMTOUTQ), refer to the following documents in the Rochester Support Center knowledgebase:

17690939, Information on Printers from Various Manufacturers :

11944305, Version 5 Printer Model Settings for Host Print Transform

(HPT): The requirements for all network-attached printers using TCP/IP are that the network adapter is compatible with the printer and it has a static TCP/IP address. The sections on the various options will list some additional requirements for that type of configuration.

1 Remote Output Queue or SNDTCPSPLF and LPR Commands Support for printing using the TCP/IP Line Printer Requester (LPR) and Line Printer Daemon (LPD) protocols is available in the base code for V2R3M0 (R230) OS/400 and above for the Send TCP/IP Spooled File (SNDTCPSPLF or LPR ) command, and in the base code for V3R1M0 (R310) OS/400 and above for Remote Output Queues (RMTOUTQs). Support for Remote Output Queues, as well as the SNDTCPSPLF and LPR commands, is largely dependent on the internal network interface card (NIC) or external print server used with the printer. Therefore, this column is as much of a statement about the NIC or print server typically shipped with the printer, than it is about the printer itself. If it is unclear whether the NIC, print server, or printer supports LPR/LPD, contact the manufacturer. For more information on Remote Output Queues, refer to the following documents: 8983237, Configuring a Remote Output Queue (RMTOUTQ):

Document information

Software version:

5.4.5, 6.1, 6.1.1, 7.1, V3R2M0, V4R4M0, V4R5M0, V5R1M0, V5R2M0, V5R3M0, V5R3M5, V5R4M0, V5R4M5, V6R1M0, V6R1M1

Operating system(s): OS/400

Reference #: 22393632

Modified date: 2010-09-07

Page 1 of 5IBM - Options to Configure a Printer on an IBM System i

2/10/2011http://www-01.ibm.com/support/docview.wss?uid=nas1455975a3bf2ac71e862569f9006ba...

24291009, Configuring a Remote Output Queue (RMTOUTQ) to a

Thermal Label Printer: 24305723, Configuring a Remote Output Queue (RMTOUTQ) to

Another IBM System i System Using TCP/IP: 8233537, Recommended Remote Printer Queue Values for Remote

Output Queues (RMTOUTQs): 19254944, Configuration Settings and Error Messages for Remote

Output Queues (RMTOUTQs): 14143423, Capabilities and Limitations of Remote Output Queues

(RMTOUTQs): 7995114, Creating a Dummy Device Description to Use with a

Remote Output Queue (RMTOUTQ): 18762910, Configuring a *LAN 3812 Device Description that Uses

the LPR Print Driver (TSPLPRD) Exit Program: 12594243, TSPRWPR Remote Writer Page Range Support Exit

Program: 11401901, Using Host Print Transform (HPT) with a Remote Output

Queue (RMTOUTQ): 2 *LAN 3812 PJL Device Description

The term PJL refers to the Printer Job Language protocol from HP. PJL allows for two-way communication with the printer when attached to the LAN using a print server that also supports bidirectional PJL. Support for the PJL print driver is available in the base code for V4R1M0 (R410) OS/400 and above, and was added to V3R7M0 (R370) OS/400 through PTFs. Support for the PJL print driver is largely dependent on the internal network interface card (NIC) or external print server used with the printer. If it is unclear whether the NIC, print server or printer supports PJL, contact the manufacturer. For more information on *LAN 3812 PJL device descriptions, refer to the following documents: 8695149, Configuring a *LAN 3812 PJL Device Description: 12454128, Recommended PJL Port Number Values for *LAN 3812

PJL Device Descriptions: 14461435, Configuration Settings and Error Messages for *LAN 3812

PJL Device Descriptions: 7532429, Using Host Print Transform (HPT) With an *LAN Device

Description: 3 *LAN 3812 SNMP Device Description

The term SNMP refers to Simple Network Management Protocol. SNMP allows for two-way communication with the printer when attached to the LAN using a print server that also supports SNMP. Support for the SNMP print driver is available in the base code for V4R5M0 (R450) OS/400 and above, and was added to V4R3M0 (R430) and V4R4M0 (R440) OS/400 through PTFs. Support for the SNMP print driver is largely dependent on the internal network interface card (NIC) or external print server used with the printer. If it is unclear whether the NIC, print server or printer supports SNMP, contact the manufacturer. For more information on *LAN 3812 SNMP device descriptions, refer to the following documents: 19932815, Configuring a *LAN 3812 SNMP Device Description: 19934440, Recommended SNMP Port Number Values for *LAN 3812

SNMP Device Descriptions:



19935220, Configuration Settings and Error Messages for *LAN 3812

SNMP Device Descriptions: 7532429, Using Host Print Transform (HPT) With an *LAN Device

Description: 4 *LAN 3812 IPP Device Description

The term IPP refers to the Internet Print Protocol. IPP allows for two-way communication with the printer when attached to the LAN using a print server that also supports IPP. Support for the IPP Print Driver is available in the base code for V5R2M0 (R520) OS/400. Support for the IPP Print Driver is largely dependent on the internal network interface card (NIC) or external print server used with the printer. If it is unclear whether the NIC, print server or printer supports IPP, contact the manufacturer. For more information on *LAN 3812 IPP device descriptions, refer to the following documents: 27285732, Configuring a *LAN 3812 IPP Device Description: 27285056, Recommended Remote Location (RMTLOCNAME) Values

for *LAN 3812 IPP Device Descriptions: 27295239, Configuration Settings and Error Messages for *LAN 3812

IPP Device Descriptions: 7532429, Using Host Print Transform (HPT) With an *LAN Device

Description: 5 *LAN *IPDS Device Description

The term IPDS refers to the Intelligent Printer Data Stream. IPDS allows for two-way communication with the printer when attached to the LAN, provided the printer has the IPDS feature installed and using an internal print server that allows the IPDS data stream to pass through to the printer. IBM Print Services Facility (PSF/400) is required for network-attached IPDS printers. For more information on *LAN *IPDS device descriptions, refer to the following documents: 8234913, Configuring a *LAN IPDS Device Description: 24475739, Recommended IPDS Port Number Values for *LAN IPDS

Device Descriptions: 7992809, Support for IPDS Printing via Lexmark Optra Printer Using

TCP/IP: 8063814, Using the 7913 Brick for TCP/IP AFP Printer Attachment to

the AS/400 System: 24483927, Configuration Settings and Error Messages for *LAN IPDS

Device Descriptions:

If Your Printer Is Attached to the Network and Using the Lexlink

Protocol The requirement for this configuration is that the printer is attached to a Lexmark network adapter that can use the Lexlink protocol, such as the Lexmark MarkNet XLE or the MarkNet Pro, or that it is a Lexmark printer with an internal Lexmark network card. The Lexlink protocol cannot be routed across networks, so the router would need to be configured to bridge the Lexlink protocol. For information on configuring *LAN 3812 Lexlink device descriptions, refer to the following document:

17604455, Configuring Internal and External *LEXLINK Device

Descriptions:

If Your Printer Is Attached to the Network and Using SNA The requirements for printing using SNA are that a communications line, controller, and device



description are configured for APPC or APPN support. Also, the IBM-supplied subsystems QSNADS and QSYSWRK, the Mail Server Framework job QMSF, and the Object Distribution job QNFTP all must be active. For additional assistance configuring or troubleshooting SNA, contact the Peer queue. For information on configuration communicating over SNADS, refer to the following documents:

11855333, Printer Passthrough or Remote Output Queues:

7995114, Creating a Dummy Device Description to Use With a Remote

Output Queue (RMTOUTQ):

12051129, Configure SNADS and Setting Up SNA Distribution Services :

12844012, SNADS - Basic Troubleshooting Process:

If Your Printer Is Twinax Attached If the printer is twinax attached to a dumb terminal or to a controller, the best way to configure this is to let it autoconfigure. The system value QAUTOCFG must be turned on. The address set for the printer must be available. For a printer attached to a dumb terminal, some additional setup might need to be done on the dumb terminal. If the printer is twinax attached to a remote workstation controller, it will autoconfigure if it is a 5494 controller. If the printer is attached to a 5294 or 5394 controller, it must be configured manually. For additional assistance configuring a printer on one of the remote workstation controllers, contact the RWS queue. For information on configuring devices on a remote workstation controller, refer to the following documents:

18120337, 5394 Detailed Configuration for X.21 (No OS/400

Information):

18111333, 5394 Detailed Configuration for X.25 (No OS/400

Information): For ASCII printers, Host Print Transform can be turned on after the device description has been configured. The appropriate Manufacturer Type and Model for the printer must be specified. For IPDS printers, Advanced Function Printing can be turned on if the Print Services Facility (PSF/400) is installed.

If Your Printer Is Attached to a PC An emulation program must be run on the PC to allow the IBM i system (or IBM iSeries system) to print to it. This emulation program can be IBM iSeries Access or some other emulation program that can create a printer session and configure a device on the IBM i system. The type of emulation program used might have its own special requirements, so refer to the documentation for the program. Refer to Rochester Support knowledgebase document # 6163631 for additional information on connection and configuration methods not mentioned here. For information on printing on a PC running Client Access/400, refer to the following documents:

23355320, iSeries Access for Windows: Configuring a PC5250 Printer

Session:

17211755, Client Access Express: Configuring a PC5250 Printer Session:

8694509, Windows 95/98/NT: Configuring a PC5250 Printer Session:

15365924, Capabilities and Limitations of Client Access Express Printing:

6163631, Support for PC5250 Printer Sessions Over TCP/IP (and Its

Alternatives):

29263358, Client Access Express: Configuring a PC5250 Multiple Sessions

Batch File:

13730932, Configuring a PC5250 Multiple Sessions Batch File:

If You Are Printing from a PC to a Printer on an IBM i System Depending upon the version of System i Access for Windows (also known as iSeries Access for Windows or Client Access/400 in earlier versions), the printer can be installed on the PC as a network printer or it can be set up under IBM AS/400 NetServer or IBM iSeries NetServer. Refer to the documentation for the version of Client Access or iSeries Access for the requirements. For information on configuring an AS/400 NetServer or iSeries NetServer print share, refer to the following documents:



11600129, Getting Started with iSeries NetServer:

15222518, IBM iSeries NetServer Security Requirements for Printing:

14385318, Creating iSeries NetServer Printer Shares:

14323730, Adding a Printer that Uses an iSeries NetServer Share:

16965557, Configuring Windows 95/98/NT/2000/XP to Fax PC Output

Using Fax/400 and IBM iSeries NetServer: For information on configuring a Network Printer using R320 Client Access for Windows 95/NT (5769-XD1), refer to the following documents:

10024335, Installing a Network Printer on Windows 95/98:

13180855, Installing a Network Printer on Windows NT:

If You Are Converting Spooled Files to PDF instead of Printing them to

a Printer The IBM Infoprint Server for iSeries product (5722IP1) that can be used to convert spooled files to Adobe Acrobat PDF format and optionally send the PDF file in an email, store the PDF file in a stream file in the Integrated File System (IFS), store the PDF file is a *USERASCII spooled file, or a combination of these. For information on configuring a *LAN IPDS device description and PSF Configuration (PSFCFG) object that uses Infoprint Server to convert spooled files to PDF, refer to the following documents:

26431812: Configuring a *LAN IPDS Device Description for E-Mail

Function of InfoPrint Server

399896086: Configuring an *IPDS Device Description for PDF Transform

Function of IBM Infoprint Server (Without a Mapping Object) For more information on Infoprint Server, refer to the following document which summarizes

all of the reference materials available for this product:

337462692, Finding Additional Information for Infoprint Server and PDF

Mapping Exit Programs :

Additional Documents

17690939, Support for Various ASCII Printers:

Recommended Fixes (PTFs) For a list of the latest PTFs refer to the Recommended Fixes Web site, which is available at:

http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes

System i Support IBM disclaims all warranties, whether express or implied, including, but

not limited to, the implied warranties of merchantability and fitness for

a particular purpose. By furnishing this document, IBM grants no

licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006,

2007, 2008, 2009, 2010 IBM Corporation. Any trademarks and product

or brand names referenced in this document are the property of their

respective owners. Consult the Terms of use link for trademark

information.

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

