Re: VM/ESA woes (W state 9025)
|
It works because Hercules does/did not correctly emulate the default controller which I believe is a 3390. It is however possible to connect 3390 DASD to a 3380 controller which Hercules does emulate correctly. So when you configure as below, it works¡ ? Dave G4UGM ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of trp
Sent: 07 January 2021 00:25
To: [email protected]
Subject: Re: [h390-vm] VM/ESA woes (W state 9025)? Well, it's now solved.
A friendly sould gave me his copy of hercules.cnf for VM/ESA.
Though his file worked, I wondered why mine didn't. So I found out why: 0123 3390 $(DASD)/240RES.123 cu=3880 0124 3390 $(DASD)/240W01.124 cu=3880 0125 3390 $(DASD)/240W02.125 cu=3880 0126 3390 $(DASD)/240W03.126 cu=3880 #0127 3390 $(DASD)/SPAREONE.127 0128 3390 $(DASD)/240SPL.128 cu=3880
This ¡±cu=3880¡± seems innocent, but the system managed to boot up after I removed it. Why? I do not know.
But now everything works great.
|
