DECdocument
Command Summary and
Processing Messages
Previous Contents Index

2.4 Device Converter Messages

BADFILABORT, file bad---aborting run

Error: The device converter cannot use the font file named in an adjacent message.
User Action: Another file may have been given the same name. Use the DIRECTORY/FULL DCL command to see that the size and format are similar to other font files. If necessary, reinstall the font data.
BADFONT, font file bad---using blanks

Warning: The file that describes the font design is unusable. The program will substitute blanks for the characters in this font.
User Action: Use the DIRECTORY/FULL DCL command to see if the size and format of this file resembles other font files. If necessary, reinstall the font data.
BADFONTSIZE, internal font error: font string scaled size out of range.

Error: The device converter has detected a font size that is out of range. This may be a problem with the font file itself, or an internal device converter problem.
User Action: None.
BADINCDVI, bad file format or error in reading included DVI file filespec

Error: The device converter has encountered a read error or illegal file format in an included DVI file. See the previous message.
User Action: Regenerate the DVI file by running Document again.
BADINCLUDE, included file is bad

Warning: The program has encountered errors in processing the contents or index file requested.
User Action: Check that previous processing steps generated the contents or index file expected, because the included file may be an old, incompatible file, it may be another file with the same name, or it may be the correct file made unreadable because of an I/O error.
BADMETRIC, bad metric file

Error: The device converter has encountered errors in processing the indicated font metric file.
User Action: This may be another file named the same. Check the file size and format with the DIRECTORY/FULL DCL command to see if it resembles other font metric files. If necessary, reinstall the font data.
BADPAPERSIZE, illegal papersize string string, ignored

Warning: An unsupported papersize string was encountered from the design file.
User Action: Correct the design to specify one of the accepted papersizes.
BADPOSTAMBLE, error in postamble of file string

Error: The device converter encountered a read or file format error in the postamble of the named file.
User Action: None.
BADPOSTFORMAT, illegal postamble format

Error: The device converter encountered a read or file format error in the postamble of the named file.
User Action: None.
BADPREAMBLE, error in DVI file's preamble.

Error: The device converter cannot accept the DVI file's preamble.
User Action: Regenerate the DVI file by running Document again.
BADPRIMDVI, bad file format or error reading primary DVI file: filespec

Error: The device converter has encountered a read error or illegal file format in the primary DVI file. See the previous message.
User Action: Regenerate the DVI file by running Document again.
BADPXLFILE, bad file format or error in reading PXL bitmap font file filespec

Error: The device converter encountered a read error or illegal file format in trying to read metrics or bitmap data for a PXL bitmap font.
User Action: Reinstall the font data.
BADSPECIAL, unknown DVI file special command code encountered.

Error: The special command code read does not match any existing defined specials.
User Action: None.
BOOKABORT, aborting run---book string not created

Error: The device converter received a fatal error; no DECW$BOOK file is made.
User Action: Check the previous message to see what caused the fatal condition.
BOOKBUILT, book was successfully built

Informational: The book was completed without any fatal errors.
User Action: None.
CANNOTCONNECT, cannot connect along a diagonal

Warning: While attempting to draw change bars, the program has encountered an attempt to draw a nonvertical line. Only vertical change bars are allowed.
User Action: Look in the macros that describe change bar positioning for errors and inconsistencies.
CANNOTCREATE, cannot create output file

Error: The program cannot create an output file.
User Action: Check that the output directory exists, that the user has permission to write in it, and that the device is available and is not full.
CANNOTOPEN, cannot open input file

Error: The program cannot open the input DVI file.
User Action: Check that the input directory exists, that the file exists or was created by earlier processing steps, that the user has permission to read the file, and that the device is available.
CANTCREATE, cannot create output file filespec

Error: The device converter cannot open the named file for write.
User Action: See next message.
CANTOPEN, cannot open file filespec

Error: The device converter was unable to open the named file.
User Action: None.
CONFIGERROR, error in configuration file

Error: An error has been detected in reading the file that describes PostScript fonts. An adjacent error message gives more details.
User Action: Check that the device is available and that the user has permission to read the file. Take the action suggested by the adjacent error message. If necessary, reinstall the font data.
DIFPAPERSIZE, papersize in design but already specified on cmd line, using cmd line value string

Warning: A papersize option was encountered both on the command line and in the design file. The command line value will be used.
User Action: Specify the desired papersize in the design file.
DOCSETUP, error in generating document setup area.

Error: The device converter experienced a fatal error while attempting to generate the document setup area, which contains all of the font definitions needed in the document.
User Action: See adjacent messages.
DVIEOF, premature end-of-file in DVI file filespec

