Re: I forgot the VOLSER of drives (3380) I created
|
Hello rene,
Thank you for your useful reply and link.
A missing comma, yup, it has been awhile since I was seriously programming in assember.? I even thought about putting the drives on the same line as the VM14 drives.? If I had, I'd have seen? my mistake.
Bertram Moshier
On Thu, May 16, 2024, 17:09 Ren¨¦ Ferland via <ferland.rene= [email protected]> wrote: >> 1. I create a drive (file) using the dasdinit command, but dasdls isn't finding the VOLSER.
This is expected behaviour for dasdls as is. Your dasdinit command creates an emulated DASD with a VOL1 label containing the VOLSER you specified but no VTOC (address) yet, and that's what dasdls is complaining about (no VTOC). dasdls does not display the VOLSER even though it is there. This is a bug in dasdls which Fish fixed. The corrected version of dasdls will be available in the next release of Hercules.
>> 2. I'm trying to add to the Hercules configuration file three drives, but Hercules won't accept them with shadow files.
Again, expected behaviour, shadow files are only supported only for compressed dasd files. Check it here: .
Therefore, if you want shadow files, create your dasd with the -z option:
dasdinit -a -z vm380-0.cckd 3380 BGM380
>> 3. I can get VM to see the drives, but I can't get them attached to the system via DMKSYS.
In your updated DMKSYS, you forgot to add a comma after VM14-3. As a result, I believe your added line about the BGM disks is treated as a comment. Add the comma and re-build the CP nucleus.
Cheers,
Rene FERLAND, Montreal
|
