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.  TADz/IZAM Migration from 8.1 to 8.2

    Posted Fri June 21, 2024 02:39 PM

    With the understanding that V8.3 is now available,  we are migrating to V8.2.

    A couple of questions about job HSISWS02.  AS reported by our DBA:

    "The queries from Job HSISWS02 have numbers that don't match the expected results. There are 62 STADZB1 VIEWS which are included in the SQL query totals. Using different queries that exclude the 62 VIEWS the numbers start to match the expected results for V8.1. The VIEWS aren't included in job HSISWS02 expected results."

    1. Should we be concerned about the differences in the number of views?
    2. If not, is it okay to proceed from this point and what are the ramifications of the additional views



    ------------------------------
    Matthew Gilliam
    ------------------------------


  • 2.  RE: TADz/IZAM Migration from 8.1 to 8.2

    Posted Mon June 24, 2024 04:56 PM

    There is only one Db2 view (VWLOGIQ), that is part of TADz/IZSAM.  We have kept this view for legacy reasons.
    Any other views are site-defined and are not part of TADz/IZSAM.
    If you migrate from V8.1 to V8.2, the site-defined views should remain.
    You may have to drop/create some of these views to include new tables or new columns of existing tables.
    Job HSISWS15 has a list of the new Db2 objects to be defined for V8.2. 

    Something for your consideration:
    IZSAM V8.2 was GA 2020-12-11 (3.5 years ago)
    IZSAM V8.3 was GA 2023-08-25 (10 months ago)

    (a) You must implement ALL PTFs in V8.1 before migrating to V8.2, especially for changes in database objects.
        This is clearly emphasized in job, HSISWS01. 
    (b) Failure to fix the data in V8.1 will result in incorrect/incomplete data after migration to V8.2.  
        Once in V8.2, it is  NOT possible to fix these records.  They will remain as orphaned records in the TUSEMTD table.
        And these orphaned records can only be deleted via HSISUDEL.

    (c) It is also possible to migrate from V8.1 directly to V8.3, bypassing V8.2. 
        This may require significant amounts DASD space for the migration. 
        Here, V8.1 data is unloaded and then loaded directly into a newly created V8.3 Repository.    
        This is something to think about. We have a few customers that have adopted this approach.

    Tony 



    ------------------------------
    Tony Foo
    ------------------------------

    Original Message


Related Content