Technote

This document contains information on configuring and using a Remote Output Queue (RMTOUTQ) to send spooled files to one IBM System i to another using the LPR/LPD (Line Printer Requester/Line Printer Daemon) protocol. Requirements include a TCP/IP interface and IP address configured on both systems and a Line Print Daemon (LPD) server running on the destination system. For information on configuring a Remote Output Queue (RMTOUTQ) for a printer or another type of system (for example, a Microsoft Windows NT Server or UNIX Server), refer to one of the following documents:

8983237, Configuring a Remote Output Queue (RMTOUTQ) Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document '   Configuring a Remote Output Queue (RMTOUTQ)'
24291009, Configuring a Remote Output Queue (RMTOUTQ) to a Thermal Label Printer Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Configuring a Remote Output Queue (RMTOUTQ) to a Thermal Label Printer'

For information on configuring and using a Remote Output Queue (RMTOUTQ) to send spooled files to one IBM System i to another using SNA, refer to the following document:

11855333, Printer Passthrough or Remote Output Queues Database 'AS400 Support Line KnowledgeBase', View 'All Documents', Document 'Printer Passthru or Remote Output Queues '

This document was last updated on 4 January 2011.


Hide details for Requirements and RestrictionsRequirements and Restrictions 
Requirements and Restrictions 

Requirements include a TCP/IP interface configured in the operating system, an IP address on the printer side, and a Line Print Daemon (LPD) TCP/IP process running on the print server. Restrictions include no page range printing. Controlling the output can also be a problem because of the lack of control over the sending of spooled files. Once a spooled file has started sending, a user may have a tough time stopping the printing from the operating system side. Putting the spooled file on hold or deleting it may not be successful. For a more complete listing of restrictions, refer to the following Rochester Support Center knowledgebase document:

14143423, Capabilities and Limitations of Remote Output Queues (RMTOUTQs): Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Capabilities and Limitations of TCP/IP Remote Output Queues'

Hide details for Required PTF LevelsRequired PTF Levels 
Required PTF Levels 

There are no required PTFs in order to print using a Remote Output Queue (RMTOUTQ), but getting the latest Print Group PTF will typically help you avoid problems:

PTF Number Licensed Program Version Description
SF99356 5761SS1 V6R1M0 610 Print Group PTF for V6R1M0
SF99347 5722SS1 V5R4M0 540 Print Group PTF for V5R4M0
SF99346 5722SS1 V5R3M0 530 Print Group PTF for V5R3M0
SF99345 5722SS1 V5R2M0 520 Print Group PTF for V5R2M0

Otherwise for a list of the latest PTFs, including PTFs that are not yet included in the latest Print Group PTF, contact the Rochester Support Center or refer to the Recommended Fixes data base at the following Web site:

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

Hide details for Configuration InstructionsConfiguration Instructions 
Configuration Instructions 

To create a remote output queue, use the Create Output Queue (CRTOUTQ ) command. Specify the following parameters:

Output Queue and Library (OUTQ)
The output queue name can be any name that you choose. It is recommended that the output queue library be set to QUSRSYS in case you need to use a dummy device description for some of your applications. For instructions on creating a dummy device description, refer to the following Rochester Support Center knowledgebase document:

7995114, Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ): Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ)'

Remote System (RMTSYS)
When configuring a RMTOUTQ to another iSeries or AS/400 system, you can either specify the other system’s TCP/IP address, host name or DNS name. If a TCP/IP address is used, the Remote System (RMTSYS) parameter should be set to *INTNETADR and then the other system’s TCP/IP address should be specified in the Internet Address (INTNETADR) parameter which comes later on in the output queue description. If a host name or DNS name is used, that name should be entered in the Remote System (RMTSYS) parameter.

If a TCP/IP address is used, verify that the system can reach the other system by using the PING or Verify TCP/IP Connection (VFYTCPCNN ) command with that TCP/IP address. If a host name or DNS name is used, verify that the system can reach the other system by using the PING or Verify TCP/IP Connection (VFYTCPCNN ) command with that host name or DNS name.

