Conference vaxuum::online_bookbuilding

248.0. "TeX out of memory in TOC build for Bookreader?" by COOKIE::MELTON (Standards and serendipity--the ideal combination) Wed Jan 03 1990 14:36

    I apologize for bothering the readers of this conference if this topic
    has been addressed in an earlier topic or reply, but I have not been
    able to find a note referencing it.

    I am responsible for a very large document (currently in the 750-page
    range in the PostScript version and around 1050 "pages" in the
    Bookreader version) that I revise and republish regularly
    (approximately every 2 months).  Compiling this document with DOCUMENT
    has always been "interesting", especially when compiling for
    Bookreader. 

    However, when I attempted to compile my most recent version for
    Bookreader use, the compilation appeared to work completely normally
    until it gets to the phase of text formatting the *contents* of the
    document!  At that time, I get the following:

       [ T e x t    F o r m a t t i n g   C o n t e n t s ]...
       %TEX-I-INFO, loading online doctype design file, TEX$O_REFERENCE - 
                                                          on page [1]
       %TEX-W-RUNAWAY, Runaway 'text'
       %TEX-I-SHOWTOKEN, 'voila:onlinetoc'
       %TEX-E-NOROOM, Exceeded memory capacity:
       -TEX-I-MEMORYSIZE, Main memory size = 131072 words
       %TEX-I-SHOWCONTEXT, '...\special {voila:onlinetoc '
       %TEX-I-SHOWCONTEXT, '                   #2 #3 #4 #5}\or \special {v...'
       %TEX-I-SHOWCONTEXT, '...: #4 :}{#1}{0}{0}{0}{0}{0}'
       %TEX-I-SHOWCONTEXT, '                   \par \or \SDMLspecial {\the...'
       %TEX-I-LINE, Error occurred on or around line number: 134
       %TEX-I-SHOWCONTEXT, '...definition{\char 62}}{\RTLnumber {452}}'
       %TEX-I-SHOWCONTEXT, '                                          '
       %TEX-I-FILENAME, 'DISK$DSRI:[MELTON.SQL]SQL2-ONLINE_CONTENTS.TEX;2'
       -TEX-I-ONPAGE, on page [1] 

       %TEX-E-NOINPUTPAGE, no pages in input file
       -TEX-I-FILENAME, 'DISK$DSRI:[MELTON.SQL]SQL2-ONLINE_CONTENTS.TEX;'
       %DOC-E-ERROR_FORMATTER, Errors found by the text formatter

    Being relatively na�ve about the bookbuilding requirements, I have
    examined the contents of the SQL2-ONLINE_CONTENTS.TEX file and
    verified that it has balanced braces, etc.  I can't think of anything
    else that would have caused "runaway 'text'" in this context.

    This version of my document is approximately 10% larger than the
    preceding version, which built just fine; however, the place at which
    the contents text formatting is perhaps 30% or 40% of the way through
    the .TEX file.  If it were 90% or 95% of the way through, I might be
    willing to believe that my document had simply grown too large for
    DECTeX to handle or something.  But it's very early in the .TEX file
    (line 134 out of 354 lines).

    Can someone offer me some clues?

    Thanks,
       Jim

    Hi, Jim-
    
    I think it must be the phase of the moon: see note 246! Why do these
    things always happen in bunches...? 
    
    Anyway, send me your xxx_contents.tex file.
    
    Also, what version of VAX DOCUMENT are you running, and what version
    of the online tools? Has anything changed on your VAX DOCUMENT
    configuration recently (since your last build for the Bookreader)?
    
    Thanks,
    
    Mary

    Hi, Mary!

    Thanks for the quick response!  I'll mail you the xxx_contents.tex
    file in a few minutes.

    I am using DOCUMENT V1.2-A for the bookreader building, though I'm still
    using V1.1 for PostScript building (V1.2 has a bug in the indexing
    stuff that is too serious for me to get around, so I'm awaiting a
    future release with the bug fixed).  My system manager claims that we
    have the "latest" version of the online tools installed, but I don't
    know the specific version---how do I quickly find out?

    Since my last build for the Bookreader, we installed a new version of
    DOCUMENT and new online tools, so lots of things seem to have changed.

    Thanks again,
       Jim

    P.S., One of these days, we'll have to resume the discussions over my
    two "holdover" problems: inability to use my index in the build for
    Bookreader, and the => hotspot indicator.

>    ... My system manager claims that we
>    have the "latest" version of the online tools installed, but I don't
>    know the specific version---how do I quickly find out?
    
    See the replies in topic 246 for an example of the "version" message. 
    You get it whenever you build online books.
    
    Mark

Thanks, Mark and Mary, for your help.

It turned out that when the latest version of the online bookbuilding
tools were installed on our cluster, the DOC$DESIGNS.DAT file(s) hadn't
been updated as required.  They still referred to TEX$O_REFERENCE.DESIGN
instead of TEX$V2REFERENCE.DESIGN.  With this fix, the "tex out of memory"
problem went away.

Thanks!
   Jim