Error: The device converter encountered a premature end-of-file while reading the named DVI file.
User Action: Regenerate the DVI file by running Document again.
EXTNESTING, Extensions are being nested

Informational: Extensions are being nested.
User Action: This is not supported. Check the output carefully.
HOTSPOTERR, HOTSPOT crosses Tex page boundary: string

Informational: Gives the symbolic name of reference and the last chunk title that was defined.
User Action: Using the symbolic name and the title locate the reference being broken up by the page break and insert an <ONLINE_CHUNK> tag before it.
EXTNESTING, Extensions are being nested

Informational: Extensions are being nested.
User Action: This is not supported. Check the output carefully.
HOTSPOTERR, HOTSPOT crosses Tex page boundary: string

Informational: Gives the symbolic name of reference and the last chunk title that was defined.
User Action: Using the symbolic name and the title locate the reference being broken up by the page break and insert an <ONLINE_CHUNK> tag before it.
FCCANTOPEN, cannot open font configuration file filespec

Error: The device converter was unable to open the named file.
User Action: None.
FIGFILERR, Error encountered while reading: filespec

Informational: An error was returned when reading the figure file.
User Action: Check to make sure the figure is not corrupted.
FIGFILOPN, cannot open figure file

Warning: The program cannot find the figure file named, or can find it but cannot open it.
User Action: Check that you have specified the right filespec, that the file exists in the path specified (or in the current default directory, if no path is specified), that you have permission to read that file, and that the file is not locked by the action of some other program running at the same time.
FIGNOTFND, cannot find figure image in figure file

Warning: The figure file named in an adjacent message does not contain the proper codes to identify the type of figure expected. White space appears where the figure would be placed.
User Action: Check the figure file.
FILEI, error in reading file filespec

Error: The device converter encountered an error while reading the named file.
User Action: None.
FILENESTING, one included file cannot include another file

Warning: One contents or index file may not include another.
User Action: Check the macros that describe contents and index files to see that they are correctly generating the filespecs. Check that the filespec generated for the contents or index file is the same as an existing file.
FILEO, error in writing file filespec

Error: The device converter encountered an error while writing to the named file.
User Action: None.
FNTCONFIG, description for font string missing or illegal in configuration file.

Error: The specified font is not present, or not fully described, in the file that describes PostScript fonts.
User Action: If necessary, reinstall the PostScript support.
FNTFILEREF, font referenced in file filespec

Error: The named DVI file contains a reference to the above font.
User Action: None.
FONTCONFIG, Font description missing or illegal in configuration file

Error: The specified font is not present, or not fully described, in the file that describes PostScript fonts.
User Action: If necessary, reinstall the PostScript support.
FONTERROR, error in font string

Warning: An error has occurred while processing the named font. The specific problem is identified in an adjacent message.
User Action: Note the name of the font. Take the action suggested by the adjacent error message.
FONTTOOBIG, too many characters in font---limit is 188

Error: The document uses too many characters from the named font.
User Action: Reinstall the font files. If the problem persists, and if you are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.
FSEEK, fseek internal error, file = string

Error: The device converter encountered an internal error while attempting to fseek in the named file.
User Action: None.
IDENT, string

Informational: Reports the version of the program in use.
User Action: None.
IGNORING, ignoring included input file filespec

Warning: The program cannot process the included DVI file for the reason specified in an adjacent message.
User Action: Note the name of the file. Take the action suggested by the adjacent error message.
INCDVICANTOPEN, cannot open included DVI file filespec

Warning: The device converter was unable to open the named file.
User Action: None.
INCLUDED, File filespec was successfully included

Informational: The named file was succesfully read and stored
User Action: None.
INCLUDING, including input file: filespec

Informational: Reports that the program is processing a DVI file other than the file named on the command line. The file is typically a contents or index file.
User Action: None.
INITMEM, ran out of memory while initializing device converter

Error: This memory error occured very early in the device conversion.
User Action: None.
INPUTBAD, bad input file---aborting run

Error: The program has encountered errors in the named input file and cannot continue.
User Action: Check the messages generated by earlier processing steps to see if a complete DVI file was created.
INPUTFILE, input file is: filespec

Informational: Reports the name of the primary DVI file, that is, the file named on the command line.
User Action: None.
INTERNALERROR, internal error

