Conference vaxuum::online_bookbuilding

    <subheadn> tags require symbol args (for online) since V2.0. See the
    V2.0 documentation of <subhead1> and <subhead2>.
    
    To ease the pain of adding symbol arguments to these tags, V2.0
    includes a symbol generation utility that you can run over your files
    to add the symbol arguments. This, too, is documented in the V2.0
    docset.
    
    Note that other tags that require symbol args in V2.0 include the
    template tags, <command>, <subcommand>, <sdml_tag>, <routine>, and
    <statement>.
    
    Mary

Hi Mary,

Thanks for the info. The information about tags that now need symbols
was not in either the External or Internal Release Notes. I didn't have
the most recent version of the Documentation in my office at the time
because we've sent it out to be copied so I couldn't look up the tags.

Thanks for letting me know which other ones do too. I will pass this
info on to the writers I support.

Sally

    DOCUMENT users in general:
    
    Note that online version of the DOCUMENT V2.0 docset are available,
    SO...(if you have a workstation), you *can* have a copy at your desk at
    all times and there is no need to make extra copies!

    What's the reason for this incompatible change?  Why wasn't it
    called out in release notes?  
    
    Kirk

    The general wishlist item that more text elements be
    cross-reference-able is the reason for the change.
    
    I don't know why it's not in the release notes. It *is* in the
    <subheadn> documentation.
    
    Mary

    I infer from your answer that it's not possible to make
    elements 'cross-reference-able' without *requiring* symbols
    for the tags that denote those elements, whether or not one
    chooses to refer to them?
    
    This introduces maintenance tasks to books that we have no writers
    assigned to.  If we had been able to anticipate the task, that
    would have been helpful.
    
    Kirk

    Seems like all you have to do is use the symbol generator...

    It has always been true that to create a cross reference using VAX
    DOCUMENT (i.e., using the <reference> tag), the text element being
    referred to must have a symbol argument. That's why we've always called
    them 'symbolic cross references.'
    
    I apologize for the fact that there was no mention of this change in
    the release notes for V2.0. There should have been, as you pointed out.
    
    As for anticipating changes, I'm not sure what you want here. Would the
    release notes have really informed you far enough in advance? The best
    way to get advance notice of new features is to be a field test site:
    VAX DOCUMENT V2.0 was in field test from last July until February. The
    new symbol-name arguments for <subheadn>, etc.  were in the field test
    update issued in December, and *were* documented in those release
    notes.
    
    As for the maintenance involved, as Ross points out, you need only run
    the symbol generator to insert the symbol arguments. A few months ago,
    I ran it for the first time on an 800-page (printed) book. To learn the
    command line and run it took me all of 5 minutes. Most of that time was
    spent waiting because of the size of the document. This utility was
    provided in anticipation of maintenance tasks introduced by the change.
    
    Sorry for the inconvenience...
    
    Mary
    
    PS. I have not checked but I seem to recall some mention of the new
    symbol args in this notes conference.

We have used the symbol generator and it works great, but we can't seem to
use it in batch mode. On our cluster we do everything in batch. Is there a
way to do it in batch? It bombs if you try using the /BATCH qualifier.

Sally

One note: if you look at the documentation under <SUBHEAD1> or any
tag that uses a symbol name it states that it is an optional argument.
It may be optional for hard copy output but it isn't for Bookreader.
There should be something with the tag description that states this.

