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

Conference vaxuum::online_bookbuilding

Title:Online Bookbuilding
Notice:This conference is write-locked: see note 1.3.
Moderator:VAXUUM::UTT
Created:Fri Aug 12 1988
Last Modified:Mon Jul 15 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:440
Total number of notes:2134

124.0. "Can't open included contents file" by LISTNH::SIMONS (Al Simons 381-2187) Thu May 04 1989 14:46

    After wasting Mary's time a few days ago reporting a known problem, I
    *swore* I was going to find this one myself. Sigh...
    
    DOC T1.2, ONLINE TOOLS April 19. VMS T5.2 FT1
    
    I built a small book (~80 pages). Everything is clean up to the device
    conversion phase, where it includes the contents file. It claims it
    can't open it! The file is there; I can open it with an editor. There
    is only one <contents_file> tag in the doc. I'm stumped. I have even
    tried it over again performing only a device conversion from the kept
    files. Same results...
    
    -Al (Who knows this stuff mostly works!)
    
$ DOCUMENT ARUS_FACILITY_PROFILE ONL.REF BOOK /CONTE /COND=ARUS_MEMORY_ROUTINES_ONLINE /KEEP /LIS
%DOC-I-IDENT, VAX Document T1.2     6-MAR-1989 14:28:26.99
[ 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-LCL_MSG01, Using online bookbuilding tools, 19-APR-89 baselevel
%TAG-I-SETCONDTN, Setting condition ARUS_MEMORY_ROUTINES_ONLINE
   on line 1 of file LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.SDML;
%TAG-I-SETCONDTN, Setting condition no_fm_overview
   on line 3 of file LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.SDML;
%TAG-I-SETCONDTN, Setting condition arus_memory_routines
   on line 6 of file LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.SDML;
%TAG-I-SETCONDTN, Setting condition online
   on line 7 of file LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.SDML;
%TAG-I-ENDPASS_1, End of first pass over the input
[ T e x t    F o r m a t t i n g ]...
%TEX-I-INFO, loading online doctype design file, TEX$O_REFERENCE - on page [1]
	.
    	.
    Many line too long/short messages
    	.
        .
%TEX-I-PAGESOUT, 83 pages written.
-TEX-I-OUTFILENAME, 'LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_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-INFO, loading online doctype design file, TEX$O_REFERENCE - on page [1]
	.
    	.
    Many line too long/short messages
    	.
        .
%TEX-I-PAGESOUT, 1 page written.
-TEX-I-OUTFILENAME, 'LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE_CONTENTS.DVI_BOOKREADER'
[ D e v i c e    C o n v e r s i o n ]...
$ !  input from DOCUMENT verb:	DVC$INPUT = name of .dvi file
$ !
$ if ("" .eqs. "") then -
	define/nolog DVC$VOILA DOC$VOILA_TOOLS:DVC$VOILA.EXE
$ $$drivoila := $ dvc$voila
$!
$ Filespec = f$parse("DVC$INPUT",,,,"SYNTAX_ONLY")
$ Nodename = f$parse("LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;",,,"NODE","SYNTAX_ONLY")
$ Devname  = f$parse("LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;",,,"DEVICE","SYNTAX_ONLY")
$ Dirname  = f$parse("LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;",,,"DIRECTORY","SYNTAX_ONLY")
$ Filename = f$parse("LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;",,,"NAME","SYNTAX_ONLY")
$ Filetype = f$parse("LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;",,,"TYPE","SYNTAX_ONLY")
$ Version = f$parse("LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;",,,"VERSION","SYNTAX_ONLY")
$ DVIspec = "LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;"
$!
$ $$drivoila "LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;" /h=36 /v=36
%DVC-I-INCLUDING, including input file: 
   doc$local_formats:small_logo.rags
%DVC-W-IGNORING, ignoring included input file 
   ARUS_FACILITY_PROFILE_CONTENTS
-DVC-W-NOINCLUDE, cannot open included file
-DVC-I-INPUTFILE, input file is: 
   LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;
-DVC-I-ONPAGE, on page [83] 
 
%DVC-E-BOOKABORT, aborting run -- book  ARUS_FACILITY_PROFILE.DECW$BOOK not created 
-DVC-I-INPUTFILE, input file is: 
   LISTNH$DUA1:[SIMONS.APAMEM]ARUS_FACILITY_PROFILE.DVI_BOOKREADER;
-DVC-I-ONPAGE, on page [83] 
 
%NONAME-W-NOMSG, Message number 00000000
T.RTitleUserPersonal
Name
DateLines
124.1Long filename BUGRAGMOP::FITZELLput nifty saying hereFri May 05 1989 09:266
    Sorry Al I probably should have stuck a warning in here early this
    week. There's a bug with long filenames that just surfaced last week.
    A workaround is to shorten the filename. Hopefully next week sometime
    we'll have this fixed.
    
    Mike 
124.2Filespecs 64 chars or lessCLOSET::FITZELLput nifty saying hereTue May 16 1989 11:065
    This has turned out to be a bug in the VAXC RTL which has been QARed.
    For now keeping the complete filespec less than 64 characters is the
    fix. 
    
    Mike
124.3filename too long revisitedCASEE::THOMSONRichard ThomsonWed Jan 17 1990 09:4625
    Our online builds have recently started to complain about the length of
    our filenames (they have been fine until now). The message reads:

%TAG-W-NAMETRUNC, tag <COUNTER>, line 304, file
        MEMEX_SYMBOLS.SDML
       Name HYPERVIEW_WORKING_DESIGN_DECWALT exceeds 31 characters.
       Name HYPERVIEW_WORKING_DESIGN_DECWAL is truncated version

    I should add that this is not all my own work. The bookbuild is adding
    the _DECWALT to my otherwise short-enough file name. Does this have
    anything to do with the previous problem? 
    
    If not, where is it coming from and why? How can I be blamed for
    creating too long a filename when I didn't add all those extra
    characters causing the overflow?

    But seriously folks, what is irritating about it is that it doesn't
    seem to affect anything: the book (appears to) build just fine. So why
    tell me about it, and more importantly, why *warn* me about it? Given
    that with sufficient warnings the build *does* bomb out, the last thing
    I need is extra warnings! What's happening?

    Regards

    Richard
124.4Documented in "Coding Documentation Source Files..."DECWET::OSHEAKate O&#039;SheaWed Jan 17 1990 13:076
    In the October 27 edition of "Coding Documentation Source Files for 
    the DECwindows Bookreader," section 1.3, "Known Problems," item 7
    describes this error message, and states that the error is harmless.
    
    As you suggest, it might be nice to change this to an information
    message instead of a warning since the output is unaffected.
124.5really, it's harmlessCLOSET::UTTWed Jan 17 1990 18:135
    I have no control over that message; it's issued in other situations
    where it may not be harmless and a warning is appropriate. No, I 
    need to fix the problem. But it *is* harmless...
    
    Mary