How do I debug a TCP/IP printer that was working and now will not print? Do you have any hints in doing this?

Document ID : KB000055720
Last Modified Date : 14/02/2018
Show Technical Document Details


I have several TCP/IP printers that were working and now and then some of them stop working and we don't know how to tell what the problem is.


  1. Find out what changes were made: Was it really working? A change to either the defnode or node or the TCP/IP address or the server printer queue name as a result of possibly moving the printer. There is also the possibility that the printer really never did work in Unicenter CA-Spool.

    If this is the case then go back to the basics as if it was a newly added printer.

  2. Find out if the problem is name resolution or the bind or is it the print results.

  3. If name resolution is the problem add Print driver option 9 to your node parameter to generate SAS/C Resolver debugging messages, which are written to your Sysprint DD in your Unicenter CA-Spool proc. Also insure you have SYSTERM DD SYSOUT=* set in your proc. The messages written in either two of these sysouts will help you determine what the problem is. This is a common called in problem, when the network staff change an IP address or move printers around and change the IP address and or the DNS for the IP address in use. Another good way to test the name resolution is to use the IBM TCPIP LPR command and for Unicenter TCPAccess you can use the DNRGET HOST BYNAME command.

  4. If the bind is the problem go back to, how to add a new TCP/IP printer.

  5. If it is a print problem, determine if it is an application change, input interface change or a formatting problem and in what area (auto formatting or not, command sent or not).

    If auto formatting is in use and you want the file to print differently, then you will need to use a PCLLIB FCB2****, FORM**** or CHAR**** resource member to pass the desired PCL commands.

    The print driver F option turns on auto formatting and allows read of file resources from the PCLLIB. Note that auto formatting can and may override your PCL commands, causing different print results than desired.

    If you do not want auto formatting to override any of your PCL commands, you can use print driver option G to only pass your coded PCL commands and turn off auto formatting. Note that if you use an FCB2**** resource member, you must also have an image module of the same name FCB in your image library accessible to Unicenter CA-Spool.

    Which resource member should be used? It depends on what type of PCL commands you are adding. If lines per page or lines per inch or characters per inch then it is suggested to use the FCB2**** resource member. Insure that the one you use is not used by other files that should not print in the format you expect for this particular file. FORM**** can also be used to send any type of PCL commands as well as a CHAR**** resource. It's your choice.

    We do not provide the resource libraries or any PCL, PJL or Binary print commands. The resource libraries, PCLLIB, PJLLIB and BINLIB should all be created with the following file attributes: (RECFM=VB,LRECL=259,BLKSIZE=2594)

    Check with Hewlett Packard to purchase a PCL Language book. You can also check the HP website for a list of basic PCL Commands. and do a search on their website for PCL Commands to be taken to a list of PCL command documents.

    You can also check with Hewlett Packard to purchase a Printer Job Language Technical Reference Manual if you wish to use PJL print commands.