DECdocument
Command Summary and
Processing Messages

If more than one name is truncated, the shortened names may not be unique and other errors may occur depending on the type of name.
User Action: Shorten this name (and any other names that are too long) to 31 characters or less, so that there is no potential for other errors.

NESTEDCOM, A <COMMENT> tag on line number of file filename is nested within <COMMENT>...<ENDCOMMENT> that starts on line number of file filename

Warning: <COMMENT> tags cannot be nested.

Sometimes an error is made in typing a <COMMENT> tag in the format <COMMENT>(text). The typing erro makes it appear that the tag does not have an argument list, and it is assumed that an <ENDCOMMENT> tag is present to end the comment text. During the search for the <ENDCOMMENT> tag, if another <COMMENT> tag is encountered it will appear to be nested within the first <COMMENT> tag's text.
User Action: Correct any typographical errors in the initial <COMMENT> tag or remove the nested <COMMENT> tag.

NOBCKNOTE, at tag or text, line n, file file-spec Accumulated back notes not referenced. Notes will not be output

Warning: A document contained <BACK_NOTE> tags, but no corresponding <BACK_NOTES> tag was specified to output the accumulated notes.
User Action: Place the <BACK_NOTES> tag in the source file at the position at which you want them output.

NOBIBNOTE, at tag or text, line n, file file-spec Accumulated bibliographic notes not referenced. Notes will not be output

Warning: A document contained <BIB_NOTE> tags, but no corresponding <BIB_NOTES> tag was specified to output the accumulated notes.
User Action: Place the <BIB_NOTES> tag in the source file at the position at which you want them output.

NOCONFILE, at tag or text, line n, file file-spec <CONTENTS_FILE> tag specified without /CONTENTS qualifier. No new file will be generated.

Warning: A <CONTENTS_FILE> tag was encountered in the input file, but the corresponding /CONTENTS qualifier was not present on the command line. No new contents file will be produced. An earlier version of a contents file, if it exists, may be included in the output.
User Action: If you want to include a current table of contents file, you should reissue the DOCUMENT command using the /CONTENTS qualifier.

NODEFITEM, at tag or text, line n, file file-spec Definition list specified no items before <tagname>.

Warning: A <DEFINITION_LIST> tag, or a corresponding tag in the SOFTWARE doctype, was specified but no <DEFLIST_ITEM>/<DEFLIST_DEF> tags were specified for the list. No output will be produced.
User Action: Remove the definition list start/end tags or provide item text for the definition list.

NOENDPROF, at tag or text, line n, file file-spec The <PROFILE> tag was not terminated by an <ENDPROFILE> tag

Warning: In order for the book build process to be completed, the <PROFILE> tag must be terminated by an <ENDPROFILE> tag. The <ENDPROFILE> tag is supplied by default in this case.
User Action: If the <PROFILE> tag is not terminated by an <ENDPROFILE> tag, add one after the final <ELEMENT> or <INCLUDES_FILE> tag.

NOFIGELMS, at tag or text, line n, file file-spec <tagname> has no elements.

Warning: A <FIGURE> or <EXAMPLE> tag was specified and terminated but there were no elements (for example, <FIGURE_SPACE>) to place in the figure.
User Action: Verify that you correctly spelled and entered tags for the figure or example.

NOHIDERVL, at tag or text, line n, file file-spec Ignoring request to hide the <REVEAL_TAGS> tag

Warning: The <REVEAL_TAGS> built-in tag cannot be hidden by the action of a <HIDE_TAGS> built-in tag.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

NOINXFILE, at tag or text, line n, file file-spec <INDEX_FILE> tag specified without /INDEX qualifier. No new file will be generated.

Warning: An <INDEX_FILE> tag was encountered in the input file, but the corresponding /INDEX qualifier was not present on the command line. No new index file will be produced. An earlier version of an index file, if it exists, may be included in the output.
User Action: If you want to include a current index file, you should reissue the DOCUMENT command using the /INDEX qualifier.

NONESTING, at tag or text, line n, file file-spec Invalid attempt to nest tag <tagname>. Ignored

Warning: A tag is referenced when its context is already active. For example, this message is issued when <CODE_EXAMPLE> is specified when a previous <CODE_EXAMPLE> is not terminated.
User Action: The indicated tag is ignored; however, you should verify your source file to determine whether the tag is a duplicate or whether, in fact, you did not terminate an earlier occurrence of the same tag.

NONEWFILE, at tag or text, line n, file file-spec <tagname> specified without string. No new file will be generated.

Warning: A <CONTENTS_FILE> or <INDEX_FILE> was encountered in the input file, but the corresponding /CONTENTS or /INDEX qualifier was not present on the command line. No new contents or index will be produced. An earlier version of a contents or index file, if it exists, may be included in the output.
User Action: If you want to include the current table of contents or index file, you should reissue the DOCUMENT command using the appropriate qualifier.

NOPROFILE, at tag or text, line n, file file-spec Tag can appear only following a <PROFILE> tag

Fatal: The tag is part of a profile and can be used only in that context and only within the same file as the <PROFILE> tag.
User Action: Check that the tag appears after a <PROFILE> tag and in the same file as the <PROFILE> tag.

