IBM Support

Configuration Settings and Error Messages for Infoprint Server IPDS-to-PDF Transform

Troubleshooting


Problem

This document contains information on configuration settings and error messages for *LAN *IPDS device descriptions that use Infoprint Server to convert spooled files to PDF format.

Resolving The Problem

This document contains information on configuration settings and error messages for *LAN *IPDS device descriptions that use Infoprint Server to convert spooled files to Adobe Acrobat PDF format. The term IBM® IPDS™ refers to IBM®'s Intelligent Printer Data Stream™. IPDS allows for two-way communication with the printer and supports advanced printing functions such as bar coding, overlays, page segments, and downloadable fonts. IPDS printer can be used to print Advanced Function Printing Data Stream or *AFPDS spooled files, in addition to *IPDS spooled files, when configured to use IBM® Print Services Facility™/400 (PSF/400).


Configuring an Infoprint Server *IPDS Device Description
Configuring a *LAN IPDS Device Description for E-Mail Function of Infoprint Server
Configuring a *LAN IPDS Device Description to Use Infoprint® Server to Convert a SPLF to PDF and Store it in the IFS


Recommended Fixes
It is recommended that the latest recommended fixes for Print and Infoprint Server be applied.  Not all PTFs are on the cumulative PTF package, which requires a separate order for the recommended fixes
Three jobs start for a LAN IPDS device configured for use with Infoprint Server:
Type PDJ (Print Driver Job)
Type BATCH
Type WTR  (Writer)
Check all three jobs for error messages.

Error Messages for *LAN IPDS Device Descriptions Configured for use with Infoprint Server:

Note: This list of error messages is not all inclusive. If you receive an error message that is not listed here, contact the IBM i Global Support Center for further support.
Infoprint Server, product 5722IP1 product option *BASE and product option 1 for Transform Manager are licensed products.  A licensed key is no longer required. 

These three messages have been seen together when using a PDF mapping program:
Message CPD9028 - Not authorized to change document profile values.
Message
 CPF9027 - Change request for QSPLJOB not successful.
Message CPF9099 - Document description not changed.

The messages were resolved by adding user QSPLJOB to the QPQSPLJOB authorization list with *ALL authority.
WRKAUTL AUTL(QPQSPLJOB)
Select option 2=Edit
Add user QSPLJOB to the list with *ALL Object Authority and specify X in the List Mgt column
Press <ENTER>


Message CPFA093 - Name matching pattern not found.
If this message is received when using a PDF mapping program, ensure the authority is changed on the PDF before it is renamed.

Message CPFA09E - Object in use.  Object is <PDF File Location>.
The PDF file creation includes the following steps:
1    The PDF file is created.
2    The Owner of the Stream file is changed.
3    The *PUBLIC authority of the object is changed.
CPFA09E indicates that something is locking out the PDF file between Steps 1 and 2.  This is caused by an error in the PDF exit program.  It can also be caused by customer software outside the PDF writer process that accesses the PDF file before steps 2 and 3 are completed.
 

Message CPFA0A0 - Object already exists.  Object is &1.
Object is a specific IFS directory that is larger than 2GB.
Refer to APAR SE75051 for additional information.  Apply the latest recommended fixes for Print and Infoprint Server

Message CPFA0B1 - Requested operation not allowed.  Access problem.
User profile QSPLJOB must have sufficient authority to the directories, including work and temporary directories.  
From the Infoprint Server User Guide (S544-5775):
QSPLJOB must have change (*RWX) authority to root ('/'). 
If the PDF is going to be stored as a stream file, QSPLJOB needs at least execute (*X) authority to every directory in the path. It also needs change (*RWX) authority to the directory that will contain the PDF files (the parent directory). For example, if you want the PDF files put in directory3, which is in this path: /directory1/directory2/directory3, QSPLJOB needs *X authority to directory1 and directory2 and *RWX authority to directory3.  
Additionally, if the directory that will contain the PDF files is assigned a Primary group, QSPLJOB must also have delete authority to the group profile.          

Message IPS5066 - TCP/IP error for device &2, port &1, printing terminated.
Error codes:
01 Create socket   
02 Bind to socket  
03 Read from socket
04 Write to socket.
Error code 24 is also possible, which refers to an issue with the port number.
Change the port number in the IPDS device description to a different port. 


Message IPS512C:   Creation of temporary PDF output file for device &2, port &1  failed, processing of spool file terminated.
Reason codes:
21 Security violation
24 Unspecified error
The message is issued in the BATCH job.
Reason code 22 is also possible, which maps to an error number (errno) EBUSY and file is locked error.
Change the port number in the IPDS device description to a different port.

