Idea Overview
Currently, z/OSMF Software Management lacks the capability to merge a new Portable Software Instance (PSI) deployment into an existing, already deployed Software Instance (Target and Distribution zone).
When a customer orders separate PSIs that happen to share common base components (FMIDs), z/OSMF forces the creation of parallel environments. For example, if a user orders "IBM Intellimagic for z/OS" and "IBM Concert for Z" via separate ShopZ orders, both include the "IBM z/OS Common Data Provider" (FMID HHBO510).
If the user deploys the first PSI (Intellimagic) into a new Global, Target, and Distribution zone, they cannot deploy the second PSI (Concert for Z) into those same zones.
Attempting to use the same zones results in z/OSMF throwing errors regarding duplicate Target Zones and existing datasets (e.g., **.HBO.**). Consequently, the user is forced to create duplicate Target/Distribution zones and duplicate the disk storage for the shared product datasets.
Differentiation from APAR PH42028
Please note that this request is fundamentally different from the data set merge capability introduced in APAR PH42028 (delivered in March/June 2022).
-
APAR PH42028: Allows the merging of like datasets (ISPF types, ZFS file systems, etc.) within the same portable software instance during a deployment.
This Feature Request: Requests the ability to merge a newly acquired portable software instance into an already existing, previously deployed software instance/SMP/E zone to prevent the duplication of shared FMIDs across an environment.
Requested Solution
Introduce a "Merge to Existing Instance" or "Append" deployment capability within z/OSMF Software Management.
When deploying a new PSI, z/OSMF should allow the user to select an existing Software Instance (with their Global, Target, and Distribution zone). During the deployment configuration phase, the system should:
- Scan the existing zones to identify already-installed FMIDs.
Recognize overlapping FMIDs between the new PSI and the existing environment (e.g., recognizing HHBO510 is already present).
Skip the allocation and deployment of the duplicated datasets for the shared FMID.
Receive and apply only the net-new components and FMIDs from the new PSI into the existing Target/Distribution libraries.
Business Justification & Value
-
Storage Optimization: Eliminates the need to duplicate datasets for shared infrastructure components (like Common Data Provider), saving valuable DASD space.
Simplified Maintenance: Prevents the administrative burden of maintaining parallel SMP/E environments for the exact same base product. Without this feature, system programmers must apply PTFs and maintenance to multiple identical FMIDs across different zones.
Modernized User Experience: Customers do not always purchase or deploy all their z/OS products at the exact same time. The Software Management toolset should accommodate iterative software catalog growth without penalizing the user with redundant overhead.
Insufficiency of Current Workarounds
Support currently suggests two workarounds, both of which are inadequate for modern enterprise lifecycle management:
- "Order both products in the same ServerPac."
-
Limitation: This requires perfect foresight. Organizations frequently purchase and deploy new software months or years apart. They cannot retroactively combine ShopZ orders once the first product is already running in production.
"Order a CBPDO for the second product and install it over the existing PSI."
-
Limitation: This completely negates the primary benefits of z/OSMF Portable Software Instances. Customers are adopting PSIs to move away from the manual, time-consuming CBPDO installation process. Forcing them back to CBPDO for subsequent product additions breaks the z/OSMF modernization strategy.
Portal Public
Duplicate of
https://ibm-infrastructure.atlassian.net/browse/ZOS-4003