NOREADOUT, at tag or text, line n, file file-spec Cannot read from file: filename The file is opened as output

Warning: A <READ> built-in tag cannot be addressed to an auxiliary file that is opened as output. (The <OPEN> tag defaults to output mode unless INPUT is specified.)
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

NOREFNOTE, at tag or text, line n, file file-spec Accumulated reference notes not referenced. Notes will not be output

Warning: A document contained <REF_NOTE> tags, but no corresponding <REF_NOTES> tag was specified to output the accumulated notes.
User Action: Place the <REF_NOTES> tag in the source file at the position at which you want them output.

NOTDOCTYP, at tag or text, line n, file file-spec Tag <tagname> is not allowed in the string doctype

Error: The indicated tag is not meaningful in the context of the doctype specified on the command line and cannot be processed. For example, the LETTER doctype does not allow <CHAPTER> or heading-level tags.
User Action: Verify that you specify the correct doctype keyword on the DOCUMENT command line. If the doctype is correct, remove the tags from the SDML source file.

NOTHIDNAM, at tag or text, line n, file file-spec A <REVEAL_TAGS> tag is referencing an unknown hide-name, string

Warning: The hide-name specified by a <REVEAL_TAGS> tag is not in use.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

NOTINELEM, at tag or text, line n, file file-spec Tag can appear only within the context established by an element heading tag such as <CHAPTER>, <PART>, and so forth.

Error: When a book build is done, all text and the tags that accompany the text must appear within some element of the book. The text and tags must follow the element heading tag in order to be considered to be in the context of the element.
User Action: Correct the source text so that the tag that is in error follows a tag that heads an element of the book.

NOTINPROF, at tag or text, line n, file file-spec The <tagname> tag must appear in the same file as the <PROFILE> tag

Error: All the tags that make up a profile must appear in the same file.
User Action: Move the tag into the same file as the <PROFILE> tag.

NOUNDEFBI, at tag or text, line n, file file-spec Ignoring <UNDEFINE> or <REDEFINE> of the built-in definition of <tagname>

Warning: A tag translator built-in tag cannot be deleted by the action of a <REDEFINE> or <UNDEFINE>. The built-in tag can be "stacked" by issuing a <DEFINE> tag for it, however.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

NOWRITEIN, at tag or text, line n, file file-spec Cannot write to file: filename The file is opened as input

Warning: The <WRITE> built-in tag cannot write to an auxiliary file that has been explicitly opened as input.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

NOZONEYET, at tag or text, line n, file file-spec Tag <tagname> specified outside its valid zone or context. It must be preceded by tag<tagname>.

Error: A tag was specified outside the context that enables it, for example, a <COPYRIGHT_PAGE> tag was specified when the tag <FRONT_MATTER> has not been specified to enable the front matter zone.
User Action: Be sure that you have specified the correct tag. Add the appropriate zone-enabling tag.

NO_OUTPUT, No output is produced for this tag

Informational: This message accompanies other warning messages. It indicates that the tag is being ignored and no output is produced.
User Action: Correct the SDML file to remove the other warning messages.

NO_PREFIX, at tag or text, line n, file file-spec No character string prefix is available.

Warning: A tag in a template specified that a character-string prefix was to be used for page or formal element numbering, but no prefix was specified.
User Action: Specify a prefix for the section in the <SET_TEMPLATE_PREFIX> tag.

NUMBERARG, at tag or text, line n, file file-spec Argument number is not valid for <tagname>.

Warning: The numeric argument is not valid for the tag.
User Action: Consult the tag's documentation to determine the valid values.

NUMLTZERO, The argument is less than 0.

Informational: This message accompanies a message about an invalid numeric argument. It indicates that a negative value was specified for a tag argument which must be a positive number.
User Action: Consult the documentation to determine the tag's valid values.

O_ARGNTNM, at tag or text, line n, file file-spec Argument number to tag <tagname> is not a valid name

Error: The indicated argument does not obey the rules for formation of a name. A name can have only letters, numbers, and underscores and a name cannot begin with two underscores. You can use spaces, tabs, and carriage returns.
User Action: Correct the argument so that the name is valid.

O_DFINTAG, at tag or text, line n, file file-spec A <DEFINE> tag should be removed from this file. Consider using a <DEFINE_SYMBOL> tag in its place.

Fatal: The definition of the <DEFINE> tag will not appear in the modified source file.
User Action: Tag definitions should be in separate files called with the /SYMBOLS qualifier on the command line.

O_FNOTPRB, at tag or text, line n, file file-spec Possible problem with footnotes

Warning: The software has detected a possible problem with footnotes.
User Action: Check to ensure that all footnotes are coded correctly.

O_IGNRTAG, at tag or text, line n, file file-spec Ignoring <tagname>. You have specified multiple <tagname> tags with the MASTER argument, ignoring all but the first tag.

Warning: Multiple <SET_ONLINE_TOPIC> tags with the MASTER argument have been specified.
User Action: Remove the extra <SET_ONLINE_TOPIC> tags.

O_TAGMISN, at tag or text, line n, file file-spec Tag <tagname> is missing

