IT Operations

AIOps on IBM Z

AIOps on IBM Z

AIOps on IBM Z is a group that brings together IT professionals to share their knowledge and expertise on leveraging AI-driven intelligence and IT Operations in order to accelerate decisions to maintain resiliency through the use of AIOps on IBM Z

 View Only

  • 1.  Using SMP/E information to identify products and verisons in IZSAM

    Posted Wed July 20, 2022 12:06 AM
    I'm seeking some input from as many users as possible on something we have been working on for a few years now.

    Currently for a product to be identified with a VRM the data needs to first be added to the GKB. There are times when customers have the updated first before we can add it the GKB. This is true with regards to applying maint to an existing product. What we have been working on is apart from scanning the Load libraries we are also scanning the CSI zones. This of course assumes the following:

    1. The products are SMP/E installed.
    2. The CSI zones for ALL products are shipped to all systems otherwise the identifications will not work.

    I'm curious as to how many users if the points above were the case would allow identification to be based on SMP/E?

    My only concern would be insisting on having all CSI zones shipped to all LPARs.

    Your thoughts please.

    Regards

    Jim K.

    ------------------------------
    Jim Kyriakakis
    ------------------------------


  • 2.  RE: Using SMP/E information to identify products and verisons in IZSAM

    Posted Mon July 25, 2022 09:57 AM
    Hi,

    Shipping the CSI's to all systems would be a big ask and contrary to the way I think most shops operate.

    If you did take this step, I would hope you'd make it optional.  Not optional for the time being with an eye towards forcing the requirement in the future but optional and never becoming a requirement.

    Thanks,
    Brian Venezia

    ------------------------------
    Brian Venezia
    ------------------------------

    Original Message


  • 3.  RE: Using SMP/E information to identify products and verisons in IZSAM

    Posted Tue July 26, 2022 07:28 AM

    Hi Jim,

    Though scanning SMPE CSIs to identify the installed products looks like a good idea, not every customer would want to move around CSIs to all Lpars, One another scenario is with Service provider clients who have a "build team" which performs the SMPE installations and ships the target libraries to all their clients, when ordering products from Build team client has an option to opt out of including the SMPE libraries with product delivery , and most of the clients I know do this, they dont need SMPE libraries as they dont manage SMPE environment and rather depend on the Build Team for SMPE work.

    Thanks 

    Abhinav Arora



    ------------------------------
    Abhinav Arora
    ------------------------------

    Original Message


  • 4.  RE: Using SMP/E information to identify products and verisons in IZSAM

    Posted Fri July 29, 2022 09:43 AM
    Hi Jim,

    We do the majority of our SMP/E work on one system and then ship only the TARGET libraries to the test and production environments. 

    Thanks,
    Tim

    ------------------------------
    Timothy Johnson
    ------------------------------

    Original Message


  • 5.  RE: Using SMP/E information to identify products and verisons in IZSAM

    Posted Mon May 22, 2023 02:10 PM

    Hi Jim

    As we need the maintenance levels for our reporting, we will ship the SMP/E zones out.

    Now that we use z/OSMF to ship target libraries for all our deliveries, it will simply be a tick in the box to send the SMP CSI's with the target libraries. No big deal for us.

    Thanks

    Michael 






    ------------------------------
    Michael Ferguson
    ------------------------------

    Original Message


  • 6.  RE: Using SMP/E information to identify products and verisons in IZSAM

    Posted Wed May 24, 2023 11:03 AM

    Hi,

    We have the CSI's on shared disks, as we do the SMP/e work on one system and copies the target datasets from the shared disk to the production dataset on the test and production LPARs.
    The shared disks are not scanned when we run the Inquisitor.

    Thanks,
    Mogens



    ------------------------------
    Mogens Larsen
    ------------------------------

    Original Message


Related Content