Message IPS512D:  Renaming of temporary PDF output file for device <DeviceName>, port <PortNumber> failed, printing incomplete. 
Reason codes
17 Target file already exists
19 Path is invalid
21 Security violation
23 Undocumented, but could be the same as reason code 21
24 Unspecified error
The message details will identify the path and name of the PDF file.
For reason code 17, a PDF file of the same name already exists in the directory.  Change the directory path or name of the PDF file.
For reason code 19, investigate the path where the PDF will be stored.  Ensure that the PDF file name fits within the limits of the directory it is being stored.  For example, if the PDF is being stored in /QDLS, the file name can be no longer than 8 characters, plus the file extension.
For reason code 21, ensure that user QSPLJOB has proper authority to the directory path in which the PDF is being stored.  Per the Infoprint Server for iSeries User's Guide, G544-5775-02: http://publibfp.boulder.ibm.com/epubs/pdf/54457754.pdf, Chapter 4. Using the PDF Subsystem:
QSPLJOB Authority Requirements
If you are going to store the PDF file in the integrated file system, before transforming to PDF, ensure that QSPLJOB has these authorities:
  • QSPLJOB must have change (*RWX) authority to root ('/').
  • If the PDF is going to be stored as a stream file, QSPLJOB needs at least execute (*X) authority to every directory in the path. It also needs change (*RWX) authority to the directory that will contain the PDF files (the parent directory).  For example, if you want the PDF files put in directory3, which is in this path: /directory1/directory2/directory3, QSPLJOB needs *X authority to directory1 and directory2 and *RWX authority to directory3.
For reason code 23, ensure user QSPLJOB has proper authority to the path listed in the message details, but also to the PDF directory specified in the PSF configuration object.  For example, if the PSF configuration object being used with the Infoprint Server printer device description is configured to create a PDF stream file in directory /ABC, ensure that user QSPLJOB is authorized to this directory and all subdirectories too.
For reason code 24, review the causes for the other reason codes.  Contact IBM i support for further assistance with problem determination.

Message IPS512E:   Unable to create directory for PDF output for device &2, port &1, printing terminated.
Reason codes:
22 Security violation  
23 Directory is invalid
24 Unspecified error   
The message is issued in the BATCH job.
For reason codes 22 and 24:
User profile QSPLJOB must have sufficient authority to the directories, including work and temporary directories.  
From the Infoprint Server User Guide (S544-5775):
QSPLJOB must have change (*RWX) authority to root ('/'). 
If the PDF is going to be stored as a stream file, QSPLJOB needs at least execute (*X) authority to every directory in the path. It also needs change (*RWX) authority to the directory that will contain the PDF files (the parent directory). For example, if you want the PDF files put in directory3, which is in this path: /directory1/directory2/directory3, QSPLJOB needs *X authority to directory1 and directory2 and *RWX authority to directory3.  
Additionally, if the directory that will contain the PDF files is assigned a Primary group, QSPLJOB must also have delete authority to the group profile.    
For reason code 23:
Correct the directory name.


Message PQT1002 - Internal system failure detected by printer writer for device
The owner of the spooled file may not be authorized to all resources necessary to print the file. Or, the user may not be authorized to the library in which the resources reside. This message may be preceded by message PQT2001: Internal system failure occurred.

Message PQT1053 - IPDS to PDF transform job not run.
 Reason codes:
  1 - No PDF exit program is registered for exit point name QIBM_QPQ_TRANSFORM and exit point format name XPDF0100 with program data of  "IPDS    PDF".
  2 - None of the programs registered for exit point name QIBM_QPQ_TRANSFORM and exit point format name XPDF0100 with program data of "IPDS    PDF" are available to PSF. Please see previous messages in job logs for the programs that can not be found. 
  3 - The PDFDIR value in the PSF configuration object associated with device &8 identifies a directory that does not exist. 

 For reason codes of 1 and 2, use the ADDEXITPGM to register a program that is available for exit point name IBM_QPQ_TRANSFORM and exit point format name XPDF0100 with program data of "IPDS      PDF" and start the writer   again.                                                                      
For reason code 3, use the CHGPSFCFG command to change the PSF configuration object associated with device &8 to use a directory in PDFDIR that exists.
Refer to Infoprint Server User Guide (S544-5775) Appendix D. Exit Points for more detail.
1.  Verify if the QIPSINIT program exists:  WRKOBJ OBJ(QIPS/QIPSINIT)
2.  WRKREGINF EXITPNT(QIBM_QPQ_TRANSFORM)
3.  Select option 8=Work with exit programs
4.  There should be only one XPDF0100 exit point format listed.  
​
  Exit                               
