2 Oct
2000
2 Oct
'00
11:56 a.m.
I know, I should ask info-vax. But I'm not subscribed there :-(
I changed the nodename on my DSSI drive (looks like an HSC50 to the VAX)
and it still boots VMS but SYS$SYSDEVICE is set to $24$DIA264 not the
newer, more friendly SYSTEM$DIA0: I tried doing an autogen but that didn't
seem to change anything :-). Clues?
--Chuck
2 Oct
2 Oct
12:45 p.m.
I know, I should ask info-vax. But I'm not subscribed there :-(
I changed the nodename on my DSSI drive (looks like an HSC50 to the VAX)
and it still boots VMS but SYS$SYSDEVICE is set to $24$DIA264 not the
newer, more friendly SYSTEM$DIA0: I tried doing an autogen but that didn't
seem to change anything :-). Clues?
--Chuck
Off the top of my head I'd say look at SYLOGICALS.COM
If it's not in there it might be defined in SYSTARTUP_VMS.COM
BTW:
$ define/sys/exec SYS$SYSDEVICE SYSTEM$DIA0:
Zane
1:35 p.m.
The system$dia0 isn't especially newer or better. It is the name of the
disk with the allocation class set to 0. Check your drive firmware to
make sure that the alloclass on that disk didn't get changed to 24 wen you
changed the node name.
There is also a MSCP_ALLOCLASS parameter in SYSGEN but that is less likely
to be the culprit.
The allocation class is a mechanism to prevent like-named devices (i.e.
machines on a CI or DSSI each with a DxAxxx device) from confusing one
another.
On Mon, 2 Oct 2000, Chuck McManis wrote:
I know, I should ask info-vax. But I'm not
subscribed there :-(
I changed the nodename on my DSSI drive (looks like an HSC50 to the VAX)
and it still boots VMS but SYS$SYSDEVICE is set to $24$DIA264 not the
newer, more friendly SYSTEM$DIA0: I tried doing an autogen but that didn't
seem to change anything :-). Clues?
--Chuck
3:09 p.m.
Some firmwares also have a parameter containing a number to add to the
UNITNUM to make the final device name seen on the host. This might account
for your DIA0 -> DIA264
Here are the exact names of the firmware parameters which might be
relevant. I don't have a drive on line with the "add to unitnum"
parameters.
ALLCLASS 0 0 Byte Dec B
UNITNUM 0 0 Word Dec U
FORCEUNI 0 1 Boolean 0/1 U
On Mon, 2 Oct 2000, Paul Thompson wrote:
The system$dia0 isn't especially newer or better. It is the name of the
disk with the allocation class set to 0. Check your drive firmware to
make sure that the alloclass on that disk didn't get changed to 24 wen you
changed the node name.
There is also a MSCP_ALLOCLASS parameter in SYSGEN but that is less likely
to be the culprit.
The allocation class is a mechanism to prevent like-named devices (i.e.
machines on a CI or DSSI each with a DxAxxx device) from confusing one
another.
On Mon, 2 Oct 2000, Chuck McManis wrote:
I know, I should ask info-vax. But I'm not
subscribed there :-(
I changed the nodename on my DSSI drive (looks like an HSC50 to the VAX)
and it still boots VMS but SYS$SYSDEVICE is set to $24$DIA264 not the
newer, more friendly SYSTEM$DIA0: I tried doing an autogen but that didn't
seem to change anything :-). Clues?
--Chuck
8847
days inactive
8847
days old
3 comments
3 participants
participants (3)
-
cmcmanis＠mcmanis.com -
healyzh＠aracnet.com -
thompson＠mail.athenet.net