Brian, I would like to assure you that this decision was not taken lightly, and was taken with all those considerations (and others) to extend both ordering types for as long as was feasible.
Some points I would like to make: - the z/OS ServerPac for z/OSMF is extremely similar to the CICS, Db2,and IMS ServerPac for z/OSMF. What is different? The Workflows which contain the configuration and verification, since they are product-specific. Where can you see those Workflow steps today? By looking at your z/OS CustomPac dialog JCL jobs you ran for your last z/OS installation. Those are the Workflow steps you'll see. So the "differences" are simply the way you submit the JCL jobs. Do you want to see how you lay down the data sets and assign them to volumes and catalogs, and how that is different with z/OSMF vs. ISPF? Look today at the CICS, IMS, and Db2 z/OSMF ServerPac. That is how it will be done - with the z/OS addition that you'll be able to use (or not use) a new master catalog, as you desire. - providing a "dual" method of installing the z/OS release (and other IBM products) requires two software manufacturing processes, for existing and every new product that GA's during that time. I'm sure I don't need to mention that the costs of have two production processes for every product in the IBM catalog is not insignificant. Now, that is what we are doing right now for CICS, IMS, and Db2, so that customers can have that choice right now for the non-z038 SREL products. It is expected that you set up and learn this process now, so that when the z/OS SREL arrives, it is not a unknown method of installing. Keep in mind, these "dual" paths and costs have been ongoing since September 2019. This overlap has been going on for a while, at varying levels for the product set. - As you mention, if you still want to see z/OS itself in z/OSMF ServerPac, then order z/OS V2.5 between Sept 2021 and January 2022. Install it. Throw it away. That would then be your "test order". That is how it will install should you re-order z/OS V2.5 (or a later release) when you are ready to install it. - You mention that the service on the ServerPac, if you keep it un-installled, will need more PTFs. Yes, if you insist that you must install a CustomPac ServerPac after that path is gone, it will age as any old ServerPac order will age. This is no different than ordering a z/OS release in ServerPac before it is end-of-marketing, putting it on the shelf, and having to install many PTFs today. I've seen lots of customers do that for z/OS V2.3, when they were on V2.1 and weren't ready to move yet. Always, I recommend that if your z/OS release is still orderable and yours has aged, order another one with current service. - You mention anyone running below z/OS V2.3, will have a harder path to z/OS V2.5. I would say that anyone on V2.2 or lower, wishing to go to z/OS V2.5, will have a harder path if they don't stay within the coexistence policy, and are not service supported. And this has little to do with how the ServerPac is packaged. I know you are involved in quite a few of those "long jumps" and all of the added complications they bring since there is no coexistence support, but I don't think that using z/OSMF to install V2.5 will be one of those largest concerns. Many of the installation and configuration enhancements were rolled back pre-V2.3 when they were released. I would install all the z/OSMF PTFs on those older systems to help as much as possible to get z/OSMF Software Management and Workflows up and running on the sandbox driving system. That should be done right now, unless the Customized Offering Driver (COD) is the better (and longer) path for the situation. Customers on V2.2 should be going to V2.4, which is orderable right now - do not delay. So, for z/OS V2.2 customers, I see no z/OSMF requirement impediment. -Marna WALLE z/OS System Installation and Upgrade IBM Poughkeepsie - ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
