Changing logicals on VMS?

From: ajp166 <ajp166_at_bellatlantic.net>
Date: Tue Oct 3 18:05:52 2000

From: Chuck McManis <cmcmanis_at_mcmanis.com>
To: classiccmp_at_classiccmp.org <classiccmp_at_classiccmp.org>
Date: Monday, October 02, 2000 11:39 PM
Subject: Re: Changing logicals on VMS?


>I got in this mess as follows:
>
>I installed an RF72 drive into my 4000/200 and proceeded to do a 'sho
dev'
>on it. It showed up on the DSSI bus as $24$DIA264:
>
>I then installed VMS 7.2 on to this drive, followed by a bunch of
layered
>products.
>
>Then I read in the KA660 technical manual how to "talk" to the DSSI
drives,
>(which is very arcane using the KFQSA but a snap on the KA640 and KA660)
>and proceeded to tell the drive to call itself node SYSTEM and unit 0.
>
>This worked fine, and I noted that I could now boot the system by
>specifying DIA0: rather than DIA264: (which I never could remember
anyway).
>
>Then I went to install another layered product. That installation failed
>because it couldn't find a file is was expecting in
>SYS$SYSDEVICE:[SY0.SYSTEMP] (or something very similar). So I did a dir
>SYS$SYSDEVICE: and sure enough there was nothing there, then I did a
SHOW
>LOGICALS and from there discovered that SYS$SYSDEVICE: was defined to be
>$24$DIA264: (the original name of the DSSI drive)


Ok, try set(or is it define) sys$sysdevice:[sys0.systemp] == $24$dia264

I may have this off some but it's only a simple necessity in systartup_*
to define the
system logicals for the devices you wish to be default.

>Now I could name it back again. But I'd rather tell VMS where the
SYSDEVICE
>now sits (for all the system, like on a permanent basis). If I 'define'
it,
>it changes for the current process but doesn't change universally and
more
>importantly other things are stuck that way to.
>
>Nothing is SYSTARTUP_VMS.COM defines these so they must be in a
parameter
>database somewhere else. That is where I'm looking now ...
>
check help define logicals.

Allison
Received on Tue Oct 03 2000 - 18:05:52 BST