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

The print server, sometimes called a LAN adapter or Network Interface (NIC) card (internal or external), has a timeout setting in the hardware configuration. A timeout is the amount of time that the print server waits for data before the print job is canceled. When this timeout expires, the adapter releases the printer so that other print jobs can be started. These other print jobs can be from another protocol, another interface, or another host. This function provides a safety net. If a host fails to send a complete print job, the print server waits for the specified time and then moves on to the next job. If a file is released to print and the timeout expires before a complete spooled file is sent to the printer or the timeout expires between the sending of buffers, the printer writer ends with message TCP342F - Remote host system closed connection unexpectedly, and the spooled file is set to HLD or RDY status.

The timeout can be configured from the printer panel or through a network utility (for example, the HP JetAdmin utility for internal and external HP JetDirect print servers and the Lexmark MarkVision utility for Lexmark Marknet print servers). For printer panel configuration, the timeout is found under some network option: under the IO and MIO Menus for HP printers, under the Network Menu for Lexmark printers, and under the Ethernet or Token-Ring Menu for IBM printers.

On the printer, the processor timer (sometimes called a job timeout or a wait timeout) should be disabled or set to maximum (usually 300 seconds) because individual pages might have a delay in transmitting to the printer due to transforming considerations. This timer controls the amount of time in seconds (5 to 300) the printer waits before printing the last page that does not end with a command to print the page. This timer should not affect the running of this print driver because each page is terminated with a form feed. We could have a case where a partial page is sent to the printer buffer while complex transforming is taking place during which this timer expires and, therefore, ejects an incomplete page.

IBM Network Printer and Infoprint printers:

Set the Port Timeout to 300 (5 minutes). Setting this timeout to 0 does not disable the Port Timeout. IBM does not have an external adapter that supports this configuration at this time. The port timeout can be set through the control panel on the printer.

Infoprint 1100, 1200, 1300 and 1400 Series Printers:

Disable the Job Timeout by setting it to 0. The Job Timeout can typically be set through the control panel on the printer, or it can be set using the Lexmark MarkVision Utility. The Lexmark MarkVision Utility can be downloaded from the Lexmark Web site, www.lexmark.com/.

HP JetDirect cards/print servers:

Set the IO Timeout (or Job Timeout) to 300 seconds (5 minutes) and set the Idle Timeout to somewhere between 900 seconds (15 minutes) and 3600 seconds (1 hour). Setting the IO Timeout (or Job Timeout) and Idle Timeout to 0 does not disable them. It causes the printer and/or print server to timeout immediately. The IO Timeout can typically be set through the control panel on the printer, or it can be set using the HP JetAdmin Utility. The Idle Timeout can be set by TELNETing to the TCP/IP address for the printer, or it can be set using the HP JetAdmin Utility. The HP JetAdmin Utility can be downloaded from HP's Web site, www.hp.com/.

Lexmark MarkNet cards/print servers:

Disable the End of Job Timeout or Job Timeout by setting it to 0. The End of Job Timeout or Job Timeout can typically be set through the control panel on the printer, or it can be set using the Lexmark MarkVision Utility. The Lexmark MarkVision Utility can be downloaded from the Lexmark Web site, www.lexmark.com/.

The printer will close the socket if the printer has not processed any communication from the host within the timeout limit for the LAN adapter, which is discussed in the section entitled Timeout Settings on the Print Server. This can happen if the printer has a large buffer and it is filled with data to print. To prevent this from happening, the TCP/IP Keep-Alive value on the system should be set to a value less than the timeout value for the print server. The TCP/IP Keep-Alive value can be changed using the Change TCP/IP Attributes (CHGTCPA) command. This causes a poll to be sent to the printer before the printer times out. We want this timeout value to be as large as possible to prevent unnecessary network traffic. Increasing the TCP keep alive (TCPKEEPALV) parameter to 50 minutes can help if printing large spooled files.

CPD0020 "Character '<Number>' not valid following string '''        '."
Followed by:  
CPD0014  "A matching apostrophe not found."
CPD0013  "A matching parenthesis not found."
CPF0001  "Error found on *N command."
CPF0006  "Errors occurred in command."
The writer ends abnormally with CPF3473 "Writer did not end normally."

In addition to the job log for the writer, a QPRINT spooled file is generated that contains dump information of the SNDTCPSPLF command that contains the configuration settings for the remote output queue.

o	There is a single quote (apostrophe) preceding the internet address in the remote output queue configuration. Remove the single quote from the INTNETADR parameter.  Refer to instruction set (2) Determining and Changing a Remote Output Queue Description

TCP100D "No ports available to establish a session"

o	Message TCP100D indicates that there are no source ports available for the Remote Output Queue to use to open a new connection. Remote Output Queues and Line Printer Requester (LPR) in general are limited to using source ports 256 through 1024 (for a total of 768 ports). Other TCP protocols also use source ports in this same range, so not all 768 are available only to LPR connections. One way to increase the number of ports that can be used by LPR is by adding the XSRCPORT keyword to the Destination Options (DESTOPT) parameter of the remote output queue description.  Refer to the following document for more details: Can the Source Ports Used by LPR (Remote Output Queues) be Changed?  For example, to change an existing remote output queue to use a source port between 899 and 5000, issue the following command after ending the writer: CHGOUTQ OUTQ(LibraryName/OutputQueueName) DESTOPT('XSRCPORT(00899 05000)') It will also help to use the Change TCP/IP Attributes (CHGTCPA) command and decrease the value of the TCP time-wait timeout (TCPCLOTIMO) parameter. This parameter indicates the amount of time, in seconds, for which a socket pair (client TCP/IP address and port, server TCP/IP address and port) cannot be reused after a connection is closed. Decreasing this value will free up socket pairs sooner, which should help when opening new TCP sessions.  For example: CHGTCPA TCPCLOTIMO(15) Development has confirmed that the default value of 120 seconds for the TCPCLOTIMO parameter was necessary in the beginning days to allow connections enough time to close successfully.  Two minutes is no longer needed. If decreasing the value of the TCP time-wait timeout (TCPCLOTIMO) parameter does not completely resolve the problem, then consider adding additional network connections or interfaces to the IBM Power Systems by installing additional network interface cards (NICs) and communications lines. This will allow for a larger number of socket pairs, because each side of a socket pair includes a TCP/IP address and port number. A Remote Output Queue will be less likely to fail with message TCP100D because a connection can be opened on another TCP/IP address if needed. Note: This problem can be circumvented by periodically using the Work with TCP/IP Network Status (NETSTAT) command, taking Option 3 (Work with TCP/IP connection status), and using Option 4 (End) to end any LPR connections that are in time-wait status.
o	This issue has also been seen with a remote output queue with a started writer that is configured to have a 'place holder' IP address, such as XXX.XXX.XXX.XXX and the address resolves to a valid IP address. The LPR application is calling getaddrinfo() on the Internet Address (INTNETADR) field, which is specifying XXX.XXX.XXX.XXX to return an IP address.  Attempts to print through such a configuration continues using up ports until all available ports between 256-1024 are used.  NETSTAT shows the ports in closed status even though the TCPCLOTIMO is set to 0. The resolution is end the writer, specify a correct IP address for the remote output queue, or prevent the remote writer from starting until a valid IP address can be specified for the remote output queue description.
o	This issue has been seen with two remote output queues configured to send to one another on the same system.  Essentially, the two output queues were sending the spooled files back and forth causing all available ports to be used.  To identify this type of a situation: 1.  NETSTAT and press <ENTER> 2.  Select option 3. Work with IPv4 connection status and press <ENTER> 3.  Press F13=Sort by column and select Remote Address and press <ENTER> 4.  Page down until you find 127.0.0.1 under the Remote Address column 5.  Select option 8=Display jobs to determine the name of the writer.  May need to look at a few to determine the name of the other writer or continue with the steps below. 6.  Use WRKOUTQD OUTQ(OutputQueueName) to check the Remote Printer Queue (RMTPRTQ).  This is the target output queue name and library. 7.  Use WRKOUTQD OUTQ(TargetOutputQueueName) to check the RMTPRTQ value to confirm the target output queue is configured to send back to the source output queue. To resolve the issue: Determine which output queue should remain the source output queue, then change the target output queue to not be a remote writer: 1.  ENDWTR WTR(WriterName) and press <ENTER> 2.  CHGOUTQ OUTQ(LibraryName/TargetOutputQueueName) RMTSYS(*NONE) AUTOSTRWTR(*NONE) and press <ENTER>

o

This can occur if the Remote Output Queue (RMTOUTQ) is configured to use a page range exit program, such as the Remote Writer Page Range (TSPRWPR) utility, and the spooled file is generated with the Printer device type (DEVTYPE) parameter set to *IPDS. Host Print Transform (HPT) does not support printing *IPDS spooled files, so this issue can only be resolved by generating an *SCS or *AFPDS spooled file, which can be done by either changing the application or by changing the printer file, or by printing the *IPDS spooled file through a *LAN IPDS printer device description to an IPDS-capable printer.

o

This can occur if the Remote Output Queue (RMTOUTQ) is configured to use a page range exit program, such as the Remote Writer Page Range (TSPRWPR) utility, and the spooled file owner's user profile does not have the Maximum allowed storage (MAXSTG) parameter set high enough to provide sufficient storage to process the spooled file. In this case, the writer job log would contain the following error messages: TCP371B: Transform exit program will not process file. CPD339B: An error occurred while transforming data. CPF6DF9: Transformed data buffer too small. This issue can be resolved by increasing the Maximum allowed storage (MAXSTG) parameter for the spooled file owner's user profile, or by setting it to *NOMAX.

TCP2617 "TCP/IP connection to remote system &2 closed, reason code &5"

o	The TCP/IP connection to the remote system, printer, or print server has closed. Refer to the following Rochester Support Center knowledgebase document for more information: N1016564: Message TCP2617

TCP3206 "No response from host within &1 seconds for connection verification &2"

o	Issued after a PING attempt.
o	Printer is powered off.

TCP3213 "Cannot reach remote system"

