Previous Contents Index


Appendix A
System Messages and Error Recovery

This appendix describes system messages issued by the DECprint Supervisor software. These messages are identified by a facility code of DCPS. Refer to the OpenVMS System Messages and Recovery Procedures Reference Manual for descriptions of other messages issued by the OpenVMS operating system.

This appendix includes the following sections:

A.1 System Message Overview

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.

Note

To system managers: To receive operator messages, ensure that OPCOM is running. Start OPCOM by issuing the command:


$ @SYS$SYSTEM:STARTUP OPCOM


Start OPCOM before executing the REPLY/ENABLE=PRINTER command.

A.1.1 Message Format

DECprint Supervisor 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 and Recovery Procedures Reference Manual for the message description.

If the User Action for a message calls for submitting an SPR (Software Performance Report), refer to Introduction to OpenVMS System Management for instructions.

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. Submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance Report (SPR).

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.

CMDREMOVED, Control command removed from file file-spec
DCPS-PLUS license required
Explanation: Control commands are removed from ANSI files when the DCPS-PLUS license is missing.
User Action: The DCPS-PLUS license must be activated in order to process control commands in ANSI files.

CMEMERR, Internal controller memory error
Explanation: The DECprint Supervisor has encountered a memory failure in the printer controller.
User Action: Call Compaq 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance 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 Compaq 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance Report.

EXITSRVR, exitserver has been executed --- permanent state may be changed
Explanation: The PostScript operator exitserver has been successfully executed. The permanent PostScript system parameters may have been altered.
User Action: No action is required.

EXTNFILEOPENERR, Cannot open file extension to data_type file DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT
Explanation: The DECprint Supervisor software could not find or open the file SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT. There will be no attempt to match a file extension to a data type.
User Action: The system manager should verify that no matching of file extension to data type is desired. If such matching is desired, a DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT should be restored from the installation, and a local site file (.DAT) created, if necessary. The queue must be stopped (STOP/QUEUE/RESET) and started (START/QUEUE) for a new file to be read.

EXTNFILEREADERR, Error reading file extension to data_type file DCPS$FILE_EXTENSION_DATA_TYPE.DAT[_DEFAULT]
Explanation: The DECprint Supervisor software could not read the file SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT[_DEFAULT]. There will be no attempt to match file extensions to data types.
User Action: The system manager should verify the integrity of this file. The queue must be stopped (STOP/QUEUE/RESET) and started (START/QUEUE) for a new file to be read.

FLUSHING, Rest of job (to EOJ) will be ignored
Explanation: An error or some other event caused the PostScript interpreter to ignore the rest of the job. This message is preceded by informational messages about the reason the job was aborted.
User Action: Check the other messages returned.

FONTNOTFOUND, Font font-name not found
Explanation: The font setup module specified by /PARAMETERS=FONTS_USED is not in the font library.
User Action: The file is printed without the requested font. If you are not satisfied with the output, then specify a font that is in the font library, or have the system manager install the missing font. (Refer to Appendix D for more information about ordering optional font kits.)

FPGGTPPS, First page > pages per sheet. First page set to 1.
Explanation: Your print job includes a layup definition file that uses the FIRSTPAGE and PAGESPERSHEET options. However, the FIRSTPAGE option requests that the first page be printed in a page spot that is beyond the number specified with the PAGESPERSHEET option.
User Action: No action is required if you want the pages to be printed at the page spots given with the PAGESPERSHEET layup option. For example, if PAGESPERSHEET=5, the first page on the first sheet will print in the fifth page spot. If you want a different spot, edit the layup definition file and resubmit your print job.

FTLDEVCTL, Fatal device control library problem. Config error: configuration error on printer-name
Explanation: The device control library has a fatal error.
User Action: Submit a Software Performance Report (SPR).

FUSCOPEN, Print Engine fuser cover is open
Explanation: This message is sent when the paper exit cover is open.
User Action: Close the paper exit cover.

FUSINGERR, Print Engine fusing error --- FATAL ERROR
Explanation: There is a fatal error in the fusing mechanism.
User Action: Call Compaq Customer Services. See the printer operator's guide for information.

HANGUP, Data set hang-up
Explanation: The printer was power-cycled during a print job and therefore the job is aborted.
User Action: Resubmit the lost print job. Subsequent jobs will print normally.

ILLEGAL_CHAR, Illegal character character 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 expected. There will be no attempt to match file extensions to data types.
User Action: The system manager should correct the problem in the file. The queue must be stopped (STOP/QUEUE/RESET) and started (START/QUEUE) for a new file to be read.

INTERNAL_ERROR, Internal error number detected, cannot continue
Explanation: A fatal internal error identified by number has occurred.
User Action: Submit a Software Performance Report (SPR). Include the number from the error message in your report.

