[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

421.0. "problems with TAG$SDML_TAGS.STT" by IJSAPL::KLERK (Theo de Klerk) Wed May 27 1987 08:52

Trying to re-compose the European Software Project Handbook, written in
Document BL7, I ended up with the following result. I haven't got a clue
what to do next. I checked the TAG$SDML_TAGS.STT and it is identical to
the one supplied with DOC010.B save set. Typing it on the screen makes
it look weird, but there are probably control characters hidden in this
file.

Any help appreciated.

Theo

DOCUMENT/tag/tex/nodev/content sph_book software.reference ln03 -
        /symbols=sph_definitions.gnc 
%DOC-I-IDENT, VAX DOCUMENT T1.0-008
%DOC-W-OPEN_DESIGN, Error opening DOC$LOCAL_FORMATS:DOC$DESIGNS.DAT data file.
-RMS-E-FNF, file not found
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0-002
%TAG-F-VMOVRFLOW, at tag <LOAD_TAGS> on line 3 in file
   DOC$STANDARD_FORMATS:TAG$SDML_TAGS.STT
   Internal error. Failure to allocate additional space in virtual memory

DOCUMENT sph_book software.reference ln03   /symbols=sph_definitions.gnc 
%DOC-I-IDENT, VAX DOCUMENT T1.0-008
%DOC-W-OPEN_DESIGN, Error opening DOC$LOCAL_FORMATS:DOC$DESIGNS.DAT data file.
-RMS-E-FNF, file not found
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0-002
%TAG-F-VMOVRFLOW, at tag <LOAD_TAGS> on line 3 in file
   DOC$STANDARD_FORMATS:TAG$SDML_TAGS.STT
   Internal error. Failure to allocate additional space in virtual memory
T.RTitleUserPersonal
Name
DateLines
421.1questionsCLOSET::ANKLAMWed May 27 1987 09:304
    
    Is this the first job you have run using DOCUMENT T1.0 ? What
    Version of VMS are you running, and on what CPU?
    
421.2virtual memory questionsVAXUUM::KOHLBRENNERWed May 27 1987 10:172
    And what is your PGFLQUOTA and the system's VIRTUALPAGECNT?
    
421.4The dataIJSAPL::KLERKTheo de KlerkWed May 27 1987 13:0310
 We are running VAX/VMS V4.5 on a 8650.

 It is the first large job that we took from a 750 running BL7 in Munich.
 We've installed BL8 and it doesn't any more (haven't tried BL7 as it
 was taken off the system here when BL8 was installed).
 It did run smoothly on that 750 and BL7.

 Our VIRTUALPAGCNT = 70,000 and the process PAGFILQUOTA = 10,000

Theo
421.5May need more PGFLQUOTAVAXUUM::KOHLBRENNERWed May 27 1987 13:474
    Try increasing the PGFLQUOTA for your process, to 15000.
    
    bill
    
421.6Problem solved, quirk noticedIJSAPL::KLERKTheo de KlerkWed May 27 1987 14:1713
   The "internal memory" problems sounded to me as if TeX was configured
   too small (at least for me). Using your questions on quota, I tried
   PAGFILQUOTA of 30,000 and that did the trick. Perhaps 15,000 would
   have been good too.

During the processing, I noticed that quite often a <CR> was given between
TeX messages, sometimes leaving me with a blank screen, interchanged with
blocks of "line too long" and "line too short" (it's difficult to please
TeX always!). Is this "blank hopping" usual or will it be suppressed in
the final release?

Theo
421.7Strange <CR>'s fixed for V10WRONGO::PARMENTERWed May 27 1987 14:559
    I don't understand how the configuration of TeX fits into this note
    at all, but I must note, that as I write this, I am unable to read note
    421.3 which might explain my confusion.  
    
    About those errant carriage returns:  Yes that is fixed for V10,
    but not (alas) for BL08.
    
    David Parmenter
    
421.8PGFLQUOTA = 15000 seems adequateVAXUUM::KOHLBRENNERWed May 27 1987 15:5815
    The problem with PGFLQUOTA was occurring in the 
    tag translator, not in TeX.
    
    For others who are wondering what value is correct for
    PGFLQUOTA, be assured that we are wondering the same thing. 
    
    We are making some changes to insure that virtual memory
    usage stays as low as it can be, and we will be doing some
    experiments in the next week to determine what the recommended
    quotas should be.
    
    At the moment PGFLQUOTA of 15000 seems to be adequate.
    
    bill