Error: A problem internal to the device converter prevents it from continuing.)
User Action: This sometimes represents a document so large or complex that it exceeds internal buffer sizes. Sometimes you can work around this by running contents and index processing as separate jobs, rather than including them in place. You may be able to process the document in two or more pieces by using the STARTING_PAGE and ENDING_PAGE or NUMBER_OF_PAGES parameters to the device converter. If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.
INVALIDDATE, Invalid date specification. Use the dd-mm-yyyy format

Error: The converter has found an invalid date specification.
User Action: use the dd-mm-yyyy format to specify the date
INVALIDOPTN, invalid option

Error: This DVI special command contains an option not supported by this device converter, or the program cannot find an option at all.
User Action: Check to see if you have requested a figure file, contents file, index file, change bars, or other function which is not supported for this destination; check for errors in the macros that generate this special command; check if the special has all required arguments
INVALIDPOINT, invalid point number number

Warning: An error has occurred in the macros used to describe change bars. Specifically, an attempt has been made to locate a point off the page, or the point is incorrectly described.
User Action: Look in the macros that describe change bar positioning for errors and inconsistencies.
IN_CANTCLOSE, cannot close input file filespec

Warning: Error in closing the file. Processing continues.
User Action: None.
NOCONTENTS, no contents file found - verify that 1 - The command line has/CONTENTS specified2 - The document has a CONTENTS_FILE tag.

Error: No contents file was processed, which causes a fatal error in bookbuilding for the Bookreader.
User Action: Make sure there is a contents file and that it is included.
NOFILABORT, cannot open file---aborting run

Error: The device converter cannot open the named file.
User Action: Check to see that the device is available, that the file exists, and that the user has privileges to access that file.
NOFONT, cannot open font file---using blanks

Warning: The device converter cannot open the named font file.
User Action: Check that the device exists and is available, and that the user has permission to read the file.
NOFONTDEF, no font defined for font select string

Error: none.
User Action: None.
NOINCLUDE, cannot open included file

Warning: The device converter cannot open the contents or index file named in the adjacent message. Either the pathname and filename are incorrect, or the program cannot gain access because of file protection or locking by another process. Processing will continue without this file.
User Action: Check that the named file exists and that the user has access to it.
NOINPUTPAGE, no pages in input file

Error: The input file named in an adjacent message contains no pages; therefore, there will be no output to print.
User Action: Check to see if errors reported in earlier processes caused there to be no pages generated.
NOMETRIC, cannot open metric file

Error: The font metric file named in an adjacent message does not exist, or the user does not have access to it because of file protection or problems with the device.
User Action: Check that the file exists and is available, and that the user has access to it. Check that the user is specifying a DVI input file appropriate for the destination requested.
NOSIXELIMAGE, cannot find sixel image in figure file

Warning: The figure file named in an adjacent message does not contain the command sequence that identifies a sixel image. White space appears where the figure is expected.
User Action: Check the figure file. For LN03 use, it must be a sixel file.
NOSUBSTITUTE, no adequate alternate font found

Error: The text formatter has requested a down-loaded font for which the device converter cannot find a reasonable substitute.
User Action: Check the document design for the fonts used. Check that the corresponding font files exist at the sizes desired.
NOSUCHUNIT, no such unit of measure

Warning: A DVI special command used to position change bars or describe graphics files contains an unknown unit of measure, or no unit.
User Action: Check the macros that describe change bar positioning or figure file characteristics for errors.
OFFPAGE, cannot set text outside page boundaries

Warning: An attempt has been made to set text outside the boundaries of the physical page specified.
User Action: Check the messages from the text formatter for lines too long, that you specified a destination that can print a page as large as required by your design. Also, check to see if you specified a horizontal or vertical offset that will push your design off the page.
ONPAGE, on page [string]

Informational: Reports the number of the output page on which the condition reported in the associated messages occurred.
User Action: Note this page number if you need to refer to the output.
OUTPUTFAIL, error writing to output file

Error: The program encountered an error in writing to the output file. This usually means that the output disk is full, the user's disk quota is exceeded, or the output disk has become unusable.
User Action: Check that the output device is usable. If the disk is full or the user's disk quota is used up, delete unwanted files and run the device converter again.
OUT_CANTCLOSE, cannot close output file filespec

Warning: Error in closing the file. Processing continues.
User Action: None.
PAGECOORDLOST, PAGE COORDINATION LOST string

Error: The converter has found a page coordination problem.
User Action: Make sure that two contents files are not being included and that there are no undefined symbols reported.
PAGENOTFOUND, starting page not found

Error: The user has specified a starting page number, but that page does not exist in the input file.
User Action: Check the starting page specified and the input file specified.
PAGESOUT, number page(s) written to file: filespec

