Common Infoprint Server problems

Customers encounter certain common problems with Infoprint Server. These problems have straightforward fixes. If applicable, try these fixes before you call your IBM® service representative.

Performance problems when printing to one printer from many printer definitions

Many customers report performance problems when they are printing output through many printer definitions when the Restrict ports field is selected in the printer definitions. Often, message ANFM1103I with errno 48 is found in the ANFMMSG data set. The problem occurs when the 11 well-known ports 721 - 731 are exhausted, and TCP/IP enforces a 2-minute wait before a port is reused.

To fix the problem, the administrator clears the Restrict ports field in the printer definition so that ports 1024 and higher can be used. By default, Restrict ports is not selected.

Printing on an HP LaserJet printer

When printing on an HP LaserJet printer, the administrator specifies 0D25 in the Line termination field in the printer definition to avoid incorrect output. If this value is not specified, the resulting output problems vary, but the most common is stair stepping, where each line is indented further than the previous line.

Error is issued for incorrect print queue name on HP printers with JetDirect cards

Message ANFM1109I with error number 54 (econnreset) can be displayed after an error (such as output bin full). This problem occurs on Hewlett-Packard printers that have the JetDirect card when the Print queue name field in the printer definition is not TEXT or RAW. To correct the problem, change the print queue name to either TEXT or RAW.

Incorrect or partial output that is caused by incorrect printer information

A user might encounter incorrect output, partial or missing output, or partial output followed by a call for user intervention (printer becomes NOT READY). A common cause is a printer definition that specifies a port or port number when a print queue name is required. Specifying a port number implies direct sockets printing, which bypasses LPR/LPD processing, causing the described output errors.

Incorrect or partial output when a transform from AFP is used

A user might encounter incorrect or partial output if the print process is interrupted during the generation of print output or an error occurred during print generation that interrupted the transform. This situation happens only when you are using a command to transform data, such as afpxpdf or pcl2afp, and the transform is interrupted.

Empty file when a transform from AFP is used

If a transform from AFP produces an empty file, the problem might be that the transform cannot find the default font and cannot write any error messages. The solution is for the administrator to specify a valid default font in the AOP_CHARS environment variable in the transform configuration file (aopxfd.conf). Also, to help diagnose the problem, the administrator can specify the -F filename option on the transform command to specify an output file for messages. This message file is created in the transform's working directory. If the problem is a missing default font, the file contains a message about the error.

Cannot print multiple copies

If you have a problem printing multiple copies, clear the Optimize copies field in the printer definition.

In addition, some line printer daemons do not support multiple copies through the standard LPD convention. The workaround is to use this JCL to generate multiple copies on the JES spool but then route them to the same printer:

//PWAYJOB4 JOB
//STEP1    EXEC PGM=USERA
//OUTDS1   OUTPUT CLASS=E,FORMS=WIDE,DEST=DEPT001
//DD1      DD SYSOUT=(,),OUTPUT=(*.OUTDS1,*.OUTDS1)

The number of JCL refer-backs (*.OUTDS1) is directly related to the number of SYSOUT data sets that are created.

Wrong font parameter passes to an AIX® machine (JES3)

In JES3, if you use the Remote PSF LPR option to pass a JCL CHARS parameter to an AIX machine as an -ochars parameter, the wrong font name might pass through to AIX. To fix the problem, add U to the WS parameter of the JES3 DEVICE IO statement for that particular printer FSA.

Data set on JES spool never closes or closes after the wrong page

If you specify an incorrect end-of-file rule for a NetSpool job, the data set on the JES spool might never close or might close after the wrong page. Check the end-of-file rule for the printer definition that is associated with this printer LU, and verify that the rule is suitable for your application. For more information, see z/OS Infoprint Server Operation and Administration.

Error messages BPXF024I and EDC5112I received when Infoprint Server daemons are started

If you start Infoprint Server daemons by using the /etc/rc facility, you can receive these error messages:

BPXF024I (BPXOINIT aoplpd: socket(AF_INET,SOCK_STREAM,0) failed in
TCPSocket::TCPSocket (int&,int,int) at ./src/tcpsock.cpp 83:
EDC5112I Resource temporarily unavailable. errno2=0x74b30296

This error occurs because UNIX System Services runs commands in the /etc/rc file early in the IPL and TCP/IP might not be completely active before the Infoprint Server daemons start. To correct this problem, you can use the setstack command. The setstack command is not formally supported by IBM. However, you can download setstack from the z/OS UNIX System Services Tools and Toys Web page to make sure that TCP/IP is initialized before the aopstart command runs. For an example of how to specify the setstack command in /etc/rc, see z/OS Infoprint Server Customization.

lp command successfully spooled but unexpected output occurs

If you run the lp command in a UNIX System Services shell and the file is spooled successfully but the expected output is not generated, one of these might be the cause:

You might be running the wrong lp command. The Infoprint Server lp command is in the /usr/lpp/Printsrv/bin directory. However, the standard UNIX System Services lp command is in the /bin directory. You can use the whence command to determine the path of the command. To correct this problem, place the /usr/lpp/Printsrv/bin directory before the /bin directory in your PATH environment variable.
If you are transforming AFP data, more error messages might be sent before the AOP007I message. Examine the message page for error information.

Infoprint Server job identifiers do not display on JES spool

You must use SDSF or a similar product to display the job identifiers that Infoprint Server assigns to output data sets on the JES spool. JES Display commands list internal job identifiers instead of the job identifiers that Infoprint Server assigns.

ISPF panel AOPIPP1 displays message 'NOT AUTHORIZED' and message AOPIM021

If you receive an ISPF message that you are not authorized when you attempt to use the Infoprint Server ISPF panels, your TSO user ID does not have the required RACF® authority. Your TSO user ID, or one of the groups to which you belong, must have READ or UPDATE access to the AOP.ADMINISTRATOR profile in the PRINTSRV class. READ access is required to list and browse objects in the Printer Inventory, and UPDATE access is required to add, copy, and edit objects. If the AOP.ADMINISTRATOR profile is not defined, you must have READ access to the AOPADMIN profile in the FACILITY class. Typically, the AOPADMIN group has UPDATE access to the AOP.ADMINISTRATOR profile or READ access to the AOPADMIN profile.

Tip: To display the RACF groups that your user ID belongs to, enter the LISTUSER command. Output from the LISTUSER command is similar to:

USER=JOHN  NAME=JOHNNIE, JOHN  OWNER=JOHN  CREATED=02.161
DEFAULT-GROUP=USER  PASSDATE=03.300  PASS-INTERVAL=186
ATTRIBUTES=NONE

If the LISTUSER command displays only one group and the AOPADMIN group is not displayed, the SETROPTS parameter NOGRPLIST might be set. NOGRPLIST causes the LISTUSER command to check only the first group that your user ID belongs to. Other groups are not checked. Therefore, if your user belongs to multiple groups and AOPADMIN is not the first one, the AOPADMIN group is not displayed. A SETROPTS list display shows 'LIST OF GROUPS ACCESS CHECKING IS INACTIVE'. Enter SETROPTS GRPLIST so that the LISTUSER command can check all groups that your user ID belongs to.

Error when text data is printed from an AS/400 system

If a user prints a text document from an AS/400 system by using a workstation customization object of QSYS/QWPDEFAULT, Print Interface might not recognize the data format as text. One of these errors occur:

If Other is not selected in the Data format field of the printer definition, Print Interface rejects the job.
If Other is selected, data does not print as expected.

This problem occurs because the host print transform and workstation customization object QSYS/QWPDEFAULT on the AS/400 system inserts an initial null byte into the print file before it sends the file to Infoprint Server. The null byte prevents Print Interface from recognizing the data format as text.

To correct this problem, you can use this source to create a workstation customization object that does not insert an initial null byte. This source is the same as for the QSYS/QWPDEFAULT object, but with :INITPRT DATA='00'X. removed. For information about how to create a customization object, see Workstation Customization Programming V4R3.

 :WSCST DEVCLASS=TRANSFORM.
   :TRNSFRMTBL.
   :SPACE
     DATA ='20'X.
   :CARRTN
     DATA ='0D'X.
   :FORMFEED
     DATA ='0C'X.
   :LINEFEED
     DATA ='0A'X.
   :EWSCST.

NetSpool page-formatting values ignored

NetSpool uses page-formatting values, such as margins and line length, that are specified in the printer definition (in the Processing section under the heading Conversion between SCS and Line), only when NetSpool formats SCS data (for LU type 1 sessions) into line data. NetSpool does not use page-formatting values in the printer definition when it formats 3270 data (for LU type 0 and type 3 sessions) because NetSpool instead uses page-formatting information that is specified in the 3270 Write Control Characters (WCCs) in the 3270 data stream.

To change page-formatting values for 3270 data, the application programmer must change the WCCs generated by the VTAM® application that creates the 3270 data.

Error messages: CSV003I REQUESTED MODULE AOXVTM NOT FOUND and CSV0281 ABEND 806–04

This message is received when an APPL ID is specified in the IP PrintWay™ FSS definition in the Printer Inventory, but Infoprint Coaxial Printer Support for z/OS is not installed.

To correct this problem, remove the APPL ID from the Applid field in the FSS definition before you restart IP PrintWay. Infoprint Coaxial Printer Support cannot be installed because it is no longer supported in z/OS V2R3.