| Previous | Contents | Index |
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]:
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 |
You need the DCPS--PLUS license to print data-types other than PostScript and ANSI and non-native PCL. |
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 DIGITAL, 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 DIGITAL, 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. |
After determining which system controls the printer port, follow these steps.
Step 1: Check port characteristics
Compare the LAT port characteristics with those listed in the Software Installation GuideSoftware Installation Guide. To view the port characteristics, issue the SHOW PORT command at the Local> prompt or the TSM> prompt.
Step 2: Use procedures in Section 11.1.1
Follow the steps in the appropriate section:
If you follow these procedures and the printer is not printing, go to step 3.
Step 3: Regain control of the LAT port
You may need to disconnect a symbiont process that controls the port connected to the printer. For example, an unsupported version of the symbiont software might not disconnect after it gains control of the port. Disconnect the symbiont process with the following command:
Local> SET PRIVILEGED Password> Local> LOGOUT PORT port_number |
You need privileged status on the LAT node to execute this command.
11.1.3.3 Common LAT Error Messages
The following list contains common error messages received in a network environment. The error message prefix is DCPS$. The severity level is not indicated. The messages are arranged alphabetically by ident-string. (Refer to the User's GuideUser's Guide for an explanation of the error message format.)
DCPS$_CONAPPLICATION, Connection request is not to a LAT applications
port
Explanation: This message usually occurs when a LAT
port is not reserved as an applications port, and another device is
connected to the port that is requested by the printer. The LAT
configuration file LAT$SYSTARTUP.COM should contain a line similar to
the following with the /APPLICATION parameter.
SET PORT LTAnnn:/NODE=server-name/PORT=port-name/QUEUE/APPLICATION |
To avoid this problem, specify a higher port number for the printer.
DCPS$_CONTERMINATED, Connection abnormally terminated
Explanation: This message occurs when communication to
the LAT node is interrupted. This results in a stopped queue. Check the
following:
DCPS$_CONTIMEOUT, Connection timed out, server not available, or
incorrect server name specified
Explanation: This message occurs when the server name
is not recognized. This problem may indicate the collision of user
terminal space and the printer port.
Verify that the server name connected to the printer port is correct. Compare the server name specified in the LAT configuration file LAT$SYSTARTUP.COM with the server name on the LAT device. LAT$SYSTARTUP.COM should contain a line similar to the following:
SET PORT LTAxxx:/NODE=server_name/PORT=port_name/QUEUE/APPLICATION |
Use the SHOW PORT command to find the server name associated with the printer port:
Local> SHOW PORT port-name |
DCPS$_LRJACCESSDENIED, Access denied
Explanation: This message usually occurs when the
group code specified in LAT$SYSTARTUP.COM does not match one of the
groups on the LAT device connected to the printer. Thus, the printer
software does not have access to the LAT port. The LAT configuration
file LAT$SYSTARTUP.COM should contain a line similar to the following:
SET NODE/GROUP=group-list/ENABLE |
Compare groups, /GROUP=group-list, set in LAT$SYSTARTUP.COM with those set on the LAT device (SHOW PORT command).
DCPS$_LRJDELETED, Queue entry deleted by server
Explanation: This message occurs when someone manually
terminates the connection to the LAT device.
DCPS$_LRJILLEGAL, Illegal request parameter
Explanation: This message indicates that an internal
LAT error has occurred. Submit a Software Performance Report.
DCPS$_LRJINUSE, Port or service in use
Explanation: This message usually occurs on a LAT port
when port-name is not set with the queuing parameter (/QUEUE)
enabled or when the queue limit is too small. On the LAT device, enter
the following command:
SET PORT port-name QUEUE ENABLE |
DCPS$_LRJNAMEUNKNOWN, Port Name is unknown
Explanation: This message occurs when the port name
specified in the LAT configuration file LAT$SYSTARTUP.COM is not known
on the server. Compare the port name specified in the LAT configuration
file LAT$SYSTARTUP.COM with the printer port name associated with the
server. LAT$SYSTARTUP.COM should contain a line similar to the
following:
SET PORT LTAnnn:/NODE=server-name/PORT=port-name/QUEUE/APPLICATION |
Find the name of the printer port associated with the server, by issuing the following command:
Local> SHOW PORT port-number |
DCPS$_LRJNOTOFFERED, Service is not offered on the requested port
Explanation: This message usually occurs when the
access mode is not set to REMOTE on the LAT port. Use the SET and
DEFINE commands as follows to set the access mode for the port:
Local> SET PORT port-number ACCESS REMOTE Local> DEFINE PORT port-number ACCESS REMOTE |
For more information, refer to the User's GuideUser's Guide or to the troubleshooting guide for your LAT device. |
Serial printers transmit unsolicited data to the host system when power-up initialization occurs. The OpenVMS operating system normally interprets unsolicited data from a terminal device as a login request. The printer software startup file sets the SECURE_SERVER terminal characteristic for all printer terminal devices on the host system. SECURE_SERVER prevents the OpenVMS host and the printer from engaging in a potentially endless login dialog.
To eliminate login dialog, set terminal characteristics for terminal devices by using the following procedures in this order:
AUTOCONFIGURE uses SYSGEN parameters to set default terminal characteristics for all terminal devices on the system. Your system will not encounter the login dialog problem if SECURE_SERVER is set with SYSGEN. The SYSGEN parameter that accomplishes this is TTY_DEFCHAR2. Refer to the OpenVMS Upgrade and Installation Manual for information on setting SYSGEN parameters.
The system startup procedure may also set terminal characteristics. Since this command file executes prior to the printer startup file, your system will be less vulnerable to the login dialog problem if SECURE_SERVER is set for printer terminal devices within the SYSTARTUP_VMS file.
DCPS$EXECUTION_QUEUE.COM (the printer execution queue command file) sets the SECURE_SERVER terminal characteristic for printer terminal devices by default. This file is provided in the software kit.
If your printer is configured on a LAT device in a local area Ethernet,
set the LAT port and the terminal server characteristics for the
printer to minimize login dialog. Refer to the Software Installation GuideSoftware Installation Guide for LAT
port characteristics.
11.2 What to Do if a PrintServer Printer Is Not Printing
The following troubleshooting procedures can help you diagnose error conditions that can occur during installation of DECprint Supervisor software for PrintServer printers.
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:
$ SHOW QUEUE queue-name/FULL |
$ SHOW QUEUE LPS40$FANG/FULL |
Printer queue LPS40$FANG, on VIPER::FANG, mounted form DCPS$$FORM
(stock=DEFAULT)
/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=(FLAG,TRAILER)
$
|
$ STOP/RESET/QUEUE generic-queue-1 $ STOP/RESET/QUEUE other-generic-queues $ STOP/RESET/QUEUE pserver-name $ DELETE/QUEUE generic-queue-1 $ DELETE/QUEUE other-generic-queues $ DELETE/QUEUE pserver-name $ @SYS$STARTUP:DCPS$STARTUP |
Slower printing speeds can result from:
Complex ANSI jobs include those that use many downloaded fonts on a page. These jobs always take longer to print.
For serial printers, a 30-second delay before the printing of ANSI jobs indicates an ANSI prologue mismatch between the ANSI translator and the print job. On a serial printer, power cycle the printer (turn it off and then on) to load the appropriate prologue. The first ANSI print job is delayed by the loading of the prologue, but subsequent ANSI print jobs are printed more efficiently.
If your printer is connected to multiple nodes running different versions of the printing system, power cycling the printer may not eliminate the 30-second delay. The node that connects to the printer first persistently loads its prologue. The other nodes must load the prologue with every print job. To eliminate the delay in this case, every node should run the same version of the DECprint Supervisor software.
| Previous | Next | Contents | Index |