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

Conference hylndr::cdrom

Title:	Topics for Discussion about CDROM
Notice:	ConOLD problems=150.; ConDist problems=151.
Moderator:	WMOENG::PACKARD

Created:	Thu Mar 14 1991
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	437
Total number of notes:	2500

434.0. "BNU/ODL Question" by CHR27::YEUNG (im2bz2p,ru?) Fri Apr 18 1997 14:33

LIBRARY.ODL uses DISK$<volume_name> resources to access the CDROMs.
This means every time we put in updated CDROMs, we have to run the
BNU setup utility to fix up the LIBRARY.BNU file.  How do I modify it
to use DAD$<service_name> instead?

On the InfoServer, my customer created services VAXDOC1, VAXDOC2, VAXDOC3,
AXPDOC1, AXPDOC2, and AXPDOC3.  They use the infoserver monitor utility to
automatically mount these services; so they can always access the CDROMs
using the logical names DAD$VAXDOC1, DAD$VAXDOC2, ..., no matter what
volume label is on the CDROMs.  All their BOOKREADER files have been setup
to use the logical names DAD$* to access the CDROMs.  So when they receive
new CDROMs, the secretary can put them in the InfoServer, the infoserver
monitor utility automatically remounts them, and everybody starts reading
them without having to change any software.  I would like to know how to
set up the LIBRARY.ODL file to accomplish the same thing.

Thanks

Tim

T.R	Title	User	Personal Name	Date	Lines
434.1	run the SETUP.COM on disc1	DONVAN::KRAETSCH		`Wed Apr 23 1997 13:45`	41
	You can use any logical device name you want when you run the library SETUP procedure and it asks where the disc will be mounted. So you could simply answer DAD$AXPDOC1 for disc1, etc. The OpenVMS MOUNT command always defines DISK$<volume_label> for your DAD$<service_name> device when you mount it. For example: LADCP> BIND /SYSTEM /CONNECT /NOWRITE AXPDOC1 %LADCP-I-CONNAVAIL, succesful connection to service AXPDOC1 %LADCP-I-BIND, service bound to logical unit DAD$AXPDOC1 (_DAD2:) SYSTEM> MOUNT /SYSTEM /NOWRITE dad$axpdoc1 AXPDOCMAR971 %MOUNT-I-MOUNTED, AXPDOCMAR971 mounted on _DAD2: SYSTEM> SHOW LOGICAL /SYSTEM /FULL DAD$AXPDOC1,DISK$AXPDOCMAR971 "DAD$AXPDOC1" [exec] = "_DAD2:" [concealed] (LNM$SYSTEM_TABLE) "DISK$AXPDOCMAR971" [exec] = "DAD2:" [concealed,terminal] (LNM$SYSTEM_TABLE) You can modify your system library to point to the generic DAD devices if you wish. To do this you would replace the "%<volume_label>" with "/DAD$<service_name>". For example: TITLE Online Documentation Library shelf /DAD$AXPDOC1/000000/contents.odl OpenVMS Alpha Library shelf /DAD$VAXDOC1/000000/contents.odl OpenVMS VAX Library This gives you a generic library that will access whatever library is mounted on your DAD$ services. However, the CONTENTS.ODL library on the target disc uses %<volume_label> references to access the category shelves. YOU STILL HAVE TO RUN THE CONFIGURATION SCRIPT (<disc1>:[SETUP]SETUP.COM when you get a new library to get the %<volume_label> references defined as BNU resources. As a temporary (i.e. unsupported/may change in the future) alternative, you can define the volume label as a logical pointing to the generic DAD device: DEFINE AXPDOCMAR971 DAD$AXPDOC1 The V1.0 BNU will treat an undefined "%<volume_name>" as a logical device name.
434.2	BNU Requires More Work	CHR27::YEUNG	im2bz2p,ru?	`Thu Apr 24 1997 13:43`	14
	Re .1: >>YOU STILL HAVE TO RUN THE CONFIGURATION SCRIPT (<disc1>:[SETUP]SETUP.COM >>when you get a new library to get the %<volume_label> references defined >>as BNU resources. That's the part I'm trying to avoid. The customer has 8 clusters and about 2 dozen standalone nodes that mount infoserver CDROMs. With the old bookreader format, nothing needed to be done when the secretary put in the new CDROMs. With the new BNU, we have to run SETUP.COM on over 30 different systems every time we get a new VAX or Alpha library. Tim