Sally

    There is a problem with the documentation. 
    
    Most tags that take symbol name arguments (<appendix>, <chapter>,
    <headn>) note in the Restrictions section that the argument is
    required for online bookbuilds. The section for the <subheadn> tags,
    however, does not state that as a restriction. I will note that
    for the next revision of the documents.
    
    There is a complete list of tags that require symbol name arguments
    in section 4.1 of Producing Online and Printed Books.
    
    Thanks,
    
    Mary

    RE .9: No, there is no way to run the symbol generator in batch
    mode in V2.0. I will forward this request as a wishlist item to
    the VAX DOCUMENT development group. You might also want to submit
    a requirement when they open phas 0.
    
    Thanks,
    
    Mary

  And for those that want to bring hardcopy books to online books for
  the first time (and either use V1.2B or V2.0) there is still the
  DOCTOR/ONLINE utility to help in providing additional tags for popup
  examples, tables etc as well as <subhead>s and others, depending on
    DOCTOR/ONLINE/VERSION_1  (= V1.2B: no labels for <subhead> a.o.)
    DOCTOR/ONLINE   or
    DOCTOR/ONLINE/NOVERSION_1 (=V2.0: labels for <subhead>, <command> etc)

  DOCTOR is found in IJSAPL::PSQ:[PUBLIC.SOURCES.DOCTOR]*.*
  
    Theo
    

    Just curious, but if the writer doesn't reference these symbols,
    and if DOCUMENT has the capability to automatically generate
    symbols for *its* use, then why not generate them on the fly
    during document processing and leave the writer's source text
    alone?  This would seem more in line with the intent of DOCUMENT
    of divorcing the act of writing from the act of style
    manipulation.

	Mike

 Re .14:   Does it run in batch? Of course it does. Provided you make
     a command procedure that does a SET DEFAULT to the correct place.
     It doesn't have a DOCTOR/BATCH qualifier

 Re .15:   Good question. In principle it should be able to, as in
     Tag Translator pass 1 it can generate them, and in pass 2 it can
     ignore them (as no <reference> is done). However it is in Pass 2
     that the TEX files are created. And since pass 2 does not create
     labels, they will not be present in the TEX file and hence cause
     a problem for the ONLINE design processing by the Text Formatter.
          
