Separating your own changes from IBM changes is probably the main point of documents like "What Mother Never Told You About VM Service." I believe you are better off NEVER modifying anything on your system? distribution disks. Using local disks to hold any system file changes you make, make it MUCH easier to re-apply those changes to subsequent releases of VM.
The thing is that I'm staring to understand (thanks to an user that promptly provided me with help) the logic on the 'layered' approach/procedure behind MAINT MEMO,? and looks to me a very clever way to implement a kind of 'version control' for maintainig the distribution changes... however, those reads now make me wonder why you just can do that. I mean, the way you say, it seems pretty straightforward (and I like it! :-D) ... no DMKRIO AUXLCL, no DMKRIO LCLxxxDK, etc, etc .... you just invoke VMFASM? ?along with DMKRIO DMKLCL (which I guess could be enough to deduce it is a Local change on CP's DMKRIO) and you're ready to rebuild CP?