Warning: A Bookreader <ONLINE_PART_NUMBER> tag is missing.
User Action: Check to ensure that the <ONLINE_PART_NUMBER> tag exists if it is required for your document.

O_TMNYXTR, at tag or text, line n, file file-spec More than 25 characters in argument to tag <tagname>.

Fatal: There is a limit of 25 characters in the argument to the <SYMBOL_PREFIX> tag.
User Action: Check to ensure that the argument to the <SYMBOL_PREFIX> tag has no more than 25 characters.

OBKSYMMSG, at tag or text, line n, file file-spec Book does not contain a valid book symbol name.

Warning: The book is missing a valid book symbol name.
User Action: Check to ensure that the <ONLINE_INFO_SYMBOL> tag exists if it is required for your document.

OCONTOMNY, at tag or text, line n, file file-spec Too many <tagname> tags.

Fatal: Too many <CONTENTS_FILE> tags have been defined for this document.
User Action: Bookreader documents are limited to one <CONTENTS_FILE> tag. Check for too many <CONTENTS_FILE> tags.

OENONSTNG, at tag or text, line n, file file-spec Invalid attempt to nest tag <tagname>.

Error: A tag is referenced when its context is already active. For example, this message is issued when an <ONLINE_POPUP> tag exists after a previous <ONLINE_POPUP> tag that you did not terminate.
User Action: The indicated tag is ignored; however, you should verify your source file to determine whether the tag is a duplicate or whether, in fact, you did not terminate an earlier occurrence of the same tag.

OESYMISNG, at tag or text, line n, file file-spec Missing symbol argument to a <tagname> tag. Symbol names are required when referencing headings, formal tables, examples, and figures.

Error: Symbols are required when referencing headings, formal tables, examples, and figures in Bookreader doctypes.
User Action: Supply a symbol name as an argument to the tag. You may want to use the /GENERATE_SYMBOL qualifier to automatically generate missing symbols.

OFILNOTCV, at tag or text, line n, file file-spec Cannot open new version of: filename File not converted.

Warning: An attempt to open an included file failed.
User Action: Verify that the file specification is correct, and that you have sufficient resources and access rights to create the file.

OFNONSTFM, at tag or text, line n, file file-spec Invalid attempt to place tag <tagname> within <ONLINE_POPUP>/<ENDONLINE_POPUP> tags.

Fatal: <HEADN> tags, formal examples, figures, and tables are not allowed between <ONLINE_POPUP>/<ENDONLINE_POPUP> tags.
User Action: Either remove the <ONLINE_POPUP>/<ENDONLINE_POPUP> tags or use an informal example, figure, or table. Also, be sure no <HEADN> tags are in the popup.

OFNONSTNG, at tag or text, line n, file file-spec Invalid attempt to nest tag <tagname>.

Fatal: A tag is referenced when its context is already active. For example, this message is issued when an <ONLINE_POPUP> tag exists after a previous <ONLINE_POPUP> tag that you did not terminate.
User Action: The indicated tag is ignored; however, you should verify your source file to determine whether the tag is a duplicate or whether, in fact, you did not terminate an earlier occurrence of the same tag.

OFONLCHNK, at tag or text, line n, file file-spec Invalid attempt to place tag <tagname> in a formal example, figure, or table.

Fatal: <ONLINE_CHUNK> tags are not allowed in formal examples, figures, or tables.
User Action: Remove the <ONLINE_CHUNK> tag or use an informal example, figure, or table.

OHIVERNUM, at tag or text, line n, file file-spec Version number detected on included file, string. Higher version of that file is being written.

Warning: The tag translator has detected a version number on an included file. A file with a higher version number is being written.
User Action: The source file has included a file with a specific version number and the symbol generator is writing a file with a higher version number. Either remove the version number or modify the file specification to the higher number.

OINVPREFX, at tag or text, line n, file file-spec Invalid symbol argument to /PREFIX= qualifier on command line.

Fatal: Invalid characters have been detected in the symbol argument to the /PREFIX= qualifier on the command line.
User Action: Check to ensure that there are no invalid characters, such as dollar signs ($) or hyphens (-), in the symbol argument to the /PREFIX qualifier on the command line.

OSYMNTDEF, at tag or text, line n, file file-spec Symbol string is undefined

Error: A symbol has been referenced but is not in the symbol table.
User Action: Verify that the symbol is spelled correctly and that the same symbol has been entered in the symbol table.

OTTLPGMSG, at tag or text, line n, file file-spec Tag <TITLE_PAGE> is missing

Error: A <TITLE_PAGE> tag is missing. Bookreader doctypes require the <TITLE_PAGE> tag.
User Action: Check to ensure that the <TITLE_PAGE> tag exists and is coded correctly.

OTL_LEVEL, at tag or text, line n, file file-spec Outline level specified, number, is not in range The argument must specify 1 through 6

Warning: An invalid number was specified in a <LEVEL> tag in an outline. Only levels of 1 through 6 are valid.
User Action: Correct your source file so that no outline level has a number greater than 6.

OTL_TITLE, at tag or text, line n, file file-spec <tagname> not valid within outlines. Enter the title as an argument to the <OUTLINE> tag