Program     Exit                     
 Number     Program        Library   
   9974     QIPSINIT       QIPS      

​
5.  If there are any other exit programs before QIPSINIT, select option 4=Remove to delete it.  
If the QIPSINIT exit program does not exist, select option 1=Add to add it, or issue the ADDEXITPGM command to add it:
Note:  The program data is case-sensitive and space-sensitive.  There must be four spaces between 'IPDS' and 'PDF' in the Program data parameter.  
    Exit point . . . . . . . . . . . > QIBM_QPQ_TRANSFORM
    Exit point format  . . . . . . . > XPDF0100
    Program number . . . . . . . . . > 9974
    Program  . . . . . . . . . . . . > QIPSINIT
      Library  . . . . . . . . . . . >   QIPS
    Threadsafe . . . . . . . . . . . > *NO
    Multithreaded job action . . . . > *MSG
    Text 'description' . . . . . . . > 'Infoprint Server PDF'
    Exit program data:
      Coded character set ID . . . . > 37
      Length of data . . . . . . . . > 11
      Program data . . . . . . . . . > 'IPDS    PDF'
-OR-    
    ADDEXITPGM EXITPNT(QIBM_QPQ_TRANSFORM) FORMAT(XPDF0100) PGMNBR(9974)
               PGM(QIPS/QIPSINIT) THDSAFE(*NO) MLTTHDACN(*MSG)
               TEXT('Infoprint Server PDF') REPLACE(*NO)
               PGMDTA(37 11 'IPDS    PDF')

                                                                        
It is possible the exit point or the program is corrupted.   Ensure the Recommended Fixes for Infoprint Server are applied, which includes the latest code for QIPSINIT program.

Message PQT2001 - Internal system failure occurred
The owner of the spooled file may not be authorized to all resources necessary to print the file. Or, the user may not be authorized to the library in which the resources reside. This message may be followed by message PQT1002: Internal system failure detected by printer writer for device.
 

Message PQT3621 - The session with device &8 ended abnormally
If the return code is 20 - 39, then this error message indicates that a communications failure occurred. If the return code is 40 - 59, then this indicates that an internal failure occurred.
 

Message PQT3624 - The session with device &8 was ended
This error message indicates that the session with the printer device was ended by the writer because the device did not respond within the time specified by the Printer response timer (PRTRSPTMR) parameter in the PSF Configuration (PSFCFG) object. The PRTRSPTMR parameter in the PSFCFG object defaults to *NOMAX, but can be set to any value from 5 to 3600 seconds (or 1 hour). If currently set to 5 seconds, end the writer and try increasing the PRTRSPTMR parameter to somewhere between 60 seconds (1 minute) and 180 seconds (3 minutes) and test to see if that resolves the problem.


Message PQT3625 - Connection with device &8 is being retried.
Error codes:
    15:      The activation timer (ACTTMR) value configured for the device expired before the device was available.     
      - Consider increasing the value for ACTTMR in printer device description (CHGDEVPRT) in order to reduce the number of retries.                        
    22:      The device did not respond to a connection request.
      - The device may be temporarily unavailable or it is disconnected from the network. If the device is temporarily unavailable, you  may not have to take any action.                                                     
    20-39:   A recoverable communications failure occurred.               
Verify that LOOPBACK is ACTIVE on the system.
     CFGTCP
     Select option 1. Work with TCP/IP interfaces
     Press F11=Display interface status and verity the Interface Status is ACTIVE

Verify that there is not a duplicate host table entry for the system.
     CFGTCP
     Select option 10. Work with TCP/IP host table entries
     Review the Host Name column to verify there is not a duplicate host table entry


Message PQT3002 - The connection to device &3 has been released.
This error message indicates that the session with the device ended because the release timer (RLSTMR) expired.
It is not recommended to set a release timer for the Infoprint Server device description as this releases the port the device uses and another device or process can use the port.
Change the RLSTMR to *NOMAX in the PSF configuration object.

Message PQT3075 - Printer or communications error detected for device &8. Print driver job ended.
This error message indicates that a printer error or communications error has been detected, and that this resulted in the writer ending abnormally. This message is usually preceded by another message, such as message PQT3621, The session with device &8 ended abnormally.


Message PQT3076 - Print driver job for device &8 ended because of an error.
This error message indicates that an error occurred and that it resulted in the writer ended abnormally. This message is usually preceded by another message, such as message PQT3075 - Printer or communications error detected for device &8. Print driver job ended. and message PQT3621, The session with device &8 ended abnormally.

