The ADCD owners confirm that they do now have plans to run IBM HealthChecker for z/OS against the ADCD (at least for the newer releases of z/OS that they support). Whether that was a direct result of this thread or not, I am not sure. It remains to be seen how much they take advantage of the exceptions that initially are reported.
Once that is underway, I expect, at least, that the DFSMRCL0 usermod will not be applied when a z/OS 1.13 ADCD system is subsequently built. I mention 1.13 only because that is the release where the HC of IEAVTRML is introduced and thus that is the release where the presence of DFSMRCL0 usermod would be flagged. Quite possibly they will be able to apply that "knowledge" to earlier releases that have IMS V9 or later (that being the release where the need for DFSMRCL0 went away, and knowing that earlier IMS versions are no longer supported). If any of you care to "contribute" by running HC yourself on the ADCD system and reporting things that both are flagged as exceptions and that in all likelihood would help just about the entire ADCD community to have changed, feel free to send me a note (but not that IEAVTRML one, please!). I mention the "entire ADCD community" only because I can imagine some exception situations being left alone in order to accommodate a subset of users who might need the flagged behavior. I have no specific examples of such things with respect to ADCD. I do also have hope that some information would accompany the distribution, setting the "expectation" for what exceptions one might see if running HC. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