o	No active route to the remote system, printer or print server. Follow Instruction Set (21) Determining if there is an Active TCP/IP Route.

TCP3405 "Not able to send the specified data"

o	The *SPOOL pool is set too low. Follow Instruction Set (1) Determining and Changing the Size of the *SPOOL Pool.
o	Incorrect value for the Remote printer queue (RMTPRTQ) parameter. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	The destination type (DESTTYPE) parameter is *OS400 rather than *OTHER. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	LPD services are not running on remote system or adapter. Follow Instruction Set (10) Determining if the Line Printer Daemon (LPD) Job is Running.
o	Verify LAN adapter settings.
o	If the target system is another IBM System i server, does the failing spooled file have the Output priority (OUTPTY) parameter set higher than the Highest schedule priority (PTYLMT) parameter in the QTMPLPD user profile on the receiving system? Follow Instruction Set (22) Determining the QTLPDxxxxx Job and Verifying the Output priority (OUTPTY) Parameter for the Spooled File in SND Status.

TCP3409 "Not able to establish connection with remote host system"

o	The *SPOOL pool is set too low. Follow Instruction Set (1) Determining and Changing the Size of the *SPOOL Pool.
o	Incorrect TCP/IP address (possible leading zeros in TCP/IP address). Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.

TCP342F "Remote host system closed connection unexpectedly"

o	SA56774 OEM printer microcode problem.
o	The *SPOOL pool is set too low. Follow Instruction Set (1) Determining and Changing the Size of the *SPOOL Pool.
o	Incorrect value for the Remote printer queue (RMTPRTQ) parameter. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	TCP/IP interface is defined for the printer. Follow Instruction set (3) Determining if there is a TCP/IP Interface.
o	The Destination type (DESTTYPE) parameter is *OS400 rather than *OTHER when sending to a printer or a system other than a Power System server. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	Host Name Search Priority is set to *REMOTE. Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used.
o	Network function named intrusion prevention system (IPS) may be identifying print packets as malicious and blocking the connection. A connection trace shows the connection opening to the printer, but no response from the printer thereafter.
o	Printer is rejecting large Maximum Transmission Unit (MTU) frames. Take a communication trace to prove. Follow Instruction Set (5) Collecting a TCP/IP Communications Trace and Instruction Set (6) Decreasing the Maximum Transmission Unit (MTU) Size on a Host Route or a TCP/IP Interface.
o	Local host name and domain name are in lowercase, but the host table entry for the system is in uppercase. Follow Instruction Set (13) Determining and Changing a Host Table Entry and Instruction Set (14) Determining and Changing Domain and Host Information.
o	The LPD Server is ending unexpectedly on the receiving system when sending to a Power System server. Follow Instruction Set (10) Determining if the Line Printer Daemon (LPD) Job is Running.
o	Receiving a FIN ACK response from the printer or print server after sending an incorrect value for the Remote printer queue (RMTPRTQ) parameter. Follow Instruction Set (5) Collecting a TCP/IP Communications Trace and Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	Duplicate TCP/IP address. Follow Instruction Set (9) Determining if there is a Duplicate TCP/IP Address and Instruction Set (8) PING the Printer or Remote System by IP Address.
o	The printer is timing out. Refer to the sections Timeout Settings on the Printer and Recommended Timeout Settings for IBM, HP and Lexmark Print Servers for information about the recommended timeout settings.
o	If a Domain Name Server (DNS) is being used, ensure the TCP/IP address of the system is added to the DNS.

TCP3423 "No TCP/IP service available"

o	TCP/IP is not started. Follow Instruction Set (7) Determining if TCP/IP is Started.

TCP3427 "Remote host system rejected the open attempt"

o	Incorrect Remote printer queue (RMTPRTQ) parameter value. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	Not able to PING printer. Follow Instruction Set (8) PING the Printer or Remote System by IP Address.
o	Duplicate TCP/IP address. Follow Instruction Set (9) Determining if there is a Duplicate TCP/IP Address and Instruction Set (8) PING the Printer or Remote System by IP Address.
o	An existing printer might have been replaced with a new printer that has been assigned the same TCP/IP address, and connectivity might not occur because of an old ARP cache entry that references the MAC address of the old printer that has been replaced. Follow Instruction Set (24) Clearing a Specific ARP Cache Entry.
o	TCP/IP interface is defined for printer. Follow Instruction set (3) Determining if there is a TCP/IP Interface.
o	LPD services are not running on the remote system. Follow Instruction Set (10) Determining if the Line Printer Daemon (LPD) Job is Running. Note: If the remote system is a PC or a Microsoft® Windows NT® server, an LPD program (such as TCP/IP Printing Service) must be running on the PC.
o	If the target system is another Power System server, QTMPLPD user profile is disabled or the password has expired. Follow Instruction Set (11) Verifying and Changing the QTMPLPD User Profile.
o	The LAN adapter is a multi-port adapter and the port that the printer is attached to is disabled. (Examine the hardware configuration and documentation or contact the manufacturer.)
o	If a firewall or SOCKS server is set up or TCP/IP traffic is going through a router then the ports used for LPR/LPD may be blocked, particularly if trying to print across a Wide Area Network (WAN). Remote Output Queues (RMTOUTQs) use destination port 515, but can use a source ports of 256 through 1024. Port 515 is considered a well-known TCP/IP port and is not usually blocked outbound, but this should be verified by the network administrator to be certain. It should also be verified that ports 256 through 1024 are not blocked inbound. For more information, refer to the following Software Knowledge Base document: N1017003: TCP/IP Ports Used by Line Printer Requester (LPR) in OS/400 or i5/OS
o	Port scanning utilities have been known to cause issues with Zebra printers when the utility scans port 515.  To identify this as the issue, a network trace of all activity at the printer level is required.  An IBM i connection trace will not show the issue.  Remove all printer IP addresses from the port scanning utility.  Contact the utilities application team if needed.
o	It is possible message TCP3427 could be issued for Zebra printers if the CONNECTION TIMEOUT CHECKING hardware setting is set on.  Using the web interface, change this setting from on to off:   Using a browser, enter the printer's IP address   From the HOME screen, select PRINT SERVER SETTINGS / STATUS AND CONFIGURATION / PRINT SERVER   Log in (default user ID is ADMIN and default password is 1234)   Select TCP/IP CONFIGURATION and locate the CONNECTION TIMEOUT CHECKING   Change from ON to OFF and SUBMIT the changes   Restart the printer, but may need to physically power off/on the printer also

TCP3436 "No response from remote host system within open time-out"

o	Incorrect TCP/IP address specified in the Internet address (INTNETADR) parameter of output queue description. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description and Instruction Set (8) PING the Printer or Remote System by IP Address.
o	TCP/IP address is specified with leading zeroes in the Internet address (INTNETADR) parameter of output queue description, for example, specifying '192.168.002.051' rather than '192.168.2.51'. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description and Instruction Set (8) PING the Printer or Remote System by IP Address.
o	The Remote system (RMTSYS) parameter is specified with a host name, but there are two or more host table entries with that name which point to different TCP/IP addresses. This can be tested by first pinging the TCP/IP address of the printer and then pinging the host name (both from an operating system command line) to determine if they are both successful and if the host name points to the correct TCP/IP address. Follow Instruction Set (13) Determining and Changing a Host Table Entry and Instruction Set (14) Determining and Changing Domain and Host Information.
o	If a firewall or SOCKS server is set up or TCP/IP traffic is going through a router then the ports used for LPR/LPD may be blocked, particularly if trying to print across a Wide Area Network (WAN). Remote Output Queues (RMTOUTQs) use destination port 515, but can use a source ports of 256 through 1024. Port 515 is considered a well-known TCP/IP port and is not usually blocked outbound, but this should be verified by the network administrator to be certain. It should also be verified that ports 256 through 1024 are not blocked inbound. For more information, refer to the following Software Knowledge Base document: N1017003: TCP/IP Ports Used by Line Printer Requester (LPR) in OS/400 or i5/OS
o	The IBM System i may have the wrong MAC address listed for the printer or print server in its ARP cache, or a router on the Local Area Network (LAN) or Wide Area Network (WAN) may have the wrong MAC address listed for the printer or printer server as well, particularly if the printer or print server hardware were recently replaced or serviced. To diagnose this further, run the Verify TCP/IP Connection (VFYTCPCNN or PING) command to see if you can successfully ping the printer IP address from the IBM System i. If not, try pinging the gateway address for the printer (such as '192.168.2.1') from the IBM System i as well. If that is successful, and particularly if a PC is able to successfully ping the printer IP address, then do an "ENDWTR WTR(writer-name) OPTION(*IMMED)" to end the remote writer immediately, leave the writer ended for at least 20 or 30 minutes, and try the VFYTCPCNN or PING command from the IBM System i again. Once you are able to successfully ping the printer again from the IBM System i, then it should be okay to restart the writer to see if you are then able to print. Note: Part of the problem we are addressing here is that the remote writer keeps trying to open a connection to the printer IP address. If the IBM System i or a router on the LAN/WAN has the wrong MAC address for that IP address then the remote writer is not giving it a chance to clear its cache on its own, so it keeps trying to use the wrong MAC address. If this is the case, then ending the remote writer and leaving it ended will typically allow the IBM System i or the router to clear its cache on its own.
o	If a router is overworked, it might discard frames (or packets) when the buffer is full rather than rejecting the frames. If rejected, then an attempt will be made to resend the frames; however, if discarded, then it could result in message TCP3436. Upgrading the router firmware might help to resolve this issue; otherwise, the network hardware might need to be replaced or the network topography might need to be changed to provide better throughput.
o	A switch may be misidentifying print packets from IBM i as an attack and shut down the port.  Or in an SD-WAN environment, 'packet inspection' is flagging the print data and not forwarding it to the printer. Turn the feature off on the switch or SD-WAN.  Refer to the documentation or contact the manufacturer for the switch or SD-WAN for instructions or for more information on the feature.
o	If message TCP3436 is issued only when printing spooled files that contain image data such as an overlay, page segment or AFP resource, it may be a firewall firmware update to address https://snort.org/rule_docs/1-9790.  A work around is to whitelist the rule to turn it off.  If further information is needed, contact the firewall manufacturer.
o	The switch might be bad.
o	The writer is using the wrong Ethernet line (interface). Use NETSTAT to determine which interface the connection is using.  IBM support cannot determine if this is the right interface to use or not.  In this scenario, the client used NETSTAT option 3 to determine only the remote writers were using the interface and then ended the interface.  This forced the writers to then use the correct active interface and all writers started working again.

TCP3600 "Spooled file &1 sent" but the spooled file shows up on the QPRINT output queue on the source system rather than printing

o	TCP/IP interface is defined for the system or printer (the TCP/IP address in output queue description). Follow Instruction set (3) Determining if there is a TCP/IP Interface.
o	The Destination type (DESTTYPE) parameter is *OS400 rather than *OTHER. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	The Remote system (RMTSYS) parameter is specified with a host name, but there is not a host table entry for the address. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description and Instruction Set (13) Determining and Changing a Host Table Entry.
o	No host table entry for the Power Systems server. Follow Instruction Set (13) Determining and Changing a Host Table Entry and Instruction Set (14) Determining and Changing Domain and Host Information.

TCP3600 "Spooled file &1 sent" but the spooled file shows up on the QPRINT output queue on the target system

o	The Remote printer queue (RMTPRTQ) parameter specifies an output queue that does not exist on the target system, so the spooled file is sent to the QPRINT output queue in library QUSRSYS instead. Create the output queue on the target system, or change the RMTPRTQ parameter on the RMTOUTQ to point to an output queue that exists on the target system.
o	The Remote printer queue (RMTPRTQ) parameter specifies an output queue that exists on the target system, but not the library name is not specified and the output queue is not in a library that is in the system library list, so the spooled file is sent to the QPRINT output queue in library QUSRSYS instead. Change the RMTPRTQ parameter on the RMTOUTQ to library-qualify the output queue name.
o	The Remote printer queue (RMTPRTQ) parameter specifies an output queue that exists on the target system, but the user profile associated with the spooled file is not authorized to the output queue or is not authorized to the library, so the spooled file is sent to the QPRINT output queue in library QUSRSYS instead. Authorize the user profile to output queue and library on the target system. This can result in message CPF4244 "Not authorized to output queue &6 in &7" being issued to the LPD daemon jobs on the receiving system.

TCP3600 "Spooled file &1 sent" but the spooled file does not print

o	This indicates the remote writer has received confirmation from the printer that the spooled file was received. This indicates a hardware problem with the printer or with the network adapter. To verify, run a communications trace. Follow Instruction Set (5) Collecting a TCP/IP Communications Trace.

TCP3602 "Spooled file &1 received from remote user &2"

o	TCP/IP interface defined for the printer. Follow Instruction set (3) Determining if there is a TCP/IP Interface.
o	The Remote Output Queue is configured with the Remote system (RMTSYS) parameter set to the host name of the sending system or to LOOPBACK or LOCALHOST. It could also be set to *INTNETADR with the Internet address (INTNETADR) parameter set to the TCP/IP address of the sending system.

TCP3701 "Send request failed for spooled file &1"

This message is normally preceded by another TCPxxxx message. Refer to the preceding message in the writer job log for further problem determination.

o	Incorrect value for the Remote printer queue (RMTPRTQ) parameter, such as a wrong value, misspelled, or in the wrong case (uppercase or lowercase). Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	The Internet address (INTNETADR) parameter could be specified with leading zeros in the TCP/IP address. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	The Internet address (INTNETADR) parameter could be specified with an asterisk ( * ) at the beginning of the TCP/IP address, for example INTNETADR('*'192.168.2.51 '). Remove the asterisk. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description. Note: The Asterisk (*) character is used at the beginning of special values, such as the setting of *INTNETADR for the Remote system (RMTSYS) parameter or the settings of *IP and *SNA for the Connection type (CNNTYPE) parameter. It is not generally used for specific values such as specifying the TCP/IP address in the INTNETADR parameter.
o	The Internet address (INTNETADR) parameter could be specified with a host name rather than a TCP/IP address, for example, RMTSYS(*INTNETADR) and INTNETADR(IBMIP1140). Either set the INTNETADR parameter to the TCP/IP address for the printer, or set the Remote system (RMTSYS) parameter to the host name for the printer. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.

TCP370A "Cannot resolve host name &1"

o	The Remote system (RMTSYS) parameter is specified with a host name, but there is not a host table entry for the address. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description and Instruction Set (13) Determining and Changing a Host Table Entry.
o	The Remote system (RMTSYS) parameter is specified as the TCP/IP address rather than *INTNETADR or a valid host name. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description. Note: V6R1M0 (R610) i5/OS and R610 PTF SI31363 (8365) added support to allow the Remote system (RMTSYS) parameter to specify an IPv4 or IPv6 address, in addition to specifying a host name or DNS name. Prior to this, the RMTSYS parameter would need to be set to *INTNETADR and the IP address would need to be specified in the Internet address (INTNETADR) parameter. For more information, please refer to APAR SE33021 OSP-TCP ADD IPV6 ADDRESS SUPPORT TO LPR.
o	Host Name Search Priority is set to *REMOTE. Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used.

TCP370D "SNDTCPSPLF cannot verify local host name &1"

o	Local host name and domain name are in lowercase, but the host table entry for the system is in uppercase. Follow Instruction Set (13) Determining and Changing a Host Table Entry and Instruction Set (14) Determining and Changing Domain and Host Information.
o	The Remote system (RMTSYS) parameter is specified with a host name, but there is not a host table entry for the address. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description and Instruction Set (13) Determining and Changing a Host Table Entry.
o	The Domain Name Server (DNS) is down. Can the DNS address be PINGed? Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used and Instruction Set (8) PING the Printer or Remote System by IP Address.

TCP371A "Send request failed for spooled file &1"

o	Storage limit exceeded for user profile. Follow Instruction Set (12) Verifying and Changing a User Profile other than QTMPLPD.
o	If a spooled file contains a Form Feed control (X'0C') in the datastream, rather than using the typical method of positioning to the first line on the next page, the spooled file page counter will not show the correct page count. This can cause the partial page buffer to overflow, which will result in message TCP371A.

TCP3719 "Send request failed for spooled file &1"

o	The Remote printer queue (RMTPRTQ) parameter value incorrect. Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
o	Problem with the Domain Name Server (DNS). Is the DNS address correct and can it be PINGed? Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used and Instruction Set (8) PING the Printer or Remote System by IP Address.

TCP9880 "Value for local domain name not valid"

o	Missing local host and domain name in TCP/IP configuration. Follow Instruction Set (14) Determining and Changing Domain and Host Information.

CPD2609 "Device &25 configuration not valid. Reason code 2301" (RC2301)

o

A printer device description has been configured with the same name as the Remote Output Queue (RMTOUTQ) and an attempt was made to vary on the printer device description, or what is commonly referred to as a "dummy device description". When using a RMTOUTQ, there is no requirement to have a printer device description or dummy device description of the same name, though some applications may need to have the device description configured. However, if a dummy device description has been configured, there is definitely no need to vary on the printer device description. Furthermore, if the dummy device description has been configured with the Attached controller (CTL) parameter left blank, then attempting to vary on the printer device description will result in message CPD2609 RC2301. For more information on configuring a dummy device description, refer to one of the following Rochester Support Center knowledgebase documents: N1010090: Configuring a Remote Output Queue (RMTOUTQ) N1019443: Configuring a Remote Output Queue (RMTOUTQ) to a Label or Receipt Printer N1018931: Configuring a Remote Output Queue (RMTOUTQ) to a Windows Print Queue N1010256: Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ)

CPD337F "Remote device rejected an attempt by the writer to open a connection"

o	A remote output queue is not being used. A LAN printer device is being used.

CPD334A "Later version of TCP/IP LPP must be installed"

The remote writer ends immediately after being started and the writer job log shows that the writer ended with messages CPD334A "Later version of TCP/IP LPP must be installed" and CPF3473 "Writer &3/&2/&1 did not end normally".

o

Product 5722TC1 or 5761TC1 (IBM TCP/IP Connectivity Utilities for i5/OS) is not installed. Although this is unlikely, you should do a GO LICPGM Option 10 (Display installed licensed programs) to verify that product 57xxTC1 is in *COMPATIBLE status and that the installed release matches the i5/OS release on the IBM System i. If not installed, then do a GO LICPGM Option 11 (Install licensed programs) to install this product using the customer's install media

o

The Send TCP/IP Spooled File (SNDTCPSPLF) command does not exist in library QSYS. Run the following Work with Objects (WRKOBJ) command: WRKOBJ OBJ(*ALL/SNDTCPSPLF) OBJTYPE(*CMD) and check to see if the SNDTCPSPLF *CMD object is found in library QSYS. If not, then take Option 3 (Copy) on the SNDTCPSPLF *CMD object in library QTCP and press the Enter key, set the To library (TOLIB) parameter to "QSYS" and press the Enter key again. Press the F5 (Refresh) key and verify that the SNDTCPSPLF *CMD command is now in the QSYS library. Use the Start Remote Writer (STRRMTWTR) command to restart the remote writer, then use the Work with Output Queue (WRKOUTQ) command or do a "WRKWTR WTR(*ALL)" to verify that the remote writer has started successfully, and then test to make sure that the Remote Output Queue (RMTOUTQ) is able to print successfully.

CPF22E3 "User profile &1 is disabled"

o	User profile is disabled. If the user profile mentioned is QTMPLPD then follow Instruction Set (11) Verifying and Changing the QTMPLPD User Profile, otherwise follow Instruction Set (12) Verifying and Changing a User Profile other than QTMPLPD.

CPF22E7 "ProfileHandle is not valid"

When receiving a spooled files from another IBM i, the LPD Daemon jobs (QTLPDxxxxx) will switch from the QTMPLPD user profile to the user profile that owns the spooled file on the original system so that user profile will own the spooled file on the receiving system.

