I believe what you stated below is the major problem. z/OS systems have years of process, embedded meta information in PROCs, file names, HLQs, etc. Its not a “fresh disk install” its about existing processes and procedures, time to migrate, the risk involved in making the alignment happen and not to mention processes that do accounting, … and rely on all of those years of tribal knowledge based in the systems. z/OSMF can probably make a dent in some of the “alignment” by forcing compliance but the problem has roots that run much deeper. That coupled with products from multiple ISV’s that are also used to the way things used to be. It’s not just the IBM products. The ISVs are also strapped for resource and unless there was a united vision and approach in the industry I believe this will be a slow slog to normalized z/OS SYSPLEXes. K8s has the benefit of defining the ephemeral state.
Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook <https://facebook.com/matt.hogstrom> LinkedIn <https://linkedin/in/mhogstrom> Twitter <https://twitter.com/hogstrom> “It may be cognitive, but, it ain’t intuitive." — Hogstrom > On May 30, 2023, at 4:58 PM, Phil Smith III <li...@akphs.com> wrote: > > It's fine for IBM to push toward a standardized layout. I don't think that's > a bad thing at all, in principle-except for the existing shops who have zero > time/resources/interest in "fixing" their configuration. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
