Andrew wrote:
I've amended CCKDDU64 to cater for 3390's larger than model
27's. It's not pretty, but it seems to do the job. I've dumped
a model-54 that has datasets allocated at cylinders higher
than 32760, checked it with cckdcdsk64, attached it to Hercules
and all appears good.
FAN-F**KING-TASTIC!! :)))
THANK YOU, Andrew!
I can't begin to thank you enough for your effort! You are a true Herculean in my book! :)
I've also dumped a Model-9 with the updated and the previous
CCKDDU64. A binary comparison comes up clean, except for cdh_vrm
in the ckd device header - the version of CCKDDU64 was updated
to 0.3.2.
Well that's not right.
The "cdh_vrm" field in the CKD/CCKD dasd device header is the version of the Hercules CKD/CCKD device's file format, not the version of the program that happened to create that particular dasd image file. That sounds like yet another bug (albeit a minor/cosmetic one) in both CCKDDUMP and CCKDDU64 that needs to be fixed.
Where can I place the updated source?
Please send it directly to me so I can be sure to get the fixed version it into Hercules.
Also, would anyone need a load module?
I guess I'll be needing that too. And the object code too.
So.... if we can get the program version bug fixed in both CCKDDUMP and CCKDDU64, then I would need a copy of the updated/fixed source code for both, as well as the updated/fixed object code for both , *AND* the updated/fixed load library module (linked executable?) for both as well. (Is that asking too much?)
I suppose if you can just send me the updated/fixed source code for each, I can try to create the object code and load library for each myself. But given my inexperience with z/OS, I'd rather not have to do that as I might only end up screwing something up, and I definitely *don't* want to do that after all of your hard work.
So, at the risk of pushing my luck, would I be asking too much if you could take care of this last little bit for me Andrew? I'd *really* appreciate it!
Thanks!
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