o	When CPF22E7 is preceded by CPF4AB8 "Insufficient authority for user profile &1" it indicates that either the user profile does not have *OBJOPER to its own *USRPRF object, or the user profile does not have *READ to one of the group profiles specified in the *USRPRF object.
o	If CPF22E7 is not preceded by any other pertinent messages, verify that the user profile that owns the spooled file on the sending iSeries system exists on the receiving system and that it is enabled.

CPF3330 "Necessary resource not available"

o	Another writer has a lock on QTMPLPRSEQ or QTMPLPRxxx data area in QTCP library. Follow Instruction Set (15) Determining and Releasing a Lock on the QTMPLPRxxx or QTMPLPRSEQ Data Area.
o	Refer to the following Rochester Support Center knowledgebase document for step-by-step instructions on putting the remote writer into DEBUG mode: N1018446: Activating Debug Mode for Remote Output Queues (RMTOUTQs) and SNDTCPSPLF

CPF3473 "Writer &3/&2/&1 did not end normally"

o	TCP/IP product not installed. Follow Instruction Set (16) Determining if TCP/IP is Installed.
o	Storage limit exceeded for user profile. Follow Instruction Set (11) Verifying and Changing the QTMPLPD User Profile and Instruction Set (12) Verifying and Changing a User Profile other than QTMPLPD for the user profile that was used to generate the spooled file.

CPF3C1E "Required parameter &1 omitted"

o	Storage limit exceeded for user profile. Follow Instruction Set (11) Verifying and Changing the QTMPLPD User Profile and Instruction Set (12) Verifying and Changing a User Profile other than QTMPLPD for the user profile that was used to generate the spooled file.

CPF9838 "User profile storage limit exceeded"

o	Storage limit exceeded for user profile. Follow Instruction Set (11) Verifying and Changing the QTMPLPD User Profile and Instruction Set (12) Verifying and Changing a User Profile other than QTMPLPD for the user profile that was used to generate the spooled file.

CPF4355 "OUTPTY value &6 exceeds priority limit for user QTMPLPD"

o

The Output priority (OUTPTY) parameter for the spooled file on the sending system exceeds the Highest schedule priority (PTYLMT) parameter for the QTMPLPD user profile on the receiving system. Follow Instruction Set (22) Determining the QTLPDxxxxx Job and Verifying the Output priority (OUTPTY) Parameter for the Spooled File in SND Status.

The majority of the time, there will be a message in the writer job log or message queue that will lead to a resolution for the problem. There are few cases where messages are not logged. For information on how to find messages in the writer job log or writer message queue, refer to one of the following Rochester Support Center knowledgebase documents:

N1010059: Finding the Job Log of a Printer Writer or Remote Writer
N1019671: Finding a Writer Job Log
N1018048: Identifying the Message Queue That a Writer is Using, Finding the Writer Job Log and Increasing the Message Logging Level for a Writer Job

Symptom: Spooled File in SND Status but Spooled File Prints on the Printer (or Arrives on the Target System)

1	This can be an indication that the data file was received and processed by the printer, but the control file has not been received or processed. This could be due to a connection or timeout problem, or the printer/print server may not be responding correctly to the Line Printer Requester (LPR) data sent by the remote writer.
2	Collect a TCP/IP communications trace to see exactly what is going on between the iSeries system and the printer/print server. N1019135: Running a TRCCNN Trace for LAN Printing Problems
3	If there is a problem where the printer/print server is not responding correctly to the Line Printer Requester (LPR) data sent by the remote writer then downloading and installing the latest printer and print server firmware from the printer manufacturer may resolve the problem. Otherwise the customer should pursue the matter with the printer manufacturer.
4	Another option would be to try switching from using a Remote Output Queue (RMTOUTQ) to using a *LAN 3812 printer device description instead. For more information, refer to the section titled "Switching to Use a *LAN 3812 Printer Device Description" below.

Symptom: Spooled File in SND Status but Spooled File Prints Over and Over Again on the Printer

1	This can be an indication that the data file was received and processed by the printer, but the control file has not been received or processed. This could be due to a connection or timeout problem, or the printer/print server may not be responding correctly to the Line Printer Requester (LPR) data sent by the remote writer.
2	Collect a TCP/IP communications trace to see exactly what is going on between the iSeries system and the printer/print server. N1019135: Running a TRCCNN Trace for LAN Printing Problems
3	If there is a problem where the printer/print server is not responding correctly to the Line Printer Requester (LPR) data sent by the remote writer then downloading and installing the latest printer and print server firmware from the printer manufacturer may resolve the problem. Otherwise the customer should pursue the matter with the printer manufacturer.
4	Another option would be to try switching from using a Remote Output Queue (RMTOUTQ) to using a *LAN 3812 printer device description instead. For more information, refer to the section titled "Switching to Use a *LAN 3812 Printer Device Description" below.

Symptom: Spooled File Stays in SND Status for Several Minutes before Spooled File Prints on the Printer (or Arrives on the Target System)

1	This can be an indication that the data file was received and processed by the printer, but the control file has not been received or processed, or that the printer is waiting for an indication that the end of the print data has been sent. The printer or print server eventually times out and prints all of the print data that it has received so far. This could be due to a connection or timeout problem, or the printer/print server may not be responding correctly to the Line Printer Requester (LPR) data sent by the remote writer.
2	Collect a TCP/IP communications trace to see exactly what is going on between the iSeries system and the printer/print server. N1019135: Running a TRCCNN Trace for LAN Printing Problems
3	If there is a problem where the printer/print server is not responding correctly to the Line Printer Requester (LPR) data sent by the remote writer then downloading and installing the latest printer and print server firmware from the printer manufacturer may resolve the problem. Otherwise the customer should pursue the matter with the printer manufacturer.
4	Another option would be to try switching from using a Remote Output Queue (RMTOUTQ) to using a *LAN 3812 printer device description instead. For more information, refer to the section titled "Switching to Use a *LAN 3812 Printer Device Description" below.

Symptom: Spooled File in SND Status and Spooled File does not Print on the Printer

1	Is the printer powered on and cabled to the network?
2	Is the printer in use by another system on the network? (Either it is busy or the other system has not released the printer as of yet.)
3	Is the TCP/IP address correct? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
4	Can the TCP/IP address be PINGed? Follow Instruction Set (8) PING the Printer or Remote System by IP Address.
5	Is it a duplicate TCP/IP address? Follow Instruction Set (9) Determining if there is a Duplicate TCP/IP Address.
6	Has an existing printer been replaced with a new printer that has been assigned the same TCP/IP address? If so, connectivity might not occur because of an old ARP cache entry that references the MAC address of the old printer that has been replaced. Follow Instruction Set (24) Clearing a Specific ARP Cache Entry.
7	Is the TCP/IP address specified in the Internet address (INTNETADR) parameter in the output queue description? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
8	Is a host name specified for the Remote system (RMTSYS) parameter? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description. Is there a host table entry for it? Follow Instruction Set (13) Determining and Changing a Host Table Entry.
9	Can the host name be PINGed? (PING HostName) Follow Instruction Set (8) PING the Printer or Remote System by IP Address.
10	Is the correct Remote printer queue (RMTPRTQ) parameter specified? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
11	Is the Remote printer queue (RMTPRTQ) parameter in uppercase when it should be in lowercase? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
12	Is it a large spooled file? (Large can be 20 pages on one system and 100 on another.)
13	Is LPD services running/enabled on the printer or network interface card (NIC)? Check the printer web access by keying the printer/NIC IP address in a web browser and check the network settings. Discuss with the LAN administrator, verify the LAN adapter configuration, reboot the PC and/or reset the printer/LAN adapter and try again.
14	Is the Destination type (DESTTYPE) parameter correct? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description. Note: Use *OS400 for sending to another IBM i server, and use *OTHER for printers/NICs and for most other servers.
15	Is the Host Name Search Priority set to *REMOTE? Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used.
16	Is the printer and LAN adapter microcode up to date? (Contact the manufacturer.)
17	Is the *SPOOL pool set too low? Follow Instruction Set (1) Determining and Changing the Size of the *SPOOL Pool.
18	Is the printer in power saver mode?
19	Are there any errors on the printer hardware?
20	Can a spooled file be printed successfully using the Send TCP/IP Spooled File (SNDTCPSPLF or LPR) command? Follow Instruction Set (17) SNDTCPSPLF (LPR Command)
21	Is the Line Printer Daemon (LPD) running on the source system? Follow Instruction Set (10) Determining if the Line Printer Daemon (LPD) Job is Running. Note: For the function of XAUTOQ queue to work, LPD must be running on the source system.
22	End the writer, check the spooled files in the output queue, cycle the printer or server, and restart the writer. Follow Instruction Set (18) Ending, Restarting, and Resetting the Writer.
23	Delete and re-create the output queue. For instructions on creating a Remote Output Queue, refer to one of the following Rochester Support Center knowledgebase documents: N1010090: Configuring a Remote Output Queue (RMTOUTQ) N1019443: Configuring a Remote Output Queue (RMTOUTQ) to a Label or Receipt Printer N1018931: Configuring a Remote Output Queue (RMTOUTQ) to a Windows Print Queue

Note: There is a known issue with Axis print servers not properly closing an LPR/LPD connection after printing a spooled file from a Power System server, which can result in spooled files staying in SND (Sending) status and printing repeatedly. This issue has been addressed by the latest firmware for Axis print servers. If experiencing this issue, download the latest firmware from the following Web site and verify that this resolves the problem:

www.axis.com/techsup/firmware.php



Symptom: Spooled File in SND Status and Spooled File does not Arrive on the Target Server or System