Warning: A <TITLE> tag was specified within the context of the <OUTLINE> tags.
User Action: Correct your source file so that the title of the outline is supplied in arguments to the <OUTLINE> tag.

OUTLIN2BG, at tag or text, line n, file file-spec Output line exceeded number bytes, and had to be broken

Warning: Text in an output line exceeded the tag translator's buffer. No text was lost because the line was written as two lines, but the division into two lines may have broken a word into two words, or interfered with the correct formatting of the text. This usually happens when the tag translator inserts many formatting commands into an output line. It also happens when a tag reference on a long input line is replaced by a very long string of text.
User Action: Check the formatted output that corresponds to the input line specified in the location information to see if breaking the line affected the formatting.

PARSECODE, at tag or text, line n, file file-spec Argument number has illegal action code char

Error: The character shown is not one of the allowed action codes.
User Action: Correct the indicated argument to the tag.

PARSELNEQ, at tag or text, line n, file file-spec Lengths of delimiter and action arguments are not equal

Error: The number of delimiter characters and the number of action codes in one of the action strings are not the same.
User Action: Correct the delimiter or action arguments to the tag.

POSTERROR, at tag or text, line n, file file-spec Error encountered during post-translation

Fatal: An error has been detected during the final step in tag translation.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

PQLISNONE, at tag or text, line n, file file-spec <tagname> specifies NONE when no heading is specified

Warning: The keyword argument "NONE" was specified to a <PARAMDEFLIST> or <QUALDEFLIST> tag in a context in which no default heading is in effect. The use of NONE in this context is meaningless.
User Action: Determine if you intended to be using default headings for the <PARAMDEFLIST> or <QUALDEFLIST> tag. If not, remove the tag from your source file. Otherwise, verify whether you should have invoked one of the reference templates to set an environment for parameter/qualifier list descriptions.

PROFORDER, at tag or text, line n, file file-spec <PROFILE> tag is out of order

Fatal: A <PROFILE> tag has been detected after an element heading tag, such as <CHAPTER> or <APPENDIX>.
User Action: Place a single <PROFILE> ...<ENDPROFILE> sequence in a file by itself in order to do a book build.

PROFQ_ILL, at tag or text, line n, file file-spec /PROFILE qualifier illegal during a book build

Fatal: The /PROFILE qualifier was supplied on the command line, indicating that an element build is desired, but the SDML file contains a <PROFILE> tag, indicating that a bookbuild is desired. The /PROFILE qualifier (which indicates an element build) should not be supplied when a bookbuild is desired.
User Action: Invoke DOCUMENT without the /PROFILE qualifier.

QUALVALUE, at tag or text, line n, file file-spec Value string to /CONDITION qualifier is not a valid name

Fatal: The condition name supplied with the /CONDITION qualifier must contain only alphabetic and numeric characters and the underscore character.
User Action: Correct the spelling of the condition name.

Q_BAD_POS, at tag or text, line n, file file-spec Argument 2, string, is invalid for queue name

Error: A position argument supplied with a queueing built-in tag is invalid. The numeric value of the position may be out of range or an invalid keyword may have been used.
User Action: Correct the tag's position argument.

Q_NONUM_E, at tag or text, line n, file file-spec Entry in queue name is not numeric

Error: An <ENQUE> tag has requested that a new value be inserted in a queue in numeric sorted order. During the insertion a non-numeric entry is discovered in the queue. This can happen only if the entry was enqueued by a method other than numeric sorted order.
User Action: Review the <ENQUE> tags that insert entries on this queue and insure that all tags request a numeric sorted order.

Q_TOOLONG, at tag or text, line n, file file-spec Concatenation of all name queue entries exceeds max length

Error: A <DEQUE>(name\ALL\RETURN) tag has been encountered. The concatenation of all the entries on the queue creates a single string that exceeds the maximum string length (65,012 bytes).
User Action: Adopt a different queueing method, breaking the queue into more than one queue.

REVISINFO, Document is using revision indicators

Informational: Indicates that the <REVISION> tag is being processed. Text that is delimited by <MARK> and <ENDMARK> tags will be accompanied by revision indicators on output.
User Action: If you intend for revision bars to print in your text, you do not need to take any action. However, if you intended for text indicated by <MARK> tags to not appear in the output, you should remove the <REVISION> tag from the file.

REVISTEXT, Revised pages will contain the text string.

Informational: This message verifies the text specified in the second argument to the revision tag and reminds you that only pages specified in an update range will be processed and printed.
User Action: None.

REVIS_UPD, Revision will contain update pages only.

Informational: This message reminds you that you specified <REVISION>(UPDATE) and that your output file will only contain the text for pages specified between <UPDATE_RANGE> and <ENDUPDATE_RANGE> tags.
User Action: None.

REV_PAGES, Update pages number through number will be output

Informational: This message indicates the pages that will be output for an update.
User Action: None.

RMVCONDTN, Removing condition condition-name on line number of file filespec

Informational: A <SET_CONDITION>(REMOVE) tag is being executed.
User Action: None.

SAVTAGACT, at tag or text, line n, file file-spec Tag <tagname> has a before or after action that is ignored when saving a tag table

Warning: You are attempting to invoke a tag that has a before action or an after action. The before action or after action cannot be executed while you are saving the tag in a tag table. The before action or after action will be executed when the saved tag table is loaded.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