Remote Printer Queue (RMTPRTQ)
This specifies the destination output queue on the other System i system. It is recommended that the fully-qualified output queue name be used and that the output queue be specified in all capital letters. For example, if the RMTOUTQ is to point to PRT01 printer device description on the destination system, specify the device corresponding output queue of the description, ‘QUSRSYS/PRT01’.

Writers to Autostart (AUTOSTRWTR)
Specifies the number of remote writers that are started automatically by the system. It is recommended that this be set to 1, so the remote writer is automatically be started after an IPL, after restarting the QSYS subsystem, or after making a change to the output queue description. If not, the writer must be started manually using the Start Remote Writer (STRRMTWTR ) command.

Connection Type (CNNTYPE)
This must be set to *IP. This indicates that the RMTOUTQ communicates using TCP/IP.

Destination Type (DESTTYPE)
In this case, this must be set to *OS400. This should be set to *OTHERwhen printing spooled files to printers that are attached to the LAN/WAN using a print server, a PC, or a UNIX server, and should be set to *OS400when sending spooled files from one operating system system to another.

Host Print Transform (TRANSFORM)
This is typically set to *NO so the source system will send the operating system spooled file to the other System i system without converting it to an ASCII printer data stream. The spooled file on the destination system will be an exact copy of the spooled file on the source system and, therefore, can usually be routed to any type of printer, including SCS, IPDS, or ASCII printers. This is, of course, dependent on the Printer device type (DEVTYPE) spooled file attribute.

User Data Transform and Library (USRDTATFM)
This is typically set to *NONE when using a RMTOUTQ to send spooled files to another System i system.

Manufacturer Type and Model (MFRTYPMDL)
This is typically set to *NONE when using a RMTOUTQ to send spooled files to another System i system.

Workstation Customizing Object (WSCST)
This is typically set to *NONE when using a RMTOUTQ to send spooled files to another System i system.

Internet Address (INTNETADR)
The Internet Address (INTNETADR) parameter must be set to the IP address for the remote system (OS/400) when the Remote System (RMTSYS) parameter has been set to *INTNETADR. The IP address should be entered without leading zeros (for example, use 192.186.10.2 rather than 192.186.010.002).

Destination options (DESTOPT)
This is typically set to *NONE when using a RMTOUTQ to send spooled files to another System i system.

Print separator page (SEPPAGE)
This is typically set to *NO when using a RMTOUTQ to send spooled files to another System i system.

Hide details for Configuration ExampleConfiguration Example 
Configuration Example 

The following is an example of a Remote Output Queue (RMTOUTQ) to another iSeries or AS/400 system. The “>” indicates important parameters to set. The Remote Output Queue (RMTOUTQ) can be configured using the Create Output Queue (CRTOUTQ ) command. Type CRTOUTQ on an operating system command line, press the F4 (Prompt) Key, fill in the following parameters, and press the Enter Key to create the RMTOUTQ:



Output queue . . . . . . . . . . > SYSTEMB       Name
Library  . . . . . . . . . . . >   QUSRSYS     Name, *CURLIB
Maximum spooled file size:
Number of pages  . . . . . . .   *NONE         Number, *NONE
Starting time  . . . . . . . .                 Time
Ending time  . . . . . . . . .                 Time
+ for more values
Order of files on queue  . . . .   *FIFO         *FIFO, *JOBNBR
Remote system  . . . . . . . . . > *INTNETADR
Remote printer queue . . . . . . > 
Destination OUTQ Name 
Writers to autostart . . . . . .   1             1-10, *NONE
Queue for writer messages  . . .   QSYSOPR       Name
Library  . . . . . . . . . . .     *LIBL       Name, *LIBL, *
Connection type  . . . . . . . . > *IP           *SNA, *IP
Destination type . . . . . . . . > *OS400        *OS400, *OS400
Host print transform . . . . . .  > *NO           *YES, *NO
Manufacturer type and model  . . > *NONE