1	Is the target system powered on and cabled to the network?
2	Is the TCP/IP address correct? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
3	Can the TCP/IP address be PINGed? Follow Instruction Set (8) PING the Printer or Remote System by IP Address.
4	Is it a duplicate TCP/IP address? Follow Instruction Set (9) Determining if there is a Duplicate TCP/IP Address.
5	Has the target server been replaced with a new server that has been assigned the same TCP/IP address? If so, connectivity might not occur because of an old ARP cache entry that references the MAC address of the old printer that has been replaced. Follow Instruction Set (24) Clearing a Specific ARP Cache Entry.
6	Is the TCP/IP address specified in the Internet address (INTNETADR) parameter in the output queue description? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
7	Is a host name specified for the Remote system (RMTSYS) parameter? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description. Is there a host table entry for it? Follow Instruction Set (13) Determining and Changing a Host Table Entry.
8	Can the host name be PINGed? (PING HostName) Follow Instruction Set (8) PING the Printer or Remote System by IP Address.
9	Is the correct Remote printer queue (RMTPRTQ) parameter specified? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
10	Is the Remote printer queue (RMTPRTQ) parameter in uppercase when it should be in lowercase? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
11	Is it a large spooled file? (Large can be 20 pages on one system and 100 on another.)
12	Is the Line Printer Daemon (LPD) running/enabled on the target server? Discuss with the LAN administrator, verify the LAN adapter configuration, reboot the PC and/or reset the printer/LAN adapter and try again.
13	Is the Destination type (DESTTYPE) parameter correct? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description. Note: Use *OS400 for sending to another IBM i server, and use *OTHER for most other servers.
14	Is the Host Name Search Priority set to *REMOTE? Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used.
15	Is the server up and operational? (Discuss with the LAN administrator.)
16	Is the *SPOOL pool set too low? Follow Instruction Set (1) Determining and Changing the Size of the *SPOOL Pool.
17	Can a spooled file be sent to the target server successfully using the Send TCP/IP Spooled File (SNDTCPSPLF or LPR) command? Follow Instruction Set (17) SNDTCPSPLF (LPR Command)
18	If the target system is another IBM System i server, is the QTMPLPD user profile disabled or has the password has expired? Follow Instruction Set (11) Verifying and Changing the QTMPLPD User Profile.
19	If the target system is another IBM System i server, does the failing spooled file have the Output priority (OUTPTY) parameter set higher than the Highest schedule priority (PTYLMT) parameter in the QTMPLPD user profile on the receiving system? Follow Instruction Set (22) Determining the QTLPDxxxxx Job and Verifying the Output priority (OUTPTY) Parameter for the Spooled File in SND Status.
20	End the writer, check the spooled files in the output queue, cycle the printer or server, and restart the writer. Follow Instruction Set (18) Ending, Restarting, and Resetting the Writer.
21	Delete and re-create the output queue. For instructions on creating a Remote Output Queue, refer to one of the following Rochester Support Center knowledgebase documents: N1010090: Configuring a Remote Output Queue (RMTOUTQ) N1019443: Configuring a Remote Output Queue (RMTOUTQ) to a Label or Receipt Printer N1018931: Configuring a Remote Output Queue (RMTOUTQ) to a Windows Print Queue
22	Is the Line Printer Daemon (LPD) running on the source system? Follow Instruction Set (10) Determining if the Line Printer Daemon (LPD) Job is Running. Note: For the function of XAUTOQ queue to work, LPD must be running on the source system.
23	If the target system is another IBM System i server, consider collecting an LPD Flight Recorder Trace on the target system using the instructions in the following document: N1017910: Line Printer Daemon (LPD) Flight Recorder Trace Instructions

Symptom: All Remote Writers Have Stopped Printing

1	Is there a writer locking the QTMPLPRSEQ or QTMPLPRxxx data area? Follow Instruction Set (15) Determining and Releasing a Lock on the QTMPLPRxxx or QTMPLPRSEQ Data Area.
2	Is the Host Name Search Priority set to *REMOTE? Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used.
3	Is there a problem with the Domain Name Server (DNS)? Follow Instruction Set (4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used.
4	Can the TCP/IP address of the DNS be successfully PINGed? Follow Instruction Set (8) PING the Printer or Remote System by IP Address.

Symptom: Remote Writer Starts and Immediately Ends

1	Is the writer message queue full? Following Instruction Set (19) Determining if a Message Queue is Full.
2	Is the spooled file an *IPDS type file? Follow Instruction Set (20) Determining the Spooled File Attributes.

Symptom: Writer Starts, Spooled File Sends, but No Output Prints on the Printer

1	Is the Manufacturer type and model (MFRTYPMDL) parameter correct? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
2	Is the Destination type (DESTTYPE) parameter set to *OTHER? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
3	Is the Remote printer queue (RMTPRTQ) parameter correct? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
4	End the writer, check the spooled files in the output queue, cycle the printer or server, and restart the writer. Follow Instruction Set (18) Ending, Restarting, and Resetting the Writer.
5	Make sure the printer and LAN adapter microcode is up to date. (Contact the manufacturer.)
6	There is a possible hardware problem. (Contact the manufacturer or hardware support.)

Symptom: Spooled Files Print only a Single Copy When the Copies (COPIES) Parameter in the Spooled File Attributes is Greater than 1

1	Does the Destination options (DESTOPT) parameter have XAIX specified (in uppercase)? Follow Instruction Set (2) Determining and Changing a Remote Output Queue Description.
2	End the writer, check the spooled files in the output queue, cycle the printer or server, and restart the writer. Follow Instruction Set (18) Ending, Restarting, and Resetting the Writer.
3	Make sure the printer and LAN adapter microcode is up to date. (Contact the manufacturer.)
4	There is a possible hardware problem. (Contact the manufacturer or hardware support.)
5	Another option would be to try switching from using a Remote Output Queue (RMTOUTQ) to using a *LAN 3812 printer device description instead. For more information, refer to the section titled "Switching to Use a *LAN 3812 Printer Device Description" below.

Symptom: The Entire Spooled File is Printed When a Page Range Is Specified in the Page Range to Print (PAGERANGE) Parameter in the Spooled File Attributes

1	This is a limitation of Remote Output Queues.
2	One option would be to try switching from using a Remote Output Queue (RMTOUTQ) to using a *LAN 3812 printer device description instead. For more information, refer to the section titled "Switching to Use a *LAN 3812 Printer Device Description" below.
3	If the printer or network interface card (NIC) supports LPR/LPD, but does not support PJL, SNMP or IPP, then another option is to create a *LAN 3812 printer device description that uses the unsupported LPR Print Driver Exit Program (TSPLPRD) utility. For more information, refer to the following Rochester Support Center knowledgebase document: N1019586: Configuring a *LAN 3812 Device Description that Uses the LPR Print Driver (TSPLPRD) Exit Program
4	If the printer or network interface card (NIC) supports LPR/LPD, but does not support PJL, SNMP or IPP, then yet another option is to use the unsupported Remote Writer Page Range (TSPRWPR) utility with the Remote Output Queue so it will print using the page range specified in the spooled file attributes. For more information, refer to the following Rochester Support Center knowledgebase document: N1019686: TSPRWPR Remote Writer Page Range Support Exit Program

Symptom: Spooled file sent from one IBM System i to another are owned by the QSPLJOB or QTMPLPD user profile on the receiving system

1	Verify that the Remote Output Queue is configured with the Connection type (CNNTYPE) parameter set to *IP, the Destination type (DESTTYPE) parameter set to *OS400 and the Host print transform (TRANSFORM) parameter set to *NO. Also, the User Data Transform (USRDTATFM) parameter should be set to *NONE.
2	Verify that the user profile exists, is enabled, and that the password has not expired on the receiving system. If so, end and restart the LPD server on the receiving system using the following End TCP/IP Server (ENDTCPSVR) and Start TCP/IP Server (STRTCPSVR) commands: ENDTCPSVR SERVER(*LPD) STRTCPSVR SERVER(*LPD)
3	Verify that the user profile exists, is enabled, and that the password has not expired on the sending system. If so, end and restart the remote writer using the following End Writer (ENDWTR) and Start Remote Writer (STRRMTWTR) commands: ENDWTR WTR(WriterName) OPTION(*IMMED) STRRMTWTR OUTQ(WriterName)
4	If the problem is still not resolved, look at the job log for the QTLPDxxxxx jobs on the receiving system by following Instruction Set (23) Displaying the QTLPDxxxxx Job Logs). Also check the writer job log on the sending system for an indication of why the problem is occurring.

(1) Determining and Changing the Size of the *SPOOL Pool

Refer to the section entitled Checking and Changing the Size of the *SPOOL Pool below.

1	Use the Work with System Status (WRKSYSSTS) command and press the F11 Key twice to display the pool data, including the pool names. Note both the Pool Size (M) and the Max Active settings for the *SPOOL pool.
2	Examine the *SPOOL pool and estimate if it is an acceptable size for the system's printing needs: Refer to the Pool Configuration information in the Work Management Guide (SC41-4306) for a list of the suggested values. When using remote output queue printing, in most cases, Host Print Transform is also being used which increases the requirement for the *SPOOL pool. A good suggestion to start with is 5000K. The IBM Redbooks publication IBM AS/400 Printing V (SG24-2160-01) recommends a minimum of 6 MB. If the system has many, many writers, this should be higher. Contact Work Management or Performance for additional help if needed.
3	Use the following Display System Value (DSPSYSVAL) command to display the current setting of the QPFRADJ (Performance adjustment) system value: DSPSYSVAL SYSVAL(QPFRADJ)
4	If the QPFRADJ system value is set to 0 (No adjustment), then proceed to the next step to set the size of the *SPOOL pool. If the QPFRADJ system value is set to 1 (Adjustment at IPL), 2 (Adjustment at IPL and automatic adjustment), or 3 (Automatic adjustment), then use the Work with Shared Storage Pools (WRKSHRPOOL) command to first set a minimum percentage for the *SPOOL pool.
5	To change the size of the *SPOOL pool, use the WRKSYSSTS command and press the F11 Key twice, as was done in Step 1 above. Type over the existing values for the Pool Size and Max Active settings and press the Enter key to change the settings. Any additional memory allocated to the *SPOOL pool will be taken from the *BASE pool. Note: If the minimum percentage for the *SPOOL pool is not increased and Performance Adjustment is used, then the pool size will gradually be reduced by Performance Adjustment until it matches the minimum percentage, at which time it will no longer be at an acceptable size for the system's printing needs. For further assistance with adjusting the system's performance, contact a Technical Support representative in the Performance (PERF) queue.