SAVTAGILL, at tag or text, line n, file file-spec This built-in tag cannot be invoked during the saving of a tag table

Error: Only certain built-in tags can be stored in a saved tag table for invocation when the saved tag table is loaded. This tag is not one that can be saved.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

SAVTAGLEV, at tag or text, line n, file file-spec Tag <tagname> cannot be invoked within an argument list during saving of a tag table

Error: During the saving of a tag table, the arguments to all tags must be constant or must be made constant by quoting them.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

SDML_INFO, message

Informational: An SDML tag is describing action taken during tag loading.
User Action: None.

SECFILOPN, at tag or text, line n, file file-spec Cannot open a secondary output file named filename A secondary output file is already open. It is named filename

Error: Only one secondary output file can be open at a time.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

SETCONDTN, Setting condition condition-name on line number of file filespec

Informational: A <SET_CONDITION> tag is being executed or a condition is being set in response to a /CONDITION qualifier on the command line.
User Action: None.

SKIPITEMS, at tag or text, line n, file file-spec number <tagname> outside of <tagname> skipped.

Warning: This message is usually preceded by a message indicating that an <LE> or <TABLE_ROW> tag was encountered. It indicates the number of additional tags that were specified. The tags will not be processed, and will be written, unformatted, to the output file.
User Action: Determine if the tags are considered invalid because there is no preceding <TABLE> or <LIST> tag, or if the <TABLE> or <LIST> tag was specified incorrectly. Correct your source file.