Message PQT3291 - Immediate program end for device.
Message PQT3291 is typically preceded by another message.  Review the job logs for another error message.


Message PQT3523 - Structured field &17 is missing
Message PQT3502 - Structured field &17 is not allowed or forms a sequence that is not valid.
These error messages indicate that a structured field in the AFPDS printer data stream is incorrect. This is usually caused by a problem in the application that generated the *AFPDS spooled file.


Message PQT3630 - Device &8 returned negative acknowledgment with sense data.
This error message indicates that the printer returned a negative acknowledgement (or NACK) to the writer. This is either caused by a problem in the AFPDS data stream.  The sense data in the message indicates what type of problem has occurred.

When message PQT3630 is received, it is usually accompanied by a second message that provides additional information about the problem, including a shorter version of the sense data. The most common messages received with message PQT3630 are:

PQT3073 - Error detected while processing spooled file. Processing of the print request ended.
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 following document provides a list of common IBM® IPDS™ sense data values that are received  and the common causes and resolutions:

IPDS Sense Data for PQT3630 Messages

Note: If the sense data is not listed in IPDS Sense Data for PQT3630 Messages, refer to the Intelligent Printer Data Stream Reference, S544-3417-06, manual instead. 


Message PQT3665 - Bar Code Specification Check exception at printer &8
This error message indicates that the printer detected a data value in the bar code data that was either not valid or not supported. The sense data provides additional information about the problem. The various sense data values are listed in the Intelligent Printer Data Stream Reference, S544-3417-06.

The most common sense data returned for bar code errors is X'04110100 DE010001 00000000 D6810101 01010000 00000001' (or the short form is X'0411'..X'00' X'01'). The IPDS Reference information on this sense data 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 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.

Message PQT4139 - Cannot connect to mail servers specified for device &1. (C R)
Per document Message PQT4139 Issued for Infoprint Server Writer, if the PDF Mail Server in the PSF configuration object is set to *LOCAL, the TCP/IP host table for the system must contain both the short and long names for the system. 

If the host table entry is correct, SMTP and/or MSF may not be active:
STRTCPSVR SERVER(*SMTP)
STRMSF
Infoprint Server will not work with a third-party SMTP server.  It will use native SMTP support.  Thus, native SMTP must be configured and cannot conflict with the third-party SMTP server.  Message PQT4139 can be issued if the native SMTP server and the third party SMTP server are conflicting.  An example would be that both the native and third-party SMTP servers configured with the same IP address and using port 25.                                                
                                                                      
The resolution is to bind the native SMTP server to one IP address and the third-party SMTP server to another.   Contact our Electronic Business and Web Serving team for assistance with binding the SMTP server(s) to a specific IP address.    
If message PQT4139 is received after changing the IP address of the system or server, ensure that the SMTP attributes are updated to specify the fully qualified domain name (FQDN) of the mail server for the Forwarding mailhub server parameter:

CHGSMTPA FIREWALL(*NO) FWDHUBSVR('FQDN of the mail server')

If there are errors, remove FIREWALL(*NO) from the command:    
CHGSMTPA FWDHUBSVR('FQDN of the mail server')

End and restart SMTP and MSF, either resetting or clearing mail messages:
ENDTCPSVR SERVER(*SMTP)
ENDMSF
STRTCPSVR SERVER(*SMTP)

Restart MSF with either *RESET or *CLEAR mail messages option:
NOTE:  *CLEAR option will clear all unsent mail
STRMSF MSGOPT(*RESET)
  -OR-

STRMSF MSGOPT(*CLEAR)

If still failing, collect an SMTP trace and contact our Electronic Business and Web Serving team for further analysis:

SMTP Trace:
1) ENDTCPSVR SERVER(*SMTP)
2) TRCTCPAPP APP(*SMTPCLT) TRCFULL(*STOPTRC)
3) STRTCPSVR SERVER(*SMTP)
**Assuming a software case has been opened, if not replace the TOINTNET email address with another:

4) SNDDST TYPE(*LMSG) TOINTNET((ibmi_support@ecurep.ibm.com<ibmi_support@ecurep.ibm.com>)) DSTD(CaseNumber) LONGMSG('Testing for <CaseNumber>.')
5) TRCTCPAPP APP(*SMTPCLT) SET(*OFF) TITLE('Outbound E-mail')
6) Locate the output:
     WRKJOB and select option 4. Work with spooled files to locate the spooled files named QTMSSTRCxxxxx