(2) Determining and Changing a Remote Output Queue Description

To verify a parameter in a remote output queue description, use the Work with OUTQ Description (WRKOUTQD) command.

To change a parameter in a remote output queue description, do the following:

1	End the writer for the output queue, if needed, using the following End Writer (ENDWTR) command: ENDWTR WTR(WtrName) OPTION(*IMMED)
2	Type the following Change Output Queue (CHGOUTQ) command: CHGOUTQ OUTQ(OutQName) and press F4 to prompt. Note: If the Enter key is pressed, the output queue will be changed. If the Writers to autostart (AUTOSTRWTR) parameter is set to 1, a writer will be started for the output queue again. Start from Step 1 again.
3	Change the necessary parameter. Press F10 for additional parameters or the F9 key for all parameters if needed.

Notes:

o	The Remote printer queue (RMTPRTQ) parameter value is case sensitive. If the value for this parameter must be lowercase, it must be enclosed in single quotes (for example, 'raw').
o	The Destination type (DESTTYPE) parameter should be set to *OTHER when sending to a printer, or to a Microsoft Windows, UNIX, or Linux print server. The default value of *OS400 should only be used when sending from one Power System server to another Power System server.
o	The Destination options (DESTOPT) parameter is also case sensitive. XAIX must be entered in uppercase, but some filters must be entered in uppercase and some must be entered in lowercase. If the value for the parameter must be in lowercase, it must be enclosed in single quotes, for example, 'x').
o	XAUTOQ processing is done automatically at V4R4 OS/400 and above, whether Destination options (DESTOPT) parameter specifies XAUTOQ or not. If the connection to the printer, print server, PC, or server is lost, XAUTOQ processing will take that the ASCII printer data stream generated by Host Print Transform (HPT) and store it in a *USERASCII spooled file with the same name as the original spooled file. That way the remote writer can attempt to send the ASCII printer data stream without having to use HPT to transform the original spooled file over again. Without XAUTOQ processing, large spooled files could stay in SND status indefinitely if the connection timed out before HPT was able to convert the spooled file to an ASCII printer data stream.

(3) Determining if there is a TCP/IP Interface

1	Type the following Configure TCP/IP (CFGTCP) command without any parameters: CFGTCP
2	Select Option 1 to Work with TCP/IP interfaces.
3	Verify that there is not an interface defined that has the TCP/IP address of the printer.

(4) Determining and Changing the Host Name Search Priority and to see if a Dynamic Name Server (DNS) is being used

1	Type the following Configure TCP/IP (CFGTCP) command without any parameters: CFGTCP
2	Select Option 12 (Change TCP/IP domain information).
3	If there is a TCP/IP address listed in the Domain name (DMNNAME) parameter, the system is using a DNS.
4	Verify the Host name search priority (HOSTSCHPTY) parameter. If this is set to *REMOTE, change it to *LOCAL by typing the new value.

(5) Collecting a TCP/IP Communications Trace

1	Refer to one of the following Rochester Support Center knowledgebase documents for step-by-step instructions on collecting a communications trace: N1019135: Running a TRCCNN Trace for LAN Printing Problems N1019324: Communications Trace for TCP/IP Printers Using the STRCMNTRC Command N1019451: Communications Trace for TCP/IP Printers (R510 and Above)
2	Incorporate the help of someone who can read the trace if needed. Involve AS4PRT or TCP as needed.

(6) Decreasing the Maximum Transmission Unit (MTU) Size on a Host Route or a TCP/IP Interface

Get assistance from the IBM i Communications Support (COM) queue to either setup a host route to the printer or router that has a smaller value for the Maximum Transmission Unti (MTU) parameter.

(7) Determining if TCP/IP is Started

1	Issue the STRTCP command. If a message is returned stating that TCP/IP is already started, it is started. If the message is not returned, TCP/IP will be started.

(8) PING the Printer or Remote System by IP Address

Ensure that the printer is powered on and cabled to the network. The printer TCP/IP address must be "PINGable" from the Power System server (some might PING from DOS).

1	CALL QCMD so the messages from the PING request can be seen.
2	On the command line, issue PING RMTSYS('xxx.xxx.xx.x'). (Note: The TCP/IP address is enclosed in single quotes.)
3	Check messages returned from PING request: o If 5 of 5 attempts are successful, the TCP/IP address is okay. o If X of 5 attempts are successful, where X is between 1 and 4, there is likely a network issue and printing might or might not work. o If 0 of 5 attempts are successful, the TCP/IP address was not enclosed in single quotes on the PING command, it is the wrong TCP/IP address, or there is a network problem. Reset the printer and try again, otherwise contact the network administrator.

Note: The TCP/IP address should not be specified with leading zeroes in the Internet address (INTNETADR) parameter of output queue description, for example, specify the TCP/IP address as '192.168.2.51', rather than '192.168.002.051'. The PING or Verify TCP/IP Connection (VFYTCPCNN) command can handle TCP/IP addresses specified with leading zeros, but the remote writer cannot. Leading zeros will cause the remote writer to consider the TCP/IP address to be specified in octal (Base 8) rather than Decimal (Base 10), so it will be attempting to communicate with the wrong printer or print server.

(9) Determining if there is a Duplicate TCP/IP Address

1	Power off and/or uncable the printer from the network.
2	PING the printer (follow Instruction Set 8).

Note: If the PING request is successful, there is a duplicate TCP/IP address. Contact the network administrator to resolve the duplicate address. If the PING request is not successful, there is not a duplicate TCP/IP address.

(10) Determining if the Line Printer Daemon (LPD) Job is Running

TCP supports LPD running on the operating system. TCP does not support other types of systems running LPD, for example, a PC running an OEM LPD product.

1	NETSTAT
2	Select Option 3 to Work with TCP/IP connection status.
3	Look for LPD under the Local Port column. If found, verify that it is in a LISTEN state. LPD found and in LISTEN state? No - go to Step 5 Yes - go to Step 4
4	Are there QTLPDxxxxx jobs in the QSYSWRK subsystem? WRKACTJOB SBS(QSYSWRK) JOB(QTLPD*) No - go to Step 5 Yes - go to Step 6
5	If the answer to question 3 or 4 is No, start the LPD server: STRTCPSVR SERVER(*LPD)
6	If the answer to question 3 or 4 is Yes, try ending and restarting the LPD server using the following End TCP/IP Server (ENDTCPSVR) and Start TCP/IP Server (STRTCPSVR) commands: ENDTCPSVR SERVER(*LPD) STRTCPSVR SERVER(*LPD)

Note: If the LPD Server ends unexpectedly on the receiving operating system after starting the LPD Server, look at the QTLPDxxxxx job logs for an indication of why the LPD Server job failed by following Instruction Set (23) Displaying the QTLPDxxxxx Job Logs.

(11) Verifying and Changing the QTMPLPD User Profile

1	On the operating system command line, type the following: WRKUSRPRF USRPRF(QTMPLPD)
2	Select Option 5 to Display or Option 2 to Change.
3	Verify that the Status is *ENABLED.
4	Verify that the Date password expires has not passed. Change the user password to *NONE or reset the expiration date as needed. This can be done by selecting Option 2 (Change) on the QTMPLPD user profile or by using the following Change User Profile (CHGUSRPRF) command and specifying the following settings: CHGUSRPRF USRPRF(QTMPLPD) PASSWORD(*NONE) PWDEXP(*NO) STATUS(*ENABLED) Note: The QTMPLPD can be prevented from being disabled in the future by adding it to the Active Profile List. This can be done by using the following Change Active Profile List (CHGACTPRFL) command: CHGACTPRFL USRPRF(QTMPLPD) ACTION(*ADD)
5	Verify that the Maximum allowed storage (MAXSTG) parameter is set to *NOMAX, if needed.
6	End the LPD server using the following End TCP/IP Server (ENDTCPSVR) command: ENDTCPSVR SERVER(*LPD)
7	Use the following Work with Active Jobs (WRKACTJOB) command to work with all of the jobs running in the QSYSWRK subsystem: WRKACTJOB SBS(QSYSWRK) JOB(QTLPD*) Press the F14 (Include) Key to include suspended group jobs, inactive prestart jobs, suspended system request jobs, and disconnected jobs on the display. Page down and look for any QTLPDxxxxx jobs running on the system. Note: If any QTLPDxxxxx jobs are found, then press the F5 (Refresh) key periodically to determine if any QTLPDxxxxx jobs are still listed. Wait until all QTLPDxxxxx are removed from the list (indicating that all of those jobs have ended) before proceeding with the next step.
8	Start the LPD server using the following Start TCP/IP Server (STRTCPSVR) command: STRTCPSVR SERVER(*LPD)

(12) Verifying and Changing a User Profile other than QTMPLPD

1	On the operating system command line, type the following: WRKUSRPRF USRPRF(user-profile-name)
2	Select Option 5 to Display or Option 2 to Change.
3	Verify that the Status is *ENABLED.
4	Verify that the Maximum allowed storage (MAXSTG) parameter is set to *NOMAX, if needed.
5	End the LPD server using the following End TCP/IP Server (ENDTCPSVR) command: ENDTCPSVR SERVER(*LPD)
6	Use the following Work with Active Jobs (WRKACTJOB) command to work with all of the jobs running in the QSYSWRK subsystem: WRKACTJOB SBS(QSYSWRK) JOB(QTLPD*) Press the F14 (Include) Key to include suspended group jobs, inactive prestart jobs, suspended system request jobs, and disconnected jobs on the display. Page down and look for any QTLPDxxxxx jobs running on the system. Note: If any QTLPDxxxxx jobs are found, then press the F5 (Refresh) key periodically to determine if any QTLPDxxxxx jobs are still listed. Wait until all QTLPDxxxxx are removed from the list (indicating that all of those jobs have ended) before proceeding with the next step.
7	Start the LPD server using the following Start TCP/IP Server (STRTCPSVR) command: STRTCPSVR SERVER(*LPD)