Theo

    Re .15: It is very easy to create the symbols "on the fly," and, in
    fact, we do that to create symbols for <online_popup>s and footnote
    popups.
    
    However, it is desirable for LinkWorks links and inter-book cross
    references that the symbols persist over subsequent versions of the
    book so that established links into the book will persist.  (Symbols
    generated on-the-fly are almost guaranteed to change with every build
    of the book.)
    
    Mary
    

    Thanks, Mary - the LinkWorks answer clears it up.  I don't know
    much about the mechanics of how it will work (will the user have
    to know the symbol name?  If not, wouldn't runtime generated
    symbols placed into the source still work?  Maybe output an
    informational message `DOC-I-SYMFIXUP  Generated symbol added to
    <SUBTITLE> tag at line xx'), but I certainly understand its
    utility.

    I would suggest that the need for symbols be made consistant
    across doctypes and destinations for common tags to avoid both
    user confusion and the `gotcha' syndrome when people decide to
    make an online document out of a perfectly working paper document.

	Mike

    RE .18:
    
    The user (of LinkWorks) won't have to know the symbol name.
    
    Runtime-generated symbols: what's running? Symbols can be
    generated "on the fly" during document processing but these
    won't persist when the document is next processed. Symbols also
    can be generated by the symbol-generation utility, which does
    exactly what you suggest. That is, it puts them in the source
    file (it writes out a new source file with the symbol names in
    it). These will persist because they are in the source file (unless
    the writer changes them...).
    
    Your point about consistency across doctypes is well taken.
    
    Thanks,
    
    Mary

    Mary,

    That's what I meant... Just put the symbol generator inline into
    the DOCUMENT run for the ONLINE doctype (actually only invoke the
    generator code when a tag requiring a symbol is missing one rather
    than making an entire pass through the file which most of the time
    would already be OK), give the user an informational that you're
    modifying his source, and move on.  This way the naive user (and
    there are a few) doesn't get a blow-up and doesn't have to go
    around asking for help until someone steers him toward the
    standalone symbol generator.  I know of one person here who
    laboriously hand entered symbols for all of her tags, using
    iterative DOCUMENT runs because she didn't know about the
    generator - just the way it is out in the sticks.

	Mike

    RE .20: That would not be straightforward. (Not impossible, mind you,
    but not straightforward and not likely to be done.)
    
    The symbol generator is documented. There are two notes conferences
    to complain in (see .0, which got this started off). It seems to me
    that it would have been far less laborious to peruse the TOC for
    "Producing Online and Printed Documentation" and check out Section
    4.7, Automatically Generating Symbol Names.
    
    Mary

       It would be extremely useful to the user community if there were 
       a document that discusses migrating V1.n source files to 2.0.   To
       my knowledge, it's traditional for Digital products to either be
       backward compatible or to provide explicit and discrete
       information about how to migrate existing applications.  So far,
       I've discovered that I've got to use symbolic names for <routine>,
       <subhead>, and <preface> tags if I want to build for bookreader; I
       don't yet know if other parts of the source code have to be
       changed.  
       
       DOCUMENT/GENERATE solves some of these issues; however, it only
       solves some of the problems some of the time.  (For example, it
       doesn't solve the <preface> issue, and it's awkward to use files
       for a manual are contributed by different writers in different
       locations.) 
       
       A discussion of how to migrate source files to V2.0 would be
       welcome; it would also be an excellent opportunity to redraft the
       WTK Release Notes.
       
       --Don

    RE .22:
    
    Migrating to V2.0: that was one of the purposes of the new document
    "Producing Online and Printed Documentation." Perhaps it fell short
    of the mark. I will forward your comments to the developers. 
    
    <preface> issue? What is that?
    
    Many of the points in this note center on documentation issues. In our
    defense, I would like to point out that two months before SSB, we lost
    our writers. They were pulled off the DOCUMENT documentation (a
    complete rewrite) for other projects. Near the end of the project,
    they came back for two weeks to "finish up." This doesn't excuse the
    flaws and omissions in the doc set, but I do think that all things
    considered they did an outstanding job under difficult circumstances.
    
    Thanks,
    
    Mary
    

    Don,
    	I'm not sure what you mean by it being 'awkward to use files for a
    manual contributed by different writers in different locations'. I 
    don't really believe it's just because of the need to have symbol
    arguments for online documents.  I'm sure that there are a lot of other
    issues, too.

    	The symbol generator writes the modified files into the source
    directories.  The only thing that could make it 'awkward' would be that
    it requires that the directory and file protection be set correctly
    when they're located in someone elses account or on a different node.
    
    	Section 4.1 in the document 'VAX DOCUMENT Producing Online and
    Printed Documentation' lists all the tags that require symbol arguments
    for online bookbuilds.  The symbol generator will add missing symbols
    to all of these tags.
    
    Have a nice one...
    
    	Wayne

       Hi Mary, Wayne --
       
       That's my mistake about <preface> -- I thought there was an issue
       when the <preface> tag didn't get updated when I used DOCUMENT
       /GENERATE on a file that wasn't in my current default directory.
       
       I can understand and sympathize with your resource issues.  It's a
       problem nearly everywhere in the company, and I'm sure that the
       writers who were available did the best they could.  Still, it
       would be a shame if the efforts of software developers were
       shortchanged because users become frustrated at figuring out how
       to get their existing applications to work.  I've read most of
       "Producing Online...": although I don't doubt that migration from
       1.n to 2.0 was originally a goal, I've found nothing in the manual
       that specifically discusses migration.  (A section in Chapter 4
       does, however, discuss automatically adding symbolic names.)
       
       As an example of the migration problems that we've run into in one
       book, we have a reference manual that uses the routines template
       in documenting about 350 functions.  A master file defines
       <set_template_routine> and then has 350 <include> tags, one for
       each function.  When a draft of the manual is produced, writers
       copy the files for their functions to a build directory (the
       writers are not on the same system, or even the same continent),
       and the book is then built.  
       
       Individual writers cannot run DOCUMENT/GENERATE on their files,
       because the <set_template_routine>'s redefinition of <routine> is
       known only to the master file, and not to the individual files. 
       So, writers would have to copy their files to a common directory,
       DOCUMENT/GENERATE would have to be run, and writers would then
       have to copy their source files back.  
       
       Even then, there's a problem.  A line of code in my V1.2 .SDML
       source file is as follows:
       
          <set_template_routine>(POSIX_FUNCTION\stack\doublerunningheads)
       
       DOCUMENT/GENERATE did not modify this line of code; as far as
       DOCUMENT/GENERATE was concerned, a symbolic name already existed.
       That's because <set_template_routine> now accepts a symbolic name,
       so the final argument to the tag is transparently changed from the
       keyword that applied in 1.n to a symbolic name!  I haven't
       reprocessed the reference manual, but I assume that I will lose
       the double running heads unless I modify the source code.
       
       These are just some examples of migration issues.  I do appreciate
       your resource issues, but I wonder whether the software will be
       accepted by the user community without some specific information
       about what a user should do to build a manual with 1.n sources in
       a 2.0 environment.  Section 4.7 of "Producing Online..." neither
       addresses nor solves the problem of migration; software that isn't
       backward-compatible needs more explanation than what now exists.
       
       --Don

>       Even then, there's a problem.  A line of code in my V1.2 .SDML
>       source file is as follows:
       
>          <set_template_routine>(POSIX_FUNCTION\stack\doublerunningheads)
       
>       DOCUMENT/GENERATE did not modify this line of code; as far as
>       DOCUMENT/GENERATE was concerned, a symbolic name already existed.
>       That's because <set_template_routine> now accepts a symbolic name,
>       so the final argument to the tag is transparently changed from the
>       keyword that applied in 1.n to a symbolic name!  I haven't
>       reprocessed the reference manual, but I assume that I will lose
>       the double running heads unless I modify the source code.


    Don,
    	I'm afraid you've found another flaw in the documentation.  It
    mistakenly lists the <set_template_routine>, <set_template_command>,
    <set_template_statement>, and <set_template_tag> tags as requiring
    symbol arguments.  Actually, the tags that you are defining with these
    tags (in your case, <POSIX_FUNCTION>(...) are the tags that require
    the symbol argument and are therefore the tags that are modified.  The
    symbol generator is doing the correct thing by not changing the
    <set_template_routine> tag.
    
    	I'll forward this information to have the documentation corrected
    for the next update.

    Thanks for bringing this to our attention...

    	Wayne

       Thanks, Wayne; that clears up a whole set of questions.
       
       --Don

Dear Mary,

I'm having trouble with Bookreader recognizing the symbol names I
provided for the <command>s.  My book has two sets of commands, one for
general users and the other for administrators.  When I compile it,
I get the 'missing symbol' error message for each command.  

I provided the symbols manually.  I thought I must have used incorrect
symbols, so I ran the symbol generator.  It didn't change anything.

The following is the .LIS generated by VAX DOCUMENT for the
compilation.  As you can see, the IPMT_COM_DICT_V1.TEX and 
IPMT_ADMIN_COM_SECTION.TEX have 0 length.

    Regards,
    
    Carolyn
    
----------------------
%DOC-I-IDENT, VAX DOCUMENT V2.0-1
[ T a g    T r a n s l a t i o n ]...
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-SETCONDTN, Setting condition BOOKREADER
   on line 1 of file USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE.SDML;9
%TAG-W-DUPSYMBOL, tag <SYMBOL_TABLE_ENTRY>, line 2, file
   INCLUDE_DIRECTORY:IPMT_COM_DICT_V1_OVERVIEW.SDML
   The symbol PRODUCT_NAME is being defined twice.
   The earlier definition is replaced by the new definition
%TAG-W-DUPSYMBOL, tag <SYMBOL_TABLE_ENTRY>, line 10, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   The symbol PRODUCT_NAME is being defined twice.
   The earlier definition is replaced by the new definition
%TAG-W-TAGNOTPRE, tag <RUNNING_TITLE>, line 2444, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Tag <RUNNING_TITLE> invalid unless preceded by TEMPLATE_SECTION_ATTRIBUTES
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-FILEWRTOK, File IPMT_COM_DICT_V1_FRONT_MATTER.TEX written
%TAG-I-FILEWRTOK, File IPMT_COM_DICT_V1_OVERVIEW.TEX written
%TAG-E-OESYMISNG, tag <COMMAND>, line 2, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 69, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 129, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 202, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 249, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 310, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 355, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 458, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 554, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 672, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 735, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 833, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 889, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 922, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 962, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1003, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1043, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1122, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1179, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1214, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1275, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1323, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1365, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1423, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1473, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1522, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1571, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1628, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1688, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1752, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1817, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1864, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1931, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1985, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2033, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2081, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2199, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <TABLE>, line 11, file
   INCLUDE_DIRECTORY:DICT_NOTIFYADDRESS.SDML
   Missing symbol argument to a <TABLE> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2353, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2399, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2457, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2504, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2619, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2656, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2704, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2753, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2787, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2916, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 3030, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_USER_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-I-FILEWRTNG, File IPMT_COM_DICT_V1.TEX written (0 length)
%TAG-E-OESYMISNG, tag <COMMAND>, line 3, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 71, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 129, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 178, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 253, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 302, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 357, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 398, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 528, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 583, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 688, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 768, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 895, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1105, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1143, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1181, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1227, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1267, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1309, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1440, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1484, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1563, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1607, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1644, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1707, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1779, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1822, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 1937, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2034, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2137, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-E-OESYMISNG, tag <COMMAND>, line 2394, file
   INCLUDE_DIRECTORY:IPMT_CLI_SPEC_ADMIN_COM.SDML
   Missing symbol argument to a <COMMAND> tag.
   Symbol names are required when referencing headings,
   formal tables, examples, and figures.
%TAG-I-FILEWRTNG, File IPMT_ADMIN_COM_SECTION.TEX written (0 length)
%TAG-I-FILEWRTOK, File IPMT_MESSAGES.TEX written
%TAG-I-FILEWRTOK, File APPENDIX_CLI_SYNTAX.TEX written
%TAG-I-FILEWRTOK, File IPMT_V1_GLOSSARY.TEX written
[ T e x t    F o r m a t t i n g ]...
%TEX-I-PAGESOUT, 315 pages written.
-TEX-I-OUTFILENAME, 'USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE.DVI_BOOKREADER'
[ C o n t e n t s   G e n e r a t i o n ]...
[ T e x t    F o r m a t t i n g   C o n t e n t s ]...
%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME, 'USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE_CONTENTS.DVI_BOOKREADER'
[ I n d e x    G e n e r a t i o n ]...
%INX-I-READING, reading file 'USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE.INX'
%INX-I-WRITING, writing file 'USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE_INDEX.TEX;'
%INX-S-CREATED, 'USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE_INDEX.TEX;' created
[ T e x t    F o r m a t t i n g   I n d e x ]...
%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME, 'USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE_INDEX.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
%DVC-I-INCLUDING, including input file: 
   IPMT_COM_DICT_V1_PROFILE_CONTENTS
%DVC-I-INCLUDED, File include_directory:ipmt_cli_syntax_pg1.fse was successfully included
%DVC-I-INCLUDED, File include_directory:ipmt_cli_syntax_pg2.fse was successfully included
%DVC-I-INCLUDED, File include_directory:ipmt_cli_syntax_pg3.fse was successfully included
%DVC-I-INCLUDED, File include_directory:ipmt_cli_syntax_pg4.fse was successfully included
%DVC-I-INCLUDED, File include_directory:ipmt_cli_syntax_pg5a.fse was successfully included
%DVC-I-INCLUDED, File include_directory:ipmt_cli_syntax_pg5b.fse was successfully included
%DVC-I-INCLUDED, File include_directory:ipmt_cli_syntax_pg6.fse was successfully included
%DVC-I-INCLUDING, including input file: 
   IPMT_COM_DICT_V1_PROFILE_INDEX
%DVC-I-BOOKBUILT, book was successfully built


DOCUMENT /NOBATCH/NOPRINT/INDEX/CONTENTS/LIST/CONDITION=BOOKREADER -
_IPMT_COM_DICT_V1_PROFILE.SDML S.O BOOKREADER
Date/Time: 29-MAY-1991 13:48:40.10
CPU time: 535.29 secs.

This is the .LIST file from the /GENERATE_SYMBOL qualifier:

---------------
%DOC-I-IDENT, VAX DOCUMENT V2.0-1
[ T a g    T r a n s l a t i o n ]...
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-ENDPASS_1, End of first pass over the input


DOCUMENT IPMT_CLI_SPEC_USER_COM.SDML GENERATE_SYM SDML/LIST=IPMT_USER.LIST
Date/Time: 29-MAY-1991 14:20:39.52
CPU time: 28.20 secs.


    

    Would you post pointers to the offending files:
    
       ipmt_cli_spec_user_com.sdml
       ipmt_com_dict_v1.sdml
    
    Thanks,
    
    Mary

    
    Dear Mary,
    
    Rather than indicate the pointer in the conference, I have
    sent mail to with the information.
    
    I appreciate your help.
    
    Regards,
    
    Carolyn
    

    Carolyn,
    
    I copied your file and looked at the two files with <command> tags in
    them:
    
    1. ipmt_cli_spec_admin_com.sdml -- it appears that you added symbols to
       argument 2, instead of argument 3. (The symbol name arg is arg 3 for
       <command>). For example,
    
          <command>(IPMT ADD ADMINISTRATOR\add_administ)
    
       The tag translator will report all of these tags as missing
       the symbol argument. 
    
       You should either remove the symbonames from arg 2 and run the
       symbol generator to add new symbol argin the correct position, or
       add a null second argument, e.g.:
    
          <command>(IPMT ADD ADMINISTRATOR\\add_administ)
    
       If you use TPU, either option is easy to code as a learn sequence.
    
    2. ipmt_cli_spec_user_com.sdml -- this file contains symbol arguments
       on 29-May by the symbol generator, and processes fine. According to 
       your log files you ran the symbol generator *after* processing your
       book and getting all the missing-symbol-arg errors. It should have 
       run OK if you reprocessed your book after running the symbol
       generator.
    
    Mary

    Mary,
    
    Thank you so much for your help.  I edited both files according to
    your #1 instruction.  The logical symbols were in the wrong place
    in the other file.
    
    The book compiles successfully.  I have a question for you about
    the layout of the format section of the commands.  In most cases,
    it works out fine.  In some cases, the arguments are thrown to
    the extreme left-hand side of the screen.  This did not happen
    when I processed the files using V1.2B.  I used S.O as the
    doctype.  Would another doctype make a difference?
    
    Regards,
    
    Carolyn
    

    Carolyn,
    
    Send me small file in which the arguments get thrown to the left.
    
    Thanks,
    
    Mary

    Dear Mary,
    
    I have been out of the office.  I can point you to the whole book and
    the bookshelf.  My group is experiencing some difficulties with
    DECwindows applications.  I cannot invoke Bookreader on my system
    today, so I am not able to view the book and pinpoint a sample
    from the file that will show you what is happening.
    
    You could look at the whole book in the following directory.
    
      MARX::USER4:[REYNOLDS.IPMT_RM_WORK]IPMT_COM_DICT_V1_PROFILE.DECW$BOOK
    
    (and DECW$BOOKSHELF.)
    
    I will be back in my office next week and with luck, can run the
    Bookreader files at that time.
    
    Regards,
    
    Carolyn