For the benefit of anyone else struggling to figure this out - it took me a few tries to nail this down, but to make VIRT=REAL work for VMS or other machine under VM, you need to build a CP nucleus with support for it.? The VIRT=REAL area needs to be reserved when VM IPLs.
The instructions that come with SIXPACK build a CP nucleus WITHOUT VIRT=REAL support, so here is a slightly modified version to build WITH that support:
LOGON MAINT
ACC 094 A
ACC 181 C
VMFMAC DMKHRC DMKHRC
* FOR EACH MODIFIED ASSEMBLE FILE "FILE ASSEMBLE":
* VMFASM FILE DMKHRC
VRSIZE
* YES
* 8192K (or whatever amount of memory to reserve for VIRT=REAL)
* YES
STATEW DMKSLC TEXT A
SPOOL PUN *
SPOOL PRT *
VMFLOAD VRLOAD HMKHRC
IPL 00C CLEAR
* You should see the message ¡°Nucleus loaded on VM50-1¡±;
* the difference between the CYL numbers should be more than just 1 or 2
IPL CMS
CLOSE RDR
READCARD CPNUC MAP
SHUTDOWN
* then re-IPL VM; during startup the VM console should show the VIRT=REAL size:
DMKCPI957I Storage size = 16384 K, Nucleus = 332 K,
?????????? Dynamic Paging = 07104 K, Trace Table = 248 K,
?????????? Free Storage = 0508 K,??? Virtual=Real = 08192 K
toggle quoted message
Show quoted text
On 6/21/21 6:57 PM, Frank D. Engel, Jr. wrote:
Thank you, that got me through it!
There were a few other issues after this but I was able to work through them and get it working.
On 6/21/21 1:01 PM, Peter Coghlan wrote:
Also, I think I discovered why those lines were commented out:
ASSEMBLER (XF) DONE
????????????? 4983????????? RDEVICE ADDRESS=(170,16),DEVTYPE=3375,CLASS=DASD
?? 158000???? 4984+??? 4,UNSUPPORTED DEVICE TYPE
IFO197 *** MNOTE ***
????????????? 6042????????? RDEVICE ADDRESS=(1B0,16),DEVTYPE=3390,CLASS=DASD
?? 158000???? 6043+??? 4,UNSUPPORTED DEVICE TYPE
IFO197 *** MNOTE ***
???????????? 10082????????? RDEVICE ADDRESS=(2A0,16),DEVTYPE=3380,CLASS=DASD
?? 670000??? 10083+??? 8,INVALID CLASS PARAMETER
IFO197 *** MNOTE ***
NUMBER OF STATEMENTS FLAGGED IN THIS ASSEMBLY = 3
*** ERROR ASMBLING DMKRIO ***
DMKRIO TEXT CREATED
Those are (mostly) the warnings I warned you you would get :-)
3375 and 3390 dasd are not supported devices so you get the:
4,"UNSUPPORTED DEVICE TYPE"
warning for them.? This is not a problem. (4=warning)
The 3380 is a supported device so you need to remove ,CLASS=DASD
from their definitions, otherwise you get:
8,INVALID CLASS PARAMETER
which is a problem (8=error).
On 6/21/21 12:47 PM, Frank D. Engel, Jr. wrote:
A bit confused here...? looking at these lines:
RDEVICE ADDRESS=(290,16),DEVTYPE=3390,CLASS=DASD
RDEVICE ADDRESS=(2C0,7),DEVTYPE=3278,MODEL=4
I was reading this as 16 device numbers starting with 290, which would be 290-29F, then 7 device numbers starting with 2C0, which would be 2C0-2C6.
I don't see 2A0 being defined as anything in that configuration file?
Or am I misreading that completely?
You are are correct.? I miscounted.? I was somehow thinking of 32 devices
starting at 290 which is not correct.? Your line above with CLASS=DASD
removed should be fine:
? ADDRESS=(2A0,16),DEVTYPE=3380
Regards,
Peter Coghlan.
