[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

159.0. "Book Shelf Verification Utility available!" by CDROM::JAGGER () Mon Jun 26 1989 18:02

	Book Shelf Verification Utility in CDROM::BSVU.

The utility consists of 2 files. BSVU.EXE and BSVU.COM.
To use it you can type
@BSVU output

and it creates two files output.err for error messages and output.log for
other messages.

It starts with the directory DECW$BOOK, if defined. Otherwise it uses
the users default directory.

It also uses the bookshelf file Library.decw$bookshelf if defined. Other
wise it uses LIBRARY.DECW$BOOKSHELF.

The utilty reads every line in every bookself that it can find starting
with the top level bookshelf.

An error occurs if the line does not contain BOOK \ filenaname \ asdfasdf
                                     or      SHELF \ filename  \ asdfasdf
A filename error occurs if the filename contains a "[","]",":","(",")" or
any character that is not allowed in a filename.type. We do not check the
filespec any further. If the file is not found an error message will be 
generated.

An error occurs if we cannot open and read an online BOOK, or if
the LMF producer, or product name is missing.

These errors are tallies and listed at the bottom of the logfile.

The logfile also contains a list of orphan files in the directory
that were not found by the utility. This allows you to check to make
sure that all the books and bookshelves in a directory can be accessed
by the bookreader, and to eliminate files that are not going to be
used.

Finally there is a DEBUG version, which lists more information.
to use:

DEFINE/USER DEBUG anything
@BSVU

Any questions?

Call Tom Jagger at DTN 381-1118 or write CDROM::JAGGER


T.RTitleUserPersonal
Name
DateLines
159.1more info, plsTLE::THORSTENSENWed Jun 28 1989 13:404
    Who would use this utility? We've been using the other Verify
    Utility and like it (except that we find some of the messages a
    bit cryptic). But, I don't understand how/why we would use this
    new one.
159.2Utility moved ... and other info.CDROM::JAGGERThu Jun 29 1989 10:1426
 In the future the bookshelfs will be binary files. The utility is
a C program that can be modified (hopefully) to handle the new
bookshelves. The current utility also 

  1. Finds orphan files

  2. Has a DEBUG switch ("DEFINE DEBUG gobiltygook" to activate)

  3. Provides summary statistics.

  4. Runs very fast...

  5. Is one .exe file.

TOM

The utility has been moved to CDROM::$1$DUA1:[sys$transfer]BSVU.*

the .* includes a .exe and a .com (the .com file is a jacket routing
to define sys$error and sys$output).

@BSVU test -> generates test.err and test.log (error messages and log messages)

TOM

  
159.3"Binary files" = DDIF?EPIK::DONOHUEMon Jul 10 1989 13:5610
    RE:-1
    >>In the future the bookshelfs will be binary files.
    
    Will the binary format be DDIF? When will base levels of the "Binary"
    Bookreader be available for testing? If DDIF, when might they accept
    DECwrite/decision input?
    
    Thanks,
    
    Jack Donohue 
159.4Location of verification utility savesetsCDROM::JAGGERMon Jul 17 1989 15:189
I just returned to find out that the bookshelf utilties and other files were
missing. From now on all files are in

CDROM::$1$dua6:[voila.public]*.* 

consists of BVU011.a, BSVU.exe, and BSVU.com

Thanks 
TOM