¿ªÔÆÌåÓý

Re: I forgot the VOLSER of drives (3380) I created


 

Ren¨¦ Ferland wrote:
Bertram Moshier wrote:

1. I create a drive (file) using the dasdinit command, but
dasdls isn't finding the VOLSER.
[...]
This is a bug in dasdls which Fish fixed. The corrected version
of dasdls will be available in the next release of Hercules.
Correct. If you want the fix, you will have to either wait until the next release of officially released, or else build the development version ('develop' branch) of Hercules yourself. Bill Lewis's most excellent "Hercules Helper" can help you do this quite easily if you're interested in doing that. Otherwise you will just have to wait for the next release.


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:
390.github.io/html/cckddasd.html. Therefore, if you want shadow
files, create your dasd with the -z option:

dasdinit -a -z vm380-0.cckd 3380 BGM380
Again, quite right. Shadow files are only supported for Compressed CKD images (CCKD/CCKD64). They are not supported for regular (non-compressed) CKD images. Refer to the mentioned web page () for more information:

"Shadow files are only supported for compressed dasd images."


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.
Yep. An easy mistake to make and one that many of us have made from time to time. Humans are known to sometimes make mistakes. It's nothing to be ashamed of.

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...

Join [email protected] to automatically receive all group messages.