If you specify incorrect job parameters or your job gets a PostScript error, your job may never finish because the LN15 printer does not always send an error message to DCPS. Use the DELETE /ENTRY command to remove the job from the queue and make the printer available for other jobs. If the LN15 printer displays "PS Error 19" or the LN15+ displays "WAIT TIMEOUT / Press Continue", you must also press the CONTINUE button on the printer to resume printing. To avoid having to press the printer button, set the printer's PostScript timeout setting to a value of 0.

18.6.4 Jobs May Not Issue Failure Notifications

Jobs that are printed with the /NOTIFY qualifier and fail may not issue failure messages. You will, however, get a DCPS error page printed when such errors occur.

18.7 DIGITAL Laser Printer LN17+ps and LN17+ps

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.

18.7.1 Output May Be Clipped on the LN17ps

Printer output on the LN17ps might be clipped when the following conditions are met:

• You specified an INPUT_TRAY value of FRONT or MULTIPURPOSE
• You specified a sheet size
• The imageable area of the requested sheet size was larger than the console-specified size for the manual tray

When you specify an INPUT_TRAY value of FRONT or MULTIPURPOSE for the LN17ps along with a sheet size, DCPS requires you to specify the sheet size that matches the console-specified manual size.

18.8 DIGITAL Laser Printer LN40

The following problems can be seen on the DIGITAL Laser Printer LN40 printer when the printer console setting OFFSET STACKING is ON:

• If a SHEET_COUNT parameter value greater than 1 is specified, job and file separator pages are printed offset from the user job. In addition, the copies of each page of your job are offset from the copies of the previous page.
• If your document was produced on a PC or contains PostScript commands specifying the number of copies to print, you may not get the desired jogging or copy behavior that you expect. For example, you may only get a single copy of your document, you may get collated copies that are offset from each other, or the job's trailer page (if any) may be printed after the first copy of your document.
  To avoid these restrictions, use the /COPIES or /JOB_COUNT qualifiers with your PRINT command rather than the SHEET_COUNT parameter. Also, do not specify a copy count other than 1 when producing a document on a PC.
• If the printer's COLLATION setting is OFF, the first DCPS job printed after the LN40 has been powered on will print with each page offset from the previous page. There is no workaround for this problem.

The Compaq Laser Printer LNC02 is equivalent to the DIGITAL Laser Printer LNC02. References in the DCPS documentation to the DIGITAL Laser Printer LNC02 also apply to the Compaq Laser Printer LNC02.

18.9.1 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.

18.10 HP LaserJet Printers

The HP LaserJet IIID, LaserJet IIISi LaserJet 4M, LaserJet 4ML, LaserJet 4MX, and LaserJet 4SiMX printers have a slightly smaller printable area than other printers. As a result, if you print an ANSI text file that utilizes 66 lines per page, the bottom three points of the 66th line will not print.

You can work around this restriction by using layup options. One solution is to create and use a layup definition file with the following options:

noborders margins = 0, 3, 0, 0

Or, you can provide those options directly on the command line:

$ PRINT /PARAMETERS=(LAYUP="(NOBORDERS;MARGINS=0,3,0,0)")

The LaserJet 5M printer has a similar restriction for 66 lines of ANSI text, except that you need to allow for an 11-point (versus 3-point) bottom margin.

18.11 HP LaserJet 4MV

The 4MV printer supports both the JIS and ISO standards for B5 paper sizes. For this printer, the JIS size is regarded as paper while the ISO size is regarded as an envelope. In DCPS, there is only one B5 option for specifying sheet size. DCPS handles the two B5 sizes as follows:

Parameter	Config.	Result
SHEET_SIZE=B5	ISO is loaded in tray xxx	Pages print in tray xxx with ISO image area
SHEET_SIZE=B5	JIS is loaded in tray xxx	DCPS reports "B5 medium not loaded in printer_name"
INPUT_TRAY=xxx, SHEET_SIZE=B5 (xxx is MANUAL_FEED)	ISO or JIS is loaded in tray xxx	Pages print in tray xxx with ISO image area, regardless of the B5 variant
INPUT_TRAY=xxx, SHEET_SIZE=B5 (xxx is anything but MANUAL_FEED)	ISO or JIS is loaded in tray xxx	Pages print in tray xxx with the correct image area for each B5 variant

18.12 HP LaserJet 5SiMX

The 5SiMX printer supports both the JIS and ISO standards for B5 paper sizes. DCPS handles the two B5 sizes as described in Section 18.11.1.

18.12.2 Optional Mailbox

DCPS numbers the optional mailbox bins on the HP 5SiMX printer from one through eight, which is consistent with the numbers molded into the plastic beside the bins. The 5SiMX console, in contrast, refers to these same bins as numbers two through nine.

18.13 HP LaserJet 2100 and 2200

The HP LaserJet 2100 and 2200 printers cannot detect the size of paper in their trays. Therefore, the following restrictions apply when using DCPS with this printer:

• It is not possible to select media by paper size.
• If paper of a different size than the default is loaded in a tray, its size will be considered as the default size. For example, if the default printer paper size is letter, a legal-size document will be truncated to letter size when printing on legal size paper.

To avoid printing on the wrong size paper, set the tray with the default paper size "unlocked" and set all other trays "locked".

18.14 HP Color LaserJet 2500

The HP LaserJet 2500 printer cannot detect the size of paper in its trays. Therefore, the following restrictions apply when using DCPS with this printer:

• It is not possible to select media by paper size.
• If paper of a different size than the default is loaded in a tray, its size will be considered as the default size. For example, if the default printer paper size is letter, a legal-size document will be truncated to letter size when printing on legal size paper.

Output trays STACKER and STAPLER refer to the same physical tray, included with the printer's optional finisher.

The preferred way to specify stapling is with the DCPS parameter STAPLE, which offers four different staple positions and takes page orientation into account when determining staple position. Therefore, when specifying stapled output with the STAPLE parameter, use OUTPUT_TRAY=STACKER.

If you specify OUTPUT_TRAY=STAPLER, the printer will staple output by default and place the staple in the printer's default staple position. Job burst and flag pages, if any, will be stapled to your job.

Not all staple positions are possible given the printer's paper feed direction and page orientation specified. Also, the HP LaserJet 9000 offers more possible stapling positions than the LaserJet 4200 and 4300 printers, which can staple only at the top left for portrait output and top right for landscape output.

18.16 HP LaserJet 8000, 8100 and 8150

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.

18.17 Lexmark Optra Rt+

The Optra Rt+ printer supports both the JIS and ISO standards for B5 paper sizes. DCPS handles the two B5 sizes as described in Section 18.11.1.

18.18 Lexmark Optra S

Lexmark Optra S printers can print paper sizes Otherenvelope and Universal. Otherenvelopetray (612 x 996) and Universal (612 x 1020) have different page sizes than Legal (612 x 1008). However, they have the same imageable area as Legal (600 x 996), so will be treated as the same size. Users wanting these sizes should specify PAGE_SIZE=LEGAL.

This appendix describes system messages issued by the DCPS software. These messages are identified by a facility code of DCPS. Refer to the OpenVMS System Messages: Companion Guide for Help Message Users for descriptions of other messages issued by the OpenVMS operating system or use the online help message utility with the command HELP /MESSAGE.

This appendix includes the following sections:

• System message overview, Section A.1
• Message descriptions, Section A.2
• Layup definition (BADLAYDEF) messages, Section A.3

DECprint Supervisor system messages are classified into two categories based on their destination. Some messages are sent to the system operator, others go to the user.

To receive user messages, use the /NOTIFY qualifier with the PRINT command. The messages are sent in response to your print request and in response to system conditions that affect your print request.

To receive operator messages, you need operator (OPER) privileges and must execute the REPLY/ENABLE=PRINTER command. You then receive the operator messages that apply to your host system.

DCPS system messages have one of the following formats:

%fac-s-ident, text
-fac-s-ident, text

Code	Meaning
%	The prefix for all primary messages
-	The prefix for all continuation messages
fac	The facility code, which should be DCPS
s	The severity level of the message
ident	An abbreviation of the message text
text	The expanded text of the message

A.1.2 Severity Level

The severity levels of DECprint Supervisor system messages are defined as follows:

Code	Meaning
S	Success --- successful completion of the request
I	Informational --- may require user action
W	Warning --- request may not have completed and may require user action
E	Error --- system encountered an error that may be recoverable
F	Fatal --- system encountered a fatal error and cannot continue processing this request

A.2 Message Descriptions

The following messages are alphabetized by the ident portion of the messages, ignoring any underscores ("_") that may be present. The message prefix, facility designation and severity code are not shown. If the facility designation is other than DCPS, refer to the OpenVMS System Messages: Companion Guide for Help Message Users for the message description or use the online help message utility with the command HELP /MESSAGE.

BAD_DATATYPE, Unexpected data type data-type at line n in DCPS$FILE_EXTENSION_DATA_TYPE file
Explanation: A data type given in the file SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT[_DEFAULT] was not expected. There will be no attempt to match the file extension to a data type.
User Action: The system manager should correct the problem data type in the file. The queue must be stopped (STOP/QUEUE/RESET) and started (START/QUEUE) for a new file to be read.

BAD_DEVCTL, Bad library device control specification --- string.
Explanation: This message appears when an error occurs in the specification of a component, indicated by string, in the logical device control library.
User Action: Change the specification and restart the queue.

BAD_FILETYPE, Unexpected file type file-extension at line n in DCPS$FILE_EXTENSION_DATA_TYPE
Explanation: A file extension given in the file SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT[_DEFAULT] was not expected. There will be no attempt to match the file extension to a data type.
User Action: The system manager should correct the problem file extension. The queue must be stopped (STOP/QUEUE/RESET) and started (START/QUEUE) for a new file to be read.

BADLAYDEF, condition on line line-number in layup definition
Explanation: There is an error in the layup definition file included with your print job.
User Action: See Section A.3 for a description of the text that can be displayed as the condition in a BADLAYDEF layup definition error message. Check the line in the layup definition file that is indicated in the error message.

BADLIBNAM_IGNOR, Bad library name library-name; ignored
Explanation: The print symbiont either did not find library-name in your library search list, or the syntax for the library was not correct.
User Action: Check the list of device control libraries defined in the search list in the printer startup file, SYS$STARTUP:DCPS$STARTUP.COM. Ensure that the libraries specified are in the SYS$LIBRARY directory.

BAD_LIBRARY_NAME, Bad library name library-name; used qualified-library-specification
Explanation: The library-name specified contained something different from the library file name.
User Action: Check the elements of the library search list in the SYS$STARTUP:DCPS$STARTUP.COM procedure. Include only library file names, without node names, device names, directory names, or file name extensions.

BADOPC, OPC belt is bad
Explanation: The OPC belt requires replacement.
User Action: Replace the OPC cartridge, carefully following the instructions in the LN03R ScriptPrinter Operator's Guide.

BADOPCTONERUFL, OPC belt is bad and or toner empty
Explanation: The toner cartridge is empty, or the OPC belt requires replacement, or both.
User Action: Replace both the toner cartridge and the OPC cartridge. Follow the directions in the respective replacement kits or refer to the procedures described in the LN03R ScriptPrinter Operator's Guide.

BAD_PUNCTUATION_GETTOKEN, Unexpected punctuation for a file type punctuation at line n in DCPS$FILE_EXTENSION_DATA_TYPE file
Explanation: The syntax of the file SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT[_DEFAULT] was not as expected. A comma (,) or colon (;) is expected to follow a file extension. There will be no attempt to match any file extension to a data type.
User Action: The system manager should correct the problem punctuation in the file. The queue must be stopped (STOP/QUEUE/RESET) and started (START/QUEUE) for a new file to be read.

BAD_PUNCTUATION_READDEF, Unexpected punctuation following a data type punctuation at line n in DCPS$FILE_EXTENSION_DATA_TYPE file
Explanation: The syntax of the file SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT[_DEFAULT] was not as expected. There will be no attempt to match any file extension to a data type.
User Action: The system manager should correct the problem punctuation in the file. A colon (:) is expected to follow a data type. The queue must be stopped (STOP/QUEUE/RESET) and started (START/QUEUE) for a new file to be read.

BADVMSVER, This product requires VMS version x.x or later to install
Explanation: The DCPS software requires that your system be running a version of the OpenVMS operating system that is later than the version it is currently running.
User Action: Upgrade your operating system to the correct version.

CANTCHECKPNT, Checkpointed job job number is requeued
Explanation: A print job was stopped and has been requeued. The job will print from the beginning.
User Action: Check the printed output. If it is not complete, resubmit the job.

CANTUSETRN, Translator from data-type to PostScript is unusable
Explanation: The translator generated a severe error and has been marked unusable. Subsequent jobs with data type data-type also incur this message and are placed on hold by the print symbiont.
User Action: Restart the print queue. This action loads a new copy of the translator. When the queue is restarted, release the jobs that were placed on hold. Report this problem to the HP Customer Support Center.

CFGERROR, configuration error: invalidmediumcode --- offending command is string
Explanation: The PostScript interpreter sensed this error while trying to execute the PostScript command represented by string.
User Action: If this error occurs during the printing of a file with a data type other than PostScript, an error exists in the translation process. If the translator is supplied by HP, report this problem to the HP Customer Support Center.

If the error occurs during the printing of a PostScript file, either the PostScript file or the program that generated the PostScript file is in error. Refer to the PostScript Language Reference Manual for help in locating the error. Resubmit the corrected file.

CMEMERR, Internal controller memory error
Explanation: The DECprint Supervisor has encountered a memory failure in the printer controller.
User Action: Call HP Customer Services. Refer to the LN03R ScriptPrinter Operator's Guide.

CONAPPLICATION, Connection request is not to a LAT applications port
Explanation: You requested a connection to a LAT applications port that the system does not recognize.
User Action: Specify the correct applications port name in the SYS$STARTUP:LAT$SYSTARTUP.COM procedure and restart the queue.

