Previous | Contents | Index |
The HP LaserJet IIISi printer exhibits the same behavior with sheet
count as mentioned in Section 10.14.2.
10.16 HP LaserJet 4SiMX Printer
10.16.1 Incorrect Sheet Count on Duplex Jobs
The HP LaserJet 4SiMX printer exhibits the same behavior with sheet
count as mentioned in Section 10.14.2.
10.17 HP LaserJet 5M Printer
10.17.1 Problems Selecting an Input Tray
DCPS may ignore explicit INPUT_TRAY parameter values for the HP 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.17.2 Incorrect Sheet Count on Duplex Jobs
The HP LaserJet 5M printer exhibits the same behavior with sheet count
as mentioned in Section 10.14.2.
10.18 HP LaserJet 5SiMX Printer
10.18.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.18.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.18.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.18.4 Incorrect Sheet Count on Duplex Jobs
The HP LaserJet 5SiMX printer exhibits the same behavior with sheet
count as mentioned in Section 10.14.2.
10.19 HP LaserJet 4000, 4050 and 5000
10.19.1 Minimum Firmware Version
To use an HP LaserJet 4000 or 5000 printer from DCPS, the printer must be running a minimum firmware version of 19980714 MB3.68. To use an HP LaserJet 4050 printer, it is recommended that the printer be running a minimum firmware version of 19991030 MB6.30. This firmware version number is displayed as Firmware Datecode on the printer's configuration page.
If your printer is running an older version of firmware, contact HP and
request the proper version. The new firmware will be sent on a SIMM to
be installed in your printer.
10.20 HP LaserJet 8000, 8100 and 8150
10.20.1 Optional Mailbox
DCPS numbers the optional mailbox bins on the HP LaserJet 8000 printer
from 1-5, 1-7 or 1-8, depending on the particular option installed.
This is consistent with the numbers molded into the plastic beside the
bins. The printer's console, in contrast, refers to these same bins as
numbers two through nine. Refer to the HP LaserJet User Guide
for your printer model for more information about the numbering and
purpose of trays with different options and configurations.
10.20.2 Problems Starting Queues
Some models in this series may not allow DCPS jobs to start. To resolve
this, either set the printer to PostScript mode or suppress DCPS's
PostScript synchronization. See the Release NotesRelease Notes or the O penVMS System Manager's Reference Manual
for more information.
10.20.3 Minimum Firmware Version
To use a HP LaserJet 8000 printer from DCPS, the printer must be running a minimum firmware version of 19980610 MB4.28. This firmware version number is displayed as Firmware Datecode on the printer's configuration page.
If your printer is running an older version of firmware, contact HP and
request the proper version. The new firmware will be sent on a SIMM to
be installed in your printer.
10.21 HP XL300 Printer
10.21.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.22 Lexmark Optra Rt+ Printer
10.22.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 its own
algorithm.
10.23 Lexmark Optra S
10.23.1 Problems Starting Queues
Some models in this series may not allow DCPS jobs to start. To resolve
this, either set the printer to PostScript mode or suppress DCPS's
PostScript synchronization. See the Release NotesRelease Notes or the O penVMS System Manager's Reference Manual
for more information.
10.24 Tektronix Phaser
10.24.1 Printer Configuration Settings
You must change the following AppSocket settings when using Phaser printers with DCPS:
AppSocket Setting | Value |
---|---|
Interpreter | PostScript |
Filtering | Interpreter-Based |
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.
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: Companion Guide for Help Message Users 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. |
When your printer stops printing, follow these steps:
After checking all messages, including the notification messages from the PRINT command, the console output, and the OPCOM log, go to step 1 if the cause of the problem is not apparent.
Step 1: Print the IVP data sheets
Print the following Installation Verification Procedure (IVP) files from SYS$COMMON:[SYSTEST.DCPS]:
DCPS$IVP_ANSI.DAT
DCPS$IVP_POST.DAT
DCPS$IVP_REGIS.DAT
DCPS$IVP_TEK4014.DAT
DCPS$IVP_PCL.DAT
DCPS$IVP_PROPRINTER.DAT
Remember to use the appropriate DATA_TYPE parameter value, indicated in the file name following the underscore, for each of the files. For example, to print DCPS$IVP_REGIS.DAT, use the following PRINT command:
$ PRINT/QUEUE=queue-name/PARAMETERS=(DATA_TYPE=REGIS)- /NOTIFY SYS$COMMON:[SYSTEST.DCPS]DCPS$IVP_REGIS.DAT |
If the files are not printed, go to step 2 to check the files for user error.
If any of the IVP files are not printed, check to see if the translator execution files exist, using the following command:
$ DIR SYS$SHARE:TRN$*.* |
Directory SYS$COMMON:[SYSLIB] TRN$ANSI_PS.EXE; TRN$DDIF_PS.EXE; TRN$REGIS_PS.EXE; TRN$TEK4014_PS.EXE; TRN$PCL_PS.EXE; TRN$PROPRINTER_PS.EXE; Total of 6 files. |
If the correct files are present, go to step 2.
If any files are missing, reinstall the DECprint Supervisor software.
Step 2: Check files for user error
If a particular file fails to print, examine the trailer page from the print job for messages that indicate the cause of the failure. For an explanation of, and recovery procedures for the error messages, see the User's GuideUser's Guide.
If the file is a PostScript file, an error exists in either the PostScript file or in the application that generated the PostScript file. If the application is supplied by Compaq, submit a Software Performance Report (SPR).
If the file is other than a PostScript file, an error exists in the translation process. If the translator is supplied by Compaq, submit a Software Performance Report.
Sometimes, when the serial communication cable between the printer and the host is disconnected and later reconnected, the active print job displays the status Printing when nothing is happening at the printer. Power-cycle the printer, then resubmit the lost print job.
When reconnecting the printer to the host, turn off and then turn on the printer. Turning the printer off and on ensures proper synchronization between the print symbiont and the printer. |
A network environment allows several separately managed systems to access the same printer. Therefore, when the printer is not printing, you must determine which node has control of the printer.
The remaining sections discuss the following steps in troubleshooting the printer in a network environment:
A network printer may fail to print if another node is accessing the printer, or if the printer has stopped printing. Perform the following steps to determine which host has control of the printer.
Step 1: Determine your printing node
To determine which node runs your printer, issue the following command, inserting the name of the print queue you use:
$ SHOW QUEUE/FULL queue-name |
From the first line of the following sample display, you determine that FIERY is the node that runs your printer and LTA546 is the application port associated with the print queue:
Printer queue LN03R3, on FIERY::LTA546, mounted form DCPS$DEFAULT (stock=DEFAULT) /BASE_PRIORITY=4 /FORM=DCPS$DEFAULT (stock=DEFAULT) /NOENABLE_GENERIC /LIBRARY=DCPS_LIB lowercase /OWNER=[SYSTEM] /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) /SEPARATE=(BURST,TRAILER) $ |
Perform steps 2 and 3 on the node (FIERY) that runs the printer.
Step 2: Determine LAT node and port name to which the printer is connected
Look in the LAT startup file SYS$STARTUP:LAT$SYSTARTUP.COM. The SET PORT command associates the application port (LTAd) with a specific port (/PORT=port_name) on the server (/SERVER=server_name).
CREATE PORT LTA546: /NOLOG /APPLICATION ! LN03R3 SET PORT LTA546: /APPLICATION /QUEUE /NODE=TAS204 /PORT=PORT_7 |
The port must be set with queuing enabled (/QUEUE) and as an application port (/APPLICATION). Make sure that SYSTARTUP_VMS.COM invokes LAT$STARTUP.COM. |
Step 3: Check port and server system names
Ensure that port and server system settings are the same as those in the SYS$STARTUP:LAT$SYSTARTUP.COM. Use the LATCP SHOW PORT command to look at the application port (LTAd) as follows:
$ RUN SYS$SYSTEM:LATCP LCP>SHOW PORT lta546 Local Port Name = LTA546: application Specified Remote Node Name = TAS204 Specified Remote Port Name = PORT_7 Actual Remote Node Name = TAS204 Actual Remote Port Name = PORT_7 Link Name = LAT$LINK |
Step 4: Determine which host controls the printer
You can determine which host controls the printer by logging in to a terminal that is connected directly to a DECserver or by connecting to a LAT device over the network. If you have direct access to the DECserver port, go directly to step 4B.
Step 4A: Connect to the LAT device
Use either the Network Control Program (NCP) or Terminal Server Manager (TSM) to connect to the DECserver device over the network.
To use NCP, issue the following commands:
$ MCR NCP NCP> SHOW KNOWN CIRCUITS |
$ MCR LATCP LCP> SHOW NODE server-name |
LCP> SHOW NODE TAS200PSSA |
Node Name: TAS200PSSA LAT Protocol Version: 5.1 Node State: Reachable Address: 08-00-2B-05-C7-05 Node Ident: LN03R V2.0 DECServer 200 Incoming Connections: Enabled Circuit Timer (msec): 80 Multicast Timer (msec): 30 Service Groups: 15, 31-32 99 Service Name Status Rating Identification BURNET Available 0 |
$ MCR NCP NCP> CONNECT VIA service-circuit PHYSICAL ADDRESS nn-nn-nn-nn-nn-nn |
After entering the NCP CONNECT command, press Return until you get the pound sign (#) prompt. At this prompt type the password (ACCESS) to get the Local> prompt:
# username: username Local> |
Step 4B: At the LAT console port
After making your connection and logging in to the LAT console, enter the following commands:
Local> SET PRIVILEGED Password> Local> SHOW SESSIONS PORT_7 |
The default password is SYSTEM.
The following example shows a SHOW SESSIONS PORT command on a DECserver 200 that tells you that a remote system HAILEY controls port 7.
Local> SHOW SESSIONS PORT 7 Port 7: (Remote) Connected Current Session 1 -Session 1: Hailey Connected Pasthru |
If your system runs the TSM software, issue the following commands:
$ RUN SYS$SYSTEM:TSM$MAIN TSM> USE SERVER tas204 TSM> SET PRIVILEGED Password> TSM> SHOW SESSIONS PORT_7 |
To run the TSM program, you need read access to the TSM management directory file and OPER privileges. For more information, refer to the Guide to Terminal Server Manager. |
Previous | Next | Contents | Index |