Conference vaxuum::online_bookbuilding

    	Usually, the 'exceeded memory' message is the result of too large a
    'chunk' for TeX to swallow.  This happens in large tables, examples,
    and lists.  The way to correct this is to periodically place
    <ONLINE_CHUNK> tags in the offending table, example or list.
    
    	If this doesn't take care of your problem, send me a pointer to
    your files and I'll check it out.
    
    Thanks,
    	Wayne

    thank you for your response
    
    i inserted <online_chunk> tags and processed each chapter (where an
    error occurred) by calling it with front matter into a profile
    
    one by one the <online_chunk> tags repaired the "runaway definition"
    problem, which occurred in all chapters 11 through 20
    
    however, when i built the book, calling all chapters into the profile,
    i received runaway definition errors again and was told to delete all
    <mark> and <endmark> commands--they cause problems in .tex files of a
    bookreader version
    
    after doing that i noticed that errors were still occurring, but now
    they were occurring where the <online_chunk> tags were so i deleted
    them too 
    
    now i am receiving a runaway definition error on chapter 20
    
    the error does not occur when i call chapter 20 all by itself into a
    profile, only when i build the whole book
    
    i wonder if the problem is related to the length of the book i am 
    processing
    
    i noticed before that errors only occurred from chapter 10 on, never
    in the first 9 chapters

    Could you send me pointers to your source files?  I'd like to take a
    look at them to see if I can find out just what's happening.
    
    Thanks,
    	Wayne

thanks for your help

i finally processed the book, after removing a <table_row_break>(first)
command and a <table_row_break>(last) command

i received a "runaway argument" error as a result of the two commands

can you find anything wrong with my use of <table_row_break>?  as shown in
the following text from my .sdml file 


