Technical data

Re-issue the job and specify document-format=PostScript.
12.2.2 Physical Printer Is Hung in Connecting State
If an output device cannot be accessed when a job is assigned to it, the
physical printer object will remain in the connecting-to-printer state.
There are several reasons for this:
• The printer is busy printing other jobs.
• The printer is off line.
• The printer is powered off.
• The network path to the printer is inaccessible.
• The printer is configured for bidirectional session control
(printer-connection-level=4), but the device is not capable of
supporting this level.
The only way to return the printer object to idle is to remove the job.
12.2.3 Jobs Remain in Pending State
Use the following steps to determine why jobs remain in the pending state
after they are submitted.
• Make sure the physical printer is enabled and that its state is idle.
• Determine whether all job and document requirements, specified
explicitly when submitting the job or implicitly by way of initial value
objects, are both supported and ready on at least one physical printer
associated with the queue.
For example, if you submitted a job to a logical printer whose initial
value objects specify job-sheets, document-sheets, duplex printing,
number-up, etc., check that the corresponding xxx-supported and
xxx-ready attributes are set on the physical printer:
# pdls -c p -r job-sheets-ready pp_name
# pdls -c p -r document-sheets-ready pp_name
# pdls -c p -r plexes-supported pp_name
# pdls -c p -r number-up-supported pp_name
12.3 System Errors and Error Information
This section contains error and resolution scenarios related to subsystems
of the print system other than the printer and server objects. In addition,
this section also contains information about where error information can be
located on the system.
12–4 Troubleshooting