Conference bulova::decw_jan-89_to_nov-90

I think you have to set up a single LIBRARY.DECW$BOOKSHELF file
that contains entries that point to all the files on whatever devices
they may be on


eg

SHELF\file spec here  \Version 5.1 Documentation Shelf

    
    The way we do it is to have decw$book defined to be a searchlist:
    
   "DECW$BOOK" = "DISK$ROBIN:[DECW$BOOK]" (DECW$LOGICAL_NAMES)
	= "PHASE5$DESIGN:"
	= "PHASE5$PLANS:"
	= "DISK$CD_DOC_83332:[DECW$BOOK]"
    
    The first element of the searchlist contains a LIBRARY.DECW$BOOKSHELF
    which references other books and shelves. I think you have to do it
    like this, as the bookreader will (I believe) only look in DECW$BOOK:
    for the book files.
    
    Trevor

If I remember right, in version 1, you need to have a your bookshelf
file point to all of the books, even the ones on CD.  I think it took the
first one, so you would need to have it find the bookshelf file on your
disk (which has pointers to additional books) BEFORE it finds the one
on the CD.  Version 2 seems to merge the bookshelf files quite nicely.

Burns

I redefine DECW$BOOK to point to my system disk and then the CD so I can
have both the C documentation and the VMS documentation online.

However, I can't figure out where to do the DEFINE in my startup, do to
the async. nature of DECwindows startup.  Sometimes my definition gets
set up before the startup procedure gets to it and then it wipes out mine.

I was going to modify the DECW$LOGICALS.COM (or whatever it is called),
but decided to heed the warning about not modifying the file.

I tried running a command procedure in my startup after I started up
DECwindows that checked to see if the logical DECW$BOOK was defined and if
so, it redefined it, otherwise it waited for it to be defined and then
redefined it.  However, it always seemed to be defined, but it always
got clobbered when I redefined it.

Is DECW$BOOK one of those logicals that is predefined and present when VMS
boots?

Puzzled,

Bob

    I create my logical in the system logical name table.  The system
    logical will always be found before the DECW logical and will take
    precedence.

               Dave

    Not only do you have to set decw$book up as a search list you have
    to combine a file (whose name i forget) to get it to come up on
    the main menu!!!
    
    Gerry_who_has_bookreader_using_a_local_disk_and_an_RRD40

    I have my Library.DECW$BookShelf file point at other library files on
    both local and remote systems and it works great - here's the library
    file on my workstation:
    
SHELF\Dub0:<DECW$Book>Library\CD Library
SHELF\MPGS""::Sys$Common:<DECW$Book>Library\MPGS Library
SHELF\BULOVA::Docd$:<52Review.Online>Library\BULOVA Library
    
    This allows me to use my RRD50, a local cluster cluster that I manage
    (and who's library I try to keep well stocked), and BULOVA for my
    libraries. I didn't set up DECW$Book as a search list because it kept
    channels open to *all* of the library files that it contained; by
    putting the pointers in my local library file, I only have channels
    open to libraries that I'm currently looking in.
    
    /Harley

Re: .-1

I also tried putting an entry in my LIBRARY.DECW$BOOKSHELF file which pointed 
to a remote node's LIBRARY.  Sure, the local Bookreader opens up the remote
library file OK because _that_ pointer has the nodename info in it, but of
course the remote LIBRARY.DECW$BOOKSHELF has entries _without_ the nodename
(since they're all local to the remote system) which just point to the files.
Thus at this point Bookreader looks in the _local_ DECW$BOOK: for the files,
can't find them and gives errors.

Did you modify the LIBRARY.DECW$BOOKSHELF files on the remote nodes to specify
full network file specifications?

Paul

re .8

I've been using *exactly* what I posted for a long time with no problems, and
the remote library files don't have any node specifications in them. Try copying
the line that references MPGS to your library file and see if you can get my
library.

/Harley

re .9

>>I've been using *exactly* what I posted for a long time with no problems, and
>>the remote library files don't have any node specifications in them. Try 
>>copying the line that references MPGS to your library file and see if you 
>>can get my library.

Tried that (plus I copied the BULOVA line too).... same error (as expected)
opening file - file not found.  That's what I would have expected though, since
LIBRARY shelves usually just contain entries that specify local files.

How on earth is it working for you?  Are you perhaps running a later version of
Bookreader than me?  I'm running DECwindows V5.2 version under VMS V5.2.

Paul

    RE:.10 and others
    
    I could not do the same thing as .9 either but an associcate running 
    V2 of DECwindows bookreader says it works on V2 but not on V1 of 
    Bookreader.
    
    	/s/	Roger
    

re .10,.11

I just tried it with the following results:

VMS V5.1, DECW V1	Failed
VMS V5.2, DECW T2	Worked
VMS X5.3-461		Worked

They all copied my LIbrary.DECW$BookShelf file to their workstations. MPGS is
currently running VMS V5.2 and DECW V1.1

/Harley