.
.
.
<table_row_break>(first)
<table_row>(
<x>(Printer Control Settings form <xs>Notify user)
<x>(Notify user)
Notify user
\Whether to receive notification when the document has been
printed.
\\Y or N<line>Default: N
)
.
.
.
<table_row>(
<x>(Printer Control Settings form <xs>Additional parameter 1 or 2)
<x>(Additional parameter 1, 2)
Additional parameter 1 or 2
\Specifies additional characteristics of the print operation.  You can 
include any PrintServer keyword that you would include on the 
PRINT/PARAMETERS command. For more information, see <emphasis>(Management
User's Guide: VAX PrintServer Client). 
\\For a list of allowable values, use the command VMS HELP PrintServer at
the VMS system prompt ($).  
)

<table_row_break>(last)
<endtable>




<<<<<<<<<here is an account of the error in the log file:>>>>>>>>>>>



.
.
.
$ D 5137MASTER.TEX; ONLINE.HANDBOOK BOOKREADER/CONT/INDE=(GUIDE_HEADINGS,SORT=(-
LETTER))/NOPRIN/NOTAG_
%DOC-I-IDENT, VAX Document V1.2-B    25-JAN-1990 11:47:33.75
[ T e x t    F o r m a t t i n g ]...
.
.
.
%TEX-W-RUNAWAY, Runaway 'argument'
%TEX-I-SHOWTOKEN, 'Specifies additional characteristics of the print operation. Y\ETC.'
%TEX-E-NOROOM, Exceeded memory capacity:
-TEX-I-MEMORYSIZE, Main memory size = 131072 words
%TEX-I-SHOWCONTEXT, '...on, see {\it {}Management User'
%TEX-I-SHOWCONTEXT, '                                          's Guide: VAX PrintServer C...'
%TEX-I-SHOWCONTEXT, '... #2->\expandafter \stripit #1'
%TEX-I-SHOWCONTEXT, '                                          \\\\\\\relax #1#2'
%TEX-I-SHOWCONTEXT, '...tempcsA \onto \tempcsB '
%TEX-I-SHOWCONTEXT, '                                          \setspanninginfo \tempcsB \...'
%TEX-I-SHOWCONTEXT, '...artfalse \fi \settablerowbox '
%TEX-I-SHOWCONTEXT, '                                          \emittablerow 1\nexttablero...'
%TEX-I-LINE, Error occurred on or around line number: 1037
%TEX-I-SHOWCONTEXT, '}'
%TEX-I-SHOWCONTEXT, ' '
%TEX-I-FILENAME, 'USER1:[HARVEY.VMSUG_ONLINE]5137CH12.TEX;1'
-TEX-I-ONPAGE, on page [PART3-1718] 

%TEX-I-PAGESOUT, 1717 pages written.
-TEX-I-OUTFILENAME, 'USER1:[HARVEY.VMSUG_ONLINE]5137MASTER.DVI_BOOKREADER'
%DOC-E-ERROR_FORMATTER, Errors found by the text formatter
$ exit ($status + (0 * 1))
  HARVEY       job terminated at 13-JUL-1990 09:10:27.14

  Accounting information:
  Buffered I/O count:          234      Peak working set size:  1166
  Direct I/O count:            690      Peak page file size:   12033
  Page faults:               73091      Mounted volumes:           0
  Charged CPU time:     0 00:08:24.73   Elapsed time:     0 00:10:35.66

    I was also having a hard time getting a book that processed without error
    for hardcopy to build for online.  This book also was failing in the
    middle of a long series of 5-100 line formal tables and giving the infamous
    '%TEX-E-NOROOM, Exceeded memory capacity' message.
    
    I followed Wayne's advice and added <online_chunk> tags to break up the
    larger tables and everything is fine now.  
    
    I would suggest, however, that the documentation for the <online_chunk>
    tag, specifically, the info in the VAX DOCUMENT Writer's Tool Kit Notes
    for Internal Users, be updated.  Currently the description of this tag
    indicates that it is for long lists and informal code examples only,
    and that it should not be used with formal tables and examples.  
    It seems that this should be changed to indicate that this tag can be
    used in formal tables.
    
    Thanks,

    -randy

    i had the same experience
    
    adding <online_chunk> to a formal table fixed things up

    The documentation is correct.  <ONLINE_CHUNK> tags should not be used
    in formal examples, figures, or tables.  The next version of the
    software will check for this and issue an error message.

Even though <online_chunk> isn't supposed to be used in formal topics, howcome
it works in a formal table but kills a formal example? (see note 367 and 
replies)  Just curious...

Also, if adding <online_chunk> to a formal table fixes a TeX out-of-memory
problem, as seems to be the case with Randy in .5, how would one fix such a
problem when <online_chunk> become illegal for real in formal topics?  Does
<table_row_break> do the job?  (Incidentally, RE .4, I just built a book with
a lot of tables containing <table_row_break> tags, and their presence or absence
didn't have any effect on the online build as far as i can tell.)

							-- Nina

    >The documentation is correct.  <ONLINE_CHUNK> tags should not be used
    >in formal examples, figures, or tables.  The next version of the
    >software will check for this and issue an error message.
    
    
    You're kidding!  When did this change?  One of my books wouldn't
    process until I put <online_chunk> into some of the formal examples.  
    I kept getting "exceeding memory" errors without them.
    
    I'm sure that I had entered a note in this notes file when I first had
    the problem (probably more than a year ago) and the advice I was given
    was to put some <online_chunk> tags in the examples.
    
    If you can get the books to process without the <online_chunk> tags,
    I'll be happy though. 
    
    Helen
    

If we aren't supposed to use <online_chunk> for large formal topics, how should
we break up a LARGE (300+ line) formal example?

mitch

    <VALID_BREAK>.
    
    Also, I just processed a 400-line formal example with no <valid_break>
    tags: the book built and the example displayed just fine.
    
    In both cases (with and without <valid_break>), TeX complained that the
    example was too large to fit on the page but the whole thing was
    displayed by Bookreader so all was well with the output.
    
    If this is not your experience, please post your log file and a pointer
    to the offending example.
    
    Mary