Troubleshooting
Problem
This document provides a list of common IPDS sense data values that are received when printing to IPDS printers and the common causes and resolutions.
Resolving The Problem
A common error message when printing to an IPDS printer is PQT3630 - Device returned negative acknowledgment with sense data. The sense data in the message indicates what type of problem has occurred. There is usually a second message that follows the PQT3630 message that has a shorter version of the sense data. Some of the following messages are commonly seen with message PQT3630 in the joblog, though not all of the messages are seen at the same time:
Note: There can also be other messages in the job log that are not listed below.
PQT3072 - Error occurred while processing &8 separator page.
PQT3653 - Device &8 reported a command reject exception.
PQT3665 - Bar Code Specification Check exception at printer &8.
PQT3675 - Data stream exception at printer &8.
CPF3433 - Printing of file &4 by writer &1 not complete.
CPF3395 - File &4 held by the writer &1 on output queue &2 in &3.
PQT3621 - The session with device &8 ended abnormally. The reason code is usually 20.
This document was last updated on 5 March 2015.
Sense Data
The following are common sense data values that are returned by the printer. Both the long form (for example, X'08210100 DE000001 00000000 D6810000 00000000 00000001') and the short form (for example, X'0821' X'00' X'01') are provided here, when known. The following information is from the IPDS Reference (S544-3417-06) and from calls to the Rochester Support Center.
For a complete list of sense codes and their meanings, refer to the IPDS Reference publication, which is available at the following Web site:
http://publib.boulder.ibm.com/prsys/pdfs/54434176.pdf
-
X'01E41500' or X'01E4..00' (or X'01E4' X'15' X'00') on Ricoh IPDS Printers
Sense data X'0154..00' indicates that the Cancel key on the printer operator panel was pressed while the printer was receiving data.
This sense data has been received on a Ricoh color laser printer that has a built-in IPDS DIMM installed, though it might also be seen on B&W printers from Ricoh or on printers from Savin, Nashuatec, Rex-Rotary, Gestetner, Lanier, or Infotec if the same type of IPDS DIMM card is installed. In this particular case, the Ricoh IPDS printer was set up with user codes to track usage and to limit the number of users that are authorized to print in color. IBM® Print Services Facility™/400 (PSF/400) does not support sending these user codes to a printer, so this prevented the system from printing to that printer. The PSF writer attempted to print to that printer without providing the user codes, so the printer cancelled the print request by sending back a negative acknowledgement (NACK) with the X'01E4..00' sense data, which in turn caused the writer to issue message PQT3630 to report the sense data received from the printer hardware.
There is no support for user codes when printing through a *LAN *IPDS device description. Therefore, the user codes had to be disabled in the printer hardware to allow PSF/400 to print to the Ricoh color laser IPDS printer.
-
X'02000100 DE000001 00000000 D62D0000 00000001 00000001' or X'0200..01' (or X'0200' X'01' X'01')
This sense data means there is an undefined or unsupported control-sequence code in the data of a Write Text command. This is usually a communications problem with the device. It is usually an intermittent problem; if the spooled file is reprinted, it might print OK or it might fail in a different area. The resolution is to examine the network or the twinax cabling.
Another known issue that receives this sense data is documented in APAR SE06890. Spooled files are sent to the printer and the spooled files print, but the job separators do not. The writer does not end. The job separator is created with invalid data, which is why it does not print. This problem is fixed by R520 PTF SI05480 or its supersede.
APAR SE06890, OSP-MSGPQT3072 ERROR PRINTING JOB SEPARATOR
R520 PTF SI05480:
-
X'02130100 DE000001 00010000' or X'0213..01' (or X'0213' X'01' X'01')
This sense data means there is an invalid or unsupported Absolute Move Baseline (AMB). If the error happens when printing an overlay, it indicates the document has data outside the allowed area for creating an overlay. Ensure all data is within the allowed area for the overlay. Determine if a header or footer is specified in the document that is used to create the overlay. If so, reduce the size of the headers and footers or eliminate them.
-
X'02140100 DE000001 00000000 D62D0000 00000001 00000001' or X'0214..01' (or X'0214' X'01' X'01')
This sense data means that the printer reported an invalid or unsupported Absolute Move Inline (AMI). This problem has been encountered when printing through an IBM® iSeries™ NetServer™ printer share that uses the IBM AFP printer driver.
To resolve this problem, configure the IBM AFP printer driver to specify Print text as graphics. This causes the IBM AFP printer driver to create the spooled file with AFPDS image data rather than text data (which has text, fonts, and certain text controls such as the AMI control). The AMI control is not sent with AFPDS image data.
This sense data has also been encountered when doing a local print screen in iSeries Access for Windows and sending the output to an iSeries NetServer printer share that uses the IBM AFP printer driver. In this case, an alternative to changing the printer driver is to use the host print screen function to generate a spooled file directly on the operating system rather than using the local print screen function to print through an iSeries NetServer print share. For this option, please refer to the following document:
N1017258: iSeries Access for Windows: Adding the Host Print Screen Function to the PC5250 Tool Bar
-
X'02180100 DE000001 00000000 D62D0000 00000002 00000001' or X'0218..01' (or X'0218' X'02' X'01')
This sense data means that there is an invalid, unsupported, or unavailable font ID. Ensure the font library is added to the library list.
If IBM Infoprint Server is used, ensure the Capture host fonts at printer (FNTCAPTURE) parameter in the PSF Configuration Object is *NO because Infoprint Server has no way of capturing fonts. Fonts can be captured only in printer memory and only on certain models of IPDS printers. Refer to APAR SE03968.
APAR SE03968, OSP-MSGPQT3630-RC0218 IPDS TO PDF FAILS WHEN CAPTURE FONTS SPECIFIED
-
X'021D0100 DE000001 00000000 D63F0003 00000002 00000000' or X'021D..01' (or X'021D' X'02' X'01')
This sense data means that one or more of the parameters in the GRID field (bytes 5 through 12) for the Load Font Equivalence (LFE) command are invalid, unsupported, or inconsistent. The printer is reporting that it cannot print the fonts being requested of it. To resolve the problem, request fonts the printer supports or turn on Font Substitution on the printer.
-
X'023C0102' or X'023C..01' (or X'023C' X'02' X'01')
This sense data means there is an invalid or unsupported value in a Load Font Index command. Correct the problem with the font. If the printer is an IBM Infoprint 2085, contact the IBM Printing Systems Company for a printer microcode fix if there is no problem with the font.
-
X'02770100' or X'0277..01' (or X'0277' X'01' X'00')
This sense data means that an XOH-DGB command was received that attempts to terminate a group that is not yet initiated. This can be seen when using the DDS keywords STRPAGGRP and ENDPAGGRP to split the spooled file data into multiple groups. Verify the commands are placed in the appropriate order. For example, the ENDPAGGRP keyword is placed before the ENDPAGE keyword.
Note: This problem can also occur because of other technical inaccuracies in the programming of the page groups.
For additional information, refer to the following Rochester Support Center knowledgebase document:
N1017134: Using STRPAGGRP DDS with Infoprint Server Mail Function
-
X'027B0100 DE000001 00000000 D68F0000 00000001 00000002' or X'027B..01' (or X'027B' X'01' X'01')
This sense data indicates the IPDS feature installed in the printer sent back a negative acknowledgement (or NACK) that there was an Incorrect number of XOH-DGB triplet data bytes. This occurs with the R510 operating system and above when printing to an OEM printer (such as an HP LaserJet or Lexmark Optra) with an third-party IPDS DIMM or IPDS SIMM installed.
As of V5R1, the operating system allows the spooled file number to have an additional 2 digits (the maximum was 9999 in V4R5 and is now 999999). Print Services Facility/400 (PSF/400) was updated in V5R1 to send a Define Group Boundaries (XOH-DGB) IPDS command to each printer with a Format 13 triplet that is new to the V5R1 operating system. The Format 13 triplet was added to handle the 6-digit spooled file number. At least one IPDS printer looks at that triplet to display the spooled file information on the printer control panel as the spooled file is printing. All other printers should be ignoring it if it does not recognize that triplet or, as the IPDS Reference states: Printers ignore any triplets that are not supported, and no exception is reported.
The problem is that certain third-party IPDS DIMM and IPDS SIMM cards return a Negative Acknowledgement (NACK) rather than ignoring this triplet. That Negative Acknowledgement causes the writer to end with messages PQT3630 and PQT3073. The third-party IPDS SIMM was reporting the Negative Acknowledgement in error because it should have ignored any triplets that it did not support, as stated in the IPDS Reference.
This can generally be resolved by upgrading the firmware version in the third-party IPDS DIMM or IPDS SIMM, though in some cases the IPDS card might have to be replaced. This problem has been reported by APAR SE03759 and a workaround has been provided by R510 PTF SI03186 (or a superseding PTF), and it is in the base code for the R520 operating system.
Caution: This workaround was no longer to be in effect after R520, but it was again added to R530 through a PTF and added to the base code for R540. However, there is no guarantee that the workaround will remain in effect after R540. Therefore, any third-party IPDS DIMMs or IPDS SIMMs that respond incorrectly to the Define Group Boundaries (XOH-DGB) IPDS command with a negative acknowledgement (NACK) must be upgraded or replaced prior to upgrading to any follow-on release of the operating system. To test any IPDS firmware upgrades or IPDS DIMM/SIMM replacements, change the *LAN *IPDS device description to set the USRDFNOPT parameter from SPLF4 to *NONE. If the *LAN *IPDS device description continues to work properly after that, then the IPDS firmware upgrade or IPDS DIMM/SIMM replacement has been successful and the printer is ready to have the operating system upgraded beyond the R520 operating system.
After the necessary PTF has been applied (or if the system is already running the R520 or R540 operating system), then do the following:1 Vary off the printer device description. 2 On the operating system command line, type the following:
CHGDEVPRT DEVD(Printer_name) USRDFNOPT(SPLF4)
where Printer_name is the name of the printer device description. Press the Enter key.3 Vary on the printer device description.
This will cause the writer specify a 4-digit spooled file number rather than the 6-digit spooled file number. This step is documented in the cover letter for APAR SE03759 as well as the cover letters for R510 PTF SI03186 and all superseding PTFs. For more information, refer to the following APAR and PTF cover letters:
APAR SE03759, AF2 EC 027B0100 ON CERTAIN OEM PRINTERS AFTER R510 DUE TO INVALID DEFINED GROUP BOUNDARY NAC:
SI03186, AF2 EC 027B0100 ON CERTAIN OEM PRINTERS AFTER R510 DUE TO INVALID DEFINED GROUP BOUNDARY NAC:
-
X'02920100 DE000001 00000000 D67D0000 00000001 00000001' or X'0292..01' (or X'0292' X'01' X'01')
The sense data can also be returned as X'02920100 DE000001 00000000 D67D0000 00000001 00000004' or X'0292..01' (or X'0292' X'01' X'04').
This sense data means that an overlay was not activated or that it was deactivated prior to its attempted use. This is usually a hardware problem that is resolved by applying the latest firmware to the printer. In some cases, there were also hardware settings that were changed at the printer, such as maximizing the twinax timeout or disabling the Job Timeout (by setting it to 0) on a LAN attached IBM Infoprint IPDS printer or InfoPrint IPDS printer.
Contact the support for the printer for additional assistance.
Note: If the *LAN *IPDS device description does not have a PSF Configuration (PSFCFG) object specified in the User-defined object (USRDFNOBJ) parameter, then this problem might be resolved by creating a PSFCFG object with the Release timer (RLSTMR) parameter set to *SEC15 and the Resource retention (RSCRET) parameter set to *NO. Then specify that PSFCFG object in the USRDFNOBJ parameter in the *LAN *IPDS device description. If a PSFCFG object is already specified in the *LAN *IPDS device description but it does not have RLSTMR(*SEC15) and RSCRET(*NO) specified, then end the writer, change the PSFCFG object to use these settings, restart the writer, and see if that resolves the problem.
-
X'040B00' or X'040B..00' (or X'040B' X'00')
This sense data means that there is an invalid or unsupported bar code modifier. To resolve the problem, correct the bar code modifier.
Example:
A CODE128 bar code fails to print to an IBM 4247 when used with the bar code modifier '01'. The DDS BARCODE keyword is specified as follows:
BARCODE(CODE128 2 *HRITOP *HRZ A (*WIDTH 0.1) (*RATIO 2) X'01')
When the X'01' bar code modifier is removed, the bar code prints. The DDS BARCODE keyword documentation states the following about the CODE128 bar code: The value 01 for the bar code modifier is not valid for some printers.
-
X'04110100 DE010001 00000000 D6810101 01010000 00000001' or X'0411..01' (or X'0411' X'00' X'01')
The sense data returned can also be X'04110100 DE070001 00000000 00000000 00000000 00000001'. According to the IPDS Reference, the sense data of X'0411'.. X'00'.. X'01' indicates that the bar code is attempting to print outside of the printable page area. This is usually resolved by doing one of the following:o Position the bar code away from the paper edge so it does not try to print off the page. o Turn on the edge-to-edge feature in the printer hardware. IPDS printers often refer to this setting as the "Printable Area" but other terms may be used, particularly when using a printer from a manufacturer other than IBM Printing Systems or InfoPrint Solutions Company.
For example, the IBM Infoprint 1125 printer, when it has the Printable Area set to 4028 Whole Page, will print with a 4 millimeter or 50 pel unprintable area on all four sides, and anything that tries to print beyond that will be truncated. However, when it comes to bar codes, the printer will send back a Negative Acknowledgement (NACK) rather than truncating part of a bar code. That is why message PQT3630 is issued in the writer job log.
If printing to an IBM Infoprint 1XXX Series IPDS printer or to an IPDS printer from InfoPrint Solutions Company, try setting the Printable Area to Full Page in the printer hardware, which formats the page for edge-to-edge printing, to see if that resolves the issue. By setting the Printable Area to Full Page, PSF/400 will format the page to not have an unprintable border, so the printer hardware will most likely compress the print image by 2% in both the horizontal and vertical directions to prevent it from actually printing the bar code to the paper edge.
Note: Some printers do not have this option, but might have other hardware options available. For example, the IBM Infoprint 62 IPDS printer has the option to set the Horizontal/Vertical positions for the Green-bar form type to "30/0" and to set the Green-bar form type to use a Media type of "Paper."o There are a few new problems with printing bar codes at V5R1M0. One problem is that the height of the bar code is incorrectly calculated (so that it prints the length of the whole page). There is another problem when specifying several bar codes on the page that they are incorrect. These problems are resolved by applying PTF SI02325 or its supersede.
Note: This does not correct the problem on existing spooled files; therefore, a new spooled file must be generated after applying the PTF.o The attributes of the spooled file do not correctly specify the page size (length, width, lines per inch, and characters per inch) for the paper being used (for example, the page is created too small). Change the printer file (CHGPRTF) or override the printer file (OVRPRTF) to specify the correct page size attributes and create a new spooled file. o The bar code is printing larger than expected after an upgrade to R520. There was a bug at the earlier releases that if *WIDTH was not specified for the bar code, then the system was sending X'00' for a width rather than X'FF'. X'00' is actually not even a value width parameter, but it appears that most printers will print with the smallest supported width in this case. That bug has been fixed at R520. The X'FF' width is sent down, and the bar code prints larger. The resolution is to set the width (*WIDTH) in the DDS. For some of the bar code specifications, the height was not specified. To ensure the height is correct, use the height parameter also.
Example: Using the *WIDTH parameter with the BARCODE keyword:
BARCODE(CODE3OF9 2 *NOHRI (*WIDTH 0.007) (*RATIO 2) X'01')
BARCODE(CODE3OF9 2 *HRI (*WIDTH 0.007) (*RATIO 2) X'01')o The DDS field is set up incorrectly. To resolve the problem, correct the DDS.
Example:
The DDS is set up with a length of 50 characters, and all but the first 10 characters are set to blanks. All 50 characters will attempt to print. Only the first 10 characters are the ones that the user wants to print, so it is positioned on the page accordingly. The bar code now extends beyond the edge of the page. In this case, the problem is resolved by changing the DDS field to be 10 characters long.
-
X'04110100 DE070001 00000000 00000000 00000000 00000001' or X'0411..01' (or X'0411' X'00' X'01')
Refer to the sense data X'04110100 DE010001 00000000 D6810101 01010000 00000001' or X'0411' X'00' X'01, which is listed previously.
-
X'08210100 DE000001 00000000 D6810000 00000000 00000001' or X'0821' X'00' X'01' (or X'0821' X'00' X'01')
This sense data means that there is a problem with the bar code. The common causes are:
To resolve the problem, correct the bar code.o An undefined character has been detected in the WBC command bar code data. o An undefined character has been detected in the font specified for text, bar code HRI, or graphics character-string data. o A character has been detected in the Write Text command data, which is undefined at the quality level specified by the XOA PQC command.
-
X'40001A00 00020000 00000000 00000000 00000000 00000000' or X'0400..1A' (or X'0400' X'00' X'1A')
This sense data means that the printer is not ready.
If Infoprint Server is used, however, this could mean that there is a problem with the PSF Configuration (PSFCFG) object. For example, an Integrated File System directory name is specified as all lowercase characters in the PDF directory (PDFDIR) parameter in the PSFCFG. The actual Integrated File System directory name is in mixed case characters. The Integrated File System directory names and the PDFDIR parameter are case sensitive. The problem is resolved by changing the PDFDIR parameter in the PSF Configuration (PSFCFG) object to match the Integrated File System directory name.
Note: The Infoprint Server product creates subdirectories within the Integrated File System directory based on the job name specified in the attributes of each spooled file. Therefore, the PDF file will never be in the directory specified in the PDFDIR parameter but should be found in one of its subdirectories.
-
X'800200' or X'8002..01' (or X'8002' X'00' X'01')
This sense data means that there is an invalid or unsupported IPDS command sequence. It is usually an intermittent problem; if the spooled file is reprinted, it might print OK or it might fail in a different area. This is usually a communications problem with the device; the resolution is to examine the network or the twinax cabling.
This can also be caused by incorrect usage of the DDS keywords. To resolve this problem, correct the usage of the DDS keywords.
Recommended Fixes (PTFs)
For a list of the latest print-related PTFs, refer to the Recommended Fixes Web site, which is available at:
http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes
References
Refer to the following Rochester Support Center knowledgebase documents:
N1019439: Configuration Settings and Error Messages for *LAN IPDS Device Descriptions
N1017134: Using STRPAGGRP DDS with Infoprint Server Mail Function
Refer to the following publications:
IPDS Reference (S544-3417-06) publication, which is available at the following Web site:
http://publib.boulder.ibm.com/prsys/pdfs/54434176.pdf
System i Programming DDS for Printer Files publication, which is available at the following Web sites::
Infoprint 1120, 1125, 1130, 1140, and 1145 Card for IPDS and SCS/TNe IPDS Emulation User's Guide (S510-2156-00), which is available at the following Web site:
http://publib.boulder.ibm.com/prsys/pdfs/51021560.pdf
Historical Number
395610872
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1019056