INTERUPT, Interrupt: The job has been interrupted
Explanation: The PostScript interpreter sensed an external request to interrupt the PostScript program. This message is displayed as part of the Abort process.
User Action: None. This message confirms a requested action.

INTRAYNOTAVL, No tray-name is installed on printer-name
Explanation: The specified input tray is not currently installed on the printer.
User Action: Install the required input tray and resubmit the print job, or resubmit the print job specifying an input tray that is installed.

INTRAYNOTSUP, No tray-name on printer-name
Explanation: The specified input tray is not supported by the printer.
User Action: Resubmit the print job, specifying an input tray that is supported on the printer, or specifying a printer that supports the required input tray.

INVACC, invalidaccess: Attempt to store into read-only object --- 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance Report.

INVDDIFDATA, Invalid DDIF data, flushing to end of file
Explanation: Your file contains unsupported DDIF data.
User Action: Make sure that your file contains only DDIF tags from the image data subset. Then resubmit the job.

INVDDIFFILE, File is not in DDIF format
Explanation: You submitted a file for printing with the DATA_TYPE=DDIF parameter but the file did not contain DDIF tags.
User Action: Resubmit your printing job with the proper DATA_TYPE parameter.

INVEXIT, invalidexit: Exit not in loop
Explanation: The PostScript interpreter sensed an error while trying to execute the PostScript operator exitserver.
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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance Report.

INVFILACC, invalidfileaccess: Bad file access string --- 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance Report.

INVFONT, invalidfont: Bad font name or 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance Report.

INVIMGPRM, Invalid DDIF image parameters, image frame ignored
Explanation: Your file contains unsupported image parameters.
User Action: Correct your file to include supported image parameters and resubmit the job.

INVREST, invalidrestore: Improper restore --- 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 Compaq, submit a Software Performance Report (SPR).

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 Compaq, submit a Software Performance Report.

IOERROR, System I/O error occurred --- offending command is string
Explanation: The ScriptPrinter printer sensed an I/O error as a result of a communication fault.
User Action: Resubmit the job to be printed. If the error occurs again, examine the communications line for hardware, data rate, or parity/framing problems.

IPHOSTUNKNOWN, unknown or invalid internet host
Explanation: The printer's internet host name is unknown or invalid.
User Action: Check that you have specified the correct host name. If it is correct, see if the ping internet host utility can communicate with the printer. You may have a problem with your network or name server. If the problem has occurred since your system was rebooted, ensure that the DCPS$STARTUP.COM procedure has commands to initialize the associated DCPS queue, and that DCPS$STARTUP.COM will run whenever your system reboots.

ITCOPN, Print engine paper input tray cover is open
Explanation: The paper input tray is open.
User Action: Close the paper input tray cover.

JOBABORT, Job job-number aborted
Explanation: The specified job was terminated for one of the following reasons. Take the actions recommended for the appropriate problem:

JOBFINISH, Job job-number finish
Explanation: The entire print job has been processed by the DECprint Supervisor software. This does not necessarily mean the print job has finished printing.
User Action: None.

JOB_ID, for job job-name (queue queue-name, entry job-number) on execution-queue-name
Explanation: Informational message received when you include the /NOTIFY qualifier with the PRINT command. This message provides you with more information about the previously displayed message.
User Action: None.

JOBSTART, Job job-number start
Explanation: Connection to the printer has been established and the printer is now printing the job.
User Action: None.

KEYNOTREC, The keyword value in the /PARAMETERS qualifier was not recognized
Explanation: The DECprint Supervisor software detected an invalid keyword in the /PARAMETERS qualifier of the PRINT command.
User Action: Check the syntax of the parameter you entered. Resubmit the print request with the correct keyword.

KIT_EXPIRED, This version of DCPS has expired
Explanation: The version of DCPS you are running is a field test version and has expired.
User Action: Upgrade your system to a released version, or later field test version, of DCPS.

LAYUPIGNORED, layup_definition parameter ignored, since Number_Up=0 was specified
Explanation: You specified NUMBER_UP=0 with layup definition, which disables layup.
User Action: If you want to use a layup definition file, specify a nonzero value for NUMBER_UP or do not use the NUMBER_UP parameter. The default is NUMBER_UP=1.

LAYUPOPENERR, Can't open layup definition file file-name
Explanation: The layup definition file you specified in the PRINT command is not in the DCPS$LAYUP directory, or the DCPS$LAYUP logical is not defined.
User Action: Check the spelling of the layup definition file name and try the command again.

LAYUPREADERR, Read error on layup definition file file-name
Explanation: The layup definition file you specified in the PRINT command is not in DCPS$LAYUP, or DCPS$LAYUP is not defined.
User Action: Check the spelling of the layup definition file name and try the command again.

LIMCHK, limitcheck: Implementation limit exceeded --- 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 Compaq, submit a Software Performance Report (SPR).


Previous Next Contents Index