| Previous | Contents | Index |
The DIGITAL Laser Printer LN15+ is an upgrade to the DIGITAL Laser
Printer LN15. References in the DCPS documentation to the DIGITAL Laser
Printer LN15 also apply to the DIGITAL Laser Printer LN15+.
10.6.1 Raw TCP/IP Port Number
When creating a DCPS queue for the LN15 using the Raw TCP/IP protocol,
specify port number 3001.
10.6.2 Printer Configuration Settings
DCPS requires certain LN15 printer characteristics to be set. If these values, described in Table 10-1, are not set, DCPS jobs will remain in a Starting state and never print.
| Setting | Value | Where Set | Documentation |
|---|---|---|---|
| PERSONALITY | PS | Printer console CONFIG menu | LN15 User Manual |
| NPAP MODE | OFF | Printer console PARALLEL menu | LN15 User Manual |
| PORT 1 BITRONICS | ENABLED | Ethernet card management | RapidPrint 600 Print Server Installation Guide |
The DIGITAL Laser Printer LN17+ps is an upgrade to the DIGITAL LN17ps
printer. References in the DCPS documentation to the DIGITAL LN17ps
printer also apply to the DIGITAL Laser Printer LN17+ps.
10.7.1 Job Remains in Starting State
If you use a raw TCP/IP or LAT-connected LN17ps printer with DCPS, the associated DCPS print job may remain in a Starting state.
You must either set the Ethernet port to use the PostScript language and disable automatic language sensing, or define a DCPS$queuename_NO_SYNC system logical for the associated queue.
When creating a DCPS queue for the LN17ps using the Raw TCP/IP
protocol, specify port number 2501.
10.7.3 Incorrect Sheet Count
The sheet count reported on the job trailer page and in the OpenVMS
accounting file may be several sheets too few due to a limitation with
the LN17ps printer. There is no known workaround.
10.7.4 Downloading and Deleting Fonts
You may download or delete fonts from the LN17ps printer's optional
hard drive using the FONT_DOWNLOADER.COM procedure described in
Appendix C.
10.7.5 Colored Separator Pages and Tray Switching
The LN17ps can switch between input trays when a specified tray becomes empty. By default, tray switching is disabled. If you currently specify colored separator pages by using the DCPS$queuename_SEPARATOR_PAGE logical, you may want to ensure that tray switching is disabled.
You disable tray switching from the printer console, under the PostScript menu. See the LN17ps User Guide for more information.
Use one of the following PostScript tray numbers as the value of the DCPS$queuename_SEPARATOR_PAGE logical:
| 0 | Main tray | |
| 1 | Front tray | |
| 2 | Lower 1 tray | |
| 3 | Lower 2 tray |
When creating a DCPS queue for the LN20 or LN40 using the Raw TCP/IP
protocol, specify port number 6869. This bidirectional port is not the
same as the unidirectional port that is configured with the printer
console.
10.8.2 Incorrect Sheet Count
The sheet count reported on the job trailer page and in the OpenVMS
accounting file is incorrect due to a limitation with the LN20 and LN40
printers. There is no known workaround. The LN20 and LN40 have,
however, an accounting feature that can be used to track printer
utilization.
10.9 DIGITAL Laser Printer LNC02
10.9.1 Minimum Firmware Version
To use the DIGITAL Laser Printer LNC02 with the Raw TCP/IP protocol from DCPS, the printer must be running a minimum firmware version of System Release 1.1.1, Revision 3.11. This firmware version number is displayed on the printer's startup page.
If your LNC02 printer is running an older version of firmware, you can download the newer version from the DIGITAL Printers Web site at
http://www.digital.com/printers/sofwar/prt_sofwar.html
You can also use the online help from the Web page on the LNC02 to be
directed to the location of the firmware update.
10.9.2 Raw TCP/IP Port Number
When creating a DCPS queue for the LNC02 using the Raw TCP/IP protocol,
specify port number 6869. This bidirectional port is not the same as
the unidirectional port that is configured with the printer console.
10.9.3 Incorrect Sheet Count
The sheet count reported on the job trailer page and in the OpenVMS
accounting file is incorrect due to a limitation with the LNC02
printer. There is no known workaround. The LNC02 has, however, an
accounting feature that can be used to track printer utilization.
10.10 DIGITAL PrintServer 17 Printer
10.10.1 Colored Separator Pages and Tray Switching
PrintServer Software, Version 5.0, adds input tray failover to the PrintServer 17 series printers. This feature allows the printer to automatically switch to another input tray containing the same size media when the current tray becomes empty. This feature is enabled by default.
If you currently use colored flag pages, you may want to disable this feature. To disable input tray failover, perform the following steps:
/TraySwitch true % Controls input tray failover.
% false = disable
% true = enable
|
/TraySwitch false % Controls input tray failover.
% false = disable
% true = enable
|
$ MCR LPS$CONSOLE <printer name> LPS> PRIV Password: <password> LPS> RECONFIG LPS> EXIT |
The DCPS$queuename_NO_SYNC logical can be used to solve
reported problems printing to Hewlett-Packard LaserJet IIID printers
with HP-supplied PostScript Level 2 cartridges. Those cartridges have a
known problem where they corrupt status messages they send to a host.
This can cause jobs to get stuck in the "starting" state when
DCPS tries to use its synchronization sequence. See Section 3.4.3 for
more information.
10.11.2 Incorrect Sheet Count on Duplex Jobs
The Hewlett-Packard LaserJet IIID and several other Hewlett-Packard
LaserJet printers do not internally count physical sheets but instead
count pages imaged. Therefore the "Sheets printed" data of
the trailer page will reflect the number of images processed. For
example, a six-page print job with burst and trailer pages enabled and
/PARAMETERS=(SIDES=2) specified will show "Sheets
printed" as eight when only five sheets are printed.
10.12 Hewlett-Packard LaserJet IIISi Printer
10.12.1 Incorrect Sheet Count on Native PCL Jobs
The Hewlett-Packard LaserJet IIISi printer does not keep track of the
sheet count while printing native PCL files. The sheet count reported
at the end of the job, both on the trailer page and to the OpenVMS
accounting system, includes only those sheets printed in PostScript
mode, such as the job separation pages. There is no known workaround
for this problem.
10.12.2 Incorrect Sheet Count on Duplex Jobs
The Hewlett-Packard LaserJet IIISi printer exhibits the same behavior
with sheet count as mentioned in Section 10.11.2.
10.13 Hewlett-Packard LaserJet 4SiMX Printer
10.13.1 Incorrect Sheet Count on Duplex Jobs
The Hewlett-Packard LaserJet 4SiMX printer exhibits the same behavior
with sheet count as mentioned in Section 10.11.2.
10.14 Hewlett-Packard LaserJet 5M Printer
10.14.1 Problems Selecting an Input Tray
DCPS may ignore explicit INPUT_TRAY parameter values for the Hewlett-Packard LaserJet 5M printer, instead utilizing paper from another input tray. DCPS may also report that TRAY_1 is not available, even though the tray is a standard tray, when tray 1 is empty.
Both classes of problems are related to the printer attempting to
select an alternate input tray if the desired tray is empty or
otherwise not satisfactory. To avoid these problems, use the HP 5M
console to specify that tray 1 is a "cassette" and to lock
out all but one of the available input trays. Refer to the printer's
user manual for more information.
10.14.2 Incorrect Sheet Count on Duplex Jobs
The Hewlett-Packard LaserJet 5M printer exhibits the same behavior with
sheet count as mentioned in Section 10.11.2.
10.15 Hewlett-Packard LaserJet 5SiMX Printer
10.15.1 Job Trailer Pages Print in Next Bin
If the network manager has placed the mailbox bins into "job
separator mode" using the administration software supplied with
the printer, the DCPS job log and trailer pages print in the next bin,
separated from the rest of the job.
10.15.2 Tray is Not Available due to Lack of Memory for Loaded Paper
If an input tray is loaded with a paper size that cannot be printed
with the current memory configuration, DCPS reports the tray as not
available. (Refer to the HP5SiMX users's guide for memory requirements.)
10.15.3 Duplex Not Supported Due to Lack of Memory for Loaded Paper
If an input tray is loaded with a paper size which cannot be printed in
duplex mode with the current memory configuration, DCPS reports that
duplex is not supported. (Refer to the HP5SiMX users's guide for memory
requirements.)
10.15.4 Incorrect Sheet Count on Duplex Jobs
The Hewlett-Packard LaserJet 5SiMX printer exhibits the same behavior
with sheet count as mentioned in Section 10.11.2.
10.16 Hewlett-Packard XL300 Printer
10.16.1 Communication Problem
If a file printed to the XL300 printer contains multiple userdata
messages that are returned in quick succession, some messages may be
lost, and others returned incorrectly. Also, occasionally, messages
that the DECprint Supervisor wants returned to it will get garbled.
This will result in spurious messages to the user's terminal (if
/NOTIFY is set). Otherwise, the job prints correctly.
10.17 Lexmark Optra Rt+ Printer
10.17.1 Tray Linking and INPUT_TRAY
If tray linking is enabled by the printer console, the linked trays cannot be selected individually using the INPUT_TRAY parameter. Specifying any linked tray in the INPUT_TRAY parameter causes the printer to select among the linked trays in accordance with it's own algorithm.
This chapter contains troubleshooting procedures for diagnosing error conditions on the printer system.
When a printer problem occurs, information may be displayed on the user's terminal if the /NOTIFY qualifier is included on the PRINT command line. This information may indicate the cause of the failure.
Check the job trailer page from the print job, which shows some of the messages that result from printing. Problems with the print files are indicated on a file error page (see Section 6.6).
When a printing system problem occurs, examine the console output or
the OPERATOR.LOG file for operator communication manager (OPCOM)
messages. If your terminal is not running OPCOM, use REPLY/ENABLE to
enable PRINTER and CENTRAL messages. Restart the symbiont, and reprint
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 Serial Printer Is Not Printing
When you examine the OPCOM messages, look for a message from the printer indicating NOTREADY. This message indicates that the printer is unable to acknowledge any queries from the system. Check for the following:
The steps in this section apply to any serial printer on a local line.
Step 1: Print a test page
Manually print a test page on your printer, following instructions in your owner's manual.
If able to print a test page, go on to step 2 to check the printer hardware and software configurations. If the printer does not produce a test page, check the printer hardware.
Step 2: Check the printer hardware and software
configurations
The configuration settings on the printer and in the software associated with the printer must be the same. To verify that the settings match, check a printed summary sheet or the printer console or switches to verify that the settings are consistent for the following settings:
Refer to the printer owner's manual for information on how to change these settings.
Check the terminal device characteristics of a directly-connected serial printer by issuing the following command on the node of the device:
$ SHOW TERMINAL device-name[:] |
The variable device-name is the device name in the printer 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.
If your printer interface runs at a different speed, make sure you set the same configuration switch settings and device characteristics.
If the printer is connected directly to the host, check the baud rate setting in the printer startup command file. If you did not enter a baud rate in parameter p6 of the execution queue definition, the startup procedure sets the printer speed at 9600 baud. Refer to the SET TERMINAL command in the OpenVMS DCL Dictionary for information on changing the system's interpretation of the device characteristics.
If your printer is connected by a LAT device to a local area Ethernet, see Section 11.1.3.
If the settings agree and the job still does not print, go to step 3.
Step 3: Check communications software
Test the operation of the communications equipment by attempting to send data directly to the device. To perform this procedure, make sure the queue is paused (see Section 5.7).
The device must not be spooled to accomplish this procedure. If the device is spooled, enter the following command:
$ SET DEVICE LTAnnnn:/NOSPOOL |
To test the communications setup, issue the SET HOST/DTE command to the printer. Use the commands in the following examples:
$ SET HOST/DTE LTA9092: Connection established, type ^\ to exit Ctrl/T %%[ status: idle ]%% |
After you press Ctrl/T, you should receive a message in the form of %%[Status: description]%%. If you receive this message, the connection to the printer is established and working.
If no message of this type is displayed, enter the commands in the following example:
^\ $ COPY TT: LTA9092: showpage Ctrl/Z $ |
The test is successful if a page of paper is ejected from the printer. If no paper is ejected, there is a faulty connection with the printer. In this case, check the communications cables. Then try the commands in the first example again.
If the COPY command succeeds, but the SET HOST command fails, check the communications cables inbound from the printer to the host node for a faulty connection.
Step 4: Check DCPS$STARTUP.COM
Make sure that the DCPS$STARTUP.COM file reflects your print queue needs and that the changes are appropriate for your printer. To check the printer execution queue characteristics, enter the following command, inserting the name of the printer execution queue:
$ SHOW QUEUE/FULL exec-queue-name |
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: /BASE_PRIORITY=4 /FORM=DCPS$DEFAULT /LIBRARY=DCPS_LIB /OWNER=[SYSTEM] /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) /SEPARATE=(BURST,TRAILER) $ |
Specifically, check the following:
If the queue characteristics do not match those defined in DCPS$STARTUP.COM, stop the printer execution queue.
Next, execute the DCPS$STARTUP.COM file, as follows:
$ @SYS$STARTUP:DCPS$STARTUP |
Recheck the execution queue characteristics. If the characteristics are correct and the job still does not print, go to step 5.
Step 5: Check queue logical defaulting
Use the following command to check the values of queue default parameters in the DCPS$STARTUP.COM file, in p4 of the execution queue definition, and in parameter p3 of the generic queue definition.
$ SHOW LOGICAL DCPS$queuename_PARAMETER |
Step 6: Check the queue configurations
The values provided in DCPS$STARTUP.COM are not validated, but simply passed as parameters to the appropriate OpenVMS commands and utilities. Therefore, the OpenVMS commands and utilities detect and report any errors directly. Refer to the OpenVMS System Messages and Recovery Procedures Reference Manual for an explanation of error messages issued by the following DCL commands:
To debug DCL command procedures and record the information in a file, you can use the following commands:
Alternatively, you can set parameter p8 in the execution queue definition in DCPS$STARTUP.COM to 1 for automatic recording. |
| Previous | Next | Contents | Index |