(13) Determining and Changing a Host Table Entry

1	Type the following Configure TCP/IP (CFGTCP) command without any parameters: CFGTCP
2	Select Option 10 to Work with host table entries.
3	Look for the TCP/IP address and/or the name of the Power Systems server or printer.
4	If found, verify the address and name are correct.
5	If not found, an entry must be created: a On the first line, select Option 1 to Add, type the TCP/IP address, and press the Enter key. b Specify the host names to be given to the TCP/IP address.

Note: If the entry is for the Power Systems server, both the long and short names for the system should be specified. The short name for the system is just the local host name. The long name for the system is the local host name.(dot) local domain name. Follow and Instruction Set (14) Determining and Changing Domain and Host Information to determine the local host and domain names.

For example, when using Instruction Set (14), it is determined that the local host name and domain information for RCHASBDS is:

Local Host Name RCHASBDS
Domain Name RCHLAND.IBM.COM

The short name is RCHASBDS.
The long name is RCHASBDS.RCHLAND.IBM.COM.

If adding a host table entry for the system:

o	For the first host name, specify the short name for the system.
o	Put a '+' in the field for '+ for more values' and press the Enter key.
o	For the second host name, specify the long name for the system.

If adding a host table entry for the printer:

o	Specify the host name to be given to the printer's TCP/IP address.
o	Press the Enter key.

Note: Host and domain names are case sensitive. If the host and/or domain name are lowercase, the host table entry for the system must be lowercase also. Lowercase attributes are maintained by enclosing the name in single quotes, for example, 'rchasbds'.

(14) Determining and Changing Domain and Host Information

1	Type the following Configure TCP/IP (CFGTCP) command without any parameters: CFGTCP
2	Select Option 12 (Change TCP/IP domain information).
3	Verify the host and domain names.
4	If missing, give them names (you might need to get the correct names from the system administrator).
5	Follow Instruction Set 12 for adding a host table entry.

Note: Host and domain names are case sensitive. If the host and/or domain name are lowercase, the host table entry for the system must be lowercase also. Lowercase attributes are maintained by enclosing the name in single quotes, for example, 'rchasbds'.

(15) Determining and Releasing a Lock on the QTMPLPRxxx or QTMPLPRSEQ Data Area

Checking For a Lock on the QTMPLPRxxx Data Area

1	You must first determine the name of the data area used for a particular Remote Output Queue. This is based on the TCP/IP address used for the Remote Output Queue. Therefore, the first step is to display the output queue description to determine if it is using a host name or a TCP/IP address.
2	If the output queue description is using a host name, use the Verify TCP/IP Connection (VFYTCPCNN or PING) command with the Remote system (RMTSYS) parameter set to the host name and look at the resulting messages to determine the TCP/IP address.
3	Convert the last two portions of the TCP/IP address from decimal to hexadecimal. For example, if the TCP/IP address is "192.168.208.29" then the "208" and "29" will be converted to X'D0' and X'1C', respectively.
4	Combine these numbers to get a 4 digit hexadecimal number. For example, X'D0' and X'1C' would be combined to a value of X'D01C'.
5	Take the last 3 digits of this number. For example, the last 3 digits are "01C".
6	Use the Work with Object Locks (WRKOBJLCK) command to check for a lock on the QTMPLPRxxx data area. In the example, the command would be: WRKOBJLCK OBJ(QTCP/QTMPLPR01C) OBJTYPE(*DTAARA)

Releasing a Lock on the QTMPLPRSEQ or QTMPLPRxxx Data Area

1	Select Option 4 to End next to the first job in the list and press the Enter key twice.
2	Press F5 to refresh to see if other locks appear and/or disappear (this indicates that the writers should be working again).
3	Refer to the following Rochester Support Center knowledgebase document for step-by-step instructions on putting the remote writer into DEBUG mode: N1018446: Activating Debug Mode for Remote Output Queues (RMTOUTQs) and SNDTCPSPLF

(16) Determining if TCP/IP is Installed

1	On the operating system command line, type the following: GO LICPGM
2	Select Option 10 to Display the installed licensed programs.
3	Verify that TCP/IP is installed. For 5.4 i5/OS, the product is 5722TC1 (IBM TCP/IP Connectivity Utilities for i5/OS), for 6.1 i5/OS the product is 5761TC1 (IBM TCP/IP Connectivity Utilities for i5/OS), and for 7.1 i5/OS the product is 5770TC1 (IBM TCP/IP Connectivity Utilities for i).

(17) SNDTCPSPLF (LPR Command)

The spooled file name, spooled file number and fully qualified job name for the spooled file are needed to issue the Send TCP/IP Spooled File (SNDTCPSPLF or LPR) command. You will also need the TCP/IP address of the printer. Following are instructions on how to get the necessary spooled file information:

1	Select Option 8 next to the desired spooled file on the WRKOUTQ or WRKSPLF screen to work with the spooled file Attributes.
2	On the top and right side of the screen, note the File name and Number.
3	On the top and left side of the screen, note the Job name, User name and Number (this is the fully qualified job name).

Following are the instructions for issuing the Send TCP/IP Spooled File (SNDTCPSPLF or LPR) command to send to a network printer:

1	On the command line, type SNDTCPSPLF or LPR and press F4 to prompt on it.
2	Specify the Remote System as *INTNETADR.
3	Specify the Printer Queue as the necessary (this value is dependent on the type of printer/adapter that the file is being sent to). Refer to the following Rochester Support Center knowledgebase document to determine the correct value to use: N1010172: Recommended Remote Printer Queue Values for Remote Output Queues (RMTOUTQs) Note: This value is case sensitive. If the value is to be in lowercase or mixed case, enclose it in single quotes.
4	Specify the spooled file name, the fully qualified job name and the spooled file number.
5	Specify the Destination Type as *OTHER.
6	Specify Transform SCS to ASCII as *YES.
7	Press the Enter key for more parameters or press F10 or F9.
8	Specify the appropriate Manufacturer Type and Model for the printer the file is being sent to.
9	Page down to the next page and specify the Internet Address as the TCP/IP address of the printer and press the Enter key.

(18) Ending, Restarting, and Resetting the Writer

