IBM Support

Configuration Settings and Error Messages for *LAN 3812 SNMP Device Descriptions

Technote (troubleshooting)


Problem(Abstract)

This document contains information on configuration settings and error messages for *LAN 3812 SNMP device descriptions.

Resolving the problem

This document contains information on configuration settings and error messages for *LAN 3812 SNMP device descriptions. The term SNMP refers to Simple Network Management Protocol. SNMP allows for two-way communication with the printer when attached to the LAN using a print server that also supports SNMP.

*LAN 3812 SNMP device descriptions have become a popular and recommended alternative to using Remote Output Queues, which use LPR/LPD. This is also an alternative to using *LAN 3812 PJL device descriptions, which are only supported for laser printers and print servers that support HP's PJL (Printer Job Language) protocol. *LAN 3812 SNMP device descriptions are similar to *LAN 3812 PJL device descriptions and as such they fully support the page range function. For information on configuration and limitations of *LAN 3812 SNMP device descriptions, refer to the following Rochester Support Center knowledgebase document:

N1019572: Configuring a *LAN 3812 SNMP Device Description

The success of this connection is dependent on the configuration settings in IBM OS/400 or IBM i5/OS and the printer. The TCP/IP network also has an effect on performance and starting of the printer writer. The following suggestions are intended to make this transition smooth and affects its success. Because the HP, Lexmark, and IBM printers are the most common, the examples include only these printers even though *LAN 3812 SNMP device descriptions work with other printers.

This document contains the following sections:

1. Timeout Settings on the Print Server discusses the timeout settings in the print server hardware.
2. Timeout Settings on the Printer discusses the timeout settings in the printer hardware.
3. Recommended Timeout Settings for IBM, HP and Lexmark Print Servers lists the recommended timeout settings for certain IBM, HP and Lexmark print servers.
4. Timeout Settings in the OS/400 or i5/OS Printer Device Description discusses some settings in the printer device configuration in OS/400 or i5/OS that can cause writers to end.
5. TCP/IP Keep-Alive Value on the OS/400 or i5/OS System discusses setting the TCP/IP Keep Alive value by using the CHGTCPA command on the operating system.
6. Inquiry (CPA) Messages versus Informational (CPI) Messages discusses what to do when certain error messages are received as inquiry (or CPA) messages, rather than as informational (or CPI) messages.
7. Error Messages for *LAN SNMP Device Descriptions at R450 and Above contains the messages that are associated with SNMP printing. These messages are found in the writer job log.
8. Additional Error Messages for *LAN SNMP Device Descriptions at R430 or R440 contains the messages that are associated with SNMP printing. These messages are found in the writer job log.
9. Known Issues with *LAN 3812 SNMP Device Descriptions discusses known issues with *LAN 3812 SNMP device descriptions that do not necessarily involve any specific error messages.
10. Required PTF Levels contains links to the latest PTF lists for TCP/IP printing.
11. Checking and Changing the Size of the *SPOOL Pool contains information about how to determine the size of the *SPOOL pool and how to adjust the size.
This document was last updated 20 October 2014.



    • - Timeout Settings on the Print Server



      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 OS/400 or i5/OS spooled file is sent to the printer or the timeout expires between the sending of buffers, the printer writer ends with message CPD337C, The session with device &1 ended abnormally, and the OS/400 or i5/OS 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.

      • - Timeout Settings on the Printer



        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 execution 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's buffer while complex transforming is taking place during which this timer expires and, therefore, ejects an incomplete page.

        • - Recommended Timeout Settings for HP, Lexmark and IBM Print Servers



          IBM Network Printer and IBM 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.

          For information on disabling the timeout on an IBM Infoprint 21 printer, refer to the following Rochester Support Center knowledgebase document:

          N1017230: Disabling the Network Timeout Values on an IBM Infoprint 21 Printer

          IBM Infoprint 1000, 1200, 1300 or 1400 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. If the printer has a Network Job Timeout then that should also be disabled by setting it to 0. These timeout values can typically be set through the control panel on the printer, or by using the Lexmark MarkVision Utility. The Lexmark MarkVision Utility can be downloaded from Lexmark's Web site, www.lexmark.com/.

          • - Timeout Settings in the OS/400 or i5/OS Printer Device Description



            Settings in the printer device configuration on the OS/400 or i5/OS system that can cause writers to end are the Inactivity timer and Activation timer.

            The recommended setting for Inactivity timer is some value other than *NOMAX so that the connection will be closed during periods of no activity. Even if not sharing on the network, *NOMAX can cause problems with the writer connection.

            The Activation timer should be set to a value large enough to prevent posting of intervention errors due to TCP/IP transmission delays and printer processing delays. The default setting of 170 seconds is usually large enough to accomplish this unless you send large files to a printer with a slow processor that has a lot of memory. Increasing the activation time prevents unwanted intervention errors; however, that time will have to pass before you will get a desired intervention error.

            Note that intervention errors do not stop the print process. If the Printer Error Message parameter in the Device Description for the writer is set to *INQ, then the intervention will require an operator input to retry or to cancel the writer. (At R370, the Printer Error message is not recognized on ASCII printers. Change the user-defined options parameter to ERRMSGINFO). If the parameter is set to *INFO, the driver continues to retry until the connection has been established or TCP/IP has closed the socket or, in the case of a slow printer processor, the proper response is obtained, which is when the printer is on-line or when the printer has received all the data. If the connection is eventually successful, the intervention message is attempted to be removed from the message queue and process continues.

            • - TCP/IP Keep-Alive Value on the OS/400 or i5/OS System



              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 operating 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.

              • - Inquiry (CPA) Messages versus Informational (CPI) Messages



                The Error Messages for *LAN SNMP Device Descriptions section includes several messages that have both a CPA (or inquiry) message ID, such as CPA404D, as well as a CPI (or informational) message ID, such as CPI404D. If one of the CPA messages is received as an inquiry message, then the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO.

                When the *LAN 3812 SNMP device description has PRTERRMSG(*INQ) specified and a problem is detected in the printer hardware, then one of the CPA messages will be issued as an inquiry message, so someone must answer this message with an "R" (Retry) after the printer is ready to continue printing. If the message is not answered with an "R" in a timely manner, it could cause the printer hardware to drop the connection, which would then cause the writer to end unexpectedly.

                When the *LAN 3812 SNMP device description has PRTERRMSG(*INFO) specified and a problem is detected in the printer hardware, then one of the CPI messages will be issued as an informational message; however, the printer writer will continue to poll the printer so printing should continue after the printer is ready to continue printing.

                • - Error Messages for *LAN SNMP Device Descriptions



                  CPA404D "A paper jam has occurred on device &1 (C R)" or
                  CPI404D "A paper jam has occurred on device &1"
                  This indicates that a paper jam was detected on the printer hardware. The printer writer will be unable to print until the paper jam has been cleared.

                  Note: If message CPA404D is received, the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPA404E "Device &1 not ready (C R)" or
                  CPI404E "Device &1 not ready"
                  This indicates that an error was detected on the printer hardware, so the printer writer is unable to print. This is most likely caused by someone taking the printer off-line, but look at the printer control panel on the printer hardware to determine if there is some other cause for the problem.

                  Note: If message CPA404E is received, then the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPA404F "Problem with device &1 (C R)" or
                  CPI404F "Problem with device &1"
                  Messages CPA404F and CPI404F indicate that there is a problem with the printer hardware, including but not limited to one of the following:

                  1 The printer is busy printing from another host.
                  2 The printer is out of paper (end of forms condition).
                  3 The printer has a paper or forms jam.
                  4 The printer is running low on toner.
                  5 The printer may not be ready to print and may require operator intervention.
                  The problem can usually be determined by looking at the printer control panel or by using the printer's Web access (built-in Web server) by specifying the printer's TCP/IP address or host name in the Address Bar on a Web browser. Once the printer hardware problem has been identified and resolved, the writer should continue to print without further intervention on the system, such as answering an inquiry message.

                  If message CPI404F is received but you are generally able to print through the *LAN 3812 SNMP device description, then verify that the User-defined options (USRDFNOPT) parameter set to *IBMSHRCNN. Specifying USRDFNOPT(*IBMSHRCNN) in the *LAN 3812 SNMP device description may reduce the incidents where spooled files are in MSGW (Message Waiting) status with message CPI404F.

                  Note: If message CPA404F is received, the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPA405B "A door, cover, or interlock is open on device &1 (C R)" or
                  CPI405B "A door, cover, or interlock is open on device &1"
                  Cause: An error was detected on device &1.

                  Recovery: A door, cover, or interlock was open. Look at the printer to determine the cause of the problem.

                  Note: If message CPA405B is received, the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPA405C "An input tray needs attention on device &1 (C R)" or
                  CPI405C "An input tray needs attention on device &1"
                  Cause: An error was detected on device &1.

                  Recovery: This might have been caused by something like an input tray missing or an input tray empty. Look at the printer to determine the cause of the problem.

                  Note: If message CPA405C is received, the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPA405D "An output bin needs attention on device &1 (C R)" or
                  CPI405D "An output bin needs attention on device &1"
                  Cause: An error was detected on device &1.

                  Recovery: This might have been caused by something like an output bin missing or an output bin full. Look at the printer to determine the cause of the problem.

                  Note: If message CPA405D is received, the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPA405E "A printer supply needs attention on device &1 (C R)" or
                  CPI405E "A printer supply needs attention on device &1"
                  Cause: An error was detected on device &1.

                  Recovery: This might have been caused by the ink, toner, or developer being empty; the ink or toner receptacle being full; or the ribbon missing. Look at the printer to determine the cause of the problem.

                  This message has been seen when using a *LAN 3812 SNMP printer device description to print to a Sharp MX printer when the printer hardware is overdue for routine service maintenance, though this same situation could occur with printers from other manufacturers as well. In this case, the printer hardware is sending back a status code that there is an issue with the printer hardware and with a flag that says to not send a print job to the printer. The printer will need to be serviced before the *LAN 3812 SNMP printer device description can continue printing, but this can be circumvented by temporarily configuring a Remote Output Queue (RMTOUTQ) or a PC5250 or TN5250e printer session to route spooled files to the printer.

                  Note: If message CPA405E is received, the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPA405F "A paper path needs attention on device &1 (C R)" or
                  CPI405F "A paper path needs attention on device &1"
                  Cause: An error was detected on device &1.

                  Recovery: This might have been caused by something like a tray in the paper path missing or a bin full. Look at the printer to determine the cause of the problem.

                  Note: If message CPA405F is received, the Printer error message (PRTERRMSG) parameter in the *LAN 3812 SNMP device description should be changed from *INQ to *INFO. For more information, refer to the section Inquiry (CPA) Messages versus Informational (CPI) Messages above.


                  CPD401A "Could not establish SNMP communications with device &1"
                  Cause: Was not able to establish SNMP communications with device &1. The reason code is &2. The reason codes and their meanings are as follows:

                  1 - The device appears to be an SNMP device but not a printer.
                  2 - The device appears to be an SNMP device but does not support the required level of an industry standard SNMP protocol.
                  3 - Communication with the device timed out. This could occur because of heavy network traffic, the device is not an SNMP device, or the read community name set on the device is different than expected.
                  o Verify that both the printer and either the internal NIC card or external print server fully support SNMP.
                  o Verify that the internal NIC card or external print server has the SNMP community name set to Public.

                  Note: As of 6.1 PTF SI54993, 7.1 PTF SI50661, and the base code for 7.2 i5/OS, the SNMP system driver program will now attempt to connect with the printer using each community that is listed in the system SNMP configuration file, until it finds a community that is supported by the printer. If unable to access the printer community using any of these names, the SNMP system driver program will attempt one last time using the "public" community before failing with message CPD401A "Could not establish SNMP communications with device &1".

                  To update the community names in the configuration file, run the following Configure TCP/IP Applications (CFGTCPAPP) command:

                  CFGTCPAPP APP(*SNMP)

                  and take Option 2 (Work with communities for SNMP), then take Option 1 (Add) to add the community name used for your SNMP printer. The change will take effect the next time the writer for your *LAN 3812 SNMP printer device description is started.

                  Note: The IBM i SNMP code will accept any non-whitespace character that can be translated from the job CCSID to CCSID 500 and to ASCII CCSID 437 for the community name. Whether the receiving SNMP agent, such as the printer, supports the same set of allowable characters or the same ASCII CCSID will depend on the printer's implementation of SNMP. Meaning, some printers may accept special characters such as an exclamation mark ( ! ), ampersand ( & ), at sign ( @ ), but others may not. Please contact the printer manufacturer or visit their website to find out what restrictions might apply for the SNMP community name on their hardware.
                  o Verify that the timeout settings in the printer and print server hardware are not set too low. Refer to the section Recommended Timeout Settings for IBM, HP and Lexmark Print Servers at the top of this document for information on changing the timeout settings.
                  o Have the network administrator examine the firewall, SOCKS server, and any routers or switches, and have the system administrator verify the TCP/IP configuration on the IBM i system, to verify that the IBM i is able to communicate with the printer using both the port number specified in the *LAN 3812 SNMP device description and port 161, which is used for SNMP communications.

                  For example, the firewall may be blocking the specified port (often 9100) or port 161, particularly if trying to print across a Wide Area Network (WAN). SNMP communications use the TCP/IP port specified in the Port number (PORT) parameter, but it also uses port 161 for the initial connection. If the port specified in the PORT parameter is not blocked, but port 161 is blocked, it can result in message CPD401A with reason code 3.
                  o The SNMP print driver code might be back-level, and getting the latest PTFs might help resolve this problem. Refer to section Getting the Latest Print-Related TCP Fixes and PJL Driver Fixes at the bottom of this document for information on getting the latest PTFs.
                  Note: A TCP/IP communications trace or a sniffer trace may be needed to diagnose this further. For more information, refer to the following Software Knowledge Base document:

                  N1019135: Running a TRCCNN Trace for LAN Printing Problems


                  CPD337A "An error occurred while printing on device &1"
                  This error message indicates that the writer has ended unexpectedly. If this is occurring, check the following:

                  o Display the printer device description and verify that the Port number (PORT) parameter is not set to 0. This should typically be set to 9100 for most newer IBM Infoprint printers or 2501 for most older IBM Network Printer and Infoprint printers, 9100 for HP LaserJet with internal HP JetDirect cards (9100, 9101 or 9102 for multi-port external HP JetDirect print servers), and 9100 for Lexmark Optra printers with internal Lexmark Marknet cards (9100, 9101 or 9102 for multi-port external Lexmark Marknet print servers).

                  For a complete list of values to use for the Port number (PORT) parameter, refer to the following Rochester Support Center knowledgebase document:

                  N1019571: Recommended SNMP Port Number Values for *LAN 3812 SNMP Device Descriptions
                  o Display the printer device description and verify that the Inactivity timer (INACTTMR) parameter is not set to *NOMAX. This should typically be set to *SEC15, which means that the writer will end the connection to the printer 15 seconds after all RDY spooled files have been processed.

                  Setting this to *NOMAX will cause the writer to attempt to keep a permanent connection to the printer. This could prevent printing from other hosts on the LAN/WAN (including PCs, Microsoft Windows NT Servers and other IBM System i products) and could cause the writer to end if the connection is lost. Setting this to a large number, such as 10 - 30 minutes, could have similar results.
                  o Verify that the timeout settings in the printer and print server hardware are not set too low. Refer to section Recommended Timeout Settings for IBM, HP and Lexmark Print Servers at the top of this document for information on changing the timeout settings.
                  o The SNMP print driver code might be back-level, and getting the latest PTFs might help resolve this problem. Refer to section Getting the Latest Print-Related TCP Fixes and PJL Driver Fixes at the bottom of this document for information on getting the latest PTFs.
                  o Use the Configure TCP/IP (CFGTCP) command and select Option 4 (Work with TCP/IP port restrictions) to verify that there are no port restrictions blocking the port number specified in the Port number (PORT) parameter in the *LAN 3812 SNMP device description. If there is a port restriction, remove it, then end and restart the printer writer.
                  o The printer or something else on the LAN may be responding to a SYN (open connection) request with a RST (or Reset), which is a both a rejection of the open requestion and a request to drop the connection immediately. Collecting a TCP/IP communications trace using the Trace Connection (TRCCNN) command will show if something is responding back to the SYN request with a RST, but a collecting a TCP/IP communications trace using the Start Communications Trace (STRCMNTRC) command is required to determine whether the RST is being sent by the printer MAC address. For more information, refer to the following Software Knowledge Base document:

                  N1019135: Running a TRCCNN Trace for LAN Printing Problems

                  CPD337C "The session with device &1 ended abnormally"
                  This means that the socket connection could not be established. Ensure the port value is correct for the LAN adapter or printer. This error can be caused by having the port blocked by a firewall or SOCKS server, or by a router or switch. SNMP communications also uses port 161 for the initial connection, so have the network administrator examine the firewall, SOCKS server, and any routers or switches to verify that the port number specified in the *LAN 3812 SNMP device description and port 161 are not being blocked.

                  This error message can also be caused by disabling bidirectional communications on either the printer or the print server/network interface card (NIC).

                  Note: If message CPD337C is received but you are generally able to print through the *LAN 3812 SNMP device description, then verify that the *LAN 3812 SNMP device description is configured with the Inactivity timer (INACTTMR) parameter set to *SEC15, and the User-defined options (USRDFNOPT) parameter set to *IBMSHRCNN.

                  If message CPD337C is received when printing to an IBM Infoprint 1000, 1200, 1300, 1400 or 1500 Series printer or a Lexmark Optra printer, it could indicate that the Job Timeout in the printer hardware is set too low. If this is the case, disabling the Job Timeout by setting it to 0 should resolve the problem. Refer to the section Recommended Timeout Settings for IBM, HP and Lexmark Print Servers at the top of this document for information on changing the timeout settings.

                  Dot matrix and line matrix printers, such as the IBM 6400, IBM 4247 and IBM Infoprint 6500 printers, typically do not have timeout settings that can be changed. However, if message CPD337C is received when printing to a dot matrix or line matrix printer, then installing the latest firmware for the printer or network interface card (NIC) hardware might resolve the problem.

                  If message CPD337C is received when printing a large spooled file with the Starting page portion of the Page range to print (PAGERANGE) parameter in the spooled file attributes set to a large number, it could indicate that the timeout settings in the printer hardware are set too low. This has been seen with a *LAN 3812 SNMP device description when printing a 22000-page spooled file that had PAGERANGE(15000 15002) specified to an HP LaserJet printer that had the Idle Timeout set to 90 seconds. The SNMP print driver code had a performance issue, which was reported by APAR SE25841 OSP-LOOP-PRT SNMP DRIVER HANGS NO PRINTING SPOOLED FILE and fixed by R530 PTF SI24372 and R540 PTF SI25703. However, even after the problem was fixed by a PTF it took almost 90 seconds to process the spooled file, so the same thing could happen with either the IBM SNMP print driver code or the HP PJL print driver code if it had taken a little longer to process the spooled file (for instance if the system had been very busy at the time). Therefore, it is recommended to increase the Idle Timeout from the default value of 90 seconds to somewhere between 300 seconds (15 minutes) and 3600 seconds (1 hour), even after applying the PTF. Refer to the section Recommended Timeout Settings for IBM, HP and Lexmark Print Servers at the top of this document for information on changing the timeout settings.

                  If message CPD337C is received when printing to IBM 4049, Lexmark Optra R, Optra L, or Optra Lx printers, ensure the setting Advanced Status is turned on. This setting is found under the printer's Parallel Menu. According to the user's guide for the Lexmark Optra R, Optra L, and Optra Lx printers (which are equivalent to the IBM 4049 LaserPrinter), "if Advanced Status is set On, bidirectional communications is enabled through the parallel interface." The factory default is On, so normally bidirectional communications is enabled for these printers. The *LAN 3812 PJL OS/400 device descriptions require bidirectional communications, so turning the Advanced Status off would cause the *LAN 3812 PJL operating system device description to fail. Refer to the User's Guide for Lexmark Optra R, Optra L, and Optra Lx printers.

                  Message CPD337C can also be caused by having the Network Job Timeout set too low in a Lexmark printer. Setting the Network Job Timeout to the maximum value of 255 may still be too low, so this timeout should also be disabled by setting it to 0. The Network Job Timeout can typically be set through the control panel on the printer, or by using the Lexmark MarkVision Utility. The Lexmark MarkVision Utility can be downloaded from Lexmark's Web site, www.lexmark.com/.

                  Message CPD337C can also be caused by having the Job Timeout set too low in a Dell printer. Try setting the Job Timeout to the maximum value, or check to see if it can be disabled by setting it to 0. The Job Timeout can typically be set through on the control panel on the printer, under the System menu, or possibly by accessing the printer hardware settings by bringing up to the printer IP address or host name in a web browser.

                  Message CPD337C can also be caused by the printer or something else on the LAN responding to a SYN (open connection) request with a RST (or Reset), which is a both a rejection of the open requestion and a request to drop the connection immediately. Collecting a TCP/IP communications trace using the Trace Connection (TRCCNN) command will show if something is responding back to the SYN request with a RST, but a collecting a TCP/IP communications trace using the Start Communications Trace (STRCMNTRC) command is required to determine whether the RST is being sent by the printer MAC address. For more information, refer to the following Software Knowledge Base document:

                  N1019135: Running a TRCCNN Trace for LAN Printing Problems

                  If the writer occasionally ends with message CPD337C when printing to an IBM Infoprint 21 printer, it could indicate that the printer microcode is back-level. However if this is the case, changing some settings in the *LAN 3812 SNMP device description and in the printer hardware might help with the situation. Try the following:

                  1 Verify that the *LAN 3812 SNMP device description is configured with the Inactivity timer (INACTTMR) parameter set to *SEC15, and the User-defined options (USRDFNOPT) parameter set to *IBMSHRCNN.
                  2 Use the Web interface for the IBM Infoprint 21 Printer to set all of the timeout values (found under Administrator and Network Settings) to their maximum values.
                  3 Download and install IBM Infoprint 21 Printer Beta Controller Microcode Version 1.056007 (20 DEC 2001) or later. The printer microcode can be downloaded using the following URL links:

                  IBM Printing Systems Web site: http://www.printers.ibm.com
                  IBM Printing Systems Downloads Web page: http://www.printers.ibm.com/R5PSC.nsf/Web/download
                  Infoprint 21 Printer Beta Controller Microcode Version 1.056007 (20 DEC 2001): ftp://ftp.software.ibm.com/printers/products/netprt/microcode/21_007.exe
                  Note: Configuring the *LAN 3812 SNMP device description with the above settings and increasing the timeout values in the printer hardware will help with this problem; however, the problem is not completely resolved until the IBM Infoprint 21 printer microcode is upgraded to version 1.056007 or later.


                  CPD337D "No TCP/IP services available"
                  Cause: A request for Transmission Control Protocol/Internet Protocol (TCP/IP) service could not be completed for one of the following reasons:
                  o TCP/IP has not been started.
                  o One of the required control jobs has ended.
                  o The job default wait time was not long enough to allow the request to complete.

                  Recovery: If TCP/IP has not been started, start TCP/IP by using the Start TCP/IP ( STRTCP) command. Then, start the writer again using the Start Printer Writer ( STRPRTWTR) command.

                  If one of the control jobs has ended, see the messages listed in the job log to locate the cause of the error. Correct any errors, end TCP/IP using the End TCP/IP ( ENDTCP) command, restart TCP/IP by using the Start TCP/IP ( STRTCP) command, then start the writer again using the Start Printer Writer ( STRPRTWTR) command. If the problem continues, call the Rochester Support Center to report the problem.

                  If TCP/IP is already started and all the required control jobs are active, use the Change Job ( CHGJOB) command to increase the Default Wait (DFTWAIT) parameter for your job, and then start the writer again using the Start Printer Writer ( STRPRTWTR) command. This increases the amount of time allowed for TCP/IP to handle your request.


                  CPD337F "Remote device rejected an attempt by the writer to open a connection"
                  This error can occur for the following reasons:
                  1. An incorrect port number or TCP/IP address was specified in the printer device description.
                  2. The remote device, if it is a printer, might be busy printing from another host.
                  3. The remote device, if it is a printer, might not be ready to print and might require operator intervention.
                  4. The printer might have an error or informational message on the control panel, such as the following:

                  002 TONER LOW
                  INSTALL NEW TONER CARTRIDGE
                  This is a common error issued if the writer is trying to send data to the printer and the printer is unable to receive. This is normal in some configurations and will not cause a problem unless the device description activation timer expires before the printer is ready to receive the data again. Refer to the section on Timeout Settings in the OS/400 Printer Device Description for information on setting the activation timer.

                  Typical reasons for this error can include the following:
                  o The printer buffer might be filling up because it is being sent spooled files faster than it can print them. When this occurs, the writer waits and issues message CPD337F. Sometimes adding more memory to the printer can alleviate this problem. It is recommended that you increase the Activation timer if this is causing the writer to end.
                  o The printer is temporarily unavailable because it is out of forms, has a paper jam, is offline, is in power saver mode, and so on. There are some instances when the writer will not start because of the power saver, though getting the latest PTFs should resolve this problem. Refer to section Getting the Latest Print-Related TCP Fixes and PJL Driver Fixes at the bottom of this document for information on getting the latest PTFs. Otherwise, you should be able to get the writer to start by disabling power save mode on the printer.
                  o A duplicate TCP/IP address might exist. To test this, power off and/or uncable the printer or external print server from the network then prompt the Verify TCP/IP Connection (VFYTCPCNN or PING) command with the F4 key and type in the printer's TCP/IP address or host name, then press the Enter key. If the PING fails, then there is no duplicate TCP/IP address, but the if PING is still successful then another device has been assigned to another device in the network. Either the printer or the duplicate device must be given a new TCP/IP address.

                  Note: If the printer is given a new TCP/IP address, then the *LAN 3812 SNMP device description must be changed to specify that new TCP/IP address in the Remote location (RMTLOCNAME) parameter.
                  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. 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

                  Note: Replacing an existing printer might also require changing the configuration from using a *LAN 3812 SNMP device description to using a *LAN 3812 PJL device description or a Remote Output Queue. To determine whether a printer model is likely to work when printing from a System i using LPR, PJL, SNMP, IPP, or a PC5250 printer session, refer to the following Rochester Support Center knowledgebase document:

                  N1019605: Information on Printers from Various Manufacturers
                  o The printer does not support SNMP commands. Examples include most dot matrix or line printers, most ink jet printers, older laser printers and many recent laser printers. If the printer supports HP PCL5e or HP PCL6, there is a good chance, but no guarantee, that it will support SNMP, which is required for a *LAN 3812 SNMP device description.
                  o The print server does not pass SNMP commands to the printer. For a complete list of known print servers that support SNMP, refer to the following Rochester Support Center knowledgebase document:

                  N1019571: Recommended SNMP Port Number Values for *LAN 3812 SNMP Device Descriptions
                  o The print server may be configured with incorrect settings for the IP address, subnet mask, default gateway or host name. Check the network settings in the network interface card (NIC) or print server, and consult with your network administrator.

                  To test this, prompt the Verify TCP/IP Connection (VFYTCPCNN or PING) command with the F4 key and type in the printer IP address or host name, then press the Enter key, and PING the printer from a Windows PC that is in the same subnet as the printer. If the PING fails from the IBM i, but PING works from a Windows PC that is in the same subnet as the printer, then the default gateway or subnet mask are most likely set incorrectly.
                  o If a firewall or SOCKS server is set up or TCP/IP traffic is going through a router, particularly if trying to print across a Wide Area Network (WAN), the TCP/IP port specified by the Port number (PORT) parameter might be blocked. SNMP communications also uses port 161 for the initial connection, so have the network administrator examine the firewall, SOCKS server, and any routers or switches to verify that the port number specified in the *LAN 3812 SNMP device description and port 161 are not being blocked.
                  o The SNMP print driver code might be at a previous level, and getting the latest PTFs might help resolve this problem, particularly if running R430 (V4R3) or R440 (V4R4) OS/400. Refer to the section Getting the Latest Print-Related TCP Fixes and PJL Driver Fixes at the bottom of this document for information on getting the latest PTFs.

                  CPD338A "Cannot resolve to remote device name &1"
                  This message indicates that the local system cannot resolve the host name to a valid IP address. This can be caused by one of the following:
                  o Specifying an incorrect host name.
                  o Specifying a TCP/IP address with extra single quotes (such as ''9.10.46.254'' rather than '9.10.46.254').
                  o Specifying a TCP/IP address with leading zeros (such as '009.010.046.254' rather than '9.10.46.254').
                  o Specifying a TCP/IP address with extra blanks after the IP address (such as '9.10.46.254 ').
                  If using a host name, verify that the host name is a valid name and that it is typed correctly. Use the Verify TCP/IP Connection ( VFYTCPCNN or PING) command to verify that the host name can be successfully resolved to the correct TCP/IP address and that the printer or print server is able to communicate with the local system. If necessary, add the host name and its corresponding TCP/IP address to the local host table or to the host table on a DNS or DHCP server. Start the writer again using the Start Printer Writer ( STRPRTWTR) command.

                  If using a TCP/IP address, verify that the TCP/IP address is valid and that it is typed correctly. Use the Verify TCP/IP Connection ( VFYTCPCNN or PING) command to verify that the the printer or print server is able to communicate with the local system. Start the writer again using the Start Printer Writer ( STRPRTWTR) command.

                  Note: Message CPD338A or CPD338B may also be issued after a socket error.


                  CPD338B "No response from the remote name server for remote device &1"
                  This message indicates that remote name server did not respond to the local server's request to get remote device information.

                  Use the Configure TCP/IP (CFGTCP) command and take Option 12 (Change TCP/IP domain information) to verify that correct Domain name server IP addresses are specified, then check with the network administrator to verify that these servers are operational. Also, use the Verify TCP/IP Connection (VFYTCPCNN or PING) command to test the connectivity between the system and the Domain name server IP addresses.

                  Note: Message CPD338A or CPD338B may also be issued after a socket error.


                  CPD338C "An internal error occurred while sending or receiving data"
                  Cause: An internal error occurred while driver was attempting to send data to remote device or attempting to receive data from remote device.

                  Recovery: Use the Analyze Problem ( ANZPRB) command or call the Rochester Support Center to report the problem.


                  CPD338E "An error occurred while sending data"
                  Cause: A communications error occurred while sending data to remote device at RMTLOCNAME &2. The error code is &4.

                  Recovery: Start the writer again using the Start Printer Writer ( STRPRTWTR) command. If the problem continues, end TCP/IP using the End TCP/IP ( ENDTCP) command, start TCP/IP by using the Start TCP/IP ( STRTCP) command. Then, start the writer again.

                  If message CPD338E is issued with error code 3408 (or RC3408) on an IBM eServer i5 system running V5R3 i5/OS, download and apply PTF SI16132 or the latest superseding PTF for APAR SE17923 - OSP-MSGCPD338E SNMP DRIVER FAILS ANSWERING MSGCPA4002 WITH G REPLY. This problem can also be circumvented by answering message CPA4002 - Verify alignment on printer &3 with an I (Ignore) rather than with a G (Go).


                  CPD339A "An error occurred while trying to connect to device &1"
                  This indicates that the operating system cannot communicate with the printer or print server across the Local Area Network (LAN) or Wide Area Network (WAN). This can including attempting to print to a LAN attached printer that has not yet been assigned a TCP/IP address or when a TCP/IP route has not yet been configured to allow communication with a printer that is attached to another network.

                  Note: If writers fail with this message after an IPL or after coming out of Restricted State, such as for performing backups, then it is most likely that TCP/IP had not yet finished starting at the time that the writer was started. If this is the case, the issue can be resolved by modifying the QSTRUP source code to use the Delay Job (DLYJOB) command with the Job delay time (DLY) parameter set to 300 seconds (5 minutes) or 600 seconds (10 minutes), or some other value if desired, immediately prior to starting the QSPL subsystem. For more information, refer to the following document:

                  N1010213: Solution to Printer Writers Not Starting at IPL


                  CPD339B "An error occurred while transforming data"
                  Cause: The data transform program &1 in library &2 returned an error code of &3 while processing spooled file &4 number &5 in job &8/&7/&6.

                  Recovery: Report the problem to your system administrator or owner of program &1 in library &2.


                  CPD339C "The amount of data returned from the data transform program is not valid"
                  Cause: The data transform program &1 in library &2 returned &3 bytes of data in the Option Specific Output Information parameter of the Writer Transform exit program while processing spooled file &4 number &6 in job &9/&8/&7. (The documentation for this exit program is located in the System API Reference manual, SC41-5801.) The minimum number of bytes expected is &5.

                  Recovery: Report the problem to your system administrator or owner of program &1 in library &2.


                  CPF3330 "Necessary resource not available"
                  Cause: The system was not able to get the resource for your job in time.

                  Recovery: This indicates that a resource is not available and the writer appears to hang. A good circumvention is to change the default wait timeout on the writer. This can be changed by using the Change Class ( CHGCLS) command and then restarting the writer. For example, type CHGCLS CLS(QSPL) DFTWAIT(120) at an operating system command line and press the Enter key.


                  CPF6DF9 "Transformed data buffer too small"
                  Cause: This can be caused from using an incorrect Manufacture type and model value in the printer device description.

                  Recovery: The value must be a *LAN-supported laser printer. For example, because an HP500 printer cannot be configured as a *LAN printer device, using this value can cause this error message and end the writer.


                  TCP2617 "TCP/IP connection to remote system &2 closed, reason code &5" with RC2
                  Message TCP2617 with RC2 indicates that the remote printer is unreachable. The TCP connection was closed because the writer has attempted to contact the remote host several times and has reached the R2 retry threshold defined in the Change TCP/IP Attributes ( CHGTCPA) command.

                  If the messages are constant and contain the same TCP/IP address over and over again, then it is most likely that the writer is trying to print to a LAN attached printer that is down or off-line, though it also could indicate that the IP address has changed in the printer hardware. Ending or holding the writer will suppress the messages until the problem with the printer hardware has been resolved.

                  For more information on message TCP2617, refer to the following Rochester Support Center knowledgebase document:

                  N1016564: Message TCP2617
                  • - Additional Error Messages for *LAN SNMP Device Descriptions at R430 or R440



                    Other issues to consider when error messages are received:

                    CPF9898 "Could not establish SNMP communications with device <device-name>.
                    The device appears to be an SNMP device but is not a printer. Make sure that the device is a printer that supports the industry standard SNMP protocol and that the read community name is set correctly. Then try the operation again."

                    CPF9898 "Could not establish SNMP communications with device <device-name>.
                    The device appears to be an SNMP device but does not support the required level of an industry standard SNMP protocol. Make sure that the device is a printer that supports the industry standard SNMP protocol and that the read community name is set correctly. Then try the operation again."

                    CPF9898 "Could not establish SNMP communications with device <device-name>.
                    Communication with the device timed out. This could occur because of heavy network traffic, the device is not an SNMP device, or the read community name set on the device is different than expected. Make sure that the device is a printer that supports the industry standard SNMP protocol and that the read community name is set correctly. Then try the operation again."

                    • - Known Issues with *LAN 3812 SNMP Device Descriptions



                      This section discusses known issues with *LAN 3812 SNMP device descriptions that do not necessarily involve any specific error messages.

                      Font Changes in the Middle of a Spooled File
                      Some customers have seen problems where the font will change in the middle of printing a spooled file when using a *LAN 3812 SNMP device description. Setting the User-defined options (USRDFNOPT) parameter to *IBMSHRCNN appears to help with this situation. However, downloading and applying the latest recommended fixes may also be needed. For more information, refer to the Getting the Latest Print-Related TCP Fixes and Print-Related Fixes section below.

                      R430 and R440 OS/400 require PTFs to provide support for *LAN SNMP device description (see the attached cover letters for more details). To get the latest print-related TCP fixes and SNMP driver fixes for your operating system version, call the Rochester Support Center at 1-800-IBM-SERV and select the appropriate option or refer to the following documents. For more information, refer to the Recommended PTF Levels section below.

                      • - Recommended PTF Levels



                        There are no required PTFs in order to print using a *LAN 3812 SNMP device description; however, getting the latest Print Group PTF will typically help you avoid problems.

                        The IBM i Support: Recommended Fixes web page contains a list of recommended fixes for all systems and for specific products or functions for a given Version, Release, and Modification Level.

                        The Recommended Fixes web site is available at the following Web site:

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

                        Or, at a minimum you can download and install that latest Print Group PTF for your version of i5/OS:

                        PTF Number Licensed Program Version Description
                        SF99366 5770SS1 V6R1M0 710 Print Group PTF for V7R1M0
                        SF99356 5761SS1 V6R1M0 610 Print Group PTF for V6R1M0
                        SF99347 5722SS1 V5R4M0 540 Print Group PTF for V5R4M0
                        • - Checking and Changing the Size of the *SPOOL Pool



                          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 determine 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 and the Max Active settings for the *SPOOL pool. Starting in V4R5 OS/400, the pool size is specified in megabytes (M). Prior to V4R5 OS/400, the pool size was specified in kilobytes (KB).
                          2 Determine the *SPOOL pool size 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, Host Print Transform is usually being used. This increases the requirements for the *SPOOL pool. A good suggestion is to start with 5000K. The IBM® Redbooks™ 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.

                        Cross reference information
                        Segment Product Component Platform Version Edition
                        Operating System IBM i 7.2
                        Operating System IBM i 7.1
                        Operating System IBM i 6.1

                        Historical Number

                        19935220

                        Document information

                        More support for: IBM i
                        Print

                        Software version: 4.3.0, 6.1, 6.1.0, 6.1.1, 7.1, 7.1.0, 7.2, 7.2.0, Version Independent

                        Operating system(s): IBM i

                        Reference #: N1019570

                        Modified date: 13 April 2016


                        Translate this page: