DevSecOps Solutions - Group home

Packaging Improvements in IBM Z Common Data Provider v2.1

  
No one purchases software just to experience the joy of installing it. For that reason the packaging of a product should be focused on making the installation process as quick, as simple and as easy as possible. The upgrade of IBM Common Data Provider for z Systems v1.1 to IBM Z Common Data Provider v2.1 brings with the change in names packaging improvements which make the product easier to install, service and manage.

    • Getting the install information is easier since the product went from two program directories to one (the PDF file may be downloaded from the IBM Z Common Data Provider 2.1 Knowledge Center under the Getting started heading).
    • Going from four FMIDs to one for the base product means all of the installation requirements are in one place.
    • The number of install JOBs (JCL to update and run) is reduced from twenty-one to eight.
    • Even the names of the eight install jobs sort in the PDS so they are listed in the order they are to be run

        • HBO0SMPE - creates the entire SMP/E environment for installing Z Common Data Provider and the optional WebSphere Liberty Profile (more below)


        • HBO1ALLO - allocates the MVS target and distribution libraries needed to hold Z Common Data Provider 2.1


        • HBO2AZFS - allocates and mounts the ZFS target library


        • HBO3RMKD - creates the paths for the components in the ZFS


        • HBO4DDDF - creates the DD Definitions in SMP/E


        • HBO5RECV - performs the SMP/E RECEIVE


        • HBO6APLY - performs the SMP/E APPLY CHECK and APPLY


        • HBO7ACCP - performs the SMP/E ACCEPT CHECK and ACCEPT

There is a second set of seven samples to install the optional WebSphere Liberty Profile which is shipped in a separate FMID and installed in a separate ZFS from Z Common Data Provider so customers who do not need it will not have to allocate the extra disk space. This brings a great service improvement over using the DVD available for installing WebSphere Liberty which was added to version 1.1. In version 2.1 servicing the Z Common Data Provider WebSphere Liberty instance is done via SMP/E so when updates are shipped there is no more need to extract the contents of a DVD on a workstation, transfer it from the workstation to the z/OS server, delete the old version and run a JOB to extract the new one. Instead, when an update is shipped an SMP/E APPLY of the PTF does it all.

Servicing the main product will be much easier as well because of the change to a single FMID. If a fix requires updates to more than one component (e.g. Log Forwarder, System Data Engine, Definitions, Data Streamer or Data Receiver, etc.) it can now be shipped and installed in a single PTF rather than having to be shipped in multiple PTFs and having them contain requisites for each other. A single PTF can supply a fix which crosses any of the components. That does not mean that the components are tied together to the point that all components must be upgraded when one is. There is still the capability to upgrade a single component when an APAR fix only applies to that component. For example:

    • a Log Forwarder fix does not have to be shipped in the same PTF as a System Data Engine

    • if a Log Forwarder fix and a System Data Engine fix address the same problem they can be shipped in one PTF.

Finally, the GLA prefix has been entirely removed from the product parts, the datasets and the messages, making it easier to identify Log Forwarder elements and messages as belonging to Z Common Data Provider and the separate versioning of the Log Forwarder is removed. The other numbering and content of the messages are unchanged, the only prefix is now HBO rather than GLA. The Log Forwarder USS components have also been combined with the other USS components in a single ZFS.

So in summary, things are simpler, information is easier to compile, the install is easier and faster both to understand and to execute and service is logically improved.