CONTERMINATED, Connection abnormally terminated
Explanation: Your network connection to the printer was terminated abnormally. For PrintServer printers, the printer was turned off or a cable was disconnected.
User Action: Make sure that the network device has power and that characteristics of the terminal server port that serves the printer agree with the characteristics listed in the Software Installation GuideSoftware Installation Guide. Restart the queue.

CONTIMEOUT, Connection timed out, server not available, or incorrect server name specified
Explanation: The connection timed out. You selected a server that was not available or you provided an incorrect server name. The timeout period is 5 seconds.
User Action: Specify the correct server name of an available server. Restart the queue.

DATAOVERUN, Data overrun
Explanation: This message indicates a communication error.
User Action: Set a lower baud rate for the printer.

DATA_TYPE_MISMATCH, file-tag tagged file being processed as data-type
Explanation: The file contained instructions indicating a data type different from the one that you included in the DATA_TYPE parameter.
User Action: The file is processed using a default data type. If it is the correct data type, your print job is processed successfully. If your print job is aborted, resubmit the files for printing and be sure to indicate the appropriate data type in the DATA_TYPE parameter.

DICTFULL, dictfull: No more room in dictionary --- offending command is string
Explanation: The PostScript interpreter sensed an error while trying to execute the PostScript command represented by string.
User Action: If this error occurs during the printing of a file with a data type other than PostScript, an error exists in the translation process. If the translator is supplied by HP, report this problem to the HP Customer Support Center.

If the message is displayed during the printing of a PostScript file, either the PostScript file or the application that generated the PostScript file is in error. If the application is supplied by HP, contact the HP Customer Support Center and submit a problem report.

DICTSTKOV, dictstackoverflow: Too many begins
Explanation: The PostScript interpreter sensed too many begins without corresponding ends.
User Action: If this error occurs during the printing of a file with a data type other than PostScript, an error exists in the translation process. If the translator is supplied by HP, contact the HP Customer Support Center and submit a problem report.

If the error occurs during the printing of a PostScript file, either the PostScript file or the application that generated the PostScript file is in error. If the application is supplied by HP, contact the HP Customer Support Center and submit a problem report.

DICTSTKUF, dictstackunderflow: Too many ends
Explanation: The PostScript interpreter sensed too many ends without corresponding begins.
User Action: If this error occurs during the printing of a file with a data type other than PostScript, an error exists in the translation process. If the translator is supplied by HP, contact the HP Customer Support Center and submit a problem report.

If the error occurs during the printing of a PostScript file, either the PostScript file or the application that generated the PostScript file is in error. If the application is supplied by HP, contact the HP Customer Support Center and submit a problem report.

DISABLED, PrintServer is currently disabled and cannot accept jobs
Explanation: You submitted a print job for a PrintServer printer that cannot accept jobs.
User Action: Enable job acceptance on that printer.

DPLXNOSUP, printer-name does not support duplex printing
Explanation: The printer does not support printing on two sides of the paper.
User Action: Resubmit your print job without asking for duplex printing or send it to a printer that supports duplex printing.

DPXFJAM, Please clear paper jam caused by DPX feed path
Explanation: The printer has a paper jam.
User Action: After you clear the paper jam, the print job will be continued.

DRIVEERR, Print Engine driving unit error --- FATAL ERROR
Explanation: The ScriptPrinter print driver has a fatal problem.
User Action: Call HP Customer Services. Refer to the chapter on service in the LN03R ScriptPrinter Operator's Guide.

DTSCOPEN, Print Engine developer tray/side cover is open
Explanation: The developer tray is open or the side cover is open.
User Action: Close the developer tray or the side cover.

EJECTJAM, Print engine paper eject section is jammed
Explanation: This is an LN03 Image printer message indicating that your printer has a paper jam in the paper eject section.
User Action: Clear the paper jam. Resubmit the current job.

ENVELDONTDUP, Envelopes cannot be printed duplex
Explanation: The print job requested an envelope paper size and either duplex or two-sided tumble printing.
User Action: You cannot print on both sides of the envelope. Resubmit the print request, changing the paper size requested (SHEET_SIZE, PAGE_SIZE, or INPUT_TRAY=ENVELOPE_FEEDER), or changing the page layout choice (SIDES parameter) to one-sided printing.

EXECSTKOV, Exec nesting is too deep --- offending command is string
Explanation: The PostScript interpreter sensed an error while trying to execute the PostScript command represented by string.
User Action: If this error occurs during the printing of a file with a data type other than PostScript, an error exists in the translation process. If the translator is supplied by HP, contact the HP Customer Support Center and submit a problem report.