Message PQT4140 - Incorrect data was returned by mapping program (&1/&2).
This message is received when using a custom PDF mapping program.
Reason codes:
  1  -- Incorrect value for Disposition of PDF e-mail.                      
  2  -- Incorrect value for More processing.                                
  3  -- A Reserved field does not have each byte set to X'00'.              
  4  -- Length of message text must be 0-255 when PDF mail server is SNDDST.
  5  -- Length of mail address must be 0 when Disposition of PDF e-mail is '0'.
  6  -- CCSID must be 0 when using SNDDST for e-mail.
  7  -- Length of Extension area must be 52 or 110.
  8  -- Length of subject must be greater than 0 when Offset to subject is greater than 0.
  9  -- When using SNDDST, all fields for specifying ReplyTo, CC, BCC, body files, attachments and directory names must be
           0.
  10 -- BCC offset and BCC length are not compatible.
  11 -- CC offset and CC length are not compatible.
  12 -- REPLYTO offset and REPLYTO length are not compatible.
  13 -- REPLYTO offset must be equal to or greater than 0.
  14 -- Use of path directory specified, but no path directory was entered.
  15 -- Disposition of PDF Error is set to 1, Do not continue processing.
  16 -- Incompatible values specified for Offset to PDF file public authority and Length of PDF file public authority.
  17 -- Incorrect value for Public authorization. Valid values are *EXCLUDE, *ALL, *RWX, *RX, *RW, *WX, *W, *R, and *X.
  18 -- Incompatible values specified for Offset to PDF stream file path and file name and Length of PDF stream file path and
            file name.
  19 -- Incompatible values specified for Offset to spooled file PDF distribution  and Length of spooled file PDF distribution.
  20 -- Values for Offset to PDF file name for e-mail and Length of PDF file name for e-mail are not compatible. One value is 0
            but the other value is not 0.
  21 -- Length of PDF encryption information cannot be less than 0. 
  22 -- Incorrect value for Disposition of PDF error.
  23 -- Incorrect value for Disposition of PDF stream file.
  24 -- Incorrect value for Disposition of PDF spooled file.
  25 -- Message text must be blank when Length of message text is 0.

PDF mapping programs are outside the scope of support provided by the IBM i Global Support Center.  To debug your PDF mapping program, refer to the section titled Specifying Directory Authorities and Troubleshooting Mapping Programs in document Finding Additional Information for IBM Infoprint Server and PDF Mapping Exit Programs

Assistance with custom PDF mapping programs can be offered through IBM i Customized Services or Lab Services.



Message CPF3330 - Necessary resource not available
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 through the CHGCLS command, then restart the writer. An example is CHGCLS CLS(QSPL) DFTWAIT(120), to be entered at the command line.
 

Message MCH3601 - Pointer not set for location referenced
You should not get this message. Getting the latest PTFs should resolve this problem. Refer to section Getting the Latest Print-Related TCP Fixes and PSF/400 Fixes at the bottom of this document for information on getting the latest PTFs.


Message MCH5601 - Template value not valid for instruction.
From Program . . . . . . . : PpPaseMIInterface
To module . . . . . . . . . : QP2LOAD
- Followed by -
Message CPFB9C8 - File descriptors 0, 1, and 2 must be open to run the PASE for i program.
From module . . . . . . . . : QP2LOAD
To module . . . . . . . . . : QXJ9STRTPA
The QIBM_USE_DESCRIPTOR_STDIO environment variable is Y and needs to be set to N for the Infoprint Server device writer to start.
Use WRKENVVAR LEVEL(*JOB) -or- WRKENVVAR LEVEL(*SYS)
Locate the QIBM_USE_DESCRIPTOR_STDIO variable
Select option 2=Change and specify the New Value as 'N' and press <ENTER>

Other Infoprint Server Failures

This section provides information on other things to check when Infoprint Server is failing, but there aren't necessarily any error messages to be found.

Emailing through Infoprint Server works when using PDF mail server as *SNDDST (SNADS), but not when using *LOCAL or an external mail server (SMTP):
If Infoprint Server works when configured to use the PDF mail server name (PDFMAILSVR) parameter as *SNDDST, but does not work when using *LOCAL or external mail server, change the SMTP attributes to Allow relay as *ALL:
CHGSMTPA ALWRLY(*ALL)
Then end and restart the SMTP server:
ENDTCPSVR SERVER(*SMTP)
STRTCPSVR SERVER(*SMTP)

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CUEAA2","label":"Print-\u003EPDF Infoprint Server-\u003EInfoprint Server 5722IP1"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0;7.1.0;7.2.0;7.3.0;7.4.0;7.5.0;7.6.0"}]

Historical Number

422560113

Document Information

Modified date:
24 June 2025

UID

nas8N1018975