William,
?
It seems to me that you are misunderstanding how to use the alternate nucleus arrangement.
?
First off, DMKSYS is a table of parameters; the resulting assembly doesn't contain any code.
?
If you want to test an alternate nucleus without any changes to a production system, you can do just that.? You still have to change DMKSYS to point to a new SYSVOL and new SYSRES (so that the system loader knows where to write the new nucleus), but your original production system nucleus would be unchanged as long as you specified a different SYSVOL & SYSRES.
?
If you needed to go back to a stable nucleus, you simply IPL from your previous sysres.
?
If you want to set it up like Melinda Varian's example, you can still do so.? But regardless, you still have to alter DMKSYS to point to the SYSVOL and SYSRES that you want the loader to write the nucleus to.
?
Note that the alternate nucleus is simply that: another copy of a CP nucleus on another volume.? It is not a copy of another set of checkpoint, error recording, and warm start areas.? If you want those to be unique on their own volume, you can set that up as well, but it really isn't part of the alternate nucleus support.
?
Finally, in VM/SP back in the day, you were allowed to specify SYSVOL=*, so that you didnt have to key in the alternate's volser, but you still had to change the SYSRES= value to the alternate dasd CUU hosting the alternate nucleus location.? SYSVOL=* is not allowed by HRC075DK.
?
Regards,
Bob
?
