Technical data

Note that a print job in a Raw TCP/IP queue may remain in a starting state for
other reasons as well.
Check the documentation for your printer, network interface card, print server, or
terminal server to determine the correct TCP port number to use. The TCP port
number may also be listed in Table A–1.
4.4 Connection Terminations for Raw TCP/IP Queue
You may get CONTERMINATED errors for long print jobs when using Raw
TCP/IP connections, especially with printers that have large memory or disks for
spooling data, such as the HP Color LaserJet 9500 and LaserJet 9055mfp and
9065mfp printers.
For jobs that consist of a single file or that only use the native PostScript
capability of the printer, these errors are most likely to occur at the end of the
job, with job trailer pages (if specified) and print job accounting (if enabled)
being lost. For other jobs, these errors may occur in the middle of the job, with
subsequent documents as well as the trailer pages and accounting information
being lost. DCPS requeues the terminated jobs, placing them in a Holding state
so that you can reprint them once you resolve the termination problem.
Some network devices, including HP JetDirect cards, drop a TCP/IP connection
if they do not receive any input from the host system within a specified amount
of time. This is a feature meant to prevent host software from monopolizing
the device. DCPS, however, waits for the printer to acknowledge that previous
documents are printed before switching from PostScript to some other native
printer language and also before printing a trailer page and gathering accounting
information. Even though the printer may be busy, the NIC may not receive any
more input from DCPS before the timeout is reached.
If your NIC allows you to alter the TCP/IP idle timeout value, you can work
around this problem by disabling or increasing the timeout. Check your NIC
documentation to determine if and how this is possible. (Recent HP printers call
this setting the TCP/IP ‘‘idle timeout’’.) Then release any requeued jobs for which
desired output was lost, and delete the other requeued jobs.
Note that it is the length of a job in time (versus size) that is important. For
example, a small PostScript program can take a long time to print. Therefore, it
is difficult to predict how large a timeout is adequate.
4.5 NOT_READY Warnings for Unavailable Raw TCP/IP Printer
If a job is queued to a printer that uses a Raw TCP/IP connection, and the printer
is busy or offline, you will get NOT_READY warning messages for the printer.
If you believe or determine that the printer is busy, you can ignore these
messages. DCPS cannot differentiate between the printer being busy, offline or
otherwise unavailable.
4.6 Translators Do Not Generate Color PostScript
The translators provided with DCPS (for example, ReGIS) do not generate color
PostScript commands, even if your source file contains color information. The
colors are instead translated to various shades of gray.
4–2 DCPS Restrictions