1	Use the End Writer (ENDWTR) command with the When to end writer (OPTION) parameter set to *IMMED to end the remote writer immediately. For example: ENDWTR WTR(writer-name) OPTION(*IMMED)
2	Use the Work with Writers (WRKWTR) command with the Writer (WTR) parameter set to *ALL to verify that the remote writer has ended. For example: WRKWTR WTR(*ALL) DSPFMT(*NORMAL) ASTLVL(*INTERMED)
3	Use the Work with Output Queue (WRKOUTQ) command to check on the status of the spooled files waiting on the Remote Output Queue (RMTOUTQ). For example: WRKOUTQ OUTQ(rmtoutq-name)
4	If there are any spooled files still in SND (Sending) status, even though the status of the output queue is "RLS" instead of "RLS/WTR", then use the Work with Output Queue (WRKOUTQ) command with the Output (OUTPUT) parameter set to *PRINT. For example: WRKOUTQ OUTQ(library-name/output-queue-name) OUTPUT(*PRINT) Note: Special code has been added to clean up the index of the output queue when OUTPUT(*PRINT) is specified on the WRKOUTQ command.
5	If running 6.1 (V6R1M0 or R610) or 7.1 (V7R1M0 or R710) i5/OS, use the Start Spool Reclaim (STRSPLRCL) command to repair this particular output queue or all output queues in a given auxiliary storage pool (ASP), as well as any spooled files that are left in unrecoverable states. For example: STRSPLRCL OUTQ(library-name/outq-name) ASPGRP(*) STRSPLRCL OUTQ(*ALL) ASPGRP(*) Note: QSPFIXUP is no longer supported in V6R1M0 (R610) i5/OS and has been replaced by the Start Spool Reclaim (STRSPLRCL) command. The STRSPLRCL command can be used to repair output queues and spooled files that are left in unrecoverable states. It can be run for a single output queue, a set of output queues using a generic name (such as PRT*), or for all output queues in the auxiliary storage pool (ASP) defined by the ASP group (ASPGRP) parameter.
6	If running 5.4 (V5R4M0 or R540) i5/OS, call the QSPFIXUP program to have the system go through all spooled files on the system and verifying that they are in the correct status. For example: CALL PGM(QSPFIXUP)
7	Use Work with Output Queue (WRKOUTQ) command again to verify that there are no spooled file still in SND status. For example: WRKOUTQ OUTQ(library-name/output-queue-name) OUTPUT(*PRINT)
8	Power the target printer and LAN adapter (if the printer is attached to an external LAN adapter off, unplugging them if necessary, then power them back on again. Note: If sending to a server, consider rebooting or IPLing the server.
9	Use the Start Remote Writer (STRRMTWTR) command to restart the remote writer. For example: STRRMTWTR WTR(writer-name)

(19) Determining if a Message Queue is Full

Refer to the following Rochester Support Center knowledgebase document to determine which message queue is being used by the writer:

N1018048: Identifying the Message Queue That a Writer is Using, Finding the Writer Job Log and Increasing the Message Logging Level for a Writer Job

After this has been determined, do the following:

1	On the operating system command line, type the following: DSPMSG MSG(WriterMessageQueueName)  Press the Enter key.
2	Move the cursor to the last message in the message queue and press the F1 key for help (if in basic assistance level, go to the last message and put a 5 to Display the details of the message).
3	Determine the date and time of the message.

If the time and date of the message is current, the message queue is probably not full. If the time and date of the message is not current, the message queue probably must be cleared. To clear the message queue, use the CLRMSGQ MSGQ(MessageQueueName) command.

(20) Determining the Spooled File Attributes

To determine the spooled file attributes do the following:

1

Use the Work with Spooled Files (WRKSPLF) or Work with Output Queue (WRKOUTQ) command and select Option 8 (Attributes) next to the spooled file.

2

The second page in the attributes will tell what type of file it is (Printer Device Type) as well as the printer file used (Device File). The third page might have only one parameter on it (User-Defined File) and the rest of the screen will be blank. This is not the end of the file. Note that there is a MORE.... option in the lower right corner. Continue paging down to see the rest of the attributes.

(21) Determining if there is an Active TCP/IP Route

1	Type the following Configure TCP/IP (CFGTCP) command without any parameters: CFGTCP
2	Select Option 2 to Work with TCP/IP routes.
3	Verify that there is a valid and active route to the TCP/IP address of the printer.
4	If a route is configured or the printer and Power System server are in the same subnet, try ending and restarting TCP/IP.
5	Try pinging the TCP/IP address of the printer again.

(22) Determining the QTLPDxxxxx Job and Verifying the Output priority (OUTPTY) Parameter for the Spooled File in SND Status

1	Use the following Display User Profile (DSPUSRPRF) command to display the QTMPLPD user profile: DSPUSRPRF USRPRF(QTMPLPD) Verify the value for the Highest schedule priority (PTYLMT) parameter. The QTMPLPD user profile ships with the PTYLMT parameter set to 3.
2	If target system is another Power Systems server, locate the QTLPDxxxxx jobs on the receiving system. Use the following Work with Active Jobs (WRKACTJOB) command: WRKACTJOB SBS(QSYSWRK)
3	Page down to find the QTLPDxxxxx jobs. Select Option 5 (Work with), Option 10 (Display job log, if active or on job queue), and press F10 (Display detailed messages) for each QTLPDxxxxx job listed in the QSYSWRK subsystem.
4	If message CPF4355 - OUTPTY value &6 exceeds priority limit for user QTMPLPD is found in one or more of the QTLPDxxxxx jobs, go to the sending operating system, select Option 8 (Attributes) on the spooled file in SND (Sending) status, and determine if the Output priority (OUTPTY) parameter is higher than the Highest schedule priority (PTYLMT) parameter in the QTMPLPD user profile on the receiving system.
5	To resolve the problem, end the remote writer with OPTION(*IMMED), then do one of the following:
5a	Use the Change User Profile (CHGUSRPRF) command to change the QTMPLPD user profile on the receiving system to set the Highest schedule priority (PTYLMT) parameter to 0, instead of the default value of 3. For example: CHGUSRPRF USRPRF(QTMPLPD) PTYLMT(0) and then restart the remote writer on the sending system.
5b	Take Option 2 (Change) on the spooled file that was staying in SND status on the sending system and set the Output priority (OUTPTY) parameter to the value for the Highest schedule priority (PTYLMT) parameter in the QTMPLPD user profile on the receiving system, and then restart the remote writer.

(23) Displaying the QTLPDxxxxx Job Logs

1	Change the QTMPLPD job description in library QTCP to set the Message logging (LOG) parameter to LOG(4 00 *SECLVL) on the receiving system to ensure that the QTLPDxxxxx job logs are generated. This is done by using the following Change Job Description (CHGJOBD) command: CHGJOBD JOBD(QTCP/QTMPLPD) LOG(4 00 *SECLVL)
2	End and restart the LPD server on the receiving system using the following End TCP/IP Server (ENDTCPSVR) and Start TCP/IP Server (STRTCPSVR) commands: ENDTCPSVR SERVER(*LPD) STRTCPSVR SERVER(*LPD)
3	Reproduce the problem sending spooled files to the receiving system.
4	After the problem has been reproduced, use the following Work with Spooled Files (WRKSPLF) command to find the QTLPDxxxxx job logs: WRKSPLF SELECT(QTCP *ALL *ALL QTLPD*)

(24) Clearing a Specific ARP Cache Entry

An existing printer might have been replaced with a new printer that has been assigned the same TCP/IP address, and connectivity might not occur because of an old ARP cache entry that references the MAC address of the old printer that has been replaced. To determine this, or to remove the old ARP cache entry, follow the instructions in the following Rochester Support Center knowledgebase document:

N1015699: Clearing a Specific ARP Cache Entry

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

 

PTF Number	Licensed Program	Version	Description
SF99366	5770SS1	V7R1M0	710 Print Group PTF for V7R1M0
SF99356	5761SS1	V6R1M0	610 Print Group PTF for V6R1M0
SF99347	5722SS1	V5R4M0	540 Print Group PTF for V5R4M0

Otherwise, for a list of the latest PTFs, including PTFs that are not yet included in the latest Print Group PTF, please refer to the IBM i Support: Recommended Fixes web page:

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

The amount of memory allocated to the *SPOOL pool and the maximum number of active jobs can have an affect on whether a writer is able to print, or how quickly a writer is able to print, to a network attached printer. To check and change the size of the *SPOOL, do the following:

1	Use the Work with System Status (WRKSYSSTS) command and press the F11 key twice to display the pool data, including the pool names. Note both the Pool Size (M) and the Max Active settings for the *SPOOL pool.
2	Examine the *SPOOL pool and estimate if it is an acceptable size for the system's printing needs: Refer to the Pool Configuration information in the Work Management Guide (SC41-4306) for a list of the suggested values. When using remote output queue printing, in most cases, Host Print Transform is also being used which increases the requirement for the *SPOOL pool. A good suggestion to start with is 5000K. The Printing V Redbooks recommends a minimum of 6 MB. If the system has many, many writers, this should be higher. Contact Work Management or Performance for additional help if needed.
3	Use the following Display System Value (DSPSYSVAL) command to display the current setting of the QPFRADJ (Performance adjustment) system value: DSPSYSVAL SYSVAL(QPFRADJ)
4	If the QPFRADJ system value is set to 0 (No adjustment), then proceed to the next step to set the size of the *SPOOL pool. If the QPFRADJ system value is set to 1 (Adjustment at IPL), 2 (Adjustment at IPL and automatic adjustment), or 3 (Automatic adjustment), then use the Work with Shared Storage Pools (WRKSHRPOOL) command to first set a minimum percentage for the *SPOOL pool.
5	To change the size of the *SPOOL pool, use the WRKSYSSTS command and press the F11 Key twice, as was done in Step 1 above. Type over the existing values for the Pool Size and Max Active settings and press the Enter key to change the settings. Any additional memory allocated to the *SPOOL pool will be taken from the *BASE pool. Note: If the minimum percentage for the *SPOOL pool is not increased and Performance Adjustment is used, then the pool size will gradually be reduced by Performance Adjustment until it matches the minimum percentage, at which time it will no longer be at an acceptable size for the system's printing needs. For further assistance with adjusting the system's performance, contact a Technical Support representative in the Performance (PERF) queue.

Many of the limitations listed above can be addressed by switching from using a remote writer, which is the type of writer started for Remote Output Queues (RMTOUTQs), to using a printer writer instead, which is type of writer started for *LAN 3812 printer device descriptions and PC5250 printer sessions. Specifically, the limitations addressed by switching to use a *LAN 3812 device description or a PC5250 printer session include page range support, printing multiple copies, receiving message CPA3394 - Load form type '&4' device &5 writer &1, receiving message CPA4002 - Verify alignment on printer &3 (when printing to a continuous form printer), printing file separators or job separators, starting a writer by using the Work with Writers (WRKWTR) command and taking Option 1 (Start) next to the writer name, and managing the writer and spooled files from iSeries Navigator.

There are limitations to printing through a *LAN 3812 device description or a PC5250 printer session, though there are fewer limitations than with RMTOUTQs. For more information, refer to the following Rochester Support Center knowledgebase documents:

N1019003: Capabilities and Limitations of *LAN 3812 Printer Device Descriptions
N1019636: Capabilities and Limitations of Printing when Using iSeries Access for Windows

Rochester Support Center knowledgebase document New contains links to several other documents. Each of the documents listed contain information on printers from one of various manufacturers, and provides information about the printer data streams supported by each printer, whether the printer is a Microsoft Windows Only printer, whether the printer will work with and how it will work with Personal Communications 5250 (PC5250), Host Print Transform (HPT), Remote Output Queues, *LAN 3812 PJL device descriptions, *LAN 3812 SNMP device descriptions, and *LAN 3812 IPP device descriptions. For information on printers from other manufacturers, refer to the following Rochester Support Center knowledgebase documents:

N1019605: Information on Printers from Various Manufacturers

Switching to use a *LAN 3812 PJL, SNMP, or IPP device description requires support for the HP PJL (Printer Job Language), SNMP (Simple Network Management Protocol), or IPP (Internet Print Protocol) in the printer hardware, as well as in the internal network interface card (NIC) or external print server used with that printer. For more information, refer to the following Rochester Support Center knowledgebase documents:

N1010134: Configuring a *LAN 3812 PJL Device Description
N1019572: Configuring a *LAN 3812 SNMP Device Description
N1019375: Configuring a *LAN 3812 IPP Device Description

If it looks like the printer, network interface card (NIC) or print server do not support PJL, SNMP or IPP, or if unable to get a *LAN 3812 PJL, SNMP, or IPP device description to successfully print to the printer, then another option would be to switch to using a *LAN 3812 device description that uses the unsupported LPR Print Driver (TSPLPRD) utility. For more information, refer to the following Rochester Support Center knowledgebase document:

N1019586: Configuring a *LAN 3812 Device Description that Uses the LPR Print Driver (TSPLPRD) Exit Program

You could also configure a PC5250 printer session on a Windows PC that is able to print to the printer and that has System i Access for Windows or Windows iSeries Access for Windows installed. However, the Windows PC would need to be powered on and the PC5250 printer session would need to started in order to print. When printing to a LAN attached printer, it is generally better to use a *LAN 3812 device description that uses the unsupported LPR Print Driver (TSPLPRD) utility, particularly when you already know that you are able to print to the printer using LPR/LPD by use of a RMTOUTQ. However, for step-by-step instructions on configuring a PC5250 printer session, refer to the following Rochester Support Center knowledgebase document:

N1018716: System i Access for Windows: Configuring a PC5250 Printer Session