Sigh. Ok, let me put it more plainly. You wasted a lot of time figuring out
what kind of disk drive you had. As I explained, probably not well, with SCSI
devices on MPE, the only thing you really need to know is if the device is SE
or Differential. If the disk is Single Ended, you know where to plug it in and
you use any of the SE disk IDs from IODFAULT.PUB.SYS. The disk will come up
and be usable.
A few months ago, I needed to install a disk to create another volumeset. I
found an old SE SCSI disk that had been connected to an HP 9000 series 300. I
did not have any information about the disk, but it did not matter. I picked
an ID, added it in SYSGEN and connected the device. MAPPER showed the drive as
an old ST1480 with 480 MB. Definitely not in IODFAULT.PUB.SYS. Doesn't
matter, all that is needed is for SYSGEN to specify the proper driver which in
this case is SCSI_DISC_DM. So I simply selected an ID, ST19171N, and used that
in SYSGEN. Rebooted the box and voila a small volume set on a single disk,
roughly the size of an old HP7933A (circa 1983.)
I have tried numerous DDS drives on the system and since they all have the same
driver, it doesn't matter what I called them. They all worked fine.
SCSI makes it much simpler compared to CS-80. I still remember the old MPE-II
and III days where one had to configure each and every device one piece of
information at a time. Device type, subtype, output device, record size,
class, etc. I spent far too many hours in the seventies and the eighties
configuring dozens of terminals on series III, 33, 44, 64, 68 and 70 system.
When the disk farms got bigger with systems having 10, 15 and 20 disk drives,
it took forever to configure these puppies. It was boring, exacting work. If
you had different disk drives, some had subtype x, other subtype y and yet
other subtype z. The various tape drives also had different subtypes.
My point was that in the nineties and the naughties, with SCSI disk drives and
MPE, the only thing that you really need to know is if the device is
single-ended or differential. The configuration for the single-ended disk is
the same for all of them. Output device: 0; record size: 128; device type:
disc; type: 4; subtype: 2; Device Manager: SCSI_DISC_DM. The only things that
vary are the path and the class.
The configuration for the differential disk is the same for all of them.
Output device: 0; record size: 128; device type: disc; type: 4; subtype: 2;
Device Manager: SCSI_DISK_AND_ARRAY_DM. The only things that vary are the path
and the class.
It's the same story for the tape drives.
I never even discussed changing the driver, so I do not understand why you
moaned about that issue. :)
I have for a long time now, complained about the fact no IBM disk drives are
listed in IODFAULT. I really like those disk drives. Now, I don't care. I
just use them and tell SYSGEN they are either SE or Diff by using an
appropriate ID.
Actually, I think it would be simpler if HP just had 2 entries instead of the
dozens of disk drive entries in IODFAULT. One could be SESCSI and the other
FWSCSI. All the other parameters are the same anyway.
Kind regards,
Denys. . .
Denys Beauchemin
HICOMP
(800) 323-8863 (281) 288-7438 Fax: (281) 355-6879
denys at hicomp.com www.hicomp.com
-----Original Message-----
From: [log in to unmask] [SMTP:[log in to unmask]]
Sent: Thursday, July 06, 2000 2:31 PM
To: [log in to unmask]; [log in to unmask]
Subject: Re: Seagate vs HP firmware on ST34573
Denys writes:
> It's actually even simpler than that.
>
> On MPE, you should be able to connect any size SE SCSI or Fast SCSI disk
> drive
> using any name you see in IODFAULT.PUB.SYS for such a disk drive, for
> example
> ST34573. The main thing is to make sure the DM (device manager or driver)
> that
> gets used is SCSI_DISC_DM. This also applied to CD-ROM.
Actually, I'd say that the better adjective is "more confusing," not
"simpler," at least until you understand what's going on.
Things either mean what they say they mean -- or they don't. For an old-time
HP3000 user, like me, who has been "taught" to get things dead right the
first time, with every decimal point and underscore in its proper place, or
suffer the consequences of having the machine crashing mysteriously, the
ability to stick in any name you want for the disc driver field in SYSGEN and
have the MPE ignore what you type in and then have MPE work it out properly
has to what you "meant to say" is a new world order for someone who was
brought up under MPE/V.
Don't get me wrong. I have always been a fan of autoadaptive designs, and I
like the way this works on MPE now. I'm just not too sure "simpler" is the
proper word to describe the condition while you're still required to enter a
"proper" driver for a new disc -- and if it's your first time doing it.
Wirt
|
