From:	CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 11-FEB-1989 12:40
To:	MRGATE::"ARISIA::EVERHART"
Subj:	WARNING -> Dual boot node LavC + shared LMF$license trap


Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Sat, 11 FEB 89 07:52:30 PDT
Received: from ucbvax.Berkeley.EDU by KL.SRI.COM with TCP; Sat, 11 Feb 89 07:35:18 PST
Received: by ucbvax.Berkeley.EDU (5.61/1.34)
	id AA24979; Sat, 11 Feb 89 07:25:30 -0800
Received: from USENET by ucbvax.Berkeley.EDU with netnews
	for info-vax@kl.sri.com (info-vax@kl.sri.com)
	(contact usenet@ucbvax.Berkeley.EDU if you have questions)
Date: 10 Feb 89 17:41:11 GMT
From: mcvax!cernvax!paul@uunet.uu.net  (paul)
Organization: CERN European Laboratory for Particle Physics, CH-1211 Geneva, Switzerland
Subject: WARNING -> Dual boot node LavC + shared LMF$license trap
Message-Id: <929@cernvax.UUCP>
Sender: info-vax-request@kl.sri.com
To: info-vax@kl.sri.com

WARNING -> Dual boot node LavC + shared LMF$license trap.

We fell into a trap and COULD NOT BOOT standalone. Read on...


On our dual boot node LavC we share a common sysuaf, net* etc.

When we upgraded to VMS V5 in January we chose to share the
licence database too using lmf$license logical name.

We discovered that the licence database is accessed BEFORE systartup_v5.com
is executed. We therefore had to move our call of clu_mount_disk.com out of
systartup.com (as was under V4) and into sylogicals.com.

Clu_mount_disk mounts the remote system disk (containing the licence database)
and makes it visible locally.

So far so good.

The problem occurred the first day we tried to boot NOT in a cluster.
Sylogicals.com called clu_mount_disk ...and waited for ever, because there
was no cluster.

We tried booting with startup_p1 "MIN" but sylogicals.com is still executed.

Where should we put the call to clu_mount_disk.com?
-->sylogicals.com is too early. (Hangs when boot standalone)
-->systartup_v5.com is too late.(Can't see remote LMF database in time)

DEC said "have 2 copies of the database"

We preferred a workaround, putting the following statements before the
clu_mount_disk.com call in sylogicals.com.

--------

$vaxcluster=f$getsyi("vaxcluster")
$!
$IF vaxcluster .EQ. 0 THEN $exit
$!
$! In a cluster, so OK to:
$@sys$sysdevice:[VMS$common.sysmgr]clu_mount_disk.com -
                                 "online$dua10" online_sys
$@sys$sysdevice:[VMS$common.sysmgr]clu_mount_disk.com -
                                 "uxocb1$dua0" uxocb1_sys
$EXIT

--------

I hope you read this before you HAVE to boot standalone. (Sigh...)

Paul Burkimsher
paul@online.decnet.cern.ch
vxcern::paul (HEPNET)
paul%online@cernvax (BITNET)
paul%cern.online@uk.ac.ean-relay (Janet)
...!cernvax!paul (UUCP)