- Use node parameter TCPDRIV=LPRT until you can get a good bind to the printer or print server. The T option will create a TCPTRACE file in Unicenter CA-Spool queued to the same printer you are testing with.
- Node parameter TCPPORT should not be specified when using LPR print driver. It will default to port 515 to receive all line print requests from Unicenter CA-Spool.
- Insure you know if this printer is network or server attached.
- If server attached insure you get the correct case sensitive printer queue name defined on the server. This value would be added to the node parameter TCPPRT. This is one of the most common errors called in. If you have IBM TCP/IP stack you have the ability to use IBM's LPR command to verify TCP/IP printers are connected correctly in your network.
Example as executed from the ISPF Command Shell screen in TSO:
lpr 'esf20.ppoption(caiqparm)' h 184.108.40.206 p XLPR
Once the LPR command is working you now have the correct printer queue name from the server to add to your node parameter TCPPRT. Note if the LPR command does not work then the same printer will not work in Unicenter CA-Spool.
- Insure you have the correct IP address for this printer or print server specified on the node parameter TCPHOST. You can also specify the DNS name defined for the IP address in your nameserver if you want to use name resolution.
- If your new printer does not bind you need to review the INFO field for error status. These INFO field status codes are found in your Unicenter CA-Spool Systems Guide in chapter 5, under Printer Display Panel. You will find they are specified in the order the function occurs. If the printer does not bind you will see a 0003 in the INFO field of the printer display panel, until it finally times out in which case INFO field will then show a 0067.
A blank INFO field is the result of a good print connection. Any other value should be researched.
Once your printer is working from Unicenter CA-Spool you can change the print driver to other values depending on the support the printer is configured with.
- If your printer is configured to handle Direct Socket connections you can use node parameter TCPDRIV=DSO and TCPPORT=9100 which will not use the LPR protocol.
- If your printer is configured to handle PCL, it needs to be at level PCL4 or higher, you can use node parameter TCPDRIV=PCL5.
- If your printer is configured to handle PJL you can use node parameter TCPDRIV=PJL or PJL4.
- If your printer is configured to handle full Bi-directional communication, you can use node parameter TCPDRIV=PJL5.