Workstation customizing object   > *NONE         Name, *NONE         
  Library  . . . . . . . . . . .                 Name, *LIBL, *CURLIB
Internet address . . . . . . . . > 
Destination IP Address 
Destination options  . . . . . . > *NONE
Text 'description' . . . . . . . > 'RMTOUTQ to another iSeries or AS/400'

Hide details for Configuring a Dummy Device Description to Use with a Remote Output QueueConfiguring a Dummy Device Description to Use with a Remote Output Queue 
Configuring a Dummy Device Description to Use with a Remote Output Queue 

Dummy device descriptions are typically used when printing from applications that do not support printing directly to an output queue but only to a printer device description (including Query/400 and the System/36 Environment). They are also useful when moving spooled files from one printer to another from the Work with Output Queue (WRKOUTQ ) or Work with Spooled Files (WRKSPLF ) commands or when using Operations Navigator to drag and drop spooled files from one printer to another.

This information can also be found in the following Rochester Support Center knowledgebase document:

7995114, Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ) Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ)'

Use the following steps to create a dummy device description:

1. Before a dummy device description can be created, the remote output queue (RMTOUTQ) must reside in the QUSRSYS library. If not, creating the dummy device description will cause you to have two output queues of the same name — one in the RMTOUTQ’s current library and one in QUSRSYS. Use the following Work with Objects (WRKOBJ ) command to verify that the RMTOUTQ is in library QUSRSYS:

WRKOBJ OBJ(*ALL/output-queue) OBJTYPE(*OUTQ)

2. To move the RMTOUTQ to library QUSRSYS, first use the End Writer (ENDWTR ) command with the When to end writer (OPTION) parameter set to *IMMED to end the writer immediately:

ENDWTR WTR(output-queue) OPTION(*IMMED) 

Then issue the following Move Object (MOVOBJ ) command:

MOVOBJ OBJ(outq-library/output-queue) OBJTYPE(*OUTQ) TOLIB(QUSRSYS)

3. Use the following Create Device Desc (Printer) (CRTDEVPRT ) command to create a device description with the same name as the RMTOUTQ:

CRTDEVPRT DEVD(output-queue-name) DEVCLS(*VRT) TYPE(3812) MODEL(1) ONLINE(*NO) FONT(011)

4. Creating the dummy device description should result in MSGCPD2602,Device name &1 already exists . This indicates that the printer device description is associated with the Remote Output Queue (RMTOUTQ) that has already been created.

If this message is not received, it most likely means that the RMTOUTQ was not in library QUSRSYS and the Create Device Desc (Printer) (CRTDEVPRT ) command has created a second output queue (but not a RMTOUTQ) with the same name in library QUSRSYS. The problem with this is that applications will typically send spooled files to the output queue in library QUSRSYS, but since this is not a RMTOUTQ, the spooled files will not be sent to the printer.

5. If working in the System/36 Environment, use the Display System/36 Configuration (DSPS36 ) command to check the System/36 printer IDs. The Change System/36 Configuration (CHGS36 ) command can be used to change the System/36 printer IDs or to assign a new System/36 printer ID to point to the new dummy device description.

Note: When you specify a printer in the //PRINTER OCL statement, you are using the System/36 printer ID for that printer. The System/36 Environment then uses a print file in library #LIBRARY that has the same name as the printer ID. If the output is not going to the correct printer, either specify the output queue name on the //PRINTER OCL status or use the Change Printer File (CHGPRTF ) command to point the printer file directly to the remote output queue:

CHGPRTF FILE(#LIBRARY/system-36-printer-id) OUTQ(outq-library/output-queue)

Notes:

o Do not use the Vary Configuration (VRYCFG ) or the Work with Configuration Status (WRKCFGSTS ) commands to vary on the printer device description.
o Do not use the Start Print Writer (STRPRTWTR ) command or Option 1 (Start) from the Work with Writers (WRKWTR ) command to start the writer. Use the Start Remote Writer (STRRMTWTR ) command to start a writer using the Remote Output Queue (RMTOUTQ).
o Remote Output Queues (RMTOUTQs) use remote writers, not printer writers. However, the WRKWTR command defaults to WTR(*PRT) which shows only the active and inactive printer writers. Therefore, using theWRKWTR command without any parameters shows the writer to be in END status, even when the remote writer is started.
o To see if the remote writer is started, use the Work with Writers (WRKWTR ) command with the Writer (WTR) parameter set to *ALL.

For example:

WRKWTR WTR(*ALL) 

This will show all active writers instead of just showing all of the active and inactive printer writers.

Hide details for Changing a Remote Output Queue (RMTOUTQ) DescriptionChanging a Remote Output Queue (RMTOUTQ) Description 
Changing a Remote Output Queue (RMTOUTQ) Description 

Once a Remote Output Queue (RMTOUTQ) has been configured, there is no need to delete and re-create the RMTOUTQ to make any changes. The RMTOUTQ description can be changed by doing the following:

1. Use the End Writer (ENDWTR ) command with the When to end writer (OPTION) parameter set to *IMMED to end the writer immediately.
2. Use the Work with Output Queue Description (WRKOUTQD ) command to display the current settings for the RMTOUTQ.
3. Verify that the status shows that a writer is not active to this output queue.
4. Press the F13 (Change) Key to run the Change Output Queue (CHGOUTQ ) command.
5. Make the desired changes to the RMTOUTQ description, and press the Enter Key.
6. If needed, use the Start Remote Writer (STRRMTWTR ) command to restart the writer.

Hide details for ReferencesReferences 
References 

Refer to the following Rochester Support Center knowledgebase documents:

8983237, Configuring a Remote Output Queue (RMTOUTQ): Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document '   Configuring a Remote Output Queue (RMTOUTQ)'
24291009, Configuring a Remote Output Queue (RMTOUTQ) to a Thermal Label Printer : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Configuring a Remote Output Queue (RMTOUTQ) to a Thermal Label Printer'
8233537, Recommended Remote Printer Queue Values for Remote Output Queues (RMTOUTQs) : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Recommended Remote Printer Queue Values for Remote Output Queues (RMTOUTQs)'
7995114, Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ) : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ)'
14143423, Capabilities and Limitations of Remote Output Queues (RMTOUTQs): Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Capabilities and Limitations of TCP/IP Remote Output Queues'
16483900, Forcing a Remote Output Queue (RMTOUTQ) to Select a Particular Paper Size : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software\Knowledge Base Documents', Document '   Forcing a Remote Output Queue (RMTOUTQ) to Select a Particular Paper Size'
17690939, Information on Printers from Various Manufacturers : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software\Knowledge Base Documents', Document 'Support for Various ASCII Printers'
11944305, Version 5 Printer Model Settings for Host Print Transform (HPT) : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Version 5 Printer Model Settings for Host Print Transform (HPT)'
11401901, Using Host Print Transform (HPT) with a Remote Output Queue (RMTOUTQ) : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'Using Host Print Transform (HPT) with a Remote Output Queue (RMTOUTQ)'
23383453, V5Rx PTF Listing for TCP/IP and LAN Printing : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software\Knowledge Base Documents', Document 'V5Rx PTF Listing for TCP/IP and LAN Printing'
12594243, TSPRWPR Remote Writer Page Range Support Exit Program : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software', Document 'TSPRWPR Remote Writer Page Range Support Exit Program'
18762910, Configuring a *LAN 3812 Device Description that Uses the LPR Print Driver (TSPLPRD) Exit Program : Database 'Rochester Support Line KnowledgeBase', View 'All Documents\All Software\Knowledge Base Documents', Document 'Configuring a *LAN 3812 Device Description that Uses the LPR Print Driver (TSPLPRD) Exit Program'

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, 2011, 2012

    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.