| Previous | dContents | fIndex |
E When printing certain PostScript files, this printer can fail with a G 49.4C02 service error. This problem has been fixed in printer firmware + version 20050524 07.007.3. ] 10.18 HP LaserJet IIID Printer
L 10.18.1 Job Remains in Starting State
F The DCPS$queuename_NO_SYNC logical name can be used to solve = reported problems printing to HP LaserJet IIID printers with C HP-supplied PostScript Level 2 cartridges. Those cartridges have a F known problem where they corrupt status messages they send to a host. H This can cause jobs to get stuck in the "starting" state when w DCPS tries to use its synchronization sequence. See Section 3.5.3 for more information. \ 10.18.2 Incorrect Sheet Count on Duplex Jobs
C The HP LaserJet IIID and several other HP LaserJet printers do not A internally count physical sheets but instead count pages imaged. G Therefore the "Sheets printed" data of the trailer page will F reflect the number of images processed. For example, a six-page print , job with burst and trailer pages enabled and /PARAMETERS=(SIDES=2)H specified will show "Sheets printed" as eight when only five sheets are printed. _ 10.19 HP LaserJet IIISi Printer
a 10.19.1 Incorrect Sheet Count on Native PCL Jobs
E The HP LaserJet IIISi printer does not keep track of the sheet count H while printing native PCL files. The sheet count reported at the end of H the job, both on the trailer page and to the OpenVMS accounting system, G includes only those sheets printed in PostScript mode, such as the job @ separation pages. There is no known workaround for this problem. ] 10.19.2 Incorrect Sheet Count on Duplex Jobs
D The HP LaserJet IIISi printer exhibits the same behavior with sheet e count as mentioned in Section 10.18.2. _ 10.20 HP LaserJet 4SiMX Printer
] 10.20.1 Incorrect Sheet Count on Duplex Jobs
D The HP LaserJet 4SiMX printer exhibits the same behavior with sheet e count as mentioned in Section 10.18.2. [ 10.21 HP LaserJet 5M Printer
\ 10.21.1 Problems Selecting an Input Tray
DCPS may ignore explicit INPUT_TRAY D parameter values for the HP LaserJet 5M printer, instead utilizing H paper from another input tray. DCPS may also report that TRAY_1 is not D available, even though the tray is a standard tray, when tray 1 is empty.
B Both classes of problems are related to the printer attempting to ? select an alternate input tray if the desired tray is empty or C otherwise not satisfactory. To avoid these problems, use the HP 5M E console to specify that tray 1 is a "cassette" and to lock E out all but one of the available input trays. Refer to the printer's ! user manual for more information. \ 10.21.2 Incorrect Sheet Count on Duplex Jobs
G The HP LaserJet 5M printer exhibits the same behavior with sheet count _ as mentioned in Section 10.18.2. _ 10.22 HP LaserJet 5SiMX Printer
_ 10.22.1 Job Trailer Pages Print in Next Bin
B If the network manager has placed the mailbox bins into "job E separator mode" using the administration software supplied with G the printer, the DCPS job log and trailer pages print in the next bin, # separated from the rest of the job. z 10.22.2 Tray Is Not Available Due to Lack of Memory for Loaded Paper
D If an input tray is loaded with a paper size that cannot be printed D with the current memory configuration, DCPS reports the tray as not H available. (Refer to the HP5SiMX users's guide for memory requirements.) { 10.22.3 Duplex Not Supported Due to Lack of Memory for Loaded Paper
H If an input tray is loaded with a paper size which cannot be printed in E duplex mode with the current memory configuration, DCPS reports that H duplex is not supported. (Refer to the HP5SiMX users's guide for memory requirements.) ] 10.22.4 Incorrect Sheet Count on Duplex Jobs
D The HP LaserJet 5SiMX printer exhibits the same behavior with sheet e count as mentioned in Section 10.18.2. [ 10.23 HP LaserJet 2100 and 2200
J 10.23.1 Problems Starting Queues
H Some models in this series may not allow DCPS jobs to start. To resolve C this, either set the printer to PostScript mode or suppress DCPS's } PostScript synchronization. See Section 11.1.1 for more information. b 10.24 HP LaserJet 4000, 4050 and 5000
G 10.24.1 Minimum Firmware Version
G To use an HP LaserJet 4000 or 5000 printer from DCPS, the printer must : be running a minimum firmware version of 19980714 G MB3.68. To use an HP LaserJet 4050 printer, it is recommended : that the printer be running a minimum firmware version of C 19991030 MB6.30. Earlier versions of firmware may G cause problems such as misprinted or missing characters when using the C DCPS ANSI translator, especially when printing jobs with landscape G orientation or NUMBER_UP. This firmware version number is displayed as ? Firmware Datecode on the printer's configuration page.
H If your printer is running an older version of firmware, contact HP and G request the proper version. The new firmware will be sent on a SIMM to be installed in your printer. [ 10.25 HP LaserJet 4200 and 4300
J 10.25.1 Problems Starting Queues
E These printers do not respond to the DCPS synchronization request at @ the beginning of a job when running older versions of firmware. A Therefore, you should upgrade the printer's firmware to at least G version 20030530 04.047.2 or DCPS jobs will not start.
G If you do not upgrade the printer firmware, you can define the logical E name DCPS$queuename_NO_SYNC before queues to these printers C are started. It is also recommended that the printer's personality B setting be set to PS (PostScript). However, setting the printer's D personality to PS (PostScript) alone will not solve the problem for these printers. [ 10.26 HP LaserJet 4250 and 4350
Y 10.26.1 Printers Fail with Service Error
G When printing certain PostScript files, these printers can fail with a G 49.4C02 service error. This problem has been fixed in printer firmware + version 20050831 08.009.3. a 10.27 HP LaserJet 8000, 8100 and 8150
B 10.27.1 Optional Mailbox
G DCPS numbers the optional mailbox bins on the HP LaserJet 8000 printer D from 1-5, 1-7 or 1-8, depending on the particular option installed. G This is consistent with the numbers molded into the plastic beside the G bins. The printer's console, in contrast, refers to these same bins as G numbers two through nine. Refer to the HP LaserJet User Guide D for your printer model for more information about the numbering and ; purpose of trays with different options and configurations. J 10.27.2 Problems Starting Queues
H Some models in this series may not allow DCPS jobs to start. To resolve C this, either set the printer to PostScript mode or suppress DCPS's } PostScript synchronization. See Section 11.1.1 for more information. K 10.27.3 Minimum Firmware Version
A To use a HP LaserJet 8000 printer from DCPS, the printer must be H running a minimum firmware version of 19980610 MB4.28. H This firmware version number is displayed as Firmware Datecode $ on the printer's configuration page.
H If your printer is running an older version of firmware, contact HP and G request the proper version. The new firmware will be sent on a SIMM to be installed in your printer. R 10.28 HP LaserJet 9050
Y 10.28.1 Printer Fails with Service Error
E When printing certain PostScript files, this printer can fail with a G 49.4C02 service error. This problem has been fixed in printer firmware + version 20050617 08.102.2. c 10.29 HP LaserJet 9055 MFP and 9065 MFP
Y 10.29.1 Printers Fail with Service Error
E When printing certain PostScript files, this printer can fail with a G 49.4C02 service error. This problem has been fixed in printer firmware + version 20050601 07.004.0. V 10.30 HP XL300 Printer
K 10.30.1 Communication Problem
B If a file printed to the XL300 printer contains multiple userdata E messages that are returned in quick succession, some messages may be H lost, and others returned incorrectly. Also, messages that the DECprint D Supervisor wants returned to it will occasionally get garbled. This G will result in spurious messages to the user's terminal (if /NOTIFY is * set). Otherwise, the job prints correctly. a 10.31 Lexmark Optra Rt+ Printer
S 10.31.1 Tray Linking and INPUT_TRAY
D If tray linking is enabled by the printer console, the linked trays @ cannot be selected individually using the INPUT_TRAY parameter. B Specifying any linked tray in the INPUT_TRAY parameter causes the D printer to select among the linked trays in accordance with its own
algorithm. h 10.32 Lexmark Optra S, Optra T and T Series
I 10.32.1 Problems Starting Queues
G Some models in the Lexmark Optra S, Optra T and T series may not allow ? DCPS jobs to start. To resolve this, either set the printer to C PostScript mode or suppress DCPS's PostScript synchronization. See ] Section 11.1.1 for more information. U 10.33 Tektronix Phaser
T 10.33.1 Printer Configuration Settings
C You must change the following AppSocket settings when using Phaser printers with DCPS:
| AppSocket Setting | Value |
|---|---|
| Interpreter or Language | PostScript |
| Filtering | Interpreter-Based |
F To print to these printers over TCP/IP, use the LPD protocol. Because E the printers do not return end-of-job information to DCPS, it is not G possible to use the Raw TCP protocol with these printers. Jobs printed F via Raw TCP will stall after the job is printed and may eventually be put on hold.
F This chapter contains troubleshooting procedures for diagnosing error ! conditions on the printer system.
C When a printer problem occurs, information may be displayed on the B user's terminal if the /NOTIFY qualifier is included on the PRINT E command line. This information may indicate the cause of the failure.
G Check the job trailer page from the print job, which shows some of the F messages that result from printing. Problems with the print files are f indicated on a file error page (see Section 6.7).
E When a printing system problem occurs, examine the console output or A the OPERATOR.LOG file for operator communication manager (OPCOM) E messages. If your terminal is not running OPCOM, use REPLY/ENABLE to G enable PRINTER and CENTRAL messages. Restart the symbiont, and reprint A the job. Then you can read the relevant messages. This procedure = requires OPER privileges. Printer messages are listed in the + User's GuideUser's Guide. { 11.1 What to Do if a Raw TCP/IP Printer is Not Printing
t 11.1.1 Job Remains in Starting State for Raw TCP/IP or LAT Queue
G Most printers respond to the PostScript synchronization command at the H beginning of a DCPS job, but some do not. If all jobs to a queue remain G in the Starting state, you may need to take one of the following steps:
A If you set up a DCPS queue that uses a raw TCP/IP connection and E specify an incorrect TCP port number for the printer, any print jobs C that you submit to the queue will remain in a starting state. DCPS B cannot determine that you have provided an incorrect port number, E because the network failure that it receives is no different than if % the printer had been busy or offline.
E Note that a print job in a raw TCP/IP queue may remain in a starting state for other reasons as well.
H Check the documentation for your printer, network interface card, print G server, or terminal server to determine the correct TCP port number to r use. The TCP port number may also be listed in Table 3-2. Z 11.1.3 Connection Terminations for Raw TCP/IP Queue
D You may get CONTERMINATED errors for long print jobs when using raw G TCP/IP connections. For jobs that consist of a single file or only use F the native PostScript capability of the printer (for example, they do F not use native PCL), these errors are most likely to occur at the end D of the job, with job trailer pages (if specified for the queue) and D print job accounting (if enabled) being lost. For other jobs, these H errors may occur in the middle of the job, with subsequent documents as F well as the trailer pages and accounting information being lost. DCPS F requeues the terminated jobs, placing them in a Holding state so that > you can reprint them once you resolve the termination problem.
F Some network devices, including the HP JetDirect cards, drop a TCP/IP H connection if they do not receive any input from the host system within D a specified amount of time. This is a feature meant to prevent host D software from monopolizing the device. DCPS, however, waits for the B printer to acknowledge that previous documents are printed before D switching from PostScript to some other native printer language and = also before printing a trailer page and gathering accounting B information. Even though the printer may be busy, the NIC may not ? receive any more input from DCPS before the timeout is reached.
G If your NIC allows you to alter the TCP/IP idle timeout value, you can G work around this problem by disabling or increasing the timeout. Check G your NIC documentation to determine if this is possible, and how to do F it. Then release any requeued jobs for which desired output was lost, # and delete the other requeued jobs.
B Note that it is the length of a job in time (versus size) that is H important. For example, a very small PostScript program can take a very B long time to print. Hence, it is difficult to predict how large a timeout is adequate. e 11.1.4 NOT_READY Warnings for Unavailable Raw TCP/IP Printer
G If a job is queued to a printer that uses a raw TCP/IP connection, and H the printer is busy or offline, you will get NOT_READY warning messages for the printer.
E If you believe or determine that the printer is busy, you can ignore F these messages. DCPS cannot, unfortunately, differentiate between the 6 printer being busy, offline, or otherwise unavailable. q 11.2 What to Do if an LPD Printer is Not Printing
N 11.2.1 No Output Printed from LPD Job
D If you do not get any printed output after an LPD job completes, it G could be the result of a PostScript error not reported by the printer. F Because LPD is uni-directional, DCPS cannot report a PostScript error E to the user as it can with other protocols. To assist in determining D the cause of the problem, turn on PostScript error reporting on the A printer. (Refer to the printer's documentation for instructions.)
B Common causes of PostScript errors on LPD printers are missing or = incorrect values for the DCPS logical names DCPS$SHEET_SIZE, ' DCPS$queue-name_SHEET_SIZE or 4 DCPS$queue-name_PRODUCT_NAME logical names.
E Receiving no output may also be caused by the printer expecting file E size information before the job is sent to the printer. This problem E often occurs with larger multi-function devices. If you suspect this . might be the problem, define the logical name ; DCPS$queue-name_SPOOL to enable DCPS LPD spooling. S 11.2.2 LPD Queue Stops and Job Put on Hold
F If you set up a DCPS queue that uses an LPD connection and specify an F incorrect internal queue name for the printer, or omit one when it is E required, any print jobs that you submit to the queue will be put on F hold and the queue will stop. The following message will also be seen:
|
" @ %DCPS-F-LPDTERMINATED, LPD connection abnormally terminated D -DCPS-I-JOB_ID, for job S (queue SNOBALL, entry 866) on SNOBALL = %%%%%%%%%%% OPCOM 19-SEP-2003 12:12:48.88 %%%%%%%%%%% ' Message from user SYSTEM on FUNYET O Queue SNOBALL: %DCPS-F-LPDTERMINATED, LPD connection abnormally terminated |
H Check the documentation for your printer, network interface card, print G server or terminal server to determine the correct internal queue name s to use. See the Section 3.3.2.2 section of this manual for information about creating LPD queues.
D Most printers do not require an internal queue name to be specified ) when creating an LPD print queue. |
H Although an incorrect or missing internal queue name is the most common H cause, this error can also occur after the line printer daemon (LPD) on D the printer or remote host establishes a connection but rejects the print job for some reason. y 11.3 What to Do if a PrintServer Printer Is Not Printing
E The following troubleshooting procedures can help you diagnose error N conditions that can occur during installation of DECprint Supervisor software for PrintServer printers.
G If the printer is not printing, check the OPCOM messages. If the cause < of the failure is not immediately apparent, check the queue characteristics, as follows:
|
" 6 $ SHOW QUEUE queue-name/FULL |
|
" - $ SHOW QUEUE LPS40$FANG/FULL |
|
" B Printer queue LPS40$FANG, on VIPER::FANG, mounted form DCPS$$FORM (stock=DEFAULT) J /BASE_PRIORITY=4 /FORM=DCPS$DEFAULT /LIBRARY=DCPS_LIB /OWNER=[SYSTEM] I /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) /SEPARATE=(FLAG,TRAILER) $ |
|
" < $ STOP/RESET/QUEUE generic-queue-1A $ STOP/RESET/QUEUE other-generic-queues 9 $ STOP/RESET/QUEUE pserver-name 8 $ DELETE/QUEUE generic-queue-1= $ DELETE/QUEUE other-generic-queues 5 $ DELETE/QUEUE pserver-name , $ @SYS$STARTUP:DCPS$STARTUP |
A When you examine the OPCOM messages, look for a message from the H printer indicating NOTREADY. This message indicates that the printer is A unable to acknowledge any queries from the system. Check for the following:
F The steps in this section apply to any serial printer on a local line.
F Manually print a test page on your printer, following instructions in your owner's manual.
C If able to print a test page, go on to step 2 to check the printer H hardware and software configurations. If the printer does not produce a & test page, check the printer hardware.
l Step 2: Check the printer hardware and software configurations
> The configuration settings on the printer and in the software A associated with the printer must be the same. To verify that the H settings match, check a printed summary sheet or the printer console or F switches to verify that the settings are consistent for the following settings:
E Refer to the printer owner's manual for information on how to change these settings.
B Check the terminal device characteristics of a directly-connected C serial printer by issuing the following command on the node of the device:
|
" 8 $ SHOW TERMINAL device-name[:] |
D The variable device-name is the device name in the printer E startup file in parameter P2 of the execution queue definition.
( Check for the following characteristics:
? The summary sheet and the terminal settings should be the same.
G If your printer interface runs at a different speed, make sure you set B the same configuration switch settings and device characteristics.
F If the printer is connected directly to the host, check the baud rate D setting in the printer startup command file. If you did not enter a B baud rate in parameter P6 of the execution queue G definition, the startup procedure sets the printer speed at 9600 baud. \ Refer to the SET TERMINAL command in the HP OpenVMS DCL Dictionary for information F on changing the system's interpretation of the device characteristics.
G If your printer is connected by a LAT device to a local area Ethernet, T see Section 11.4.3.
E If the settings agree and the job still does not print, go to step 3.
S Step 3: Check communications software
D Test the operation of the communications equipment by attempting to G send data directly to the device. To perform this procedure, make sure W the queue is paused (see Section 5.7).
D The device must not be spooled to accomplish this procedure. If the / device is spooled, enter the following command:
|
" 7 $ SET DEVICE LTAnnnn:/NOSPOOL |
H To test the communications setup, issue the SET HOST/DTE command to the 4 printer. Use the commands in the following examples:
|
" ( $ SET HOST/DTE LTA9092:' Connection established, type ^\ to exit Ctrl/T %%[ status: idle ]%% |
D After you press Ctrl/T, you should receive a message in the form of E %%[Status: description]%%. If you receive this message, the 5 connection to the printer is established and working.
C If no message of this type is displayed, enter the commands in the following example:
|
" ^\ $ $ COPY TT: LTA9092: showpage Ctrl/Z $ |
G The test is successful if a page of paper is ejected from the printer. G If no paper is ejected, there is a faulty connection with the printer. H In this case, check the communications cables. Then try the commands in the first example again.
H If the COPY command succeeds, but the SET HOST command fails, check the F communications cables inbound from the printer to the host node for a faulty connection.
L Step 4: Check DCPS$STARTUP.COM
C Make sure that the DCPS$STARTUP.COM file reflects your print queue F needs and that the changes are appropriate for your printer. To check A the printer execution queue characteristics, enter the following ; command, inserting the name of the printer execution queue:
|
" ; $ SHOW QUEUE/FULL exec-queue-name |
A For example, the characteristics for the printer execution queue ' TXA1_LN03R on host EDEN are as follows:
|
" - $ SHOW QUEUE/FULL TXA1_LN03R |
|
" * Printer queue TXA1_LN03R, on EDEN::TXA1: G /BASE_PRIORITY=4 /FORM=DCPS$DEFAULT /LIBRARY=DCPS_LIB /OWNER=[SYSTEM] F /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) /SEPARATE=(BURST,TRAILER) $ |
" Specifically, check the following:
| Previous | aNext | dContents | fIndex |