Informational: This reports the number of pages written to the output file named.
User Action: No direct action needed; however, if the number is zero or less than expected, check other messages for errors or examine the commands, filespecs, options, and input files for problems.
PAGETOOCOMPLEX, cannot hold all font data---using blanks

Warning: The amount of font data required to describe all the characters on this page will not fit in the LN03 font memory, so the characters in the current font will be represented as blanks.
User Action: If using a design that allows you to change text_size, choose a smaller size, or use only one kind of emphasis on the page, if possible, or move portions of the text to adjacent pages.
PASS1INCFNAMS, error on first pass through primary DVI file.

Error: The device converter experienced a fatal error on its first pass through the primary DVI file in which it was attempting to generate a list of included filenames.
User Action: See adjacent messages.
PFCANTOPEN, cannot open included ps plotfile filespec

Warning: The device converter was unable to open the named file.
User Action: None.
PLOTFILEFAIL, cannot open figure file

Warning: The program cannot find the figure file named, or can find it but cannot open it.
User Action: Check that you have specified the right filespec, that the file exists in the path specified (or current default directory, if no path is specified), that you have permission to read that file, and that the file is not locked by the action of some other program running at the same time.
PRIMDVICANTOPEN, cannot open primary DVI file filespec

Error: The device converter was unable to open the named file.
User Action: None.
PROLOGERROR, error in prolog file

Error: The device converter cannot read its file that contains the PostScript prolog for output.
User Action: Check that the device is available, that the file exists, and that the user has privileges to access the file. If necessary, reinstall the PostScript support.
READFCMEM, ran out of memory while reading the font configuration file

Error: This memory error occured early in the device conversion.
User Action: None.
SHELFBUILT, shelf was successfully built

Informational: The shelf was completed without any fatal errors.
User Action: None.
SPECIALERROR, error in \special string

Warning: This lists the text of a DVI special command as received by the device converter. This command is generated by macros, but may contain some user-specified information, such as a filespec or size. The specific problem associated with this special is described in an adjacent message.
User Action: See the adjacent message for a description of the problem. If necessary, check this message for a filespec or size that may have been incorrectly entered in a tag describing a figure file, contents file, or index file.
SPECTOOLONG, \special too long---will try to process anyway

Warning: This DVI special command exceeds the maximum length of 1000 characters. The program will truncate the command and try to process it.
User Action: Check the macros that generate this special command; they may be appending too many spaces or extraneous text following the command.
TITLETOOLONG, Title has been truncated to 256 characters

Informational: The chunk title is limited to 256 characters
User Action: Use shorter titles that will fit in the window.
TOLONG, device & directory spec too long cannot exceed 48 characters

Error: the complete file spec is too long.
User Action: Move the files to the directory where the device and directory specs total length is 48 characters or less.
TOOMANYDVI, too many included input files

Warning: Too many included contents or index files have been requested.
User Action: Remove excess <CONTENTS_FILE> and <INDEX_FILE> tags from the input file.
TOOMANYFONTS, too many fonts---limit is 100

Error: The document contains too many fonts.
User Action: Change the document design so it does not require so many fonts, or use SDML tags that do not require so many fonts, or break the document into separate documents, or process the contents or index separately.
TOOMANYGLYPHS, too many glyphs used in all fonts combined

Error: The document contains too many characters in too many fonts. The LN03 cannot hold this many characters.
User Action: Break the device conversion of this document into two or more jobs, specifying the starting page and ending page or number of pages. End one job before the page on which this error was reported.
UNDEFSYM, string

Error: A reference to an undefined symbol was detected.
User Action: Check that symbol names in references are legitimate.
UNRECOGOPTN, unrecognized option

Warning: This DVI special command contains an option not supported by this device converter, or the program cannot find an option at all.
User Action: Check to see if you have requested a figure file, contents file, index file, change bars, or other function that is not supported for this destination. Check for errors in the macros that generate this special command.
VMBADFREE, Internal device converter error, failure to deallocate virtual memory

Error: The device converter has failed while trying to deallocate virtual memory.
User Action: Review any related informational messages, correct the problem, and reexecute the DOCUMENT command. If you are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.
VMOVRFLOW, Internal device converter error, failure to allocate additional virtual memory

Error: The device converter has failed while trying to allocate additional virtual memory.
User Action: Review any related informational messages, correct the problem, and reexecute the DOCUMENT command. This error may be caused by the user having too small of a pagefile quota (PGFLQUO). If so, increase this value and reexecute the DOCUMENT command. If you are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

Previous Next Contents Index