STKOVRFLW, at tag or text, line n, file file-spec More than number nested levels of tags. (These are tags that are invoked inside other tags' argument lists)

Fatal: The tag translator limits the number of tags that can be invoked simultaneously. Tag B is invoked simultaneously with tag A, if it is invoked in the argument list to tag A. Thus, <A>(<B>(<C>)) requires that three tags are being invoked simultaneously. This may occur unexpectedly when the argument list to one of the tags is not properly terminated.
User Action: Verify that the argument list of the tag that is specified in the location information has been properly terminated.

STRFREE2T, at tag or text, line n, file file-spec Internal error. Attempt to free the same string twice

Fatal: The tag translator's memory allocation algorithm has failed.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

STRFREEBA, at tag or text, line n, file file-spec Internal error. Attempt to free string with bad address

STRTOOBIG, at tag or text, line n, file file-spec Internal error. Attempting to allocate number-byte string

SYMFREEBA, at tag or text, line n, file file-spec Internal error. Attempt to free symbol table entry with bad address

SYMISSING, at tag or text, line n, file file-spec Missing symbol argument. Each book element must have a symbol argument

Fatal: Each element of a book must have a unique symbol so that the element can be processed independently. The symbol table cannot be saved from this run.
User Action: Supply a symbol as an argument to the tag.

SYMISUSED, at tag or text, line n, file file-spec The symbol string is already in use as a symbol of type string

Error: Each element of a book must have a unique symbol. You have supplied a symbol on this element of the book that conflicts with an earlier use of this symbol. The symbol table cannot be saved from this run.
User Action: Correct the use of symbols on elements of the book so that each element has a unique symbol. If you are doing a book build you must repeat the book build in order to produce a good symbol table. If you are doing an element build, just correct the symbol in this tag so that this element of the book has a unique symbol, and then repeat the element build.

SYMNOTDEF, at tag or text, line n, file file-spec Symbol string is undefined

Warning: A symbol has been referenced but is not in the symbol table.
User Action: Verify that the symbol is spelled correctly and that the same symbol has been entered in the symbol table by the invocation of a tag that defines the symbol.

TAGFREEBA, at tag or text, line n, file file-spec Internal error. Attempt to free tag table entry with bad address

TAGINFILE, The tag was in the file filename

Informational: This message may accompany a message indicating that a tag that must be ended was not terminated. This message is output when the starting tag is not in the current input file.
User Action: Use the file spec given to determine which file contains the tag that was not properly terminated and terminate it.

TAGINVALD, at tag or text, line n, file file-spec Tag <tagname> is invalid in this context. The context was established by <tagname> on line number of filename

Error: A tag was specified in a context where it is not valid, for example, a header-level tag was specified within the context of a monospaced example. The message tells you what tag established the context.
User Action: Determine the current context at the point at which the message was issued to determine if you have forgotten a required terminator and correct your source file.

TAGINZONE, at tag or text, line n, file file-spec Tag <tagname> is invalid in the bounds of string.

Error: A tag was specified in a context where it is not valid, for example, a header-level tag was specified within the context of a monospaced example.
User Action: Determine the current context at the point at which the message was issued to determine if you have forgotten a required terminator and correct your source file.

TAGNOTDEF, at tag or text, line n, file file-spec Tag <tagname> is undefined

Warning: A tag has been invoked, but no definition exists for the tag. This message appears for the first invocation of an undefined tag. Subsequent invocations of the same undefined tag are counted, but the message is not repeated. A count of the total number of all invocations of undefined tags is reported at the end of the tag translator 's processing.
User Action: Correct the spelling of the tag or supply a definition for the tag.

TAGNOTEND, at tag or text, line n, file file-spec Tag <tagname> from line number not terminated

Error: A tag that has a required terminator was not terminated.
User Action: Locate the tag that was not terminated and include its terminating tag at the appropriate position in your source file.

TAGNOTHID, at tag or text, line n, file file-spec Cannot reveal tag <tagname>. It is not hidden

Warning: A <REVEAL_TAGS> tag is requesting that a hidden tag be revealed, but the tag is not currently hidden.
User Action: If you receive this message and are under a service contract with Digital, call your customer service center. Otherwise, submit a Software Performance Report.

TAGNOTPRE, at tag or text, line n, file file-spec Tag <tagname> invalid unless preceded by string

Warning: A tag is being invoked that is invalid because it is being used out of context.
User Action: Check the sequence of tags to ensure that the proper context is established before the tag is used. Correct the SDML source file.

TAGNOTPRX, at tag or text, line n, file file-spec Tag <tagname> invalid unless preceded by an example tag

Warning: A tag is being invoked that is invalid because it is not being used within an example.
User Action: Check the sequence of tags to ensure that an example tag is used before the <VALID_BREAK> tag. Correct the SDML source file.

TAG_FAILS, The tag translator has detected a fatal error

Error: The tag translator is terminating execution with failure status. The accompanying error message supplies details of the error.
User Action: See the description of the accompanying error message.

TAG_IDENT, message

Informational: This message will appear only in patched or baselevel systems. The tag translator inserts the text, which is usually some kind of internal baselevel indicator.
User Action: None.

TAG_INARG, at tag or text, line n, file file-spec <tagname> is invalid in an argument to <tagname>.

Fatal: The indicated tag was specified in an argument to a tag that does not allow it. For example, a header level tag was specified in an argument to <TABLE_ROW>.
User Action: Verify that you correctly terminated the argument list for the tag in which this tag was specified.

TBLATTIGN, at tag or text, line n, file file-spec <TABLE_ATTRIBUTES> specified following <TABLE_SETUP> ignored.

Warning: The <TABLE_ATTRIBUTES> tag must be specified preceding the <TABLE_SETUP> tag. The specified attributes will be ignored.
User Action: Move the <TABLE_ATTRIBUTES> tag in front of the <TABLE_SETUP> tag.

TBLATTRIB, at tag or text, line n, file file-spec Argument string to tag <tagname> is not a valid table attribute

Warning: A keyword was specified in a <TABLE_ATTRIBUTES> tag that is not a valid keyword attribute for tables.
User Action: Verify that the specified value is a valid table attribute and check its spelling. Correct the SDML source file.

TBLBRKCOL, at tag or text, line n, file file-spec Table cannot be broken in column number

Warning: The <VALID_TABLE_ROW_BREAK> tag is valid only in columns two through four of a table.
User Action: Remove the <VALID_TABLE_ROW_BREAK> tag. If the text in column is too long for a page, consider restructuring the table to be less complex.

TBLCOLCNT, at tag or text, line n, file file-spec Tag <TABLE_SETUP> argument 1 string is missing or is not a number in the range 2 through 9

Error: The <TABLE_SETUP> tag must specify a numeric value in the range of 2 through 9 to specify the number of columns in the table. The indicated argument is invalid.
User Action: Correct the <TABLE_SETUP> tag.

TBLCOLNUM, at tag or text, line n, file file-spec Table column size argument string is missing or is not numeric

Error: An argument specified as a width for table rows in setting up the table is not a numeric argument.
User Action: Correct the <TABLE_SETUP> tag that specifies a non-numeric value for a table column width.

TBLCOLWID, at tag or text, line n, file file-spec Sum of table column widths number is too large or is 0 or less.

Error: The sum of the values specified for the column widths in the <TABLE_SETUP> tag is excessive or is less than or equal to 0. The message displays the current summed value of all column widths specified.
User Action: Verify that the numbers you specified in <TABLE_SETUP> are accurate. Adjust them to smaller numbers so that the table will fit. If you did not specify <TABLE_ATTRIBUTES>(WIDE) and the doctype you are using provides an extra margin for wide tables, specify <TABLE_ATTRIBUTES>(WIDE) in front of the <TABLE_SETUP> tag. To request that the table appear in a smaller typesize, use <TABLE_ATTRIBUTES>(MAXIMUM).

TBLDUPSET, at tag or text, line n, file file-spec Tag <TABLE_SETUP> specified twice. Duplicate setup ignored.

Warning: A table contains two <TABLE_SETUP> tags. The second tag is being ignored.
User Action: Determine which <TABLE_SETUP> tag is correct and remove the extra one.

TBLFNOTEM, at tag or text, line n, file file-spec Table footnote number number exceeds maximum number

Warning: A numeric argument specified for a footnote declaration in a table exceeds the maximum. The maximum number of table footnotes is normally 12; however, if you use any non-numeric keywords in table footnotes, the maximum number allowed is reduced to 6.
User Action: Verify the number of footnotes in the table and the numeric arguments you use to declare and reference them.

TBLKEYDUP, at tag or text, line n, file file-spec Table already specifies <TABLE_KEY>. Duplicate ignored.

Warning: Only one key can be specified in a table. The second key specified is being ignored.
User Action: Determine which table key is the one that you want and remove the extra one.

TBLKEYNES, at tag or text, line n, file file-spec <tagname> is not valid in a nested table. Nested table on line number in file string.

Warning: A <TABLE_KEY> or <TABLE_KEYREF> tag was specified in a nested table, that is, in a table that is specified in another table's <TABLE_ROW>. Table keys and table key references are invalid in nested tables.
User Action: Place the table key and/or the reference to it in the outer table.

TBLKEYNUM, at tag or text, line n, file file-spec The <TABLE_KEY> tag will replace table footnote 12.

Warning: When a key is specified in a table, you cannot specify a table footnote numbered 12. The text of the table key will replace the footnote number 12, and references to footnote 12 will be result in the table key being printed.
User Action: Check the arguments you specified to the <FOOTNOTE> tags in the table and do not specify a number greater than 11.

TBLKNOREF, at tag or text, line n, file file-spec Tag <TABLE_KEYREF> tag encountered in a table that has no key.

Warning: A <TABLE_KEYREF> tag is not valid because there is no key in the table to reference.
User Action: Verify that the <TABLE_KEY> tag is correctly specified in the main table (it must not be specified in a nested table). If the table has no key, remove the <TABLE_KEY> tag.

TBLNBREAK, at tag or text, line n, file file-spec A nested table with more than three columns cannot be broken.

Error: The <NESTED_TABLE_BREAK> was specified in a nested table that has more than three columns.
User Action: Verify that the <TABLE_SETUP> tag for the table you are trying to break was correctly specified. If the nested table has four columns, you may need to restructure your information.

TBLNONEST, at tag or text, line n, file file-spec Invalid table nesting. Ignored

Warning: You coded a nested table incorrectly. There are three possible problems:

You specified a <TABLE> tag with a caption argument in an argument to a <TABLE_ROW> tag. You cannot place a formal table inside another formal table.
You specified a <TABLE> tag inside another table, but outside of a <TABLE_ROW> tag. All text (including nested tables) that occur within a table must be coded within <TABLE_ROW> tags.
You specified a <TABLE_UNIT> tag inside a table that is nested in another table. <TABLE_UNIT> tags are not valid in nested tables.

User Action: Based on the above situations, you should:

Remove the caption argument from the nested table tag.
Nest the table inside a <TABLE_ROW> tag.
Remove the <TABLE_UNIT> tags.

TBLNOROWS, at tag or text, line n, file file-spec A table was specified without any table rows.

Error: <TABLE> and <ENDTABLE> tags were encountered in the file, but there were no <TABLE_ROW> tags between them.
User Action: Verify that you specified <TABLE_ROW> tags correctly. Or, remove the <TABLE> and <ENDTABLE> tags if you did not want to place a table there.

TBLNOTDEC, at tag or text, line n, file file-spec Table footnote number is referenced but not declared.

Warning: A <FOOTREF> tag is specified in a table, but there is no corresponding <FOOTNOTE> tag at the beginning of the table. The footnote reference will not be printed.
User Action: Verify that you specified the <FOOTNOTE> tag correctly at the beginning of the table. Verify that the number specified in the declaration matches the number in the <FOOTREF> tag.

TBLNOTMTP, at tag or text, line n, file file-spec <tagname> invalid in table that is not multi-page

Error: A tag, for example <TABLE_UNIT> was specified in a table that does not have the multipage attribute.
User Action: Determine whether the table is a multipage table. If so, be sure that it is not specified with the KEEP attribute.

TBLNOTROW, at tag or text, line n, file file-spec Tag <tagname> specified outside of <TABLE_ROW>.

Error: A tag is specified between two <TABLE_ROW> tags and is therefore not valid in this context.
User Action: Correct your source file to move the tags and related text, if any, to within the bounds of a <TABLE_ROW> tag.

TBLNOTSET, at tag or text, line n, file file-spec Table from line number has no <TABLE_SETUP> attributes.

Error: A <TABLE_ROW> tag was encountered in a table without a <TABLE_SETUP> tag.
User Action: Correct your source file to specify the number of columns and widths for the table.

TBLNUMCOL, Table row column count does not match setup

Informational: A tag, such as <TABLE_ROW> or <TABLE_HEADS>, specifies more or fewer arguments than indicated by the table setup. For example, a <TABLE_SETUP> tag indicates that a table has four columns, but a <TABLE_ROW> tag specifies only three arguments.
User Action: Determine whether you have not specified a column that is required, or whether you have correctly specified the <TABLE_SETUP> tag.

TBLSPANNO, at tag or text, line n, file file-spec Argument number to tag <SPAN> is invalid for the current column count.

Warning: A <SPAN> tag's argument exceeded the number of remaining columns in the table. For example, you specified <SPAN>(3) in a table with only 2 columns.
User Action: Correct your source file to specify the number of columns to span. Be sure that your numeric argument, plus the current column number, do not exceed the number of columns in the table.

TEXT_FORB, at tag or text, line n, file file-spec Text forbidden after <tagname> tag

Warning: The <tagname> tag cannot be followed by a text segment.
User Action: Correct your source file to remove the text that follows the tag or tag the text correctly.

TEXT_NEST, at tag or text, line n, file file-spec Attempt to pop a text state that has not been pushed

Error: A <SET_TEXT_STATE>(POP) tag is being invoked when there is no text state saved.
User Action: Examine the tag definitions that contain the <SET_TEXT_STATE>(POP) tag for a missing <SET_TEXT_STATE>(PERMITTED\PUSH) tag.

TEXT_REQD, at tag or text, line n, file file-spec Text missing after <tagname> tag

Warning: The <tagname> tag marks a text segment, but the text is missing.
User Action: Correct your source file to use the tag correctly.

TMPNONEST, at tag or text, line n, file file-spec Invalid attempt to nest reference templates. Last template was string

Error: A tag invoking a reference template was encountered when a reference template was already in effect; for example, a <ROUTINE_SECTION> is specified before a previous <COMMAND_SECTION> was terminated.
User Action: Correct your source file to correctly terminate the reference section that was not terminated.

TMPTAGDEF, You cannot redefine <tagname> using <tagname>.

Informational: A tag that defines a template tag specified a tag name that is already a defined tag. This message indicates one of the following:

Your input file has more than one reference template section, and you use the same template tag names in both. (For example, a <SET_TEMPLATE_ROUTINE> tag may specify the same tag name in more than one occurrence of <ROUTINE_SECTION>.
You have specified a name that is the name of an SDML global tag.

User Action: If the message occurred because you used the same template tag names in more than one reference template section, you need take no action. If you have used a name that is the name of an SDML tag, you should select another name; future use of the SDML tag name in the same source file may produce unpredictable results.

TMPTAGEND, at tag or text, line n, file file-spec <tagname> not terminated before <tagname>.

Warning: A tag occurring within the context of a reference template was not terminated before the end of the file or before the beginning of the next reference section. For example, an <OVERVIEW> tag from a <COMMAND> description was not terminated before the next <COMMAND> description was encountered.
User Action: Correct the source file so that you correctly terminate the template tag.

TMPTAGNAM, at tag or text, line n, file file-spec string is an invalid template tag name.

Error: A template tag, for example <SET_TEMPLATE_COMMAND>, specifies that the tag name that already defined in SDML, or it is an invalid name, that is it contains more than 31 characters, or it contains nonalphanumeric characters.
User Action: Choose another name for the tag and modify your source file.

UNBALPARS, at tag or text, line n, file file-spec Unbalanced parentheses in argument number

Warning: One or more left parentheses are present without matching right parentheses. A sufficient number of right parentheses are appended to the argument to achieve a balance.
User Action: Correct the unbalance either by adding the proper number of right parentheses or by coding the left parentheses using the <OPAREN> tag.

UNDEFSYMS, There were number undefined symbol references

Informational: Reports the total number of references that were made to undefined symbols. Only the first reference to a specific undefined symbol is reported.
User Action: Either define the undefined symbol or correct the spelling of the symbols being referenced. The undefined symbols were reported in other messages.

UNDEFTAGS, There were number undefined tag invocations

Informational: Reports the total number of invocations of undefined tags. Only the first invocation of a specific undefined tag is reported.
User Action: Either define the undefined tags or correct the spelling of the tag being invoked. The undefined tags were reported in other messages.

UPDATINFO, Update page label string, <tagname>

Informational: A document that is being processed to produce update pages may have associated update information. The information indicated will be printed on the bottom of each page output.
User Action: Verify that the update page label is correct for your document.

USEDEFINC, Using a value that is one greater than previous value

Informational: Accompanies other warning messages. It indicates that a default value is being used that is one greater than a previous value.
User Action: Edit the SDML source file to correct the argument.

USENODLIM, Using no delimiters

Informational: Accompanies other warning messages. It indicates that a stacked list will be output without delimiters.
User Action: Edit the SDML source file to correct the argument.

USER_IMSG, string Line is number of file filename

Informational: This message code is used for messages written to the terminal or output stream when a <USER_I_MESSAGE> tag is specified in the input file.
User Action: The action you take depends on the content of the user's message.

USER_WMSG, at tag or text, line n, file file-spec string

Warning: This message code is used for messages written to the terminal or output stream when a <USER_W_MESSAGE> tag is specified in the input file.
User Action: The action you take depends on the content of the user's message.

USESPCOUT, Alignment characters will be output as spaces

Informational: Accompanies other warning messages. It indicates that a default value of space will be used as output for the alignment character.
User Action: Edit the SDML source file to correct the argument.

USETAGDEF, Using tag's default: number

Informational: Accompanies other warning messages. It generally indicates that a default value is being taken.
User Action: Edit the SDML source file to correct the argument.

VBARINARG, at tag or text, line n, file file-spec A vertical bar was found in argument number to tag <tagname>. Use the <VBAR> tag to code a vertical bar in an argument

Fatal: The tag translator treats the vertical bar character as a special operator character in arguments to tags. If you include a vertical bar character in an argument, the tag translator may overlook the right parenthesis that terminates the argument list, and may scan all of the remaining input looking for the proper terminator.

Contents

Index

DECdocument Command Summary and Processing Messages

DECdocument
Command Summary and
Processing Messages